Cookie Policy
Effective date: October 11, 2026
This policy explains how SynthGap ("we," "us") uses cookies and similar technologies. It supplements our Privacy Policy.
In short: We set one cookie, and it is essential: it keeps you signed in. If you choose to continue with Google we set a second essential cookie, for at most ten minutes, that protects that sign-in. We use no analytics cookies. Advertising measurement by Google is off unless you accept it: our public pages (not the app) ask once, with an Accept and a Decline button of the same size, and load nothing from Google until you accept. If you accept, Google's tag sets cookies of its own, for measurement only: it tells us whether an ad of ours led to a visit, and whether you then signed up or subscribed (Section 2). You can change your mind at any time (Section 4). The notice you may see in the app is informational.
1. What we use
| Name | Type | What it does | How long | Category |
|---|---|---|---|---|
sg_session | Cookie (first-party) | Keeps you signed in. Holds a signed token containing your account name and an expiry time. Set only when you sign up or log in. HttpOnly, Secure and SameSite=Strict | Up to 14 days, or until you log out | Strictly necessary |
sg_oauth | Cookie (first-party) | Protects "Continue with Google" against forged sign-in requests: it holds a random value that must match when Google sends you back. Set only when you press that button. HttpOnly, Secure and SameSite=Lax, sent only to our sign-in addresses (under /auth). Removed as soon as the sign-in finishes | At most 10 minutes | Strictly necessary |
mad_recent_topics | Browser local storage (first-party) | Remembers the last few topics you searched so you can reuse them with one click. Stays on your device and is never sent to our servers | Until you clear your browser's site data | Functional (a feature you use) |
sg_notice_ok | Browser local storage (first-party) | Remembers that you dismissed the cookie notice | Until you clear your browser's site data | Strictly necessary |
sg_ads_consent | Browser local storage (first-party) | Remembers whether you accepted or declined advertising measurement, and when, so we don't ask on every page. Stays on your device and is never sent to our servers | Until you clear your browser's site data; we ask again after 180 days | Strictly necessary (it records your choice) |
We treat all of the above as either strictly necessary or as functionality you asked for that stays on your device. Laws such as the EU ePrivacy Directive don't require consent for those. If that changes, we will ask first. Advertising measurement is different (Section 2): it needs your consent, and we ask for it.
2. Third-party content on our pages
- jsDelivr. The app page (the one you sign in to and work in) loads the open-source scripts "marked" and "DOMPurify" from the jsDelivr content-delivery network. We don't set cookies through it, but like any web server it receives your IP address and browser details when your browser fetches those files. Our other pages, including the home page, load nothing from it.
- Google, to sign in. If you press "Continue with Google" you leave our site for Google's, which sets its own cookies under its own policy. Signing in loads no Google script, button or widget on our pages.
- Google, advertising measurement (only if you accept it). We advertise SynthGap with Google Ads. On our public pages (the home page, Help, the guides, the topic ideas and the legal pages; not the app page where you sign in and work, apart from the short report of a sign-up or payment described below) a notice asks whether Google's advertising tag may load. Until you press Accept, nothing is requested from Google. If you accept, your browser loads Google's tag, which sets cookies and sends Google the pages you view on our public pages, the address you came from, any ad-click identifier in the address, your IP address and details of your browser and device. The cookies are Google's: on our own site names such as
_gcl_auand_gcl_aw, and Google may set cookies of its own on its domains. Google uses the information to tell us whether an ad of ours led to a visit, and whether you then signed up or subscribed. We have switched ad personalisation (remarketing) off for the tag, so a visit is not used to show you ads elsewhere. Google handles the information under Google's privacy policy. Your browser's Global Privacy Control signal counts as a decline: with it on, we show no notice and load nothing from Google. - Google, reporting a sign-up or a first payment (only if you accept it). The app page does not load Google's tag while you work on your research. The one exception is the short time (up to twenty seconds) right after you create an account, or right after your first plan payment is confirmed: the app then opens a hidden page of ours, with no content of its own, which loads Google's tag and reports that the sign-up or payment happened. Besides what the tag always sends (which, from that hidden page, includes the address of the app page,
/app, and nothing you have written or found), that report carries the kind of event, a random order number made for the purpose (not your account name, your email address or any Stripe number) and, for a payment, the amount. It happens only if you accepted the advertising notice on a public page in its current wording, the one that mentions sign-ups and subscriptions (an Accept given to the older wording does not count), and your browser is not sending Global Privacy Control. If you declined, were never asked, or took your choice back, nothing is loaded from Google when you sign up or pay. - Stripe. When you subscribe or manage billing you are redirected to pages hosted by Stripe, which sets its own cookies under Stripe's cookie policy. Those pages are operated by Stripe, not by us.
3. What we don't use
We don't use analytics cookies, social-media widgets or browser fingerprinting. The only cookies and tracking pixels for advertising are Google's, and only if you accept them (Section 2).
When a link we share ends in a label such as ?ref=newsletter, the label stays in the web address while you move between our pages. We don't put it in a cookie or in your browser's storage, and it is saved only if you create an account (see our Privacy Policy).
4. Controlling cookies
You can delete or block cookies in your browser settings. If you block sg_session you won't be able to stay signed in. You can clear local storage from your browser's site-data settings.
Cookie choices
You can change your mind about advertising measurement at any time: change your choice. The same link, "Cookie choices", is at the foot of every public page. If you accepted, you can take it back there: we then stop Google's tag on that page and delete the Google cookies set on our own site (names starting _gcl_, _gac_ and _ga). The cookies Google set on its own domains stay in your browser until you delete them in your browser's settings. After you decline or take your choice back, nothing is reported to Google when you sign up or pay. You can also manage Google's personalised ads at adssettings.google.com. We ask again 180 days after your last choice.
5. Changes
Advertising measurement is the only optional use of cookies today, and we ask for your consent first. If we ever add another (for example, analytics) we will ask first as well, and update this policy. The effective date above shows the current version.
6. Contact
SynthGap · alikesen54@gmail.com