QUOME CLOUD COOKIE POLICY
Last Updated: November 5, 2026, 1:24 AM PST
Approved: November 5, 2026, 1:24 AM PST
Document ID: QUOME-LEGAL-COOKIES-CLOUD-001
Version: 1.0
This Cookie Policy explains how Quome, Inc. ("Quome", "we", "us", or "our") uses cookies and similar technologies in the Quome Cloud console at console.quome.cloud (and its successor hostnames) and in the sign-in pages that serve it. It should be read alongside our Privacy Notice.
Quome Cloud is small on purpose here: the console sets no third-party cookies, pixels, or scripts. Everything listed below is set by our own code, and we tell you exactly what each item is for.
1. What Are Cookies?
Cookies are small text files placed on your device when you visit a website. They let sites remember information about your visit — session state, preferences, your choices — so the site works properly and, where you consent, so it can remember how you like it.
We also use similar technologies — localStorage and sessionStorage in your browser — and we treat them the same as cookies for consent purposes.
2. How We Categorize Cookies
| Category | Purpose | What we set today | Opt-out |
|---|---|---|---|
| Strictly Necessary | Required for the console to function: your sign-in session, protection of the sign-in handshake, an action you were in the middle of when you had to sign in again, and the record of this cookie choice itself. | Yes | Not available |
| Functional | Preferences you set in the console, kept in this browser: terminal theme and font size, sandbox sounds, and which organization you had open. | Yes | Yes; the console then keeps these for the page only |
| Analytics | Aggregate usage measurement to help us improve the console. | None | Yes |
| Marketing | Measuring the effectiveness of our outreach or retargeting. | None | Yes |
| Social | Embedded content from social platforms. | None | Yes |
We keep the empty categories in the banner so that adding anything to them is a visible change that asks for your consent again, rather than a quiet one.
A complete inventory — every cookie and storage key we set, with its name, purpose, duration, and storage type — is published at /cookies. The inventory is generated from the code that sets each item, so it cannot drift from what the console actually does.
3. Your Choices
Cookie Banner
On your first visit we show a banner that lets you accept all, reject all, or customize non-essential cookies. "Accept" and "Reject" are presented with equal visual weight. Because our network edge does not yet tell the console where a visitor is, every visitor is treated the way the strictest law (the EU's ePrivacy rules) requires: nothing non-essential is stored until you choose. In U.S. states with opt-out laws, the banner's "Reject all" is also your "Do Not Sell or Share My Personal Information" choice, although we do not sell or share personal information in any case.
Preference Center
You can change your choices at any time from:
- The /cookies preference center, linked from the banner, the sign-up page, the consent screen, and every legal page
- The keyboard shortcut
Shift+Alt+Canywhere in the console
Withdrawing a category takes effect immediately: the console deletes the storage keys in that category and stops writing them.
Global Privacy Control (GPC)
If your browser sends the Sec-GPC: 1 signal, we automatically treat Marketing and Social as rejected. You do not need to interact with the banner for this to take effect: we record your GPC signal as your decision for those categories, and the banner still asks about the rest.
Browser-Level Controls
All modern browsers let you block or delete cookies directly. Blocking all cookies will prevent Strictly Necessary cookies from working, which will break sign-in. We recommend using the banner's category toggles instead.
4. Evidence of Consent
When you make a cookie choice, we record:
- Your consent ID (a random identifier stored in the
quome_consentcookie) - The categories you accepted
- Your IP address and user agent
- The region we derived for you (today: "unknown", since the edge sends no location)
- The version of this policy you saw
- Whether a GPC signal was detected
- Which account was signed in at the time, if any
Each change adds a new record and marks the previous one superseded; records are never edited. We retain them for five years to satisfy GDPR Article 7 and ePrivacy Directive burden-of-proof requirements. You can view your own history, and reset your consent ID — clearing the association with your prior choices — from the /cookies preference center; resetting makes the banner ask again.
5. Cookies on Apps Deployed Through Quome Cloud
Applications you or other customers publish on Quome Cloud (at *.quome.cloud app hostnames or on custom domains) are operated by their publishers. They do not include our banner, and this policy does not cover them. The only thing our infrastructure adds to such an app's traffic is routing; we set no cookies on it. If you have a question about an app published on Quome Cloud, please contact that app's operator directly.
6. International Transfers
Consent records are stored on our control plane in the United States. For EU/EEA/UK visitors, we rely on Standard Contractual Clauses and supplementary technical measures (encryption in transit and at rest, access controls, audit logging) for any transfers. See our Privacy Notice for full details.
7. Changes to This Policy
When we add a cookie category, start setting anything in a category that is empty today, add a vendor, or make other changes requiring re-consent, we bump this policy's version and the banner asks again automatically. Non-material updates (typo fixes, clarifications) do not trigger re-prompting.
8. Contact
Questions about this policy, or requests to access or delete a consent record, should go to legal@quome.com, or by post to the address in the Privacy Notice.
This Cookie Policy is informational and, together with the Privacy Notice, describes our practices. It is not a contract.
Document ID: QUOME-LEGAL-COOKIES-CLOUD-001
Version: 1.0
Classification: Public