SpineVault

Privacy Policy

What personal information SpineVault collects, why, who handles it for us, how long we keep it, and what you can do about it.

Effective . Last revised . SpineVault is made by tomPhyzx.llc, doing business as SpineVault.

Who we are · What we collect · What we don't keep · AI apps · How we use it · Who handles it for us · Cookies · How long we keep it · Your rights · Security, children, contact

1. Who we are and what this covers

SpineVault is made by tomPhyzx.llc ("we", "us"), a company in the United States.

This policy covers spinevault.app and its pages, the SpineVault app at beta.spinevault.app, and SpineVault's connector for AI apps at mcp.spinevault.app, including when you use SpineVault through an AI app. It explains what personal information we collect, why, who handles it for us, how long we keep it, and what you can do about it.

SpineVault turns a project into a spine: a small set of plain-text files you keep and can give to any AI. That design shapes everything below. We keep no copy of your spines, and an account is little more than an email address.

2. What we collect

We collect only what it takes to run your account and keep the service safe.

WhatWhere it comes fromWhy
Your account: your email address, when you made the account, when you last signed in, and our internal id for itYou, when you sign upTo sign you in and run your account
Sign-in details: your password if you set one, the codes we email you, and your sign-in sessionsYou, through our sign-in provider, WorkOS. WorkOS stores your password; we never see itTo sign you in securely
Security signals at sign-in: your IP address, approximate location (city and country), browser and device type, and a score for whether the request looks automatedYour browser, checked by WorkOS's bot and fraud protection and a human-verification check on the sign-in pageTo stop automated sign-ups, password guessing and abuse
Spines and files you bring: the zip, notes or AI work you upload, and spines we build or seal for youYou, or your AI app through our connectorTo check, build or seal your spine. Held for two hours at most (section 3)
Connector session records: the id and times of each session an AI app opens for you. No contentOur connectorSo your AI can find its session again while it lasts
App logs: for each request, the time, the page or kind of action, the result, the size and how long it took; for the connector, our internal ids for your account, the session and the operationOur serversTo run the service, find faults and stop abuse. They record no IP addresses, no file names and no file contents, and never your email address
System logs: the connecting address of traffic to the servers themselves, such as certificate checks and attempts to log in to the server. Not your use of SpineVaultOur serversTo keep the servers secure
Messages you send usYou, by emailTo answer you
Email addresses left with us at eventsYou, on a sign-up sheetTo follow up about SpineVault, with an unsubscribe link in every email

The download page for our demo spine counts downloads from a log that records no addresses.

3. What we don't keep, and don't do

We keep no copy of your spines. Our software reads what you bring only to check, build or seal it, and then it's gone:

We don't sell your information, or share it for money or anything else of value. We show no ads, run no analytics or tracking scripts, and don't use your spines or your account to train AI.

Your AI is not us. When you give a spine to an AI, by attaching it or through our connector, the company behind that AI handles it under its own privacy policy, not this one.

Please keep passwords, keys and regulated data (such as health, financial or legal records about other people) out of your spines. Before adding a file, have your AI scan it for that kind of detail, then anonymize what it finds or leave the file out.

4. When you use SpineVault through an AI app

SpineVault has a connector that AI apps such as Claude, ChatGPT and Gemini can use for you. Here is what happens when you connect one.

5. How we use it, and on what legal basis

We use your information only for the purposes below. The last column names the legal basis that European and UK data protection law asks us to state.

PurposeWhat it usesLegal basis
Run your account and the service: sign-in, building, sealing, the connector, and the emails these need (such as sign-in codes)Your account, sign-in details, spines in transit, connector session records, app logsNeeded to provide the service you asked for (contract)
Keep the service secure and stop abuseSecurity signals, app logs, system logsOur legitimate interest in a safe, working service
Answer your messagesYour messages, your email addressOur legitimate interest in replying to you
Follow up after an event where you left your addressYour email addressYour consent, which you can withdraw any time with the unsubscribe link
Meet legal obligationsWhatever the law requiresLegal obligation

Our bot protection may ask you to confirm a sign-in by email, or block one it judges automated. If it blocks you by mistake, write to us (section 10).

6. Who handles it for us

These companies process personal information for us, under their data processing terms:

CompanyWhat it does for usWhat it handles
WorkOSSign-up, sign-in, the codes we email you, and bot and fraud protection at sign-inYour email address, password, sign-in sessions and security signals, kept under WorkOS's privacy policy
DigitalOceanHosts our servers, our database and its nightly backups, in New YorkEverything we keep, and spines while they pass through
Google WorkspaceOur emailMessages you send us, and our replies

We share information with anyone else only when the law requires it, to protect our rights or someone's safety, or as part of a sale or merger of our business, in which case this policy would continue to apply to it.

7. Cookies

We use cookies only to sign you in. No analytics, advertising or tracking cookies.

WhereCookieWhat it's forHow long
beta.spinevault.appwos-session: your sign-in, encryptedKeeps you signed inRenewed while you use the app, for up to 7 days at a time. Your sign-in ends when you sign out, after two days without use, or 30 days after you signed in, whichever comes first
beta.spinevault.appwos-state: one sign-in attemptLinks the sign-in page back to your request, to stop forged sign-ins10 minutes at most; cleared when you finish signing in
WorkOS's sign-in pageWorkOS's own cookies and device checksSign-in, and telling people from automated scriptsSet by WorkOS under its own policy

The pages at spinevault.app set no cookies. The app also saves two settings in your browser (your text size, and whether to skip an explainer); neither identifies you. Because these cookies are needed to sign you in, the app doesn't ask for consent to them; blocking them in your browser stops sign-in from working.

8. How long we keep it

WhatHow long
A spine we build or seal for youTwo hours, then deleted
A spine your AI opens through the connectorTwo hours from the start of that session, then removed
Your account: email address and datesUntil you delete your account
Connector session records (ids and times)Until you delete your account
After you delete your accountYour address and sign-in are removed at once, with any download still waiting. Our backups keep your address for up to six weeks; then it is gone from there too
A record that an account was deletedKept, so a deleted account can't come back from a backup. It holds our internal ids and the date, not your address
Sign-in sessionsUntil you sign out, after two days without use, or 30 days after you signed in, whichever comes first
Security signals at sign-inKept by WorkOS under its own privacy policy
App logs and system logsNo more than 30 days
Messages you send usAs long as needed to answer you and keep a record of the exchange
Email addresses left at eventsUntil you unsubscribe or ask us to delete it

9. Your rights

These rights are for everyone who uses SpineVault, wherever you live.

You can do four things yourself, on your account page (sign in, then click your address at the top right):

You can also ask us to:

Write to us from the address on your account (section 10). We answer within one month, and we will never treat you differently for asking. If we turn a request down, we tell you why, and you can ask us to reconsider. If you are in Europe or the UK, you can also complain to your data protection authority.

10. Security, transfers, children, changes and contact

Security. Every connection to SpineVault is encrypted (HTTPS). We limit who can reach our servers, and we keep spines only for the two hours described above. Your account record, our database and its nightly backups, and the files a session holds are stored on an encrypted volume. Our server logs, which hold our internal ids and the connecting addresses described in section 2 and never your address or your files, are kept on the server's own disk. No system is perfectly secure, so we can't promise that nothing will ever go wrong.

Do Not Track and Global Privacy Control. We don't track you across sites, and we don't sell or share your information, so there is nothing for these browser signals to switch off. We treat every visitor the same way.

International transfers. We are based in the United States, and our servers are in New York. Our providers may process information in other countries. If you are in Europe or the UK, your information is transferred to the United States under safeguards such as the standard contractual clauses in our providers' terms.

Children. SpineVault is for adults. You must be 18 or older to use it. We don't knowingly collect information from anyone under 18; if you think someone under 18 has made an account, tell us and we will delete it.

Changes. When we change this policy, we update the date at the top. For a significant change, we email account holders before it takes effect.

Contact. Questions and requests about your information: privacy@spinevault.app. Anything else: support@spinevault.app.