Clear about what we collect, and careful with what churches entrust to us.

Churches use Pewly to manage information about their members, visitors, services, attendance, prayer requests, reminders, and follow-up care.

For most church-member information, the church decides why the information is collected and how it is used. Pewly provides the platform that stores and processes that information on the church's behalf.

Pewly separately decides how to handle information needed to operate its own business, including team accounts, authentication, support requests, security records, website analytics, waitlist registrations, and marketing-consent records.

If you are a church member or visitor with a question about information entered or managed by your church, you may need to contact the church first. Pewly can assist the church and will also respond to privacy requests sent directly to us.

We use personal information to:

• Create and authenticate accounts.
• Associate team members with the correct church and role.
• Operate church member, attendance, prayer, follow-up, and reminder features.
• Provide public church join and self-check-in forms.
• Send account confirmations, password resets, invitations, service reminders, follow-ups, and support responses.
• Help churches identify members who may need follow-up care.
• Respond to support and contact requests.
• Maintain security, prevent abuse, and investigate errors.
• Improve reliability and usability using privacy-conscious analytics.
• Maintain consent records and send future product updates only where the recipient expressly opted in.

Pewly does not sell personal information and does not use church member or prayer-request information for advertising.

We may access or disclose information when reasonably necessary to operate and secure the service, investigate misuse, comply with legal obligations, or respond to valid legal process.

Account confirmations, password resets, invitations, support replies, church reminders, and follow-up messages are transactional or service-related communications.

These messages are sent because they are necessary to provide the requested service or because a church is using Pewly to communicate with its members. They do not depend on Pewly marketing consent.

A church is responsible for ensuring that its use of member email addresses and phone numbers complies with its own legal and consent obligations.

Pewly's marketing opt-in is optional and unchecked by default. Declining marketing does not prevent someone from creating an account, joining a waitlist, contacting support, or receiving transactional communications.

Pewly is not currently sending marketing-email campaigns.

Although Pewly records marketing-consent decisions, the automated unsubscribe and suppression system has not yet been built. Pewly will not begin sending marketing campaigns until each marketing email includes:

• A clear unsubscribe link and no-login unsubscribe process.
• Appropriate email unsubscribe headers.
• A suppression mechanism that prevents future sends after someone unsubscribes.
• Pewly's mailing address and sender identification.

Until self-service withdrawal is available, you can withdraw a marketing opt-in by emailing [email protected]. Withdrawing consent will not affect transactional communications or actions taken before the withdrawal.

Pewly's primary database, authentication system, and file storage are provided by Supabase.

The Supabase project is hosted in East US (Ohio), United States, in the us-east-2 region. Pewly does not currently provide Canadian data residency.

Information may also be processed in other countries where Pewly's service providers and their subprocessors operate. Information processed outside Canada may be subject to the laws of those countries, including lawful access by courts, law-enforcement agencies, or government authorities.

All churches currently share one Supabase project and database. Pewly does not operate a separate physical database for each church.

Instead, tenant information is logically separated using:

• A church identifier on tenant records.
• PostgreSQL Row Level Security and role-based permissions.
• Restricted public database access and server-side validation for public forms.
• Account-revocation checks enforced at the database level.
• Short-lived signed URLs for private team profile photos.

Church administrators and sub-administrators can access the information their role permits within their church. Ushers and other roles receive more limited access.

Pewly's trusted server processes and authorized operators may use privileged access when needed to operate, secure, troubleshoot, or support the service. Privileged credentials are not exposed to ordinary users.

Team profile photos are stored privately and displayed through temporary signed links. Church logos remain public because they are intended for public-facing church pages.

No online system can guarantee complete security. We take reasonable steps to protect information, but cannot promise that unauthorized access, loss, or misuse will never occur.

Before an analytics event is sent, Pewly removes query strings and replaces sensitive route information such as invitation tokens, member IDs, church slugs, service IDs, and church subdomains with non-identifying placeholders. Vercel's infrastructure and diagnostic logs are separate and may still process IP addresses and request metadata.

Pewly uses essential authentication cookies to keep users signed in, refresh sessions, and protect authenticated areas. Disabling them may prevent you from signing in or using authenticated features.

Pewly does not currently use advertising cookies. Vercel Web Analytics is cookie-free and is used for general, aggregated product and site analytics rather than cross-site advertising.

On Pewly's public pages, a small local-storage value records that you acknowledged the cookie notice so it does not reappear on every visit. It contains only the acknowledgment state, not an advertising identifier or browsing history. Because browser storage is scoped by website origin, a church subdomain may remember the notice separately from pewly.app.

Google and other external providers may use their own cookies when you visit their sites or complete an OAuth sign-in flow. Their use of cookies is governed by their own policies.

Pewly provides billing owners with a self-service way to close a church workspace. This is a soft deletion: access, public forms, invitations, check-in, and unattended messaging stop immediately, while the church's records remain preserved for a possible support-led restoration. Restoration is manual and is not available as a self-service action.

Generally:

• Church and account information remains while the church uses Pewly and, after a soft deletion, while reasonably needed to support restoration, legal obligations, security, and dispute resolution.
• Removing a team member revokes access but preserves the account row and historical activity.
• Deleting a member currently removes associated attendance, follow-up, and reminder records.
• A prayer request may remain as an unlinked church record after its associated member is deleted unless separately removed.
• Marketing-consent records may be retained as evidence of the choice presented and recorded.
• Short-lived rate-limit records are automatically pruned.
• Service providers may retain operational or delivery records under their own retention policies.

Churches and individuals can request access, correction, or deletion by emailing [email protected]. Pewly will verify the request and handle it manually. Where the information is controlled by a church, Pewly may need to coordinate with that church.

We may retain limited information where reasonably required for legal obligations, security, fraud prevention, dispute resolution, or evidence of consent and withdrawal. We will not claim that information has been deleted until the applicable records have actually been identified and handled.

Pewly is not directed at children and does not knowingly invite children to create Pewly team accounts.

Churches may use Pewly to manage information about children or youth who participate in church activities. The church is responsible for deciding what youth information is appropriate to enter and for obtaining parental or guardian authorization where required.

Public church forms are provided for use by the church. Because those forms do not currently include an age-verification system, it is possible that a minor could submit information directly.

If you believe a child submitted personal information without appropriate authorization, contact [email protected]. Pewly will review the request and coordinate with the relevant church where necessary.

Depending on the circumstances, you may ask to:

• Access personal information Pewly holds about you.
• Correct inaccurate or incomplete information.
• Withdraw marketing consent.
• Request deletion of personal information.
• Ask how information has been used or disclosed.
• Raise a concern about Pewly's privacy practices.

Send requests to [email protected]. We may need to verify your identity before providing access or changing information. If your request concerns information managed by a church, we may refer the request to or coordinate with that church.

If you are not satisfied with Pewly's response, you may contact the Office of the Privacy Commissioner of Canada or another privacy regulator with jurisdiction over your concern.

Pewly is operated from Canada, while its primary Supabase-hosted data is stored in Ohio, United States.

Churches and users outside Canada should understand that their information may be transferred to and processed in Canada, the United States, and other countries where Pewly's service providers operate.

A church using Pewly outside Canada remains responsible for understanding and meeting the privacy and communication requirements that apply to its own collection and use of member information.

Pewly may update this Privacy Policy as the service, its providers, or legal requirements change.

If a change is significant, we will provide reasonable notice through the service, by email, or by another appropriate method. The “Last updated” date at the top will show when the policy was most recently revised.

Questions, concerns, access requests, correction requests, consent withdrawals, and deletion requests can be sent to:

Email: [email protected]