Privacy, in plain words.

Voclyn is made in Vancouver, BC, Canada, by Voclyn Atelier Inc.. We provide live captions and AI voice translation for church services. When this page says “we”, it means Voclyn Atelier Inc.; “your church” means the church or organization that holds an account.

We follow Canada’s federal privacy law (PIPEDA) and British Columbia’s Personal Information Protection Act (PIPA). For the information a church puts into Voclyn about its own services, we act on the church’s behalf and only on its instructions, as our data processing addendum sets out.

Our privacy officer is our founder, who is responsible for how Voclyn Atelier Inc. handles personal information. Privacy questions and requests go to hello@voclyn.com. A person reads every message.

You scanned a QR code or typed a church’s link, and you read or listen along. For you:

• No account, no name or email, no cookies, no tracking. The listener page has no advertising or analytics trackers and never asks who you are.
• It never uses your microphone, camera or location.
• Your language, text size and similar choices are saved on your phone (in the browser’s storage), not on our servers, so the page remembers them next Sunday.
• To deliver the captions and voice, our servers see what any website sees: your network (IP) address and browser type. Your network address is kept briefly, for security: we use it only to run the service and protect it from abuse, and it stays only in short-lived server logs.
• We count how many people follow each service, in which language, and for how long, as numbers only, so the church sees how many people were served. These counts are never linked to a person.
• Once we switch error reports on, a page that breaks tells our own server what went wrong, and we pass that to Sentry (see who helps us) without your network address or anything said in the service. Your phone never contacts Sentry itself.
• If you ask for a language your church doesn’t show, we count the request: which language, and on which day. Nothing else is kept with it, so the church sees that someone asked, never who.

During a live service, the sound from the church’s sound desk is streamed to our servers, turned into text by a speech-recognition provider, translated, and, where someone is listening, spoken by an AI voice. We do not record or keep the service audio. It is processed as it arrives and then discarded. The AI voice is held only for the few moments it takes to play.

Transcripts are saved only if the church turns on “Save transcripts” for a room. Saved transcripts are kept for the period the church’s plan includes (the last service on Free, 90 days on Chapel, 12 months on Church and Campus); when the free month ends or the church moves to a plan that keeps them for less time, the older ones stay 14 more days before they go. We delete them sooner whenever the church asks.

A church can add words to its glossary (for example its pastors’ names). The church’s name and glossary go to the speech-recognition provider (up to 150 terms) and to the translation provider, so names come out right.

Our providers process speech and text to provide the service and, under the terms we use, do not use it to train their AI models.

Three things in Voclyn are done by AI, and each is labelled where people see it:

• Speech recognition turns what is said into text (Soniox, or ElevenLabs when a room includes Cantonese).
• Translation turns that text into each language its listeners choose (Google Gemini). On the listener page every translation carries an “AI” label, and the page says it is not checked by a person.
• The AI voice reads the translation aloud for those who choose to listen (Alibaba Cloud’s Qwen, in the voice of a person the church recorded if it chose one, see cloned voices; Google Gemini in the languages Qwen doesn’t speak, and whenever Qwen is slow to answer). It is always called “AI voice”, never presented as a person; a voice made from someone’s voice is named as theirs on the phone (“Pastor David’s AI voice”), and the page says it was made with their permission.

What is preached is never changed. We don’t write, summarise, shorten or soften a sermon. The translation is instructed to add nothing and leave nothing out, apart from “um”s and false starts, and to follow the church’s glossary for names and words like 神 or 上帝. AI can still mishear or mistranslate, which is why it is always labelled.

Scripture comes from a Bible, not from AI. When the preacher names a passage and reads it, listeners in English, Spanish, Korean, Cantonese and Mandarin see it from a public-domain Bible in their language, on their phones and on the big screen, labelled “Published text · not AI” (see the versions). A reading that wasn’t named first, and every other language, is translated like the rest of the service, following the wording of each language’s classic Bible, and carries the AI label.

Audio is streamed, not stored. The sound from the desk goes to our live server and on to the speech-recognition provider as it happens; we don’t record it or keep it. We send every translation and voice request to Google with its storage option switched off. The one thing we ask Google to keep is the translator’s instructions, with the church’s name and glossary: so that they aren’t sent again with every sentence, they sit in a Gemini cache that expires 30 minutes after it was last renewed, and we renew it only while a service is using it. Alibaba Cloud receives only each sentence to read and the voice to read it in. The text is saved only if the church turns on “Save transcripts” (see service audio and transcripts); otherwise only the last few lines are held in the live server’s memory, so someone who arrives late can catch up.

You can always ask a person. If something was translated wrongly, or you want to know how AI was used in your service, write to hello@voclyn.com. A person reads every message and answers.

A church whose plan includes it can record a person’s voice, usually its pastor’s, so that the AI voice reads translations in that voice. Only with that person’s own consent: they read a statement of what the voice is for, in the language they will read aloud, sign it with their name and tick the box themselves, then say so in the recording itself: it opens with “This is my own voice, and I agree to it being cloned”. Before anything is cloned, our speech-recognition provider transcribes the recording and we check that it says those words, so a recording of someone else can’t become a voice. We keep their name, the statement as they read it and the date with the voice, and what the recording says, with its language. Our terms forbid cloning a minor’s voice (see children).

The recording goes to our voice provider, Alibaba Cloud (Model Studio, in Singapore), which makes the voice from it, reviews each new voice before it can be used, and keeps the voice until it is deleted. We don’t keep the recording ourselves. Every sentence the voice reads is sent to Alibaba Cloud to be spoken in it. In languages the voice can’t speak, the stock AI voice reads instead.

A room’s voice is chosen for each language, not for each speaker, so it reads everything translated into that language in the room, whoever is speaking: a guest preacher’s words too. Listeners see it named as an AI voice made from that person’s voice, with their permission. If a church moves to a plan with fewer voices, or none, the voices beyond it are kept, unused, for 90 days: a plan that includes them again brings them back, and after that we delete them at Alibaba Cloud.

The church can delete the voice at any time from its settings, and we delete it at Alibaba Cloud at the same time. The person whose voice it is can also ask us directly at hello@voclyn.com. We keep the record of their consent (name, statement and dates) while the church’s account is open, even after the voice is deleted, so it can be shown that it was given.

When you try the demo with your voice, your microphone audio is processed live, exactly like a service, to show you captions and play the AI voice. It is not recorded or kept. The browser asks for your permission first, and you can stop at any time.

To share the free demo time fairly (2 minutes a day), we keep a count of demo seconds against a scrambled form (a hash, mixed with a secret of ours) of your network address, never the address itself. We delete it after two days.

The demo no longer makes an AI voice of your own voice. One made before 2 November 2026 (“Hear it in your own voice”) is deleted within the 24 hours you were told, or as soon as you open our website again in the same browser; we never kept the recording.

We count visits to our website ourselves, with our own code and in our own database, so we can see which pages help churches and where people get stuck. Counting visits uses no cookies, and no advertising or analytics companies. The listener page and the big screen send none of this.

• For each page you open we note the page, the website that sent you (its address without anything after a “?”), any campaign tags in the link, the type of browser, system and device, the screen’s width, the browser’s language, and the country your time zone points to. We also note clicks on links and buttons, how long a page was on screen and how far down it was read, and the steps of setting up a church and of the voice demo, never what you type into them.
• To count a visitor once a day without a cookie, our server mixes your network (IP) address and browser type with a random value that changes every day, and keeps only the scrambled result (a hash). The random value is deleted the next day, so the hash can’t be traced back to you or linked to your visits on other days. We never keep the address itself.
• If you’re signed in to a church account, the pages you use in the dashboard are recorded with your account, so we can see how Voclyn is used and help you. When you create an account, we note how you first found us: the page you arrived on and the site or campaign that sent you.

We keep these counts for 13 months, then delete them.

Microsoft Clarity also shows us how our public pages and setting up a church are used: where people click, tap and scroll, as heatmaps and as replays of a visit. Anything you type into a form never leaves your browser, and numbers and email addresses on the page are hidden too. Clarity runs without cookies: we tell it no one has agreed to any, so it sets none and can’t link the pages you load, or your visits, to each other. Microsoft sees your network address and browser, to tell the country. Clarity never runs on the listener page, the big screen, the sign-in pages or the dashboard.

Separately, to protect our pages from abuse, our servers use your network address briefly to limit how often it can call some of them, such as the visit counter, the demo’s link check and the opt-out form.

Once we switch them on: the sign-up, sign-in and password-reset forms run a bot check from Cloudflare as they open, which sees your network address and browser but never what you type; and when a page breaks, an error report goes to Sentry, with network addresses, email addresses, sign-in tokens and the words of services taken out first. Both are in who helps us.

The listener page and the big screen set no cookies. A few other pages set cookies of our own that make them work. None is for advertising or follows you to other sites, and none is shared with anyone:

• The live demo on our home page, once you name a church in it: demo_church, the church you set up (its name, building, tradition and languages), so that setting it up for real starts from it. It lasts 30 days.
• Setting up a church (/onboarding): ob_draft, the church you are setting up, so that a reload or signing in doesn’t lose it. It lasts 30 days, and is cleared once the church is created.
• Signing in: our sign-in provider’s cookies, which keep you signed in until you sign out or the session ends.
• The dashboard: dash_theme (light or dark), sunday_lit (the trial Sundays it has already shown) and kit_printed (whether the print kit was used), each for a year, and press_pulled (which print sheets have already played their animation) until the browser closes.

Microsoft Clarity, on our public pages and while you set up a church, sets no cookies: we tell it not to.

Other choices are kept in your browser’s own storage, never in a cookie: on the listener page your language and text size; on our website the motion setting and the church you set up in the demo.

To give your church its account, we keep:

• Your name, email address and password (stored only in scrambled, hashed form by our sign-in provider). If you continue with Google instead, Google tells us your name, email address and profile picture and confirms the address is yours; we never see your Google password.
• Your church’s name, link, rooms, languages, glossary, settings, and who is on your team with which role.
• Usage counts (speech-hours, languages, listener numbers) for your dashboard and your plan, and the dashboard pages you use (see when you visit our website).
• If your church uses our API or webhooks: its API keys, of which we keep only a scrambled form; its webhook addresses and their signing secrets; and, for 30 days, what was sent to each address and how it answered.
• What your team writes to us in the dashboard’s Support page, and our answers. With each new conversation we keep the dashboard page it was written from, your plan and role, whether a service was live, and your browser and device type, so we can see what went wrong without asking.
• Billing details, held by Stripe. We see the plan, the amounts and the last four digits of a card, never the full number.

We use this to run your account, help you on Sunday morning, send you emails about your account and trial, and keep the service safe. We do not sell personal information, and we do not use it for advertising.

We sometimes email churches that might want Voclyn. We write only to an address a church has published itself (on its own website or social page, or in a directory it gave its details to), only to the church office or to someone whose role fits what we offer, such as a pastor or whoever runs the sound desk, and never to an address whose page asks not to be sent offers. We don’t buy lists or guess addresses.

For each church we write to, we keep:

• the church’s name and website;
• the name and role of the person we write to, when the church’s page gives them;
• the work email address the church published, the page we found it on, the date we found it, and a dated copy of that page;
• what we sent and when, and your answer if you reply.

We use this only to offer Voclyn to your church, and to show where your address came from if we are ever asked. We don’t sell it or share it, except with the email services we use to send our emails and to check that an address works, which handle it only for us. We keep it for three years after the last email we send to that address, then delete it.

One request stops all our marketing email. Reply to any of our emails asking us to stop (“no thanks” is enough), use the link at the bottom of it, or enter your address on our opt-out page. It stops every marketing email from Voclyn Atelier Inc. to that address, from any of our addresses and not only the series it came in, as Canada’s anti-spam law (CASL) requires. It takes effect within 10 business days, usually the same day. We then keep your address on our do-not-email list, with no end date, so that we never write to it again, and we use that list for nothing else.

We use these companies to provide Voclyn. Each receives only what it needs for its job.

• Soniox

  Turns speech into text (speech recognition), and checks that a recording for a cloned voice says the person’s consent.

  Receives: Service audio and demo audio, live; your church’s name and up to 150 of its glossary terms, so names are heard right; the resulting text. A recording for a cloned voice, deleted at Soniox as soon as it has been read.

  Where: United States

• ElevenLabs

  Speech recognition for rooms that include Cantonese.

  Receives: Service audio, live; the resulting text.

  Where: United States

• Google

  Translates the text (Gemini), and reads it aloud in the languages Alibaba Cloud’s voices don’t speak. Signs you in when you choose “Continue with Google”.

  Receives: Transcribed text; the translator’s instructions with your church’s name and glossary, held in a cache for up to 30 minutes after a service last used them; translated text. For sign-in: your name, email address and profile picture.

  Where: Where Google processes Gemini requests (we can’t choose the region)

• Alibaba Cloud

  Reads the translation aloud as the AI voice, and makes and keeps cloned voices (Qwen, in Model Studio).

  Receives: The translated sentences the AI voice reads. For a cloned voice: the recording it is made from and its language, never the person’s name; Alibaba Cloud reviews each new voice before it can be used, and keeps it until the church deletes it in Voclyn or closes its account, or 90 days after the church’s plan stops including it.

  Where: Singapore

• Stripe

  Takes payments and keeps billing records.

  Receives: Billing name, email, address and payment details (we never see full card numbers).

  Where: United States and the other countries where Stripe works

• Resend

  Sends the emails a Voclyn account needs: sign-up confirmations, sign-in links and password resets, and account emails (the welcome, the free month ending or ended, a payment that didn’t go through). Also our own alerts when a church’s service runs into trouble.

  Receives: The email address each one goes to, and the email itself, with its links: an account email names the church and carries its link and QR code, its plan and dates. Our alerts name the church and room, never what was said.

  Where: United States

• Sentry

  Tells us when something breaks on our website, in the dashboard or on our live servers (error reports), once we switch it on.

  Receives: The error and where in our code it happened, with the page’s path. Before a report leaves our servers we take out network addresses, email addresses, sign-in tokens and anything said in a service (captions and transcripts). Reports from your browser go through our own server first, so Sentry never sees your network address.

  Where: United States

• Cloudflare

  Checks that a person, not a bot, is using our sign-up, sign-in and password-reset forms (Turnstile), once we switch it on. Most people never see it.

  Receives: While the form is open: your network (IP) address, your browser’s type (user agent) and connection fingerprint (TLS), and our site’s key and which form it is. Never what you type. Cloudflare uses them to tell people from bots, and to improve that check.

  Where: Cloudflare’s worldwide network (we can’t choose the country)

• Microsoft

  Shows us how our public pages and setting up a church are used, as heatmaps and replays of visits (Clarity). Never on the listener page, the big screen, the sign-in pages or the dashboard.

  Receives: On those pages: what the page shows and what you do on it (clicks, taps, scrolling, mouse movement), with anything typed into a form, numbers and email addresses left out; the page’s address and the site that sent you; your browser, device, screen size and network (IP) address, from which Microsoft tells the country. No cookies.

  Where: Where Microsoft’s Azure cloud keeps it (we can’t choose the region)

• Supabase

  Our database and sign-in.

  Receives: Accounts, church settings and logos, rooms, glossary, team invitations, usage counts, saved transcripts, the consent records of cloned voices, the demo’s counts against scrambled addresses, API keys (only a scrambled form), webhook endpoints and the log of what was sent to them, our website’s visit counts, and the addresses entered on our opt-out page.

  Where: United States (us-east-1, Virginia)

• Render

  Hosts our website and live servers.

  Receives: Everything that passes through the service, in transit; server logs.

  Where: United States (Virginia)

Each of these providers stores or processes information outside Canada: in the United States; for the AI voice and cloned voices, in Singapore; for the bot check, wherever Cloudflare’s network handles it; and for Clarity, wherever Microsoft’s cloud keeps it. It is protected there by our contracts with them, but it may be accessible to authorities under the laws of those countries. Before a new provider receives any information from a church’s account or services, we add it to this list and tell account holders, at least 14 days ahead (see changes to this page).

Sentry and Cloudflare were added on 1 November 2026, before we use them: neither receives anything until we switch it on, at least 14 days after we have told account holders. Microsoft (Clarity) was added and switched on on 2 November 2026: it sees only our public pages and setting up a church, never a church’s account, dashboard or services.

• Service audio: not kept.
• Saved transcripts: for your plan’s period, then deleted automatically (14 days later when the free month ends or the plan changes to one that keeps less), unless the church asks us to delete them sooner.
• The translator’s instructions at Google (with the church’s name and glossary): up to 30 minutes after a service last used them.
• Demo time counts (the scrambled network address): two days.
• A church’s cloned voice: at Alibaba Cloud, until the church deletes it in Voclyn or closes its account; a voice beyond the church’s plan, 90 days after the plan stopped including it; its recording: not kept by us. The record of the person’s consent: while the account is open, even after the voice is deleted.
• Webhook deliveries (what was sent to a church’s webhook address, and how it answered): 30 days.
• Website visit counts: 13 months. The random value that scrambles network addresses: deleted the next day.
• Clarity’s recordings of our public pages: up to 30 days, at Microsoft.
• Account information, including API keys, webhook settings and support conversations: while the account is open. When a church closes its account, we delete it within 30 days, apart from what the law requires us to keep.
• Billing records: as long as Canadian tax law requires (generally six years).
• What we keep about churches we write to: three years after the last email we send to that address.
• Our do-not-email list: with no end date, so that an address that asked us to stop is never written to again.
• Server logs: a short time, for security and to fix problems.

You can ask us what personal information we hold about you, ask us to correct it, or ask us to delete it, by writing to hello@voclyn.com. We answer within 30 days. If the information belongs to a church’s account, we may ask the church to confirm. If you asked us to stop emailing you, a request to delete what we hold leaves your address on our do-not-email list, so that we never write to you again.

You can withdraw your consent at any time, for example by closing your account or, if we wrote to your church, by asking us to stop emailing you. If you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia.

Everything between your device and our servers is encrypted in transit. Each church can see only its own information, and that rule is enforced in the database itself. Only the few people who run Voclyn can reach our systems, and only to keep the service running or when you ask for help. Our security page has the detail, including what we haven’t verified yet.

If something ever goes wrong with your information, we will tell you and the regulator as the law requires, and say plainly what happened.

Anyone, of any age, can follow a service: the listener page asks for no personal information at all. Church accounts are for adults acting for their church.

Voices are cloned only from adults. Our terms forbid a church to clone the voice of anyone under 18 (or under the age of majority where they live, if that is higher). If you think a child’s voice was cloned, write to hello@voclyn.com and we will delete it.

When we change this page in a way that matters, such as keeping something longer or using it for something new, we will email account holders at least 30 days before the change takes effect, and show the date at the top. A new provider that will receive information from a church’s account or services is added to the list, and account holders told, at least 14 days before it receives any. If we must change sooner to keep the service running or safe, we tell you as soon as we can. Our terms explain how the service itself works.