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:

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

Who else sees it

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.