Privacy policy

What we hold, why we hold it, and how you get it back or make it go away.

Last updated 13 October 2026

Controller

SCRIVT LIMITED, 33 Downfield Road, Cheshunt, Hertfordshire, EN8 8SP, United Kingdom. Privacy questions and rights requests: hello@palt.io.

What we hold

DataWhyKept
Account profile (name, email, avatar), and the GitHub or Google account you sign in withrunning your accountuntil deletion
Password, if you set one (stored hashed)signing you inuntil deletion
GitHub or Google sign-in tokens (encrypted at rest)signing you in; we never call those services on your behalfreplaced at each sign-in, removed on deletion
Sign-in sessions (IP address and browser)keeping you signed in and listing your active sessionsuntil 7 days after last use, or sign-out
API keys you create (stored hashed; we cannot read them back)authenticating your API callsuntil revoked or deletion
Projects: specs, guide pages, branding and imagesthey are the productuntil you delete them
Team invitations (the invitee's email and role)sending the invitationuntil accepted, revoked or expired (7 days)
Bridge credentials: the OAuth bridge client secret, the MCP bridge access token, and the OAuth tokens your readers grant when they connect an AI assistant (all encrypted at rest)calling your API on their behalfuntil disconnected, or the bridge or project is deleted
Docs analytics on your public docs (page, search text, referrer, browser type)showing you readershipuntil the project is deleted; no visitor identifiers or IP addresses
Access log of password-protected docs (which of your docs passwords opened them and when, wrong passwords, browser type and country; which teammate changed the passwords)showing you who reads protected docs90 days; no IP addresses
Monthly usage counters (AI generations, MCP tool calls)enforcing plan allowancesuntil deletion
Billing: plan, status and Polar customer referencerunning paid plans; card details stay with Polaruntil deletion
Operational logskeeping the service standingrotated at 10 MB; the last five files are kept
Backupsdisaster recovery7 days

What we do not do

We do not sell personal data, run third-party advertising or analytics trackers, or train models on your specs. When you ask for an AI action (drafting docs, improving a page, describing MCP tools, the MCP playground), the content it needs goes to a model provider only to produce that output, under API terms that do not use it for training. Try it requests your readers send pass through our server to reach your API; we do not store them.

Legal bases

Contract (running the service you signed up for), legitimate interest (security, abuse prevention, the readership counts above), and consent where we ask for it (marketing email, which currently does not exist).

Where it lives

Production runs on Oracle Cloud Infrastructure in London, United Kingdom, including the database, file storage and the mail server that sends our email. Images uploaded in the page editor are stored with UploadThing. Every company that can touch service data is listed on the Subprocessors page.

Your readers and teammates

For personal data inside your projects, such as the teammates you invite, the readers who connect through your bridges and the access log of password-protected docs, you are the controller and we are your processor. The Data processing addendum covers that.

Your rights

Access, rectification, erasure, portability, restriction and objection. Settings covers deleting your account directly, and hello@palt.io covers the rest. You may also complain to your supervisory authority; for the UK that is the ICO.

Privacy policy · palt.io