Privacy Policy
Effective July 12, 2026
Who runs ScriptureTrack
ScriptureTrack is built and run by its operator, an independent developer in the United States. (“Developer” is doing a lot of work in this sentence. For now, he’s a vibe coder I suppose.) For anything privacy-related, email joe@josephwaterman.com.
What we collect, and why
- Account basics — your email address and a password (we never see the password itself — it’s stored as a secure hash by Supabase, our sign-in provider). If you sign up with Google instead, Google sends us your name, email address, and profile photo. Why: creating your account and signing you in.
- Preferences — optional display name, timezone, week start day, theme, and your preferred Bible translation and reading site. Why: your timezone is how we know what “today” means for your schedule; the rest makes the app yours.
- Reading activity — the plans you start and the readings you mark complete, with dates. Why: tracking this is the entire point of ScriptureTrack.
- Reminder email records — if you opt in to daily reminders: your opt-in setting and a log of which reminders we sent on which days (so we never double-send, and so we stop automatically if emails to you bounce). Why: only to run the reminders you asked for.
- Error reports — when something breaks, a report goes to Sentry (our error-tracking service) that can include your IP address, browser type, and the page where the error happened. Why: finding and fixing bugs.
Cookies
We use only the essential cookies that keep you signed in. Your theme choice lives in your browser’s local storage. There are no advertising or analytics cookies. We don’t track you across other websites — so a “Do Not Track” browser signal changes nothing here; there’s no tracking to turn off. No third party collects data about your activity on other sites through ScriptureTrack.
What we do not do
- No ads, and no ad networks.
- No analytics trackers following you around.
- We do not sell or rent your personal information to anyone, for anything.
(Each item here is literally true today. If we ever add, say, privacy-friendly analytics, this section changes first.)
If you sign in with Google
When you choose “Sign in with Google,” Google sends us your name, email address, and profile photo. We use them only to create and secure your account and to show your name inside the app. We store them with the same protections as everything else, and we never share them with anyone beyond the service providers listed below. You can disconnect ScriptureTrack from your Google account any time at myaccount.google.com/permissions.
The services that help us run ScriptureTrack
These providers process data solely to provide their service to us:
| Provider | What it does | What it handles |
|---|---|---|
| Supabase | Database & sign-in | Your account, preferences, and reading data |
| Netlify | Hosts the website | Standard web-server logs, like every website |
| Resend | Delivers our email | Your email address and the messages we send you |
| Sentry | Error tracking | IP address & technical details when errors happen |
| Sign-in — only if you choose it | Name, email, photo at sign-in |
How long we keep your data and how to delete it
Your data stays as long as your account does. You can change your details in Settings any time, and deleting your account (Settings → Delete Account) permanently and immediately erases your account, profile, preferences, plans, reading progress, and reminder history. Two honest footnotes: our providers’ encrypted backups age out on their own schedules (within 30 days), and error reports already at Sentry expire after its 30-day retention period.
Your rights
- See it: email us and we’ll send you a copy of your data.
- Fix it: Settings.
- Delete it: Settings → Delete Account. No questions asked.
- If you’re in the EU or UK, you also have the right to complain to your local data-protection authority.
Children
ScriptureTrack isn’t directed at children under 13, and we don’t knowingly collect their information. If we learn we have, we’ll delete it.
When this policy changes
For changes we’ll update this page and its effective date.