Privacy Policy
This policy explains what information Gndsoft ("we", "us") collects when churches and their people use the GndChurch platform, including Ezra at ezra.gndsoft.com and its mobile apps, how we use it, and the choices you have.
1. Our role
Our customers are churches. Each church decides who it invites, which records it keeps in the platform and how long it keeps them. For that church information we act as a service provider that processes it on the church's behalf. If you have a question about your church's records, you may ask your church's administrator; we will help them answer it.
2. Information we collect
- Account information: your email address and name. If you sign in with Google, we receive your name, email address and profile picture, and, for Google Workspace accounts, the organization's domain.
- Church records: the church's name and settings, the people it adds (name and email), departments, roles and approval rules.
- Finance records: spending requests, reimbursements, budgets, amounts, receipts (images and the text on them), comments, approvals, hand-drawn signatures and signed final documents.
- Connections: if a church connects QuickBooks Online, the access tokens for that connection and the account mappings the church chooses.
- Technical information: IP address, browser and device type, and request logs used to run and secure the service. Our logs do not contain amounts, receipt contents, tokens or keys.
- Browser storage: we keep your sign-in session and preferences (such as language and theme) in your browser. We do not use advertising or analytics trackers.
3. How we use information
- To provide the service: sign you in, route requests to the right approvers, keep budgets, produce signed documents and send notification emails.
- To read receipts with AI when a church uses that feature, and to send approved records to QuickBooks Online when a church connects it.
- To keep the service secure, prevent abuse, fix problems and give support.
- To meet legal obligations.
We do not sell personal information, we do not share it for advertising, and we do not use church data to train AI models.
4. Google user data
When you choose "Continue with Google", we request only your basic profile (name, email address, profile picture and, for Workspace accounts, the domain). We use it only to sign you in and to match you to the church that invited your email address or allows your Workspace domain. We do not use Google user data for advertising, we do not sell it, and we do not transfer it to others except the service providers below that are needed to run the sign-in. Our use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.
5. Service providers
We use these companies to run the service. They process information only for us and under their own security and privacy commitments:
- Supabase – database and sign-in (United States).
- Cloudflare – hosting and encrypted file storage.
- Google Cloud – producing signed PDF documents and storing encrypted backups (United States).
- Anthropic – reading receipts with AI, only when a church uses that feature.
- Resend – sending sign-in and notification emails.
- Microsoft Azure – managing the master encryption key.
If a church connects QuickBooks Online, the records it approves are sent to the church's own Intuit account, where Intuit's privacy policy applies. We may also disclose information when required by law, to protect people's safety or our rights, or as part of a merger or sale of our business, in which case this policy continues to apply.
6. Security
Information is encrypted in transit. Amounts, receipts, signatures, AI results and final documents are encrypted with keys we manage before they are stored. Each church's records are kept separate from every other church's, access follows the roles the church assigns, and changes are recorded in an audit log. Database backups are encrypted and kept for 35 days. No system is perfectly secure; if a breach affects your information we will notify the church and, where required, you.
7. How long we keep information
We keep church records while the church uses the service, because approvals and financial records often have to be kept for accounting and tax purposes. Signed final documents and the audit log are not changed after the fact. When a church closes its account we delete its records within 90 days, unless the law requires us to keep them longer; encrypted backups expire within a further 35 days.
8. Your choices and rights
You can ask to see, correct, export or delete your information. Because many records belong to your church's financial history, we may need your church's administrator to approve a deletion. Residents of California and other places with privacy laws have rights to know, access, correct and delete personal information and to not be discriminated against for using these rights. We do not sell or share personal information as those laws define it. Contact us using the details below; we answer within 45 days.
9. Children
Ezra is not directed to children under 13, and we do not knowingly collect their information through it. If a future GndChurch product lets churches keep records about children, we will update this policy before it launches.
10. Where information is stored
The service is run from the United States, and information is stored there.
11. Changes
We will post any change on this page with a new effective date. If a change is significant, we will tell church administrators before it takes effect.
12. Contact
Gndsoft · support@gndsoft.com