Who we are

Acts Bible is operated by Stoney DeVille (stoney@stoneytech.net). If you have any questions about this policy or your data, that's the address to write to — you will reach the human who operates the service.

What we collect, and why

Account data (signed-in users only)

When you sign in with Google, we receive:

• Email address: used to identify your account and to send the monthly note unless you unsubscribe.
• Display name: the name your Google sign-in gives, until you save a different one in your profile. Cases, ideas and comments you post show it as their author, and a deacon nomination you make shows it as its sponsor. If what you post still shows your Google name after you saved a different one there, save it again.
• Photo URL: used only as your avatar in the UI.
• Firebase UID: a random opaque identifier linking your contributions to your account.

If you choose to add optional profile info (church name, etc.), that is also stored with your user record.

Content you create

Bookmarks, notes, study history, apologetics cases, votes, and any other contributions are stored under your UID. Deacon and admin actions (reviews, approvals) are written to an audit log for transparency.

Usage data

Like any web service, we see IP addresses and basic request metadata in server logs for rate limiting, fraud prevention, and cost attribution of LLM-backed features. We do not fingerprint browsers or sell analytics data.

Email: the monthly note

Once a month, Acts Bible sends one email, the monthly note, about what is on the site. It goes to every account with a verified email address, unless that account has unsubscribed. Stoney reviews and edits each issue and sends it himself. The site sends no other bulk email. A message about a single event, such as a deacon invitation, is separate and goes only to the person it concerns.

Who sends it

The site sends the note itself, from an actsbible.com mailbox. Namecheap Private Email carries the mail as our email processor: it receives each message, with your email address on it, to deliver it. The note does not go through Substack or any other newsletter service, and we do not give your address to anyone else to send it.

The older weekly debate article went through Substack. If you turned it on, your email address, display name, account ID and the date you opted in could have been shared with Substack for that list. That article has been retired, and the site no longer sends anyone's details to Substack. The export that built the list has been removed, and deleting an account no longer sets its email address aside for removal from the list. Deleting your account here does not reach that list. To leave it, use the unsubscribe link in any email from it, or write to stoney@stoneytech.net.

How to stop it

• Every note has an unsubscribe link at the bottom. Open it and confirm, and the note stops for your account at once. If your mail app shows its own Unsubscribe button, it uses the same link.
• Or turn off Monthly note in your profile, under Account. You can turn it back on there at any time.

Stopping the note does not change anything else about your account.

What we keep

Your account record holds whether you get the note and when that last changed. Each change is also written to your account's audit log, with where it came from: the checkbox in your profile, the email link, or the set_my_monthly_note MCP tool.

For each issue we keep a one-way record per recipient, so that no one gets the same issue twice if a send is interrupted and run again. Each entry is a one-way code made from the issue and the account. No email address, name or account ID is stored with it.

No tracking

The note has no tracking pixels and no click tracking. Its links go straight to the pages they name, with nothing added to them, and we do not record whether you opened it.

Your GDPR + CCPA rights

If you're a signed-in user, you can exercise the following rights directly from the app. Your profile opens when you select your name at the top of the app.

• Right of access (GDPR Article 15): download a JSON archive of your account: your profile, what you keep in the app (bookmarks, notes, reading history and plans, workbook answers, group memberships), the cases, ideas and comments you wrote, your votes on ideas, and your deacon activity (your role, your votes on cases and nominations, and the nominations you made). It also holds the entries you made in the audit log on each case and in the weekly dispatch log, and the entries in the log of deacon role changes that name your account ID. Some records of review and publishing work are not in it yet, among them your requests for edits and your approvals of history lessons; to have those, write to the address below. Use the "Export my data" button in your profile, under Your data, or call the export_my_data MCP tool. Rate limited to 1 export per 24 hours.
• Right to erasure (GDPR Article 17): permanently delete your account. Use the "Delete my account" button in your profile, under Your data, or call the request_account_deletion MCP tool. The action is irreversible. First it cancels any monthly donation you started through Stripe while signed in. If it cannot confirm with Stripe that the donation has stopped, it deletes nothing, and you can try again later. Then it deletes your profile and what you keep in the app, and takes you out of every study group. It takes your name and account ID off the cases you wrote, the deacon nominations you made, and the ideas and comments you posted; their text stays, shown as from a former user. A study group you made keeps going for its other members. A one-way code takes the place of your account ID in the audit log on each case, the log of deacon role changes and the weekly dispatch log, and on your votes on cases and ideas, your requests for edits to a case or a history lesson, your approvals of history lessons with the audit entry for each, and any study group you made. It does the same on a case you featured as an admin, a chapter synopsis or Life Graph arc you reviewed or unpublished, a monthly note you edited or sent, and a deacon nomination you accepted. Your donation records are kept for refunds, chargebacks and tax records, under that one-way code and with any customer ID Stripe gave you. A few other records of review and site administration keep your account ID, such as a draft of site content you saved as an admin; to have those removed, write to the address below. Two small records about the erasure itself remain. One, filed under your account ID, stops a session that is still signed in from writing anything again. The other, filed under a one-way code made from that ID, lists which erasure steps finished. Neither holds your email address or name.
• Right to rectification: update the display name and church name stored with your profile at any time in your profile, under Account. Saving a display name there also changes the name on what you post: at once from the browser you saved it in, and within an hour from any other device or app where you are already signed in. What you posted before keeps the name it was posted with. Your email address comes from your Google sign-in; to have it, or anything else we hold, corrected, write to the address below.
• Right to object to email: stop the monthly note at any time with the link in any note or the "Monthly note" checkbox in your profile, under Account. Past changes remain in your audit log; every send uses your current setting.
• Right to data portability: the JSON archive from Article 15 above is a machine-readable export you can feed into any other service.

For any rights request we can't surface in-app — or to ask questions about how we handle your data — write to stoney@stoneytech.net.

AI service providers

When you choose an AI-backed feature, Acts Bible may send the text needed to answer that request to an external model provider, such as Anthropic, Google, OpenAI, xAI, or OpenRouter. We minimize the context sent and do not send passwords, payment-card data, or unrelated account records. These providers may process data outside our US-hosted Google Cloud environment; do not include sensitive personal information in an AI prompt.

How we store and protect your data

• All data is stored in Google Firebase / Firestore (us-central1), encrypted at rest and in transit.
• Authentication is handled by Firebase Auth — we never see your password.
• Payments (if you support the project) are handled by Stripe — we never see your card details.
• Admin access is restricted by Firebase custom claims and a Firestore-backed allow-list.

Cookies & local storage

Acts Bible uses only essential cookies + local storage — mostly Firebase Auth session tokens and your display-preference cache (tabs open, last verse viewed, etc.). We do not use advertising cookies or third-party trackers.

Children

Acts Bible is not directed at children under 13. If you become aware that a child has signed up, please contact stoney@stoneytech.net and we'll delete the account.

Changes to this policy

If we materially change this policy, we'll tell signed-in users in the app or by email. The change of 2026-10-01, which starts the monthly note for every account, is announced at the top of the first monthly note each account receives. This page always shows the current effective version; the "Last updated" date below tracks the most recent revision.