Security
Security at SpellBout
SpellBout — Security Policy
Last updated: 24 August 2026
How we protect accounts and gameplay, and how to tell us if you find something wrong.
How accounts are protected
Sign-in is handled by a third-party identity provider, so we never hold a password on our own servers. If you sign in with Google or Apple, no SpellBout password exists at all. If you sign in with an email address and password, that password is handled and stored by our authentication provider — salted and hashed, never in plain text, and never readable by us. The providers we use are named in our privacy policy.
Sessions are held in the device's secure storage, and Face ID or fingerprint unlock, where you enable it, unlocks that stored session on the device rather than sending anything to us.
Every record is protected by access rules enforced by the database itself. Most player data cannot be read directly by an app at all — those requests go through our servers, which check that you are asking only for your own data before answering. One player cannot read another player's data even if a bug in the app asked for it.
How scores are kept honest
All scoring is calculated on our servers. The app never computes the score that counts, and a modified app cannot submit one. Every submitted word is re-validated server-side before it scores.
The clock is measured server-side too — from the moment your tiles are served to the moment your word arrives — so the speed bonus cannot be manufactured by a client that lies about how long it took. Submissions are limited to one per player per day at the database level, not merely in the interface.
Data in transit and at rest
Traffic between the app, this website and our servers is encrypted in transit, and this site is served over HTTPS with strict transport security. Data at rest is encrypted by our infrastructure providers as standard.
Inside our internal admin tools, email addresses are masked by default, and revealing one writes an audit entry. We hold no payment information of any kind — the game is free and has no in-app purchases.
Reporting a vulnerability
If you believe you have found a security problem in SpellBout or this website, please tell us before telling anyone else. Email security@spellbout.com with enough detail to reproduce it.
What we commit to:
- We will acknowledge your report and tell you whether we can reproduce it.
- We will keep you informed while we work on a fix.
- We will not pursue legal action against anyone acting in good faith under this policy, and we will credit you when a report leads to a fix, if you would like us to.
What we ask:
- Give us a reasonable opportunity to fix the issue before publishing it.
- Do not access, change or delete data belonging to anyone else. If you encounter another person's data, stop and tell us.
- Do not run denial-of-service tests, send spam, or use social engineering against our people or our players.
- Use your own account for testing.
We are a small team, so we cannot promise a fixed response time — but a real person reads every report. We do not currently run a paid bug-bounty programme.
Out of scope
Reports generated solely by automated scanners without a demonstrated impact, missing security headers with no exploitable consequence, and issues in third-party services we do not control are generally out of scope. Tell us anyway if you think we have missed something — we would rather read one report too many.
Privacy and your data
What we collect, why, how long we keep it, and how to have it deleted are set out in our privacy policy. You can request deletion of your account and data at any time from this page, without signing in.