← LoreLynx

Privacy Policy

Effective September 24, 2026

Who handles your information

LoreLynx is operated by an individual sole proprietor based in Tennessee, United States, who is responsible for the personal information described here. Contact support@lorelynx.app about privacy, access, corrections, exports, deletion, or the identity of the operator. This notice covers the website, workspace, reading and sharing features, and support contacts.

Information we collect

Account information includes your email address, chosen display name, authentication records, and the versions and time of your agreement to our terms and eligibility confirmation. Google sign-in provides your Google email, name, and profile-picture link; we use the email and name and do not display that picture. We do not receive your Google password.

Workspace information includes projects, manuscripts, lore, outlines, images, maps, settings, versions, and other material you save. Sharing features also process invited email addresses, member roles, comments, activity, published work, pen names, reading progress, ratings, saves, and abuse reports. Support contacts can include your messages, attachments, email address, and any voicemail you leave.

Technical information can include IP addresses, request times, browser/operating-system details, authentication and security events, rate-limit records, and filtered error reports. Cloudflare Turnstile processes browser and device signals to distinguish people from automated abuse.

How and why we use information

We use account and workspace information to authenticate you, save and sync work, provide requested AI and sharing functions, and respond to support. We use limited technical and activity information to secure the service, investigate errors or abuse, enforce agreements, and comply with legal obligations.

We do not sell personal information or creative content, share it for cross-context behavioral advertising, or run advertisements. We do not use your writing to train AI models or license it for that purpose. We do not automatically enroll account holders in marketing emails.

Where applicable data-protection law requires a legal basis, we rely on performance of our agreement for requested account/workspace functions, legitimate interests in proportionate security, support and abuse prevention, legal obligations where required, and consent where a particular optional activity requires it. You may object to processing based on legitimate interests and withdraw consent where relied upon, without affecting earlier lawful processing.

Service providers and other disclosures

We use Vercel for hosting, Supabase for authentication/database/storage, Resend to deliver authentication emails through Supabase, Cloudflare Turnstile for abuse prevention, and GlitchTip for filtered error reporting. Support email is handled through Proton Mail; Google Voice processes voicemail left on our support line. These providers receive information needed for their services. Authorized operator access may be needed for support, security, moderation, or maintenance; cloud content is not end-to-end encrypted against the operator.

We disclose content to the people you choose through sharing or publishing and to a cloud AI provider when you use that connection. We may also disclose limited information when legally required or reasonably necessary to protect rights, investigate abuse, or address a security incident. If the service is transferred to another operator, we will provide required notice and maintain applicable privacy protections; this is not permission to sell your writing for advertising or AI training.

AI and API keys

You obtain your own provider account and key independently. A cloud AI request may contain your prompt, selected prose, relevant lore, outline, and other project context. It passes through our server to your chosen provider. LoreLynx does not persistently store the relay request body, though content you save in the workspace remains part of your project.

The provider handles requests under its own terms and your account settings; retention, human review, training, and regional practices differ. Check them before sending confidential material. LoreLynx cannot promise that every provider account excludes training.

With a model actually running on your computer, supported local AI requests go directly to that model. A remotely configured endpoint is not necessarily local. Local AI does not disable cloud project synchronization. API keys are stored encrypted in browser local storage, with the encryption key in IndexedDB. Your provider API key is transmitted for cloud requests; LoreLynx does not persistently store them on its servers.

Collaboration, public content, and links

Projects are private to your account unless you authorize access. Project owners can see invitees' and members' email addresses; ordinary collaborators see display names and shared project content. Editors can change the shared project, while readers have read-only access. Contributions to someone else's project may remain if you leave or delete your account.

Read-only share links expose prose and chapter structure to anyone holding the link. Once the book feed opens, released books and selected World entries are available to signed-in readers. Published cover and World image URLs can be publicly accessible. Revocation or unpublishing stops future access through the relevant feature but cannot recall saved copies, and existing cached or signed image URLs may remain usable until they expire.

Device storage and error reporting

Your browser stores authentication state, settings, project caches, and local backup snapshots in local storage or IndexedDB. These support sign-in and the workspace. You can clear them in browser settings; doing so may sign you out or remove unsynced work and local backups. Export anything you need first.

Vercel Web Analytics and Speed Insights measure page views and page performance without cookies; before a measurement leaves your browser, the page address is reduced to its route, with query strings, fragments, and share, invite, project, book, author, and request identifiers removed. Session recording and performance tracing are disabled. GlitchTip receives filtered error information such as error type, code location, environment, and sanitized request paths/status codes. We remove request bodies, authentication material, free-form error messages, and identifying path values before sending reports. These safeguards reduce unintended disclosure; contact us if you suspect sensitive information was included.

We do not track you across third-party sites for advertising. There is no sale or advertising sharing for a browser Do Not Track or Global Privacy Control signal to opt out of; these signals do not disable essential authentication, storage, or security processing.

Retention and deletion

We keep active account and project data while needed to provide your account. Deleted projects remain in Recently deleted until permanently removed. Scene version history keeps the newest 20 versions of each scene in the editor; the cloud copy of that history retains up to 50 per scene, and entries beyond that are pruned nightly once more than 30 days old.

You can request account deletion in Settings or by contacting support. Deletion first removes your uploaded images, then your account, which removes account-owned projects, share links, published books and World pages, and account data with it. If any step fails, your account is left unchanged and you can try again or contact support. Restricted production database backups follow a seven-day rotation; deletion from active systems does not instantly erase an earlier backup.

Security/error records are retained only while needed for investigation, protection, and troubleshooting. Support and rights-request records are retained while needed to handle the request, document its resolution, or address a related dispute. We may retain limited information for applicable legal, financial, or evidence-preservation obligations, and remove it when that need ends. We do not keep creative work for an unrelated commercial purpose after deletion.

Account deletion cannot erase exports, reader downloads, messages in recipients' mailboxes, or collaborators' independently retained copies. Browser snapshots may remain on another device until cleared. Contact support for questions about contributions to a project you do not own.

Payments

Paid plans are not on sale yet and no payment details are required for the free launch. If payments open, Stripe is the planned payment processor. We will update this notice before collecting billing information to describe the actual checkout, records, and retention. Never send full card details to support.

Your choices and rights

You can update account settings, export projects, revoke sharing, and request deletion. Email support@lorelynx.app to request access to, correction of, deletion of, or an export of personal information, or to raise a privacy concern. We may reasonably verify ownership before acting. Project export alone may not include every account, support, or security record.

Depending on applicable law, you may also have rights to restrict processing, object, obtain portable data, withdraw consent, or complain to your local data-protection authority. We will respond within the period required by applicable law and explain a permitted refusal or extension. We will not penalize you for exercising applicable privacy rights.

Children and international processing

LoreLynx is not intended for children under 13. Users aged 13–17 need parent or guardian permission. If you believe an under-13 child has supplied personal information, contact support so we can investigate and take appropriate deletion or other legally required action. Optional AI services have separate age restrictions.

LoreLynx operates from the United States. Our service providers may process information in the United States and other countries. Laws may differ from those where you live. Where applicable law requires safeguards for international transfers, those safeguards must apply; contact us for information about the providers and arrangements relevant to your data. Website availability is not a representation that every feature or provider is available in every country.

Changes to this notice

We will update the effective date when this notice changes. We will notify account holders of material changes through email or a prominent in-app notice before they take effect, unless urgent legal or security reasons require otherwise, and obtain consent where required. We do not retroactively authorize materially different uses merely by changing this page.

Contact: support@lorelynx.app. You can also use our contact page.

Provider privacy information