Get started
Privacy

Only what you typed, and who you signed in as.

Vitna reads pricing pages, not people. The personal data this site holds is what a visitor types into one of its two forms, and, for anybody who signs in, the GitHub profile or the email address they sign in with. This page says what happens to each.

01What is collected

Two forms, and a sign-in.

The design partner form, on the homepage and at the foot of the Switchyard page, stores a work email, the description written beside it, and the path of the page it was submitted from. The removal form at the bottom of this page stores an address and an optional note. Reading the boards, the log, the docs or the API asks for neither, and this site keeps no record of who read what.

Signing in is the one other path, and nobody needs it to read anything here. It uses GitHub, or an email address and a password. With GitHub, the site asks GitHub for your profile and your email addresses and nothing more, and keeps your GitHub account number, login, display name, a verified email (the primary one where there is one) and avatar address, with when you first and last signed in. The access token GitHub issues is used for those two reads of your profile and then discarded. An email address and a password are checked by Convexity, which holds that account: the address and the password go to Convexity's sign-in service each time you sign in, and so does an authenticator's code if you have turned one on. This site keeps the address, the username and name Convexity holds, Convexity's number for the account, and a scrypt hash of the password, so that you can still sign in while Convexity is not answering; an account with an authenticator keeps no hash here. Each sign-in also writes one line to the server's own log naming the login, which is how the operator sees that sign-ins are working. A name you set in the console's settings is kept beside the one your sign-in reported and shown in its place. Inside the console, what an owner enters about an org (its name, its workloads, its decisions, a connection to OpenRouter) is kept against that org.

The Vitna app at app.vitna.ai can be signed in with an account if the person using it asks. The app is then told the account's login, name and email address, and this site keeps when that sign-in began, when the app last asked who it is signed in as, and when it ends, with the sha256 of the token the app holds and never the token. Nothing the app keeps comes here: not its OpenRouter key, its conversations or its ledger.

When the app's Research is set to search with Vitna Search, each search its model writes comes here with the org's Vitna key and goes straight on to the Search service. This site keeps neither the search nor the key: it records the search as the org's activity, by its request id, its status and how long it took, as it records a search from the console, and never the words searched or a result.

This site adds no analytics script, no tag manager, no session recording and no advertising pixel. It sets no cookie for a visitor who never starts a sign-in. Starting one sets vitna_signin, which ties the sign-in to the browser that started it, is sent only to the sign-in routes, and expires after ten minutes whether or not you finish; finishing one sets vitna_session, which keeps you signed in for thirty days and no longer. Neither is used for anything else. Opening the Vitna app from the console sets vitna_app_open, which lets that one sign-in of the app skip its approval page, is sent only to that page, and expires after two minutes. Inside the console, the theme switch sets vitna_console_theme to light or dark, sends it only to the console's own pages, and keeps the choice for a year. The content policy the server sends refuses scripts and network connections from any other origin, so a tracker could not phone home from these pages even if one were added by accident.

The collector that fills the market boards fetches pages published by providers, identifying itself honestly and obeying robots.txt. It reads product pricing, never anything about a person, and the archive it keeps is copies of those public pages.

02Where it is held

On one server, and what the forms took in a table this website cannot read.

Both forms write to a Postgres database on Vitna's own server. Neither goes to a third-party CRM, mailing list or form service, so no other company receives what you typed into them.

The process that serves these pages writes the forms with a role holding INSERT and nothing else, not even SELECT. It can add a row and it cannot read one back. That is not a policy about who looks; it is a privilege the database does not grant, so a bug in this website, or somebody who found one, could not be made to hand over the list.

Signed-in accounts do not have that protection, and this page says so rather than letting the sentence above stretch to cover them. A session has to be looked up to be a session, so the role that handles sign-in can read every account row, emails and password hashes included, and every session. It can also see which orgs each account belongs to, and each org's connections and push keys by label, never the keys themselves. A bug in the part of this website that handles sign-in could therefore expose the list of accounts, which the forms' list cannot be. What the session table holds is the sha256 of each cookie, never the cookie itself, so a copy of the table opens no session.

Other companies take part. Cloudflare carries every request to this site, including what is typed into a form, and so sees the address each visit comes from; the nightly backups are stored with Cloudflare too. GitHub takes part when you sign in with GitHub, and Convexity when you sign in with an email address and a password, since Convexity holds that account and checks the password. Stripe takes part if an owner buys a plan: the payment page is Stripe's own, the card goes to Stripe and never reaches this site, and what this site sends Stripe is the org's id, the plan, and, until the org has a subscription on record, the email address the owner signed in with. An owner who connects OpenRouter leaves a key OpenRouter minted, which is stored encrypted and can be revoked at OpenRouter without asking Vitna.

A nightly backup goes off the box to that object storage, encrypted before it leaves, precisely because it carries these addresses. The archive of providers' pages is copied unencrypted beside it, because it is other people's public pages and holds nothing personal.

03How long

Until you ask for it back.

An address given to arrange a scoping call is kept until the conversation it was for has ended or until somebody asks for it to be removed. An address left on the Switchyard page is kept until we have written to say Switchyard can be run, or until somebody asks for it to be removed. There is no automatic expiry, and saying otherwise would be describing a job that does not run.

A signed-in account has no automatic expiry either. It can be asked back with the same form, and what can be removed then is the profile: the login, both names, email and avatar. The account number stays, because decisions, purchases and connections made under it point at it, and the record of those is not edited. A session stops working thirty days after it began, or when you sign out, which deletes its row; a session left to expire is deleted the next time that account signs in. A connection of the Vitna app ends ninety days after it began, or when it is disconnected from the app or from the console, which deletes its row. Asking an account back ends its sessions and every connection of the Vitna app in the same step, rather than leaving them to run out.

Backups taken before a removal are not rewritten, and the lines the server's log wrote at sign-in are kept for as long as that log keeps lines.

The market record itself is append-only and never deleted, which is what makes a price checkable years later. It holds no personal data at all: it is kept in a separate schema from anything a visitor typed, deliberately, so that the record that must never be edited and the data a person can ask to remove are never the same rows.

Removal

Ask for it back.

This is a form rather than an address, and the reason is worth stating: publishing an inbox nobody has agreed to watch is a promise that quietly breaks. A request made here lands in the same database as the address it names, read by the same person who reads the requests to join.

Nothing here is automatic. Somebody removes the row by hand, which is the only way anything leaves that table.

The address you type here is stored so somebody can find and remove the one that matches it.