Security and data: your community’s trust, kept with rigor

How we protect data

• Per-church isolation (Row-Level Security): every row of every table carries its owning church’s ID. It is PostgreSQL itself, at the database level, that rejects any read or write not belonging to the authenticated user’s church, not the app code.
• Encrypted throughout: TLS 1.2 or higher for all traffic; database and storage encrypted at rest with AES-256. Sensitive keys never leave the server and never reach the browser.
• Authentication and granular roles: passwords handled by Supabase Auth (bcrypt hashing), signed JWT sessions, “Remember me” limited to 7 days. Each user has a per-church role (owner, admin, coordinator, member, viewer) plus custom roles; the owner role is protected from accidental downgrade or deletion.
• Anti-abuse protection: public pages and functions (forms, sign-ups, requests) are protected by server-side rate limiting, stopping spam and automated requests before they reach your data.

GDPR rights

ChiesApp acts as Data Processor; your church is the Data Controller of its members’ data. We give you the tools to answer a GDPR request on your own, in a few clicks.

• Access and portability, per person (Art. 15 and 20): from each member’s page you export all the data the church holds about that person in a single file; each module also allows CSV export of aggregate data.
• Erasure, per person or for the entire church (Art. 17): you can anonymise a single member’s data on request, or delete the entire church and all linked data in a single action.
• Consent and communications: consent to email is tracked per person, with date and the ability to revoke. Nothing is sent to those who have not consented.
• Compliance inside the app: from the Compliance section you generate your church’s privacy notice and DPA, sign them electronically and download the PDF dossier. For each personal data field you ask for, you state purpose and legal basis, church by church.
• Reports shared without names: Analytics reports are shared with a link that never shows people’s names, with a password if you like, and you can revoke it. Site drafts stay private until you publish.
• DPA and sub-processors: the Data Processing Agreement is available on request at privacy@chiesapp.com. Sub-processors: Supabase (EU), Vercel, Resend, PostHog (EU) and Google, only with Google Calendar enabled. The full list is in the Privacy Policy.

ChiesApp team access to your data

The ChiesApp team does not access your church’s sensitive data automatically. When support or debugging on a specific case is needed, the path is explicit and audited.

• The super admin sends a motivated access request to your church.
• You receive an email and an in-app notification.
• You explicitly approve, specifying the duration (default 1 hour).
• Access expires automatically when the time is up.
• Every operation during access is recorded in an immutable audit log. Requests and audit trail are under Settings → Privacy and Support.

Where your data lives

• Database and storage: Supabase, in Frankfurt, Germany. Data stays within the European Union. The provider is SOC 2 Type II and ISO 27001 certified, and ChiesApp inherits those infrastructure guarantees.
• Application: Vercel (edge CDN), served over HTTPS only, with security headers (HSTS, X-Frame-Options, X-Content-Type-Options).
• Transactional email: Resend, with a domain verified with SPF, DKIM and DMARC.
• Backups: managed automatically by Supabase with Point-in-Time Recovery; notification logs are purged periodically to minimise the data processed.

What is on you

• Use a strong, unique password for the owner account.
• Do not share invite links or public access codes over insecure channels.
• Review your team’s roles periodically.
• Approve ChiesApp team support requests only if you actually requested them.

Found a vulnerability?

If you believe you have found a security issue, please report it responsibly to security@chiesapp.com before making it public. We respond within 48 business hours, and we run periodic, repeatable security tests across the whole platform.

Transparency: what we do not promise

No platform is immune to attacks, and we will not promise the impossible. What we guarantee is a model built on established best practices (RLS isolation, encryption, least privilege, audit logs, rate limiting), with periodic security testing and fast incident response. We do not yet hold independent certifications (ISO 27001, SOC 2) for ChiesApp itself: we inherit those of our hosting provider. Last updated: 14 July 2026, version 1.1.