SnapLab is a football play builder for coaches. This policy describes the website and companion app as they work today. We do not sell personal information, serve ads, or run advertising or analytics trackers in the current version.
Information we use
- Account: username, email address, password verifier, password-reset token verifiers, any legacy recovery-code verifier retained from before email recovery, and, for new accounts, the date and version of the Terms accepted. New verified accounts also have an email-verification timestamp. Our database stores password, recovery-token, and email-code verifiers rather than the plain-text passwords, tokens, or codes. Pending signup records contain your username, email, password verifier, Terms acceptance record, protected code and challenge verifiers, send and expiry times, and attempt count. They grant no account access. If you choose Google or Apple sign-in when available, we receive provider account identifiers and verified email information; Apple refresh tokens may be stored in encrypted form for account management.
- Content: formations, plays, player labels, route geometry, notes, folders, and playbook names that you create. A playbook owner can see the usernames and email addresses of coaches who join it.
- Security and operation: sign-in session tokens, short-lived sign-in state, one-use shared-playbook code verifiers and encrypted unused codes, email-delivery state, and limited request information needed to serve and protect the service. Abuse controls use hashed rate-limit keys derived from IP addresses and/or email addresses, with counts and time windows. Our hosting provider may process technical request details such as IP address, browser information, and timestamps to deliver and secure the site.
- On your device: the website stores account-specific unsaved play drafts in browser local storage for recovery across refreshes and tab closure, with a session-storage fallback when persistent storage is unavailable. Browser drafts expire for recovery after 30 days without an update and are removed when next accessed. During signup, sessionStorage temporarily remembers an opaque signup challenge and email address so the verification screen survives a refresh in the same tab; it stores neither your password nor the code and is cleared on verification or cancellation. A device preference remembers when you dismiss the getting-started guide. The mobile app stores its session in secure device storage and may keep unsynced drafts on the device. Depending on your device settings, system backups may also include local app data. The service worker caches app icons and the manifest for installation.
Why we use it
To create and secure accounts, sync your work, let you print and organize plays, enable playbook sharing that you choose, recover access, prevent abuse, and respond to support and privacy requests. We do not use your plays to train an AI model or display them publicly.
Email verification and account messages
New password accounts require a six-digit email code before the account and sign-in session are created. The code expires after 10 minutes, can be used once, and allows up to five attempts. A resend is available after 60 seconds and replaces the previous code; additional abuse limits apply. Existing accounts retain access without retroactive verification. New Google or Apple accounts use the provider’s verified email claim instead of another SnapLab code.
SnapLab sends verification codes, one welcome after a verified signup, requested password-reset links, and confirmation after a successful email password reset. The welcome uses your username when one is available. These are account messages, and creating an account, accepting the Terms, verifying an email, or contacting support does not subscribe you to newsletters or promotional emails. No newsletter subscription or automated marketing campaign is currently enabled. If we offer one later, it will have a separate choice and a way to unsubscribe.
Sharing and service providers
When you create a one-use access code and another coach redeems it, that coach can view, edit, add, and delete plays in the shared playbook. The owner can remove access. Our hosting and database services process data to run SnapLab. Resend processes recipient addresses, message content, and delivery information to send account emails. Verification codes and reset links are included in the messages sent through Resend; the welcome includes your username when available. We do not send your plays, formations, notes, password, or payment details to Resend as part of these emails. If you reply, your message goes to SnapLab support through our support email service. Your own email provider also processes the messages it receives.
The email templates do not add tracking pixels or per-recipient tracking links. If your mail app loads the public SnapLab logo, that image request can produce ordinary hosting request logs; the logo URL is shared across recipients. Email-provider delivery records and support correspondence may have their own retention schedules. Google or Apple receives information when you choose its sign-in flow; that provider’s own privacy terms apply. SnapLab does not currently load third-party embeds, ad pixels, or analytics scripts on its pages or enable third-party tracking across websites.
Signup and email-record retention
- A successful verification removes the pending signup records for that email. Abandoned pending signups stop being usable after 24 hours from creation; physical removal occurs during later signup, verification, or resend activity. Verification emails that cannot be sent cause that pending signup record to be removed.
- A welcome-delivery record temporarily contains the recipient address and rendered message, including the username, so a failed delivery can retry on a later sign-in for up to 24 hours. Accepted delivery clears the message payload; expired payloads are cleared during later signup activity. Minimal delivery state, such as the account ID, creation and send times, and attempt count, remains until account deletion to prevent repeat welcomes.
- Single-use password-reset links expire after 30 minutes. Reset records are removed after a successful reset or account deletion; expired records are pruned during later reset requests.
- Account deletion removes that account’s pending signup and welcome-delivery records from SnapLab’s active database. It does not recall delivered emails or automatically erase copies in your mailbox, support correspondence, or providers’ operational logs. For privacy requests about these records, contact us below.
Retention and security
Saved plays and account details remain until you remove them or delete your account. Deleted plays, folders, and playbooks are held for owner-only recovery for 30 days. After expiry they cannot be restored and are pruned during subsequent Recently Deleted requests. Deleting an account permanently removes its active content and recovery entries. Sign-in cookies expire after 30 days; the OAuth sign-in state cookie expires after 10 minutes. Expired sign-in and abuse-prevention records are pruned during later authentication activity. Signing out does not erase an unsynced local draft. Account deletion clears its drafts in the current browser’s site storage or mobile app; other open tabs, browsers, devices, and system backups may require separate clearing. Downloaded JSON backups are under your control and are not erased by account deletion. Provider operational logs may follow separate retention schedules. We use encrypted connections, restricted access, and hashed credentials, but no online service can promise absolute security.
Backups and support
Exports contain your owned plays, folders, playbooks, and saved formations, not credentials or collaborator grants. Imported backups create private copies. Keep downloaded files secure. The problem-report form prepares an email in your mail app; it does not automatically send a report or upload your plays. Browser information is included only if you choose it. Information you send to support is processed to answer your request, and may be retained in our email service.
Your choices
You can edit your username and delete your account and saved content in Account settings. You can remove plays and formations individually, control shared-playbook access, and clear local browser or app storage from your device. For access, correction, deletion, or other privacy questions, contact us below. We may need to verify that a request concerns your account or pending signup. Nevada residents can also send a request not to sell their personal information to the contact address below; SnapLab does not currently sell personal information. Applicable state law may provide additional rights.
Children
SnapLab is intended for coaches and adult account holders, not for children under 13. Please do not create an account for a child under 13. If you believe a child’s information was submitted, contact us so we can review and remove it as appropriate.
Changes
We will post the revised policy here and update its effective date. For material changes, we will provide a notice in the service or contact account holders by email before the change takes effect, where required by applicable law. Advertising, analytics, paid features, or new data uses will be described, with any required choices, before they are enabled.
Questions or requests: Snaplabsupport@gmail.com. Include the email address associated with your account or pending signup so we can verify your request. Do not send your password, verification code, password-reset link, playbook access code, or any legacy recovery code.