Problems API
Privacy
What the API keeps about your account, your streams and your learners, what it never keeps, and who else sees it.
Your account
You sign in on pages run by Clerk, our sign-in provider. Clerk keeps your account: your email address, your name if you give one, how you sign in (for example a password, or Google), and the API keys you make. If you sign in with Google, Google tells Clerk your name and email address.
When a call arrives with a key, the API asks Clerk which account the key belongs to and acts as that account. The API does not store your keys.
What the API keeps
For each account, in a database hosted by Render:
- each stream you make: its name, its title and its definition (the skills you chose, or the paragraph written in your conversation), every earlier version of that definition, the small program a model wrote to make the questions of a definition written in conversation, with each program it tried before that one and what was wrong with it, the questions it served recently, so it can avoid repeating them, and up to 120 questions a model wrote, or wrote words for, for its pulls, with their answers, so a later pull can serve some of them again;
- each stream you share: its title, its definition and its program as they were when you shared it, kept under the ref you were given, and which ref each version was shared under;
- each pull: the key you sent, when it was made, the questions it served with their answers, the numbers drawn to make them and any words a model wrote for them (such as a first name or a colour), and the token your learners’ pages use to read it;
- each learner’s answer that a question’s own check asked the judge model about on its own: the question the check asked, the answer, and the judge’s ruling, so the judge is asked about the same answer once.
Every stream and pull belongs to one account, and no account can read another’s. The one exception is a stream you share: any account that holds its ref can copy it, and so read its title and its definition as they were when you shared it. A ref works for whoever has it, including anyone it is passed on to, and cannot yet be withdrawn.
What it never keeps
- Your conversation. The messages you send to
/chat/completionsgo to the model. The API keeps only the stream definition the model writes from them, and the program written for that definition. - Learners’ answers. A check marks the answers and returns the marks. Nothing else about the check is saved: only an answer a question’s own check asked the judge model about on its own is kept, with the judge’s ruling, as described above.
- Photos. A photo check sends the photo to the model, which reads the answers off it. The API keeps neither the photo nor its address.
- Who your learners are. A learner’s page sends only a pull’s token and the learner’s answers, so the API never learns a learner’s name or account.
Who else sees it
- Clerk runs sign-in and keeps your account and keys, as described above.
- Render hosts the API, its database and these pages.
- OpenRouter and OpenAI run the model. They see the messages of your conversation; a stream’s definition when the model writes its program, and that program’s first questions when the model solves them to check it; a stream’s definition and its recently served questions when the model writes a pull’s problems; a pull’s questions and the photo when the model reads a worksheet; and, when a stream’s program asks for words such as a first name or a colour, only the kinds of words wanted, with nothing of your stream or its questions. The API asks OpenRouter to send these only to OpenAI, and only where OpenRouter lists the provider as not collecting the data it is sent.
- OpenRouter and TypeSafe run the judge model. When a question’s own check cannot decide a learner’s answer in its code, they see that answer, any other answers of the same check they are asked about, and the yes-or-no question the check asks about each, with nothing else of your stream or your learner. The API asks OpenRouter to send these only where it lists the provider as not collecting the data it is sent.
Nobody else. The API and these pages run no analytics or advertising, and we do not sell your data or give it to anyone not named here. These pages set no cookies; Clerk’s sign-in pages use cookies to keep you signed in.
Seeing or deleting your data
Write to steven.noble@gmail.com to see or delete what the API keeps for your account. If you delete your account in Clerk, its keys stop working, but its streams and pulls stay until you ask us to delete them.