The Challenge App

Legal

Privacy Policy

Effective 3 November 2026 · Version 2026-11-03 · Challenge App LLC

The Challenge App is operated by Challenge App LLC ("we", "us"). We decide what the app collects and why, and we are responsible for it.

Write to us at admin@challengeyourfaith.com about anything in this policy — a question, a correction, a copy of your data, or a deletion request.

You can also write to us on paper:

Challenge App LLC, 21049 Devonshire St., Chatsworth, CA 91311, United States. Online at challengeyourfaith.com.

This policy describes the app as it actually works. Where something is imperfect, we say so.

Who else is involved

The Challenge App is licensed to churches, which run programs inside it. Freedom Church is a program partner, not the operator. When you register with a church's code, that church receives your registration record — your name, email, phone number and which group you joined — because it is the church that placed you in the program and organises your group. The church is responsible for what it does with that information. We are responsible for the app.

Who may use the app

You must be 13 or older. The Challenge App is not directed to children under 13 and we do not knowingly collect information from them. We ask for your date of birth at registration to enforce this. An account one of our system administrators creates by hand needs one too: the administrator must enter a date of birth, and the app refuses one that makes the person younger than 13. We create those accounts for group leaders we already know. An administrator used to be able to leave that date blank, and for an account made that way the check was the administrator's judgement rather than a date we held. If we hold no date of birth for you at all — none on your account and none on your church's registration record — for that reason or any other, and you lead a group that belongs to a church program, you can add one yourself, once, at Me → Phone & Email — on our website, if the app on your phone does not show it yet — and the app refuses one that makes you younger than 13 there too. If you believe a child under 13 has an account, email admin@challengeyourfaith.com and we will delete it.

What we collect

Things you give us when you register — or that an administrator enters or corrects for you

Most people type all of that in themselves. Group leaders are often set up before a program starts: one of our system administrators enters those details, sets a first password, and hands it over. If that is how your account was made, replace that password — our Support page says how, and why signing out first matters.

Things you create by using the app

Things your device gives us

Things about your access

What we do not collect

No location data. The app requests no location permission and contains no location code. No contacts. No audio recording. No browsing or search history. No advertising identifier.

We do not currently strip embedded metadata from the photos, GIFs, videos and files you share in group chat before they upload: the app uploads each one as your device hands it over. If a file you share already contains location data in its own metadata, that data travels with the file to your group. Remove it before sharing anything you would rather not disclose. We intend to fix this.

A profile photo is not uploaded as the original file — the app uploads the new copy it makes on your device, as described above. We have not yet confirmed whether that copy keeps any of the original's embedded metadata, so do not rely on it to remove location data either.

What we do not do

The one exception worth naming honestly: the Stripe payments library is compiled into the app on every platform and reports its own product-interaction telemetry to Stripe. That is Stripe's own processing for fraud prevention and service operation, not ours, and it is not used for advertising.

Who can see what, inside the app

Those last three protections are about what another account can read. They are not protection against somebody who knows your password, because to the app that is simply you signing in. They are not protection against somebody who can change the address on your account either, because the code that sets a new password follows that address. If an administrator set your account up and chose your first password, replace it — and to end a session somebody else may already be holding, sign out first and then use Forgot password? Just before that signs you out everywhere, it also deletes every push token your account has, so a phone somebody else was holding stops being sent your pop-ups; "Things your device gives us" above says which versions do this and when it can fail. Changing your password while you are signed in ends every session too, the one on the device you are using included. Either way, each device that was signed in as you — yours, and any somebody else is holding — is signed out within about an hour, and signing in again on it takes the new password. But changing it while you are signed in deletes no push token, so a phone somebody else was holding can go on being sent your pop-ups after it is signed out; the route above is the one that stops them. Our Support page walks through both. That route only works while the address on your account is one you can open, because that is where the code goes — and correcting a wrong address ends no session, so putting the right address back does not remove somebody who is already signed in.

Group chat is private to the group. It is not public, not indexed, and not readable by people outside the group, with three exceptions. A message someone has reported can be read by our administrators and by church staff we authorise, even if they are not in the group — the message itself while a report on it is open, and the report's frozen copy of it after that. The pop-up for a new message, which carries its sender's display name and up to 140 characters of it, goes to every phone holding a push token for each member it is sent to, which can be a phone somebody else now uses (see "Things your device gives us" above). And someone who leaves the group, or is removed from it, can keep the notifications already in their Notifications list, each new-message one with up to 140 characters of its message, until they clear them, their own account is deleted or the group is deleted. Please still treat it as you would any group conversation — anyone in the room can screenshot it.

What our registration pages show

Our website's registration pages are public: anyone can open them, with or without an account. A church program's registration page lists that program's open groups, and any open group that is not part of a program — such as a group a member creates in the app — so that somebody registering can choose one. A group registration link — a challengeyourfaith.com/join address we give out for one group in a church program — shows that group to anybody who has the link while the group is active, including a group the program's page does not list, and forwarding the link forwards what it shows. While a group is inactive, its link shows nothing about it. For each group, these pages show its name, the day, time and place it meets, and its leader's name: the display name on the leader's account, or their first and last name if it has none. If you lead a group, your name can appear on a public web page. Nothing else about the leader or any member is shown — no email address, phone number or account id — although the page is told how many places each group has left.

Files our administrators download

A system administrator can download a spreadsheet listing every account in the app, whichever church or program it belongs to, members under 18 included. Church staff cannot download it, although the screens they use list every account's name and sign-in address, and let them find an account by the phone number on its registration record.

Each row is one account and can hold, depending on the columns the administrator picks: its account id, which every file includes; its first and last name (a name the account is missing — unless one of our administrators removed it — comes from the church's registration record or, for an account with no name at all, from a paid registration at the same email address that is not yet linked to the account); the email address it signs in with; the phone number on the church's registration record; the programs it is in or has paid for, the groups it is in or leads, and whether it leads each one; whether its program fee was paid, how much and how (once, or monthly, with the plan's number of payments and the date the first one was recorded), and anything unusual about its payments or about other registrations at its email address that are not linked to it, such as a refund, a second charge, a test payment or a checkout started and not finished; when the account was made; whether it is one of our administrators, church staff, or a test or store-review account; and notes about its registration and access, such as how it joined, that it has access through an older purchase from us, that it is waiting to be placed in a group, or that the registration form used a different email address (not what that address is). It never holds a date of birth, a password, a registration or invite code, check-ins, points, reading progress, Bible highlights, spiritual gifts answers or results, messages or photos, or the phone number on your account. Hiding your phone number or email address at Me → Phone & Email does not leave you out of it. Those switches decide what your groups' leaders are shown, not what our administrators can download.

Each time our database supplies the rows for such a file, it records who asked for them, when, which columns and how many accounts. That record keeps none of the rows themselves.

A system administrator can also download a spreadsheet of one week's results as our web console shows them, described under "Who can see what, inside the app" above. It lists either the groups in one church program or in all of them — for each group, its name, its program, its status (listed, private, invite-only or inactive), how many members it has and how many of them scored any points, its points and the points it could have scored, its completion, and its rank and how that rank changed from the week before — or one group's members: for each member, their name, whether they lead the group, their points and the points they could have scored, their completion, and their rank in the group and how it changed from the week before. Church staff cannot download it. It never holds an email address, a phone number, a date of birth, an account id, or which challenges anybody completed on which day.

Each time our database supplies a week's results for such a file, it records who asked for them, when, which week, whether they were the groups or one group's members, which program or group, and how many groups or members they covered. That record keeps none of the rows themselves.

We use these files to organise groups and programs, contact members about their program, check registrations and payments, and review each week's results. Nobody outside our administrators receives one, except a week's results: a system administrator may share those with your church's pastors and ministry leaders, so that they can recognise and announce the week's leading groups and members — for example, at a service or in your church's announcements. If you would rather not be named in an announcement, write to us and we will not name you. We keep these files only on our administrators' own computers, and a shared week's results only on those leaders' own devices, and we delete each one within 90 days of downloading it. Until then, a file downloaded before you delete your account still lists you. Write to us and we will delete any of these files that lists you sooner. We never sell these files or use them for advertising.

Companies that process data for us

We use a small number of service providers. Each receives only what its job requires.

We do not permit any of these providers to use your information for their own advertising. Google's delivery of a notification to a phone or tablet that is not an iPhone or iPad is governed by Google's own terms rather than by that promise.

Videos in the Library

The videos on the Library's Watch shelf are made by Freedom Church and hosted by Vimeo (vimeo.com) on the church's own Vimeo account. When you open the Library and it has videos for you, your device loads every video's picture from Vimeo, whether or not you scroll down to the Watch shelf, and may keep a copy so it need not ask again; Vimeo receives your IP address, your user agent and which picture it is. When you open a video, Vimeo's player loads inside the app or our website, and Vimeo receives your IP address, your user agent, other information about your browser or the app's web view, and which video it is. If you cast a video to a TV or another screen, that device loads it from Vimeo too. We turn on the player's "do not track" setting, which Vimeo says blocks the player from collecting session data and analytics; with it on, Vimeo says, the player sets only the few cookies it considers essential to running securely. That setting does not stop a browser sending cookies it already holds from vimeo.com, so on our website yours may send any it has from your own visits to Vimeo. Nothing else about you is sent — not your name, email address or account id. What Vimeo does with what it receives is governed by Vimeo's own privacy policy.

Where data is held

Our database, storage and functions run in the United States. If you use the app from elsewhere, your information is processed in the United States.

How long we keep things

While your account exists, we keep your profile, your profile photo if you have added one, your messages and media, your check-ins, your reading progress, your Bible highlights, your notifications, your notification choices, your Phone & Email choices and your subscription record, because they are the app. Removing a highlight deletes it, and removing your profile photo deletes it from storage. Removing the phone number on your account deletes it from your account; a phone number you gave on your church's registration form stays on that record — only a system administrator can correct or remove it there, and deleting your account erases it.

Registration records — the seat your church issued, the audit trail of your registration attempts, and a record of any correction we made to the email address or phone number on it — are kept for the life of the program and afterwards as a record that the seat was used. Once Stripe has told us that you paid for a seat, the church's payment record for it — and, for a monthly plan, the record of what you agreed to — is kept after your account is deleted and after any plan ends, as the church's record of what was agreed and paid.

The record of each confirmation code we email while you register — the address it went to and a truncated hash of your IP address, described under "Things about your access" above — is deleted automatically once it is more than a day old, a batch at a time, whenever we send somebody a code. That clean-up does not run on a timer, so a record can stay longer, especially while few people are registering. If you want yours removed sooner, write to us.

A registration you start on a church's registration page and then do not pay for is kept differently. It holds what you typed into that page — your name, email address, phone number, date of birth and the group you chose — with our record of any checkout you started. It is not part of any account, so deleting an account does not remove it, and nothing removes it just because time has passed. Once the time for paying has run out and any checkout it had has closed, only two things remove it: one of our system administrators deletes it from our web console (church staff cannot do this; only a system administrator can), or a new checkout is started for the same program with the same email address and a new registration replaces it. Either way, the registration and our record of any checkout it had are deleted. When a new registration replaces it, we keep no copy of them and no record that it happened. When an administrator deletes it, the deletion record described next keeps a copy of that checkout record. Stripe keeps its own record of the checkout, with the email address it was started with. If you want a registration like this deleted, write to us. If you paid and your place has not opened, write to us before you start again. If the copy of this policy in the app on your phone does not mention deleting a registration you did not pay for, it is out of date — this version replaces it.

When a system administrator deletes one, we keep a permanent record that it was deleted: which administrator deleted it and when, the reason they chose — that you registered again, asked to be removed or are not joining, or that it was a test or spam — and any short note they added, which the console asks them to keep free of personal details. That record also keeps which program the registration was for and the group you chose, when it was started and when its time for paying ran out, when you agreed to our Terms of Use and this policy, whether an account in the app used its email address at the time, the part of that address after the @, and a copy of our record of each checkout it had: Stripe's reference for it, the plan and the amount, and, for a monthly plan, the record of what you agreed to — the sentence you ticked, when, its version and the time zone its dates were shown in. Apart from anything an administrator types into that note, the record holds no email address, name, phone number or date of birth. The identifiers it keeps are enough to find, in Stripe's own records, any checkout started for it and the email address it was started with.

Records of the changes our administrators and church staff make to your account and your groups have no set end date either: they are kept after your account is deleted, as described under "Deleting your account" below. So is the record that an administrator deleted a registration you did not pay for.

Every spiritual gifts assessment you complete is kept as a dated record for as long as your account exists. Taking it again adds a new result rather than replacing the old one — that is deliberate, so you can see how your answers change over time. Answers to an assessment you have not finished are working notes and are cleared when you start again; nothing is lost when they are, because each completed result keeps its own copy of the answers it was worked out from.

Server logs held by Supabase and Expo, and whatever Apple's and Google's push services keep of a notification on its way to a phone, are retained according to those providers' own schedules.

Deleting your account

You can delete your account from inside the app: Me → Delete Account. You can also do it on our website: sign in at challengeyourfaith.com and go to Me → Delete Account. It is immediate and it cannot be undone. Here is exactly what happens, stated plainly:

These survive on purpose, and you should know about them:

Anything already saved or screenshotted by another member of your group — including your phone number or email address, if they were shown them — is outside our control.

Your rights

You may ask us to:

Some of this you can do yourself. At Me → Phone & Email you can hide your phone number, your email address or both from your groups' leaders and show them again, add, correct or remove the phone number on your account, and — if you lead a group that belongs to a church program you are registered in and we hold no date of birth for you at all — add one. Deletion is available at Me → Delete Account, in the app or on our website. For everything else, email admin@challengeyourfaith.com. We will answer within 30 days. We may need to confirm you control the account's email address before we act.

There is one request that cannot work that way, and it is the one people need most: correcting the email address itself. You cannot write to us from an address that never reached you, and there is no way to change it yourself in the app — only a system administrator can. So for that one request we ask for something else: something from the registration record your church gave us, such as the phone number that was on it when you registered (a number one of our administrators put there later does not count), or word from the church that issued your code. Be clear about what that is worth. Your name and the group you are in can already be read by other members of the app, and your group's leaders may be shown your phone number, so what we are doing is weighing up whether your story holds together, not proving it. It is a system administrator's judgement and we will refuse when it does not add up. We hold to the stricter check for anything we cannot undo — a deletion carried out for the wrong person cannot be reversed — so if the address on your account is wrong and you want the account deleted, write from an address you can open, tell us so, tell us how else to reach you, and expect us to take longer over it.

Depending on where you live you may have additional rights, including the right to complain to a data protection authority. Write to us first and we will try to sort it out.

Security

Access to your data is enforced at the database level, per row, per account — not just in the app's screens. Chat media lives in a private bucket that only members of the relevant group can read, except that while a message has an open report, our administrators and church staff we authorise can also read that message's photos, videos and files. Profile photos live in a separate private bucket, where another signed-in member can read only a member's current photo, and not across a block in either direction; the app shows each one through a link that stops working within an hour. Passwords are hashed. Traffic is encrypted in transit.

No system is perfect, and we will not pretend otherwise. If we become aware of a breach affecting your information, we will tell you.

Changes to this policy

If we change this policy in a way that matters, we will update the version and effective date at the top and show you the new version in the app. Continuing to use The Challenge App after that means you accept the updated policy.

Effective 3 November 2026.

Questions: admin@challengeyourfaith.com