Privacy policy

Updated October 25, 2026

Wren & Quill is a worldbuilding studio, operated by Grant Reinhart. This page explains how the app handles your information.

Sign-in and account information

Clerk manages sign-in, email verification, password recovery and account security. The app receives your Clerk account identifier, name, email address, email-verification status, and profile image when available. It uses this information to create your account, authenticate you, show your account identity, and match collaborator invitations to your email address. The app does not request access to Gmail, Drive, Calendar, or contacts, and never receives your Google password.

Clerk stores authentication credentials and manages sessions, which may include your IP address and browser information. The app database stores account/profile information, a mapping to your Clerk identity, and session identifiers and expiry for collaborator presence. Legacy authentication records may remain during migration. Essential cookies keep you signed in and protect the login flow; request records also support rate limiting.

Account activity statistics

While you are signed in, the app records your first recorded activity, most recent activity, and which UTC dates you used it. Visits and interactions on a visible, focused page update activity at approximately five-minute intervals; an idle or background tab does not continually report activity. Authorized staff can see account creation and activity timestamps and daily, weekly, and monthly active-member and new-account totals. These statistics help us understand service usage and improve the app. Staff accounts are excluded from member totals.

This collection does not record your project content, page URLs, workspace choices, clicks, keystrokes, IP address, or device information. It uses your existing authenticated session without additional analytics cookies or browser identifiers. Daily activity records are retained for the most recent 30 UTC calendar days and removed by scheduled maintenance. First and latest activity timestamps remain while your account exists; account deletion removes both those timestamps and daily activity records.

Where applicable, we rely on our legitimate interests in understanding and improving service usage, balanced against your privacy rights. To ask about this processing or object to it, contact grant.p.reinhart@gmail.com.

Your worlds and sharing

Saved worlds include Dictionary languages and vocabulary, Atlas maps and planets, Encyclopedia articles, Ecology relationships, Timeline events, uploaded images, collaborator email addresses, and available version history. Encyclopedia, Ecology and Timeline share a document. Projects are private to their owner and invited editors. An owner can publish read-only snapshots at public links; anyone with a link can read and copy the published content. Articles marked secret are excluded from reference publications. Later draft changes do not change a published snapshot. Unpublishing removes the app's public access to that version but cannot remove copies other people have already made.

Guest work is saved in your browser's local storage. It stays in that browser until you export it, import it elsewhere, or save it to an account. Clearing browser storage removes those local copies.

Discord dictionary

If you connect a Discord server, the app stores its server ID, the chosen world and language IDs, and connection update metadata. Command interaction IDs are retained to prevent duplicate processing and pruned after one day when further commands are received. The bot uses only published dictionaries and does not read chat messages or store Discord usernames. Requested dictionary results are sent to Discord and appear in the channel where requested. Unpublishing prevents new lookups but does not remove messages already posted to Discord. A server manager can disconnect the dictionary with /dictionary-disconnect.

Service providers and access

Vercel hosts the app and processes web requests. Turso stores account and project data. Cloudflare R2 stores uploaded images. Clerk handles authentication and account emails; Google handles Google sign-in when enabled through Clerk. These providers process information needed to provide their services, potentially outside your country. The operator can access stored data for operating and supporting the app. Invited editors receive access to the projects you share, and published language content is publicly readable.

API connections and operational monitoring

Owners can issue project-scoped API keys. The service stores a key hash, display prefix, name, permission, expiry and usage timestamps; the full key is returned only when created. A connection can read or change the documents its key permits. Owners can revoke keys.

Operational monitoring records fixed event categories, workspace categories, response status codes, counts and timestamps for up to 30 days. These event records do not contain project text, document titles, account identifiers, email addresses, tokens, or request bodies. If an alert webhook is configured, it receives the same limited event summaries. Provider request logs have separate retention and may contain request metadata.

The app does not sell Google user data, use it for advertising, or use it to train AI models. Google user data is used only for the account and collaboration functions described here. Its use follows the Google API Services User Data Policy, including the Limited Use requirements.

Retention and your choices

Working projects and current published revisions are kept while you use the service. Free accounts keep their newest three unpublished revisions without expiry; older revisions start a 30-day countdown when they leave that group and are then permanently deleted. Staff can grant longer or unlimited history. The project owner's allowance applies to shared projects. Atlas also keeps bounded automatic checkpoints and copies before supported destructive changes. Encyclopedia, Ecology and Timeline do not currently provide that automatic history. You can overwrite or delete unpublished revisions, export projects, remove collaborators, and unpublish releases in the studio. You can revoke the app's Google access in your Google account settings; revoking access does not itself delete previously saved app data.

Use the support and account-data page to request deletion while recently signed in to a verified account. Requests are recorded for the operator; submission does not immediately delete content. For access, correction, or help, contact grant.p.reinhart@gmail.com. Deletion removes the account, its owned worlds and publications, project keys and owned image files. Contributions in other owners' worlds may remain without your account attribution. Signed deletion records help prevent a restored backup from reactivating deleted accounts. Hosting logs and encrypted recovery backups have separate retention; deletion records must be reconciled before restored data is returned to service.

Changes to these practices will be reflected on this page with an updated date.