Privacy Statement

This statement explains what SDA Flow (sdaflow.com), a service of Tompkins R&D (tompkinsrnd.com), collects on this Site, and how we handle the information a church keeps in its workspace on the church’s behalf.

If you sign in to a church’s workspace, the church decides what it keeps about you and who may see it, and its own privacy statement, on its own site, describes that in detail. This statement covers what we do as the company that runs it.

1. What we collect on this Site

• A request for a workspace: what you type into the form — the church, your name and email address, and any phone number, conference, attendance, interests and message — and the network address it was sent from, which we use only to limit how often one address can send it.
• Mail you send us at info@sdaflow.com.

We use it only to answer you and, if your church goes ahead, to set up its workspace. The Site sets no analytics, advertising or tracking cookies.

2. Information in a church’s workspace

A church’s workspace holds what the church keeps: its people and their contact details, its rosters, bulletins, mailings, captions and the rest, depending on the features it uses. That information is the church’s.We handle it only on the church’s behalf and only to run the Service for it — never for our own purposes, and never for anyone else’s.

• Kept apart.Each church’s records are in a database of its own, separate from every other church’s. Its files are kept in private storage and reached only through its own site.
• What our staff see.Our operators’ console shows each church’s plan, its features, how many people and sign-ins it has, how much storage it uses and how much of each paid service it used — never a person’s details. We look inside a church’s records only to keep the Service running and secure, to fix a problem the church asks us about, or where the law requires it.
• What we count. To price the paid services a church uses — AI, captions, translation, voices, Bible text, address lookup, mail — we record how much was used: a quantity, a model, the feature, and whose account paid. Never the words.
• Requests from a church’s people. If you want to see, correct or remove what a church keeps about you, ask the church: it decides, and its administrators can do it. If you write to us instead, we will pass your request to the church and help it answer.

3. Signing in

You sign in to a church’s workspace with a one-time link sent to your email address, with a password if you set one, or with a Google, Microsoft or — where offered — Facebook account. With one of those accounts we receive your account identifier, your email address, whether that address is verified, and your name; never your password, your contacts or anything you post, and we never post anything for you. A sign-in passes once through sdaflow.com on its way back to the church’s site; nothing about you is kept there.

4. Service providers

We use a small number of other companies to run the Service. Each receives only what its task needs:

• Hosting, for the Service’s servers and databases.
• DigitalOcean, for file storage — pictures, flyers and other files a church uploads.
• Amazon Web Services, to deliver email: sign-in links and the mail a church sends.
• Cloudflare, for our domain names, and to pass mail sent to us on to our inbox.
• Google, Microsoft and Facebook, only when you choose to sign in with them.

Depending on the features a church uses, its workspace may also send what a task needs to AI providers (such as Anthropic, OpenAI or Google), Deepgram (live captions), Lara (translation), Microsoft Azure (voices), Google Maps (address lookup), API.Bible and Biblia (Bible text) and YouTube. The church’s own privacy statement names the ones its features use. We may also disclose information if the law requires it, or to protect the safety of a person or the security of the Service.

5. Cookies

A church’s site uses one essential cookie to keep you signed in, and a short-lived one while a sign-in is under way; our operators sign in on a separate address with a cookie of their own. Choices such as your language are remembered in your own browser. There are no analytics, advertising or tracking cookies.

6. Security

Information travels over encrypted connections. Sign-in links, sessions, passwords and keys are stored only as one-way hashes, and the keys to other companies’ services are encrypted. No system is perfectly secure, but we take reasonable measures to protect what we hold, and we will tell a church promptly if we learn its records have been exposed.

7. How long it is kept

We keep a request for a workspace for as long as we need it to answer you and to follow up. What a church keeps is kept as the church decides, for as long as it uses the Service; when a workspace ends, its records and files are deleted as our Terms of Service describe. A record of what our operators change is kept permanently.

9. Children

The Site is not directed at children, and signing in is meant for adults. A church may keep records of the children in its families, such as who is in a household; it is responsible for doing so with a parent’s or guardian’s permission where that is required.

10. Changes

We may update this statement; the effective date above shows when it last changed. See also the Terms of Service.

11. Contact

Questions about this statement or your information: info@sdaflow.com.