AI Spoiler Shield privacy policy

Effective 7 November 2026

AI Spoiler Shield is a browser extension with one purpose: it hides GTA 6 content and spoilers on the pages you visit. This page explains exactly what data it handles.

What stays in your browser

• Everything is checked locally first against a keyword list. Posts with no match are never sent anywhere.
• Your settings, custom keywords and the "blocked today" counter are stored in Chrome's local extension storage on your device.
• If you add your own AI key or buy the launch pass, that key or purchase identifier is kept in this browser only, in extension storage that websites can't read. It is never synced.
• AI Spoiler Shield does not read or send cookies, passwords, form contents, browsing history, or your account details on any site.

What is sent, and when

Only when a post, video card or search result matches a keyword signal, AI Spoiler Shield sends that one item to our classification service to decide whether it is a spoiler. The request contains only:

• the item's visible text fields: author name or handle, community or channel name, title, body text, the text of the post it quotes or replies to, link title, image alt text and flair;
• the site type (for example "youtube") and section type (for example "search results");
• for some items, a small downscaled thumbnail image (about 256 pixels);
• your chosen mode (Story-safe or Total blackout) and whether trailers should be hidden;
• a random, anonymous install ID, used to apply rate limits and your daily allowance of AI checks, and (if you buy the launch pass) to record that the pass is active.

It never contains page addresses (URLs), query strings, cookies, the rest of the page, or anything that identifies you.

How posts are checked

You choose in Settings → "How posts are checked". Keyword protection on your device is always on, whichever you pick.

• Our AI checker (default; free with a daily allowance, or with the AI checks of the optional launch pass): matching posts are sent to our service as described above.
• Your own key (Cloudflare Workers AI or TypeSafe Jev): matching posts are sent from your browser directly to that provider under your own account and its privacy terms, not to us. Your key is stored only in this browser, in extension storage that websites can't read: never synced, never logged, never sent to us. Our service only receives one-way hashes of the items (with your anonymous install ID), to look up results it has already computed; it never receives the text, and nothing you check this way is stored by us.

The optional launch pass

• Payments are handled by ExtensionPay (extensionpay.com) and Stripe. We never see your card details.
• When you open the payment page, AI Spoiler Shield asks ExtensionPay for a random identifier for this browser and keeps it locally (it isn't synced). To use a pass on another browser, use the "log in" option on ExtensionPay's page there.
• To confirm a purchase, AI Spoiler Shield sends that identifier to our service, which asks ExtensionPay whether it has been paid and records "paid" against your anonymous install ID. The record expires after two days unless it is confirmed again (the extension re-checks once a day). ExtensionPay's answer can include the email address you paid with; our service only reads whether and when the pass was paid, and doesn't store or log anything else from it.
• The pass is a one-time pack of AI checks. Its balance (how many checks are left, and when it expires) is stored by our service under a hash of the purchase, made from the extension and the time of its first payment, never your email or payment details. Every browser you use the pass on draws from the same balance. Only AI checks our service actually runs use it; posts it has already checked are free. The balance is kept until the pass expires, 12 months after the purchase, and then deleted.
• One pass is active on up to 5 browsers at a time. To enforce that, our service keeps the anonymous install IDs that used the same pass in the last two days, under the same hash of the purchase.
• These pass records are kept in Cloudflare Workers KV and expire automatically: the "paid" record two days after it was last confirmed, the list of installs about two days after the pass was last used (at most four), and the result of a check with ExtensionPay after at most six hours ("not paid yet" after one minute).

How it is processed

• The service runs on Cloudflare Workers and uses Cloudflare Workers AI (the Clef models), which Cloudflare operates with zero data retention.
• To avoid classifying the same viral post thousands of times, the result (a few probability numbers, not the content) is cached for up to 7 days under a one-way hash of the item. The text and images themselves are not stored. Only results computed by our own service are ever cached; results from your own key are never written to it.
• To apply the daily allowance, we count how many checks your anonymous install ID used today. Nothing else is attached to that count.
• So that one network can't multiply the free allowance by creating new installs, free-tier checks are also counted per network per day. That count is stored under a keyed hash of your IP address (for IPv6, its /64 block) and the date, never the address itself. The key is a random secret created for that day only. Launch-pass checks aren't counted per network. Daily counts are kept in the Cloudflare region nearest you.
• The daily counts and the daily secret are deleted shortly after the day ends (UTC), and a launch pass's balance shortly after the pass expires. They are kept in Cloudflare Durable Objects, whose storage has a built-in recovery history: for 30 days, Cloudflare lets the account owner (us) restore an earlier state of it. We don't use that for these records, but it means deleted counts, secrets and balances remain technically recoverable by us for up to 30 days. Until then, a network count is pseudonymous: whoever holds that day's secret could test candidate addresses against it, and we don't. After those 30 days, it can't be linked back to an address by anyone, including us.
• Your IP address itself is processed transiently by Cloudflare to deliver the request and apply rate limits. We do not store it.
• We keep only aggregate operational numbers: daily totals of requests, AI checks, new installs and launch passes activated, plus cache hit rate, latency and how many items were hidden or allowed. These contain no content and no identifiers.

What we never do

• No analytics or tracking scripts, no advertising, no profiling.
• We do not sell or rent data, and share it only as described here: Cloudflare runs our service and the AI model; ExtensionPay and Stripe handle the launch pass if you buy it; and if you use your own key, your posts go to the provider you chose.
• No remote code: the extension downloads only a data file (keyword lists, numeric settings, and the text of the classifier's instructions used by the own-key mode).

Your choices

• Turn AI Spoiler Shield off, or off for a site, from its popup at any time.
• "Other sites" support is off unless you grant the extra permission in Settings, and you can revoke it there. On other sites, AI Spoiler Shield only uses its keyword list on your device; nothing is sent.
• Uninstalling the extension deletes all of its local data. The anonymous install ID isn't linked to your identity. On our side it's kept only with today's check count and, if you use the launch pass, with the pass records described above, all of which expire as described.

AI Spoiler Shield is an independent fan-made tool. It is not affiliated with, endorsed by or sponsored by Rockstar Games or Take-Two Interactive. Grand Theft Auto is a trademark of its owner, used here only to describe what the extension hides.

Questions: use the support contact on the AI Spoiler Shield Chrome Web Store listing.