PRIVACY

How Livefy handles your information

Last changed 22 October 2026.

The short version

We do not record or keep the sound of your services, and we keep the words only if your church turns transcripts on.
People who read captions or listen on their phones need no account, and we ask them for nothing that names them.
We do not sell anybody’s information.
The public pages and the sign-up page carry Google’s ad tag, so that Google can tell us which clicks on our ads led to a sign-up, and can show our ads to people who have visited (see Visitors to this website).
You can ask us for a copy of your information, or to delete your account, at hello@livefy.live.

During a service

The sound from your microphone (or, while a video you added plays during a service, the video's own sound) goes from your browser straight to our speech service, which turns speech into words and translates them. The words it hears are sent through our server to an AI translation service to be translated, and each translated line goes to one once more to tidy its punctuation. The translated voice on phones is made by our speech service. If the church chooses the whole-sentence voice, the translated lines also go through our server to the translation service, to be written for reading aloud.

We do not record or keep the sound, and our server keeps none of the words unless your church keeps transcripts. These services process the sound and the words to give you captions and voice, under their own terms for business customers.

We also keep our speech provider’s record of each connection: when it opened and closed, and how long it listened. It holds no words. We use it only to count translation time that a church’s computer did not report, for example after a crash.

Dubbed audio and subtitles for a video: when someone at the church makes dubbed audio, or subtitles that match a video, from a kept service, the recording they choose is read on their own computer. To line it up with the service, about a minute of its sound is sent through our server to our speech service, which finds where the words are; that minute is deleted there straight away and is kept nowhere. The rest of the recording never leaves the computer. For dubbed audio, the kept words of that service are sent through our server to an AI translation service, which translates the sermon again as one text; the translation is sent, a paragraph at a time, to our speech service to be read aloud; and the finished files, one per language, are made on that computer, in its browser’s own storage, and removed from there a few minutes after the dub window is closed, or else the next time Livefy is opened on that computer.

Captions and the voice reach phones and screens through our relay. It holds the lines of the service so far, as text, so that a phone that joins late can catch up or read from the beginning, and deletes them when the service ends. It keeps a small record of the service (the church’s name, its languages and how many phones followed) for a day after it ends, then deletes that too.

People reading or listening on phones and screens

They need no account, and we ask them for nothing that names them. Their phone connects to our relay to receive the captions and the voice. We count how many phones are connected, and the relay notes, for fixing faults, whether the sound is playing. A phone may remember its chosen text size on the phone itself. As for every visitor, the phone’s internet address and browser appear in our web server’s log, and in an error report if the page runs into an error (see below).

What we keep about a church’s account

When a church signs up and uses Livefy, we keep:

The church’s name, and the email address and, if given, the name of each person with an account, with their password kept only in a scrambled form we cannot read back.
The phone number given by the person who starts a free trial, asked once after the email address is confirmed. We use it only to call about setting up and using Livefy; we never share it and never send advertising to it.
The email address of anyone invited to help run services, from the invitation on.
If you book a call on the website: your name, your church, your email address, the phone number to call, anything you write in the note, the time you chose, your time zone and the internet address the booking came from. We use them only to make the call and to stop misuse of the booking page.
The names you type in for the people who run services, the details of your usual service (its name, day, time and room) and your settings.
Your plan and payments. Our payment processor handles the card; we keep its reference numbers and, when a card is added to a free trial, the fingerprint it gives that card, so one card starts one trial.
A record of each service: its name, when it started and ended, who ran it (the account and the name chosen at Go live), the spoken and caption languages, the minutes of speech, and how many phones followed it.
A record of each dub: the service and language it was made from, who made it, the stretch of the service it covered and the hours it used.
A transcript of each service, only if the church’s owner turns transcripts on in the console. They are off unless the owner chooses them, and turning them off deletes every transcript already kept (copies in the nightly backups go within 30 days). When someone at the church asks for a sermon summary, the kept words of that service are sent to an AI service to write it; the summary is handed back and not kept.
Any star rating or comment you send us. If you agree to it being published, also the name, the role and the photo you give with it, which may then appear on this site.
Any message you send with Send feedback in the console, with your email address, the console page you were on, the version of Livefy and your browser, so we can read it, find a problem again and answer you. It is also emailed to us.
Your welcome card, if you set one up: its words, colours and the logo you upload. The card is made to be shown in your room, so anyone with its link can see it, logo included.
Slides you load to show on your screens, as pictures. Each is sent to our server as soon as it is added, so screens on other computers can show it, and the screens and phones of a service are told its address. Anyone with that address can see it. Each slide is deleted 7 days after it was last sent to us. Slides you keep in the console are sent again each time the console opens, so they stay while you keep them.
If you arrived by a link carrying ad tags (see Visitors to this website), those tags.
If your church signed up with another church’s referral code, which church that was, and whether the hours the referral earns you both were given or taken back. To make sure it is a different church, we compare the card fingerprints and payer email addresses our payment processor shows for the two churches’ payments, and the email addresses of the people with an account at each; and we note for ourselves when both signed up from the same network, or paid with cards of the same brand ending in the same four digits. When the hours are given, each church is told the other’s name, and the church that gave the code is told the other paid for its first plan; nothing else about either church is shared with the other.

Each sign-up, each sign-in on the sign-in page, each failed sign-in and each sign-in by a confirmation link is recorded with the email address used, the internet address it came from, the browser, the time, and the approximate place our network provider reports for the connection (country, region, city and rough map coordinates, usually where the internet provider routes the connection rather than where the person is). A signed-in try at starting a translation from a phone, which Livefy does not allow, is recorded the same way. We also receive an email about each new sign-up with the same details.

We use this to protect accounts, to see and stop misuse, and to give each internet connection one free trial every 30 days. An email address used for misuse may go on a list of addresses that cannot sign up, with the reason.

Visitors to this website

We count visits to the public pages without cookies: which page was read, the site that linked to it, the country, and a key made fresh each day so that one person’s visits on one day count once. The count does not store the internet address.

If you arrive by a link that carries campaign tags or an ad click code (Facebook adds a click code to most links people follow from it), your browser keeps those, with the page you landed on and the site that sent you, for 30 days, and removes them the next time you open this site after that. We use them only if you sign up, to tell which ads bring churches, and then your browser forgets them. Your browser keeps nothing like this for any other visitor, and we send none of it to Facebook or Google ourselves (Google’s tag, below, sees the address you arrived at). The address you arrived at, tags included, is also in our web server’s log, like every request (below).

If a page runs into an error, it sends us the error, the page address, the browser, the internet address and, when someone is signed in, the church, so we can fix it.

Like any web server, ours logs each request: the internet address, the full address asked for, the page that linked to it, the time and the browser. That log is deleted after 15 days at most. Our server’s own log records faults, such as an email that could not be delivered and to whom, and is written over as it fills up. Some faults also go on a list we keep, which can name an email address that could not be reached.

The public pages and the sign-up page also load Google’s tag for Google Ads. It sets cookies, and sends Google the page you are on, the page that sent you, your browser and your internet address, and, if you came from one of our Google ads, that click. When someone signs up, it tells Google that a sign-up happened, without the name, the email address or the church. Google uses this to tell us which of our ads led to sign-ups. We may also ask Google to show our ads to people who have visited this site: Google shows them on other websites across the internet, and uses its cookies to choose them from your earlier visits here. This means Google can collect information about your activity here and on other websites over time; see how Google uses information from sites that use its services. Visitors whose connection Google places in the European Economic Area, the United Kingdom or Switzerland get no advertising cookies from it, and their visits are not used to personalise ads; Google is still sent, without cookies, the page, the page that sent you, your browser, your internet address and whether a sign-up happened. No other page loads it: not the phone and feed pages, invitations, password resets, the console or admin, and those pages do not pass their address on to the page opened next.

One of the typefaces on this site comes from a web font service, so your browser fetches it from there, as it does on most websites.

Cookies and what your browser keeps

Two cookies of ours, both needed for the account: one keeps you signed in, and one, set when you sign up, lets the confirmation link sign in only the browser that signed up.

On the public pages and the sign-up page, Google’s tag sets cookies of its own, to link a click on one of our ads with a sign-up that follows, and to show our ads to people who have visited (see Visitors to this website); it sets none for visitors whose connection Google places in the European Economic Area, the United Kingdom or Switzerland.

Your browser also keeps some things on your own device: your choices, such as light or dark, text size and how the console is laid out; on the computer that runs services, the name of whoever is running one and what is needed to resume it, any slides loaded there until they are cleared or taken out of the saved slides, and any videos added there, until they are cleared or for 7 days after they were added, whichever comes first; and the ad tags described above. None of it is sent anywhere, except the ad tags, which come to us only if you sign up, and the slides, as described above. Videos are never sent to us.

Do Not Track: the site does not change for that setting. A browser or extension that blocks Google’s tag stops it, and every page works the same without it.

Who else handles information for us

These companies do work for us, each only for the part below:

Our speech service: speech recognition, translation and the translated voice, on phones and in dubbed audio.
AI translation services: translation of the words recognised, tidying the punctuation of each line, writing translated lines to be read aloud when a church chooses the whole-sentence voice, writing a sermon summary from a kept transcript when a church asks for one, and translating a kept sermon again as one text for dubbed audio.
Our payment processor: payments and card details. It keeps its own record of each church that opens a checkout or adds a card (the email address and the church’s name), and of its payments.
Our email service: the emails we send you, such as the confirmation link, a reminder to confirm, password resets and invitations to help run services, and the notices we send ourselves about new sign-ups and faults. Payment receipts come from our payment processor.
Our network and storage provider: delivering the site, the approximate place of each connection, the relay to phones and screens, and storing photos and backups.
A web font service: one of the typefaces the site is drawn in.
Google Ads: our ads on Google, and Google’s tag on the public pages and the sign-up page (see Visitors to this website).
The companies that host our database and our server, both in Oregon, in the United States.
A map service: the map on our own admin page that shows roughly where sign-ins came from, so its servers receive those rough areas when we open it.

How long we keep it

A church’s account information: while the account exists.
Transcripts: until the church deletes them or turns transcripts off, or the account is deleted.
Slides: 7 days from the last time each was sent to us.
A call booked on the website: until you ask us to delete it, because it is how we remember who we spoke to and stop misuse of the booking page.
A copy of the whole database is made every night to our storage provider, so that nothing is lost if something breaks. Each copy is deleted after 30 days.
The web server’s log: up to 15 days. Our server’s own log is written over as it fills up. Until 23 September 2026 it also noted the start of each line heard and of its translation; those old lines go the same way.
Sign-in records, the list of addresses that cannot sign up, error reports, our list of faults and visit counts: with no end date, including after an account is deleted, because they are how we stop repeated free trials and misuse, and find what went wrong.

When an account is deleted

We remove the church, its people and invitations, its services, transcripts and settings, its welcome card and logo, its slides, any feedback it sent (the copy emailed to us stays in our mailbox until we delete it), and any rating or testimonial with its photo. A testimonial already shown on this site comes off when we next publish the site, which the deletion reminds us to do. We keep the record of any refund we made, and the sign-in records, error reports and faults described above. Copies made before the deletion stay in the nightly copies, and in the backup copy of photos, for about 30 days. Our payment processor keeps its own records.

Your choices

Write to hello@livefy.live to ask for a copy of what we keep about you, to correct it, or to delete your account. We reply within 45 days. We do not sell personal information. To keep Google’s tag out, block it in your browser; the site works the same. Turning off personalised ads in Google’s My Ad Center, signed in or not, stops Google personalising the ads it shows you.

The church’s owner can turn transcripts on or off in the console at any time. Turning them off deletes every transcript already kept.

Children

Livefy is for churches and organisations. Accounts are for adults. Children can read captions or listen on a phone like anyone else, and that needs no account and asks for nothing that names them.

Who we are

Livefy is run by Genesis One, a trade name of MARDANIA LLC, 2834 Hamner Ave #1014, Norco, CA 92860, United States. “We” on this page means MARDANIA LLC, doing business as Genesis One.

Changes and contact

If what we do with information changes, this page changes first, with its date. Questions go to hello@livefy.live, or by post to MARDANIA LLC (Genesis One, Livefy), 2834 Hamner Ave #1014, Norco, CA 92860.