Privacy Policy

Forms for Church can be reached about privacy questions and requests at hello@formsforchurch.com. Churches choose the questions in their forms and control their responses, team access, and delivery settings. Forms for Church operates the platform and handles account, support, and security data.

Information we collect

• Account and church information: names and email addresses of account holders and invited team members; church name, website, size, and campus details supplied during setup; roles, invitations, and account activity needed to run the service.
• Forms and responses: form questions, settings, responses, notes, and files uploaded by respondents. Responses may include personal or sensitive information that a church asks for or a respondent chooses to enter. A public form may be submitted without a Forms for Church account.
• Technical information: sign-in and church-selection cookies; a short-lived setup cookie; submission timestamps; limited browser information; and a keyed hash of a visitor's network address used to limit abuse and protect submissions. Abuse-limit counters are kept briefly and later cleaned up. A shortened hash and limited browser metadata remain with a submission until that submission is deleted. Service providers may also process ordinary request and security logs.
• Website analytics: we use Vercel Web Analytics to count visits to our public website pages, such as the home, pricing, templates, guides, comparison, use-case, and policy pages, and the sign-up, sign-in, and church-setup pages. For each counted visit, Vercel receives the page address shortened to its path plus up to four campaign labels (source, medium, campaign, and content), the website that linked to the page if your browser shares it, and ordinary request information such as network address and browser type, which Vercel uses to estimate unique visitors without cookies. We do not count visits to the signed-in app, our administration pages, church forms, or a church's own web address. When someone creates an account, their browser also reports the signup to Vercel with the campaign source label and the template chosen, if any.
• Setup milestones: our database records when an account or church first reaches each setup step: creating an account, confirming its email, creating a church, creating and publishing its first form, receiving its first response from someone who is not signed in, and starting its first paid subscription. It keeps at most the template used or the plan chosen. We use these records to understand and improve setup, to learn which outreach works, and to show aggregate counts on our website, such as how many churches have received their first response. We report each milestone once to Vercel Web Analytics as a named event with at most the template or plan and ordinary request information from the account holder's own request; the report for a church's first response is sent without the respondent's network address or browser information. Our own team's accounts and test or demo accounts are left out of these counts and reports.
• Campaign labels: when someone signs up through a tagged link, we may keep up to four short labels (source, medium, campaign, and content) with the account to understand which outreach led to signup and later church setup or payment. We do not store the full referring URL or form answers for this measurement.
• Billing information: a church owner's selected plan, trial period, subscription and payment status, Stripe customer and subscription identifiers, and related billing events. Stripe collects and processes payment details when the owner chooses a paid plan; Forms for Church does not ask for payment card numbers in a church form.
• Referral information, if the program is offered: the referral code used, the referrer and referred account and church, the original 14-day trial and first successful paid subscription payment needed for qualification, eligibility and fraud-review decisions, payment reversals, and reward delivery records. A referrer sees only aggregate referral status, not the referred church's name or payment details. If you provide a PayPal email address or Venmo username, we store it privately to arrange your reward. Authorized administrators can review payout details and record payment references and fees. Payout details are not included in referral alert emails or analytics.
• Support messages: information you provide when you contact us at our support email.

Creating a church begins a 14-day Pro trial without a payment method. The church owner may separately enter payment information with Stripe during the trial; no subscription charge is scheduled before the original trial end. Paid access depends on successful payment.

How information is used and shared

We use information to authenticate users, run forms and church workspaces, store and deliver responses as the church configures, send operational email, answer support requests, limit abuse, maintain the service, and understand how churches find, set up, and use it. Authorized support access to account or response data may be needed for a support request, security concern, abuse report, or legal duty.

Church members can see responses according to their church's permissions. A church can send notifications to addresses it chooses, including addresses outside its team after those addresses confirm. By default, a notification includes the form name, time, and a sign-in link; the church can instead choose fields whose answers appear in the email. A church can send confirmation email to a respondent. If webhooks are available and enabled, the church can send a full response, including the respondent's name and email if supplied, to its chosen endpoint. The church is responsible for explaining those destinations to respondents and for copies it sends outside Forms for Church.

Vercel hosts the service and provides the website analytics described above, Supabase provides authentication, database, and file storage, Resend delivers operational email when configured, Google Workspace hosts the support mailbox, and Stripe processes paid subscriptions when enabled. These providers receive information needed to perform those functions. If a referral reward is approved, an authorized administrator uses the PayPal email address or Venmo username you provided and the reward amount to send payment through your selected provider. We do not send church form answers to PayPal or Venmo. We do not use form answers for advertising or install an advertising pixel in the app.

Cookies and online tracking

The service uses cookies needed for sign-in, church selection, first-form setup, remembering a plan chosen during setup (up to 30 days), and securing a Planning Center connection while it is being set up (up to 10 minutes). Our website analytics does not use cookies. Campaign and referral labels can be carried through a signup link and associated with an account when provided; they are not kept in a tracking cookie. Our team can mark a browser used for testing so its visits are not counted; that setting is saved only in that browser's local storage. We do not use the app to follow a person's activity across unrelated websites, so a browser Do Not Track setting does not change this first-party service behavior. Service providers may receive technical information needed to deliver their services.

Optional advertising measurement

On our public marketing website, you can choose whether to allow the Meta Pixel to measure visits from our ads. It does not load before you choose Allow. If you allow it, Meta receives a page-visit event, public website address, approved campaign labels and ad click and browser identifiers, together with ordinary connection information such as your network address and browser type. Meta may use first-party and its own cookies to connect these visits with ads. Meta processes this information under its Privacy Policy.

We do not send Meta form answers, names, email addresses, church content, signup events or account activity. Automatic advanced matching and automatic event collection are disabled. The pixel does not run in our app, sign-in or signup pages, church forms, forms.church, or church custom domains. It also does not load when a page address or referrer contains data outside our reviewed marketing allowlist. We save your choice in this browser's local storage. You can withdraw or change it through Ad measurement choices in the marketing website footer. We treat Global Privacy Control as a refusal; declining does not affect the service.

Security verification

When enabled on account creation, sign-in and password-recovery pages, Cloudflare Turnstile checks browser and network information to help prevent automated abuse. Supabase validates the resulting verification token before accepting protected authentication requests. This check is for security, not advertising. Cloudflare describes its processing in its Privacy Policy.

Planning Center

If Forms for Church enables Planning Center for a church, and that church connects it and enables a form routing rule, we send only the mapped respondent name and email to its confirmed Planning Center People account and, if selected, its chosen workflow. We read limited account identity, workflow details, exact-email matches, and existing workflow-card state to route safely and avoid duplicates. We do not import a Planning Center directory or form responses into Forms for Church, or continuously sync changes from Planning Center. The church must provide any required respondent notice and permission before sending this information.

We keep connection credentials while connected and retain provider IDs and delivery records to operate the connection and investigate uncertain sends. Restricted safety and audit records can include Planning Center account, person, workflow, and card IDs, and a SHA-256 digest of a trimmed, lowercase email address. These records may remain after the related response, form, or church is deleted; they currently have no scheduled expiry. Deleting a response in Forms for Church does not remove a person or workflow card already sent to the church's Planning Center account.

Retention and deletion

Church owners and administrators can delete responses and forms in the app; only a church owner can delete a church. A successful response deletion removes the response and its file records from the active database and queues attached files for later removal. File cleanup may take longer if a maintenance job must retry. A previously issued download link may work briefly while the file still exists. Deleting a form or church also starts removal of its active data and associated files, subject to the service's cleanup process.

Deletion cannot retract notification or confirmation emails already delivered, copies sent to church-controlled webhooks or Planning Center, or copies a church exported. Backup copies and some security, billing, referral, or support records may remain after active data is removed where needed to operate the service, prevent abuse, or meet legal obligations; we cannot promise immediate permanent erasure from every system. There is no self-service account-deletion button. To request review, correction, or deletion of account information, email hello@formsforchurch.com. We will verify the request and explain what can be changed or removed. Respondents should first contact the church whose form they used; they may also write to us so we can help route a request to that church.

Children and changes

The service is for adult church account holders and is not intended for forms directed to children under 13. If you believe a child under 13 submitted personal information directly, contact hello@formsforchurch.com so we can review it with the church.

We will post the effective date of this policy. For material changes, we will update the policy and notify account owners by email before the changes take effect when we have a working owner contact address.