Skip to the document
Thrive Church
Contents

Thrive Church App: Privacy Policy

Last updated 最後更新:2026-11-21 Version 版本:1.9.9

Applies to: the Thrive Church member app (iOS and Android, and any web or computer version of it that we offer), the staff web admin, and the church web pages that go with them (the web forms, the account deletion page, and these documents). 適用範圍: Thrive Church 成員 App(iOS 與 Android,以及我們提供的任何網頁版或電腦版)、同工使用的後台網站,以及與之搭配的教會網頁(網頁表單、刪除帳號頁面,以及這兩份文件)。

Languages. This policy is published in English and Traditional Chinese. The two versions are meant to say the same thing. If they ever differ, the English version governs.

語言。 本政策以英文與繁體中文發布。兩個版本的內容應為一致。若兩者有任何歧異,以英文版為準。

THE ESSENTIALS | A QUICK GUIDE

This guide highlights important points. The complete policy below governs and includes exceptions.

We collect information needed for church community, prayer, events, messaging, care, giving, and app administration. Not every feature is active today.

Your profile, group records, messages, and prayer information have different access rules. Ordinary staff do not read direct messages, but the Safeguarding Officer has exceptional, logged access for safety or legal reasons.

Anonymous prayer posts hide your name from ordinary readers, not from every internal record. Some leaders or servant team members can record attendance and care notes about you.

Data may be handled outside Taiwan. Deleting an account does not instantly delete every record. Specific financial, safety, and other records may remain.

Routine changes to features already covered by this notice do not require you to accept the Privacy Policy again. We publish policy updates and provide additional notice or seek specific consent where the law requires it.

Questions and privacy requests: app@thrivetaipei.com

1. About this policy

This policy explains what personal data the Thrive Church app collects, why we collect it, who can see it, how long we keep it, and what rights you have over it.

Taiwan's Personal Data Protection Act (the PDPA) is the law that governs how we handle your data.

This policy is also the notice the PDPA requires us to give you when we collect your data: who we are (section 2), what we collect and what happens if you do not give it to us (section 3), what we use it for (section 4), who receives it (sections 5 and 7), where it is stored and for how long (sections 8 and 9), and your rights and how to use them (section 11).

2. Who we are and how to contact us

社團法人興世代教會 (Thrive Church) ("we", "us") is responsible for the personal data in this app. Under the PDPA we are the non-government agency collecting and using your data.

  • Registered address: 4th Floor, No. 98, Section 3, Xinsheng South Road, Da'an District, Taipei City
  • Website: https://www.thrivetaipei.com/
  • Privacy questions and requests under section 11: app@thrivetaipei.com
  • Safety concerns, reports, or anything involving a child: patrick.ng@thrivetaipei.com
  • Giving, receipts, and your ID number: finance@thrivetaipei.com

We answer requests to see or copy your data within 15 days, and requests to correct, complete, or delete it within 30 days. If we need longer, the law lets us extend each of those once by the same amount again, and we will write and tell you if we do.

3. What we collect, and why

The categories below describe the types of personal information Thrive collects for the identified church and app purposes. Examples illustrate how a category may be used; they are not an exhaustive inventory of screens or features. A later feature is covered only when its actual collection, purpose, recipients, access, location, and retention remain within the disclosures here. The fact that a feature is foreseeable does not authorize a materially different use or replace a notice or consent required by law.

  • Identity and contact details, such as your name in English and Chinese, your email address, phone number, and LINE ID, your profile photo, and how your name is printed on a name tag.
  • Personal details, such as your gender, your birthday if you give one, and whether you are recorded as married.
  • Your place in the church, such as whether your account is approved, whether you are an attendee, a member, or an inactive member, your role, your family group, the ministry teams and interest groups you join, your attendance, and staff follow-up on forms you send. It also covers people who come to a family group but have no account, whom a leader or staff member lists (section 3.2).
  • What you write, share, and upload, such as messages, prayer requests, photos, videos, stickers, and files, poll votes and event RSVPs (with the names of anyone you add as coming with you), form answers, space requests, notes, your prayer journal, and reading progress.
  • Care and safety records, such as care and benevolence requests, care notes, reports, blocks, and preservation holds.
  • Giving and tax receipt details, such as donation records, the last few digits of a bank account, and, only if you ask for a tax receipt, your national ID or ARC number.
  • Staff and volunteer records, which exist only for paid staff and for some volunteers: working hours, overtime applications and decisions, comp time (time off saved from overtime), leave and how unused leave is carried forward or paid, pay rates, payroll (each month's pay and paystub, insurance, pension, and tax details, and, for government filings, an ID number, date of birth, and home address), reimbursement requests posted in the church's Teams finance channel, the terms of employment including the days off each person sets, and a record that required checks and briefings were completed (section 3.10).
  • Technical information about your device and the app, such as the app version and which app update it is running, the platform, the device model, a notification token, a random ID the app makes for each installation, your notification settings, when your device last opened the app or reported to us, the key that a staff member's clock-in widget uses on that device (section 3.9), and the IP address a request comes from, which our hosting provider's logs record (section 3.11).
  • Records that keep the app running and safe, such as which version of these documents you agreed to and when, earlier versions of your name tag and receipt details, audit logs of administrative actions, message and posting timestamps used for rate limits, a record that you left a church-wide room so the app does not re-add you, and a short-lived queue of pending notifications.

When the app changes. We may add, change, or remove features without asking you to accept this notice again if their collection, purposes, recipients, access rules, processing locations, and retention remain within what this policy already discloses. An interface change or new feature name alone does not create a new consent requirement. We review changes that fall outside the existing disclosures, give any additional notice required by law, and obtain separate consent before the affected processing where required. Earlier acknowledgment does not authorize unrelated uses or protected information processing.

If you do not give us something. You need an email address and a password to have an account. Everything else you are asked for is optional. If you leave something out, the usual result is that the feature that needs it does not work for you: without a birthday you are not on the birthday list, without an ID number we cannot file a tax receipt for you, and without your name staff may not be able to recognize you when they review your account. Some records, such as attendance, are kept by leaders and staff rather than given by you.

3.1 Your account and profile

To create an account we collect your email address and a password. Passwords are handled by our login provider and we never see them. Staff accounts that use the web admin also set up a second sign-in step, a code from an authenticator app, which our login provider handles. We record which version of this policy you accepted, and when.

A short onboarding form then asks for your name in English, Chinese, or both, how you would like your name printed on a name tag, your gender, and optionally your phone number and LINE ID. It also asks whether you are in a family group or would like to join one, and whether you are a member or would like to know more. Your answers to those last two are used to flag you for staff follow-up; saying you are a member does not make you one in our records, as staff confirm that separately.

We use this to know who you are, to let other members find you, to let leaders reach you, and, in the case of gender, to decide which gendered family group rooms you can see. Your name, and the way you want it printed on a name tag, are also sent to the welcome desk's name tag records in the church's staff-restricted Google Drive, so that the right tag is ready at the door (section 7).

You can skip the onboarding form, and if you do, none of it is collected. Gender cannot be answered separately from the rest of the form, and the later "Update my info" screen does not include it, so if you skip the form or want your gender, family group, or membership answer changed, email app@thrivetaipei.com and a staff member will set it for you.

Profile photos. If you choose a picture, we store it. It is kept in a private area of our hosting provider's file storage and shown to signed-in members alongside your name. An earlier version of this policy said we stored no profile photo for anyone and promised to update this policy first if that changed. This is that update.

Language and appearance. Your choice of light or dark mode, your text and reading settings, and the emoji you use most for reactions (the app learns them for your quick row) are saved on your own device only and never sent to us. Your choice of English or Chinese is also sent to us, so that notifications and reminders reach you in your language.

Staff record, about you rather than by you: whether your account is approved, whether you are an attendee, a member, or an inactive member (someone who joined as a member and is no longer at Thrive), your role, and which family group you are placed in.

Whether you are married. Staff record this for one purpose only: deciding whether the option to see giving combined with a spouse is available to you. It is a yes or no, not a marital history, because that single question is all the feature needs. Other members never see it. If it is wrong, ask any staff member to change it.

Your birthday, if you choose to give one. It is optional everywhere it is asked, and nothing in the app requires it. You can give the day and month only: the year is a separate choice, because the year is your age and the birthday list does not need it. It is visible to you, to staff, and to the leaders of your family group, so they know when to wish you happy birthday. It is not shown to the congregation. Leave it blank and you do not appear on that list, unless a leader has noted a birthday for you, as described next. You can remove the one you gave at any time from Profile, then My Info.

A birthday a leader noted. A family group leader, or a staff member, can note a birthday they have learned for a member who has not given one, as a private reminder for the group's leaders. It is kept apart from your profile and shown only to the group's leaders and to staff. You are not shown it and not notified. It is deleted when you enter your own birthday or delete your account.

3.2 Your family group

If you join a family group we store your membership of that group and your role in it.

Your leader can record attendance at each meeting, optionally with a reason and a note. This is recorded by your leader about you. Repeated absence shows up in a staff list so someone can check in on you.

Your group's servant team (its leaders, co-leaders, and helpers) can keep care notes about you, so they can care for you well and follow up: how you are doing, something to pray about or celebrate, or a practical need. Each note is either shared with the servant team or kept only by the person who wrote it, and it can carry tags and a reminder date for its writer. The team can also keep a short summary about you. This is recorded by them about you, and it includes people in the group who do not use the app.

Leaders and staff should record only what is reasonably needed for attendance, follow-up, and care, and avoid unnecessary speculation or sensitive details about another person's private life. If information comes from someone other than the person concerned, we will give any notice required by law or rely on an applicable legal exception. You can ask about records concerning you and exercise applicable rights by emailing app@thrivetaipei.com (section 11).

We also store photos and videos uploaded to your family group with their captions, and the meeting location, which is often somebody's home and may include access details such as a door code.

People who come to a family group but have no account. A leader or a staff member can keep a list of people who come to a group but are not in the app, and can note visitors. For a person on the list we keep only their name (in English, Chinese, or both) and whether they were present or absent at each meeting, with a reason for an absence if one is given. For a visitor we keep their name, who brought them, and when they came. That attendance and visitor list contains no phone numbers, email addresses, or care notes. Separately, a family group servant team may keep care notes about a person without an app account under the distinct care-note arrangements described above; those notes have their own access and retention rules. The members of the group can see the names on their group's list; only the group's leaders and staff can see attendance and visitors. When a person on the list creates an account, a leader or staff member can join the two so their history follows them. Attendance follows the schedule in section 9, a visitor is deleted after about a year without coming, and a name taken off the list and never joined to an account is deleted once no attendance record needs it. If your name is on a list like this and you want to see or remove it, email app@thrivetaipei.com.

3.3 Messages

The app has several kinds of messaging and they are not protected the same way. Section 6 explains the differences, and it is worth reading.

  • Direct messages, group chats you create, and family group rooms. We store the message and any attachment, who sent it, when, what it replies to, whether it was forwarded, and reactions.
  • Church-wide rooms, such as Announcements, General, Thrive Friends, the interest rooms, and ministry teams. These are open rooms, not private ones: everyone in the room can read what you post, and a member who joins later can read everything the room has ever said, with its photos and files. Some rooms add every approved member automatically; Thrive Friends, the chat for the whole church, is one of them. You can leave a room like that or mute it at any time. If you leave, we keep a note that you did, so the app never adds you back, and you can rejoin whenever you choose.
  • Messages to the staff team. A separate conversation between you and the staff team as a whole.
  • Unsent messages. You have a short window to withdraw a message you sent. Section 6.1 explains what withdrawing does and does not do.
  • Edits, mentions, and read receipts. If you edit a message, the earlier text is kept, and only the safeguarding officer can read it. If you @mention someone, they are notified. Read receipts are off unless you and the sender both turn them on in Settings; then the sender can see that you have read their message. Typing indicators are shown live and are never stored.
  • Polls, notes, and weekly prayer lists in a room. A poll stores its question and choices and who voted for what, and everyone in that room can see the votes. A room can also keep a notes board for standing facts, such as a meeting address, and a family group room can open a weekly prayer list that the people in the room add their requests to; a leader can add a request for someone who shared it in person or is not in the app. Everyone in the room can read its polls, notes, and prayer lists. Polls and prayer lists go when the message that carries them goes (section 9); a prayer list is carried by the card that opened it, so if the person who started it deletes their account, the list goes too, with every entry in it (section 11). Notes stay with the room until someone removes them, and if their author's account is deleted, only the author's name is removed (section 11). No prayer list is ever copied to the staff prayer list, and being staff gives no extra access to one.
  • Translation. So that members can read one another in English and Chinese, the words of a message, a post, a note, a poll, a prayer list request, and a message to the staff team can be sent to our translation service (section 7) and shown in the other language. From October 18, 2026, the same goes for posts and written prayers on the Prayer and Praise Wall, and staff can have the words of a care request sent on or after October 18, 2026 translated (section 3.7). Staff can also have the words of a sermon response form translated (section 3.6). Only the words are sent, never the name beside them or anything else from your account. An anonymous post is sent with nothing that says who wrote it. The translation is stored once beside the original, so everyone who can read the original sees the same one without it being sent again; it is deleted when the original is deleted or hidden, and replaced if the original is edited.

Stickers you make, share, and suggest. If you make a sticker from one of your photos, we store the cropped picture and the short caption you add. They are kept in your own list, My stickers, so you can send the sticker again. Only you can see that list. Another member sees a sticker only because it was sent in a conversation they can read, and it is shown like any other attachment.

When you make a sticker, Let others save this is on unless you turn it off. While it is on, another member who sees your sticker in a conversation can save it. A save is a link to your sticker, not a copy of it. The member can send it from their own Saved list, but cannot change it or take it out of the app, and the app offers no public link and no way to save it to the phone's photos. Anyone can still take a screenshot of their own screen. You can see how many people saved a sticker, never who. If you turn sharing off or delete the sticker, it disappears from everyone's Saved lists. Messages that already used it keep showing it, unless you also choose to remove it from chats.

You can also suggest a sticker for a church pack. Staff who review suggestions can see the picture, its caption, and your name. If staff choose it, we keep a separate copy as a church sticker that everyone can send, stored with the church's other published images (section 10), together with a record of your permission, your name as it was then, and the date. That copy stays when you delete your own sticker or your account, because it is then the church's sticker, and the church can remove it at any time.

A staff member cannot browse stickers, only the suggestions that members send. The safeguarding officer can open a sticker that someone reported. Stickers you make are kept by our hosting provider, not in Google Drive, and the app removes the photo's hidden details, such as its location, when it makes the sticker. The church's own stickers are the church's artwork and hold no information about you.

Some messaging features are not currently enabled. When we enable a feature, the disclosures in this policy apply to its information practices. We will provide additional notice or seek consent before launch if its practices fall outside what this policy already describes or the law requires it.

3.4 Prayer

We store posts on the Prayer and Praise Wall, including whether you chose to post anonymously; who prayed for a post or gave thanks on it (the Praise God button), and their reactions; the written prayers people leave under a post; the requests you follow, so that we can tell you when someone writes a prayer on one; and any blocks you place on another poster. Who prayed, who reacted, and who wrote a prayer are shown by name to everyone who can open the wall, unless that person chose in Settings not to be named, in which case the app says "Someone". Posts drop off the wall after about a week, but the record is kept, and written prayers stay with their post. See section 9. Posts on the church-wide prayer wall, and prayer requests you chose to share on a sermon response form, are also copied to a staff prayer list. See section 7. In this policy, a prayer request or a prayer wall post includes a praise report (a thank-you to God that you share in the same way), and it is treated the same way for anonymity, reporting, blocking, and deletion, and for what you choose to share on a response form. The one difference is that a praise report posted straight to the wall is not copied to the staff prayer list. From October 18, 2026, the words of a post on the Prayer and Praise Wall, and of a prayer written under one, can be sent, with no name beside them, to our translation service (section 7) so that they can be shown in the other language to anyone who can read them. An anonymous post is sent with nothing that says who wrote it, and a choice not to be named is honored here too.

3.5 Your private study material

Sermon notes, your prayer journal, reading plan progress and the chapters you have read (for your Bible map), reflections, saved verses and highlights, memorized verses, and bookmarks.

Nobody else can read any of it: not other members, not your family group leader, not staff, and not the safeguarding officer.

One exception: reading progress inside a family group is shared with that group, so everyone in your group can see who has finished which chapters.

The words you write here can also be sent, with no name beside them, to our translation service (section 7) so that they can be shown in the other language.

3.6 Forms you fill in

Connection cards, membership class and baptism interest, retreat signups, sermon response forms, and similar. Between them these collect your name and contact details, your answers to the questions asked, and anything you write in your own words. A connection card can be submitted by a visitor who has never signed up.

Translation of a sermon response. So that every member of the staff team can read a sermon response form, a staff member can have its words translated into English or Chinese: your reflection, your prayer request, your praise report, and a next step you wrote in your own words. This applies to any response, including one sent before October 24, 2026. Only those words are sent to our translation service (section 7), never your name, your LINE ID, the next steps you ticked, or your choices about sharing, and a staff member can translate only the parts they are allowed to read (a private prayer request stays readable only by the person who handles private prayer requests).

Event sign-ups and other church forms. Some church events and surveys use a form built in the church's form builder. You can fill one in inside the app or, if the church makes it public, on a church web page without an account. Each form tells you at the top who is collecting it, why, who can see it, how long it is kept, and where it is stored. For each form we store the answers you give; the name, email address, phone number, and LINE ID the form asks for; your party size, if it asks; whether your place is confirmed, on a waiting list, or canceled, and when each of those changed; and any note or tag staff add. A form may also let you add photos or PDFs, if you are signed in (the public web page does not take files). Those files are kept privately by our hosting provider, not in Google Drive. Only the staff who can read that form's responses can open them, and you cannot open them again in the app. A file is deleted when you cancel your sign-up, when staff cancel or delete it, when the form's retention period deletes it, when you remove the file, and when your account is deleted; the file's name stays in your answers until the form's retention period ends. A file you add but never send is deleted after 14 days. Pictures that staff put on a form, such as a banner, are public: anyone who can open the form, or who has the picture's address, can see them. If you sign up without an account, you get a private link to change or cancel your sign-up. If you gave an email address, the church may also email you a confirmation, a reminder, or that link (section 7). The link stops working when the event starts, or after about six months for a form with no event. We keep only a scrambled version of its code (a hash). The web page also remembers your sign-up in your own browser, so you can come back to it, and your browser sends it to us only when you change or cancel the sign-up; clear that browser's site data to forget it. A public form can run Cloudflare's security check, and counts requests by a scrambled version of your address, as section 3.11 describes.

Staff read form responses: all staff by default, or only the staff a form names. Other members never see them; members see only totals, such as spots left. A form's responses are deleted 6 months after the event for a sign-up (6 months after the form closes, if there is no event), 12 months for a survey, or at a different time that form states, and never more than 24 months after you submit (section 9). If you want yours removed sooner, email app@thrivetaipei.com; staff can find every sign-up under your email address, phone number, or account and delete them together. Staff can download a form's responses as an Excel or CSV file, and can copy them into a file in the church's Google Drive (section 7). If staff choose, an export also includes links to the files people added; they work for 1, 3, or 7 days, and stop sooner if the sign-up is canceled or deleted. A downloaded file is outside our database, the nightly deletion does not reach it, and a download cannot be recalled. A copy in Google Drive is deleted when the form's answers are, and sooner if staff delete it.

Family group signup can happen in more than one place, and the app decides which. One is a signup form inside the app: your answers are stored in our database like the other forms on this list, staff read them there, and the retention rules in section 9 apply. Another is a Google Form, which opens instead if you are not signed in (unless the church has opened the web form described below to everyone), if your version of the app is older than the in-app form, or whenever the church chooses to use it. The church may stop using the Google Form at any time; if it does, what is said below about the Google Form simply stops applying. What you write in a Google Form goes to Google, and staff read it in the form's response sheet. Your answers are not held in our database, so the retention rules in section 9 do not reach them. When a response arrives, though, a small script in that sheet tells our database that it did, so staff are alerted only when someone has really finished the form. It sends only the time of the response and the email addresses and phone numbers typed on the form. We keep the time and which account the response matched. If no account matched, we also keep that email address or phone number, so staff can find you, until staff match it to an account or you ask us to remove it. A response made in the in-app form or the web form leaves the same note on the same terms, and its answers follow the retention of the form that took them. See section 7. The church may also run the family group signup as a form on a church web page that anyone can fill in without an account; that works like the event forms described above.

Staff also record follow-up attempts based on these forms: who contacted you, when, how, what happened, and a note.

Fees. A form for an event with a fee may tell you how to pay by bank transfer and ask for the last few digits of the account you paid from, so staff can match your payment. Forms do not ask for a national ID, passport, or card number (the form builder refuses to publish a question that does), and the app does not take the payment.

Space requests. Approved members can ask to use a space at the church. We store the space, the date and time, how many people are coming, a short event name, what it is for in your own words, and what staff decided, including any note or reason they give you. Any staff member can see and decide your request. You hear the answer by a notification and in your conversation with the staff team. The person booking and staff can see the event name. Other members never see who asked, what the event is called, or why: once a request is approved, they see only that the time is taken. To keep the church's calendars in step, the space, the time, and the event name of an approved reservation may be copied to the church's own Google Calendar, and times already on those calendars may be read so the app can show when a space is free (section 7). The event name is free text that the person booking writes, so write nothing there that you would not want on a staff calendar. The copy never shows what the event is for, and never shows the name or contact details of the person who booked it. The church keeps these calendars for staff, and other members still see only that the time is taken. The event name follows the same rules as what the event is for: it is erased 12 months after the time you asked for, and on day 30 if you delete your account, and the name on the calendar copy is erased then too (section 9). A calendar copy is deleted when a reservation is canceled. If your account is closed, marked as departed, or returned to pending review, or you ask to delete it, any request still waiting for a decision is canceled at once. After a booking ends, we may ask you how it went. If you say everything is done, we keep that, which items on the Before leaving list you ticked, and when. If you report a problem, we also keep the note you write and the one photo you may add. Only you and staff can see them, and other members never do. The note and the photo are erased 12 months after the booking ends, and on day 30 if you delete your account (section 9).

3.7 Care and benevolence requests

If you ask the church for help we store the type of need you selected, your description in your own words, how urgent it is, how you want us to contact you, and whether you agreed to share it with your family group leader.

Staff then keep a contact log about your case, including their own notes.

Translation. So that every member of the staff team can read a request, a staff member who can read it can have its words translated into English or Chinese. This applies only to requests sent on or after October 18, 2026; a request sent before then is never translated. Only the words you wrote in the description are sent to our translation service (section 7), never your name, your contact details, who the request is for, or any note staff keep. Care requests can hold health information, so read the paragraph on medical and health information in section 4.

Requests cannot be submitted anonymously. Your name is always attached.

3.8 Giving and tax receipts

If you record a donation we store the date, amount, currency, purpose, and the last few digits of your bank account.

If you want a Taiwanese tax receipt filed on your behalf, we ask for your name for the receipt, mailing address, contact details, and your national ID or ARC number. This is entirely optional and used only for that purpose.

We also import a spreadsheet exported from the church's accounting software and match transactions to members. For each transaction it holds the date, the amount, what the gift was designated for, the donor's name as the accounting software recorded it, and the last digits of the bank account it came from. Finance staff match transactions to members by that name and account, confirm or change a match by hand, and can mark a gift as from an unidentified giver, with a reason, when nobody can say whose it is. That file may contain donors who do not use the app, and payments that are not gifts, such as retreat fees.

3.9 Your device and the app

We keep a small amount of technical information about your device and the app on it, and only what these features need. If you allow notifications we store a token for your device, your device model, the platform, and your notification preferences and quiet hours. Whether or not you allow notifications, we also store which version of the app each device you sign in on is running, and its platform, so we can tell when an update has reached you. For that we also keep three more things. The first is a random ID the app makes for itself the first time it runs. It identifies that installation of the app, not you; it is not an advertising ID; it is not made from anything about you or your phone; and it is never shown to anyone, staff included. The second is which app update the device is running, with the date it was published and whether it is the version that came with the store download. The third is when the device last reported, which happens when its version or update changes and at least every 30 days. We use this information to deliver notifications, to keep the app working on your device, and to know when an update has arrived, and never to track you or what you do in the app. Staff can see, on the admin website, which version and platform each person's devices run (only devices that have opened the app in about the last 60 days appear), so they can help someone whose app is out of date, and totals of how many people opened the app in the last 7 and 30 days. The totals name no one.

What a notification shows. A notification for a chat message names the chat (and the family group or topic it belongs to), the sender, and the first part of the message, as section 7 explains. When you read a chat on one iPhone or iPad, the app may send your other iPhones and iPads a silent update that changes only the number on the app icon; it carries no message text.

Home screen widgets. If you add one of the app's widgets (for example this week's memory verse, today's reading, or, for staff, clocking in and out), the app saves a small snapshot of what the widget shows, such as the verse, the reading and your streak, or whether you are clocked in, in a place on your own device that the widget can read, and it removes the snapshot when you sign out. Anyone who can see your home screen can read a widget. A widget holds no sign-in. The staff clock-in widget also uses a key the app makes for that device, which lets the widget show whether you are clocked in and clock you in or out, and nothing else. We keep only a scrambled version of the key (a hash), with a random ID for that installation and when the key was last used. The key stops working when you sign out, after 60 days, or when your employment ends.

3.10 Safety and administrative records

  • An audit log of administrative actions: who did what, to what, and when. It does not record message content.
  • A rate limit log: a timestamp each time you send a message, file a report, or post a prayer request.
  • Reports you file about a message, which include a frozen copy of that message.
  • Problem reports: if you use Settings > Report a problem, we keep what you write, up to 3 screenshots you choose to add, and basic details about your app (version, device type, the screen you were on, and language) for 180 days. Unless you untick them, the report also carries the app's recent error codes, each with the screen and time it happened and never anything you wrote; until then the app keeps them only on your device, for up to 7 days. Only staff can see reports, and they are deleted with your account.
  • Safeguarding flags and preservation holds. See section 6.6.
  • Staff and volunteer records. These exist only for paid staff and for some volunteers. For paid staff: the times you clock in and out (in the app or with the home screen widget) and whether overtime was asked of you, with any request to correct a clock record and the correction made; your overtime applications, which hold the days and minutes asked for, your reason if you give one, whether you want the hours paid or saved as time off later, and who decided, when, and with what note; your own statement, if you say that time past 8 hours was not work, with the minutes it covers and any words you add; your comp time (time off saved from overtime), which is the hours saved from each day, when they expire, the leave that used them, and any unused hours that were paid out (the hours at each rate, the hourly wage used, the amount, the date paid, and who recorded it); for each day with overtime, how its minutes were counted and whether they were paid or saved, with the hourly wage and overtime rates used, frozen when a month is locked for payroll; pay for work past 12 hours of a day, which HR may pay with a note, recorded with who decided and when; the two weekdays you set as your days off, which of them is your full day off, who set them and when, and, if you chose a Sunday, the approver's decision and note; the leave you ask for and take, in days or hours, including the kind of leave (such as sick, hospital, family care, or maternity leave), any note you add, and who decided the request; what happens to unused leave at the end of a leave year, which is either an agreement to carry it forward (the date each side signed and where the signed paper is kept) or a payout (the hours, the daily wage it was based on, the amount, and the date paid); your pay rate, which is an hourly wage (or the monthly salary it was worked out from) and the date it applies from; and the terms of your employment, such as job title, full-time or part-time, start and end dates, daily and weekly hours, rest days, and probation. For paid staff and some volunteers: the date a required check or briefing was completed, such as a suitability declaration, a police clearance certificate, or a harassment prevention briefing, with a pointer to where the document is kept and never the document itself. Only the person concerned, super admins and others a super admin has given HR access, and the people who approve staff leave and overtime (who see only what each decision needs) can read them, with three exceptions. Only people with HR access can read pay rates; the people who approve leave and overtime never see them. The words you add to a statement that time was not work can be read only by you; HR sees the days and the minutes. HR's note on pay for work past 12 hours can be read only by people with HR access, and you see that the time was paid. Other members and ordinary staff cannot read these records. Taiwan's Labor Standards Act requires the church to keep working-hour, overtime, wage, and leave records for five years, so these records, comp time included, are kept at least that long, and they stay, under the name they were filed under, when an account is deleted (section 11).
  • Payroll. For paid staff, payroll also keeps: each month's pay and how it was worked out (salary, allowances, overtime, deductions or payouts for leave, and one-off amounts such as a bonus or a correction, each with its reason); the amounts taken out for labor insurance, employment insurance, health insurance, any pension contribution you choose to make, and income tax; what the church pays on top for your insurance and pension; your paystubs; which insurance and pension schemes you are in and the insured amounts the government has on file; your tax residency, how tax is withheld from your pay, and how many dependents are on your health insurance (a number, not their details); and, so the church can make the filings the law requires with the Bureau of Labor Insurance, the National Health Insurance Administration, and the tax authority, your legal name as filed, your national ID, resident certificate, or passport number, your date of birth, your home address, and, if you are not a Taiwanese national, your gender. Only you and people with HR access can read your pay and paystubs. Only people with HR access can read your identity details, which are shown masked, and each time one of them shows them in full is recorded. Those details go only into the files HR sends to those agencies, never into a notification, a paystub, or the church's accounting software. Payroll records are wage records, so they are kept for five years like the rest of this section (section 9).
  • Reimbursements. Reimbursement requests that staff post in the church's Microsoft Teams finance channel, with their receipt photos, are copied into the staff web admin so finance can check them and record them in the church's accounting software. The words of a request and its receipt images, never account details, are sent to our AI provider (section 7) to fill in the amount, date, and purpose for finance to check. Only people with finance access can read them, and they are kept for five years after the year they are paid as accounting records; a post that is not a request is deleted after 90 days.
  • The church door. Staff, and people staff choose, can unlock and lock the church door from the app, and staff can also do it from the staff web admin. For this we keep who may open the door, who gave that access, and when; your own door code, if you have one, whose digits only you can read, in the app (staff never see them); every unlock, lock, and change made through Thrive, with who made it and when, but never a code's digits; and, if staff link one, which person a card or fingerprint belongs to. Cards and fingerprints are added at the door with TTLock's own app, and a fingerprint stays in the lock; Thrive never receives it. Before the app unlocks the door or shows your code, your phone asks you to confirm it's you with Face ID, a fingerprint, or your passcode. That check happens on your phone, and the app learns only whether it passed. If staff approve a room reservation you made, you can also unlock the church door in the app from 30 minutes before it starts until it ends, and Thrive sends you a keypad code that works only during that time. Staff can also make a code for you, such as a visitor code. Thrive tells you about these codes in a notification and a message in your conversation with staff, with the steps to use the keypad, and shows them in the app; staff can see their digits. Your own door code is never sent in a message. Staff can see who has access, the visitor and reservation codes, and the door's history with names. The history includes the lock's own record of openings, which comes from TTLock (section 7), so staff can see when your code, card, or fingerprint was used. When your access ends, your code is removed from the lock, and a reservation's code is removed when the reservation ends or is canceled. Door history is kept for 12 months (section 9).

3.11 What we do not collect

These are real and deliberate choices, so we want to be specific:

  • No third-party analytics, no tracking, and no automatic crash reporting. There is no analytics or tracking service of any kind in the app, and we do not measure which screens you visit or how long you stay. Error codes leave your device only inside a problem report you send. The church does keep a few simple totals for staff, such as how many people opened the app this week, how many new members joined a family group, and how many people used a reading plan. They are counts, not records of what any one person did, and they never include direct messages.
  • The app does not record your IP address in any of its own features. It is still seen in the ordinary way the internet works: our hosting provider's login system and service logs note the address each request comes from, to keep accounts secure and to investigate problems, and some of the services in section 7 see it when your phone or browser loads something from them (our web host, the security check, our app update service, GIPHY, and YouTube). One thing is kept in scrambled form: to slow down abuse, a few of our server functions (the church's web forms, GIF search, and Bible passage lookup) count requests per one-way scrambled version of the address (a hash), never the address itself, and delete those counters after about two days. Our login provider also keeps the browser or device type of each sign-in, which you can see and sign out of in Settings.
  • No advertising, no data selling, and no data sharing for marketing.
  • No location tracking.
  • No access to your contacts or calendar.
  • Your photo library is read only when you open the attachment sheet, and only if you allow it. Thrive adds a photo or video to your library only when you tap Save. Your camera is used only when you tap to take a photo in the app, and only if you allow it. A sticker is made only from a photo you pick, and a form takes only a photo you pick.

4. What we use your data for, and why we are allowed to hold it

What we use it for. We use personal data only for these purposes:

  • Running and securing the app: creating your account and signing you in, delivering messages, notifications, and app updates, keeping the app working on your device, and protecting accounts and the church from abuse.
  • Communicating with you: replying to you, telling you about your account and your requests, announcing church news and changes to the app or to these documents, and sending the emails your account or your sign-ups need.
  • Church ministry and care: the member directory and family group lists, prayer and praise, following up on forms you send, care and benevolence, space requests and the church's calendars, events, sign-ups, and surveys, serving and ministry teams, name tags, birthdays, and reading and learning together.
  • Everyday church community: chat, polls, photos, videos, stickers, and reactions, and translating words between English and Chinese, including what members write, so that members can read one another and take part in the life of the church through the app.
  • Safety and safeguarding: handling reports, blocks, and preservation holds, and protecting children and vulnerable people (section 6.6).
  • Giving, employment, and legal duties: recording donations, filing the tax receipts you ask for, keeping the working-hour, leave, and employment records of paid staff, and meeting other duties the law places on the church.
  • Improving the app, without analytics or tracking: we learn from what members tell us, including messages to the staff team, and from technical information and simple totals, such as which app versions are in use and how many people opened the app this week. We never measure which screens you visit or how long you stay (section 3.11).

A new feature serving one of these purposes may be covered by this policy without a new agreement when it remains within the data categories, recipients, access boundaries, and retention rules already disclosed. We will give additional notice or seek consent when applicable law requires it.

We do not use your data for advertising or marketing, and we never sell it. If we ever want to use it for a purpose outside this list, we will ask for your consent first (section 13).

How it is handled. Most of this is processed automatically by the app and our servers. Some is handled by people in the roles in section 5, such as staff, family group leaders, and the safeguarding officer, each limited to the access described there.

Why we may collect and use it. The legal basis depends on the information and purpose. This Privacy Policy provides notice, and you agree to it when you sign up or sign in; agreeing to it does not, by itself, authorize every use of personal information. Our bases may include:

  • Your consent. You accept this policy when you sign up, when you sign in, and when we ask you to agree to an updated version. We record which version you agreed to and when. Not every update asks again: section 13 explains when it does. Filling in an optional field is itself a choice to give us that information.
  • Consent where required. When a particular use requires consent, we explain that use and request the applicable consent separately. We keep records of consent where appropriate. Registering, signing in, or reading an updated notice is not, by itself, new consent to unrelated uses. Providing an optional field is your choice, but it does not replace any specific or written consent required by law.
  • Our relationship with you. Running a church you belong to requires a member record, a family group list, and a way to contact you.
  • A specific legal duty. Donation and tax receipt records exist because tax law requires them, and staff working-hour and leave records exist because labor law does.
  • Protecting someone's life, body, freedom, or property. This is the basis for keeping safety records and preservation holds, even when you have asked us to delete your account.

Medical and health information. Members, staff, and family group leaders may share or record information concerning illness, medical treatment, or personal circumstances when requesting prayer, providing care, or following up on church activities. Some information, including information in care requests or attendance notes, may be subject to additional restrictions under the PDPA. Before collecting, processing, or using protected medical or healthcare information, we must identify an applicable legal basis; when written consent is required, we will obtain it separately. Accepting this notice, using the app, or voluntarily entering information does not replace consent required by law. Members and leaders should share only information reasonably necessary for prayer, care, or administration and respect other people's privacy. If a staff member has the words of a care request translated, that happens only for a request sent on or after October 18, 2026, only the words are sent, and they are sent without your name. Access remains limited as described in sections 5 and 6. Ordinary app use does not require medical information.

Staff records are a separate case. For paid staff, leave records may include health-related details. For paid staff and some volunteers, the church records when a required police-clearance check was completed, without storing the certificate itself. Some underlying health or criminal-record information can be subject to additional legal restrictions; the fact that a check occurred is not necessarily the same as collecting the underlying criminal record. These records are used for employment administration and safeguarding and are accessible only to the limited roles described in section 3.10.

Religious belief and other jurisdictions. Taiwan's PDPA does not list religious belief among the specially restricted categories in Article 6. Nonetheless, we treat information about faith and personal spiritual life as sensitive in practice. Other privacy laws may apply in particular circumstances. Contact app@thrivetaipei.com if you have questions about rights under a law outside Taiwan; we will assess the applicable requirements.

5. Who can see your data inside the church

5.1 The roles

RoleWhat it is
YouYour own account.
Approved membersAnyone the church has approved. They see the member directory.
Family group leadersThe leader and co-leader of a group, for their own group only. Other members of the family group's servant team (its helpers) are not included. They help run the group and join the group's servant team chat room; apart from the care notes described in section 3.2, they see no more of your data than any other member does.
StaffChurch staff accounts. The broadest everyday access.
Safeguarding officerOne or more named people who handle reports and safety matters. This permission cannot be granted from the admin website at all, so no staff member can give it to themselves.
Super adminThe small number of people who decide who has access to what, including who can see giving. A super admin can grant that access to anyone, themselves included, and every grant and removal is written to the audit log. The app refuses to remove the last remaining super admin.
HR access and leave and overtime approversA few super admins and staff the church has chosen to handle paid staff's employment, pay, and leave records (HR access), and the people who approve staff leave and overtime, who see only what each decision needs. Only people with HR access can read pay rates.
Database administratorWhoever holds the keys to our database account.

5.2 What each role can see

Swipe sideways to see every column.

Your dataYouOther membersYour FG leaderStaffSafeguarding officer
NameYesYesYesYesYes
Phone, LINE ID, emailYesHidden by defaultHidden by defaultYes, alwaysYes
GenderYesNoYes, in your groupYesYes
Role, membership status, family groupYesYesYesYesYes
Whether you are recorded as marriedYesNoNoYesYes
Private chats and DMsYesOnly people in the chatNoNoOnly via a report, a block notice, or an audited retrieval
Messages to the staff teamYesNoNoYes, all staffYes
Prayer wall posts (named)YesYesYesYesYes
Prayer wall posts (anonymous)YesHiddenHiddenHiddenCan unmask
Notes, prayer journal, highlightsYesNoNoNoNo
Reading progressYesNoYesYesYes
Family group attendanceYesNoYesYesYes
Care notes your family group's servant team keeps about youNoNoYes, with your group's servant teamNo, unless they serve on your group's servant teamNo
Sermon responses, connection cards, signup formsYesNoNoYes, all staff (a form can limit this to the staff it names)Yes
Space requests, including the event name, the purpose you wrote, and your check-in note and photoYesOnly that a time is takenOnly that a time is takenYes, all staffYes
Care and benevolence requestsYesNoOnly if you agreedYes, all staffYes
Staff notes about your care caseNoNoNoYesYes
Paid staff's hours, overtime, comp time, leave, and employment recordsYes, your ownNoNoNo, except people with HR access, and leave and overtime approvers for the request in front of themNo
Paid staff's pay ratesNoNoNoNo, except people with HR accessNo
Paid staff's pay, paystubs, and insurance and tax detailsYes, your ownNoNoNo, except people with HR accessNo
Paid staff's ID number, date of birth, and home address for government filingsNoNoNoNo, except people with HR accessNo
Reimbursement requests copied from the Teams finance channelNoNoNoNo, except people with finance accessNo
Giving records, bank digits, national IDYesNoNoNoNo
Reports you fileNoNoNoNoYes
Event RSVPsYes, your ownOnly the totalOnly the totalYes, individuallyYes

Giving is the exception to this table. Nobody in it can see your donation records or your ID number, including staff and the safeguarding officer. Only accounts a super admin has given finance access to can, and section 6.5 explains how that is handled.

5.3 Things that commonly surprise people

  • Your contact details are hidden from other members by default. Your name appears in the directory; your phone, LINE ID, and email do not. In Settings, under Directory, you can show any of them, hide your photo, or take yourself out of the directory altogether. Your family group, and the people in the chats you are in, still see your name.
  • Staff see your profile in full, including the contact details hidden from other members, and staff can edit it.
  • Staff can see which version of the app each person's devices run, and totals of how many people opened the app recently. They cannot see which screens you visit.
  • Tapping your name or photo in a chat opens your profile card. It shows only what the directory would show to the person looking (your photo, your name, and any contact details you chose to show), with a Message button when they are allowed to message you. Report and Block are under the … in its corner.
  • Who prayed is shown by name. Everyone who can open the prayer wall can see who prayed for a post, who reacted, and who wrote a prayer, unless that person chose in Settings not to be named.
  • Stickers you suggest. When you suggest a sticker for a church pack, staff can see it, with your name, while they decide.
  • Files you add to a form. The staff who can read that form's responses can open them. You cannot open them again in the app.
  • Poll votes are not secret. Everyone in the chat can see how you voted.
  • Event RSVPs look anonymous, and are not. Other members only see a total, but every staff account can see exactly who said going, maybe, or cannot make it. If you say you are going with others, you can add the names of the adults and kids coming with you. Only you and staff see those names, and they are deleted 30 days after the event. If someone added your name and you want it removed, email app@thrivetaipei.com.
  • You cannot read back a report you filed. It goes to the safeguarding officer and only they can open it, including the reason you typed. This is deliberate, so that nothing about a report can be used to work out who filed it. Keep your own note first if you want a record.
  • Reading progress in your family group is a shared list.
  • Your family group leader can see and record your attendance, including a reason and a note.
  • Your family group's servant team can keep care notes about you, and you cannot see them in the app. Staff cannot read them either, unless they serve on your group's servant team.

6. The sensitive parts, explained plainly

6.1 Private messages between members

Staff cannot read your direct messages, your group chats, or your family group rooms. This is enforced by the database itself, not by the app being polite.

There are exactly five exceptions:

  1. The safeguarding officer can retrieve a full transcript of conversations you were part of, if there is a safety reason to. This includes messages you unsent and messages hidden by our retention schedule. Every retrieval is written to the audit log.
  2. Anyone in a conversation can report a message. Reporting freezes a copy and sends it to the safeguarding officer. A reported sticker's picture, and who made it, are kept with the report. This is the intended route for private content to reach someone who can act on it.
  3. When you block someone, the safeguarding officer can see the messages around the block. To understand the block, they can open the conversation around the message in the block notice, including private messages between you and the other person. They see only what you could see, and every time they look it is written to the audit log.
  4. A staff member who is in the chat reads it like everybody else in it. Being staff gives no extra access; being in the room does.
  5. Whoever administers our database can technically read anything. We restrict who holds those keys, but no software rule can prevent it. Your messages are not end-to-end encrypted.

Those five are about who can read your messages. Translation is a separate route: if the church uses it, the words of a message can also be sent, with no name beside them, to the translation service in section 7 so that they can be shown in the other language.

When you unsend a message, others see only a note that a message was withdrawn, and the text is hidden from everyone including you. It is not erased: the record stays for the retention period in section 9, and the safeguarding officer can still retrieve it. A notification that has already reached someone's phone cannot be recalled.

A reported message can be removed. When you report a message, the safeguarding officer or a staff member can take it down from the chat room. That is the whole point of the report button, and it is the only route to it: there is no browse-and-delete tool, and nobody can remove a message they have not been shown by a report. Removal hides the message from everyone; it does not erase it, and the record stays for the retention period in section 9. Every removal is written to the audit log with who did it and why.

6.2 Messages to the staff team

This is a separate conversation from your chats with other members, and it is not private in the same way.

Every staff account can read every message in it. It is a shared inbox by design, so that no single person is the sole holder of a difficult conversation and so that someone always replies. That is a deliberate accountability decision, but it means when you write to "the staff team", you are writing to all of them. If you need to tell one specific person something in confidence, please speak to them directly.

When staff reply, the notification on your phone deliberately shows no preview.

6.3 Prayer requests, including the anonymous option

Anonymous means anonymous to people, not to the system.

When you post anonymously, your name is hidden from other members, from family group leaders, and from ordinary staff, and that hiding is enforced by the database. But your name is stored on the post, and the safeguarding officer can see it. We keep the link because a prayer request is sometimes how someone tells us they are in danger, and we need to be able to reach that person.

So, honestly: anonymous prayer is a good way to share something you would rather other members did not attach to your face. It is not a way to say something you need nobody to ever trace back to you. If you need that, please talk to someone in person.

If you block an anonymous poster, we do the blocking on our side so you never learn who it was.

6.4 Care and benevolence requests

These are among the most sensitive things in the app. If you tell us about an illness, a job loss, a debt, or a family crisis, that text is stored.

  • Every staff account can read your request in full, including the free text.
  • Your family group leader can read it only if you ticked the box to share it with them. That box is a real control and it works.
  • A staff member can have the words of your request translated into English or Chinese, if the request was sent on or after October 18, 2026. Only the words are sent, without your name or any other detail, and a request sent before October 18, 2026 is never translated. Your family group leader cannot translate it.
  • Staff keep a contact log about your case that you cannot currently read. We think you should be able to see notes about yourself, and that is on our list to change. In the meantime, ask us at app@thrivetaipei.com.
  • There is no self-service way to delete a care request. Email us and a staff member will handle it, subject to section 9.
  • Requests cannot be anonymous.

6.5 Giving, bank digits, and your ID number

This is the one area where ordinary staff have no access at all. Donation records can only be seen by an account a super admin has granted finance access to. Holding finance access does not let that person grant it to anyone else, and every grant and removal is recorded in the audit log.

Your national ID or ARC number gets the strongest handling in the app:

  • It is only collected if you ask for a tax receipt to be filed on your behalf.
  • It is encrypted before it is stored, using a key kept separately, so it is not readable even in a copy of the database.
  • Every time it is decrypted, that is written to the audit log with who did it and when.
  • If you withdraw consent for this optional use, your ID or ARC number is promptly removed from active records unless another lawful obligation requires retention. Encrypted backup copies expire under the backup retention schedule in section 9.

Tax receipt documents are stored privately, where you can only ever reach files in your own folder. They may contain your ID number.

6.6 Safeguarding reports, flags, and preservation holds

Anyone can report a message. When you do:

  • A copy of the message is frozen at that moment, so an edit or an unsend cannot change the evidence.
  • The report goes only to the safeguarding officer. Ordinary staff cannot see reports, and neither can you, after you send it. Filing one does not give you a copy or a status page.
  • A preservation hold is placed on the person who wrote the message, which stops anything they were part of being deleted until the hold is lifted.
  • The person reported is not told, and the app deliberately gives them no way to find out. That protects you as the reporter. The one exception is a sticker removed as not its maker's to share: its maker is told that staff removed it because it may not be theirs to share, and never who reported it.

If a preservation hold applies to you and you request account deletion, we may postpone deletion of records covered by that hold while they are necessary for safeguarding or a legal purpose. We will consider applicable legal obligations and exceptions; we may be unable to disclose details that would identify a reporter or compromise an investigation. An unrelated record is not automatically preserved merely because your account has a hold if the system and applicable requirements allow it to be handled separately.

A report being dismissed does not automatically release a preservation hold. The Safeguarding Officer makes a separate, documented decision to release a hold when it is no longer needed; any other lawful reason for continued retention still applies. Access, preservation, and release actions are logged.

7. Who outside the church receives your data

We do not sell personal data or share it for advertising. We use outside services only to operate the app and support church activities, including hosting, notifications, email, file storage, Google Workspace, translation, security, Bible text, media, backups, and app distribution. The table groups these services by provider or service category, explains the kinds of information involved, and identifies their main processing locations. The paragraphs below explain important access and retention details.

WhoWhat they receiveWhere they are
Supabase (hosting, authentication, database, and file storage)Our main app records, including accounts, messages, group and prayer records, and operational data; login services, private file storage, and server-side functions. This includes the photos, videos, and files in chat and the family group photos and videos. A new full-size photo waits in the church’s Google Drive until a nightly job moves it here, as described below.Singapore (primary project region)
Our notification and app update service, and Apple and GoogleYour device token and the text of each notification, every time you get one: for a chat message, the name of the chat (with the family group or topic it belongs to), the sender's name, and a short preview of the message; for an announcement, event, reminder, or decision, its title and first words. When you read a chat on one iPhone or iPad, a silent update that changes only the number on the app icon may go to your other iPhones and iPads; it carries no text. When the app checks for an update, the update service also receives technical information about the app on your phone, such as its version and platform, and your IP address, but nothing from your account.United States and elsewhere
Our email delivery serviceYour email address and the content of each email the app sends you, such as a sign-up confirmation, a password reset, a link to confirm a new email address, or, if you signed up for an event or a form, a confirmation or reminder, including when you signed up without an account.United States
GIPHYWhat you typed, when you search for a GIF. The search is sent from our server, not from your phone, so your IP address is not shared. Once a GIF has been sent, anyone who scrolls past it loads the image from GIPHY, which does reveal their IP address to GIPHY in the same way any image on the internet does.United States
YouTubeNothing from your account. When the app shows the picture for a sermon video, your phone loads it from YouTube, which reveals your IP address to YouTube the same way any image on the internet does. If you tap to watch, the video opens in YouTube, under YouTube's own terms.United States and elsewhere
Crossway (ESV)The Bible passage reference only. No account, no device, and no identifying information. Most requests never reach them because we cache the text.United States
Our web hostStandard web logs (IP address, browser, and page) for anyone who opens a page it serves: staff using the admin website, anyone using the church's web forms or reading these documents on the web, and your phone when the app opens its security check page. Member data does not pass through it; the admin site and the web forms talk to our database directly from the browser.United States
Cloudflare (security check)When the app or one of our web pages runs its security check, which tells a person from an automated attack (at sign-up, sign-in, password reset, and email change, and on the connection card, sermon response, and public sign-up forms), Cloudflare's check runs on your device and receives technical signals from it, including your IP address. It is not given your name, your email address, or your password.United States and elsewhere
Google Workspace (including Google Drive)Church-managed documents and records needed for particular features: new full-size photos, and files sent from older versions of the app, until they are moved to private storage; earlier copies of photos and files that were moved, kept for now as a backup; a nightly backup copy of the photos, videos, and files in private storage, in a separate folder of the church’s shared drive; staff-restricted name tag records; prayer requests that members chose to share with the church; staff-authorized form-response exports (which may contain contact details, answers, file names, and staff notes); family group signup answers if collected through Google Forms; and approved space bookings (venue, time, and event name) if synchronized to the church calendar. Access depends on each record's purpose and sharing settings. Sections 3.6, 7, and 9 explain relevant limits, retention, and revision-history risks.United States and other locations
Anthropic (Claude)The words of each prayer request going onto the staff prayer list, so Claude can translate it into the other language. Claude may also be given text that members write in the app (chat messages, including direct messages and group chats, posts, polls, prayer list requests, messages to the staff team, notes, and posts and written prayers on the Prayer and Praise Wall) and text the church itself writes and publishes, such as announcements, so that it can be shown in the other language. From October 18, 2026, a staff member can also have the words of a care request sent on or after that date translated, and a staff member can have the words of a sermon response form translated. For translation, Claude is given only the words to translate. It is never given the name beside them or anything else from your account, and an anonymous post is given with nothing that says who wrote it. A care request is given to it only when a staff member asks for a translation, and never for a request sent before October 18, 2026. From November 18, 2026, Claude is also given the words and receipt images of reimbursement requests that staff post in the church's Teams finance channel, so it can suggest the amount, date, and purpose for finance to check, and never any account details.United States and elsewhere
Microsoft (Teams)The church's own Microsoft 365. Reimbursement requests and their receipt photos are read from the church's Teams finance channel and copied into the staff web admin (section 3.10). The app sends nothing to Microsoft.Where the church's Microsoft 365 keeps its data
TTLock (the church door lock)The commands to unlock and lock the church door, sent from the church's TTLock account, and the door codes Thrive puts on the lock with the times they work. Each code is named "Thrive P-", "Thrive V-", or "Thrive B-" followed by random letters and numbers, never a person's name; Thrive sends TTLock no name, email address, or other account details. Cards and fingerprints are added at the door with TTLock's own app, with any name the person adding them types there. TTLock keeps the lock's own record of each opening (the time, how the door was opened, and which code, card, or fingerprint), which Thrive reads to show staff the door's history.Outside Taiwan; the church's account uses TTLock's European service
Our code host (backups)A nightly backup of the whole database, encrypted before it leaves us and readable only with a key the church holds. It is kept for 90 days and then deleted automatically. Nobody at that company can read it.United States
Apple App Store and Google PlayStandard app distribution and crash information collected by the stores themselves.United States and elsewhere

Read this before you decide about notifications. When someone sends you a message in any chat, the first part of what they wrote, together with their name and the name of the chat, is sent to Apple or Google so it can appear on your lock screen. Those companies handle it outside Taiwan. So a piece of the real message leaves our systems every time you are notified, and anyone who can see your locked phone can read it. Thrive Friends notifies you only when someone @mentions you, unless you choose to be notified of every message.

Changing your phone’s lock-screen preview settings hides the text from people looking at your phone, but it does not by itself stop the notification content from being transmitted through Apple or Google. To stop these chat-message push notifications from being sent, turn off message notifications in the app. Other kinds of notifications follow their own settings.

Replies from staff never carry a preview, whatever your settings.

About files and photos in chat. Photos, videos, and files in chat, and full-size family group photos and videos, are kept in the app's private storage with our hosting provider, Supabase, along with small previews so conversations load quickly. Stickers you create and files you attach to forms are kept in Supabase's private storage, not Google Drive. A new full-size photo is first uploaded to the church's Google Drive, and a nightly job moves it to private storage; files sent from older versions of the app take the same route. Copies in Google Drive of photos and files that were already moved are kept for now as a backup, until the church removes them. We may use private storage with our hosting provider for additional files in the future. Where the location, access protections, or other data handling changes materially, we will give notice and obtain consent if the law requires it (section 13). A change of storage tool alone does not change who is allowed to open the content or how long we keep it.

Google stores the files placed in Google Drive, but does not receive the surrounding chat text or a separate list of conversation participants from this upload. Each night, a backup copy of the photos, videos, and files in private storage, including files attached to forms, is also placed in a separate folder of the church’s Google shared drive. The backup copy of a removed photo or file is deleted within 30 days, and sooner for some, such as files attached to forms and deleted accounts. Deleting a chat attachment disables its access link and removes the stored file and its other copies in Google Drive under the deletion rules in section 9. Content retained for a legal or safeguarding reason may be an exception. Stickers you create and files attached to forms are stored with Supabase instead.

About the staff prayer list. Prayer requests shared with the church are copied into staff-restricted records in the church's Google Drive. These include prayer requests or praise reports that you chose to share on a sermon response form, and requests posted on the church-wide prayer wall. Praise reports posted directly to that wall are not copied. We do not copy private sermon responses, personal reflections, LINE IDs, other contact details, or private prayer journals. The record includes the date, the name supplied (if any), the prayer text in both languages, and its source. Anonymous wall posts and forms with no name remain unnamed on the staff list. Anthropic's Claude translates the words only, without your name; your original words are preserved.

A prayer wall post comes off the list within about a day of leaving the wall, whether it expired after a week, you deleted it, or it was removed for safeguarding reasons. Google Workspace may retain earlier file versions, so authorized staff may still be able to see an entry after it has been removed from the current list. A request from a sermon response form stays on the list until staff remove it: the nightly deletion in section 9 does not reach the list, and neither does deleting your account. To have one removed, email app@thrivetaipei.com.

To fill the list, we make our own copy of each request in both languages (the words only, with no name). That copy is deleted as soon as the request is recorded as on the list. The translating is done in a Claude session on a staff member's computer, and that session's own record of its work, which includes the words it translated, is deleted automatically after about 30 days. If a request never reaches the list, a nightly job deletes its copy once the request no longer qualifies, for example because the wall post was deleted, removed, emptied, or expired, because your choice to share it no longer applies, or because the account that posted it on the prayer wall was deleted.

About the church's calendars. If the church shows approved space bookings on its own Google Calendar, each entry has the space, the time, and the event name given to the booking, and nothing else from the booking: not what the event is for, and not the name or contact details of the person who booked it. The event name is free text that the person booking writes. The church keeps these calendars for staff, and other members still see only that a time is taken. The app may also read the times already on those calendars to show when a space is free. Google Calendar is part of the church's own Google Workspace, in the United States and elsewhere.

Links that take you out of the app. When you tap an address, a video, a website, or a LINE link, the app hands it to the app or website you chose, such as Google Maps, Apple Maps, YouTube, LINE, or your browser. What happens next is between you and that service, under its own policy; the app sends it nothing else about you. When someone posts a link in a chat, our server fetches that page to build the preview, so the website sees a request from our server, not from you or anyone else in the chat, and the preview picture is kept with our hosting provider.

Things we are sometimes assumed to use, and do not. The church uses accounting software, but the app is not connected to it; a person exports a spreadsheet and uploads it by hand. There is no analytics or advertising service of any kind.

When this list changes. Providers and tools may change as the app develops. A new spreadsheet, file, or feature within the purposes, recipients, locations, and safeguards already described does not by itself require a new policy acceptance. Before a material change to a provider category, the types of information shared, its purpose, location, access, or safeguards, we will give the notice required by law and seek additional consent where required (section 13). We do not share information for advertising or sell it.

8. Where your data is stored, and transfers outside Taiwan

Your data is stored outside Taiwan. Our primary Supabase database and storage project is hosted in Singapore. Supabase is a United States company; its corporate operations and legal obligations may involve the United States. Other companies that help deliver the app may process information in additional countries, as set out in section 7.

This is an international transfer of personal data out of Taiwan. Our principal database and storage are in Singapore. Depending on the feature, information may also go to the church’s Google Workspace for files, prayer lists, name tags, forms, and calendars; to Apple or Google for notifications; to Anthropic for translation of selected text and to read reimbursement requests; to our email service for email delivery; to TTLock for the church door; and to our encrypted backup provider. The types of information, access restrictions, and relevant locations are described in sections 3 and 7. We will give any additional notice and seek consent required by Taiwan law before materially different processing begins.

Our current hosting and selected service providers operate outside Taiwan, so we cannot offer a Taiwan-only storage and processing option at this time. Contact app@thrivetaipei.com before creating an account if this is a concern.

9. How long we keep things

We apply the retention periods below and routinely delete records when they expire, subject to the exceptions described in this policy. A change to a material retention commitment will be disclosed as required by law (section 13).

DataHow long
Chat and staff team messagesHidden from everyone at 12 months, destroyed at 36
Stored translationsA translation is kept beside the words it was made from, and deleted when those words are deleted, hidden, or edited (an edited message gets a new translation). It holds only the translated words, with no name
Photos in chats and family groupsDestroyed together with the message or photo record they belong to
Stickers you makeUntil you delete them or delete your account. If you delete a sticker, it leaves your list and everyone's Saved lists, but it stays visible in conversations where it was already sent until those messages are destroyed, unless you choose to remove it from chats too. A reported sticker is kept for as long as the report.
Stickers you saveUntil you remove them, the maker deletes the sticker or turns sharing off, or you delete your account. A saved sticker is only a link.
Stickers you suggestA suggestion that staff decline, or that you withdraw, is deleted 90 days later. A suggestion that staff accept is kept, with the record of your permission, for as long as the church sticker exists. The church sticker itself stays after you delete your account.
Care and benevolence requests3 years after the case is closed. An open request is never deleted while it is still open
Connection cards and signup forms held by us2 years
Event sign-ups and surveys from the church's form builder6 months after the event for a sign-up (6 months after the form closes, if there is no event), 12 months for a survey, or the time that form states at the top; never more than 24 months after you submit. Only anonymous totals, such as how many came, are kept. A downloaded file is outside our database and the nightly job does not reach it
A guest's private link for a sign-upThe link stops working when the event starts, or after about 6 months for a form with no event. The church keeps only a scrambled version of its code; your own browser keeps its own copy until you clear it
Names of the people you add as coming with you to an event30 days after the event. How many adults and kids came with you stays with your RSVP
Files you add to a formDeleted with the sign-up: when you cancel, when staff cancel or delete the sign-up, when the form's retention period deletes it, when you remove the file, and when your account is deleted (the file's name stays in your answers until the form's retention period ends). A file you add but never send is deleted after 14 days
Staff-authorized exports of form responses to Google DriveDeleted when the form's answers would be (the same months, and never more than 24 months after the copy was made), sooner if staff delete it, and when the form is deleted. A copy someone has downloaded or shared cannot be recalled
Welcome desk name tag records in Google DriveUpdated regularly; people no longer on the current approved list usually disappear within about a week. Earlier versions may remain accessible to authorized staff through Google Workspace revision history. See section 7.
Sermon responses2 years
Prayer requests shared on the church staff listPrayer wall posts come off the list within about a day of leaving the wall. Requests from a sermon response form stay until staff remove them; the nightly job does not reach the list, and deleting your account does not remove them. Our own copy of each request in both languages is deleted as soon as the request is recorded as on the list, or, if it never gets there, once it no longer qualifies. The translation session's own record of its work is deleted after about 30 days. See section 7
Space requestsThe space, the time, and the number of people are kept with no end date, as the record of who used which space when. 12 months after the time you asked for has ended, the event name, the purpose you wrote, and any note from staff are erased. If you delete your account, on day 30 the event name, the purpose, and any note from staff are erased, and any upcoming reservation is canceled. A copy on the church's Google Calendar loses the event name at the same times, and is deleted when a reservation is canceled. The message we send you about a decision repeats any note from staff, and it is kept like any other message to the staff team. A check-in keeps whether it was done or a problem, the items you ticked, and the time, until you delete your account. The note and the photo of a problem report are erased 12 months after the time you asked for has ended
Family group attendance3 years
Care notes your family group keeps about youWhile you are in the group. When you leave it, they are archived and deleted six months later, or restored if you come back before then. A note kept only by its writer is deleted when that person leaves the group's servant team. All of the notes about you are destroyed when you delete your account; notes you wrote about other people are covered in section 11
Prayer wall posts, the prayers you write under them, your notes, reading records, and saved versesFor as long as you have an account. Posts leave the wall after about a week, you can delete your own at any time, and all of this is destroyed when you delete your account
Technical information about your devices: push tokens, app versions and updates, the installation ID, and notification settingsPush tokens, app versions and updates, and the installation ID are deleted when you sign out or tap delete on your account. Notification settings stay until your account is deleted on day 30. If you remove the app without signing out, a notification token is deleted the first time a notification to it fails, and an app-version record, with its installation ID, after about six months without a report from that device
The log of when you sent messages or postedShort-term, and only to enforce rate limits
Problem reports (Settings > Report a problem)180 days, or until you delete your account if that comes first. Only staff can see them
Counters kept by scrambled address, for abuse limitsAbout 2 days
A staff member's clock-in widget keyIt stops working when the person signs out, after 60 days, or when their employment ends (the app makes a new one after 30 days). The church keeps only a scrambled version of it, with a random ID for that installation and when it was last used, and deletes it when the account is deleted
The note that you left a church-wide room, and the queue of notifications waiting to be sentThe note stays until you rejoin the room or delete your account. The queue is cleared after 14 days
People on a family group's list who have no account, and visitorsAttendance follows the 3 years above. A visitor is deleted after about a year without coming. A name taken off the list and never joined to an account is deleted once no attendance record needs it
Family group signup responses from a Google Form: the time, the account matched, and an unmatched email address or phone numberUntil staff match an unmatched email address or phone number to an account, or you ask us to remove it. The nightly job does not reach them. See section 3.6
Paid staff's hours, overtime, comp time, pay rates, payroll and paystubs, leave, and employment recordsAt least 5 years, as labor law requires. They are kept after an account is deleted (section 11)
Reimbursement requests from the Teams finance channel, with their receipts5 years after the year they are paid, as accounting records. A post that is not a request: 90 days
Records that required checks and briefings were completed (paid staff and some volunteers)For as long as the church needs to show the check was done. The nightly job does not delete them, and they are kept after an account is deleted (section 11)
The church door: who may open it, door codes, and the history of unlocks, locks, and changes made through ThriveAccess and your door code last until your access ends, and then the code is removed from the lock. A reservation's code is removed when the reservation ends or is canceled. The history, and the record of a removed code, are deleted after 12 months. The lock's own record of openings is kept by TTLock (section 7)

Between month 12 and month 36 a message is invisible to you, to other members, and to staff. Only the safeguarding officer can retrieve it, and only with an audit record.

What we keep for longer, and why

Three things outlive the schedule above, deliberately:

  • Giving and tax records: 7 years. Tax law requires it.
  • The audit log: retained without routine expiry for accountability. It records administrative actions, not message content. Ordinary app accounts, including super admins, cannot alter or delete entries through the app; technical infrastructure access is separately restricted (section 10).
  • Safeguarding reports, flags, and records subject to preservation holds: retained as long as reasonably necessary for the safeguarding or legal purpose. Some matters emerge years later, so evidence may need long-term preservation. A hold is reviewed and released through a separate, documented decision by the Safeguarding Officer when it is no longer needed, unless another lawful retention reason applies.

Active records and encrypted backups have different deletion times. Information removed from active records may remain in encrypted nightly backups for up to 90 days, until the last pre-deletion backup expires. Backups are maintained for recovery and security, not ordinary use; access to their keys is restricted. Specific financial, safeguarding, and legally required records may follow longer retention rules.

Preservation holds suspend routine deletion for affected records. When a person is under a hold, or content has been reported or flagged, the relevant records may be retained outside the periods above for safeguarding or legal reasons. The current hold mechanism can affect all records the person participated in. We review the need for retention and resume the applicable schedule after a hold is released, unless another lawful basis requires the records.

If you want something specific deleted sooner, ask us at app@thrivetaipei.com. A person will do it by hand.

10. How we protect your data

  • Database access controls. Each data table has access rules enforced at the database level according to user roles and permissions. These controls are designed to reduce unauthorized access, including access that might otherwise result from errors in the app interface. No technical control eliminates every vulnerability.
  • Encryption in transit. All traffic between the app and our servers is encrypted.
  • Your national ID is encrypted at rest with a key stored separately from the data, and every decryption is logged.
  • Private file storage. Tax receipts, the photos, videos, and files in chat, and family group photos and videos, including the full-size originals, are in private storage, with rules tied to your membership of that chat, group, or account. A link to a photo or file stops working within fifteen minutes of being opened, and a link to a video within an hour. A new full-size photo waits in the church's Google Drive until the nightly move to private storage, and copies of earlier originals stay there for now as a backup. See section 7.
  • Split permissions. An ordinary staff account cannot promote itself to anything. Access to giving, and super admin itself, can only be granted by an existing super admin, and every grant and removal is logged. Safeguarding officer is the only permission that cannot be granted from the admin website at all, so nobody can hand themselves the ability to read reports and unmask anonymous prayer.
  • Access-restricted audit logs. Administrative actions are logged and ordinary app accounts, including super admins, cannot edit or delete entries through the app. Infrastructure access is separately restricted to authorized personnel and service providers; privileged technical access cannot be described as impossible. The logs are retained as described in section 9.
  • Report details are kept from ordinary staff, so that filing a report cannot expose the person who filed it.
  • No third-party analytics, so there is no extra copy of your behavior anywhere else.

What we cannot promise

  • Messages are not end-to-end encrypted. Anyone with our database keys can read them. We limit who has those keys.
  • Some storage is public: images published by staff for the whole church, including the church's stickers (a member's sticker that the church accepts is kept there too) and the pictures staff put on a form (anyone who can open the form can see them). Do not treat those as private. Chat photos, family group photos, stickers you make, files you add to a form, and tax receipts are all private.
  • Notification previews leave our systems, as explained in sections 7 and 8.
  • Anyone with access to a screen can copy or photograph what is on it. No software rule stops that, which is why staff access is limited by role and why administrative actions are logged.

11. Your rights, and how to use each one

Under PDPA Article 3 you have five rights. Here is how each works today, including which ones need a person rather than a button.

To ask what we hold, to see it, and to get a copy

Email app@thrivetaipei.com. There is no self-service export in the app, so a staff member assembles your data by hand. We will tell you within 15 days whether we can do it, extendable once by a further 15 days if the request is complicated, in which case we will write and tell you. We provide it in a readable format, and may charge a reasonable fee for the work, as the PDPA permits.

To correct or complete your data

Some of this you can do yourself. In the app, go to Profile, then Update my info, where you can change your names, how your name is printed on a name tag, your LINE ID, and your phone number.

You can also change your email address yourself, in Settings, then Account. These need a staff member: your gender, your family group, your membership status, and your role. Email app@thrivetaipei.com and we will correct them.

To stop us collecting, processing, or using your data

Several controls exist in the app and genuinely work:

  • Notification preferences and quiet hours, in Settings.
  • Directory settings, in Settings: whether you are listed, and whether your photo, phone number, email, and LINE ID show.
  • Read receipts, in Settings: off unless you turn them on.
  • Block another member. This hides their messages from you everywhere, stops direct messages in both directions, and tells the Safeguarding Officer. The notice carries the most recent message or post of theirs that you could see. To understand a block, the Safeguarding Officer can also see the messages around it in that conversation, including private messages between the two of you. They see only messages you could see, and every time they look it is written to the audit log. The person you blocked is never told. The Safeguarding Officer may also send you a note in the app suggesting that you unblock someone; nothing changes unless you choose. You can unblock in Settings.
  • Tax receipt consent. If you withdraw it, the ID or ARC number is removed from active records promptly, subject to legal retention and the encrypted backup schedule in section 9.
  • Sharing a care request with your family group leader. A per-request choice.
  • Posting a prayer request anonymously. With the honest limits in section 6.3.

There is no single in-app switch for withdrawing every permission while retaining an account. Your consent is recorded at sign-up, at sign-in, and whenever you agree to an updated version. You can change the individual settings above, and you may email app@thrivetaipei.com to withdraw a particular consent or request that a specific use stop. Some processing is necessary to maintain an account or meet legal duties; if you wish to stop using the app entirely, you may request account deletion as described below. Updating this notice does not, by itself, renew or expand your consent.

To have your data deleted

In the app: Settings, then Account, then Delete my account.

WhenWhat happens
The moment you tap deleteYour account switches off. You disappear from the directory, member features stop, and notifications stop. Your devices' notification tokens, app versions and updates, and installation IDs are erased at once, and your phone cannot add new ones while the deletion is pending. Nothing else is erased until day 30.
The next 30 daysA cooling-off period. Sign back in and cancel, or ask a staff member to cancel for you. Everything comes back as it was, except a space request that was still waiting for a decision, which was canceled when you tapped delete, and your devices' notification tokens, app versions and updates, and installation IDs, which your phone makes again the next time you open the app after canceling.
Day 30 (normally)If no preservation hold or other lawful reason delays deletion, the account and profile are removed and the account-linked records identified in section 11 are deleted. Other records remain for their disclosed retention periods. If deletion is delayed, the account stays disabled until the hold or other restriction is resolved.

What is normally deleted when account deletion completes: After the 30-day waiting period, and subject to preservation holds or other lawful retention requirements, we remove the following account-linked information from active records: your chat messages, prayer wall posts, personal notes, care notes your family group kept about you, prayer journal, reading records, saved verses, your stickers and the pictures behind them, your saved stickers (the links only), files you added to forms, giving profile including any encrypted ID number, notification settings, the prayers you wrote under prayer wall posts, the requests you follow, any clock-in widget keys, any weekly prayer list you started (it goes with the card you posted to open it, which is one of your chat messages, and takes the entries other people added that week with it), and the note that you left a room. Your push tokens, app versions and updates, and installation IDs are not on this list because they were already erased when you tapped delete. Some records described below survive, and encrypted backups expire separately under section 9.

What survives, and why. Please read this part, because "deleted" does not mean every trace of your name is gone.

Deletion removes more than your profile, but it does not erase every record. When deletion completes, your login and the account-linked content identified above are deleted, and your profile details (name, email address, phone number, and LINE ID) are scrubbed. Other records may stop pointing to your account while keeping the names or contact details originally typed into them. Removing an account link does not erase that plain text. In practice:

  • Forms you submitted keep a snapshot of the name and contact details you entered at the time, along with everything you wrote. The snapshot exists so a form does not go stale when someone later changes their details, which is exactly why deleting your profile does not remove it. The retention period in section 9 is what ends it.
  • Sermon responses keep your name and LINE ID as you typed them, with your reflection and prayer request.
  • The staff prayer list keeps any sermon response prayer request you chose to share, with the name you typed, until staff remove it. Staff who can edit the list can still find a removed request in its version history, including a prayer wall post. See section 7.
  • Space requests keep the space, the time, and the number of people, no longer attached to you. The event name, the purpose you wrote, and any note from staff are erased, and any upcoming reservation is canceled. Any check-in and problem report you made is deleted, including its photo.
  • Financial records imported from the church's accounting software keep the donor name as the accounting software recorded it. Your own donation entries keep the amount, date, and bank digits, no longer attached to you.
  • Staff employment records (hours, overtime, comp time, leave, pay rates, payroll and paystubs, and employment terms) are kept for at least five years because labor law requires it, and they keep the name they were filed under. Records of completed checks and briefings keep that name too.
  • Entries you wrote in a chat room's weekly prayer list for other people. They stay in the list, with your name removed as the writer, and the words stay as you wrote them. Entries about you are deleted. A request of yours that another member saved to their own prayer journal is that member's copy and stays in their journal.
  • Care notes you wrote about other members. Notes you shared with a group's servant team stay with the group, with your name removed as the writer, and the text stays as you wrote it; so does a short summary you last updated. Notes kept only by you are deleted by the nightly job within a day after your account is deleted. Notes about you are destroyed on day 30 (see the list above).
  • Photos in your family group's album, notes in a chat room, and family group announcements. The church decided that a group's album and a room's notes belong to the group or the room, so they stay, with your name removed as their author. Anything you typed into a caption or a note stays as you typed it, and an announcement a leader sent keeps the leader's name as it was then.
  • The welcome desk's name tag list. The church refreshes these staff-restricted records regularly, removing people who are no longer on the approved list, usually within about a week. Earlier versions may still be available to authorized staff through Google Workspace's revision history. See section 7.
  • A sticker you suggested that staff accepted stays as a church sticker, with the record that you gave permission: your name as it was then, the date, and any credit you asked for. Once accepted, it is the church's sticker.
  • Safety reports and flags keep the frozen copy of the reported message (a reported sticker's picture included) and the reason the reporter typed. Safety evidence has to outlive the accounts involved, or it would be useless to the person who has to act on it.
  • The church door's history keeps the unlocks, locks, and changes you made through Thrive, no longer attached to you, until its 12 months are up. Your access and your door code are removed, and so is the link between you and any card or fingerprint. A card or fingerprint added at the door stays in the lock until staff remove it, so ask us if you want it removed.
  • The audit log is retained without routine expiry for accountability, so account deletion does not automatically remove its entries. Your account’s internal ID may still appear where you were the subject of an action. Access remains restricted as described in sections 9 and 10.
  • Our encrypted nightly backups can still contain your data for up to 90 days after it is deleted, and are then deleted automatically. Only the church holds the key.
  • During a preservation hold. The app may postpone completion of account deletion and suspend routine deletion of records the person participated in until the hold is released. Your account is still disabled when you submit the deletion request. Where our systems and applicable law permit, unrelated records may be handled separately. Sections 6.6 and 9 explain how holds are reviewed and released.

If this matters to you, ask us. Email app@thrivetaipei.com and a staff member can remove your name from the surviving records by hand, except from anything held for safety or tax reasons. That is a manual job, and we would rather do it than have you find out later.

Before you tap delete:

  • If anything blocks completion, your account is still disabled when you request deletion. The automated deletion process retries, but a preservation hold requires a separate, documented release decision (section 6.6). Email app@thrivetaipei.com if you want confirmation that deletion is complete.
  • Children’s ministry check-in is not currently active and no child records are stored in that feature (section 12). If we introduce the feature later and link a child’s record to a parent’s account, deleting the account may affect the linked record; we will explain the applicable process before launch. Contact us if you have a question about a child’s information.

If you are not happy with how we handled it

Contact us first at app@thrivetaipei.com. If we do not resolve it, you can complain to the relevant Taiwanese authority for personal data protection, or seek a remedy in court under the PDPA.

There is no privacy contact form inside the app. Messages in the app go to the staff team, which is not a privacy channel and is itself covered by the retention schedule, so please use email.

12. Children and young people

We need to be straightforward here.

The app does not currently ask for or verify a user's age. Birthday details are optional, including the year. It therefore cannot reliably distinguish an adult account from a minor's account. The Terms require anyone under 18 to have the knowledge and permission of a parent or legal guardian, subject to applicable law.

A person under 18 can technically register through the same screens as an adult, but that technical ability does not remove any legal permission requirement. The app does not currently obtain guardian permission electronically. A minor's acknowledgment of this notice is not a substitute for a guardian's legally required involvement or consent.

If you are under 18, please contact app@thrivetaipei.com before registering so we can explain the requirements and arrange any necessary permission. We can also answer questions from your parent or guardian.

If you are a parent or guardian and you want to see, correct, or delete data about your child under 18, email app@thrivetaipei.com and we will treat it as a priority.

Children's ministry check-in. The system contains an unused design for children's check-in, covering things like allergies, medical notes, authorized pickup, and emergency contacts. It is not switched on, no part of the app writes to it, and no child's record exists in it. We will update this policy and ask parents for consent properly before it is ever turned on.

Reporting a concern about a child. Contact patrick.ng@thrivetaipei.com immediately. Our approach to child safety, mandatory reporting, and preserving evidence is set out in our separate Safeguarding and Retention Policy.

13. Changes to this policy

We review this policy when our information practices or legal obligations change, not automatically whenever a feature is released. The current notice and its revision date are published in the app and on our website. New features are covered by the existing notice only when their purposes, data categories, recipients, access, locations, and retention remain within what is disclosed here.

We may give more specific information within a form, device permission, or feature. Such a notice supplements this policy and does not reduce rights or safeguards. Nothing here constitutes advance blanket consent to protected medical information processing, unrelated purposes, or sharing beyond the disclosed scope. We assess these changes before implementation.

We will provide additional notice when law requires it, including for material changes to collection, purposes, recipients, access, processing locations, or retention. We will explain the practical effect through the app, at collection, or by other appropriate means. Posting a revised policy alone is not a substitute for legally required individual notice or consent.

Publishing a revised Privacy Policy does not automatically require you to accept it again. When a change fits within the existing disclosures, the app may continue operating without a new policy-acceptance screen. Where the law requires additional notice, we will provide it. Continued use alone does not replace an affirmative or written consent required by law.

When specific consent is legally required, we will request it before the affected processing. Where possible, this will be a feature-specific choice rather than requiring everyone to reaccept the full Privacy Policy. We will separately assess changes that would materially weaken commitments about advertising, tracking, retention, access to private content, or safeguarding powers, and will obtain any additional legal basis and consent required. Declining optional processing should not block unrelated app features where practical.

You may contact app@thrivetaipei.com about a revised notice, a particular use of your information, or a request under section 11. You may also stop using the app and seek account deletion. Routine revisions do not require a new acceptance merely because the policy version number changes.

14. Questions

Questions, concerns, or privacy requests: app@thrivetaipei.com.

If anything in this policy is unclear, please ask. We are happy to explain how your information is handled.