Privacy, accessibility and contact

Privacy

No account needed. Your work belongs to this browser, identified by a random cookie (slate_owner). Nobody else can open it unless you share a link.

If you create an account, Slate stores your email, an optional name, and a one-way (scrypt) hash of your password, never the password itself. Your sessions are stored only as hashes. Signing in links this browser to your account so your work follows you; signing out gives this browser a fresh, empty identity. Sign-ins, sharing and deletions are recorded in an audit log without any of your content.

What is stored: the problems and working you check, the lessons you make, your practice answers, and feedback you choose to give, on the server that runs this Slate. It is used to show you your work, your progress and suggestions, nothing else.

What is sent elsewhere: nothing when you check working. Trace runs on Slate's own code. Only if you ask for an animated lesson, or ask a model to read working Slate couldn't, is your text sent to the configured model provider to do that job.

Product analytics record that things happened (a check was made, a practice problem was solved, how long a diagnosis took), never what you wrote, and identify you only by a one-way hash. You can switch them off below.

Sharing is off until you create a link for one lesson, explanation or collection. Each link is a random token you can make unlisted or public, give an expiry, and revoke on its own. Viewers never see your code, answers or history; a shared explanation shows your own working only if you include it.

Practice records (which questions you answered, whether you were right, and whether you used help) are kept so your progress reflects what you did. They are yours: exported with everything else, deleted with everything else.