GOLProductions
Research
All Research The Problem AI Hallucination Root Causes Debunked Fixes Industry Impact Cost & Compliance The Fix
Pricing Docs
Products
Check Envie Exnos
Login
Legal

Privacy Policy

Last updated 24 September 2026

The headline: GOL has three products. Check processes the commands your AI session sends it, plus minimal operational data; command content is processed in memory and discarded immediately. For customer keys, none of it is written to storage (the one exception, our own key, is described below). Envie sends nothing to us. Exnos runs entirely on your machine and sends nothing to us. We never sell your data. We do not share your data for cross-context behavioural advertising. Here is everything else, plainly.

1. What we collect, exactly

DataWhyWhere it livesRetention
Your email addressSign-in, license, receipts and the emails you ask forCloudflare KV (encrypted at rest)Until account deletion
Single-use sign-in codesVerifying it is really youCloudflare KVDeleted on use or expires in 5 minutes
Session tokens and license keysKeeping you signed in and metering usageCloudflare KVSessions: 30 days. Keys: until account deletion.
Credit balance, usage counts, and transaction logBilling: deducting the per-use price, providing your transaction historyCloudflare KVUntil account deletion
Payment recordsCrediting your top-upsStripe. We never see or store card numbers.Per Stripe's retention policy
IP address and user agentLogin notifications, session tracking, rate limiting, abuse preventionCloudflare KV (login records), Cloudflare standard server logsLogin records: until account deletion. Server logs: per Cloudflare's policy.
Device fingerprint (hashed)Preventing duplicate accounts per device and enforcing free daily check limitsCloudflare KVIndefinite (hash only, not reversible to device identity)
Usage analytics for customer keysNone collected. Command content is processed in memory and never written to storage: not a truncated copy, not a hash, nothing. Check does not receive your prompts. What survives a request is usage counters and your billing record: the time, the cost, and whether it passed.NowhereNot retained
Usage analytics for one internal test key we ownProducing 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 KVRolling 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 statisticsCloudflare KVAggregate counters kept indefinitely; individual events only in the rolling 200-event feeds above
Feedback you submit from the console (message, category, your email, IP)Reading and acting on your feedbackCloudflare KV, and delivered to us by email via ResendUntil account deletion, or on request
Terms-acceptance record (timestamp, terms version, IP)Evidence that you accepted the TermsCloudflare KVUntil account deletion

Envie and Exnos appear nowhere in this table. Neither tool sends us anything at all. See section 2A.

2. What we do not collect

  • Your source code. GOL products never request or store your source code, and Check never reads your repository. Check does not receive your prompts, so code you paste into a prompt does not reach us. When your AI writes or edits a file, Check parses it on your machine; file contents are never sent. Envie renders videos locally on your machine; the HTML templates and output videos never leave your device.
  • Anything from Envie. Envie runs entirely on your machine and makes no network requests to GOL for any purpose. Earlier versions contacted our servers to authorise each render; that system was removed and no version we now distribute contains it. There is no licence check, no render grant, no machine fingerprint, and no telemetry. We have no way to know you are using it.
  • Your commands or messages, at all. Check sends one kind of content: the commands an AI generates, with some credential patterns redacted. It does not send your prompts. With each command it also sends the working folder (your username masked) and the results of the existence checks your machine ran. Commands are processed in memory and discarded the moment the verdict is returned. Installs made before 24 September 2026 still send each prompt to an endpoint we retired that day; it discards the prompt unread, stores nothing and charges nothing. Reinstalling Check stops it being sent. Nothing is written to storage for customer keys: not a truncated copy, nothing. What survives a request is usage counters and your billing record: the time, the cost, and whether it passed.
  • Anything from Exnos. Exnos runs entirely on your local machine. It communicates only between a Chrome extension and a server on 127.0.0.1 (localhost). It never contacts GOL servers, never phones home, never sends telemetry, and never collects or transmits any data. We have no way to know you are using it.
  • Advertising or cross-site tracking profiles. No advertising pixels, no cross-site tracking, no sale of data to anyone, ever. We do not sell or share your personal information for cross-context behavioural advertising.

2A. Envie and Exnos: local tools, and where their data goes

Envie and Exnos are free tools, released under the GOL Free License, that run entirely on your machine. They have no account, no key, and no server component of ours. Because we receive nothing from either tool, most of this policy simply does not apply to them: there is no data of yours for us to store, share, sell, retain, or hand over, and no deletion request to make of us, because we hold nothing.

Envie. Compositions, assets, audio, and rendered video files stay on your device. Rendering happens in a local headless Chrome process. Nothing is uploaded anywhere.

Exnos, and an important disclosure. Exnos reads live browser state, which can include page content, form field values, network activity, and console output. That data travels from the Chrome extension to a server on 127.0.0.1 (localhost) and then to the MCP client that requested it. It never reaches us.

However, your MCP client is normally an AI coding agent, and such agents typically transmit what they receive to their own model provider so the model can act on it. So while Exnos sends nothing to GOLProductions, browser content you expose to it can still leave your machine through your AI tool. When that happens, the receiving provider is the one handling your data, under their privacy policy and terms, not ours. We are not a party to that transfer and have no visibility into it.

Exnos reads local pages (localhost, 127.0.0.1, local files) and only the other sites you allow by clicking its icon; it masks passwords and similar fields and returns storage and cookies only when asked, with credentials redacted. Redaction works by pattern and can miss a secret in an unusual place, so do not allow sites showing credentials, payment details, health or financial records, private messages, or other people's personal information unless you are satisfied that sending that content to your AI provider is appropriate. Exnos is read-only and never clicks, types, or navigates.

3. Website analytics

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.

4. Cookies and local storage

The GOL website uses:

  • Google Analytics cookies (_ga, _ga_*): website analytics as described above.
  • Local storage: your session token is stored in your browser's local storage to keep you signed in. It is not sent to any third party.

We do not use advertising cookies or third-party tracking cookies beyond Google Analytics.

5. Services we rely on

Four providers touch slivers of your data so the product can work:

  • Cloudflare: hosting, Workers runtime, KV storage, and standard server logs (IP addresses for security and uptime).
  • Stripe: payment processing. We never see or store card numbers.
  • Resend: transactional email (sign-in codes, login notifications, low-balance alerts).
  • Package registries (npm, PyPI, crates.io): when a command installs a package, our server looks the package name up to confirm it exists. The request comes from our server, not your machine, and names the package. Results are cached for up to 24 hours, not linked to your key.
  • Google: website analytics via Google Analytics 4, and web fonts served from Google Fonts. When a page loads, Google's font servers see your IP address and browser user agent. Both apply to the website only, not the API.

Each processes data under its own privacy policy and our instructions. Your data may be transferred to and processed in countries outside Australia by these providers. Cloudflare, Stripe, Google, and Resend each maintain standard contractual clauses and/or certifications for international data transfers.

6. Emails

We send transactional email only:

  • Sign-in codes (on your request).
  • Login notifications (when a new session is created).
  • Low-balance alerts and spending notifications (if you enable them in settings).
  • Payment-related notices.

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.

7. How long we keep things

DataRetention
Sign-in codesDeleted on use or auto-expires in 5 minutes
Rate limit countersAuto-expires in 60 seconds
Daily spending recordsAuto-expires in 48 hours
SessionsUp to 30 days
Usage analytics eventsCustomer keys: none, ever. 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 recordsUntil account deletion, or on request
Transaction logRolling window of last 200 entries per account
Account records (email, keys, balance)Until you close your account
Webhook idempotency keysAuto-expires in 7 days

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 Status Terms.

8. Your rights (Australia)

Under the Australian Privacy Principles and applicable law, you have the right to:

  • Access the personal information we hold about you.
  • Correct inaccurate personal information.
  • Delete your account and associated personal information.
  • Complain to the Office of the Australian Information Commissioner if you believe we have breached the Australian Privacy Principles.

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.

9. Your rights (United States)

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:

  • Right to know. You can request a copy of the personal information we hold about you and the categories of third parties we share it with.
  • Right to delete. You can request deletion of your personal information. We will comply unless a legal exception applies.
  • Right to correct. You can request correction of inaccurate personal information.
  • Right to opt out of sale or sharing. We do not sell your personal information. We do not share your personal information for cross-context behavioural advertising. There is nothing to opt out of.
  • Non-discrimination. We will not discriminate against you for exercising any of these rights.

To exercise any of these rights, email [email protected]. We will verify your identity using your account email and respond within 45 days.

10. Automated decision-making

GOL products use automated processing in the following ways:

  • Check, command validation: automated validation of commands and code against your project environment. The result (pass/fail) is deterministic and based solely on whether the checked item exists in your environment or its package registry, and whether the command or file parses. No profiling or behavioural scoring is involved.
  • Check, messages: none. Check no longer reads or annotates your messages. Installs made before 24 September 2026 still send each message to an endpoint we retired that day; it discards the message unread, stores nothing and charges nothing. Reinstalling Check stops it being sent.
  • Envie: no automated decisions. Envie runs entirely on your machine, makes no network requests to GOL, and renders without any licence check or authorisation step.
  • Exnos: no automated decisions. Exnos reads browser state from the sites you allow and returns it, with passwords and similar values masked.

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].

11. Children's privacy

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.

12. Security

We take reasonable steps to protect your personal information:

  • Sign-in requires a single-use emailed code.
  • API secrets are stored in Cloudflare's encrypted secret store, not in source code.
  • Payments are processed entirely by Stripe and card details never pass through our servers.
  • Command, code, and message prompt content is processed in memory and not persisted to storage.
  • Timing-safe comparison is used for all authentication token validation.
  • Stripe webhook signatures are verified with HMAC-SHA256 to prevent forgery.
  • OTP attempts are capped and codes are deleted after use or expiry.

13. Data breach notification

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.

14. Changes

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.

15. Contact

Privacy questions, access requests, or complaints: [email protected].

© 2026 GOLProductions. All rights reserved.
Check Envie Exnos Console Terms Privacy Contact