Your account is not the story.
This policy explains what information may be used when you read, write, vote, or contact MillionTale.
Information MillionTale handles
You can read the story without an account once it begins. Participation requires Google sign-in. Google shares your name, email address, sign-in identifier and, when available, profile image so MillionTale can recognise and operate your account.
Participation records may include your Human Number, writer turns, submitted sentences, votes, queue activity, notification preferences, reports, and the rounds connected to those actions. They also include the times needed to operate and preserve those records.
Contact messages include a category, message and optional name. Signed-in messages may be linked privately to an account. Reports include the reason and the item reported. The Contact form does not collect a reply email or provide a reply channel.
The service and its security providers may process browser, device and network information needed to deliver the service, protect forms, prevent abuse and investigate failures.
What is public and what stays private
Your Human Number is a public pseudonymous identity. Public pages may also show an applicable Writer Number, Founding Human recognition, participation totals, official contributions, and the calendar date participation began. These public numbers are not your Google identity.
Winning sentences and completed round results form part of the public story record. Approved candidate sentences that entered voting may remain in the round archive. Writers stay anonymous while voting is active, and losing writers remain anonymous afterward. After completion, only the winning Writer Number may be publicly associated with its Human Number.
Your Google name, email address, profile image, sign-in identifier, notification tokens, individual voting identity, reports, contact messages and private account records are not presented as your public story identity.
How information is used
MillionTale uses account information to authenticate you, operate your account, assign and preserve your Human identity, and apply writing and voting rules.
Participation records are used to select eligible writers, accept and moderate sentences, prevent duplicate votes, determine human-voted outcomes, maintain round history, and keep the official collaborative story reliable.
Information is also used to provide optional notifications, handle reports and contact messages, process account deletion, prevent abuse, protect the service, and investigate operational or safety problems.
The public story record
MillionTale preserves official sentences, completed outcomes, recorded vote totals, public Human and Writer Numbers, and approved candidates that remain in the round archive. This history allows readers to understand how the story was made without exposing private Google account details or the identities of losing writers.
Public story history is designed to persist as part of the collaborative record. Rejected or unpublished writing is not treated as permanent public literary history.
Service providers and optional services
MillionTale uses service providers for authentication and for operating, storing and protecting account, participation and story information. Google provides sign-in. Google services, including Firebase and Google Cloud, support operation of the service. Information needed for these functions may be processed by those providers.
Firebase Cloud Messaging processes private device subscription tokens to deliver optional browser notifications.
Cloudflare Turnstile processes browser and network information needed to check forms for automated abuse.
OpenAI processes submitted sentence text when optional automated safety moderation is enabled. This service is used only for safety review; it never writes, rewrites, ranks, selects or chooses story content.
Notifications and browser storage
Browser notifications are optional. They require your explicit choice and browser permission. If enabled, a device subscription token is stored privately with your account so MillionTale can send selected story updates; delivery is not guaranteed.
You can turn notifications off using the notification control or your browser settings. Subscription tokens are removed when you unregister them, during account deletion, or when the delivery service reports them as invalid.
Cookies help keep you signed in. Your browser also stores your Follow preference, notification state and cached pages for offline use. Browser permission and locally cached information may remain until you clear them in your browser.
Retention and security
Private and operational information is kept only as needed to operate accounts and participation, maintain security and reliability, review moderation and abuse concerns, handle requests, or meet applicable legal obligations. Exact retention periods have not yet been approved.
Pseudonymous public story history is retained separately as a lasting record of the collaborative project. Rejected or unpublished material, reports, contact messages and safety records are not part of that permanent literary record, although they may be retained for the operational purposes described above. Minimal security records may remain to prevent deleted credentials from restoring an old account.
MillionTale uses safeguards intended to protect private information and restrict public pages to appropriate story records. No online service can guarantee absolute security. Do not put private or confidential information in story submissions or messages unless it is needed for your request.
Your choices and privacy requests
You can choose whether to enable notifications and can request account deletion from Account. You may also ask about access to or correction of private account information, or raise a privacy concern, through Contact by choosing Privacy.
The current Contact form records a request but does not collect a reply address or provide a reply channel. A complete verified process for requests that require an identity check or response has not yet been established. There is no self-service account export.
Private profile information may be corrected where appropriate. Human and Writer Numbers, official sentences, completed vote outcomes and round history are controlled historical records rather than editable profile fields. A genuine technical error in those records requires controlled review.
Deleting your account
Self-service deletion is available from Account. After a valid request is accepted, new account activity and notifications are frozen. Your name, email address, profile image and connection to your Google sign-in are removed or separated from the public story record.
If you are currently selected as a writer in an active round, that round is allowed to finish naturally before final separation. The deletion process does not alter the active round, completed vote totals or official outcomes.
Deletion does not erase the shared story. Human and Writer Numbers, Founding Human facts, winning sentences, completed results, and approved candidates that remain in the archive may continue as pseudonymous public history. Public numbers are never reassigned, and losing writers remain anonymous.
Rejected or unpublished writing is not treated as permanent public literary history. After deletion completes, signing in again with the same Google account creates a new MillionTale identity with no automatic recovery of the previous number or history.
Age requirement
You must be 16 or older to participate in MillionTale. Reading the public story does not require an account.
Changes to this policy
This policy may be updated as MillionTale and its data practices change. The current version will be published on this page.
To delete your account, visit Account. Read how account deletion works, including what may remain in the public record. To record a privacy question or request, use Contact and choose Privacy. The current form does not provide a reply channel.