Security Policy
Effective November 6, 2026
The stories are meant to be shared. Your account credentials are not. Here is how we protect the service, what a game link makes visible, and how to tell us about a problem.
1. Safeguards and their limits
This policy covers the History, Allegedly website and game at historyallegedly.com and www.historyallegedly.com. It describes the current service; it is not a security certification, audit report, or guarantee that every vulnerability has been eliminated.
- Encrypted connections. The live site uses HTTPS to protect information in transit. This does not make a forwarded game link private or protect a compromised device.
- Managed authentication. Supabase handles authentication and password storage. Server endpoints check credentials before account operations. Studio voices also require a confirmed email and an adult-confirmation record.
- Restricted database access. Protected game and account operations run through server-side code. Database controls restrict direct browser access to protected tables. The newsletter-management endpoint checks the server-controlled owner role before returning subscribers.
- Seat permissions. Shared turn and vote submissions require a random seat token stored on the player's device. The server stores a cryptographic hash of it. Tokens are omitted from ordinary game-share links and saved game exports.
- Input and usage checks. The game validates supported actions and short text inputs. Game creation and joining have request limits; studio voices have usage caps. These checks reduce misuse but do not prevent every form of abuse.
- Server credentials. Privileged credentials stay in server configuration, rather than browser code. Public client identifiers are not administrative credentials.
Vercel, Supabase, and the providers in our Privacy Policy operate parts of the service. Infrastructure security, availability, and incident handling also depend on them. We do not promise uninterrupted service, end-to-end encryption of shared stories, or recovery of every lost draft or file.
2. Protect your account and stories
Use a unique password and protect the email account used for sign-in and resets. Sign out on shared devices. Do not send passwords, login links, or seat tokens in ordinary email. If you suspect unauthorized access, use the password-reset option and contact us.
Anyone with a shared-game link can read that story's player names, completed turns, and votes. A seat token controls writing, not reading. Recipients can forward links and exported files. Use invented names and avoid sensitive information in blanks.
Local words, media, sessions, and seat tokens depend on device security. Clearing browser data may lose your seat and unexported work. Save important files separately. Account deletion does not automatically remove shared stories or copies saved by other people; contact us about shared-game removal.
3. Report a security concern
Email hello@historyallegedly.com with “Security report” in the subject. Use this address for suspected unauthorized access or accidental exposure of information.
Include the affected page or feature, approximate time, what you observed, likely impact, and safe reproduction steps using your own account or synthetic data. Redact credentials and other people's information from evidence. If sensitive evidence is essential, describe it first and ask us to arrange an appropriate transfer method. Do not email secrets.
4. Responsible reporting
We welcome good-faith reports. Reporting an issue does not authorize access to someone else's account, inspection of private data, or intrusive testing. Contact us before testing that could affect people, data, availability, or a system you do not own. Agreed testing must stay within its expressly authorized scope.
- Use your own accounts and test data. If you encounter another person's information or credentials, stop and report it without downloading, copying, changing, or sharing that information further.
- Do not disrupt service, send bulk requests or spam, brute-force credentials, impersonate people, use social engineering, install persistent access, or alter or destroy data.
- Coordinate a reasonable disclosure timeline with us before publishing exploit details so we have an opportunity to address the issue. Do not publish exposed personal information or credentials.
- Provider systems, linked shops, other domains, and services operated by others are outside this policy's scope. Follow their reporting policies and obtain their permission where needed.
This is a reporting channel, not a paid bug-bounty program. Reporting does not create a payment obligation or authorize prohibited activity. Nothing here limits rights or protections provided by applicable law.
5. Reports and incidents
We review reports, assess impact, and prioritize appropriate remediation. We may ask for clarification or coordinate with an affected provider. We aim to acknowledge useful reports within a reasonable time, but do not promise a fixed response time, resolution deadline, or reward.
A confirmed incident may require restricting access, rotating affected credentials, applying a fix, preserving necessary evidence, and working with providers. We will notify affected people or authorities when applicable law requires it. We may limit technical detail during investigation or remediation.
Security-report information is used to investigate, respond, and protect the service under our Privacy Policy. Relevant details may be shared with providers or authorities where needed and permitted by law.
6. Changes and contact
We update this policy as the service changes. The date above identifies the current version. For account help, privacy requests, or security reports, contact hello@historyallegedly.com.