Security & your data

• We never sell or rent personal information.
• We never show ads — on any plan, including Free.
• We don't use your data to train AI models.
• Volunteers never receive marketing email from us.
• Your admins can delete sign-ups or whole sheets at any time, and the owner can delete the church's account entirely from the dashboard.

Your sheets, sign-ups, logos, and the people on your People page belong to your church (or to the people who submitted them). For volunteer information we act as your service provider — a data processor, in GDPR terms: the church decides what to collect and how to use it, and we process it only to run the service for you. That also makes your church responsible for handling volunteer information appropriately, including a volunteer's request to correct or remove their own details.

• Admins: name, email, church name, and a password stored only as a secure hash we can't read. Whether you ticked the product-news box, and when you confirmed it.
• Volunteers: what your sheet asked for — typically a name and email, sometimes a phone, a quantity, a note, and answers to your custom questions. A mobile number and the opt-in only when they ticked “text me a reminder” themselves.
• Your People list: names, emails, and optional phones you import, held for your church alone and used only for your own invitations, each with a one-click stop link.
• Connections: the tokens or API keys for a ChMS or Slack workspace you connect, encrypted at rest. Billing holds only your Stripe customer and subscription identifiers and your plan — Stripe handles the card itself.
• Logos and preview images you upload, and the server logs (IP address, browser type) any website keeps for security and debugging.

• All traffic is encrypted in transit with HTTPS.
• Passwords are stored as secure hashes, never as text.
• ChMS and Slack credentials are encrypted at rest and never shown back to you after you enter them.
• Access to production data is limited to the people who need it to run the service.
• Every admin can add two-factor authentication to their login — optional and free on every plan — with recovery codes.
• Two roles, deliberately: admins run sheets and volunteers; only the owner can change billing, add or remove admins, delete a sheet or the account, email the whole People list, or disconnect a ChMS.
• Public forms carry a quiet bot check and rate limits, so one inbox can't be flooded through a sheet.
• A read-only roster link is a long random address you can revoke or replace at any time from the Share tab.

No system is perfectly secure. If we learn of a breach affecting your data, we notify you as the law requires.

SignUpChurch runs on 9 service providers, all in the United States: hosting, the database, email delivery, text reminders, the bot check, analytics, the AI sheet builder, and payments. Each one, what it handles, and where, is on the subprocessors page. We tell account owners at least 30 days before adding a new one. Your own ChMS and Slack aren't on that list: you choose them and decide what we send, so they're your recipients, not ours.

The public sign-up page, the embed, and the manage, waitlist, and email-preference pages carry no analytics scripts, no session recordings, no advertising, and set no cookies. Fonts load from our own servers, not Google's. The only thing a sign-up page saves on a volunteer's device is their name and contact details, and only if they tick “Remember my details on this device.” The one note we keep about an embedded sheet is the domain of the website it's embedded on, counted toward your account — nothing about the volunteer viewing it.

Volunteers get email only about their own sign-ups — confirmation, reminder, a change to the date or place, a message from your church, waitlist and carpool notices — plus invitations your church chooses to send, each with a one-click stop link. The only text we ever send is the day-before reminder to a volunteer who ticked the box themselves; mobile numbers and opt-ins are never shared with anyone for marketing. Product news from us goes only to admins who opted in and confirmed from the email we sent. The full list is in Every email you can get from SignUpChurch.

SignUpChurch is intended for use by adults. We don't knowingly collect personal information from children under 13; a parent signs a child up for VBS, not the child. If you believe a child has given us information directly, contact us and we'll delete it.

• Export: each sheet's Sign-ups tab downloads a CSV of everyone on it, and the People page exports your whole roster with their latest answers (Basic and Pro).
• Correct or remove a volunteer: edit or remove them from the Sign-ups tab. A volunteer who asks us directly is pointed to your church first, since you control their record; we help either way.
• Delete a sheet or sign-up: any time, from the dashboard. That removes it from SignUpChurch; copies already synced to your ChMS or posted to your Slack are yours to manage there.
• Delete the account: the owner can do it from Dashboard → Security — the subscription is cancelled first, then every sheet, sign-up, person, and login is removed and a receipt emailed. Residual copies may persist briefly in backups before being purged. See Your account.

Churches in the UK, EU, or wider EEA are covered by our Data Processing Agreement, which is part of the Terms and needs no signature: we follow your instructions, keep data confidential, use only the listed subprocessors, help you answer people's requests, tell you about breaches, and delete the data when you leave. For admin accounts, billing, and our website the controller is Katie Allred Consulting LLC, PO Box 31, Nolensville, TN 37135, USA.

Found a security issue, or a sheet on SignUpChurch being used to deceive or harass people? Email support@signupchurch.com with the address of the page. A real human reads it, and the acceptable-use terms let us act on abusive sheets.