We use necessary cookies for secure sign-in and bot protection. We do not sell your stored data. We use no optional analytics, advertising cookies, tracking pixels, or cross-site advertising profiles.
What the Cookie Button Means
“Accept Necessary Cookies” acknowledges this notice. It does not enable optional tracking or waive your privacy rights. Public pages work without acknowledging the notice. Blocking necessary sign-in cookies can prevent accounts from working.
What Stays in Your Browser
| Storage | Why & How Long |
|---|---|
| Cloudflare clearance cookie (cf_clearance) | Records a JavaScript detection result or that your browser passed a security challenge. Its lifetime depends on the check or challenge. Cloudflare can set it before you acknowledge this notice. |
| Supabase session cookies (sb-…-auth-token, sometimes split into numbered chunks) | Keep your website session signed in and refresh it securely. Cookie lifetimes may be up to 400 days; actual session validity depends on Supabase’s settings. This site’s logout clears this site’s session. |
| PKCE code-verifier cookie (sb-…-auth-token-code-verifier) | Protect the sign-in return flow. Used during authentication and cleared on successful exchange or cookie expiry. |
| theme (local storage) | Remembers Light, Dark, or System appearance until changed or browser storage is cleared. |
| toastizle-cookie-notice-v1 (local storage) | Remembers acknowledgement of this essential-cookie notice until browser storage is cleared or the notice version changes. |
The decorative embers animate locally in your browser. The pause control keeps its choice only while this page stays loaded. Pointer coordinates are used only in memory to move nearby embers, and are not logged, stored, or transmitted by this effect. It adds no cookie, stored preference, analytics, or network requests. Reduced motion settings disable the effect automatically.
Google, Discord, Supabase’s dashboard, and other linked sites have their own cookie policies. The Sealminer and Studworks setup buttons check your existing session on this site, then send your browser to their release services. Website session cookies are not sent to those services. Cloudflare Turnstile, if contact is enabled, may use storage/browser signals needed for spam protection. We do not load it when contact is disabled.
Database Records & Logging
The website stores the Sealminer license token encrypted on the server when you redeem a key or the site admin adds it. Show Token uses your existing signed-in session and displays the token on request without saving it in cookies or browser storage.
Sealminer removal is recorded on the server through a private hash of the retired key. The license countdown does not add cookies or write to local storage.
This inventory describes application storage and the service providers involved. It does not claim that necessary cookies are the only data processed.
Sign-In & Connections
Information: Account UUID, email, provider identifiers and provider-supplied profile data; session and sign-in metadata.
Use: Authenticate you, link supported sign-ins, refresh sessions, and prevent unauthorized access.
Storage / Provider: Shared Supabase Auth project; Google or Discord handle their own consent flow.
Retention: Shared account persists until separately removed. Provider audit and session retention follow the project’s settings.
Your Website Profile
Information: Display name, optional bio, avatar color, theme, account UUID, and creation/update timestamps.
Use: Personalize your private dashboard and remember your preferences.
Storage / Provider: toastizle_profiles in Supabase. No public profile directory.
Retention: Until you remove the website profile. Returning to the dashboard creates a new one.
Existing Shared Authenticators
Information: Existing authenticator records may remain in the shared Supabase Auth account for other applications.
Use: Other applications may use these factors. Toastizle Labs does not offer or require 2FA or enroll, verify, or remove shared factors.
Storage / Provider: Shared Supabase Auth; no factor secrets or codes are collected by this website.
Retention: Existing factors remain unchanged. Their management and authentication audit retention follow the shared project's settings.
Product Keys & Licenses
Information: One-way SHA-256 key hashes, last four key characters, product identifiers, license terms, account ownership, grant/expiry/revocation dates, and an optional purchase reference.
Use: Redeem a key once, show your entitlements, prevent reuse, and support future paid products.
Storage / Provider: Separate Toastizle Labs key and entitlement tables. Complete keys are not stored in these tables. No payment cards are collected.
Retention: Licenses survive website-profile removal. The website does not process payments.
Sealminer Adventure (When Enabled)
Information: Game username and email, an encrypted copy and one-way hash of the redeemed key, an encrypted copy of the supplied KeyAuth license token, activation status, website account UUID, and HWID reset timestamps.
Use: Create your KeyAuth game account, tie it to your website account, display license time remaining, check eligibility for setup downloads, and enforce device reset limits.
Storage / Provider: Toastizle Labs stores the account link in Supabase. KeyAuth receives the submitted key, username, email, and game password for activation. Show Key decrypts the saved copy and verifies its hash. Older redemptions may be looked up in KeyAuth. The site stores the token supplied during redemption, or the token added by the site admin for an earlier redemption. Show Token decrypts the saved token for the signed-in owner on request. The site's server reads the linked KeyAuth subscription or uses the redeemed key to look up its duration and redemption time. Only countdown data is sent to your browser for this lookup. The site does not store an extra copy of the expiry, save the password, or receive your device ID.
Retention: The link survives removal of the website profile. Admin removal clears the website link, saved encrypted key and token, and reset history. The site retains a private key hash to prevent reuse, with no automatic expiry configured. KeyAuth manages its separate game records.
Sealminer and Studworks Installer Downloads
Information: Request metadata such as network address and browser details.
Use: Deliver the current Windows installer.
Storage / Provider: The website checks your session and your Sealminer link or active Studworks license before sending your browser to the corresponding Cloudflare release service. The service receives ordinary download request metadata and delivers the file from GitHub Releases without receiving website session cookies, account details, or product keys.
Retention: Download request metadata is subject to the release providers’ logging settings.
Website Product Administration
Information: Website profile display name, account UUID, and product grant and revocation records.
Use: Allow the designated site owner to manage website product access.
Storage / Provider: Toastizle Labs profile and entitlement tables in Supabase.
Retention: Revoked entries remain in entitlement history.
Key Attempt Limits
Information: Account UUID, attempt count, and start of the 15-minute window. No submitted key text is stored here.
Use: Limit key guessing to five attempts per account per 15 minutes.
Storage / Provider: Private Toastizle Labs database table, unavailable to ordinary clients.
Retention: Counters reset after 15 minutes on the next attempt; records remain until operational cleanup or shared-account removal.
Contact (When Enabled)
Information: Name, reply email, subject, message, duplicate-detection identifiers, review status, timestamps, and a keyed network-address hash for rate limits.
Use: Receive inquiries in a private owner inbox and limit spam.
Storage / Provider: Separate private Toastizle Labs tables. Cloudflare Turnstile processes anti-spam browser/network signals. No notification email provider.
Retention: The website contact form is currently disabled.
Bot Protection
Information: Browser and request signals, JavaScript detection results, and challenge clearance cookies.
Use: Distinguish automated traffic from regular visitors and protect the site against abuse.
Storage / Provider: Cloudflare Bot Fight Mode and JavaScript Detections.
Retention: Cookie lifetime depends on the check or challenge. Provider-side retention follows Cloudflare’s service settings.
Operational & Provider Logs
Information: Request times, paths, status codes, network addresses, browser/network metadata, authentication/security events, and errors may be processed by the hosting/authentication providers.
Use: Serve pages, investigate failures, prevent abuse, and protect availability.
Storage / Provider: Local server during development; Cloudflare when deployed, Supabase, and sign-in providers. Application code does not deliberately log messages, submitted keys, tokens, or authenticator secrets.
Retention: Log and backup retention varies with the provider and service settings.
Control Your Information
Use Privacy & Data to export your website data or remove your profile. Use your browser’s settings to clear local preferences and cookies. Clearing browser data does not delete database records. Read the Privacy Policy for shared-account effects and privacy requests.