free cheat sheets

privacy policy

last updated 2 November 2026

The short version

We are a training app for church worship and tech teams. To do that, we keep track of what you have learned, what you have built in the app, who you are on a team with, and how you use the app, so we can make it better and tell you about the parts you would like. We do not sell any of it, we do not run ads, and we do not share it with anyone except the handful of companies listed below that we need to actually run the thing.

If your organization has a team here, your team leader can see how you are doing in the training. That is the point of a team, but you should know it before you start.

Who we are

WorshipTechU is a registered sole proprietorship in British Columbia, Canada (registration number FM1094836), operated by Canyon Coulter Lewis. Questions, requests or complaints: canyon@worshiptechu.ca.

What we collect

When you make an account: your email address and name. If you sign in with Google or Apple, we get your email address and basic profile information from them, not your password and not access to anything else in your Google or Apple account. If you sign in with Apple and choose Hide My Email, Apple may give us a private relay address that forwards to your real one, and that is the address we keep. You then choose a username, and can add a photo, a short bio, the instrument you play, your preferred key and which roles you serve in. All of that is optional except the username.

As you use the app:

If you are part of an organization: which organization and teams you belong to, your role in them, assignments you have been given, and records of invitations and membership changes. Team leaders can add notes about members.

If you connect Planning Center: we store a connection token and the schedule information we pull from it. You can disconnect at any time, which deletes the token and the schedule we kept, and tells Planning Center to end the link.

You can also connect Planning Center at each other organization you serve at, one connection per organization. We keep each connection's tokens sealed (encrypted) so nobody can read them from our database, and with them we read your schedule there and, for each plan from a week back to 90 days ahead, its times, its order (songs, arrangements and keys) and its team (names, positions and answers). We keep that for you only and show it on your schedule with the organization's name; nobody else here sees it. When you pick a church, we read that church's people, songs and plans with your connection for that church, show them to you, and do not keep a copy of those lists. Since 13 October 2026 we read it again every hour, and we keep this copy of your plans for your first Planning Center connection too. Your accept or decline goes back to Planning Center as you. Disconnecting a connection deletes its tokens and the plans we kept through it, and tells Planning Center to end that link.

Automatically: basic technical information that comes with any web or app request, error reports when something breaks, and how long the app took to open (or that it did not get to your home page within a minute), with your account, whether it was the web, iPhone or Android app, and which version. Once a day we email ourselves a summary of those error reports: what broke, which screen, and how many times. The summary goes to our own address through the same email service as our other mail. It does not include anyone's email address, name, or account id, or a code from the page address. We also keep a record of how you use the app; see "How you use the app" below.

If you pay us: payments run through Stripe or, if you subscribe in the iPhone or Android app, through Apple or Google. We never see or store your card number. We keep a record of what you bought and what access it gives you. For a subscription bought in the app, Apple or Google takes the payment and tells us what was bought, its price, currency and country, when it renews, ends or is refunded, the store's reference for it, and whether it was a test purchase, never your card or your Apple or Google account details. So a purchase finds your account, the app hands the store a random code made for your account that says nothing about you.

How you use the app

We keep a detailed record of how you use WorshipTechU, in our own database, tied to your account. We use it to make the app better, to see which lessons, games and tools people use and where they get stuck, and to choose what we tell you about by email and in the app. It never goes to an advertising network, and we never sell it.

Our website, worshiptechu.ca, keeps the same kind of record, with its own random code for your browser: the pages you open and the page you came from, the parts of each page you reach and how long you stay on them, how far you scroll, what you tap, which sign-up form you used (never what you type into it), the before and after mixes you play, your screen size, language and time zone, the website and campaign tags that brought you, and a rough idea of where you are (country, region and city), worked out by our web host from your network address, which we do not keep. It is not joined to your account in the app.

If you use the app before you sign in, the same record is kept against that random device code, and joined to your account when you sign in (on a shared device, only what was done there since somebody else last signed in on it). Your team leader does not see this record; they see the training progress described in "What your team leader can see". You can ask for a copy of it, or for it to be deleted, like the rest of your information.

Everywhere else, this record is on from the start. You can turn it off any time: in the app, under "usage record" in your privacy settings; on the website, with "your tracking choice" at the bottom of any page. Turning it off stops the record from then on and clears what was waiting on your device; to have what was kept before deleted, ask us.

If you are in the European Union, Iceland, Liechtenstein, Norway, the United Kingdom, Switzerland or Quebec, the app and the website ask you first, and keep none of this record unless you say yes. See "If you are in the EU, the EEA, the UK or Switzerland" and "If you are in Quebec" below.

What we do not collect

We do not read your contacts, photos, calendar, or anything else on your phone beyond what is described here. The usage record never includes what you type (your notes, logs, messages or passwords), apart from what you search for in the app's own search boxes, and never any sound or a recording of your screen. We do not use advertising trackers and we do not build advertising profiles. We do not sell your information to anyone, for any purpose, ever.

The microphone

Three tools measure sound through your microphone. The SPL meter measures how loud the room is. The tuner listens to the note you are playing so it can tell you if you are in tune. The drum tuner listens to a drum when you tap it, so it can tell you its pitch.

We do not record, store or transmit audio. The sound is measured on your device and thrown away. The SPL meter saves only the numbers: average level, peak level, how long it ran and the timestamp, plus where it was taken if you allow it (see "Location"). When the SPL meter hears a ring and you ask CanyonAI what to cut, only the note's pitch, how far it stands out and where you pick it is coming from are sent to Anthropic (see "The AI features"). The tuner and the drum tuner send no sound anywhere. The drum tuner's saved kits and target pitches are kept on your account (see "As you use the app"); its other settings stay on your device. The app only uses the microphone while one of these tools is open and running.

CanyonAI can also listen when you tap its mic. In a web browser, the browser turns your voice into text. In the iPhone app, Apple does it, on your iPhone where it can and otherwise on Apple's servers; in the Android app, your phone's speech service does it, on the phone where it can and otherwise on its provider's servers (usually Google). Either way only the text comes to us (see "The AI features"): we never get the audio, and we never record or save it. What Apple or your speech service keeps is up to their own settings and policies (on an iPhone, "Improve Siri & Dictation"; on Android, your Google voice and audio activity). It listens only from when you tap the mic until you stop it. Before the text is used, the app tidies it on your device (the ums and repeats taken out, a correction you made out loud kept, gear names it misheard put right; on an iPhone or iPad with Apple Intelligence, with Apple's own model, on the device); nothing is sent anywhere for that.

In the EQ and compression labs you can play a file of your own. It never leaves your device: it is played there, and, if it is not too big, kept only in your device's own storage so it is still there next time.

Location

The SPL meter can save where a reading was taken, so you can compare rooms: a place name, like "church" or "the youth room", and map coordinates rounded to about a hundred meters. That is close enough that Apple counts it as precise location, and Google does too, so that is how we describe it in the App Store and on Google Play, but the app keeps only the rounded spot, never your exact one. Your browser or phone asks you first, and if you say no the reading saves without a place. Apart from that, we keep only the rough place (country, region and city) described in "How you use the app", and we do not track where you go.

Using the app offline

If you lose your connection, the lessons you finish and the games you play are kept on your device, for up to 8 days, until the connection comes back, and are then saved to your account like anything else. Until then they are only on that device: if you delete the app before they sync, or stay offline longer than 8 days, they are lost. On the website they can also be lost if you sign out or are signed out (there or on another device), or sign in again, before they sync, so the next person on a shared computer never gets them. Duels need a connection.

Things that are public by link

Two parts of the app deliberately make something viewable without an account, because the person who needs to see it is standing in a room on a Sunday morning and is not going to sign up:

In both cases the link itself is the key. Anyone you give it to can see it, and anyone they give it to can too. You can turn sharing off.

What your team leader can see

If you join an organization in the app, the leaders of that organization can see:

A team leader also gets a weekly email with the same things for their team: how many trained that week, and who has not trained for a while.

They cannot see your private notes, your sound level readings, your personal game scores outside of shared leaderboards, your quiz answers, where you are, or anything from a different organization. If you would rather your leader did not see your training progress, do not join their organization. The app works fine as a personal account.

When you join an organization, it gets a person record for you in its people list: your name, your profile photo and the email you sign in with (only once you have confirmed it). When your organization has its people list here (it is opening to organizations a few at a time), its owners, admins and leaders can add to that record what a church keeps about its people, like a phone number, an address, a household, a birthday, a campus and notes, and people who are not on the app at all can be in the list too, such as a child in your household. Nobody outside that organization sees its people list. If you delete your account, your login and the contact details that came from it (the email you sign in with and your profile photo) come off the organization's record, and, when the organization has its people list here, its admins are told. The organization keeps your name and its own history of when you served, the way a church keeps its records.

When your organization has its people list here, other members of the organization see only its directory: the people who are in it, by name, photo, what they play, whether they are on the app and whether they serve on a team, never their contact details, notes or other details, and never anyone known to be under 18. You are not in the directory unless you or a leader put you there, and you can leave it from your own record. Members also see the names of the people in their own household. Leaders can bring people in from a spreadsheet (a Planning Center export, for example), matched to who is already there by its Planning Center or other system id, email, phone or name, and can merge two records of the same person; a merge keeps a copy of the record it folded in for 30 days, so it can be undone, and then the copy is emptied. A leader can send someone on the list an invitation to the app, to the email the organization has for them. When a person is deleted from the list, their copies go with them.

When your organization has services here (opening the same way, a few at a time), it can plan its services and ask people to serve. Its owners, admins and leaders make the plans (the order, the times, the notes) and put people on them, and a person they ask gets a push if they are on the app and an email if the organization has their address. That email has a button that opens a page where you can accept or decline without signing in; the link in it works only for that one request, until the service starts. We keep whether you accepted or declined, for which times, the reason you gave if you gave one, when you answered, and when you first opened the request, so the leaders can see it has been read. A decline reason, when you first opened a request and your blockouts (the dates you can't serve, and why) are seen only by you and that organization's owners, admins and leaders. Other people on the same plan see your name, your position and whether you said yes or no, never your reason. Before you serve, you get a reminder on the day the team's leaders chose (up to a week before), from 10am in the organization's time zone, if you said yes or have not answered yet; it carries the plan's notes and the notes the leaders wrote for your team. If you use the app, one day's reminders come as one message, so if you serve with two organizations in different time zones, the second one's reminder can come with the first, before its own 10am; by email, each organization's come as one email. To send each reminder only once, we keep a record that it went, with a coded fingerprint of who it went to (not your name, email or account), for two days. If you ask a teammate to cover for you, they are told who asked. If you delete your account, the organization keeps your name with your answers in its plans, the way a church keeps its records; if the organization removes you from its list, your answers stay in its past plans with no name on them, and your blockouts go. You can see the positions you're on in each team and how many people are on each (never the others' names or settings), and set how often you can serve in each; the organization's owners, admins and leaders see and can change that too.

An organization can keep its songs here too: each song's arrangements and keys, the chord charts its leaders paste in, and the practice tracks and PDFs they upload. These belong to the organization, under its own licenses (its CCLI license, and what it bought from SongSelect, PraiseCharts or anyone else). Only that organization's owners, admins and leaders see its song library; a song's chart, words, arrangement notes, tracks and files (with the tags a leader gives them) are shown to the other people on a plan the song is in, and never to another organization or on a public page. The library's own notes, tags and themes stay with its leaders. The files are kept in the organization's own folder, reached through links that last fifteen minutes, and are deleted with the organization (or sooner, when a leader removes them, or the key, item or plan they are on); a file whose upload was never finished is removed when we clean up. When you mark a song "i've practiced this", we keep that and when, in which key, for that plan; the organization's owners, admins and leaders see who has practiced, and you can take it back. We keep no copy of a chart on your device, and we don't report songs to CCLI for the organization: its leaders get a list of the songs it used to report themselves. An organization's owner or admin can also bring its people and plans in from Planning Center, when they choose to. It uses that leader's own Planning Center connection, so it copies what their Planning Center account can see: the people (names, emails and whether one is blocked from mail, phones, addresses, households, campus, birthdate, gender, school grade, whether they are a child, membership, whether they are active and since when, and another system's id if Planning Center keeps one), the teams and who can serve in them, the songs with their arrangements, chord charts, keys and files, the plans from a year back to six months ahead with their items, notes, files and who was asked and how they answered, and the blockouts of the people who serve. It is the organization's own information, copied into that organization only. It only reads Planning Center and changes nothing there; to copy a file it asks Planning Center to open it, as opening it yourself would. A copied file (a pdf, audio or a picture, up to 20 MB, or 50 MB for audio) is kept in that organization's own private storage, and anything else stays in Planning Center. People are matched to who is already on the list by their Planning Center id, then email, then phone, with the first name agreeing. Someone who signs in is matched only by their Planning Center id or an email they proved, and anyone else comes in as a new person. It can be run again to stay in step: what it brought in that nobody here has changed since is brought up to date, and anything a leader or member changed here stays as they left it. On plans that haven't happened yet, the roster, and blockouts that aren't over, what Planning Center no longer has is taken off unless someone here changed or answered it, and only when every import so far used the same Planning Center account; past plans are never changed that way. Nobody is asked, reminded or emailed by us for what it brings in: Planning Center keeps doing that, reminders stay off on an imported plan until a leader turns them on for it, and even then they only go for requests sent from here.

An organization can also keep an app in step with Planning Center both ways, instead of a one-time copy (services today; people come in so the people on its plans stay in step). Its owner or admin connects the organization's own Planning Center once; we keep that connection's tokens sealed (encrypted) so nobody can read them from our database, never show or log them, and hand them back to Planning Center when they disconnect. Planning Center then tells us when something changes, and we read that thing again from Planning Center and keep it in the organization's own rows, with when Planning Center last changed it and when we last synced it. Changes made here that Planning Center takes (an answer to a request, who is scheduled, a plan's title, items, times, blockouts, songs, arrangements and keys) are sent back to Planning Center under the organization's connection, and we keep a record of each change sent (when, what kind, Planning Center's answer; never a token) for 90 days, which the organization's leaders can see. If Planning Center changed the same thing first, Planning Center's stands and the leader sees that. While an app comes from Planning Center, Planning Center asks and reminds the people on its plans, and we don't. Switching it back to on its own stops the sync both ways and keeps everything here. When Planning Center tells us something changed, we keep a note of that notice (what kind of thing changed and which, never its details) for 30 days. If the organization keeps its people on its own while its services come from Planning Center, only the names of the people on its synced plans come in, never their contact details or households. The connection stays until an owner or admin disconnects it, even if the person who connected it leaves. A plan deleted in Planning Center is deleted here too, with its schedule, items, notes and files.

Friends and leaderboards

If you add friends or appear on leaderboards, other users can see your name, username, photo, and the scores or progress that leaderboard covers. You control this in your social settings, including opting out. If you turn off both "Appear in search" and the global leaderboard, people who are not your friends and do not share an organization with you no longer find you in search, on a board, or in a list of profiles. Someone who opens your profile link still sees your name, username, photo, bio and roles. Your scores stay behind the score switch. Friends, your organization, and a leaderboard you still appear on still show your name, username and photo.

The app suggests friends from the people who share an organization or a team with you, people on a team with you first. A suggestion shows their name, username and photo, never an email address. If you turn off "Appear in search", or take friend requests from no one or only from friends of friends, you are not suggested to anyone. If you dismiss a suggestion, we remember that, so it stays dismissed.

You can block someone from their profile or your friends list. Once you do, you don't find each other in search or in suggestions, they can't send you a friend request or a duel, open duels between you are called off (a run already under way still finishes), and on your profile they see only your name, username, photo, bio and roles, not your scores, progress or whether you are online. In a comment thread in your organization (on a stage plot, an incident or a playbook), their comments are hidden from you and you are not told when they comment; everyone else who can see the thread still sees them. If you can remove comments in that organization (an owner, admin or leader), you still see theirs, folded away and marked as from someone you blocked, so you can remove them. They are not told that you blocked them: a friend request they try to send you looks sent to them, but never reaches you. If they block you too, that works like any block: theirs stays until they unblock you, even if you unblock them first. You can unblock them in your privacy settings.

If you invite a friend by email, we send that person one email with your name on it, and we do not email them again about it. We keep their address only to match the invitation when they join. It is removed when they join, when you delete your account, or after a year if they have not joined, and they can email us to have it removed sooner. We also keep a fingerprint of it (not the address) with your invitation, for as long as you have your account (and up to a month after, with nothing that says it was you), so you never send them a second one, and one inbox gets one friend invitation email a month at most. If they tap "don't send me friend invitation emails" in that email, we keep only a fingerprint of the address, not the address itself, for as long as their no stands, so no friend invitation email goes to it again. If the address is already confirmed on an account, they get a notification in the app with your username or name instead, if their settings allow friend requests from you, there has never been a friend request or friendship between you in the app, and they have not already had an invitation from you. You see the same message either way, so inviting an address never tells you whether it has an account.

My rigs

My rigs keeps your rigs and the gear you add to them: each rig's name, what it is for, its power supply, notes and photo, and for each piece of gear its name, brand, kind, colour, size, settings, notes and where it is (on a rig, in your locker, on the shelf or sold). It also keeps what you log (when gear came, moved or sold, maintenance, spending, problems and notes), the boards you save for your memoir, each with a copy of its gear and a photo, and your board layout: where each pedal sits, its cables and their types, and the voltage and power supply you pick for its pedals.

Everyone signed in can see your rigs on your profile, unless you change it. Each rig has its own setting: everyone, friends, or only me. Someone who can see a rig sees its gear in order with its settings and notes, its board layout, the rig's own notes and photo, its saved boards and their photos, when its gear came, moved or sold, its maintenance, and the problems you log on it, so whoever runs sound can help. They never see your spending, your notes, or any entry with a cost on it. A rig you retire is yours alone. Nobody you have blocked, or who has blocked you, sees any of your rigs. What you paid, what you sold for and what anything cost is only ever yours: it never leaves our server for anyone else, whatever a rig is set to.

When you ask CanyonAI about a rig, or ask for help with the band in Sunday SOS, the rigs it reads (yours, and the rig of whoever plays that instrument on your stage plot or whoever you name, only as they let you see it) go to Anthropic with your question, never with a price. CanyonAI adds gear or notes a problem on your rigs only after you say yes. To compare your board with a saved snapshot it reads your own photo, and doesn't keep it. Sunday SOS keeps your rigs, a teammate's rig CanyonAI looked up for you (for two weeks at most, and only while they still let you see it), and the last three weeks of your incident logs on your phone for when there's no signal, and clears them when you sign out. Your rigs, gear, history and saved boards are deleted with your account, and so are the photos.

Tips and updates by email

While WorshipTechU is in beta, we added the accounts with a confirmed email address made before the evening of 7 October 2026 (Vancouver time) to our tips and updates emails, including the accounts that had said no to them. Accounts that had unsubscribed were put back on only after Canyon spoke with each person and they said yes. If you had unsubscribed from our mailing list, you were not added. A new account is asked when it signs up, with the box already checked; uncheck it and we don't send them. Every one of those emails has an unsubscribe link, and you can turn them off in your settings any time. We keep when you were put on them and how (when you signed up, in settings, on the home screen, as a beta account, or by telling Canyon), and when you turned them off, so we don't email you again.

Our emails and the notices in the app only point you to the parts of the app you can open. To choose them, we check what your account and your church open against what each part needs. Every Thursday tip is sent to everyone on the list, whatever you can open. A lesson or course a friend shares with you only reaches you if you can open it, and the friend is told when it couldn't reach you.

The mailing list

If you sign up for the free cheat sheets (at app.worshiptechu.ca/free, on worshiptechu.ca, on a cheat sheet page or from a code at an event), we keep your first name, your email address, whether you lead your team or serve on it, where you signed up, your time zone, and when you said yes and the words you said yes to. We don't keep your IP address. We use them to send you the cheat sheets and then our tips and extras. Every one of those emails has an unsubscribe link: one tap stops them, and we keep your address and when you unsubscribed so we don't email you again unless you sign up again. If you make an account with the same address and confirm it, we connect the two, so the emails can skip what you already use. To keep bots out, we count signups from each address and each network for a day, kept as a scrambled code rather than the address or the network. When someone new signs up, the owner of WorshipTechU gets a notification and an email with their first name and address. If you use a form on the website to ask us for something (a quote, a training weekend, a call, mentorship, the beta, to give, to donate gear, to add us to a missions budget, or to nominate a church), what you write in it and the problems you picked are emailed to us, with your first name, address, whether you lead or serve, which form it was and whether you were already on the list, so we can answer you. We keep that email (Resend, which sends it, sees it and keeps its own record of it for a while), and none of what you wrote is added to your list signup. If it can't be emailed, the owner gets a notification with your first name, address and which form, which stays in his notifications, so we can still write to you. The buttons in these emails carry a code that says which email it was and who it was sent to, so we can tell which emails people use, and we keep a record of which emails we sent you and when. Resend, which sends them, tells us when each one is delivered, each time it is opened, which link was tapped, and whether it bounced or was marked as spam, and we keep that with the email (Resend also sees the network and browser of an open or a tap; we don't keep those, and of a tapped link we keep only the page and which email it was, never the private codes in it). Resend tells us the same about the other emails we send (invitations, receipts), and we keep that too. If you mark one as spam, we stop sending them. When you arrive in the app from one, we note which email brought you. In the app, we also note once a day which tools you open, when you open something your plan doesn't include, and when you look at the plans, so the emails can skip what you already use and tell you about what you were looking at. All of it stays with us: none of it goes to an advertising network. Deleting your account deletes your list signup and that record too. Without an account, email us to have it removed.

Inviting someone to an organization is separate: the invitation comes by email, with one reminder before it expires, and an organization admin can send it again.

The AI features

WorshipTechU includes AI features that answer questions about worship tech and about your own setup. When you use them, your question and relevant context from your account, for example your gear list or your recent sound level readings when they are what you are asking about, are sent to Anthropic, the company that makes Claude, to generate an answer.

You can add a photo to a question for CanyonAI, from your camera or your photo library. The photo is stored privately with your conversation. It is not public: the app shows it only to you, through links that stop working after ten minutes. It is sent to Anthropic with your question so CanyonAI can see what you are asking about. It is deleted when you delete your account.

If you tap "start from my photo" in the avatar builder, your profile photo is sent to Anthropic for a one-time read, so it can describe what it sees and suggest a starting look. Only your own photo is sent, and only when you tap it. We keep no copy of the photo for this, and do not keep Anthropic's description; only the look you end up with is saved, like any change you make, and you can change it.

CanyonAI also works inside some tools. What you say, type, photograph or upload to CanyonAI there is sent to Anthropic to read, with what is in the tool at the time (and in the stage plot designer, the gear locker and the lighting patch, when you ask again, its last suggestion as you left it):

None of it is stored by us. CanyonAI only suggests: you see what it would change and can edit it, nothing is saved until you put it in, and then it is saved like any change you make. The one thing we keep is a usage record of each request: who made it, their organization, which tool and AI model, how much it used and what it cost, how long it took, whether it worked, how many photos or PDFs came with it, and when. We also record the credits used. Weekly credit counters keep your account and organization identifiers. Counters older than the current week and two previous weeks are removed when another AI request is admitted. You can see your balance and your selected organization's shared total; this does not show you anyone else's individual usage. Deleting an account removes its counter and identifying link from the usage record; the organization's and platform's spent totals stay spent. If you talk instead of typing, your voice is turned into text first (in a web browser by the browser: Chrome uses Google for this, Edge uses Microsoft, Safari uses Apple; in the iPhone app by Apple, on the iPhone where it can; in the Android app by the phone's speech service, on the phone where it can and otherwise on its provider's servers), and only the text is sent.

Some questions also trigger a web search to find current information. The search terms derived from your question go to the search provider; your account details do not. We do not use your content to train AI models, and we do not allow our providers to either.

Who we share information with

We share only what is needed, only with these:

We will also disclose information if the law requires it, or to protect someone's safety. If the business is ever sold or transferred, your information would move with it, and we would tell you first.

Some of these companies are in the United States, so your information is processed outside Canada and is subject to the laws there.

How long we keep it

While your account is open we keep your information so the app works. Your progress, your projects and your team history are the product.

Some records have to stay: payment records for tax and accounting, and anonymized or aggregated data that no longer identifies you. Content you contributed to a shared organization, a stage plot the team uses or a gear record, may remain with that organization. You can delete your account from your profile settings in the app.

Your choices and your rights

You can see and correct your information, most of it directly in the app. You can also:

Email canyon@worshiptechu.ca for anything you cannot do in the app. We will respond within 30 days.

Canadian users have rights under PIPEDA and British Columbia's Personal Information Protection Act, including the right to complain to the Office of the Privacy Commissioner of Canada. If you are outside Canada, the same requests above are open to you, and local law may give you further rights. Ask and we will honour what applies.

If you are in the EU, the EEA, the UK or Switzerland

This part is for people in the European Union, Iceland, Liechtenstein, Norway (together, the European Economic Area), the United Kingdom and Switzerland. The GDPR, the UK GDPR and Switzerland's Federal Act on Data Protection give you the rights below, and we follow them. WorshipTechU (Canyon Coulter Lewis, in Canada) is responsible for your information, as the "controller" those laws talk about. Reach us at canyon@worshiptechu.ca.

What we collect. Everything in "What we collect" above, with one difference: the record of how you use the app and the website ("How you use the app") is kept only if you say yes.

We ask first. When the app or the website works out that you are in one of these places (from the rough place our web host gives for your network address), it asks you once, on a small card in the app or a banner on the website, whether we may keep a record of how you use it. Until you say yes, it keeps none of it: no screens, taps, visits, searches or timings, nothing from the device to identify it, and none of the email opens and clicks below. If we cannot tell where you are, we treat you as not being in one of these places. Saying no changes nothing else, and you can use all of the app either way. A no holds wherever you are next. We keep your answer, when and where you gave it, and that you were found in one of these places, so we can show what you agreed to; if we already knew you were in one of them (from your time zone, or the record from before this was added), we count you as found there too. A yes in the app covers both the record of how you use the app and which of our emails you open; a yes on the website covers the website's record (and, when you join the mailing list there, which of the emails to that address you open). Each asks for itself.

Changing your answer. Any time: in the app, in your profile's settings (the cog), under "usage record"; on the website, with "your tracking choice" at the bottom of any page. Changing it to no stops the record from then on and clears what was waiting on your device; to have what was kept before deleted, ask us.

Emails. Our emails are sent by Resend, which notes when an email is opened and which link is tapped, for every email it sends for us. Until you say yes, we keep none of your opens or clicks of our tips, updates and mailing list emails, and their links carry no code saying who tapped them. For other emails (an invitation, a receipt) we keep an open or a click against that email only, not against you. Until you say yes, your tips, updates and mailing list emails, and the emails about what you do in the app, are sent from a second address of ours (notes.worshiptechu.ca) that has Resend's open and click noting turned off, so Resend does not note them either. Other emails (an invitation, a receipt or welcome, a code to confirm an address, an announcement from your organization) still come from the usual address. Tips and updates, and the mailing list, are only ever sent if you asked for them, and every email has a link to stop them.

Why we may use your information (the legal basis):

Your rights. You can ask us to:

We make no decisions about you by computer alone that have legal or similarly serious effects. Email canyon@worshiptechu.ca and we will answer within one month. You can also complain to the data protection regulator where you live or work: in the EU and the EEA, your country's data protection authority (listed at edpb.europa.eu); in the UK, the Information Commissioner's Office (ico.org.uk); in Switzerland, the Federal Data Protection and Information Commissioner (edoeb.admin.ch).

Where your information goes. It is stored in Canada, with Supabase in its Montreal region. The European Commission has decided that Canada protects personal information adequately for businesses covered by PIPEDA, as we are, and the UK and Switzerland recognize Canada the same way, so it can come here from those places without anything more. Some of the companies in "Who we share information with" are in the United States (Vercel, Stripe, Resend, Anthropic, Google and Apple, Planning Center if you connect it, and Supabase itself as a company, though your information stays in Montreal). For them we rely on the protections in each company's data processing terms: the EU-U.S. Data Privacy Framework, and its UK and Swiss extensions, where the company is certified, and otherwise the standard contractual clauses the European Commission (and the UK and Switzerland) approved. Ask us and we will tell you which applies to which company.

How long we keep it. As in "How long we keep it" above.

If you are in Quebec

Quebec's privacy law (the Act respecting the protection of personal information in the private sector, as changed by Law 25) says technology that can profile you stays off until you turn it on. So in Quebec the app and the website treat you as they treat people in the EU: they ask you first, on the same small card or banner, and keep none of the record of how you use them, and none of your email opens and clicks, until you say yes. You can change your answer the same way, any time. If we cannot tell that you are in Quebec, we treat you as being elsewhere in Canada.

You can ask to see, correct, delete or get a copy of your information, as in "Your choices and your rights", by emailing canyon@worshiptechu.ca. Canyon Coulter Lewis is the person in charge of protecting personal information at WorshipTechU. You can also complain to Quebec's Commission d'accès à l'information (cai.gouv.qc.ca).

Security

Information is encrypted in transit and at rest. Access inside the app is limited by your account and your role, and the database enforces this rather than just the screens. We limit who on our side can see user data.

No system is perfectly secure and we will not pretend otherwise. If a breach ever affects your information, we will notify you and the relevant regulator as the law requires.

Children

You need to be at least 13 to have your own WorshipTechU account, or at least 16 in the European Union, the European Economic Area or the United Kingdom.

Nothing in WorshipTechU is unsuitable for a younger audience. It is worship team training, and we would be glad for a twelve-year-old drummer to learn from it. The reason for the age limit is not the content. It is that an account here stores a name, a photo, a bio, your training progress, and can connect you to other people through friends, leaderboards and comments. Looking after that properly for children under 13 carries legal obligations we are not set up to meet, so we do not knowingly collect information from anyone under 13, or under 16 in those places.

We do not ask your exact age or birthday, and we keep none. When you make your account, if the app finds you are in one of those places (the rough place from your network address, or your device's time zone), the profile step asks you to say you are 16 or older before you can go on. If you are under 16 there, you can delete the account you just made from that step, with everything in it, or email us and we will.

If you are under that age and want to learn this material, ask a parent, guardian or your team leader. They can hold the account and work through it with you, which is how most younger volunteers learn on a team anyway.

If we find out we have collected information from a child under that age, we delete it. If you think a child has given us their information, email canyon@worshiptechu.ca and we will take care of it.

Changes to this policy

If we change this in a way that matters, we will tell you in the app or by email before it takes effect. The date at the top always reflects the current version.

Contact

canyon@worshiptechu.ca
Canyon Coulter Lewis, carrying on business as WorshipTechU
BC sole proprietorship registration FM1094836
26890 32A Ave, Aldergrove, BC V4W 3G4, Canada