Privacy Policy

Effective Date: August 28, 2026

ChurchTrakr LLC (“ChurchTrakr,” “we,” “us,” or “our”) respects the privacy of our customers and the individuals whose information is processed through ChurchTrakr.

This Privacy Policy describes how ChurchTrakr collects, uses, processes, discloses, protects, retains, and deletes information in connection with the ChurchTrakr websites, software platform, applications, church portals, and related services collectively referred to as the “Services.”

ChurchTrakr provides church management software to churches, ministries, and other organizations referred to as “Customers.” Because Customers use ChurchTrakr to manage information about their congregations, it is important to distinguish between information ChurchTrakr collects for its own purposes and information ChurchTrakr processes on behalf of a Customer.

1. United States Service

ChurchTrakr is a United States-based service intended for churches and organizations located in the United States.

ChurchTrakr does not currently market or offer its Services to organizations outside the United States.

Information processed through ChurchTrakr may be stored and processed in the United States.

2. ChurchTrakr’s Role

Customers use ChurchTrakr to manage information concerning their churches, ministries, members, attendees, guests, donors, volunteers, staff, children, families, and other individuals.

Information that a Customer enters, imports, collects, creates, or otherwise maintains through ChurchTrakr is referred to in this Privacy Policy as “Customer Data.”

For Customer Data, the Customer generally determines:

Why the information is collected;
What information is maintained;
How the information is used;
Who may access the information;
How long the information is retained; and
Which ChurchTrakr features are enabled.

In those circumstances, ChurchTrakr generally processes Customer Data on behalf of the Customer in order to provide the Services.

For information ChurchTrakr collects for its own business purposes—such as Customer account information, subscription and billing information, payment-platform administration, support requests, security information, and website usage—ChurchTrakr determines how that information is processed.

If you have questions about information a particular church maintains about you through ChurchTrakr, you should ordinarily contact that church directly.

3. Information We Collect and Process

The information ChurchTrakr processes depends upon how the Services are used.

Customer Account Information

When a Customer or authorized user creates or uses a ChurchTrakr account, we may collect or process information including:

Name;
Email address;
Telephone number;
Church or organization name;
Mailing or business address;
Job title or organizational role;
User role and permissions;
Login and authentication information;
Account preferences;
Subscription information;
Billing status;
Payment-service selections;
Connected payment-account identifiers and status;
Communications with ChurchTrakr; and
Other information reasonably necessary to create, maintain, secure, and support the account.

Congregant and Church Records

Customers may use ChurchTrakr to maintain information about members, attendees, guests, donors, volunteers, staff, children, parents, families, and other individuals.

This information may include:

First and last name;
Email address;
Telephone number;
Mailing or residential address;
Photograph or profile image;
Household and family relationships;
Birth date or birthday;
Membership status;
Member-since information;
Attendance records;
Worship service attendance;
Class and group participation;
Event registrations;
Volunteer teams, roles, schedules, and availability;
Check-in information;
Child and family check-in relationships;
Tags and lists;
Forms and form responses;
Communication preferences;
Portal access;
Directory information;
Giving and donation records;
Notes and other information entered by authorized Customer users; and
Other information the Customer chooses to maintain through ChurchTrakr.

The exact information maintained about an individual depends upon how the applicable Customer configures and uses ChurchTrakr.

Payment Account and Onboarding Information

When a Customer enables ChurchTrakr Payments or connects a separate Stripe account to ChurchTrakr, ChurchTrakr may process information relating to the payment connection, including:

Customer organization name;
Business contact information;
Stripe or connected-account identifiers;
Payment-account connection status;
Onboarding status;
Payment capabilities;
Charges-enabled or payments-enabled status;
Payout status;
Verification requirements or outstanding account requirements;
Information about authorized representatives supplied to ChurchTrakr;
Payment-processing settings;
Transaction and settlement information;
Dispute, refund, and chargeback information; and
Payment-related support communications.

Stripe may separately collect additional business, financial, ownership, tax, identity-verification, and payout information as described in Section 14.

4. Information About Children

ChurchTrakr includes functionality that allows Customers to maintain information concerning children for legitimate church purposes such as household records, classes, events, attendance, and child check-in.

ChurchTrakr does not intend for children under 13 to independently create ChurchTrakr portal accounts or directly provide personal information to ChurchTrakr.

ChurchTrakr portal accounts are intended for individuals age 13 or older.

Information concerning children under 13 should be entered or managed by a parent or legal guardian or by authorized personnel of the applicable Customer, as appropriate.

Customers are responsible for determining what information they collect about children and for obtaining any parental or guardian permission required by applicable law.

If ChurchTrakr learns that a child under 13 has independently provided personal information directly to ChurchTrakr contrary to these requirements, we will take reasonable steps to address the information appropriately.

5. Giving and Transaction Information

Customers may use ChurchTrakr to manage charitable contributions, online giving, event payments, registration fees, and related transactions.

ChurchTrakr may process transaction-related information such as:

Donor or payer name;
Email address;
Telephone number;
Billing address;
Donation or payment amount;
Transaction date;
Fund or designation;
Event or registration associated with the transaction;
Transaction status;
Payment-method type;
Recurring-giving information;
Payment schedule;
Payment-processor and transaction identifiers;
Limited payment-method details;
Refund information;
Dispute or chargeback information;
Giving batch information;
Processor fees and net amounts;
Payout or settlement status; and
Other accounting information associated with the transaction.

Payment processing is provided through Stripe and Stripe Connect.

Depending upon the payment arrangement selected by the Customer, transactions may be processed through:

ChurchTrakr Payments, which is ChurchTrakr’s integrated card-payment service powered by Stripe Connect; or
A separate Stripe account that the Customer already owns or creates through an onboarding process made available from within ChurchTrakr and then connects to ChurchTrakr through Stripe Connect.

ChurchTrakr Payments currently supports card payments. ACH bank payments are not currently offered through ChurchTrakr Payments.

A Customer that wishes to accept ACH bank payments must connect a separate Stripe account that it owns or create its own Stripe account through the Stripe onboarding process made available through ChurchTrakr.

Sensitive payment credentials are generally submitted directly to Stripe through Stripe-hosted or Stripe-provided payment interfaces. ChurchTrakr’s Services are not designed to receive or store complete payment-card numbers, card security codes, complete bank account or routing numbers, or bank login credentials.

ChurchTrakr may receive limited or tokenized payment-method information from Stripe, such as:

Payment-method identifiers;
Card brand;
Card expiration information;
The last four digits of a card or bank account;
Bank name;
Bank-account type;
Payment status;
Verification status; and
Information reasonably necessary to maintain transaction records and provide support.

6. Information Collected Through the Church Portal

Individuals may interact with ChurchTrakr through a portal made available by their church.

Depending upon the features enabled by the church, portal users may be able to:

Create or access a portal account;
Update profile information;
View or manage directory information;
Make donations;
Review giving information;
Register for events;
Submit forms;
View groups or classes;
Manage volunteer schedules;
Submit volunteer blockout dates;
View church information; and
Use other features made available by their church.

Information submitted through a church portal is generally processed on behalf of the church providing that portal.

When a portal user makes a donation or other payment, certain information may be provided to Stripe for payment processing as described in Sections 5 and 14.

7. Church Directory Information

A Customer may choose to enable a church directory through its ChurchTrakr portal.

Participation in the directory is not intended to make an individual’s information publicly available on the Internet.

Where directory functionality is enabled, the applicable church determines who may be eligible to participate, and eligible individuals may be given choices regarding the information they share.

Depending upon available settings, an individual may choose whether to share information such as:

Profile photograph;
Email address;
Mobile telephone number;
Address;
Birthday; and
Other available directory information.

ChurchTrakr processes directory information in accordance with the applicable Customer’s configuration and the individual’s available privacy choices.

8. Technical and Usage Information

When individuals use ChurchTrakr, we may automatically collect technical information such as:

IP address;
Browser type;
Device type;
Operating system;
Login activity;
Date and time of access;
Pages or features accessed;
Application events;
Error and diagnostic information;
Security events; and
Application performance information.

We use this information to operate, secure, troubleshoot, maintain, and improve ChurchTrakr.

Stripe and other providers may also collect technical information when their hosted, embedded, or integrated services are used.

9. Cookies and Similar Technologies

ChurchTrakr websites and applications may use cookies and similar technologies necessary to provide functionality such as:

Authentication;
Session management;
Security;
User preferences;
Application functionality;
Payment functionality;
Performance monitoring; and
Fraud prevention.

ChurchTrakr may also use reasonable website analytics to understand how our public website and Services are used.

We do not use church member, donor, child, giving, or Customer Data to create advertising profiles for unrelated third-party advertisers.

Third-party services embedded in or linked from ChurchTrakr, including Stripe, may use their own cookies or similar technologies in accordance with their own privacy policies.

10. How We Use Information

ChurchTrakr may use information as reasonably necessary to:

Provide and operate the Services;
Create and maintain accounts;
Authenticate users;
Maintain Customer records;
Provide church portals;
Process giving-related functionality;
Facilitate card and ACH payments;
Enable and administer Stripe Connect relationships;
Support payment-account onboarding;
Display payment-account, onboarding, verification, or capability status;
Record transactions;
Manage recurring giving;
Facilitate refunds;
Support payment disputes and chargebacks;
Reconcile transactions and payouts;
Deliver email communications;
Deliver SMS communications;
Manage attendance and check-in;
Support events, classes, groups, and volunteers;
Operate workflows and automation;
Provide reports;
Provide requested integrations;
Process subscriptions and billing;
Provide customer support;
Diagnose and correct technical problems;
Monitor application performance;
Protect accounts and information;
Detect and prevent fraud, abuse, and security threats;
Maintain and improve ChurchTrakr;
Develop new functionality;
Communicate with Customers about their accounts and the Services; and
Comply with applicable legal, financial, contractual, and regulatory requirements.

11. Email Communications and Resend

ChurchTrakr may use Resend or other email-delivery providers to deliver account communications, transactional email, and messages initiated by Customers.

Information processed for email delivery may include:

Recipient email address;
Sender information;
Message content;
Delivery status;
Bounce information; and
Other technical information necessary to provide email delivery.

Email providers process this information as necessary to deliver and support the requested communications.

12. SMS/Text Messaging and Twilio

ChurchTrakr may use Twilio or another telecommunications provider to provide toll-free SMS/text messaging functionality.

When SMS functionality is used, ChurchTrakr and its telecommunications providers may process:

Mobile telephone numbers;
Message content;
Sender information;
Opt-in and consent information;
Opt-out information;
Delivery status;
Message timestamps; and
Other technical information necessary to provide messaging.

Customers are responsible for obtaining appropriate consent before sending SMS communications and for complying with applicable messaging requirements.

Where applicable:

Message frequency may vary.
Message and data rates may apply.
Recipients may reply STOP to opt out of further messages.
Recipients may reply HELP for assistance.
Consent to receive SMS communications is not a condition of purchasing ChurchTrakr or making a donation.
Wireless carriers are not liable for delayed or undelivered messages.

SMS Privacy

Mobile information will not be sold or shared with third parties or affiliates for their marketing or promotional purposes.

SMS opt-in data and consent will not be sold or shared with third parties or affiliates for their marketing or promotional purposes.

Information may be provided to service providers, including telecommunications providers such as Twilio, solely as reasonably necessary to deliver and support SMS communications and related functionality.

This restriction does not prevent ChurchTrakr from disclosing information when required by law or from using service providers that process information on ChurchTrakr’s behalf to provide the requested messaging service.

13. Toll-Free Messaging Verification

ChurchTrakr’s SMS functionality may use toll-free telephone numbers subject to verification requirements imposed by Twilio, telecommunications carriers, or other messaging providers.

ChurchTrakr may process and provide information necessary to complete such verification, including:

Customer organization information;
Website information;
Messaging use cases;
Expected message volume;
Sample messages;
Opt-in procedures;
Consent information; and
Other information required by the applicable telecommunications provider.

This information is used for messaging compliance, fraud prevention, and operation of the SMS service.

14. Stripe Connect and Payment Processing

ChurchTrakr uses Stripe and Stripe Connect to support Customer subscription billing, ChurchTrakr Payments, Customer-connected Stripe accounts, donations, event payments, registration payments, recurring payments, refunds, disputes, payouts, and related functionality.

Stripe is a separate company that maintains its own privacy, security, identity-verification, fraud-prevention, compliance, and data-retention practices.

ChurchTrakr Subscription Billing

ChurchTrakr may use Stripe to process subscription fees, add-on fees, usage fees, and other amounts paid by Customers directly to ChurchTrakr.

When a Customer pays ChurchTrakr, Stripe may collect and process the payment information necessary to complete the transaction.

ChurchTrakr may receive limited billing information from Stripe, including:

Customer name;
Billing email address;
Billing address;
Subscription status;
Invoice information;
Payment status;
Payment-method type;
Card brand;
Last four digits;
Payment-processor identifiers;
Refund information; and
Failure or dispute information.

ChurchTrakr Payments

ChurchTrakr Payments is ChurchTrakr’s integrated payment service powered by Stripe Connect.

ChurchTrakr Payments currently enables Customers to accept card payments through ChurchTrakr-powered giving pages, registration pages, portals, or other payment functionality.

ChurchTrakr Payments does not currently support ACH bank payments.

To enable ChurchTrakr Payments, a Customer may be required to complete a Stripe Connect onboarding or account-verification process.

When a donor, registrant, or other payer makes a payment using ChurchTrakr Payments, information necessary to complete and record the transaction may be provided to Stripe.

ChurchTrakr may receive and maintain information such as:

Donor or payer name;
Email address;
Telephone number;
Billing address;
Transaction amount;
Transaction date;
Fund or designation;
Event, registration, or other transaction purpose;
Transaction status;
Payment-method type;
Card brand;
Last four digits of the card;
Card expiration information;
Payment-method identifier;
Stripe customer or transaction identifier;
Recurring-payment identifiers and schedules;
Refund information;
Dispute or chargeback information;
Processor fees;
Application or platform fee information;
Net transaction amount;
Payout or settlement information; and
Information needed for receipts, reconciliation, accounting, fraud prevention, and support.

Customer-Connected Stripe Accounts and ACH

A Customer that wishes to accept ACH bank payments must use a separate Stripe account that the Customer owns.

The Customer may:

Connect an existing Stripe account to ChurchTrakr; or
Create its own Stripe account through a Stripe onboarding process launched from within ChurchTrakr.

ChurchTrakr uses Stripe Connect to connect the Customer’s Stripe account with ChurchTrakr and provide the requested payment functionality.

The Customer maintains a separate relationship with Stripe and is responsible for its Stripe account, including:

Information provided to Stripe;
Payment methods enabled within the account;
Merchant and business information;
Account representatives;
Identity-verification requirements;
Tax information;
Payout settings;
Bank accounts used to receive payouts;
Stripe fees;
Disputes and chargebacks;
Refunds;
Account security; and
Compliance with the terms and requirements applicable to the Stripe account.

When authorized by the Customer, ChurchTrakr may exchange information with Stripe as reasonably necessary to:

Establish the Stripe Connect relationship;
Identify the connected Stripe account;
Display onboarding or connection status;
Display verification requirements;
Determine whether payments or payouts are enabled;
Initiate or record authorized transactions;
Maintain giving and transaction records;
Manage recurring payments;
Process or record refunds;
Receive payment-success or payment-failure information;
Receive dispute or chargeback information;
Receive payout or settlement information;
Reconcile ChurchTrakr records with Stripe records;
Provide financial reports;
Provide payment-related support; and
Troubleshoot integration or payment errors.

ACH availability is determined by Stripe and depends upon the Customer’s Stripe account, eligibility, payment settings, verification status, and compliance with Stripe’s requirements.

Stripe Account Onboarding and Verification

When a Customer enables ChurchTrakr Payments, connects an existing Stripe account, or creates a Stripe account through ChurchTrakr, Stripe may collect information about the Customer organization and its owners, officers, representatives, or other associated individuals.

Depending upon Stripe’s requirements and the payment arrangement selected, this information may include:

Legal organization name;
Doing-business-as name;
Organization type;
Business or mailing address;
Website address;
Email address;
Telephone number;
Tax identification information;
Business registration information;
Information about owners, officers, directors, executives, or authorized representatives;
Names;
Residential addresses;
Dates of birth;
Personal identification information;
Government-issued identification;
Proof-of-address documentation;
Ownership or control information;
Bank account information used to receive payouts;
Information used to verify ownership of a payout account; and
Other information required by Stripe for underwriting, identity verification, fraud prevention, payment processing, legal compliance, or account administration.

Information entered into Stripe-hosted or Stripe-provided onboarding interfaces is submitted to Stripe.

ChurchTrakr may receive Stripe account identifiers, business profile information, onboarding status, verification status, capability status, outstanding requirements, payment status, payout status, and other information made available through the authorized Stripe Connect relationship.

The exact information available to ChurchTrakr depends upon the Stripe account configuration, permissions, payment arrangement, and Stripe’s current products and requirements.

Payment Credentials

Complete card numbers, card security codes, complete bank account and routing numbers, and bank login credentials are generally collected directly by Stripe or through Stripe-provided interfaces and are not intended to be stored by ChurchTrakr.

ChurchTrakr may receive limited or tokenized information, such as:

Payment-method identifier;
Card brand;
Card expiration date;
Last four digits of a card;
Bank name;
Bank-account type;
Last four digits of a bank account;
Payment verification status;
Payment status; and
Information reasonably necessary to identify and support a transaction.

A token, payment-method identifier, or limited payment description does not contain the complete payment credentials needed to independently access the payment account.

ACH Bank Information and Authorization

When a payer uses ACH, Stripe may collect bank account information and may provide methods for verifying the bank account.

Depending upon the payment experience selected by the applicable Customer and made available by Stripe, bank verification may involve:

A bank-login or authorization flow;
Account and routing information;
Tokenized bank-account information;
Microdeposit verification; or
Another verification method provided by Stripe.

ACH payments require authorization from the bank-account holder.

Stripe may collect and retain information relating to that authorization, which may include:

Whether the authorization is for a one-time or recurring payment;
Date and time of acceptance;
Internet Protocol address;
Browser or device information;
User agent;
Mandate or authorization identifier; and
Other information necessary to document the authorization.

ChurchTrakr may receive information indicating that an ACH payment method was authorized or verified, together with limited payment-method and transaction information made available by Stripe.

Payment Recipients, Payouts, and Settlement

Stripe may process payouts or settlement transfers to a bank account designated by the Customer.

ChurchTrakr may receive information such as:

Payout amount;
Payout date;
Payout status;
Settlement status;
Related transaction identifiers;
Fee information;
Failure information; and
Limited information identifying the payout destination.

ChurchTrakr does not control the independent practices of the Customer’s bank or other financial institution.

Refunds, Disputes, and Chargebacks

When a payment is refunded, disputed, reversed, or charged back, ChurchTrakr and Stripe may process information necessary to:

Identify the transaction;
Communicate with the Customer;
Process or record the refund;
Respond to or document a dispute;
Provide transaction records;
Prevent fraud or abuse;
Reconcile payment records; and
Meet legal, contractual, or payment-network requirements.

This information may include transaction details, payer contact information, payment status, correspondence, supporting documentation, dispute reason, and resolution status.

Stripe’s Independent Processing

Stripe may process information for its own purposes, including:

Providing payment services;
Maintaining Stripe accounts;
Verifying identities and businesses;
Underwriting accounts;
Processing payments and payouts;
Preventing fraud and abuse;
Detecting security threats;
Managing disputes and chargebacks;
Complying with laws and financial regulations;
Enforcing Stripe agreements; and
Improving Stripe’s services.

Stripe’s independent processing is governed by Stripe’s own terms and privacy practices.

Individuals and Customers should review the Stripe Privacy Policy available from Stripe for additional information about Stripe’s processing.

Disconnecting a Customer Stripe Account

A Customer may disconnect its Stripe account from ChurchTrakr through functionality made available by ChurchTrakr or Stripe.

Disconnecting the account prevents ChurchTrakr from making new requests through the disconnected authorization, except where limited continued access is permitted or required for pending transactions, disputes, refunds, accounting, security, fraud prevention, or legal compliance.

Disconnecting a Stripe account does not automatically delete:

Giving records maintained in ChurchTrakr;
Transaction records;
Refund records;
Dispute or chargeback records;
Accounting information;
Records previously transmitted to Stripe;
Records independently maintained by Stripe; or
Information required for legal, financial, fraud-prevention, security, or recordkeeping purposes.

Information previously recorded in ChurchTrakr remains subject to the retention and deletion provisions of this Privacy Policy.

15. Intuit and QuickBooks Online

ChurchTrakr may provide Customers with an optional integration with Intuit QuickBooks Online.

A Customer must affirmatively authorize the connection between ChurchTrakr and its QuickBooks Online account through Intuit’s authorization process.

ChurchTrakr will access QuickBooks information only within the permissions authorized by the Customer.

How ChurchTrakr Uses QuickBooks Information

The ChurchTrakr integration may allow a Customer to transmit financial or accounting information from ChurchTrakr to QuickBooks Online.

For example, a Customer may choose to send information associated with a closed ChurchTrakr giving batch to QuickBooks Online for accounting purposes.

Depending upon the functionality enabled, ChurchTrakr may process information necessary to:

Authenticate the QuickBooks connection;
Identify the Customer’s QuickBooks company;
Map ChurchTrakr accounting information to QuickBooks;
Create or synchronize authorized accounting records;
Determine whether an authorized transfer succeeded;
Display synchronization status;
Troubleshoot integration errors; and
Maintain the requested integration.

ChurchTrakr does not use QuickBooks information for advertising.

ChurchTrakr does not sell QuickBooks information.

ChurchTrakr does not provide unrelated third parties access to QuickBooks information for their independent purposes.

Information obtained through Intuit is used only as reasonably necessary to provide, maintain, secure, troubleshoot, or support the functionality requested by the Customer, subject to applicable Intuit requirements.

Disconnecting QuickBooks

Customers may disconnect their QuickBooks Online integration through functionality made available by ChurchTrakr or Intuit.

Disconnecting the integration prevents ChurchTrakr from making future requests through the revoked Intuit authorization, except as otherwise permitted or required by Intuit or applicable law.

Information previously transferred between systems may remain in the system to which it was transferred.

16. Service Providers

ChurchTrakr uses third-party service providers to operate the Services.

These providers may provide services such as:

Cloud hosting;
Data storage;
Payment processing;
Stripe Connect services;
Merchant and connected-account onboarding;
Identity verification;
Fraud prevention;
Payment-method verification;
Payout and settlement processing;
Email delivery;
SMS delivery;
Telecommunications;
Authentication;
Application monitoring;
Security;
Error reporting;
Customer support; and
Accounting integrations.

Service providers may process information only as reasonably necessary for the services they provide to ChurchTrakr, subject to applicable contractual and legal requirements.

Certain providers, including payment processors and financial institutions, may also process information independently under their own terms, legal obligations, and privacy policies.

17. When We Disclose Information

ChurchTrakr may disclose information:

To service providers that help operate ChurchTrakr;
To Stripe and other payment processors;
To payment networks, banks, financial institutions, or payment-method providers as reasonably necessary to complete or support a transaction;
At the direction of the applicable Customer;
When requested or authorized by the individual;
To establish or maintain an integration requested by a Customer;
To provide a transaction, communication, payment, payout, or integration requested through the Services;
To support account onboarding, identity verification, fraud prevention, or payment compliance;
To process refunds, disputes, reversals, or chargebacks;
To protect ChurchTrakr, Customers, users, or others from fraud, abuse, security threats, or unlawful activity;
When reasonably necessary to enforce our agreements;
When required by law, subpoena, court order, or other valid legal process; or
In connection with a merger, acquisition, financing, restructuring, sale of assets, or similar corporate transaction, subject to applicable legal requirements.

18. We Do Not Sell Personal Information

ChurchTrakr does not sell personal information to data brokers or advertisers.

ChurchTrakr does not sell or use church member, attendee, donor, volunteer, child, family, or Customer Data for unrelated third-party advertising.

ChurchTrakr does not sell SMS opt-in or consent information.

Providing information to Stripe, a bank, a payment network, a telecommunications provider, or another service provider in order to provide a requested transaction or service is not a sale of personal information.

19. Customer Responsibility for Congregant Information

Each Customer is responsible for determining:

What information it collects;
Why it collects that information;
Who within its organization may access it;
How long the Customer needs the information;
Which ChurchTrakr features it enables;
What communications it sends;
Which payment arrangement it selects;
Which payment methods it enables;
Whether it connects an existing Stripe account or creates a new Stripe account;
What notices it provides to donors, registrants, members, or other payers;
Whether it has obtained any consent or authorization required for recurring payments or ACH transactions; and
Whether its use of ChurchTrakr, Stripe, messaging, giving, and other functionality complies with applicable law and the Customer’s own policies.

ChurchTrakr provides the technology used by the Customer but does not independently determine the church’s ministry, membership, giving, attendance, volunteer, pastoral, payment, or other recordkeeping practices.

20. Accessing, Correcting, or Deleting Congregant Information

If ChurchTrakr maintains information about you on behalf of a church or other Customer, requests to access, correct, update, or delete that information should generally be directed to that Customer.

For example, if your church maintains your address, household information, giving records, or attendance information in ChurchTrakr, you should normally contact your church regarding changes to those records.

ChurchTrakr may assist Customers with appropriate requests when reasonably necessary.

Requests concerning information ChurchTrakr maintains directly about a ChurchTrakr Customer account may be sent to ChurchTrakr using the contact information below.

Requests concerning information maintained independently by Stripe should be directed to Stripe or handled through the applicable Stripe account or payment process.

21. Data Retention

ChurchTrakr retains information for as long as reasonably necessary to:

Provide the Services;
Maintain Customer accounts;
Fulfill the purposes described in this Privacy Policy;
Process or document transactions;
Maintain giving, accounting, and financial records;
Support refunds, disputes, and chargebacks;
Maintain security;
Prevent fraud and abuse;
Maintain appropriate business and financial records;
Resolve disputes;
Enforce agreements; and
Comply with legal obligations.

Retention periods may differ depending upon the type of information and the purpose for which it is processed.

Customer Data is generally retained while the applicable Customer maintains an active ChurchTrakr account.

Transaction, giving, subscription, payment, refund, dispute, payout, accounting, tax, fraud-prevention, and security records may be retained after a payment account is disconnected or after a particular transaction is completed.

Stripe independently determines how long Stripe retains information under Stripe’s own terms, legal obligations, and privacy practices.

22. Account Closure and Data Deletion

When a Customer closes its ChurchTrakr account, the Customer should export information it wishes to retain before closure.

Following account termination, ChurchTrakr may maintain Customer Data for a limited period to allow for ordinary account recovery, backup processing, security, fraud prevention, dispute resolution, financial recordkeeping, and legal compliance.

After the applicable retention period, Customer Data will be deleted or anonymized unless continued retention is required or permitted by law.

Information stored in backups may remain until those backups are overwritten or deleted through ChurchTrakr’s ordinary backup cycle.

Certain records may be retained longer when reasonably necessary for:

Financial and accounting obligations;
Payment reconciliation;
Refunds;
Disputes and chargebacks;
Fraud prevention;
Security;
Legal compliance;
Enforcement of agreements; or
Establishment, exercise, or defense of legal claims.

Closing a ChurchTrakr account does not automatically close or delete a Customer’s separate Stripe account.

Customers are responsible for managing or closing their Stripe accounts through Stripe.

23. Intuit Data Retention and Deletion

Information obtained through the Intuit or QuickBooks integration will be retained only as reasonably necessary to provide the integration and related ChurchTrakr functionality or as otherwise permitted by applicable Intuit requirements and law.

When a Customer disconnects QuickBooks or closes its ChurchTrakr account, ChurchTrakr will cease obtaining new information through the revoked connection.

ChurchTrakr will delete or anonymize Intuit-derived information that is no longer reasonably necessary for the authorized integration, subject to legitimate backup, security, accounting, fraud-prevention, and legal-retention requirements.

Information that originated in ChurchTrakr and was transmitted to QuickBooks remains subject to the Customer’s QuickBooks account and Intuit’s practices.

24. Data Security

ChurchTrakr uses reasonable administrative, technical, and organizational safeguards intended to protect information against unauthorized access, loss, misuse, alteration, or disclosure.

Safeguards may include measures such as:

Authentication;
Access controls;
Role-based permissions;
Encryption of data in transit;
Infrastructure security;
Application monitoring;
Logging;
Backups; and
Security practices appropriate to the nature of the Services.

No Internet-connected system can guarantee absolute security.

Customers are also responsible for maintaining appropriate passwords, account permissions, devices, administrative procedures, Stripe account controls, and other safeguards within their control.

Payment information submitted directly to Stripe is protected according to Stripe’s security practices and obligations.

25. Security Incidents

If ChurchTrakr becomes aware of a security incident affecting Customer Data, ChurchTrakr will investigate and respond as reasonably appropriate under the circumstances.

Where required by applicable law or contractual obligation, ChurchTrakr will provide appropriate notification to affected Customers or individuals.

Security incidents involving information maintained independently by Stripe or another third-party provider may also be handled under that provider’s incident-response and notification practices.

26. Business Transfers

If ChurchTrakr is involved in a merger, acquisition, financing, reorganization, sale of assets, or similar business transaction, information may be transferred as part of that transaction.

Any successor that receives personal information as part of such a transaction will be expected to handle that information in accordance with applicable law and the privacy commitments applicable to the information.

27. Legal Requests and Protection of Rights

ChurchTrakr may preserve, access, or disclose information when we reasonably believe doing so is necessary to:

Comply with applicable law, regulation, subpoena, court order, or other valid legal process;
Respond to lawful requests from governmental authorities;
Comply with payment, financial, tax, accounting, fraud-prevention, or recordkeeping obligations;
Protect the rights, property, or safety of ChurchTrakr, our Customers, users, or others;
Investigate or prevent fraud, abuse, security incidents, or unlawful activity;
Enforce our agreements and policies; or
Establish, exercise, or defend legal claims.

Where legally permitted and reasonably appropriate, ChurchTrakr may direct a request concerning Customer Data to the Customer that controls the information.

28. Privacy Rights

Depending upon applicable law and the nature of ChurchTrakr’s relationship with you, you may have rights regarding your personal information.

These rights may include the ability to request:

Access to personal information;
Correction of inaccurate personal information;
Deletion of certain personal information; or
Information concerning how personal information is processed.

When ChurchTrakr processes information on behalf of a Customer, such as a church, the Customer generally controls the information.

If you are a member, attendee, guest, donor, volunteer, parent, or other individual whose information is maintained in ChurchTrakr by a church, you should generally submit your privacy request directly to that church.

ChurchTrakr will reasonably assist Customers in responding to appropriate privacy requests when required.

If your request concerns information ChurchTrakr maintains directly about you for ChurchTrakr’s own purposes, you may contact us using the information at the end of this Privacy Policy.

We may need to verify your identity before fulfilling certain requests.

Certain financial, transaction, tax, security, fraud-prevention, dispute, or legal records may not be eligible for deletion when continued retention is permitted or required by law.

29. California and Other State Privacy Laws

Residents of certain U.S. states may have additional privacy rights under applicable state law.

The availability and scope of those rights depend upon factors including:

The state in which the individual resides;
The nature of the information;
ChurchTrakr’s role in processing the information;
The Customer’s role in processing the information;
Whether an applicable statutory exemption applies; and
Whether applicable statutory thresholds are met.

ChurchTrakr will respond to legally valid privacy requests as required by applicable law.

ChurchTrakr does not sell personal information to data brokers or advertisers.

ChurchTrakr does not sell or share personal information for cross-context behavioral advertising.

30. Do Not Track and Targeted Advertising

ChurchTrakr does not use Customer Data concerning church members, attendees, donors, volunteers, children, or families for behavioral advertising.

Because ChurchTrakr does not use such Customer Data for cross-site behavioral advertising, browser “Do Not Track” signals do not alter the processing of Customer Data within the ChurchTrakr application.

If ChurchTrakr’s public marketing website uses additional analytics or advertising technologies in the future, this Privacy Policy may be updated to describe those practices.

31. Links to Other Websites and Services

ChurchTrakr may contain links to websites or services operated by Customers or third parties.

For example, a Customer may provide links to:

Its own church website;
Social media accounts;
External resources;
Stripe-hosted onboarding or account-management pages;
Stripe-hosted payment or verification pages;
Financial institutions; or
Other third-party services.

ChurchTrakr is not responsible for the privacy practices, content, or security of independent third-party websites and services.

You should review the privacy policies of those services before providing information to them.

32. Third-Party Integrations

Customers may choose to connect ChurchTrakr with third-party products and services.

When a Customer enables an integration, ChurchTrakr may exchange information with the applicable provider as reasonably necessary to provide the requested functionality.

Third-party providers may have their own terms, privacy policies, security practices, and data-handling requirements.

Enabling an integration does not authorize ChurchTrakr to use information obtained through that integration for unrelated advertising or marketing purposes.

Disconnecting an integration does not necessarily delete information previously transmitted to or maintained by the third-party provider.

33. Congregant Privacy

ChurchTrakr provides a separate Congregant Privacy notice designed to explain in plain language how ChurchTrakr handles information about church members, attendees, guests, donors, volunteers, parents, children, and families.

The Congregant Privacy notice supplements this Privacy Policy but does not replace it.

If there is a conflict between the Congregant Privacy notice and this Privacy Policy regarding ChurchTrakr’s legal privacy obligations, this Privacy Policy controls.

34. Portal Users

Individuals who access a ChurchTrakr-powered church portal are also subject to the ChurchTrakr Portal Terms of Use.

Information submitted through a church portal is generally processed on behalf of the church operating that portal.

The church determines:

Which ChurchTrakr portal features it enables;
What information it makes available to portal users;
Whether online giving is enabled;
Whether ChurchTrakr Payments or a Customer-connected Stripe account is used;
Which payment methods are available; and
What information the church requests from portal users.

Payment information submitted through the portal may also be processed by Stripe as described in this Privacy Policy.

35. Changes to This Privacy Policy

ChurchTrakr may update this Privacy Policy periodically to reflect:

Changes to ChurchTrakr;
New features or integrations;
Changes to payment arrangements;
Changes to third-party providers;
Changes to our data practices;
Security or operational changes; or
Changes in applicable law or regulatory requirements.

When we make changes, we will update the effective date shown at the top of this Privacy Policy.

If changes materially affect how we handle personal information, we may provide additional notice through the ChurchTrakr Services, our website, email, or another reasonable method.

36. Contacting a Church About Your Information

If you are a member, attendee, guest, donor, volunteer, parent, guardian, or other person associated with a church that uses ChurchTrakr, your church is generally the appropriate first point of contact regarding the information it maintains about you.

For example, contact your church if you want to:

Correct your name or contact information;
Change household or family information;
Ask about attendance records;
Ask about giving or payment records;
Change church directory information;
Change communication preferences;
Ask about information submitted through a church form;
Ask about information concerning your child; or
Request deletion of information maintained by the church.

ChurchTrakr provides the software used by the church but generally does not decide what congregant information the church maintains.

For questions about a card or ACH transaction, you may also need to contact the church, Stripe, or your financial institution, depending upon the nature of the question.

37. Contact ChurchTrakr

Questions about this Privacy Policy or ChurchTrakr’s privacy practices may be directed to:

ChurchTrakr LLC
925 North Point Parkway, Suite 130
Alpharetta, GA 30005
USA

Email: support@churchtrakr.com

Website: ChurchTrakr.com

For requests concerning information maintained by a particular church, please contact that church first.