Collect less. Explain the rest.
Effective October 13, 2026. ScratchSignal is independently operated and is responsible for the information described here. Privacy and deletion requests may be sent to hello@scratchsignal.win.
Account and billing data
Sign-in data notice updated October 13, 2026. Google and email authentication are processed through Supabase Auth. ScratchSignal stores the Supabase user identifier, verified email address, and optional display name needed to recognize an account and connect it to service access. ScratchSignal never stores a plaintext or reversible password; password verification and salted password hashes are handled by Supabase.
ChatGPT sign-in is processed by OpenAI Sites. ScratchSignal receives a site-specific user identifier and, when supplied, a contact email. It stores these with a canonical account identifier. A ChatGPT contact email is not treated as proof that an email destination is verified. ScratchSignal does not receive or store your ChatGPT password or conversation history through this sign-in.
If you explicitly link ChatGPT with a currently authenticated Google or email sign-in, ScratchSignal stores the link and its creation time so both methods access the same subscription and private records. Matching emails do not automatically link a ChatGPT account. For a new ChatGPT account, ScratchSignal stores the acknowledged Terms version and server-recorded acceptance time. Existing separately created accounts are not automatically merged.
For a new account, the Supabase authentication profile also receives a copy of the accepted Terms version, an acceptance time supplied by the ScratchSignal server, and whether the entertainment-purpose notice was acknowledged. ScratchSignal checks the submitted acknowledgment before it creates the application account. This is separate from the recurring-billing acceptance required at checkout. ScratchSignal does not add an IP address, user agent, or precise location to this acknowledgment record.
Stripe, not ScratchSignal, collects and stores payment-card details. ScratchSignal stores Stripe customer and subscription identifiers, billing status, and paid-through dates needed to provide and manage Signal Pro access.
Essential session and feedback cookies
ChatGPT sign-in uses the authentication session managed by OpenAI Sites. ScratchSignal's sign-out action clears its Supabase session, when present, and continues through the Sites ChatGPT sign-out route.
Supabase Auth uses first-party essential session cookies so a browser can remain signed in and refresh an authorized session. They contain session tokens, not a password. ScratchSignal sets these cookies for the site path with SameSite=Lax and requires Secure transport on the production HTTPS site. The browser maximum may be up to 400 days, while the usable session remains subject to token expiry, refresh, sign-out, account action, and server-side revocation. The current browser-based Supabase session flow requires script access to refresh the session, so these cookies are not HttpOnly.
An anonymous visitor who searches or contributes a Stock Signal receives one first-party, HttpOnly feedback cookie that contains a random token and expires after 30 days. ScratchSignal converts that token into a one-way pseudonymous reporter identifier so it can rate-limit reports, prevent one browser from counting repeatedly, and recognize independent corroboration. The token is not an advertising identifier and is not shared with retailers.
Alerts and community reports
When you request a game update, ScratchSignal stores the email address, selected state and game, consent record, confirmation state, and delivery status needed to send or stop the requested launch notice and relevant product updates. Automated official-report change emails begin only after their provider and retry checks pass. Stock reports store the selected retailer, game, observation type, time, moderation state, and a one-way pseudonymous account or guest identifier. Precise device location and travel history are not required; visitors select a retailer manually.
If Stock Signal is available, a search sends the five-digit ZIP and game number you entered from ScratchSignal's server to the Texas Open Data API over encrypted HTTPS. ScratchSignal does not put the ZIP in a query URL, usage counts, or application logs. A short-lived scrambled lookup key supports caching without putting the ZIP in the saved result. Official public retailer records returned by Texas may include a retailer address and ZIP; those records are not linked to the searching account or guest identifier.
Signed-in reports can enter the vetted signal immediately. Anonymous reports begin pending and cannot influence a displayed player signal unless at least three distinct guest identifiers independently corroborate the same retailer and game over at least 30 minutes. A one-way pseudonymous network bucket may also be used only to enforce anonymous rate limits; the full source address is not stored in a report or rate-limit key.
Community reports are excluded from signals after 72 hours and are designed to be deleted once older than 30 days by an independent daily scheduled cleanup, with traffic-triggered cleanup as a second path. Unconfirmed game-update requests are deleted after 30 days without confirmation. Confirmed requests are retained until unsubscribe or a deletion request; unsubscribed request records are deleted after 30 days. Operational logs may contain request and payment event identifiers, but not card details, passwords, or secret keys.
Private ticket ledger
Signed-in users may save structured ticket records including the monitored game, purchase date, quantity, price recorded from the official game feed, and optional retailer, note, result, and winnings amount. Entries are not publicly displayed and access is restricted to the signed-in account, subject to limited authorized operational access and infrastructure processing needed to run, secure, and support the service. Users can delete individual entries from the account page.
The ledger does not accept or store ticket photos, barcodes, or dedicated serial- or claim-number fields. Do not put sensitive ticket identifiers in the optional note. ScratchSignal is a supplemental recordkeeping aid; retain original tickets, receipts, tax forms, and other supporting records.
Anonymous traffic counts
ScratchSignal uses privacy-preserving daily traffic and interaction counters and does not set a tracking cookie. The service stores only a calendar day, an approved page or action, a broad source category such as search, AI, or direct, and a total count. It does not keep one row per visitor, an email address, account identifier, tracking cookie, browser identifier, full IP address, user agent, precise location, query string, or full referring URL. A daily scrambled value is used only to slow abusive repeat requests. It expires about one minute after the latest counted request and may remain until a later cleanup pass. The source address is never stored, and the scrambled value is never added to the traffic-count table. Cloudflare may set essential security or abuse-prevention cookies at the infrastructure layer.
Temporary comparison choices
Game-comparison selections, board filters, the self-set limit, and the chosen goal remain temporarily in the page. They are not saved to an account or added to ScratchSignal traffic counts. They reset when the page session resets.
Request access, correction, alert removal, or account deletion through the support page.