Privacy Policy
Short version: everything PriorStates makes is local-first. Your memory, your documents and your apps run on your own device or your own computer, with the AI you already have there. Nothing is sent to us unless you use a hosted feature (such as the free starter AI in Studio on your phone, or on a computer with no AI of its own), and then only what that feature needs. No telemetry, no analytics, no accounts except the optional Memory server.
Last updated: 21 November 2026 · one policy for every PriorStates product; PriorStates Studio on your phone (formerly Palmtop) also has its own, store-facing policy.
PriorStates Memory (open source)
Memory runs entirely on your device. Your memory, journal and project
data are stored locally (under ~/.priorstates and your per-project
.priorstates/) and never sent to us. The software contains no telemetry, no
analytics and no usage tracking, and needs no account or API key.
The only outbound requests it makes are the ones you ask for:
- installing the package from PyPI or GitHub;
- a one-time download of the local embedding model from Hugging Face (skippable with
--lite); - connecting to an AI agent on your own machine over the Model Context Protocol (MCP).
If you point Memory at a third-party model or service yourself, that provider's own privacy terms apply to those requests.
The Memory server (optional, hosted)
Memory is open core. If you choose to create a free account on the Memory server at priorstates.com/w to share packs, keep them across devices or join a group, we store the minimum needed: your account email, a hashed password, and the packs you explicitly publish. That data is used only to provide the features you opted into, is never sold, and is deleted on request. Nothing reaches the server unless you send it.
PriorStates Studio (on your computer)
Studio is a free program you run on your own computer. It keeps its
settings, its pairing identity and your apps there (~/.config/palmtop and
~/.local/share/palmtop). Builds and answers come from the coding agent you
already have on that computer — Claude Code, Codex, the Gemini CLI or Antigravity — under
that provider's terms and your own subscription; Studio never sees your login. Only when no
coding agent is set up on that computer, builds (with the pictures and files you attach to them) and
an app's question (reading a receipt or a price, filling in a form) use the free starter AI, as on a
phone without a key: each request goes to our relay, which passes
it to an AI service provider we choose, under that provider's terms. The relay does not store or log
the content of these requests or answers; it counts requests per IP address for the day, to apply
the daily limit. Setting "no_starter_ai": true in Studio's settings file keeps it off.
Discuss, the panel beside Build, works the same way: your questions, any pictures or files you
attach, and the app as it is now (its code, its saved data, its log and its screen) go to that coding
agent or, if none is set up, by that same starter AI path. Saved data can include other people's
answers. Documents the AI writes there stay on that computer. Notes you keep for Studio, a space
or an app go with Build and Discuss requests too; anything in them that looks like a password, key or
token is replaced before they are sent, and the notes themselves stay on that computer. When the AI
arranges a space, it gets your apps' names and descriptions and how they are arranged.
If you add your own API key for an AI service in Studio's settings, it stays on that computer (not in backups) and your requests go from it straight to that service, under its terms. Reminders your apps set stay on that computer and go off while Studio runs. If you own a shared app's board and let it notify you, Studio reads that board about once a minute while it runs, with the same encrypted request your open app makes, decrypts it on that computer and keeps only short summaries there. If you set up an app's backend on a server of yours, Studio installs it there over SSH with your keys; the app's data then lives on that server, and your phone reaches it through our relay, encrypted end to end.
Studio keeps a local log of what it did, on that computer only.
When a phone or a browser reaches Studio away from home it goes through our relay at priorstates.com/relay. Everything that passes through is encrypted end to end on your devices: the relay sees that a Studio with a random id is online and moves sealed messages it cannot read. It keeps no content. Pairing links carry the key; they are yours to share or not.
Studio reports nothing to us. There is no telemetry and no account.
Studio on your computer and its apps
The computer Gallery in the browser (priorstates.com/desk, formerly called Desk) is a launch page: it keeps the list of apps it last loaded in your browser's own storage, and nothing on our server.
Studio on your computer (its apps served only to the browser on that machine) runs the apps that need your folders, your Python and your coding agent. Each app keeps its data on that computer, in its own folder. What the apps reach:
- Apps you make are written by the AI on that computer (your own subscription, through its coding tool) into a folder of their own, which Studio never syncs anywhere. While it builds, the AI's tools reach only that folder. The app then runs with your files, Python and network, and sends nothing unless you asked for an app that does. The conversation that made it is kept in your browser.
- A space kept in a folder (often a git repository your team shares) holds its layout, notes and apps as files in the folder you choose. When you commit, push or pull, Studio runs the git on your computer with your own sign-in, and it sends them only to the repository you set up. Nothing goes to us. Studio never asks for or keeps a git password. A commit or a shared note that looks like it holds a password, key or token is refused. Your conversations with the AI and each app's saved data stay on your computer, out of the folder's git.
- 📱 Take with my phone: when an app or the builder in Studio on your computer asks your paired phone for a picture, the picture you take or choose on the phone goes to that computer through our relay, encrypted end to end with your pairing key. The relay can't read it and keeps nothing, and Studio does not save it to your phone's photo library. The computer can only ask: the camera opens only when you tap it on the phone, and you decide whether to send.
- 🖥️ From my phone: words, drawings, signatures and codes travel the same way when an app or an AI box in Studio on your computer asks your paired phone, or when you send them with 🖥️ For my computer: only to the app or AI box you choose, through our relay, encrypted end to end with your pairing key. The relay can't read them and keeps nothing. Words come from your phone's own speech recognition or keyboard, so no recording passes through us; codes are read by your phone's camera on the phone. Nothing is captured until you tap and nothing is sent until you send it, and Studio on your computer only fills the box: it never sends anything on by itself.
- 💻 My computer and 📲 Phone's apps: if you turn on phone access in Studio on your computer (Settings → Phone), your paired phone can show that computer's spaces, ask their AI and run their projects' commands; the phone asks for its own lock (your fingerprint or a PIN) every 30 minutes. If you allow it on your phone, Studio on your computer can list your phone's apps and copy one there to change it, and send it back; private apps never go. Both travel between your own devices through our relay, encrypted end to end with your pairing key; the relay can't read them and keeps nothing.
- 📺 TVs: a TV running Studio Screen (or its page in the TV's browser) keeps a private inbox on our relay. Pictures, web addresses, messages and board links you send it from Studio go there encrypted end to end with the TV's key (a picture as an encrypted file the TV fetches); the relay can't read them, and the TV deletes each message once read. A web page or video link you send opens on the TV from that site. A video file you send from Studio on your computer goes straight from that computer to the TV over your home network, not through us, and Studio keeps it there for 24 hours.
- 🌐 Studio's browser window: when you ask the AI in Studio on your computer to open a web page, Studio opens it in a browser window of its own on that computer (your Chrome or Edge, with a separate profile kept in Studio's folder), signed in only where you signed in there yourself. The text of the pages it reads, and a picture of the page when it asks for one, go to the AI you use in Studio, as your other requests do. Sign-ins and cookies stay in that window's profile on your computer; Studio never reads or types a password. Buttons that finish something (submit, publish, send, pay, delete) are left for you to press unless you turn that off.
- Resume Writer keeps your documents in your browser on its own origin (resume.priorstates.com); AI review runs through your Studio or your Google key. No account.
- Reader reads the folders you add — on that computer, or on another one of yours over ssh with your own keys. Nothing is copied anywhere.
- Add (Studio for Chrome's first tab) and the apps it opens (Saved Links, Receipt Keeper, Price Book, Order Form, and any app with a form) read the web page in front of you, or what you selected on it, only when you pick an app or press "From this page". What they read goes to the AI described above, never to us otherwise; nothing is saved until you press Save.
- Ask reads the web page in front of you only when you ask (see the extension below) and hands it to your coding agent on the same computer. On Gmail that can include the open conversation, so a reply can be drafted; "Put reply in page" types the draft and never sends it.
- Workspaces run your coding agent in folders you list in Studio's settings, on that computer or on another one of yours over ssh. Each run's transcript and files stay on that computer; nothing about them reaches us.
Studio's assistant only ever sees an app's declared style settings, the current style and your request — never an app's code and never your documents.
The Studio for Chrome browser extension
PriorStates Studio for Chrome (formerly Desk for Chrome) is a side panel for PriorStates Studio. The extension has no server of its own and sends nothing to us: no telemetry, no analytics, no account. When you ask it to, it reads the page in the tab in front of you (its text, headings, links and selection, or what you last copied, for editors such as Google Docs that expose no selection) and the tab's address and title, and passes them only to Studio on the same computer, at 127.0.0.1. The extension stores one setting in Chrome, the port Studio listens on. Reading pages on every site is off until you turn it on, and you can turn it off again on the extension's options page. What Studio does with a page follows the sections above: it stays on your machine unless you point Studio at a third-party service yourself.
PriorStates Studio on your phone, and PriorStates Studio Link
Studio on your phone keeps your mini-apps and their data on the phone; sharing, circles and replies travel through the relay sealed end to end; links that collect answers keep them encrypted with a key that is only in the link, and if you ask people to confirm their email the relay keeps only a hash of the address; with the free starter AI, build requests and questions from your apps (including photos you give them) go through the relay to an AI provider we choose, and the relay does not store or log them; it sends at most one anonymous usage count per day (with the names of our own Gallery apps opened the day before), which you can turn off, and feedback only when you choose to send it. Its full policy, written for the app stores, is at priorstates.com/palmtop/legal/privacy.html.
PriorStates Studio Link is the Studio add-on you put on a server to send alerts to the Alerts app on your own devices. Each alert is sealed on that machine to your devices' keys; the relay stores what it cannot read, for a limited time, and a machine can be revoked from the phone. The credential it keeps is its own, on that server.
Plans on your computer and servers. When the AI that builds your apps proposes to set something up on your computer, or on a server you shared in Studio under Settings → Machines, Studio on your computer shows every step and command and runs them only after you allow them there; a phone can propose but not allow. Servers are reached with your computer's own SSH and your keys; Studio never asks for or keeps a password, and the AI sees only the names of the machines you shared. The output goes back to that AI and into a log on your computer; none of it passes through our servers.
A copy in your Google Drive (optional, PriorStates Studio)
Studio can keep a copy of your apps’ data in your own Google Drive, so it is safe if you lose your phone and the same on your other devices. It is off until you turn it on in Settings → Your data → “Keep a copy in my Google Drive”.
What Studio can reach. When you turn it on, Studio asks Google for one permission: to use a hidden folder in your Google Drive that only Studio can see (Google calls it the app data folder). Studio cannot see, open or change any other file in your Drive.
What goes there. The data your apps keep, the apps you made yourself, and your settings. The keys of your inboxes and links go there too, locked with a recovery phrase that only you have. The copy goes straight from your device to your Google Drive and from there to your other devices. PriorStates never receives it, and never receives the access Google gives Studio: the sign-in stays on your devices.
How it is used. Only to keep that copy and bring it back to your devices. It is not used for advertising, not sold, not shared, and nobody at PriorStates reads it.
Turning it off. In the same place, turn it off; “Remove the copy” deletes the folder from your Drive. You can also remove Studio’s access in your Google Account at myaccount.google.com/permissions. Your Google Drive itself is covered by Google’s terms and privacy policy.
PriorStates Studio’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
This website
priorstates.com is a static site. We do not set tracking cookies or run third-party advertising or analytics. Our web server keeps standard access logs (IP address, timestamp, requested URL) for a short period to operate the site and protect it from abuse. Some installers are served from GitHub Releases and the app stores, which have their own policies.
Ask about Studio (the helper on our website). Some pages of priorstates.com have a box marked “Ask about Studio” that answers questions from our own pages. When you send a question, its text (with your last few questions and answers in that box, so it can follow the conversation) goes to our server, which passes it to an AI service provider we choose, under that provider’s terms, to write the answer. We do not store or log your questions or the answers, and we keep no chat history: the conversation stays in your browser tab and is gone when you close it. We keep only anonymous counts per day: how many questions were asked, in which language, whether our pages had the answer, which suggested link was followed, and how many people tapped 👍 or 👎. To limit use, our server counts questions per IP address for the hour and the day, in memory only, without writing the address down. Please don’t type personal details into the box. Answers are written by AI and can be wrong; the pages they link to are what counts.
The Studio apps directory for AI assistants
priorstates.com/mcp/apps is a public, read-only service that lets AI assistants look up Studio's free Gallery apps. It needs no account and keeps no data about you: no sessions, no cookies, no request contents. Its own log holds only the method, the tool name and the result status. Like the rest of this website, the web server keeps standard access logs for a short period. What the assistant you use does with the answer is covered by that assistant's own terms.
Your choices & contact
Because the software is local, you are in control: you can inspect, export or delete your data on your own device at any time — Memory's files, Studio's folders on your computer and its backup on your phone, Studio's export. For anything about the Memory server, the relay or this policy, write to service@priorstates.com.
We may update this policy as the products evolve; material changes will be reflected here with a new "last updated" date.