Cookies · Abyss

Last updated: November 1, 2026

In short

We keep a few things in your browser so Abyss works: your sign-in, your analytics choice and, on a Covered page, your Guest key.
Some parts of Abyss load an outside service to do their job: reCAPTCHA, Stripe, Pusher and Sentry.
In some countries the law lets Google Analytics load unless you turn it off, and there it does. Where the law asks for your consent first, a banner asks, and nothing is sent or kept for it until you accept. Where the law doesn't allow it, it never loads.
We set no advertising cookies, and we load nothing that identifies you or records what you do on a page.
You can change your analytics choice at any time, from this page.

The full text below is what counts.

1. What this page covers

Abyssal Corporation ("Abyss", "we", "us") runs abysshub.com. This page names everything the site keeps in your browser and every outside service it loads. "Cookies" here means cookies and the browser's own storage, which work the same way. What we do with personal data is in our Privacy Policy.

Google Analytics shows us which links bring people to Abyss. In some countries the law lets Google Analytics load unless you turn it off, and there it does. Where the law asks for your consent first, a banner asks, and nothing is sent or kept for it until you accept. Where the law doesn't allow it, it never loads.

Where the banner asks, refusing counts the same as not answering.
If your browser sends Global Privacy Control, we take it as a no.
Wherever Google Analytics loads, it loads on every page. It sets its own cookies to tell visits apart, and sends Google the pages you open, where you came from and details of your device and browser. Google receives your IP address with them.
Accepting also lets your browser keep where you arrived from (the campaign tags in the link you followed, the referring site's address and the first page you opened), which is saved on your account when you sign up.
On a Covered page, Google Analytics never loads and no banner shows.
Your answer is kept in your browser, so the banner doesn't ask again. To change it, or to turn Google Analytics off where it loads without asking, ask me again and the banner comes back.

We also count arrivals ourselves, from the page request your browser sends anyway. Nothing is kept in your browser for it (Privacy, "How many people use Abyss").

3. What we keep in your browser

These are needed for Abyss to work, so we don't ask for them. They stay in your browser, and only Abyss reads them.

Your sign-in. When you sign in, your browser keeps your Session, with the account details last shown to you, so pages show them straight away. A Creator with a Studio also gets one cookie naming their Studio Address and plan, so the Studio page shows them their own view. Logging out removes all of it.
Your analytics choice. Accept or Refuse, so the banner doesn't ask again.
Your Guest key. On a Covered page, your browser makes a random key and keeps it for that page's site. It ties your Runs on that link to this browser, so you can come back to them. We keep the key only as a hash. Your browser also notes once the key has passed reCAPTCHA's check, so you aren't checked again.
What carries you through signing up. A Creator's referral from a shared Widget link, which is sent with your first Run of that Widget. Inputs you typed before signing in, which are put back afterwards. The page to return to once you're signed in.
Your settings. The country you chose for prices, and the code language you picked in a Widget's API panel.
Work in the open tab. A Widget you're creating or editing, and notes that keep a page from redrawing or reloading needlessly. These stay in the tab's own storage and go when you close it.

4. What we load from other services

Each service loads only where it does its job, and may set what it needs to do it, under its own privacy policy.

reCAPTCHA, by Google, checks that a person is there: when you sign up with an email address, and when you run a Widget as a Guest on a Covered page. It receives your IP address and details of your browser.
Stripe.js, by Stripe, takes your card when you pay in the checkout. Your card details go to Stripe, not to us, and Stripe sets its own cookies to catch fraud.
Pusher keeps a live connection open while you're signed in, so notifications and your Runs' progress arrive without a reload.
Sentry receives a report when something on a page breaks, and the timing of some page loads, so we can fix the site and keep it fast. A report carries the page's address and details of your browser. Sentry records no sessions and no screens.
Google Analytics: where the law lets it, unless you turn it off; where the law asks for your consent first, only after you accept (section 2).

5. A Run's web pages

When a Run's output is a web page, we show it in a frame on its own address, apart from Abyss. That page is its Creator's work, and it can load whatever its Creator built into it.

6. Do Not Track and tracking by others

Your browser may send a Do Not Track signal. There is no agreed standard for it, so the site works the same either way. Global Privacy Control is different: we take it as a no to Google Analytics (section 2).
Google, through reCAPTCHA and, wherever it loads, Analytics, and Stripe, through Stripe.js, may collect information about what you do over time and across other websites, under their own privacy policies: Google's and Stripe's. So may whatever a Run's web page loads (section 5).

7. Your choices

To change your analytics choice, ask me again and the banner comes back.
Your browser's settings can clear or block cookies and storage. If you block them, Abyss can't keep you signed in, and a Covered page can't bring back your Runs on your next visit.

8. Changes and contact

When what the site keeps or loads changes, we update this page and its date. Questions go to support@abysshub.com.

Abyss Cookie Policy