KeyText Cookies Policy
Effective Date: April 29, 2026 Last Updated: November 7, 2026
COOKIES POLICY
This Cookies Policy explains what cookies and similar technologies are, which ones KeyText uses, why we use them, and how you can control them. It supplements our Privacy Policy.
If you have any questions, email [email protected].
1. WHAT ARE COOKIES?
A cookie is a small text file that a website stores on your device when you visit it. Cookies are widely used to make websites work, work more efficiently, remember preferences, and provide information to the site owner.
"Similar technologies" include things like local storage and session storage, which behave like cookies but are stored differently in your browser. Where this policy says "cookies," we mean both.
2. WHERE THIS POLICY APPLIES
This policy covers cookies set by keytext.app and its subdomains (the "Website").
It does not cover the KeyText Chrome extension, because the extension does not use cookies — see Section 6 below for how extension data is stored.
3. CATEGORIES OF COOKIES WE USE
We group the cookies on our Website into four categories. Only strictly necessary cookies are used by default; functional, analytics, and advertising cookies stay off until you allow them in our cookie banner.
3.1 Strictly Necessary
These cookies are required for the Website to work: remembering your cookie-banner choice, keeping you signed in on account pages, and protecting our forms from spam and abuse. They cannot be turned off through our consent banner because the site would break without them.
Spam protection uses Google reCAPTCHA. It is not loaded when a page opens — only once you start filling in one of our forms (the newsletter sign-up or the contact form).
3.2 Functional
These cookies remember small preferences so the site behaves the way you expect — for example, that you chose yearly billing on the pricing page.
3.3 Analytics
These help us understand how visitors use the Website in aggregate — which pages are visited, where visitors come from, and where they drop off — so we can improve the product and the documentation. We use Google Analytics 4 and Ahrefs Web Analytics. Neither is loaded until you allow Analytics.
3.4 Advertising
If you allow Advertising, we load the Google Ads tag to measure whether our ads lead to visits and sign-ups (conversion measurement). We do not use it for remarketing or personalised ads: Google's ad-personalisation signal stays switched off, and we don't use advertising pixels from any other network.
4. SPECIFIC COOKIES SET BY KEYTEXT
The exact set of cookies on a given page may vary, but the table below covers the cookies we currently set. We update this list when we add or remove a cookie.
| Cookie | Set by | Category | Purpose | Duration |
|---|---|---|---|---|
kt_cookie_consent (local storage) | keytext.app | Strictly necessary | Remembers your cookie banner choice so we don't show it again on every page load. | 12 months, then we ask again |
kt_promo_cache (local storage) | keytext.app | Strictly necessary | Caches the text of our site-wide announcement bar so it doesn't flicker on each page. Holds no information about you. | Until you clear your browser storage (refreshed on every visit) |
kt_scroll_to (session storage) | keytext.app | Strictly necessary | Remembers which section to scroll to when a link takes you to another page. | Removed as soon as the page loads |
sb-<project>-auth-token (local storage) | keytext.app (Supabase Auth) | Strictly necessary | Keeps you signed in on /account, where you start a checkout or manage billing. A short-lived …-code-verifier entry is added while you sign in. | Until you sign out |
_GRECAPTCHA | Google reCAPTCHA (www.google.com) | Strictly necessary | Lets reCAPTCHA tell people from bots when you submit one of our forms. Set only once you start filling in a form. | About 6 months |
kt_billing_period (local storage) | keytext.app | Functional | Remembers whether you selected monthly or yearly billing on the pricing page. | Until you clear your browser storage or turn Functional off (we delete it then) |
_ga | Google Analytics | Analytics | Distinguishes unique visitors so we can understand site traffic in aggregate. | 2 years |
_ga_<property-id> | Google Analytics | Analytics | Used by GA4 to persist session state. | 2 years |
_gcl_au (and _gcl_aw when you arrive from one of our ads) | Google Ads | Advertising | Links a later visit or sign-up to the ad click that brought you here, so we can tell which ads work. | 90 days |
Strictly necessary cookies are set when the feature that needs them is used. Functional, analytics, and advertising cookies are only set after you allow that category in our cookie banner — wherever you are, we don't set them by default.
Ahrefs Web Analytics sets no cookies and keeps no persistent identifier: Ahrefs says it discards raw IP addresses, uses a pseudonymous visitor ID that changes daily, and doesn't track visitors across days. We still load it only after you allow Analytics.
5. THIRD-PARTY COOKIES
Three third-party services can set cookies or similar data in your browser while you use the Website. All three are provided by Google (Google Ireland Limited for EEA/UK visitors; Google LLC elsewhere):
- Google Analytics 4 (Analytics) — only after you allow Analytics.
- Google Ads tag (Advertising) — only after you allow Advertising, and only for conversion measurement.
- Google reCAPTCHA (Strictly necessary) — only once you start filling in one of our forms.
Google's privacy policy explains how Google handles this data: policies.google.com/privacy. Ahrefs Web Analytics (Ahrefs Pte. Ltd., Singapore) also runs after you allow Analytics, without cookies; see ahrefs.com/legal/privacy-policy.
We have configured Google's tags to:
- Load nothing until you allow the matching category, through Google Consent Mode v2
- Keep ad personalisation off (no remarketing lists, no personalised ads), with Google signals disabled for Analytics
- Redact ad-click identifiers from Google requests whenever Advertising is off
You can also opt out of Google Analytics across all websites by installing the official browser add-on at tools.google.com/dlpage/gaoptout.
We do not use:
- Remarketing or personalised-advertising pixels (Meta, LinkedIn, TikTok, etc.)
- Third-party social-media share trackers
- A/B testing or session-replay tools
- Affiliate networks
6. COOKIES IN THE CHROME EXTENSION
The KeyText Chrome extension does not set cookies. Extensions installed from the Chrome Web Store can't set cookies in the traditional sense; instead, they store data through chrome.storage APIs.
KeyText uses two storage areas:
chrome.storage.sync— stores your Extension settings (such as your trigger prefix) so they follow you across the Chrome browsers you're signed into. This data is governed by Chrome's data policies.chrome.storage.local— stores a cached copy of your snippets, folders, and saved prompts (the copy on our servers is the source of truth), your sign-in session, and other device-specific state that doesn't sync.
Neither of these stores is a "cookie" under most cookie laws, and neither is shared with any website or third party.
7. YOUR CHOICES
7.1 The Cookie Banner
The first time you visit the Website, we show a banner asking what you'd like to do with non-essential cookies. You can:
- Accept all — strictly necessary, functional, analytics, and advertising cookies are enabled.
- Reject non-essential — only strictly necessary cookies are enabled. Functional, analytics, and advertising cookies are blocked.
- Customize — choose which categories to enable.
You can change your choice at any time with the "Cookie preferences" link in the footer of every page. Withdrawing consent is as easy as giving it: when you turn Analytics or Advertising off, we delete the cookies that category set on keytext.app and reload the page so its tags stop running immediately.
7.2 Browser Controls
Most browsers let you view, manage, and delete cookies through their settings. Search your browser's documentation for "manage cookies" or "clear cookies." Note that blocking strictly necessary cookies may break parts of the site (for example, signing in to your account).
7.3 "Do Not Track" Signals
Because there is no industry standard for interpreting Do Not Track (DNT) signals, our response is the same regardless of DNT settings: we never use remarketing or personalised ads, and analytics and ad measurement run only if you allow them in our banner.
7.4 Global Privacy Control
If your browser sends a Global Privacy Control (GPC) signal, we treat it as a refusal of functional, analytics, and advertising cookies for that browser and don't show the banner. You can still opt in later through "Cookie preferences" if you want to.
8. CONSEQUENCES OF DISABLING COOKIES
- Disabling strictly necessary cookies (for example, by blocking them in your browser) will break sign-in, will make the cookie banner reappear on every page, and may stop our forms from accepting your submission.
- Disabling functional cookies means small preferences (like the pricing-page billing period toggle) will reset on every visit.
- Disabling analytics cookies has no impact on your experience — we just won't see your visit in aggregate stats.
- Disabling advertising cookies has no impact on your experience either — we just can't tell whether one of our ads brought you here.
9. CHANGES TO THIS COOKIES POLICY
We may update this Cookies Policy from time to time to reflect changes in the cookies we use or in applicable law. When we do:
- We will update the "Last Updated" date at the top of this page.
- For material changes — adding a new analytics or marketing cookie, for example — we will re-prompt you with the cookie banner so you can renew (or refuse) your consent.
10. CONTACT
Cookie or privacy questions: 📧 [email protected]
General support: 📧 [email protected]
Postal address: KeyText, Sheik Zayed Road, Sama Tower, Office 305, Dubai, United Arab Emirates
Effective Date: April 29, 2026 Document Version: 1.1
Cookies should be predictable and few. If you spot one we haven't documented here, please tell us: [email protected]