Last updated 13 October 2026
The headline: GOL offers one product, Check. Check receives the actions your AI is about to take (commands, and the names of files it writes), never your messages and never your file contents. From 13 October 2026 we keep a record of each check: when, which key (as a one-way hash), your network address, Check's version, which AI tool asked, and the verdict. If improvement records are on for your key, we also keep the command (with credentials removed) and the reason Check gave, to make Check better. They are on for keys created from 14 October 2026 and off for older keys; you can turn them on or off at any time in the console. Chats with GOL Support, our own assistant on this website, are recorded. When you sign in we save your email and how you first found us. We never sell your data. We do not share your data for cross-context behavioural advertising. Here is everything else, plainly.
| Data | Why | Where it lives | Retention |
|---|---|---|---|
| Your email address | Sign-in, license, receipts and the emails you ask for | Cloudflare KV (encrypted at rest) | Until account deletion |
| Single-use sign-in codes | Verifying it is really you | Cloudflare KV | Deleted on use or expires in 5 minutes |
| Session tokens and license keys | Keeping you signed in and metering usage | Cloudflare KV | Sessions: 30 days. Keys: until account deletion. |
| Credit balance, usage counts, and transaction log | Billing: deducting the per-use price, providing your transaction history | Cloudflare KV | Until account deletion |
| Payment records | Crediting your top-ups | Stripe. We never see or store card numbers. | Per Stripe's retention policy |
| IP address and user agent | Login notifications, session tracking, rate limiting, abuse prevention | Cloudflare KV (login records), Cloudflare standard server logs | Login records: until account deletion. Server logs: per Cloudflare's policy. |
| Device fingerprint (hashed) | Preventing duplicate accounts per device and enforcing free-trial limits | Cloudflare KV | Indefinite (hash only, not reversible to device identity) |
| Check record (from 13 October 2026), one row per check and per message: the time, a short one-way hash of your key (never the key), your IP address, Check's version, which AI tool asked, and the verdict | Legal and billing records, abuse prevention, and knowing how many people use Check | Cloudflare D1 database | As long as the law and our terms require; at present, indefinitely |
| Improvement record, only while improvement records are on for your key: the command your AI was about to run (with credentials removed), the name of a file it was about to write, and the reason Check gave. On for keys created from 14 October 2026, off for older keys; one switch in the console turns it on or off for future checks. Never your messages, never your file contents. | Improving Check: finding where it blocked something it shouldn't have, and what it missed | Cloudflare D1 database | Indefinitely, or until you ask us to delete it |
| Check message identifier (installs of version 4.3.0 or later): the identifier your AI agent gives each message you send (or, for agents that give none, one Check makes on your machine from the session and time). Never the message text. | Charging once per message, however many checks it contains | Cloudflare Durable Object (your wallet's billing record) | Today and yesterday, then deleted |
| Usage analytics for one internal test key we own | Producing published case studies of what Check catches on our own machine. Retention is limited in the server's configuration to that single key; a customer key is not retained. | Cloudflare KV | Rolling event windows on our own key only |
| Lifecycle events (install, uninstall, key created, key re-issued, free-limit reached, top-up) with the tool channel, OS, architecture, and the first 12 characters of the account ID. No command content. | Understanding adoption and where the product loses people, aggregate statistics | Cloudflare KV | Aggregate counters kept indefinitely; individual events only in a rolling 200-event feed carrying a truncated account ID |
| Feedback you submit from the console (message, category, your email, IP) | Reading and acting on your feedback | Cloudflare KV, and delivered to us by email via Resend | Until account deletion, or on request |
| Terms-acceptance record (timestamp, terms version, IP) | Evidence that you accepted the Terms | Cloudflare KV | Until account deletion |
| How you found us: the first page you landed on, the name of the website that sent you (for example google.com, never the full address), any campaign tags in that first link (utm_source, utm_medium, utm_campaign), the product you first signed in for, and the dates of your first and latest sign-in with a count of sign-ins | Understanding which pages and channels bring customers, so we know where to put effort | Your browser's local storage until you sign in; then Cloudflare KV, against your account email | Until account deletion |
| GOL Support chats (our own assistant on golproductions.com): each message you send, our answer, the page you were on, a random conversation ID and the time | A record of exactly what we told you, so either of us can check it later | Cloudflare D1 database | Up to 2 years, then deleted automatically |
| Website visitors' IP address (the human check) | Limiting how fast any one visitor can send messages, and blocking automated abuse | Held in memory for a few seconds; Cloudflare Turnstile, when a human check is switched on | Not stored by us |
--feedback in the terminal, we store your message and its kind. From the website, also the email you choose to give (if any) and your network address; from the terminal, Check's version, your operating system, which AI agents Check is installed in, and a shortened form of your key (never the whole key); from the console, your account email. It is kept to read and fix problems, and emailed to our support inbox. If Check itself fails on our server, we record the kind of failure and the version, never your command.Retired tools. AI Assistant and the Hallucination Checker were withdrawn on 12 October 2026; any data still held for them is deleted on request. Envie and Exnos, retired the same day, run on your machine. Envie versions before 0.8.0 send an anonymous machine identifier to obtain a free render grant; it is not stored. Nothing else is ever sent to us. See the Legacy section of our terms.
The golproductions.com website uses Google Analytics 4 (measurement ID: G-4E865XW6LD) to understand how visitors interact with the site. Google Analytics collects anonymised data such as page views, session duration, approximate geographic location, device type, and referral source. This data is processed by Google under its own privacy policy. Google Analytics does not have access to your GOL account data, API key, or any data you send through the Check API.
If you prefer not to be tracked by Google Analytics, you can use a browser extension such as the Google Analytics Opt-out Browser Add-on or enable your browser's "Do Not Track" setting.
The GOL website uses:
gol_first_touch): on your first visit we note the page you landed on, the name of the website that sent you and any campaign tags, in your browser only. It is sent to us only if you sign in, and saved against your account (section 1, "How you found us"). Clearing your browser storage removes it.We do not use advertising cookies or third-party tracking cookies beyond Google Analytics.
These providers touch slivers of your data so the products can work:
Each processes data under its own privacy policy and our instructions. Your data may be transferred to and processed outside Australia by these providers: mainly in the United States (Stripe, Google, Resend, and Cloudflare), in the European Union (Stripe), and wherever Cloudflare operates the data centre nearest the person using our products. Cloudflare, Stripe, Google, and Resend each maintain standard contractual clauses and/or certifications for international data transfers.
We send transactional email only:
No marketing lists unless you explicitly opt in, and anything optional will have a working unsubscribe.
If you email us for any business reason, we keep that correspondence as ordinary business records for the life of the engagement and as required by Australian tax and record-keeping law. We do not share it with anyone except the service providers listed in section 5, and never for marketing.
| Data | Retention |
|---|---|
| Sign-in codes | Deleted on use or auto-expires in 5 minutes |
| Rate limit counters | Auto-expires in 60 seconds |
| Daily spending records | Auto-expires in 48 hours |
| Sessions | Up to 30 days |
| Check record (each check and message, from 13 October 2026) | As long as the law and our terms require; at present, indefinitely |
| Improvement record (while switched on for your key) | Indefinitely, or until you ask us to delete it |
| Usage analytics events, our own internal test key | Rolling event windows for published case studies |
| Lifecycle event counters (installs, uninstalls, key issuance, top-ups) | Aggregate counts kept indefinitely. Individual lifecycle events sit in a rolling 200-entry feed carrying a truncated account ID; no command content in either. |
| Feedback and terms-acceptance records | Until account deletion, or on request |
| Transaction log | Rolling window of last 200 entries per account |
| Account records (email, keys, balance) | Until you close your account |
| Webhook idempotency keys | Auto-expires in 7 days |
| How you found us (first-visit and sign-in record) | Until account deletion |
| GOL Support chats on golproductions.com | Up to 2 years, then deleted automatically |
Ask us to delete your data and we will remove your account records. Unused credits are non-refundable and, if you have not requested full deletion, remain honoured in your account records indefinitely as described in the Terms.
Under the Australian Privacy Principles and applicable law, you have the right to:
Email [email protected] for any of the above. We handle requests in line with the Australian Privacy Principles, and we will respond like humans, not like a ticket queue. We aim to respond within 14 days.
If you are a resident of a US state with a comprehensive privacy law (including California, Virginia, Colorado, Connecticut, Texas, Oregon, and others), you may have additional rights:
To exercise any of these rights, email [email protected]. We will verify your identity using your account email and respond within 45 days.
GOL products use automated processing in the following ways:
None of these automated processes make decisions that produce legal effects or similarly significant effects on you. If you believe an automated decision has affected you unfairly, contact us at [email protected].
GOL products are not directed at individuals under 18 years of age. We do not knowingly collect personal information from children. If we become aware that a user is under 18, we will delete their account and associated data.
We take reasonable steps to protect your personal information:
In the event of a data breach that is likely to result in serious harm, we will notify affected users and the Office of the Australian Information Commissioner in accordance with the Notifiable Data Breaches scheme under the Privacy Act 1988 (Cth), as promptly as practicable.
If this policy changes, the date at the top changes with it. Material changes will be flagged in the console or by email at least 14 days before they take effect.
Privacy questions, access requests, or complaints: [email protected].