Privacy Policy
Worlderous is a writing workspace for manuscripts, story planning, Google Docs sync, Local Vault files, and optional AI assistance. This policy explains what the app accesses, what it stores, and the privacy boundaries built into the product.
Plain-language summary
Worlderous does not store connected manuscript text, prompts, AI responses, or Google document text in an application database. Google Docs content is used only while loading, editing, comparing, or saving a document you choose. AI output stays temporary until you accept it. Local Vault writes only to a folder you explicitly choose on your device.
Information Worlderous handles
Account data can include your name, email address, profile image, and Google account identifier when you sign in with Google.
Project data can include project names, chapter metadata, story memory records, Local Vault connection metadata, Google document IDs, tab IDs, revision IDs, spreadsheet IDs, and storage preferences.
Manuscript content may enter browser memory while you edit, and server memory only while a specific load, save, review, import, or AI request is being processed.
Support reports include only what you type into the support form plus any safe diagnostics you explicitly choose to include, such as route, app version, browser, screen size, and theme.
Google user data
Worlderous uses Google sign-in for authentication and requests the narrow Google Drive file permission for files Worlderous creates or files you explicitly select. It does not request Gmail access and does not request broad Drive access.
Google Docs content is used to display, edit, compare, and save your selected manuscript document. Google revision IDs are used to protect saves from silently overwriting remote changes.
Routine remote checks use metadata such as document ID and revision ID. They do not fetch or store full manuscript text unless you explicitly load, compare, or save the document.
Worlderous does not sell Google user data and does not use Google user data for advertising. Access is used only to provide the user-facing features you choose.
AI requests
AI features are optional. When you run an AI action, Worlderous sends the selected request context to the chosen provider, which may include selected manuscript text, nearby scene context, style rules, review targets, or selected project-memory context.
Worlderous does not persist prompts, manuscript context, generated prose, provider request bodies, provider response bodies, or chat history by default. AI suggestions and review findings are temporary until you explicitly accept, save, or export them.
Bring-your-own-key credentials are encrypted server-side and stored only in provider-specific HttpOnly session cookies. Browser JavaScript cannot read the decrypted key. Managed provider keys stay on the server and are never exposed to browser code.
Local Vault and browser storage
Local Vault writes project files only to a folder you choose through your browser. Worlderous does not request folder access without a user gesture, and it does not claim continuous local file watching.
The browser may store preferences, theme settings, Local Demo content, Google connection metadata, revision metadata, and recovery state needed to protect active work. Connected manuscript content is not stored in browser local storage, IndexedDB, or an application database.
Payments and credits
If billing features are enabled, payment processing is handled by Stripe. Worlderous stores billing metadata needed to manage credits, subscriptions, invoices, refunds, currency preferences, and payment status. Worlderous does not store full payment card numbers.
Logging and diagnostics
Logs may include safe metadata such as request ID, route, provider, model, duration, token counts, normalized error code, and HTTP status category. Logs must not include API keys, credentials, prompts, manuscript excerpts, generated output, Google document text, chapter names, character names, or raw provider responses.
Sharing and third-party services
Worlderous uses third-party services only as needed to provide the product: Google for sign-in, Google Docs/Drive/Picker integration, optional Google/Vertex AI services, optional OpenAI API access, optional Stripe payments, and infrastructure providers used to host the application.
Third-party providers process data according to their own terms and privacy policies. Worlderous does not claim that AI providers have zero retention unless the relevant provider and configuration explicitly support that.
Your choices
You can choose not to connect Google storage, not to use AI features, not to use Local Vault, and not to include diagnostics in support reports. You can disconnect Google Docs, change or disconnect Local Vault, forget bring-your-own-key credentials, and export your project data from available export tools.
Contact
For privacy questions, contact the creator through the in-app Contact the Creator form or the support channel that provided your Worlderous access.