Privacy
How Suvartha handles personal data in the Suvartha app, on suvartha.in and on every church website. Last updated 14 September 2026.
Who we are
Suvartha is the service at suvartha.in: the Suvartha app, this site, and each church’s own website at its suvartha.in address. In this notice “we” means the people who run Suvartha. Each church decides what goes on its own site and app, and who its members are.
What we collect
- Your account: your name and phone number, which is how you sign in, and an email and address if you add them. Your password is stored hashed, so it cannot be read — not by us, and not by anyone with a copy of the database.
- A profile photo, if you choose one: the app opens your photo gallery only when you pick a photo, and uploads only that one photo. This is optional.
- What you post to your church: prayer requests, testimonies and live chat messages. These need you to be signed in. A testimony can be shown without your name, but the church office still sees who wrote it.
- Requests for help: when you ask your church for help, what you write, your name and phone number and any contact phone you give for the request are seen only by the church office. If the office publishes your need, it shows the name or family name you give, or no name if you leave that blank — never a phone number.
- Gift records: if you fill in a church’s “I’ve given” form, it stores your name, WhatsApp number, amount, UTR reference, fund, date, and whether you asked for an 80G receipt or to stay anonymous. Only the church office sees these. The payment itself happens in your own UPI or bank app — Suvartha never handles the money.
- Your Bible reading: saved verses, highlights, notes, your Bible in One Year progress and your reading journal, stored so they follow you. The church office cannot read your notes or your journal.
- About the device: a device id, which is a random string the app makes up the first time it runs, with the platform and app version. It is not your phone’s serial number and not its advertising ID.
- How the app is used: which screens are opened and a small set of events, sent to Google Firebase Analytics. Names, phone numbers and anything you read or write are removed before anything is sent.
- Counts, not histories: how many times a song was opened on a day, how many installs a church has. These are daily totals, with no record of which person read what.
- Messages to us: if you write through “Talk to us” or ask to delete your account, the name, phone number, email and message you send.
- Churches that register: the church’s details and its admins’ names and phone numbers. Subscription payments are processed by Razorpay; we do not see or store card details.
- Notifications, if you turn them on: a push token — an address that Expo, and through it Google or Apple, gives this phone so your church’s announcements, the daily verse and new-sermon notices can reach it — stored with your account and the kinds of notification you chose. It is used only to send those notifications, and is deleted when you turn notifications off or sign out, or when the phone stops accepting them.
- Birthday and wedding anniversary, if you give them: your date of birth and wedding anniversary, if you or your church office add them to your member profile. The year is optional. Only your church office sees them; other members see only your first name under “Celebrating this week”, and only if you turn on “Let my church wish me” and your church shows it — never your age or year. They are removed when you leave the church or delete your account.
What we do not collect
- Your voice. Live transcription in the app uses your phone’s own speech recognition — on the phone itself where the language is installed for offline use, otherwise the phone’s built-in recognition service, such as Google’s. Suvartha receives only the text, never the audio, and stores no audio.
- Your location, contacts, calendar, text messages or call logs.
- Card numbers, UPI PINs or bank logins.
- Your advertising ID. The app tells Meta’s and Google’s software not to read it, and does not ask Android for permission to use it.
Why we use it
To sign you in and keep your account working; to show your church’s content, and what you post, to the people it is meant for; to send sign-in codes by SMS; to answer your messages; to see which parts of the app and sites are used so we can improve them; and, on the websites, to measure our own adverts. We do not sell personal data, and there are no adverts inside Suvartha.
Who else receives data
- Your church: the church office sees its members’ names and phone numbers, and the prayer requests, testimonies, requests for help and gift records sent to it. One church can never see another church’s members, content or statistics.
- Google: Firebase Analytics receives app usage as described above, and Google Analytics receives page visits on suvartha.in and every church website.
- Meta (Facebook): the websites — suvartha.in, every church website and the admin panels — load the Meta Pixel. When a page first loads it sends Meta one page view, with the page address and what Meta’s script reads from your browser. When a church or a person finishes registering on suvartha.in, it also tells Meta that a registration was completed and of which kind. No names, phone numbers, emails or church details are sent. The app tells Meta only that it was opened, so we can tell whether an advert led to an install; it does not send your advertising ID.
- Companies that run the service for us: Railway hosts our servers and database, Cloudflare stores photos, audio and files and carries traffic to our API, an SMS provider in India sends sign-in codes, and Razorpay processes subscription payments. They handle data only to provide that service.
- Nobody else: we do not sell or rent personal data, and we disclose it only when the law requires us to.
If you start registering and stop before the end, we keep what you had typed (the church or your name, town, web address, your name, phone number and email) and the page you reached, so we can help you finish. We never keep your PIN. Ask us and we delete it.
Where it is kept and how it is protected
Accounts and records are in a managed Postgres database hosted on Railway. Photos, audio and files are in Cloudflare R2 storage. Everything between the app or your browser and our servers travels over HTTPS. Passwords and sign-in codes are stored hashed; a code expires and stops working after five wrong attempts. Each church’s data is kept apart from every other church’s.
How long we keep it
Your account is kept while it is open. What you post stays until you or your church office removes it, or your account is deleted. If a church leaves Suvartha, its data is kept for an export window and then purged. Messages to us are kept while we need them to answer you. Analytics are kept by Google as reports, under our analytics account’s settings.
Deleting your account
You can ask us to delete your account at any time. The account deletion page explains how, what is deleted and what is kept, and has a form for the request. We confirm with you on your registered phone number before anything is removed, and finish within 30 days.
Churches and their congregations
A church controls its own congregation’s content: what is on its site and app, who is on its members list, and which requests it publishes. We store that content on the church’s behalf. It belongs to the church, and the church can export it while its account is open. For something a church holds about you, such as a gift record, you can also ask the church office directly.
Children
The Suvartha app is for people aged 13 and over. It is not directed at children under 13, and we do not knowingly collect their personal data. If you think a child under 13 has an account, tell us and we will delete it.
Questions and requests
To ask for a copy of your data, a correction or a deletion, or to ask anything about this notice, write to us through “Talk to us” on the Suvartha home page. If we change this notice, the date at the top changes too.
This notice describes how the software behaves. It is not legal advice, and a church with a specific obligation should take its own.