Privacy
What our servers hold, what passes through them, and what never arrives. This page restates our data-handling design of record (written 2026-08-24, last ruled on 2026-11-11); when that changes, this page changes.
Never on our servers
- Your Canvas sign-in. The session from signing in to Canvas in the app (or a pasted access token) stays on your computer, in an encrypted file only HomePlate can open: sealed with a key the Mac app keeps in its own keychain item, or with your Windows account's own encryption. Our account database has no column it could land in, and the same goes for any other credential.
- Your grades. The app reads them live from Canvas on your machine. No synced table carries a score, and a filter scrubs grade numbers out of machine-written text (AI replies, summaries) before it leaves your computer. What you type yourself is yours and syncs as written.
- Your quiz and homework results. When the app keeps what happened on a quiz — the questions, your answers, what was right — it keeps it on your computer only. It never syncs, and an AI answer written from it syncs only as a note that the words stayed on the computer that wrote them. Practice inside HomePlate is different: the answers you give on its own practice tests and flashcards are yours and sync, so your review schedule follows you to another device.
- What the homework panel shows. When a homework site opens beside the tutor, the app keeps what is on your screen in memory and reads it for the tutor only when you ask it to find the problem you are on. It never answers or submits anything. The one thing it presses is a site's own "Enable accessibility" switch, which some sites need before their questions exist as text. The page as read is never saved; the problem it finds (its text, with your numbers) joins your assignment's problem list like any other and syncs with it, while the site's right-or-wrong marks and your results stay on your computer.
Transits, never stored
When you use HomePlate's AI without your own AI key (chat, the tutor, the study tools, the phone's chat), your prompt passes through our server to the AI provider and back. It is never written down: our usage ledger records only your account, a timestamp, the model, token counts, cost, and which part of the app asked (for example "tutor" or "class chat"). There is no column a prompt or a reply could land in, and prompt logging is never enabled at the provider. The tutor's prompts can include the problem on your screen and your own quiz results; every request goes only to AI providers that keep nothing (zero data retention).
A scanned page is read on your own device first. Only a page it reads poorly, and each page the phone app scans, is sent the same way as a picture, to be read into text; the provider keeps nothing, and what we keep of a scan is under "Stored when you scan".
A textbook you add stays on your computer. When an assignment or a study session needs its exercises, the page they are printed on is sent the same way as a picture, to be read into text; the provider keeps nothing, and the reading is kept on your computer only.
The shared AI has daily limits per account and product-wide; when one is reached you are told in plain words. Your own limit resets at midnight on your device's clock; the product-wide one resets at midnight UTC, and the message gives that hour on your clock.
How the app is used
While you are signed in, the app tells our server how long each of its pages was on your screen: the page's name (like "Today" or "Classes"), when, and for how many seconds. Nothing else: no web addresses, no course or assignment, nothing you type, click, or scroll. We keep it for 180 days to see which parts of HomePlate students use, and your account's rows are deleted with your account. Only HomePlate's operator can see these numbers and the AI usage above, on an internal dashboard that shows accounts by number, not by email.
Your sign-in
An account is required. Our account database holds your email, a hash of your password if you set one (never the password; an account created with Google has none), one hashed token per signed-in device, and — only if you choose it — the identifier Google gives us for your Google account. Signing in with Google tells us your Google account id and your verified email; we never see your Google password. Signing in with Google happens in your browser and returns to the app on your own computer; while you finish linking it to an existing account or enter an invite code, our server holds the verified Google identity, keyed by a token only the app holds. It is good for ten minutes; expired ones are cleared the next time our server stores another identity waiting like that, and deleting your account clears yours at once.
If you turn on two-step sign-in, we hold the secret your authenticator app and our server share, and hashes of your recovery codes (never the codes). When you sign the beta agreement we keep the name you typed, when you signed, the app version, and the internet address and app identifier the signature came from. We also keep how far your device's clock is from UTC, so your daily AI limit resets at your own midnight.
Stored when you sync
If you create an account, the app state you choose to sync — marks, overrides, syllabi, Class Memory, projects and chats, study tools, briefs, plans, reviews, drafts, and the files you upload to a project — is stored per account so it can follow you to another device. What may sync is a fixed list on both the app and the server; grades and your Canvas sign-in are on neither. Uploaded files count against a per-account storage quota. Data is stored in the United States (AWS us-east-2).
Stored for the phone app
So the phone app can show your day and follow a study session, your Mac sends our server three small things, each one row that is replaced as it changes: whether a study session is running, with its title and its start and end times; today's plan and class meeting times; and your classes' names. No grade and nothing from your Canvas sign-in is in them.
Counted when you add a textbook
When your computer finishes reading a textbook you added, it tells our server which book it was: the title, authors, edition and publisher from its title page, how many pages, sections and exercises it has, and a fingerprint of the file. Our server keeps one row per book and a count of how many times it was reported. It does not keep which account reported it, so the count stays when an account is deleted, and nothing from inside the book is sent.
Stored when you publish a theme
A theme you make stays with your own settings until you choose Publish. Then the gallery holds the theme's colors and fonts, its name and the author name you typed, for other students to see. Which account published it is kept so you can take it down, and is never shown. A like, an install or a report is kept once per account per theme.
Stored when you scan
Notes you scan and whiteboards you photograph in the phone app are stored per account so they follow you to your Mac: the page photos, the typed version the app reads from them, your corrections, the class and the date. They are yours; nothing from Canvas and no grade is in them. They count against the same storage quota as uploads, deleting one removes it, and deleting your account removes them all. A photo you take to check your work on the Mac is not stored: it is read once and kept only on your Mac.
Deleting your account
Settings → Account → Delete account removes every synced row, every uploaded file, every signed-in device, the Google link, any Google sign-in still waiting to be finished, your two-step sign-in secret and recovery codes, your signed agreement, what the phone app was shown, your scans, any theme you published and the likes you left, the usage ledger, the record of page time, and the account itself. The promise extends into our backups: the database replica ages out within 72 hours and the nightly file backup deletes what you deleted, so a deleted account leaves the backup within days. Signing out on its own deletes nothing remotely.
Questions
Write to grahamlmcwilliams@gmail.com.