Privacy policy

Effective date: 15 October 2026

Wells is operated by Jethro Staggs trading as Wells Church Communications (ABN 23 650 020 425) (“we”, “us”). This policy explains how we handle personal information when you use Wells, manage a church workspace, or visit a church page hosted on Wells.

Information we collect and why

For church team accounts, we hold your email address, profile name, account identifier, workspace memberships and roles, invitations, and account activity. We use this information to sign you in, control workspace access, support you, and protect the service. Password authentication is handled by our authentication provider. We do not receive your Google password.

If you choose Google sign-in, we request your basic account identity: your email address, name, profile information and Google account identifier. We use these details for authentication and account management. Wells does not request access to your Gmail messages, Google Drive files, contacts, or calendars.

We store the content churches enter or upload, including church contact details, event information, links, teaching material, photographs and other artwork. Drafts and published versions are held separately. A church’s authorised editors decide what to publish; published material is available to the public and may be indexed or copied by others. Content and team membership may reveal a person’s religious affiliation. Churches should only provide and publish personal or sensitive information they are authorised to use.

We also process support enquiries, invitation and account-email delivery information, security logs, and workspace billing-contact details when entered. Paid subscription processing is not currently enabled.

You can browse public church pages without creating an attendee account. We collect basic page and interaction measurements, such as page views, link clicks, referring website hostname, approved campaign labels and timestamps. A church-specific random identifier is stored in your browser and refreshed when you visit on a new day. The server transforms it into a church-and-day-specific identifier for approximate visitor counts. It is not used as a cross-church advertising identifier. Infrastructure providers may separately process IP addresses, request paths and device/network information to deliver and secure the service.

Cookies, local storage and external services

Team sign-in uses session cookies. Visitor measurement uses browser local storage. You can clear these through your browser settings; disabling storage may affect sign-in or measurement. Authentication email open and click tracking are disabled in our sending configuration.

When an editor searches for an address, the entered search text is sent to Geoapify to return suggestions. Adding a quick link may retrieve the linked website’s public title and image metadata. Playing embedded media, opening an external link, or using another organisation’s registration or giving service can share information with that provider under its own privacy policy.

Who receives information

Authorised members of your church workspace can access information according to their role. We use service providers to operate Wells, including Supabase for authentication, database and file storage; Vercel for hosting; Resend for transactional email; Google for optional sign-in; Geoapify for address suggestions; and Kit for newsletter and early access sign-ups. Authorised support personnel may access information when needed to operate, support or secure the service.

We may disclose information where required or permitted by applicable law. We do not sell personal information, and we do not use Google sign-in data for advertising.

Churches are responsible for their own collection and use of information, including information submitted through services they link to. Contact the relevant church about its content and activities, or us about Wells account and platform information.

Storage, security and retention

Our primary application database region is Sydney, Australia. Our configured email sending region is Tokyo, Japan. Other provider operations, delivery networks and support may process information overseas. Our providers are based in, or may process information in, the United States (Vercel, Supabase, Resend, Google, and Kit for newsletter and early access sign-ups), Japan (email sending) and Germany (Geoapify address search).

We use access controls, encrypted connections, private file storage and role-based workspace permissions. No online service can guarantee absolute security.

Detailed product analytics are scheduled for aggregation and deletion after 90 days; aggregate daily totals remain. Account information, church content, publication history and operational records are kept while the church workspace or your account is active. When you ask us to delete your account, we delete it within 30 days, unless we need to keep something to meet a legal obligation. Backups and legal obligations may affect when information can be fully removed. Unpublishing a page does not necessarily remove copies retained by search engines or other people.

Your choices, access and complaints

Contact hello@wells.church to request access to, correction of, or deletion of your personal information, or to raise a privacy concern. We may need to verify your identity and consider legal or operational requirements before acting. A workspace owner can manage team access; losing workspace access is distinct from deleting your Wells account and records.

Please explain your concern and the outcome you are seeking. We will acknowledge your complaint within 5 business days and aim to give you a full response within 30 days. If the matter remains unresolved, you may be able to contact the Office of the Australian Information Commissioner at oaic.gov.au or another relevant regulator, depending on the applicable law.

Changes

We will publish updates to this policy with a revised effective date and provide further notice where appropriate or required.