DRAFT
Privacy Policy
DRAFT. Not legal advice. Not in force until reviewed by a lawyer and published. Last updated: [DATE TBD].
This explains what [ENTITY NAME TBD] ("Loudroll") collects when you use the hosted website and relay. We do not sell your personal information, and we do not run ads or tracking pixels.
What we collect
- Email address. For host sign-in, receipts, service and billing notices, and support. Hosts who create an account or subscribe.
- Display name and chosen character. To show you at the table. Everyone who joins; players need no account.
- Campaign data. The world state, story log, player actions and messages, table settings, and resident data in Tuckaway. Used to run the game, save campaigns and make recaps, while a table is active and during retention.
- Payment details. Handled by Stripe. We receive a customer ID, plan, status and the last four card digits, not your full card number.
- Technical data. IP address, browser type, request logs and error reports, collected automatically for security, rate limits, abuse prevention and fixing bugs.
- Anonymous usage counters. For example, a session started or a plan chosen, tied to an anonymous ID and not your name, to learn whether the product works.
Invite secrets are kept in the part of the link after the #, which browsers do not send to servers, and are not logged.
What happens to what you type
Player actions and messages are sent through the relay to the host's AI assistant, which runs on the host's own account with their AI provider (for example Anthropic). That provider processes the text under the host's agreement with it, and we do not control that. Do not put sensitive personal information in game text. We do not receive or store audio from voice play; voice is handled by each person's own assistant or browser.
How we use it
To run and secure the service, bill you, answer support, prevent abuse, meet legal duties, and improve the product using anonymous counts. We do not use your campaign content to train AI models. [CONFIRM: true for us and for each subprocessor.]
Sharing and subprocessors
We do not sell or "share" personal information for advertising. We use these service providers, who process data for us:
- Cloudflare: hosting, network, relay and storage.
- Stripe: payments and billing.
- Resend: sending email.
- Sentry: error monitoring.
[ROBERT/LAWYER: confirm the final list before launch, including any analytics tool.] The host and other players at your table can see your display name and what you do at the table. We may disclose information if required by law, to protect safety or rights, or in a business transfer.
Retention
- Free campaigns: kept 30 days after the last session, then read-only for 90 days, then deleted. [Confirm against the pricing doc.]
- Table Pass campaigns: kept while the plan is active. After a plan ends, frozen read-only for 90 days and then deleted unless you resubscribe or export.
- Idle tables: active relay state closes after 2 hours idle.
- Logs: [PERIOD TBD, e.g. 30 days].
- Billing records: kept as long as tax and accounting law requires. [LAWYER: confirm period.]
- Backups: removed on a rolling basis [PERIOD TBD].
Your choices and deletion
You can ask us to access, correct, export or delete your data by emailing [EMAIL TBD]. Hosts can delete their campaigns in the app [CONFIRM when built]. We will respond within [45] days. Washington and other state laws may give you additional rights, and we will honor them. [LAWYER: confirm which statutes apply at our size, including the Washington My Health My Data Act, and whether a state-specific section is needed.] We will not discriminate against you for exercising your rights.
Children
Loudroll is for people 18 and older. We do not knowingly collect personal information from anyone under 18. If you believe a child has used Loudroll, email [EMAIL TBD] and we will delete the data.
Security
We use reasonable measures such as encryption in transit and access limits. No system is perfectly secure.
International users
Loudroll is run from the United States and data is processed there. [LAWYER: GDPR and UK rules need lawful bases, transfer terms and possibly a representative if we market to the EU or UK; decide whether to launch there.]
Changes and contact
We will post changes here and update the date. [ENTITY NAME TBD], [ADDRESS TBD], [EMAIL TBD].