Froogle | Cookie Policy

A | What is a Cookie?

Cookies are small text files - created by the visited website - that contain data. They are stored on the visitor’s computer to give the user access to various functions.

There are session cookies and non-session cookies.

A session cookie is temporarily stored in a computer’s memory while the visitor is browsing the website. This cookie is erased when the user closes his/her web browser (or after a certain time has passed).

A non-session cookie remains on the visitor’s computer until it is deleted.

B | Why Doesn't Froogle™ Use Cookies

No need

No incentive.

FroogleMe.com is a free, independent website that doesn’t have a need/incentive to collect people's personal information.

C | Site Functionality

The Facebook share button is used by visitors to recommend certain pages to their colleagues. Facebook controls that API, and Facebook could potentially store cookies when the share button is hit. However, Froogle™ has never seen any 3^rd-Party Facebook cookie used on this site.

Other functions on Froogle™ use 3^rd-Party suppliers. For example, when you visit a page with embedded YouTube videos, the content may contain 3^rd-Party cookies.

Altogether, Froogle™ only uses APIs from the following third parties:

• FaceBook (≈ 100 share buttons)
• Google (≈ 35,000 analytics tags; ≈ 35,000 adSense tags; ≈ 40,000 search bars)
• Microsoft (≈ 100 bingAds tags;)
• MIT (≈ 200 graphs)
• YouTube (≈ 4 videos)

So, you might care to consult the policies of these third party websites for information regarding their use of cookies.

D | Google Analytics

As mentioned, Froogle™ uses Google Analytics (hereinafter “GA”). GA stores cookies on your machine. Froogle™ does not have access to that data.

However, Froogle™ can retrieve Google’s high-level statistical reports. This visitor information includes location, duration, and more. Froogle™ only sees the aggregated data. Froogle™ does not see granular data.

For clarity:

Google tells Froogle™ that '1,000 Texas residents viewed Page X during Month Y'.

Google never tells Froogle™ that 'John Doe – from Anytown, TX – visited Page X at hh:mm:ss on m/d/yyyy'.

Plus, Froogle™ doesn’t need to know that personal detail.

Reason #1: Froogle™ doesn’t have an incentive to know people's personal information
Reason #2: Froogle™'s server logs collect a lot more web traffic data than Google Analytics.

F | Microsoft Clarity

Similar to Google Analytics, Froogle™ also makes use of Microsoft Clarity (hereinafter “MC”). All of the details [of this Cookie] which pertain to GA will also pertain to MC (ie, please see Part D for more information).

G | How to Reject Cookies

You can choose to reject or block the cookies set by any of the aforementioned third parties.

You can do so by changing your browser settings – see the “Help function” within your browser for further details. Please note that most browsers automatically accept cookies. So, if you don’t want cookies to be used then you may need to take these aforementioned deliberate steps.

H | Mobile Devices

For information on the use of cookies in mobile phone browsers (and for details on how to reject/delete such cookies), please refer to your mobile phone manual.

I | Effective Date

This policy became effective on March 9, 2025.

user comments

thank you, come again!
Froogle 1.1.1.7

COOKIE POLICY