Privacy Policy

Every category of data we hold, and the specific reason it exists:

• Email address. Identifies your account, lets you sign in, and is how we send confirmation and password-reset emails and any notice our Terms require. It's also the address we'd use to reach you about a material change or a security incident.
• Password. Hashed by Supabase Auth before storage. LoreVault never receives, sees, or stores your password in plain text — not in our database, not in logs. Changing your password requires re-entering your current one, so a hijacked session alone can't lock you out of your own account.
• Your display name. Stored so the app can address you by name. Optional to keep accurate; you can change it in Settings.
• The text of your documents. When you upload a file we parse it server-side and store the extracted plain text, along with the filename and file type. This is what gets read and organized, and what Ask your vault searches. Documents written in the writing room are stored the same way.
• What was found in your writing. The characters, locations, events, lore rules, and items organized from your documents — each with its description, any alternate names, its relationships to other entries, and the source passage it came from, so every card can be traced back to your own words.
• Consistency findings. Details that LoreVault noticed don't agree across your documents, plus whether you resolved or dismissed each one, so the same finding isn't raised at you repeatedly.
• Usage counters. A per-day count of how many documents we've read for you. Used solely to enforce the daily reading limits described in the Terms and to prevent abuse of the reading service.
• Plan and billing state. Your plan tier, your Stripe customer and subscription identifiers, the subscription's status, and its current period end date. Used to know what your account has access to and to show your billing page accurately.
• Consent and setup timestamps. When you accepted the Terms and Privacy Policy at signup, and when you completed the first-run welcome. The first is the record that you agreed; the second stops us showing you the intro twice.
• Standard request information. Like any website, serving a page involves your IP address, browser user agent, and request time reaching our hosting provider. We don't build profiles from this or combine it with your vault content.

Stated explicitly, because the absences matter as much as the list above:

• Not your original files. We parse an upload for its text and store the text. The original PDF, Word, or text file itself is never written to storage — there is no file bucket in LoreVault.
• Not your card details. Payment happens on Stripe's own hosted checkout page. Your card number, expiry, and security code never touch our servers, and we cannot see them.
• No analytics or product telemetry. There is no Google Analytics, no Segment, no PostHog, Mixpanel, Amplitude, or equivalent anywhere in the app. We do not track which pages you visit or what you click.
• No advertising or cross-site trackers. No ad pixels, no retargeting tags, no third-party cookies, no fingerprinting.
• No location tracking, no contacts, no device scanning. LoreVault asks your browser for none of these.

LoreVault runs on a small number of specialized providers. Each receives only what its one job requires. This is the complete list.

If we ever add or replace a subprocessor, this list gets updated, and we'll email you if the change meaningfully affects how your content is handled.

This is the single most important thing to understand about how LoreVault handles your writing, so we're stating it as plainly as we can.

Organizing your world requires something to actually read your words. LoreVault does that through Anthropic's commercial API, which operates under contractual terms that exclude API inputs and outputs from model training. That is a meaningfully stronger protection than the default terms attached to free consumer chatbots, where conversations may be used for training — the distinction is exactly why the commercial API is what we use.

Specifically, your document text is sent to Anthropic when:

• A document is read after you upload it or save it from the writing room.
• You ask a question in Ask your vault — the question, plus the relevant parts of your vault needed to answer it.
• A consistency scan checks your world for details that don't agree.

Anthropic retains API logs for a limited period under its commercial data retention policy, for abuse monitoring and debugging rather than training. We deliberately link to Anthropic's published Commercial Terms and their privacy documentation rather than restating specific retention windows here — those are Anthropic's to set and can change, and a number copied into this page could quietly go stale and mislead you.

We do not use your writing to train any model, including any model of our own. We have no model of our own, and no plan to build one from your work. If that ever changed, it would require your explicit opt-in consent — not a quiet edit to this page.

No other LoreVault user can reach your vault.Row Level Security is enabled on every table holding your content — projects, documents, cards, consistency findings, usage counters, and profile — with policies tying each row to the account that owns it. This is enforced by the database itself, not merely checked in application code, so the database refuses to return your rows to anyone else's session even if a bug in the app asked it to. On top of that, API routes that touch your data require a valid signed token and verify you own the specific project or document being requested.

There is no sharing, no collaboration, no public profiles, and no team access in LoreVault. Nothing you write is visible to another user, because there is no mechanism by which it could be.

That access exists because someone has to be able to run migrations, fix corrupted data, diagnose a failed document read, and answer support requests. It is used only for:

• Keeping the service running — schema changes, backups, and repairing data problems.
• Debugging a specific reported fault, such as an extraction that failed or a card that came out wrong.
• Responding to a support request you initiated, where looking at the affected content is necessary to help.
• Complying with a valid legal obligation.

We do not browse, read, sample, or review your writing outside of those situations. We don't read your work for curiosity, for product research, or to build training sets. If resolving a support ticket requires looking at your content, we'll say so.

• We never sell your personal information or your writing — not to advertisers, not to data brokers, not to anyone. We do not sell or share personal information as the CCPA defines those terms.
• We never share your writing with anyone beyond the subprocessors listed above, each of which only receives what its single job requires.
• We never use your writing to train, fine-tune, or evaluate any machine-learning model.
• We never publish, post, or display your content to anyone but you.
• We never run ads, ad trackers, or third-party analytics in the app.
• We never email you marketing you didn't ask for. Account email is transactional — confirmation, password reset, and notices these documents require.

If you're in the EU or UK, the GDPR requires us to name a lawful basis for each purpose. LoreVault is the data controller for the data described here.

• Performance of a contract. Storing your account, storing and reading your documents, organizing them into cards, answering your questions, and running your subscription. Without this processing there is no service to provide.
• Legitimate interests. Keeping the service secure and available, enforcing daily reading limits, preventing abuse, and debugging faults — balanced against your interests, which is why access is limited to the situations described above.
• Consent. Your affirmative acceptance of the Terms and this policy at signup, recorded with a timestamp. Where we'd ever want to do something new with your content, we'd ask separately.
• Legal obligation. Retaining financial records relating to payments, and responding to valid legal process.

Retention differs by data type, so here it is per type:

• Account details and vault content. Kept as long as your account is active, because it is the thing you came here to keep. We don't expire or auto-delete your work for inactivity.
• A vault you delete yourself. Deleting a vault from Settings removes its documents, its cards, and its consistency findings from the database immediately. This is not reversible on our end and there is no trash to restore from — the confirmation step asks you to type the vault's name for exactly that reason.
• A document you delete. Removed immediately. Cards found only in that document are deleted with it; cards that also appear in other documents lose that document's citation and remain in your vault.
• Usage counters. Per-day reading counts are small and retained with the account; they hold no content, only numbers.
• Billing records. Stripe retains transaction records under its own policy and applicable financial-record law, which can require keeping them for years after a payment. This continues even if you delete your LoreVault account, because it's a legal obligation rather than our choice.
• Account emails. Delivery records at Resend are retained under its own policy.
• Anthropic API logs. Retained by Anthropic for a limited period under its commercial retention policy — see the AI section above, which links to their current terms.

If you delete your account.Account deletion is handled manually so nothing is destroyed by a mis-click: email us and we'll confirm it's really you asking, then remove your account, your vault content, and associated personal data from our active systems. We aim to complete this within 30 days of confirming the request, and we'll tell you when it's done. Ask us for an export first if you want your work — we'll provide one before deleting.

Backups. The database is backed up as a matter of ordinary operational safety. Deleted content can persist in those backups briefly after removal from the live database, until routine backup rotation overwrites them. We do not restore from a backup to resurrect deleted content for any purpose other than recovering from a genuine incident, or honouring a deletion request that turned out to be a mistake and that you asked us to reverse promptly.

Most of these you can exercise yourself in the app, right now, without asking us:

• Access. Everything in your vault is visible to you in the app at any time — open the card tabs, the Documents tab, and Settings. For a copy of account data that isn't shown in the interface, email us.
• Correction. Edit any card's name, description, or alternate names directly on the card — your correction becomes the record and won't be overwritten. Change your display name and password in Settings. Email us to correct your account email address.
• Export and portability. On Pro, export an entire vault as a single Markdown document from within the app. On any plan, including Free, email us and we'll provide an export of your data in a portable, machine-readable format at no charge.
• Deletion. Delete individual documents from the Documents tab, and whole vaults from Settings, yourself and immediately. For full account deletion, email us — see the retention section for what happens and how long it takes.
• Objection and restriction. You can ask us to stop or limit a particular use of your data. Because nearly all of our processing is what makes the service work, in practice this often means closing your account — we'll be straight with you about that trade-off rather than quietly doing nothing.
• Withdrawing consent. Where we rely on consent, you can withdraw it. That doesn't undo processing already carried out lawfully.

How to submit a request. Email hello@lorevault.techfrom the address on your account, and say what you want. Sending it from your account's own address is how we verify it's you; if you can't, we may ask another question to confirm before acting on a deletion or export, so that nobody can delete your vault by pretending to be you. You never need to give a reason.

How quickly we respond.We aim to acknowledge within a few days and to complete requests within 30 days. If your local law sets a specific deadline we meet that instead: one month under the GDPR (extendable for genuinely complex requests, where we'll tell you and explain why), and 45 days under the CCPA (extendable once, with notice). Exercising these rights is free, and we won't degrade your service or charge you differently for asking.

EU and UK residents.In addition to the above, you have the right to lodge a complaint with your national data protection authority, or the UK Information Commissioner's Office. We would genuinely rather you raised it with us first so we can fix it, but that right is yours regardless and you don't need our agreement to use it.

California residents.Under the CCPA/CPRA you have the right to know what personal information we collect, the purposes for collecting it, and the categories of third parties we disclose it to — all set out above; the right to request a copy; the right to correction; the right to deletion; and the right not to be discriminated against for exercising any of them. We do not sell or share your personal information, and we do not use or disclose sensitive personal information for purposes beyond providing the service, so there is no opt-out for you to submit — but you're welcome to ask us to confirm that in writing. You may use an authorised agent to submit a request on your behalf; we'll ask for proof of their authority.

LoreVault's database and hosting are located in the United States, and our subprocessors are US-based companies. If you use LoreVault from outside the US — including from the EU or UK — your data is transferred to and processed in the United States.

The US does not have an EU-wide adequacy decision covering all transfers, so for EU and UK users these transfers rely on the appropriate safeguards our providers make available, typically Standard Contractual Clauses in their data processing terms. By using LoreVault you understand your data is processed in the US. If that isn't acceptable for your work, LoreVault isn't currently the right tool for you, and we'd rather say so plainly here than bury it.

LoreVault uses no advertising cookies, no analytics cookies, and no third-party cookies of any kind. What it does use is strictly functional, and this is the complete list.

Cookies

• Session cookies (Supabase Auth). Hold your signed-in session so pages can be protected on the server before they render, and so you aren't asked to sign in on every navigation. Removing them signs you out.
• A short-lived signup verification cookie. Set while you're confirming your email, so that clicking the link in your email can complete sign-in securely on the device that started the signup. It's consumed as soon as confirmation completes.

Both are essential to signing in and staying signed in, which is why LoreVault shows no cookie consent banner — there are no non-essential cookies to ask you about.

Local storage (stays in your browser)

These never leave your device and are not sent to us as analytics. If you clear your browser data you lose only the conveniences described:

• lv_active_project_id — which vault you had open, so you return to the same one.
• lv_draft_… — an in-progress draft in the writing room, saved as you type so a closed tab or crash doesn't lose unsaved words.
• lv_last_visit_… — when you last opened a vault, so the app can show what's new since then.
• lv_ai_tone — your chosen phrasing style for how LoreVault talks to you, from Settings.

LoreVault is not intended for children under 13, and our Terms set 13 as the minimum age to hold an account. If you are under 18, you need a parent or guardian's permission to use the service.

We do not knowingly collect personal information from children under 13. If we learn that we have, we will delete the account and its contents. A parent or guardian who believes their child under 13 has created an account can email hello@lorevault.techand we'll remove it and confirm once it's done.

Specifically, what protects your account:

• Encryption in transit. All traffic between your browser and LoreVault runs over HTTPS.
• Row Level Security at the database level. Enabled on every table holding your content, with policies tying each row to its owner — enforced by the database, not just checked in app code.
• Hashed passwords. Handled by Supabase Auth. We never store or handle plaintext passwords, and changing a password requires re-entering the current one.
• Authenticated API routes. Every route that touches your data requires a valid signed token, and verifies you actually own the project or document you're asking about — not merely that you're logged in as somebody.
• No card data to steal. Payment details live entirely with Stripe. A breach of LoreVault could not expose a card number, because we never had one.
• Privileged writes stay server-side. Sensitive fields such as your plan tier can only be written by server code, so a user cannot grant themselves Pro from a browser console.
• No original files at rest. We store parsed text, not your uploaded documents, so there is no file store to compromise.

If a breach happens.If we discover a security incident affecting your personal information or your writing, we will notify affected users by email without undue delay, and within any deadline the law sets — 72 hours to the relevant supervisory authority under the GDPR where it applies. That notice will tell you what happened, what data was involved, what we've done about it, and what we recommend you do, in plain language. We would rather deliver an awkward, specific disclosure than a vague reassuring one.

If you find a security problem in LoreVault, please email us — we'll take it seriously, act on it, and we won't pursue anyone who reports a genuine issue in good faith without exploiting it or accessing other people's data.

If we change how we handle your data, we'll update this page and the "Last updated" date at the top.

For material changes — anything affecting what we collect, who receives it, how long we keep it, or your rights over it — we'll email you at your account address at least 14 days before the change takes effect. Adding a new subprocessor that handles your document content counts as material. Clarified wording and corrected typos take effect when posted.

We will never quietly start using your writing to train a model, or begin selling your data, on the strength of an edit to this page. Either would require asking you first.

For any privacy request — access, correction, export, deletion, objection, or just a question about something here — email hello@lorevault.tech. A real person reads every message.

LoreVault is operated from California, United States, and is the data controller for the data described in this policy.