Legal
Privacy Policy
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
- First and last name, and the display name shown to your group.
- Email address.
- Phone number.
- Date of birth.
- A password, stored only as a hash — we never see the one you choose. The exception is an account one of our system administrators creates by hand: they type that first password themselves, so they know it until it is changed. It is stored the same way; the difference is that a person chose it and remembers it.
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
- Group chat. The text of your messages, and the photos, videos and files you share, along with their file names and types. Reactions and likes.
- Profile photo. Optional: if you have not added one, the app shows your initial instead. You add, change or remove it from the Me tab of the app installed on your phone or tablet — not on the website. Before it uploads, the app crops the picture you choose to a square and saves a new JPEG copy of it on your device, no larger than 512 × 512 pixels, and it uploads that copy rather than the original.
- Daily check-ins. Which of your group's daily challenges you completed, on which day. Those challenges are written by your group leader and in practice include religious practice ("SOAP", "Pray for your group") and physical activity ("100 push-ups"). A check-in is therefore a record of your religious practice and your fitness activity, and we treat it as sensitive. Each member of your group whose check-in alerts are on is also sent a notification naming you and the challenge each time you check one off — apart from anyone you have blocked or who has blocked you. Whether a member gets one depends on their settings, not yours; "Companies that process data for us" below says what it carries and where it goes.
- Reading progress. Which library chapters you have opened, how far through one you are, and when you finished it.
- Bible highlights. The verses you highlight, recorded by book, chapter and verse, and when you highlighted them. Copying or sharing a verse does not send us the verse, or the fact that you copied or shared it; it goes to your device's clipboard, or to the app you choose to share it with.
- Points and streaks derived from your check-ins.
- Notifications we have sent you, and whether you have read them.
- Your notification choices. Which kinds of notification you have switched on or off — at Me → Notifications in the app, or on our website at Me → Notifications (on a computer, then What you hear about), which you can use if the app on your phone does not show these choices yet — and when you last changed each one. The kinds are group chat, check-ins, lead changes and, if you lead a group, new members. Your choices are kept with your account, not on your phone, so they follow you to every phone you use and to our website. A kind you have never changed follows our default for it: group chat and new members start on, and check-ins and lead changes start off at first. We plan to switch check-ins and lead changes on for everyone who has not chosen — we are telling you now rather than after. Once you have changed a kind, we keep your choice for it, even if you switch it back to where it started, so a change to our defaults never overrides it. A kind you have switched off is not sent to you at all: it adds nothing to your Notifications list and sends no pop-up. Report alerts, which go to group leaders and our administrators, cannot be switched off: they always reach the Notifications list, though their pop-ups still follow each phone's Pop-ups on this phone switch and the phone's own settings. If the copy of this policy in the app on your phone does not mention notification choices, it is out of date — this version replaces it.
- Your Phone & Email choices. Whether your phone number and your email address are shown to the leaders of your groups that belong to a church program, under the rules set out below — both are, until you turn either off — and when you last changed that. Me → Phone & Email is also where you can add, correct or remove the phone number on your account, and add a date of birth if we hold none for you at all and you lead a group that belongs to a church program you are registered in.
- Spiritual gifts assessment. If you take it, your answers to a questionnaire of statements about yourself, and the gift profile computed from them — the scores for each gift, the gifts it ranks highest for you, and a copy of the answers that result was worked out from. Your answers to that questionnaire are a self-description of your religious life, and we treat them as sensitive.
Things your device gives us
- An Expo push token for each install of the app on a phone or tablet where Pop-ups on this phone is on and notifications are allowed for the app on that phone (most phones ask you first). The switch is at Me → Notifications — on an older version of the app, it is the Notifications setting on the Me tab — and it starts on. The token identifies that installation so a pop-up can reach it; with it we keep whether the phone or tablet is an iPhone or iPad, and when the token was first and last saved. The switch itself is kept on that phone, not by us. Turning it off deletes that install's token from our database, and so does signing out of a version of the app that shows Pop-ups on this phone; your notification choices stay with your account, and what you have chosen still arrives in your Notifications list. Either can fail to delete the token — for example if the phone cannot reach us at that moment, or if notifications are turned off for the app in the phone's settings — and signing out of an older version does not delete it at all. Resetting your password with Forgot password? while you are signed out — on our website, or in a version of the app that shows Pop-ups on this phone — deletes every push token your account has, on every phone and tablet, just before it signs you out everywhere; each of your own phones saves its token again when you sign in on it. That deletion can fail too, and for up to about an hour after it a phone that was signed in as you can save its token again — for example if its app is closed and opened again. Apart from deleting your account, no other way of being signed out deletes a token. Until a token is deleted, it stays with your account even if somebody else signs in on that phone, and that phone can still be sent pop-ups for your account. If you think a phone you no longer use is still being sent your pop-ups, write to us and we will delete every token your account has; your own phones save theirs again the next time the app starts on them — and so does any phone still signed in as you, so if that phone may still be signed in as you, sign out and use Forgot password? instead (see below). Deleting your account also deletes them. Our website does not use pop-ups: it shows your notifications in its Notifications list instead.
Things about your access
- Subscription state — whether your access comes from a church grant or a purchase, its status, and the Stripe identifiers that describe it. We never see or store your card number.
- A monthly plan, if you pay Freedom Church monthly. When you agree to it, we record the exact sentence you were shown and ticked, when you agreed to it, its version, and the time zone its dates were shown in. We keep that with the church's payment record for your seat. Stripe, which takes the payments for the church, records each payment's date, amount and status. We make that record before you pay, so a monthly checkout you start and do not finish leaves one too; "How long we keep things" below says what then happens to it.
- During registration, a truncated one-way hash of your IP address and the email address the confirmation code was sent to, used to rate-limit abuse of the registration form; and, when you start a checkout, one-way hashes of your email address and IP address for the same purpose. We do not store the raw IP address.
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
- No advertising. There are no ads in the app and we do not sell ad space.
- No analytics SDK, no crash-reporting SDK, no attribution SDK. None is installed. We have verified this against the app's own dependency list.
- No tracking. We do not track you across other companies' apps or websites, and we do not link your data to anything from a data broker. The app never shows the App Tracking Transparency prompt because it has nothing to ask for.
- No sale or sharing of personal information for advertising, ever.
- No record of what you watch. The app does not record which videos you open or play, or for how long. Opening a video does ask our database for that video's details, and like every request to it, that request passes through our database provider's own logs (see Supabase, below).
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
- Your group sees your display name, your profile photo if you have added one, your messages, the photos, videos and files you post, your reactions, your check-in progress and your points — and, if their check-in alerts are on, each challenge you check off, as you do it (see "Daily check-ins" above). Its members who do not lead it are not shown your phone number or email address — only its leaders can be, under the rules set out below.
- Your group leader sees everything the group sees, and additionally sees reports made about content or members in that group, including a frozen copy of the reported message — or, for a report about a member, their name and role in the group when it was filed and which profile photo they had then: a reference to that photo, not a copy of it. In a group that belongs to a church program, your leader may also be shown your phone number and email address, under the rules set out below.
- While a group is inactive, the app closes it to everyone in it, its leaders included. Only our system administrators can make a group inactive, and make it active again; church staff cannot. From the next time the app loads your groups (an app that is already open keeps showing what it had already loaded until then), it shows the people in an inactive group at most that it is inactive — nothing of its chat or the photos, videos and files posted there, its members, or its check-ins and points — though a link to a photo, video or file that was already opened keeps working for up to an hour. It shows its leaders neither the reports other people filed in it nor anybody's phone number or email address. Nobody in it can post, react, check in or report anything there, and nobody new can join it. The only lines its chat can still gain are the short system lines the app adds when our administrators or church staff remove somebody from it, move somebody out of it or change its leader, or when its leader's account is deleted and leadership passes to another member. Making a group inactive deletes nothing, and notifications you already received about it stay where they are; when it is made active again, its members see it as before. Our administrators and church staff still see the group on their own screens, as described below, and can finish any report filed in it. If the copy of this policy in the app on your phone does not mention inactive groups, it is out of date — this version replaces it.
- Our system administrators can see every report and the reported content, so that a report about a leader has somewhere to go.
- Our system administrators can create an account and set its first password. We do this to set up group leaders before a program starts, and nothing in the app limits it to them. Until that password is changed, the administrator who chose it can sign in as that account — and that means everything the account can do, including posting in its group under its display name, reading anything it can read, and permanently deleting it, because the password is also what confirms a deletion. Church staff cannot do this; only a system administrator can. A password you chose yourself is never readable by anybody, including us. The bullet below is why that is less protection than it sounds.
- Our system administrators can also change the email address on an account. We do this so that mail can reach somebody whose address is wrong — usually mistyped when they registered, sometimes typed by the administrator who set the account up. Nothing in the app limits it to those accounts: it works on an account you registered yourself, and changing your password does not put it out of reach. We refuse it on only a few accounts — one that is deleted or suspended, one that signs in through another provider, and our own administrators' accounts. Nobody proves they can open the new address before we start using it: an administrator types it, records how they checked it with you, and the app treats it as confirmed on that word alone. Know what that moves. The code that sets a new password is sent to the address on your account, so whoever sets that address can ask for that code, read it, set a password, and then be you inside the app — posting in your group under your display name, reading anything the account can read, and permanently deleting it, because the password is also what confirms a deletion. Church staff cannot do this either; only a system administrator can. Correcting an address signs nobody out: anybody already signed in to that account stays signed in, and correcting it is not a way to remove them. It moves the address on your account and on the registration record your church holds, for every program you are registered in, all of them or none. It changes nothing held by Stripe — a payment record keeps the address the payment was made with. We record every change, holding the old and the new address masked rather than written out. And this is the part the bullet above cannot promise you: an administrator who can move where a new password is sent never needs to read the old one.
- Our system administrators can also correct your name, and the phone number on your church's registration record. We do this when one of them is wrong; nothing in the app checks that it was. Correcting your name changes the first and last name on your account and sets your display name to match them. That is what your group, every other signed-in member and, if you lead a group, our registration pages show from then on. It does not change the name on your church's registration record, and it does not rewrite anything already written with the old name, such as chat lines already posted about you, notifications already sent and reports already filed. Correcting the registration phone changes the number on that record for every program you are registered in, all at once, and can add a number where there was none or remove one. It does not change the phone number on your account, which is the one your groups' leaders may be shown. Church staff cannot do either; only a system administrator can. We do not tell you when we make either correction. We record that it happened, who made it and when, and which of your first name, last name and registration phone changed, but not what any of them said before or after. For the phone number, the administrator also records how they checked it with you.
- Our system administrators can also delete a registration you started on a church's registration page and then did not pay for. They can do it only once the time for paying has run out and any checkout it had has closed, so it never reaches a registration that was paid for, or one that could still be paid for, and it changes no account. Church staff cannot do this; only a system administrator can. Deleting it removes the name, email address, phone number and date of birth you typed into that page. It finishes nothing and sends nobody anything, and we do not tell you when we do it. What we keep afterwards, including a copy of our record of any checkout it had, is set out under "How long we keep things" below.
- Church staff we authorise can see every report and the reported content too. A church staff account is one we have given that role; only we can give it. The role is not tied to a church: a staff account can see reports from every group in the app.
- An administrator or church staff member who is not in your group can see a reported message itself, including its photos, videos and files, only while a report on it is open. Once every report on it is resolved, the app stops opening the message and its media to them — though a link to a photo, video or file that was already opened keeps working for up to an hour after that. They can still read the report and the frozen copy of the message it keeps, and so can your group's leaders while the group is active. The reported message's text also reaches our moderation inbox by email the moment the report is filed, and we keep that email as the record of the report — see "Our email provider" below.
- A report about a member — about their profile photo or how they act — keeps no copy of any message and opens no message or media to anybody. Whoever reviews it, in the app or in our web console, can choose to show that member's profile photo from the report only while the report is open, and only the way any signed-in member can see it: their current photo, and not across a block in either direction.
- The person who made a report can read the note left on it when it is resolved.
- Who filed a report is hidden from the person that report is about. If someone reports you and you are one of the people who review reports — a group leader, an administrator or authorised church staff — the review screen on your phone and in the web console does not show you who filed it, and it withholds what they typed in the report's description box as well, because that description is their own words about you and would often identify them. It withholds two more fields for the same reason: the note written when the report is closed, and the name of whoever closed it — because the person who reviews a report may be the person who filed it, and then that note is the reporter's own words about you too. You still see the reason, the frozen copy of your own message — or, on a report about you as a member, what it recorded about your profile and whether it is about your photo or how you act — the status and the time the report was closed; if you closed it yourself, you also see your own note. The database enforces all of this, per row: the report table itself will not hand your own account a report somebody else filed about you, and the review screens read it through a routine that removes those fields first. The alert that tells a moderator a report has been filed records no account as its author, so it adds nothing about who filed the report to what that moderator can already read in the report itself, on a screen or otherwise. Another moderator, reviewing that same report, sees it whole. The alert email described under "Our email provider" below withholds the first two of those fields as well, on every report and from every reader: the line that would name the person who filed it reads the same on every one of those emails, and what they typed is not in the email at all — it is not even read out of the database to write it. An administrator who reads that inbox does not find the reporter's name or description there. What that email does still tell whoever opens it about the person who filed it, and we would rather name that than imply nothing is left: that a report exists, which group it is in, the reason chosen — and, for a report about a member, whether it is about their photo or how they act — and the time it was filed. Those are the same facts the review screen already gives the person a report is about, and they can use them to narrow down who is likely to have filed it, especially in a small group. Being church staff does not put an account on any report notification list — no push, no alert in the app, and that email goes to our own inbox rather than to staff; staff find reports in the web console. Our administrators are notified of every report, including one about themselves, so that a report about a leader always reaches somebody. If you do not review reports, none of this reaches you: you are never shown a report filed about you, or the note that closes it.
- Other signed-in members of the app can currently read basic profile fields — your first name, last name, display name and which group you are active in — even if they are not in your group. This is wider than it should be and we are narrowing it to your own church and group in a future release. We are telling you now rather than after.
- Your profile photo, if you have added one, can be seen by every signed-in member of the app, whether or not they are in your group — in the app on a phone or tablet, and on the website. That is the reach your display name has today, and the narrowing promised in the bullet above covers those profile fields, not your photo. The one exception is blocking: if you have blocked another member, or they have blocked you, neither of you is shown the other's photo, and each of you sees the other's initial instead — though a photo already loaded on the other person's device, or on another device of yours, can stay on screen for up to an hour after the block. The app gives nobody else a control to change or remove your photo. As with anything on your account, an administrator who can sign in as you (described above) could; and, as our Terms of Use say, we may remove a photo that breaks them, or the account that posted it.
- Among members, your phone number and email address are shown only to your group's leaders, unless you hide them. What our administrators' and church staff's own screens show, and the files a system administrator can download, are set out below and under "Files our administrators download". Unless you turn them off, the phone number on your account and the email address you sign in with are shown to the leaders of each group you are in that belongs to a church program, on that group's roster — on our website, and in the app once it shows Phone & Email. Nobody else in the group is shown them, whatever their age, and in a group that does not belong to a church program — such as a group a member creates in the app — nobody is shown anybody's details, its leader included. A leader is shown them only while the group is active and they lead it, are registered in its program and are 18 or over by the date of birth we hold for them. Anybody we hold no date of birth for is treated as under 18, so a leader we hold none for is shown nobody's details. The same rules decide what you are shown: if you lead a group that belongs to a church program and meet those conditions, you are shown the details of every other member of it who shares them, other leaders included, whatever their age; if you do not lead the group, you are shown nobody's details in it, not even your leader's. This is worked out afresh each time the app shows them, so from the day a leader turns 18, by the date of birth we hold, they are shown their group's details without anything further from them. If you have blocked a member, or they have blocked you, neither of you is shown the other's, even if one of you leads the group. A group's leaders are whoever leads it at the time, including anybody who becomes its leader later; leaving a group, being removed from it or deleting your account stops the app showing your details to that group's leaders. No member outside your groups is shown them: they are not among the profile fields every signed-in member can read, and our registration pages show neither.
- Each is your own choice. Turn off your phone number, your email address or both at Me → Phone & Email, and turn them back on the same way, at any time; it is one setting for all of your groups. If the app on your phone does not show Phone & Email yet, use it on our website. That screen shows you the phone number on your account and the email address you sign in with. Turning one off — like blocking, leaving a group or deleting your account — stops the app showing it from the next time somebody's roster loads, but none of those can recall a number or address somebody has already copied, saved or used. The same screen lets you add, correct or remove the phone number on your account; that changes the number on your account only, not the one on your church's registration record. The email address shown is the one you sign in with, the one our password-reset codes go to. You cannot change it in the app — only a system administrator can correct it, as described above — and if one does, your group's leaders are shown the corrected address. An administrator who set your account up knows any phone number they entered for it. If your account is on hold — you can sign in, but the app stops at a screen about your plan, a payment or a registration code instead of opening — you cannot reach Phone & Email, and your groups' leaders can still be shown your details: email admin@challengeyourfaith.com and we will turn either or both off for you.
- Our administrators and church staff are shown the phone number on your account only as a leader of a group you are in, under the same rules as any other leader. That is within their reach: a system administrator can add themselves to a group and make themselves its leader, and church staff can add themselves to a group and make another staff member its leader. Whoever is made the leader of a group that belongs to a church program is then shown its members' details the same way as any other leader. Their own screens show them other things, whether or not you hide your details from your groups' leaders: the email address you sign in with, and the phone number and email address on your church's registration record. That record is part of what your church receives, described under "Who else is involved" above, and our administrators and the church staff we authorise can see it on the screen they use to organise groups — a role that, as described above, is not tied to one church. Your group is not shown that record: the number its leaders may be shown is the one on your account, which is usually the one you registered with. The number on that record is the one given when you registered, unless a system administrator has since corrected, added or removed it, as described above.
- Our administrators' and church staff's own screens also show each week's results. Our web console shows them every week since the one that began on Sunday 4 October 2026, the week in progress included. For each week it ranks the groups in our church programs — inactive groups, and groups our registration pages do not list, included — and shows each group's points, the points it could have scored, its completion, its rank and how that rank changed from the week before, how many of its members scored any points, and how many did every challenge on every day of the week — or, in the week in progress, how many have done every challenge today. For any of those groups, it also shows each of its members by name, whether they lead it, and each week's points, completion and rank in the group, with how that rank changed from the week before. Points come from check-ins, so this shows how much of each week's challenge each member completed. Church staff see all of it too — a role that, as described above, is not tied to one church. The console works these results out from check-ins each time it reads them, keeps no copy of them, and counts only the people in a group at that moment: once you are no longer in a group, or your account is deleted, its results no longer show you or count your points, for any week, from the next time the console reads them (a console page that is already open keeps showing what it had already read until it reads them again). If the copy of this policy in the app on your phone does not mention weekly results, it is out of date — this version replaces it.
- Your date of birth is never readable by another user. It is held in a separate, owner-only table that no other account can query — not by your group, not by your group leader, and not by an administrator. That stays true of an account an administrator created — but if they entered a date of birth when they set it up, they know it, because they typed it. Our database does use it, to work out whether you are under 18, which decides whether you are shown anybody's details when you lead a group; if we hold more than one date for you — one on your account and another on your church's registration record — it goes by the one that makes you youngest. No screen shows anybody else the date, or tells them whether you are under 18, and your age makes no difference to who is shown your own details.
- Your spiritual gifts assessment is yours alone. Your answers and your results are readable only by your own account. This is one place where "your group leader sees everything the group sees" does not apply: your group does not see it, your group leader does not see it, and there is no administrator or church staff screen that reads it — not your answers, not your results, and not how many assessments you have completed. The database itself enforces that, per row: no group, leader, administrator or staff path to those rows exists.
- Your Bible highlights are yours alone. Which verses you have highlighted is readable only by your own account. No other member sees them, your group leader does not see them, and there is no administrator or church staff screen that reads them — not which verses, and not how many. The database itself enforces that, per row: no group, leader, administrator or staff path to those rows exists.
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.
- Supabase — our database, authentication and file storage provider. Supabase holds everything above except the downloaded files themselves: your account, your profile and any profile photo, the phone number and date of birth on your account, your Phone & Email choices, your chat and its media, your check-ins and your subscription record. Its infrastructure logs also record request metadata including IP addresses.
- Stripe — payments. Stripe receives your email address and your user id, and holds the subscription or purchase record. Card details are entered into Stripe's own screens and go to Stripe directly; they never reach our servers. If we later correct the email address on your account, the address already at Stripe is not changed: a payment record keeps the address the payment was made with.
- Expo — pop-up notifications. To deliver one, Expo's push service receives the push token of each phone or tablet it is going to, plus the notification itself: a title, a line of text, which kind of notification it is, a reference to the group and the screen a tap opens. The title is the group's name, except on a report alert, which says that content or a member was reported. The line of text depends on the kind: for group chat, the sender's display name and up to 140 characters of the message text, or that they sent a photo, GIF, video or file; for a check-in, the display name of the member who checked in and the name of the challenge they checked off — "Maria completed SOAP", for example; for a lead change, the display name of the member who took the lead in the group this week; for a new member, the display name of the person who joined; and for a report, the display name of the member who was reported, or whose message was, and the reason chosen. The check-in alert is the one to weigh, and we would rather say so plainly. A check-in is a record of your religious practice or fitness activity, which this policy treats as sensitive, and its alert carries that record into the Notifications list of each member of your group whose check-in alerts are on and — through Expo, and then Apple or Google — onto the phones that hold a push token for their account, which can include a phone somebody else now uses; depending on each phone's settings, it can show on the lock screen. Those members can already see your check-in progress and points in the app; the alert also tells them which challenge you checked off, and when. Whether they also get an alert depends on their settings, not yours: the app has no switch that keeps your own check-ins out of other people's alerts, although no alert passes between you and a member either of you has blocked, except a report alert. Expo also issues each push token: to get one, the app sends Expo that phone's Apple or Google push address and an identifier for that installation, so Expo also sees the phone's IP address. The app does that each time it signs the phone up for pop-ups — when you sign in, each time it starts while you are signed in, and when you turn Pop-ups on this phone on — and again whenever that push address changes and whenever it needs the token to delete it.
- Apple (APNs) — the same notification, downstream of Expo, so that it can reach an iPhone or iPad.
- Google (Firebase Cloud Messaging) — the same notification, downstream of Expo, so that it can reach a phone or tablet that is not an iPhone or iPad. To get the address a notification is sent to, the app on such a phone also registers with Google's service directly, which gives Google an identifier for that installation.
- Cloudflare (Turnstile) — the "are you human?" check on the registration form. Cloudflare receives your raw IP address, the challenge token and information about your browser or in-app web view. We keep only a truncated hash.
- Expo (EAS Hosting) — that human check, and the player for the Library's videos, each load a page we host with Expo, so Expo's hosting sees your IP address and user agent when they do — but not which video you open, because the part of the player's address that names the video is never sent to a server. On the web version, Expo's hosting also serves the app's own files, so if you read a Bible translation other than the World English Bible it can see that your browser downloaded that translation's text — a single file holding the whole translation, so the download itself never says which book or chapter you read. A video's own page on our website is different: its address does name the video, so if you open that address directly — from a link, or by reloading the page — Expo's hosting receives it, as it receives any address you open on our website.
- AudioTreasure (audiotreasure.com) — the source of the World English Bible audio, which is what plays for every translation except the Berean Standard Bible. When you press play while reading any other translation, that host receives your IP address, your user agent and which chapter you are playing. Nothing else about you is sent.
- Open Bible (openbible.com) — the source of the Berean Standard Bible audio. When you press play while reading the Berean Standard Bible, that host receives your IP address, your user agent and which chapter you are playing. Nothing else about you is sent.
- Our email provider — the email service configured on our Supabase project. It delivers the confirmation code sent during registration, so it receives your email address and name. It also delivers our moderation alert when a message is reported, which carries the reported message's text and caption, the reason that was chosen, the report's own reference, the group it was posted in, the time it was filed, the display name and account id of the person who posted the reported message, and the name and storage path of any photo, video or file attached to it. It does not carry the name or the account id of the person who filed the report, and it does not carry what they typed about it. When a member is reported, the alert carries the reason that was chosen, whether the report is about their profile photo or how they act, the report's own reference, the group, the time it was filed, the display name and account id of the member reported, the display name and role in the group they had when it was filed, and the storage path of the profile photo they had then — not the photo itself, and not a link to it. It does not carry the name or the account id of the person who filed the report, or what they typed.
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:
- Your profile, your streak and every check-in you have logged are deleted.
- Every message you have sent is deleted, and the photos, videos and files you uploaded are removed from storage.
- Your profile photo, if you added one, is removed from storage.
- Your notifications, your notification choices and every device's push registration are deleted.
- The phone number and date of birth on your account, and your Phone & Email choices, are deleted.
- Your spiritual gifts assessment goes with your profile: your answers and every completed result, including every earlier attempt, are deleted.
- Your library reading progress and your Bible highlights are deleted.
- Your name, email, phone number and date of birth are erased from the church registration record.
- If you lead a group, leadership passes to another member. If nobody else is in it and it belongs to a church program, the group stays in place, without a leader, for the church to reassign. If it is a personal group with nobody left in it, it is deleted.
- If you pay Freedom Church monthly, deleting your account cancels that plan at Stripe, and no further payments are taken. A month already paid is not refunded.
- If you have an older subscription with us — one Challenge App LLC sold before we stopped selling — deleting your account may not stop it. We changed payment processors after those were sold, so write to admin@challengeyourfaith.com and we will cancel it by hand and confirm. The remainder of the period is not refunded. This does not apply to a monthly plan with Freedom Church, which deleting your account does stop.
- Your church registration seat stays used up. This is deliberate: erasing an account does not mint a free seat. If you want to come back, your church has to issue you a new code.
These survive on purpose, and you should know about them:
- A short system line noting that you left — only in a group you lead, and only when leadership passes to another member. It carries the display name you were using. It is part of the group's record and no control in the app removes it. Deleting your account posts no such line in a group you are simply a member of: your messages go with your account and nothing is posted in their place. Lines that were posted about you earlier are a different matter — see the next point.
- Short system lines other people posted about you. When an administrator or church staff member adds you to a group, moves you from one group to another or makes you a group's leader — or when one of them removes you from a group, which that group's leader can also do — the app posts a line in that group saying so, and a move posts one in each of the two groups. Those lines are recorded as posted by whoever made the change, not by you, so deleting your account does not remove them: each carries the display name you had when it was posted and stays in that group's history.
- Notifications other members received that name you. Each keeps the display name you had when it was sent, and what it said: up to 140 characters of a message you sent, a challenge you checked off, that you took the lead in your group that week or joined a group they lead, or — for a group's leaders and our administrators — that you or a message of yours was reported, and the reason. Those notifications belong to the members who received them, so deleting your account does not remove them: each can stay in that member's Notifications list until they clear it, their own account is deleted or the group is deleted. Pop-ups already shown on their phones are outside our control.
- An audit record that a deletion happened, identified by the account id you had. It holds no name and no contact details. We keep it so that we can show a deletion was performed.
- Records of changes our administrators and church staff made to your account or your groups. That an administrator created your account, if one did. For a correction, which only a system administrator can make: which of your first name, last name and registration phone they changed, and when, with — when the phone changed — their note of how they checked the change with you; or, for an email correction, the old and new address masked and their note of how they checked it with you. For your groups: which ones you were added to, moved between, made the leader of or taken out of while organising groups, and when — and, if one of them made somebody else the leader of a group you led, the display name you had then. They carry your account id, like the deletion record.
- A registration you started on a church's registration page and did not pay for. It is not part of your account, so it keeps what you typed into that page until one of our system administrators deletes it or a new checkout replaces it, as described under "How long we keep things" above. Write to us and we will delete it once its time for paying has run out and any checkout it had has closed.
- The church's payment and consent records for your seat. What was paid at checkout and when, and — for a monthly plan — the record of what you agreed to, described under "Things about your access" above. They hold no name and no contact details, and yours are erased from the registration record they belong to.
- Stripe's own records. Stripe keeps its record of each payment, with the email address it was made with, and — for a monthly plan — its customer record and invoices. Deleting your account does not delete them.
- A spreadsheet one of our system administrators downloaded before you deleted your account. A list of accounts keeps your row, with whichever details it was downloaded with — your name, email address and registration phone, for example, and always the account id the records above carry. A week's results for a group you were in keeps your name, whether you led the group, and your points, completion and rank that week, with how that rank changed — but no account id. Either stays until we delete the file, and any copy we shared with your church's leaders, within 90 days of downloading it. Write to us and we will delete it sooner.
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:
- give you a copy of the personal information we hold about you;
- correct anything that is wrong;
- delete your account and its data.
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