Last updated: September 18, 2026
ChurchMng holds information about real families and real children. This policy explains what we collect, why, and what we will never do with it.
ChurchMng is operated by SMC Media Technologies, Inc. (“SMCTech”, “we”, “us”). This policy covers the ChurchMng platform at churchmng.app, the ChurchMng website at churchmng.com, and the ChurchMng Admin and ChurchMng Family mobile apps.
It matters which hat we are wearing:
ChurchMng Admin is the counter and administration app used by a church’s own staff and volunteers. There is no sign-up inside the app: a church administrator creates the account on the web platform, and the operator then signs in with that phone number and a one-time code texted to it. ChurchMng Family is the companion app for a church’s member families.
Everything the apps send goes to that church’s own ChurchMng account. Neither app contains advertising, analytics SDKs or tracking of any kind, and we do not track users across other companies’ apps or websites.
| Data | Why |
|---|---|
| Name | The signed-in operator; the family member, customer or donor chosen at the counter. |
| Phone number | Signing in (the one-time code), finding a family member, and texting a receipt. |
| Email address | Optional, on a donation record. |
| Purchase history | The orders, donations and refunds recorded at the counter. |
| User ID | The signed-in account, so the church knows who rang up a sale and which permissions apply. |
| Other user content | Order notes and special instructions typed by the operator. |
The apps never see card data. When a card is tapped on Tap to Pay on iPhone or read by a Stripe Reader, the card details go from the reader directly to Stripe. We receive only the outcome and a masked reference such as “Visa •••• 4242”. We do not store card numbers, bank account details or payment credentials anywhere.
| Permission | What it is for |
|---|---|
| Location (while using the app) | Required by Stripe for every in-person card payment, for fraud prevention. The app itself never reads your location and we do not store it. |
| Bluetooth | Connecting to a Stripe Reader for card payments. |
| Camera | Scanning item barcodes and reward QR codes. Images are processed for the scan and not kept. |
| Face ID | Optional. Unlocks a sign-in token stored in the device keychain so an operator does not need a texted code every time. Face data never leaves the device and is never available to us. |
Settings kept on the device itself — the chosen card reader, the last shop opened, the display theme — stay on the device.
Household and member records: names, phone numbers, email addresses, postal addresses, birthdays and family relationships. Activity records: event registrations, orders, payments, family tab balances, rewards, messages to the church, and Sunday School enrolment and attendance where that module is in use.
Sign-in events, administrative actions written to the audit trail, and technical logs such as IP address, device and browser type, and error diagnostics. We keep these to operate the service, investigate problems and detect abuse.
We do not store card numbers, bank account details or payment credentials. We do not use advertising trackers or third-party analytics, and we do not build profiles of visitors or users.
We do not sell personal information, rent or trade it, use it for advertising, or use one church’s data for the benefit of another. Churches on the platform cannot see each other’s directories.
We use a small number of service providers to do specific jobs, and each receives only what it needs for that job:
| Purpose | Provider | What is shared |
|---|---|---|
| Card payments and donations | Stripe, PayPal | The payment amount and the details the processor needs to complete the transaction. Your church’s own processor accounts are used, and funds settle directly to your church — SMCTech never holds the money. |
| Text messaging | SignalWire | The recipient’s phone number and the message content. |
| Email delivery | Your church’s own mail server | The recipient’s email address and the message content. |
| Optional AI camera features | Anthropic | Only the image or document a user chooses to scan, such as a supplier receipt. Church data is not used to train AI models. |
We may also disclose information where we are legally required to, or where it is necessary to protect someone’s safety or to establish or defend a legal claim.
Church systems necessarily hold information about minors — a child registered for a retreat, a student in a Sunday School class. That information is entered by the child’s own parent or guardian, or by a church servant acting for the church. It is visible only to that family and to the administrators the church authorises. It is never used for advertising, never sold, and never shared outside the church except through the service providers listed above. A parent may ask their church to correct or remove it at any time, and the church can act on that request directly.
We keep church data for as long as your church uses ChurchMng, and for a short period afterwards so that an accidental departure can be undone. Your church can ask us to delete its data at any time, and we will — subject to any records we are legally required to retain, such as payment records kept for accounting purposes. Backups are cycled on a schedule, so deleted data may persist in backups briefly before it ages out.
Accounts in the ChurchMng Admin app are created and removed by a church administrator on the web platform; the app itself has no sign-up. To have an operator account removed, ask your church administrator, or write to us at the address below and we will pass the request to your church. Families using the ChurchMng Family app can delete their own account and its data from inside that app.
The ChurchMng platform uses cookies that are strictly necessary to run it: keeping you signed in, remembering your church and shop selection, and remembering interface preferences such as your counter layout. There is no advertising, no analytics and no cross-site tracking, which is why you are not shown a consent banner. The mobile apps use no cookies.
Data is transmitted over encrypted connections and stored on infrastructure operated by SMCTech in the United States. Administrator sessions use hashed, expiring tokens and support passkey and Face ID sign-in. Access within a church is limited by granular permissions, and administrative changes are recorded in an audit trail. No system is perfectly secure, but we treat church data as the sensitive information it is.
If we change this policy we will update the date at the top. If a change materially affects how we handle personal information, we will notify the churches on the platform directly rather than relying on you to re-read this page.
Questions about this policy, or a request about your information: churchmng@churchmng.app.
© 2026 SMC Media Technologies, Inc. · ChurchMng