Perfectly Flawed Designs, LLC
Privacy Policy
Last updated: November 7, 2026
Information We Collect
We collect information you voluntarily provide, including church names, administrator contact information, user account credentials, and — optionally, to ensure no sales tax is applied to your subscription — your church’s tax-exempt ID / EIN. Church administrators may also enter congregation member data including names, contact details, giving records, attendance history, and prayer requests. Church administrators, and the finance team members they designate, may also keep the church’s financial records in Accounting, including accounts, budgets, income and expense entries, and uploaded receipts and bank or credit card statements. When AI features are enabled, we additionally collect and store the text of AI chat conversations — including your messages and AI responses — in our Supabase database for quality assurance, support resolution tracking, and service analytics.
How We Use Your Information
Information collected is used solely to operate and improve the Service. AI conversation logs are used to calculate support resolution metrics visible to super-administrators and to improve the quality of AI interactions. We do not sell, rent, or share your church’s data with third parties for marketing or advertising purposes.
AI-Powered Features
The Service includes several AI features powered by Anthropic’s Claude API. The Church Assistant is a floating chat widget available to all authenticated users that answers questions about your church — events, service times, groups, contact information, announcements, and bulletins. The Lighthouse AI Support feature guides users through self-service troubleshooting before submitting a formal support request. The AI-assisted worship schedule generator, available to worship coordinators, proposes a service schedule based on your worship team roster and stated availability. In Accounting, a church leader with edit access can choose to have AI read an uploaded receipt or a bank or credit card statement and suggest the details of each entry; every suggestion is shown to that person to review and correct before anything is saved. All AI features operate exclusively on data belonging to your church and are logically isolated — no user can query or receive data from another church through the AI. Church administrators can enable or disable the Church Assistant, AI Support, and AI reading of receipts and statements at any time from the Settings page; the worship schedule generator is invoked only when a worship coordinator actively requests a schedule, and a receipt or statement is read only when a church leader uploads it and asks for it to be read.
Data Accessed by AI Features
When the Church Assistant or AI Support chat is used, a snapshot of your church’s live data is included in the request sent to Anthropic’s API servers. This snapshot may include: upcoming events, active groups and meeting schedules, recent announcements and bulletins, and the church directory (names, membership status, email addresses, and phone numbers for authenticated members). Giving amounts, pastoral care notes, individual attendance details, and prayer request content are excluded from AI context. The Church Assistant provides contact information from the directory to all authenticated church members. When the worship schedule generator is used, the request instead includes the names, assigned roles, and stated availability or blackout dates of your worship team members. When a church leader asks AI to read a receipt or statement in Accounting, the request includes that document (with everything printed on it) and the church’s list of accounting account names, so the AI can suggest a category for each entry. Apart from what is printed on the document itself, the request does not include donor names, individual giving records, or other church data. The Service instructs the AI to report only the last four digits of any card or account number, and masks long card and account numbers in the extracted details it saves. Sensitive pastoral notes are never included in any AI request, and no financial records are sent to AI other than a receipt or statement a church leader chooses to have read.
Third-Party AI Processing — Anthropic
AI features in this Service are powered by Anthropic, PBC (“Anthropic”). When you use an AI feature, your messages and relevant church data context are transmitted to Anthropic’s API for processing. Anthropic processes this data in accordance with its own privacy policy and API usage policies. Anthropic does not use API-submitted data to train its models without explicit consent under its standard API terms. We encourage you to review Anthropic’s privacy policy at anthropic.com/privacy. Church administrators who have concerns about third-party AI processing may disable AI features in Settings. Turning AI features off also turns off AI reading of receipts and statements; Accounting entries can still be typed in or imported from a CSV file.
AI Conversation Storage & Retention
All AI chat conversations — whether resolved by AI or escalated to a human support request — are stored in our Supabase database as feedback records. Stored records include: your messages, AI responses, your name and email, your church name and ID, a timestamp, and whether the issue was resolved by AI or escalated. Super-administrators can view aggregated AI resolution statistics and individual conversation transcripts through the Feedback Admin dashboard. These records are retained as part of your church’s data and are subject to the same deletion rights as other personal records.
Internal Error Diagnostics
When the Service encounters an unexpected technical error, diagnostic information (such as error messages, stack traces, and the name of the affected component) may be logged and, in some cases, sent to Anthropic’s Claude API to generate an automated root-cause suggestion for our engineering team. This diagnostic data is used solely to help us fix bugs and improve the Service, and error logs are visible only to super-administrators through the internal Error Logs dashboard. We take reasonable steps to avoid including sensitive personal data in error diagnostics, but automated error capture cannot guarantee complete exclusion in every case.
Data Storage & Security
Congregation and church data — including people records, giving history, accounting records, attendance, groups, and AI conversation logs — is stored in our primary database, provided by Supabase, which holds SOC 2 Type II and ISO 27001 certifications. Data is encrypted in transit using TLS 1.2+ and at rest using AES-256 encryption. Access is enforced through role-based authentication and database-level Row Level Security (RLS) policies — church admins, group leaders, and members each have distinct, scoped permissions, and these policies prevent any user from reading or writing data outside their authorized church and role. Accounting records are available only to church administrators and the finance team members they designate, and uploaded receipts and statements are kept in private storage and opened only through short-lived links. AI requests, payment processing, and message delivery are all made server-side through Supabase Edge Functions, ensuring that API keys and raw church data are never exposed to the client browser. Google Firebase infrastructure is used only for delivering push notifications and hosting the Service’s public website — it does not store congregation or member data. Our other service providers (Stripe, Twilio, Postmark, and Anthropic) maintain their own industry-standard security certifications, described further under Third-Party Services below. While these controls align with industry best practices, no system is entirely immune to breach and we encourage churches to follow their own data governance policies.
Church Data Responsibility
Each church is responsible for the data it collects and stores within the Service. Church administrators control who has access to their church’s data and whether AI and messaging features are enabled. Perfectly Flawed Designs, LLC acts as a data processor on behalf of each church organization, and uses the following subprocessors to operate the Service: Supabase (database, authentication, file storage, and server-side application logic); Stripe (subscription billing and donation payment processing); Anthropic (AI language model processing, when AI features are enabled); Twilio (SMS delivery, when SMS alerts are enabled); Postmark (transactional email delivery); Google (optional Google sign-in authentication, and Firebase push notification delivery and website hosting); and Cloudflare (Turnstile bot verification on login and public forms).
Church Financial Records (Accounting)
Accounting lets a church keep its budget, income and expenses, and supporting documents in the Service. Only church administrators, and the finance team members an administrator adds (with view-only or edit access), can see Accounting; ministry directors, group leaders, and members cannot unless they are added. Gifts recorded in Giving and payments for paid events are included in Accounting as totals by fund, event, and month — finance team members who are not administrators do not see who gave or who paid. Year-end contribution statements, which show each donor’s name and gifts, can be produced only by administrators. Every addition, change, and deletion in Accounting is recorded in a change history that cannot be edited. Receipts and statements uploaded to Accounting are stored privately with the church’s records and are subject to the same retention and deletion terms as the church’s other data.
Data Retention
While a church’s subscription is active, its data is retained for as long as the church continues using the Service. If a church’s free trial ends without a subscription, or its paid subscription is cancelled, the church moves to the free plan and is deactivated rather than deleted — there is no self-service “delete this church” feature. On the free plan, the church’s People directory (people and family records, photos, and user profiles) remains available to the church and is retained for as long as the church continues using it. The church’s other data — including giving history, accounting records, attendance, groups, events, and related records — is retained but not accessible until the church subscribes again. Perfectly Flawed Designs, LLC reserves the right to retain that other data for up to thirty-six (36) months following deactivation. This retention period supports legitimate purposes, including responding to legal, tax, or regulatory obligations, resolving disputes, preventing fraud, and allowing a church to recover its full history if it resubscribes within that window. During this period, a deactivated church’s data remains subject to the same access controls and security measures described elsewhere in this Privacy Policy, and is not accessible to other churches. After the retention period expires, or sooner at our discretion, data outside the People directory is permanently deleted from our production systems, except where a longer retention period is required by applicable law (for example, certain tax or financial recordkeeping requirements) or where records have already been anonymized (see Data Storage & Security). If a free-plan church has no account activity for thirty-six (36) consecutive months, we may also permanently delete its People directory. A church may request deletion of any of its data, including its People directory, at any time by contacting support@lighthousechrm.com, subject to any records we are legally required to retain.
Payment Processing — Stripe
The Service uses Stripe, Inc. to process all payments, including church subscription billing and congregation giving/donations. We never receive or store your full credit card or bank account number — that information is collected directly by Stripe, which is certified PCI DSS Level 1, the highest level of payment card industry certification. When a church accepts donations through the Service, donation funds are routed to that church’s own Stripe Connect account, which the church controls directly; Perfectly Flawed Designs, LLC does not hold or have access to donated funds. Subscription payments for use of the Service are billed directly to the church’s payment method on file with Stripe. Review Stripe’s privacy policy at stripe.com/privacy for details on how Stripe handles payment data.
Church Directory & Contact Information
When the Church Assistant AI feature is enabled, all authenticated members of a church may ask the AI for contact information — such as a phone number or email address — for other members listed in the church directory. This is equivalent to providing members access to a shared congregational directory. Church administrators should inform their congregation that directory contact information is accessible through the AI assistant and obtain any consent required by their internal policies before enabling this feature. Administrators may disable the AI feature at any time if they prefer to restrict directory access.
Third-Party Services
The Service integrates with the following third-party providers, each with their own privacy and security practices: Supabase (primary database, authentication, file storage, real-time updates, and server-side application logic — review Supabase’s privacy policy at supabase.com/privacy); Stripe (subscription billing and giving/donation payment processing, including Stripe Connect payouts to each church’s own account — review Stripe’s privacy policy at stripe.com/privacy); Anthropic (AI language model processing for the Church Assistant, AI Support chat, AI-assisted worship schedule generation, AI reading of receipts and statements in Accounting, and internal error diagnostics — review Anthropic’s privacy policy at anthropic.com/privacy); Twilio (delivery of optional SMS alerts and processing of SMS opt-out requests — review Twilio’s privacy policy at twilio.com/legal/privacy); Postmark (delivery of transactional emails, including account emails, giving receipts, invitations, RSVP confirmations, and support correspondence — review Postmark’s privacy policy at postmarkapp.com/privacy-policy); Google (optional “Sign in with Google” authentication, which shares your Google account’s name and email with us to create or log into your account — review Google’s privacy policy at policies.google.com/privacy — and separately, Google Firebase for delivery of browser/device push notifications and hosting of the Service’s public website only; Firebase does not store congregation or member data); and Cloudflare (Turnstile, a bot-verification challenge used on the login and public registration/RSVP forms to block automated abuse — review Cloudflare’s privacy policy at cloudflare.com/privacypolicy). We encourage you to review the privacy policies of each provider.
Congregation Member Rights
Congregation members can access and correct most of their own personal information directly from their Profile page, and can self-service export a copy of their own data or request deletion of their own account from the “My Data” section there — see Self-Service Data Export & Deletion below for exactly what that deletion does. For information a member cannot edit themselves, or for records about someone else (e.g. a minor in their household), contact your church administrator. Church administrators may contact us at support@lighthousechrm.com for assistance.
Self-Service Data Export & Deletion
From the “My Data” section of your Profile, you can export a copy of your own account and person record, or request deletion. Requesting deletion unlinks your login from your church’s person record and permanently clears personally identifying fields on it — including your email, phone number, address, notes, and birthday — along with corresponding fields on your giving records, and then deletes your login account. It does not delete the underlying person or giving records themselves, or history such as attendance and giving amounts already recorded against them: churches are permitted to retain ministry and financial records for their own recordkeeping, tax, and continuity purposes even after a member’s login is removed. If you want those underlying records fully removed as well, contact your church administrator, who can delete individual records directly, or contact us at support@lighthousechrm.com.
Children’s Privacy — User Accounts
Login accounts for the Service are intended for individuals who are at least 13 years of age, consistent with the U.S. Children’s Online Privacy Protection Act (COPPA) and analogous regulations worldwide. Perfectly Flawed Designs, LLC does not knowingly collect personal information directly from children under 13 through account registration. Church administrators are responsible for ensuring that only age-eligible individuals are granted login credentials. AI features should not be enabled for accounts belonging to individuals under 13.
Church-Managed Records for Minors
Churches routinely maintain records for members of all ages — including children in youth programs, Sunday school, Vacation Bible School, and similar ministries. Church administrators may enter and manage records for individuals of any age within the Service. In this context, the church acts as the data controller and Perfectly Flawed Designs, LLC acts solely as a data processor. All minor data entered into the Service is managed by authorized church staff, not collected directly from the children themselves. Note that when AI features are enabled, the church directory — which may include records of minors — is included in the AI context. Churches should consider whether this is appropriate before enabling AI features.
Parental / Guardian Consent
Churches are responsible for obtaining appropriate written parental or guardian consent before collecting, storing, or processing personal information about individuals under 18 (or the applicable age of majority in their jurisdiction). This responsibility extends to names, birthdates, contact details, photos, attendance records, and any other identifying information. This is not merely a recommendation — the Service technically enforces it: a minor’s record cannot be created or updated unless a staff member has affirmatively confirmed consent, and the Service stores who confirmed it and when as part of that person’s record. If a parent or guardian believes their child’s information has been stored without appropriate consent, they should contact their church administrator directly or reach us at support@lighthousechrm.com.
Minor Data Protection Standards
Records for minors are protected by the same security controls that apply to all data in the Service — AES-256 encryption at rest, TLS 1.2+ in transit, and role-based Supabase Row Level Security (RLS) policies that prevent unauthorized access — plus a dedicated name- and contact-masking system specific to minors: a church administrator can flag a minor’s record as protected, which hides that child’s name and contact information throughout the Service (including from AI features, where it is rendered only as “Name protected”) from everyone except administrators, the child’s own household head or spouse, and the child’s own account, if one exists. These controls align with the data protection principles of COPPA (16 C.F.R. Part 312), GDPR Article 8 (parental consent for under-16 processing), and CCPA Section 1798.120 (opt-out rights for minors under 16). Churches operating in the European Union or the United Kingdom should additionally ensure their use of the Service complies with applicable GDPR or UK GDPR obligations regarding the processing of children’s personal data.
Data Minimization for Minors
We recommend that churches collect only the minimum personal information necessary to support their ministry activities involving minors. The Service is designed to support this principle — fields for sensitive details are optional, and administrators control which information is recorded for each individual. Avoid storing sensitive medical, behavioral, or disciplinary information about minors unless it is strictly necessary and appropriate consent and security controls are in place.
Access Controls for Minor Data
Access to congregation records — including records involving minors — is limited to authorized users within each church based on their assigned role. Church administrators should periodically review which staff members have access to the Service and remove access for individuals who no longer need it. Role assignments and access should follow the principle of least privilege: group leaders and volunteers should have access only to the specific groups and records relevant to their ministry responsibilities.
Minor’s Right to Deletion
Parents or legal guardians may request the deletion of a minor’s personal data at any time by contacting their church administrator. Church administrators can delete individual records directly within the Service. If you need assistance or if a church is unresponsive, please contact Perfectly Flawed Designs, LLC at support@lighthousechrm.com and we will work with the church to facilitate the request.
Email Communications
The Service sends transactional emails — including giving receipts, user invitation emails, account/authentication emails, and support correspondence — delivered through our email service provider, Postmark. These are sent only in response to actions you or your administrator initiate. We do not send unsolicited marketing or promotional emails on our own behalf. Email addresses collected in the Service are used solely to operate the Service and are not shared with third parties for marketing purposes. To stop receiving a particular type of transactional email, adjust your preferences in your profile or contact your church administrator. We comply with the CAN-SPAM Act: each email includes accurate sender identification and an opt-out or unsubscribe mechanism. Separately, your church’s administrators and directors can use the Service’s Communications tool to compose and send their own email messages to some or all of the congregation directory (also delivered via Postmark) — this is content sent by your church, not by us, and your church is responsible for the content and recipients of those messages.
SMS Communications & TCPA
The Service provides an optional SMS alert feature (e.g., urgent prayer request notifications and group messages), delivered through our SMS service provider, Twilio. SMS alerts are strictly opt-in. When you enable SMS alerts, you provide your mobile phone number and consent to receive text messages from the Service. This constitutes prior express written consent as required by the Telephone Consumer Protection Act (47 U.S.C. § 227) and FCC regulations. Message frequency varies. Standard message and data rates may apply. You may opt out at any time by replying STOP to any message or disabling SMS alerts in your profile; STOP, START, and HELP keyword requests are processed automatically through Twilio’s messaging infrastructure. We store your mobile number securely in our Supabase database, associated with your user record, for the sole purpose of delivering SMS alerts you have opted into. Mobile numbers are never shared with third parties for marketing purposes. We do not guarantee SMS delivery; delivery depends on your carrier and network conditions. Church administrators are responsible for ensuring that SMS features are used in compliance with applicable telecommunications laws and that member consent records are maintained, including when using the Service’s Communications tool to send a bulk text message to some or all of the congregation directory — that message content and the consent basis for it is your church’s responsibility, not ours. Separately, when a child is checked in to a church program, Check-In staff or Group Leaders may send a one-off text to the emergency contact number on file for that check-in (e.g. a pickup notice). That number is provided by church staff at check-in time, not by the recipient opting in through their own profile — it is an operational safety communication tied to the child’s active check-in, not an SMS-alerts subscription, and this section’s opt-in/STOP mechanism does not apply to it.
Push Notification Data
When you grant notification permission and subscribe to push alerts, the Service registers a Firebase Cloud Messaging (FCM) device token for your browser or device. This token is stored securely in our Supabase database, associated with your user account and church, and is used solely to deliver push notifications you have opted into. FCM tokens are not sold or shared with third parties. Stale or invalid tokens are periodically cleaned from our database. You may withdraw push notification consent at any time by revoking browser or device notification permissions, or by using the Unsubscribe button on the relevant page. Withdrawing consent removes your token from active use for that notification type.
Passkey (Biometric) Sign-In
The Service offers an optional passwordless sign-in method using passkeys (the WebAuthn standard), which may rely on your device’s fingerprint or face unlock. Your fingerprint, face scan, or other biometric data is captured and matched entirely on your own device by your device’s operating system — it is never transmitted to us, never sent to Anthropic, and never stored on our servers. We store only a non-reversible public-key credential identifier associated with your account, used solely to verify sign-in requests. You may register or remove a passkey at any time from your Profile settings.
Cookies, Local Storage & Offline Data
We use cookies and browser local storage for authentication session management — keeping you signed in and identifying your church and role on each request. We do not use third-party advertising or analytics tracking cookies. The Performance Mode feature additionally caches sheet music charts and queues in-progress annotations in your browser’s local storage (IndexedDB) so worship leaders can keep using charts during a temporary loss of internet connectivity; queued annotations are synced to our Supabase database automatically once connectivity is restored. You can configure your browser to refuse cookies or clear local storage, though this may affect Service functionality, including staying signed in and offline availability.
Legal Compliance
Churches using this Service are responsible for compliance with all applicable data protection laws in their jurisdiction, including but not limited to GDPR, CCPA, and other regional privacy regulations. When AI features are enabled and church member data is included in AI requests, churches should evaluate whether additional consent, disclosure, or data processing agreements are required under their applicable law. Perfectly Flawed Designs, LLC does not provide legal advice.
Changes to This Policy
We may update this Privacy Policy from time to time. Continued use of the Service after changes are posted constitutes acceptance of the updated policy.
Contact Us
For privacy-related questions or concerns, contact Perfectly Flawed Designs, LLC at support@lighthousechrm.com.