True Disciple
Start a church

True Disciple Terms of Service

Last updated: November 6, 2026

These terms are a contract between the operator of True Disciple (“True Disciple,” “we,” “us”) and the person or church that uses the Service. The Service is the True Disciple mobile app, the church admin website, and the features they connect to.

The operator’s legal name and address are above. Section 16 names the governing law.

By creating an account, joining a church, uploading content, or paying for a plan, you agree to these terms and to the Privacy Policy. If you are accepting for a church, you represent that you have authority to bind that church.

Part A applies to everyone. Part B applies to members. Part C applies to a church that opens an organization, starts a trial, or buys a plan. Schedule 1 is the data-processing addendum and applies to every church.

Part A — Everyone

1. The Service

True Disciple helps a church turn a sermon into lessons its members can study. Church staff upload a manuscript, an audio file, or a video link. We transcribe recordings, draft an outline and practice questions, and hold that draft until a pastor reviews and publishes it. Members study published lessons, practice verses, earn reward-fact cards we have written, and may send a question to church staff.

We may change, suspend, or discontinue a feature. We will not remove a church’s published lessons without notice except where these terms allow us to suspend the account or the law requires it.

Generated outlines, practice questions, and reward facts can be wrong, incomplete, or a poor fit for a congregation. They are study aids. They are not pastoral care, counseling, or a statement of what a church believes. A pastor is responsible for what that church publishes. You are responsible for how you use what you read.

2. Accounts

You must give a working email address and a display name. The display name is the name other people in your church can be shown. It is not a separate username, and it is not your email address. You may sign in with email and a password, or with Sign in with Apple.

You are responsible for activity under your account and for keeping the password confidential. Tell us if you believe someone else is using it.

One person, one account. Do not share an account. Do not create an account for a child under 13. If we learn an account belongs to a child under 13, we will delete it. Teenagers 13 and older may hold ordinary accounts. A church that invites a minor is responsible for any parental permission that church chooses to obtain. We do not ask for age and we do not screen invitations.

3. Acceptable use

You will not:

We scan audio uploads for malware on our own systems before we store them. We may reject a file the scan flags. We may remove content or suspend an account that breaks these terms. We will tell the account holder when we can do so without compromising security or a legal duty.

4. Our intellectual property and yours

We own the Service, the reward-fact catalog, and our software. We grant you a personal, non-exclusive, non-transferable license to use the Service while these terms are in effect and your access is allowed.

You keep ownership of content you submit: manuscripts, audio, video links, questions, and pastoral replies. You grant us a license to host, copy, transcribe, process with the suppliers named in the Privacy Policy, display to the people these terms allow, and back up that content, only to provide the Service to the church it belongs to. The license ends when the content and any backups are deleted, except for copies we must keep for a legal or billing record.

Scripture in the app is the Berean Standard Bible, the World English Bible, or the King James Version, from copies we host. The app labels the translation. That text is not ours to assign, and you will not strip the label or present the text as a different translation.

Google does not take ownership of text generated for you through the Gemini API. Similar output can be generated for someone else. You are responsible for reviewing generated lesson content before a church publishes it.

5. Privacy

The Privacy Policy is part of these terms. It names the suppliers who process personal information, including Fly.io, Neon, Cloudflare, Google (Gemini API via AI Studio on a billed project), AssemblyAI, Resend, Stripe, RevenueCat, Expo, Apple, and Google’s consumer services. It also states that we do not sell personal information, do not share it for cross-context behavioral advertising, and do not use it for advertising.

6. Disclaimers

The Service is provided “as is.” To the extent the law allows, we disclaim implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement, and we do not warrant that the Service will be uninterrupted, that transcription or generated lessons will be accurate, or that a particular translation or feature will remain available.

Some places do not allow these disclaimers. In those places they apply only as far as the law allows.

7. Limitation of liability

To the extent the law allows, neither party is liable for lost profits, lost data, or indirect, incidental, special, consequential, or punitive damages, even if advised of the possibility.

To the extent the law allows, each party’s total liability arising out of the Service in a 12-month period is limited to the amount that party paid or was paid under these terms in that period. If you paid nothing, the limit is 100 US dollars.

These limits do not apply to a church’s indemnity in section 12, to misuse of the other party’s intellectual property, or to liability the law does not allow us to limit.

8. Termination

You may stop using the Service at any time. You may delete your account in the app. If you cannot, email the contact above and we will delete it. Deleting your account deletes your profile, sessions, progress, push tokens, and questions tied to you. Lessons a church has published remain with that church. A church admin can export that church’s content from the admin tools before the content is deleted.

We may suspend or close an account that breaks these terms, creates a security risk, or is required to be closed by law. A church’s payment terms are in Part C.

Sections that by their nature should survive do survive, including intellectual property, disclaimers, liability limits, indemnity, and governing law.

Part B — Members

9. Joining a church

You see a church’s lessons only after that church connects you. That happens when you enter a current registration code, when church staff approve a join request, or when staff invite you. Staff can remove your connection. We are not a party to the church’s decision to admit or remove a member.

A church’s plan, not a purchase inside the app, is what pays for the church’s use of the Service. If the church’s plan lapses or is canceled, published lessons may become unavailable. Unlocks you bought in the app are described in section 10 and are separate.

10. In-app unlocks

Some lessons can be unlocked by an in-app purchase. Apple or Google charges you and handles the receipt and any refund under that store’s rules. We cannot issue a store refund ourselvs. RevenueCat validates the receipt on our servers so we can record the unlock.

Church subscription checkout on the admin website is for churches. The app will not send you there to buy digital content that is sold inside the app.

11. Questions to church staff

You may send a question about a lesson. Church staff see the question and your display name. They do not need your permission to read it.

The question is private to you and church staff unless you allow it to be shared and a pastor then marks the reply public. Other members who can see that lesson then see the question and the reply, without your display name. They can see the display name of the church staff who answered. If you did not allow sharing, staff cannot make the reply public.

Do not send a question you would not want that church’s staff to read with your name attached.

Part C — Churches

12. Authority and content

The person who creates the church organization, accepts a co-admin invite, or starts a checkout represents that they can bind the church. The church is responsible for its admins, the registration codes it distributes, and the people it approves.

The church represents that it has the rights needed to submit each manuscript, audio file, and video link, and to let us transcribe it, process it with the suppliers in the Privacy Policy, store it, and show the resulting lesson to that church’s members. A recording of a service often includes music or quoted material. The church, not us, is responsible for those rights, including any license the church needs for music in a recording.

The church will indemnify us and our operators against claims, damages, and reasonable attorneys’ fees arising from church content it did not have the rights to submit, from a member’s question or a pastor’s reply, or from the church’s use of the Service in breach of these terms. We will give the church prompt notice of a claim, let the church control the defense, and cooperate at the church’s expense. The church will not settle a claim in a way that admits fault by us or imposes an obligation on us without our written consent.

We will indemnify the church against a third-party claim that the unmodified Service, as we provide it, infringes that party’s United States copyright, trademark, or patent, excluding claims that arise from church content, from a combination we did not supply, or from the church’s continued use after we told it to stop. Our obligations are to defend the claim and pay damages finally awarded or a settlement we approve. We may obtain a license, modify the Service, or end the church’s access and refund prepaid unused fees for the affected feature. This section states our entire obligation for intellectual-property claims.

13. Plans, trials, and payment

Church plans are billed in US dollars through Stripe on the church admin website. The current self-serve plans, member caps, and monthly outline allowances are shown at checkout and in the app’s plan comparison. A 14-day trial uses Starter limits. Enterprise pricing is agreed separately and is not available at self-serve checkout.

Checkout defaults to monthly billing where both monthly and yearly prices are offered; you may choose yearly before checkout. The plan renews for the period you selected until it is canceled. Cancellation takes effect at the end of the period already paid.

When you change tier or switch between monthly and yearly billing on an active Stripe subscription, Stripe applies proration: unused time on your current price is credited against the new price for the rest of the current billing period, and any net charge or credit is handled through Stripe invoices and your payment method on file. We do not issue discretionary cash refunds outside what Stripe calculates, except where the law requires it.

If payment fails, Stripe may retry the charge. If the subscription is no longer active, the church’s ability to create and generate lessons ends. Members may lose access to that church’s lessons as the product’s entitlement rules provide.

The church will not direct members to the admin website to buy a digital unlock that is offered as an in-app purchase.

14. Staff, members, and generated lessons

Church staff may invite co-admins. An invite is sent by email through Resend. The church is responsible for removing an admin who should no longer have access.

Staff see a member’s display name and email, the member’s role, and questions that member asks, with the member’s display name. Staff see church-wide totals of membership, lessons started, medals, questions, and reviews due, for every member that opts into the anonymous aggregate metric collection. Staff do not get a view of one member’s practice answers.

A draft is not a published lesson. Publishing is an act of the church. The church is responsible for the pastoral fitness of what it publishes, including scripture references and generated questions.

15. Suspension

We may suspend a church that does not pay, that breaks these terms, or that creates a security risk. Our operators record that action in an audit log. We will give the billing admin notice by email when we can do so without compounding the risk.

Schedule 1 — Data processing

This schedule applies when the church submits member or staff personal information to the Service and we process it on the church’s behalf. The church is the controller of that ministry information. We are the processor. For our own account-security logs, billing records, and operator audit log, we act as an independent controller, as the Privacy Policy describes.

What we process

Member and staff accounts, church connections, lesson progress, questions and replies, and church content, for the purpose of providing the Service under these terms. We will not sell that information, share it for cross-context behavioral advertising, or use it for advertising. We will not use church content or member information to train a model for anyone other than that church’s use of this Service.

Subprocessors

The processor list in the Privacy Policy is the list of subprocessors. The church gives us general authorization to use those subprocessors. Before we add a subprocessor that will process church or member information, we will update that list and email the church’s billing admin. The church may object by canceling before the new subprocessor processes its information. If the church does not cancel, the authorization covers the addition. Canceling ends the subscription at the end of the period already paid, under section 13.

Security and breaches

We maintain the safeguards described in the Privacy Policy. If we become aware of a breach of security that affects the church’s personal information, we will notify the church’s billing admin without undue delay, with the information we have about what happened, what was affected, and what we are doing about it. The church is responsible for notices the church itself must give to its members.

Deletion

When a paid subscription ends, we keep the church’s content and member connections for 120 days, as the Privacy Policy describes, so the church can resubscribe or a billing dispute can be resolved, unless the law requires a longer record. The church may ask us to delete that content sooner. A church admin can export the church’s content from the admin tools before it is deleted. A member who deletes an account deletes that member’s profile, progress, and private questions. Published lessons remain the church’s until the church’s content itself is deleted.

International transfers

Google may store Gemini prompts and responses transiently in any country where Google or its agents have facilities, as Google’s paid-service terms describe. Other subprocessors may process information in the United States. Where the law requires a transfer tool, we will use the supplier’s standard contractual clauses or an equivalent mechanism the supplier offers.

Assistance

We will provide the information the church reasonably needs to answer a member’s privacy request, and we will fulfill a deletion or access request the church directs us to fulfill, unless the law says otherwise.

16. Governing law

These terms are governed by the laws of the State of Illinois, without regard to conflict-of-law rules. The state courts located in Lee County, Illinois, and the United States District Court for the Northern District of Illinois, have exclusive jurisdiction over disputes arising out of these terms, except that either party may seek temporary or injunctive relief in any court of competent jurisdiction to stop misuse of its intellectual property or unauthorized access to the Service.

We do not require arbitration. A court of competent jurisdiction as set out above is the forum.

17. Other terms

These terms, the Privacy Policy, and any enterprise order are the entire agreement. They replace earlier oral or written terms about the Service. If a court holds a provision unenforceable, the rest remains in effect.

We may update these terms by posting a new version and changing the date above. If a change is material for a paying church, we will email the billing admin before it takes effect. Continued use after the effective date is acceptance. If the church does not accept a material change, its exclusive remedy is to cancel under section 13.

We may assign these terms to a successor of the Service. The church may not assign them without our consent, except to a successor of the church.

Notices to us go to the contact at the top. Notices to a church go to the billing admin’s email on the account.