Cookie Browser
Privacy Policy
Revised , revision 2026-11-11.1
Cookie Browser stores browsing history, bookmarks, passwords and site data in the local profile on your device. Account processing includes provider identifiers and profile details, while cloud chats are stored on the server. When you use AI, search, translation or voice features, the selected function may send a prompt, context, page, attachment or audio to its provider. Browser analytics is off by default; website analytics starts only after consent. Infrastructure providers may process your IP address and technical request data. Contact Cookie Support on Telegram to ask about access, correction or deletion.
1. General provisions
1.1. This Privacy Policy (the “Policy”) describes the collection, use, sharing, storage and protection of information when using Cookie Browser, the official Cookie website, Cookie Account, cloud Cookie AI, Cookie Search, page translation and support (collectively, the “Service”).
1.2. The Policy applies to information provided by the user, generated through use of the Service or processed by its infrastructure and feature providers. Visited websites, sign-in providers and other third-party services process data under their own policies.
1.3. Acknowledging this Policy is not consent to every possible form of data processing. Where separate consent is required for a specific purpose, it is requested separately; optional analytics is controlled by separate settings.
2. Information collected
2.1. Depending on the feature used, the Service may process the following categories of information:
- Account and profile identifiers: Google or GitHub identifier, name, email, email verification status, profile image and selected avatar.
- Technical information: IP address, browser type and version, device, operating system, session or installation identifier, Cookie version and request details.
- Information submitted for a feature: prompts and cloud chat history, search queries, text selected for translation, page text and address, agent action results, attached files, images and audio recordings.
- Support messages and Telegram account details visible in the conversation.
2.2. Cookie’s local profile on the user’s device stores browsing history, bookmarks, passwords, cookies and other site data, settings and other profile data. Browsing history, bookmarks and saved passwords are not uploaded to Cookie Account or synchronized with the account. A visited website receives ordinary network request data.
2.3. When cloud features are used, only information needed for the selected action is processed:
- Cloud AI receives the submitted prompt, necessary conversation history and selected context; when page reading is allowed, context may include page text and its address.
- Search processes the query; translation processes selected text; speech recognition processes audio or the text derived from it.
- Quota accounting processes the account identifier, plan, counters, reservations and operation times.
2.4. When contacting Support, the Service processes the message, attachments and Telegram account details available in the conversation. Browser diagnostics are attached to a report only when the user separately chooses that option. A random code used to receive a reply to an in-browser report is stored locally for up to 30 days or until a reply is received.
2.5. Analytics and technical operations may process installation, version, platform, launch, update, crash, selected feature, network request and operation-time data. Cloudflare and Vercel may receive the IP address and technical request metadata; the IP address is also used for request rate limiting.
2.6. When a paid order is placed, the selected plan, price, access term, payment status and technical transaction reference are processed.
3. Use of information
3.1. Information is used only to the extent necessary for the following purposes:
- operating the browser, account and online features, sign-in, session management, plans and quotas;
- fulfilling AI, search, translation and speech recognition requests;
- responding to requests, providing support and communicating about the Service;
- protecting accounts and infrastructure, preventing abuse, rate limiting and diagnosing errors;
- analyzing statistics and improving the Service within the user’s selected settings.
3.2. AI, search, translation and voice data is used to perform the feature selected by the user and account for its use. Analytics data is used according to the user’s settings; declining or withdrawing a choice stops future optional analytics transmission.
3.3. If a user separately submits a Cookie AI response rating, Cookie receives the rating, an optional reason from a fixed list, and a technical app-environment label. The answer text, prompt, conversation, account details and installation identifier are not sent for this purpose. Ratings are stored only as daily aggregate counters; an infrastructure provider may process the IP address to deliver and rate-limit the request.
5. Data storage and protection
5.1. Retention depends on the processing purpose, feature settings and mandatory legal requirements. Cookie analytics data is deleted on the following schedule:
- raw website and browser analytics events — up to 90 days;
- installation identifiers and linked daily records — deleted after 90 days without events;
- daily website aggregates without identifiers — up to 13 months.
- daily Cookie AI rating aggregates without identifiers — up to 13 months.
5.2. Account, session, cloud chat, order and support data is retained as needed to operate the Service, fulfil obligations and respond to requests. Account deletion removes linked records from the working database; it does not mean immediate removal from infrastructure backups and provider logs.
5.3. Cookie uses HTTPS, session validation, access controls and server-side storage of session token hashes. Internet transmission involves risks, and absolute security cannot be guaranteed. This statement does not waive duties or liability under applicable law.
5.4. Users can manage local data and analytics through Cookie, revoke sessions and delete their account. Contact Support to request access, correction, a copy, deletion or exercise other applicable rights. Proportionate account verification may be required.
6. Disclaimer
6.1. Cookie takes reasonable steps to protect information but cannot guarantee absolute security during internet transmission or processing by independent third-party services.
6.2. Cookie does not control third-party websites and services or their independent data processing, to the extent permitted by applicable law. This Policy does not exclude mandatory user rights or liability that cannot legally be waived.
7. Changes to this Policy
7.1. The current edition is published on the official website with its date and revision number.
7.2. Cookie gives clear notice of material changes. Where law or the nature of a change requires renewed acceptance, it is requested explicitly. Continued use of the Service alone does not constitute consent to new data processing.
7.3. Consent to optional analytics is requested separately, may be withdrawn and is not included in acceptance of the User Agreement.