Privacy Policyversion 1 · published 10 Nov 2026

Privacy Policy

This policy explains how AweChMS ("we", "us") handles personal information in AweChMS, the church management system we provide to churches, and on our website. It applies to church staff, church members and visitors whose details a church keeps in AweChMS, and to anyone who signs in.

1. Who is responsible for your information

  • Your church decides what information it keeps about you and why — for example your contact details, family, groups, attendance and giving. For that information your church is in charge (the "data controller"), and AweChMS keeps and processes it on the church's behalf, under our agreement with the church.
  • AweChMS is responsible for the information we need to run the service ourselves: sign-in and security records, our billing with churches, and messages you send to our support team.
  • If you have a question about the information your church keeps, contact your church first. You can also contact us at privacy@awechms.com.

2. What we collect

  • Information your church enters or you give it: names, contact details, addresses, date of birth, family links, membership details, groups and ministries, attendance, giving and pledges, and any notes or extra fields your church chooses to keep.
  • Your account: your email address or mobile number, your password (stored only as a one-way hash we can't read), 2-step verification settings, and your display preferences.
  • Sign-in and security records: when you sign in, the IP address and browser used, failed sign-in attempts, and a record of important actions (such as changes to money, permissions and personal data) so your church can see who did what.
  • How the service is used: counts of which parts of AweChMS each church uses each day (for example how many pages of the giving section were opened, how many check-ins or messages there were) and which accounts were active that day. These counts never include what anyone wrote, gave or looked at.
  • Online payments: when you give online, the payment provider your church uses (such as Stripe or Paystack) handles your card or mobile money details. We receive only the result — the amount, date, reference and the type of payment — never your full card number or PIN.

3. Signing in with Google

If your church allows it and you choose "Continue with Google":

  • We receive from Google your name, email address and Google account ID, and nothing else. We never see your Google password.
  • We use them only to sign you in to your church account: the first time, we match the email to the one your church has for you; after that, we recognise your Google account by its ID.
  • We don't use Google information for advertising, don't sell it, and don't share it with anyone except as needed to provide the service.
  • You can stop using Google sign-in at any time under Sign-in methods in your account, or remove AweChMS's access in your Google Account settings.
  • If a church connects a Gmail or Google Workspace account to send its emails, we keep a token that lets AweChMS send email from that account. We do not read, store or change the emails in it.

AweChMS's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. How we use information

  • To provide AweChMS to your church: keeping its records, sending the receipts, reminders and messages your church chooses to send, running reports, and letting you see and update your own details.
  • To keep accounts secure: confirming your email or phone, 2-step verification, spotting suspicious sign-ins, and signing you out after a period without activity.
  • To support churches when they ask for help, and to fix problems.
  • To bill churches for the service, and to understand which features are used so we can improve them (from the usage counts above, never from your church's records).

We don't sell personal information or use it for advertising, and we don't use your church's data for any purpose of our own.

5. Who we share it with

  • Your church's staff, according to the permissions your church gives them.
  • Service providers that help us run AweChMS, only as needed and under confidentiality obligations: the hosting provider where the system and backups are stored, the email and SMS services used to send messages, payment providers for online giving, and an error-reporting service (which receives technical details of errors, not your personal details).
  • The authorities, only when the law requires it.
  • If our business changes hands, the new owner would take over this policy's commitments.

6. Where it's stored and how long we keep it

  • Information is stored on servers in United States and may be accessed from the United States by our team, with the same protection wherever it is.
  • Your church decides how long to keep its records. Some records, such as giving receipts and the books, may have to be kept for the church's accounts.
  • Security records are kept for the period your church sets, so it can look back at what happened.
  • When a church stops using AweChMS, it can download its data for 30 days; we then delete it within 90 days, apart from backups, which are overwritten on their normal schedule.

7. Keeping it safe

Connections are encrypted (HTTPS); passwords are stored as one-way hashes; secrets such as payment and SMS keys are encrypted; staff must use 2-step verification; access follows the permissions each church gives; and important actions are recorded in a tamper-evident log. No system is perfectly secure, so please keep your password and devices safe too.

8. Cookies

We use only the cookies needed to run the service: one that keeps you signed in, and — if you tick "don't ask again on this device" — one that remembers your 2-step verification on that device. Your browser may also remember display choices, such as which menu sections you opened. We don't use advertising or tracking cookies.

9. Children

Churches may keep records of children, for example for Sunday school and family links. The church is responsible for having the agreement of parents or guardians where the law requires it. Parents can ask their church to see, correct or remove their child's information.

10. Your rights

You can ask your church to show you the information it keeps about you, to correct it, or to stop using or delete information it no longer needs. You can update much of it yourself in the members' page. The data protection law of the country where your church is located may give you further rights, and nothing in this policy takes those away. If you're unhappy with how your information is handled, contact your church or us at privacy@awechms.com; you may also complain to the data protection authority in your country.

11. Changes to this policy

We'll publish any changes here, with the date and version at the top. If a change is significant, we'll tell churches before it applies.

12. Contact us

AweChMS — privacy questions: privacy@awechms.com; support: support@awechms.com.

Back