Toastizle Labs LLC. operates this website. We do not sell your stored data or use optional analytics or advertising trackers. Our Cookies & Data page lists the information stored, its purpose, providers, and known retention limits.
Personal Accounts
Your visitor profile is private. We store your shared account ID, display name, optional bio, avatar color, appearance preference, and timestamps to provide your dashboard. We do not use Living Word study history, prayer records, notes, or application roles for this website.
Shared Sign-In & Connections
Google and Discord sign-in use the existing Supabase project shared with The Living Word. Identity providers may provide your email, identifiers, avatar/profile details, and authentication metadata. Connected identities let you use supported providers to access the same account. We request sign-in identity/email access, not Discord messages or Google files. Native linking is used; we do not merge accounts ourselves.
Connection changes affect your shared identity. Browser sessions on different domains remain separate. Living Word’s existing signup trigger creates its profile and statistics records for new shared users, including signups started here.
Account Security
This website validates your provider sign-in but does not offer or require two-factor authentication. It does not enroll, verify, or remove shared authenticators. Existing shared factors and Living Word security settings remain unchanged. Google and Discord may apply their own security checks during sign-in.
Product Licenses
The designated site owner can see website profile names, account IDs, and product access records to grant or revoke website access. Revoked entries remain in license history.
Keys and future purchase entitlements are tied to the account UUID. We retain only a one-way hash of a key and its last four characters in the key tables. License and attempt records support redemption, fraud prevention, ownership, and future product access. Raw key submissions are sent for validation without deliberate application logging. No checkout or payment-card collection is active.
Sealminer Adventure Game Accounts
Your product tile reads the linked license’s expiry from KeyAuth. If subscription expiry is unavailable, our server uses the saved key to look up its redemption time and duration. Only countdown data is sent to your browser for this lookup.
When enabled, we send your game username, email, password, and submitted key to KeyAuth to create your game account. We keep the account link, activation status, an encrypted key copy, a one-way key hash, and device reset timestamps in Supabase. The website does not store your game password or collect your hardware ID. KeyAuth handles game sign-in and device binding. When you choose Show Key, we open the encrypted copy or retrieve the key from KeyAuth and verify it against its stored hash. During redemption we encrypt the KeyAuth license token you supply and save it with your account link. For earlier redemptions, the site admin can save the token against the same key. We reveal it only to the signed-in owner on request. The link survives website profile removal.
If the site admin removes Sealminer from your account, we delete the website link, saved key and token, and website reset history. We keep a private one-way hash to block reuse of that key. KeyAuth manages the separate game account and license.
We check your website session and Sealminer link before sending your browser to the game’s Cloudflare release service. The service receives ordinary download request metadata and delivers the file from GitHub Releases. It does not receive your website session cookies, account details, or product key.
For Studworks, we check your website session and active license before directing your browser to the Studworks release service. That Cloudflare service receives ordinary download request metadata and delivers the Windows MSI from GitHub Releases. It does not receive website session cookies, account details, or product keys.
Contact & Abuse Prevention
The website contact form is currently disabled. If you contact us by email, we use your address and the information you send to respond and handle your request.
Service Providers & Logs
Supabase stores account and application records. Cloudflare is the hosting provider. Its Bot Fight Mode and JavaScript Detections process browser and request signals to detect automated traffic and may set a clearance cookie. Cloudflare also provides contact spam protection when the form is enabled. Google and Discord process their own sign-in flows. Those providers may handle network addresses, request metadata, security/audit events, and backups under their settings. Retention and processing locations vary by provider and service.
Optional Discord Community
The optional Discord community invite opens Discord. Visiting or joining that community is separate from signing in here and is subject to Discord’s own privacy practices and community rules. This website does not collect community messages through the invite link.
Access, Export & Removal
You can edit your profile, download its data and license summary, and remove the website profile in your account. Profile removal preserves shared identity, connections, 2FA, product licenses, and Living Word data. Visiting the dashboard again creates a fresh profile. Full shared-account removal requires a separately verified process because other applications and future ownership records can be affected.
Profile records persist until removal. License and key-attempt records have the limits described in the data inventory.
Questions & Updates
For privacy questions or requests about your data, email [email protected]. We may verify your identity before acting on a request. We publish updates to this policy here.