Privacy policy
Who handles your data
The data controller is ZapLive Limited. For any request: info@zaplive.app.
What data we collect
- Account: email address or, if you sign up that way, phone number, username, display name, and whatever you add to your profile (bio, pronouns, link, photo).
- Date of birth and country: we ask for your date of birth when you sign up, and after you log in if you already had an account; when you sign up we also store the country you're connecting from, worked out from the connection, because the minimum age varies from country to country. We don't show them to anyone and we don't give them to Google: we use them to check the minimum age, to apply the rules for anyone under 18 and to choose which ads to show you.
- Content: the videos and photos you post, the thumbnails and audio your phone extracts from them, the captions, the labels and the comments. We store direct messages only end-to-end encrypted: we can't read them.
- Interactions: likes, saves, follows and follow requests, views and shares. Videos you've liked only show on your profile if you choose to show them, in Settings → Privacy.
- Lives: if you broadcast, the title, times, choices and figures of each live; if you watch, the comments you write. The video and audio pass through in real time and we don't record them («Live» section).
- If you withdraw diamonds: your Stripe account ID, the country, the verification status and your withdrawal requests.
- App usage: for each video you watch, for how long, whether you finish it, rewatch it or skip it, along with the app version. This data is linked to your account, and we use it to choose the videos in For You.
- Country of posts: for each post we store the country it was published from, worked out from the connection, for the sound charts by country. It isn't shown on the post.
- Account country: a country for your account, and for 24 hours the country of your last connection, so we know which features are available in your country («Your account's country» section).
- Devices: for each device you sign in on, an identifier created by the app, the public keys for end-to-end encryption, the operating system (iOS or Android) and the last time you used it; if you turn on notifications, also the code Apple or Google use to deliver them, the language to write them in and the phone's time zone, which we use to avoid sending notifications at night to anyone under 18.
- Reports and appeals: what you send us when you report something or appeal a decision («Moderation and reports» section).
We don't collect your precise location and we don't read your contacts. For advertising, Google collects some data from the app: you'll find it in the «Advertising» section.
If you use BlindMatch, also the gender you indicate, the blurred photos if you choose to show them, and who you met and when; not the messages («BlindMatch» section).
If you choose «Near me» in BlindMatch, also your approximate location, only while you're searching and without saving it («BlindMatch» section).
Why we process them
To let you use the app (performance of the contract), to keep the platform safe and moderate abuse (legal obligation and legitimate interest), to check the minimum age and protect minors (legal obligation and legitimate interest), to offer in each country the features available there and to comply with its laws (legal obligation and legitimate interest), to order the feed sensibly (legitimate interest), and to show ads (legitimate interest, and your consent where the law requires it).
Where they're kept
On Supabase, in a European Union data centre (Ireland, eu-west-1). We never see passwords: the authentication system keeps them encrypted. Videos, photos, sounds and profile pictures open only in the app, after you log in: someone who only has the link can't open them.
Our providers
To make Zap Live work we use a few providers, who process data on our behalf and only as far as needed:
- Supabase, for the database, account login and files, in a data centre in Ireland;
- Amazon Web Services, for the automatic check of posts, for connecting calls and for sending account emails (address confirmation and the code to reset your password), in the Frankfurt region, in Germany;
- Apple and Google, to deliver notifications on iPhone and Android;
- Cloudflare, for the video, audio and comments room of lives, for the Zap Live website and to forward the emails you send us, which reach a Google Gmail inbox;
- Stripe, for payments to creators who withdraw their diamonds: the «Payments to creators» section explains this.
Google also provides the ads, but as an independent data controller: the «Advertising» section explains this.
Some of these providers are US companies, or belong to US groups, and some data, such as notifications and lives, may pass outside the European Union. When that happens, the transfer takes place with the safeguards provided for by the GDPR: the European Commission's adequacy decision for companies that participate in the EU-US Data Privacy Framework, or the standard contractual clauses approved by the Commission.
For age verification, when we ask for it, we also use Yoti: the «Age verification» section explains this.
Cloudflare also delivers BlindMatch messages, without storing them: the «BlindMatch» section explains this.
Logins and technical logs
For each phone you've logged in on, Supabase's login system keeps a session with the IP address and the app's technical data: it stays until you log out of the account on that phone, and it's deleted with the account. Every request the app sends to our servers also leaves a technical log with the IP address it comes from: it's used to make the service work, to find faults and to protect the service from abuse, and Supabase deletes it automatically after 7 days at most. Visits to the website also go through Cloudflare, which processes the IP address to serve the pages and protect them: we receive nothing from those logs, and the website doesn't use cookies or analytics.
Your account's country
Some features aren't available in every country, because a law requires it or because we open them up one country at a time: for example lives, gifts, coins, calls or advertising. To know which ones to show you, we keep a country for your account. We work it out from the connection, like the sign-up country and the country of posts, and it changes only after a few days in which everything points to a new country: a short trip or a VPN won't change it. For features that a country's law prohibits for anyone located there, such as calls in some countries, we also keep the country of your last connection, and we delete it after 24 hours.
To work out the country more accurately, the app can also read on your phone the country of the SIM and of the mobile network (on Android), the country of your App Store account (on iPhone) and the region set on the phone. Of these values we store only the resulting country, and which of them agreed: never the values themselves. We don't read your phone number, your carrier or your location. In the European Economic Area, the United Kingdom and Switzerland the app doesn't read this phone information at all: there, only the connection counts.
The country isn't shown on your profile and we don't give it to anyone. Moderators can see it and correct it, for example if you move and the app doesn't notice.
For how long
As long as you keep the account. When you delete it, profile, date of birth, videos, files, comments, messages and interactions are removed straight away. The record of moderation decisions about you remains for 24 months, to protect the platform and its users and to respond to the authorities («Moderation and reports» section). A copy of your comments that someone has reported also remains, until 90 days after the decision. If an account is involved in a serious crime, such as child exploitation, or an authority orders us to, we can block its deletion and keep a copy of its data and files, which nobody looks at, to hand over to the authorities. We keep it only as long as needed, and review it at least every year.
Direct messages don't stay forever: they disappear once everyone has seen them and left the chat, or 24 hours after viewing if the chat is set that way, and in any case within 30 days of being sent (within 24 hours for text messages and posts in groups). Only what someone saves in the chat stays, until they remove it from the saved items.
The viewing data the app sends us is deleted after 90 days, even if you delete your account in the meantime; how much you watched each video, which For You uses to choose, is deleted one year after the last time you watched it, or straight away if you delete your account. The frames from the automatic check are deleted as soon as the check is finished, and messages attached to a report 90 days after the decision.
Posts you delete stay for 30 days in «Recently deleted»: they aren't shown to other users, and from there you can recover them or delete them right away. After 30 days we delete them, along with their files, unless there's a report to decide or an obligation to keep them.
For BlindMatch, we keep each chat's data for 30 days after it ends or, if someone reported it, with the report and for as long as the report is kept; the gender you indicated and the blurred photos until you leave BlindMatch or delete your account; the messages, never.
We don't keep the approximate location from «Near me»: it stays only in the memory of the server that does the matching, while you're searching.
With «Clear history» and «Remove from history» the videos disappear from the «Watch history» page, but we don't delete the fact that you watched them: For You uses it so it doesn't show you videos you've already seen again, and the view count uses it so it doesn't count you twice. This information stays as long as both your account and the video exist, and is deleted straight away if you delete your account.
To protect the app from bots and abuse, we count how often you post, comment, send messages, start new chats and make reports: for each action we keep only the time, linked to your account, without the content or the recipient, for at most 48 hours. Then we delete it, and immediately if you delete your account.
We don't record lives: we keep nothing of the video and audio. Comments on lives are deleted 30 days after being written; if there is a report still open on a comment, or on its live, the comment stays until a decision has been made on the report. The title, times, choices and figures of each live stay for as long as the account of the person who broadcast it exists («Live» section).
A follow request stays until the person receiving it accepts or declines it, until the person who sent it withdraws it, until one of the two blocks the other, or until the account receiving it becomes public again. The notification of the request also stays afterwards, just one for each pair of people, for as long as both accounts exist: it is used to avoid notifying the same person more than once a day and to count requests, at most 200 new requests a day.
The coin record — purchases made in the stores, with the transaction ID, movements of coins and diamonds, and withdrawal requests — remains even after deletion, for six years from the end of the year in which the movement took place, for accounting and tax obligations and so that the same purchase cannot be credited twice; then it is deleted. It stays detached from your account, without username or email and without tip messages: only Apple, Google or, for a withdrawal, Stripe can link the transaction ID back to you.
Withdrawal requests and payments to creators: 6 years from the end of the year, even after the account is deleted.
Your account's country is kept for as long as you keep the account and is deleted along with it; the country of your last connection is deleted after 24 hours.
Advertising
Zap Live is free and shows ads. In Home, between posts, full-screen ads labelled «Sponsored» appear. Google provides them, through the AdMob service, and the app receives them directly from Google's servers. We don't store anything about the ads you see, and from Google we only receive overall figures, such as how many ads were shown. We also use viewing data, added together and without names, to estimate how much advertising earns and to decide how many ads to show.
To show the ads, measure their results and fight fraud, Google collects from the app: the IP address, from which it can estimate the area you're in, not your precise location; technical information about the phone and the app, such as performance and errors; when you open the app, the ads you see and what you do with them, for example whether you tap them or watch their video; an identifier linked to the app and, in the cases described below, the phone's advertising identifier. To do this it may also store data on the phone and read it back, as cookies do on websites. Google processes this data as an independent data controller, under its own rules, including outside the European Union with the safeguards provided for by the GDPR. We don't give Google your date of birth, nor your username, your email or your content.
If you've told us your date of birth and you're at least 18, ads may be personalised, that is, also chosen based on what Google knows about your interests. Where the law requires consent, as in the European Union, the United Kingdom and Switzerland, Google asks you for it the first time with a form of its own: if you don't give it, you still see ads, but not personalised ones. You can change or withdraw your consent whenever you like from Settings → Ad preferences, and it applies from then on. On iPhone there is also Apple's request about tracking: unless you say yes, Google doesn't receive the iPhone's advertising identifier, and you can change your mind in the iPhone's settings, under Privacy & Security → Tracking. On Android, the advertising identifier can be deleted or reset in the phone's settings.
If you're under 18, or you haven't told us your date of birth, you see only non-personalised ads, without the phone's advertising identifier and without third-party measurement, chosen from those suitable for minors. We don't ask you for consent, and all we tell Google is to treat your ad requests as those of a minor.
The icon in the corner of every ad opens the Google page that says who paid for it and why you're seeing it, and from there you can also report it. How Google processes data: https://business.safety.google/privacy/. How it uses data from the apps that show its ads: https://policies.google.com/technologies/partner-sites.
End-to-end encryption
Direct messages and calls on Zap Live are protected by end-to-end encryption. Content is encrypted on your device before it leaves, and only the devices of the people taking part in the conversation can decrypt it: the keys to do so stay on those devices. Neither Zap Live nor the providers hosting our servers can read your messages or listen to your calls.
Protected:
- the text of messages, emoji included;
- photos and videos in Snaps;
- posts you share in a chat;
- the audio and video of calls and video calls.
We use public, well-reviewed standards: HPKE (RFC 9180) with X25519 to deliver the message key to each device, ChaCha20-Poly1305 to encrypt the content and Ed25519 to sign it. The signature lets the receiving device discard a message that has been tampered with or doesn't come from the sender. In calls, the two devices recognise each other with the same keys as soon as the connection opens, and on every reconnection they check it is still the same one: if the check fails, the call ends.
Keys and devices
Every device you sign in on creates its own keys. Private keys stay on the device and never move to another phone, not even when a backup is restored; we only store public keys, so that others can write to you. You can use Zap Live on up to five active devices: beyond that, the one unused for the longest stops receiving messages, as does a device where the app hasn't been opened for 60 days.
A new device has new keys and can't read messages that arrived before; in the same way, someone who joins a group only sees messages sent after they joined. When you log out, the device deletes its keys and stops receiving messages; its public key stays on record, marked as withdrawn, to verify messages already sent, and is deleted together with the account.
The public keys of other devices are provided by our servers. The app remembers the ones it has already received and doesn't accept them changing, and in every one-to-one chat it shows a security code, as numbers and as a QR code, to compare with the one on the other person's phone: if they match, no one has got in between. The code changes when either of you changes phone, adds one or logs out of one, and the app points it out in the chat. The phones work it out, and only yours knows whether you've verified it.
What we see of messages
To make the chat work, we process some information that isn't encrypted: who writes to whom and when, the type of message (text, Snap or post), whether it has been read, opened, replayed, saved or captured with a screenshot, and when it expires; for Snaps, also the format, the size and for how many seconds they can be viewed. Group names and members, chat settings and the notices written by the app, such as “Missed call” or who joined a group, aren't encrypted either. When you share a post in a chat, its share count goes up, and the device of the person receiving it asks us for the post's card in order to show it, as with any post being watched.
Message notifications don't contain the text: they only say who wrote to you and, in groups, which group, and they go through Apple's and Google's notification services. Since we can't read messages, we don't monitor them. You can always block or report a person; when you report a chat you can choose to attach the last 5 text messages, which your phone decrypts and sends to us. This is the only way messages reach us in readable form, and it's the person reporting who decides («Moderation and reports» section).
Messages sent before 26 September 2026 weren't encrypted; none of them is still stored on our servers.
In every chat we also keep when each person wrote their first message, and we keep it even after the messages have disappeared, for as long as the chat and your account exist: it is needed so that, if a private account has already written to you in a one-to-one chat, you can reply to it even without following it.
Calls and video calls
We don't record calls or listen to them. Audio and video travel from one phone to the other, encrypted; when the two networks can't connect directly, they pass, still encrypted, through an Amazon Web Services server in Frankfurt. To find each other, the two phones exchange their IP addresses through the same service: whoever is on a call with you receives yours.
For each call we store who called whom, when, whether it was a video call, how it ended and how long it lasted. We use this to make the phone ring, to show whether the other person is already on another call and to stop anyone calling too many times in a row, and it's deleted 30 days after the call. The call's line in the chat, such as “Missed call”, stays and follows the same rules as other messages.
Live
We don't record lives. The broadcaster's video and audio reach viewers in real time, through Cloudflare Realtime, a Cloudflare service, and we keep no copy of them, neither we nor Cloudflare on our behalf: a live that has ended can't be watched again. Viewers, however, can always record their phone's screen. Lives are public, and for this reason they aren't end-to-end encrypted like messages and calls: the connection between the phone and Cloudflare is encrypted, but Cloudflare receives the video in order to deliver it to viewers.
If you go live, in addition to the video and audio we process the title you write, the choices you make before starting, when the live starts and ends and how it ends, and its figures: how many people are watching it, the peak reached, how many hearts and how many comments it receives. If your account is public, your live can be seen by anyone with a Zap Live account, even people who don't follow you; if it is private, only by people who follow you. If you choose «Adults only», among them only those we know to be at least 18 can see it. Zap Live's moderators can always see it. For those who can see it, it appears in the LIVE tab and on your profile, and for people who follow you also in the «Live» row of Following; your followers also receive a notification, at most one every 30 minutes. People you have blocked, or who have blocked you, can't see it; people whose account is suspended, and people you have removed from the live, can't enter it.
If you watch a live, its room knows you are there: it counts you among the viewers, a number that everyone can see. As an adult, when you enter, the room may show your username for a few seconds to the people already there, and you can comment: your comments are seen by people in the room, with your username and your photo, and people who enter later see the latest comments already written. Under 18, you can only watch lives: no comments, and your name doesn't appear when you enter or in the host's list. Hearts can be sent at any age, and they are counted all together, without keeping a record of who sent them. The lives you watch aren't included in the data For You uses to choose videos, and you don't need the microphone or the camera to watch: the app doesn't ask for them.
If a comment of yours contains a word the broadcaster has filtered, or a variant of it, only you can see it. The same happens if it is stopped by the automatic filter, on by default, which the broadcaster can turn off: it stops links, the same text sent again within a minute and offensive words from a default list. If the broadcaster mutes you, the comments you had already written in that live disappear from everyone's chat, including yours, and people who enter later don't see them either. You don't see the comments or the joining of people you have blocked, not even in another person's live; people you have blocked, on the other hand, can still see yours, because the room is public.
To deliver the video, the phone connects to Cloudflare's servers, which receive its IP address and the technical data of the connection, such as the audio and video formats the phone can use. If the network doesn't let the connection through, the video goes, still encrypted, through a Cloudflare server that acts as a relay. Unlike calls, the broadcaster and the viewers don't exchange IP addresses: each connects only to Cloudflare. To let you into the room, Cloudflare also receives your username, your profile photo and whether you can comment.
Cloudflare processes this data on our behalf, like the other providers in the «Our providers» section. While the live is in progress, the room keeps on Cloudflare who is there, the comments, the hearts, the removals, the mutes and the words filtered by the broadcaster: we ask Cloudflare to keep the room in a data centre in Western Europe, and the room deletes everything after the live ends, usually within a few minutes and at the latest within a few hours, even if the live ends because the broadcaster's phone switches off. The video, on the other hand, goes through Cloudflare's network, which has servers all over the world, and to reach viewers in another country it may leave the European Union, with the safeguards explained in «Our providers». Cloudflare also keeps a technical log of connections to the room, which is used to find faults and is deleted after 7 days at most. We save the title, times, choices, figures, comments and removals in our database on Supabase, in Ireland.
We keep comments for 30 days from when they were written, even after the live has ended: they are the only trace of what happened, and they are used to examine reports. Once the live has ended, only Zap Live's moderators read them. They are deleted sooner if whoever wrote them, or whoever broadcast the live, deletes their account, or if moderators remove them. A comment that has been reported, or a comment on a live that has been reported, stays until a decision has been made on the report, even beyond 30 days. If the broadcaster mutes you, for the comments you had already written in that live we keep a marker that they have been removed: no one sees them any more, except Zap Live's moderators, and they are kept and deleted like the others. The title, times, choices and figures of a live stay for as long as the account of the person who broadcast it exists. If the broadcaster removes you, we keep which live, who removed you and when, so that you can't rejoin: it stays for as long as that live exists, or until you delete your account. The mute itself, that is who is muted and until when, and the comments turned off are held only in the room, and go away with it. Once the live is over, our database doesn't keep the list of who watched it, only how many people there were.
Lives don't go through the automatic check of posts: we don't send the video to any system that analyses it. Viewers can report the live or one of its comments, and Zap Live's moderators can watch it, even if the broadcaster's account is private, close it for everyone and remove comments. If the report arrives after the live has ended, the video no longer exists: the moderators decide on the basis of what remains, that is, the report, the comments, the other reports and the history of the account, and if necessary take action on the account of the person who was broadcasting, for example by suspending it. For the rest, the rules in «Moderation and reports» apply.
The legal basis is the contract, that is, the service you have chosen to use, for broadcasting, watching and commenting; for the comments we keep after the live ends and for the moderation of lives, the legal obligation and the legitimate interest in keeping the platform and the people who use it safe.
BlindMatch
If you use BlindMatch, we process:
- the gender you indicate (man, woman or «prefer not to say»), whether you want to show your blurred photo as a clue, and when you gave us your consent;
- if you choose to show it, two tiny copies of your profile photo, 16 and 32 pixels on each side, which your phone makes from the photo and sends to us: only the person chatting with you sees them, enlarged and blurred, after 10 and after 20 messages each. They are too small to show any detail, but someone who already knows your profile photo, or compares them with profile photos, might recognise you;
- for each chat, who met whom, when it started and ended, how it ended and whether you revealed yourselves.
We don't store who you want to meet (men, women or everyone): we use it only while you're searching, in the memory of the server that does the matching, and only your phone remembers your last choice. While you search we also use the app language and your age in years, to suggest first people who speak your language and are close to your age.
If you choose «Near me», when you search your phone reads your approximate location, with the permission the system asks you for the first time, rounds it to about 5 km and sends it to us with the radius you chose. We use it only to match you with people who made the same choice and are within the radius: it stays in the memory of the server that does the matching while you're searching, and we don't write it anywhere, neither in the database nor in logs. We don't show the other person your location or the distance: they only know you're within the chosen radius. If you choose «Anywhere», we don't ask for your location.
For your location, the legal basis is your consent (Article 6(1)(a) of the GDPR and, because we read it from your phone, Article 5(3) of Directive 2002/58/EC; in Italy, Article 122 of the Privacy Code). You give it by granting the permission after our explanation, and you can withdraw it at any time by choosing «Anywhere» or by removing the permission in your phone's settings.
BlindMatch messages aren't end-to-end encrypted like the ones in the chat. They go through a Cloudflare server, normally in Europe, which delivers them to the other person, counts them to unlock the clues, and doesn't deliver the words our filter always blocks or, before you've revealed yourselves, phone numbers, email addresses, links and usernames on other social networks. The server keeps each message in its memory only to deliver it and doesn't write it anywhere: we don't store it, we don't read it and we can't retrieve it. On your phone too, the chat stays only in memory and disappears when you close it. When you report, your phone sends us the last 5 messages, yours and the other person's: they are the only BlindMatch messages that reach us, and we handle them like other attachments to reports («Moderation and reports» section).
On Android we prevent screenshots and screen recordings in BlindMatch. On iPhone they can't be prevented: the phone tells us there has been a screenshot or a recording, the chat closes for both of you and the other person is told. No app can prevent a photo of the screen taken with another phone.
The legal basis is the contract, that is, the service you have chosen to use. The gender you indicate and your choice of who you want to meet can, together, reveal your sexual orientation: for this reason we process them only with your explicit consent (Article 9(2)(a) of the GDPR), which we ask for the first time and which also covers the blurred photos. You can remove the photos whenever you like from the BlindMatch settings, and withdraw your consent with «Leave BlindMatch and delete my data», which immediately deletes the gender you indicated, your choices and the blurred photos; without consent, BlindMatch can't be used.
We keep the data of each chat for 30 days after it ends, so that we can follow up on a report and stop anyone abusing the service (legitimate interest in keeping the platform and the people who use it safe); if someone reported it, the data stays with the report and follows its retention periods. For as long as your account exists, we also keep the pairs of people who ended a chat with a report, who don't meet again, or with «Drop», who only meet again if there's no one else, and exclusions from BlindMatch. Nothing from BlindMatch is used for advertising, for the For You feed or for analytics.
Payments to creators
If you want to withdraw your diamonds, you connect a payout account to Stripe, the provider that makes the payments. You enter the data needed to verify you and pay you — name, date of birth, address, identity document if Stripe asks for one, bank account and tax details — on Stripe's page, and Stripe processes it as an independent data controller, under its privacy policy and the legal obligations it has as a payment institution. We don't store it.
We keep your Stripe account ID, the country, the verification status (for example whether the account can receive payments) and your withdrawal requests: diamonds, amounts, dates, status, the reason for any refusal and the Stripe payment ID. Stripe also tells us when the account changes status.
We process this data to pay you what you request (contract), to keep the accounting and tax records the law requires of us (legal obligation) and to prevent fraud (our legitimate interest and that of people who buy coins). Before every payment, a person reviews the request using a few signals: how long you've had your account and your payout account, how many people have given you the diamonds, how large a share comes from the most generous one and whether their accounts are new. It isn't an automated decision: a person always decides, and you can appeal it.
We keep withdrawal requests and payments for 6 years from the end of the year in which they took place, as Irish accounting and tax rules require, even if you delete your account: in that case they stay detached from your username. The link to your Stripe account is deleted along with your account; the data Stripe keeps is subject to its own rules.
Moderation and reports
For the automatic check of posts, Amazon Rekognition, an Amazon Web Services service, in the Frankfurt region, receives from us the post's thumbnail and, for videos, up to four frames that your phone extracts before posting. The frames are deleted as soon as the check is finished; the result remains, that is, whether the post passed, was blocked or is waiting for a person, and why. If the check blocks one of your posts, appealing the decision gets it reviewed by a person.
When you report something we keep who reported, what was reported, the reason, the note you write and the outcome, which we send to your Inbox. Someone reported from the app doesn't know who reported them. If you report a chat and choose to attach the last 5 messages, your phone decrypts them and sends them to us: only the text, five at most, with who wrote them and when. Only Zap Live's moderators read them, and they're deleted 90 days after the decision. For reports that arrive by email, we keep what you write to us and your contact details, to handle them and reply to you.
We keep a record of moderation decisions: what was decided, on which content or account, when and for what reason. We use it to show you the decisions and answer your appeals in Settings → Account status, to count violations and to respond to the authorities. Appeals are deleted with the account; the record remains even after that, for 24 months from the decision, then it is deleted.
When you report a comment or a post, along with the report we keep a copy of what you reported, taken at that moment: the text of the comment or the caption of the post, who wrote it and when. If the comment is then deleted, by the person who wrote it or together with their account, the copy stays with the report: it's what moderators use to decide, and what lets the person who reported receive the outcome. Only Zap Live's moderators see it. A report stays open until the moderators decide; 90 days after the decision, we keep only the content's ID from the copy. When a post is deleted, on the other hand, its reports and the copy are deleted with it.
When the law requires it, we give data to the authorities, and only the data they request. We report child sexual abuse material to the Italian Polizia Postale and to NCMEC, the US National Center for Missing & Exploited Children, with the data needed to find whoever posted it.
Copyright reports
When we receive a copyright infringement report we process the reporter's data (name, contact details, the work claimed and the title on which they hold it), the identifier of the reported content and the outcome of the check. We tell whoever published the content the reason for its removal; if they reply, we pass the reply and their contact details on to the reporter, because a dispute over rights is settled between the two parties.
Established infringements stay recorded on the account so that the rule on repeated infringement can be applied: they are kept for 24 months from each infringement. The legal basis is legal obligation and the legitimate interest in defending the platform and rightsholders.
Support requests
If you open a ticket from Settings → Report a problem, we keep the category you choose, what you write and our replies, together with a few details that help us understand the problem: the system and its version, the app version, the phone model and the app language. The ticket is linked to your account, isn't end-to-end encrypted and is read only by the people who answer for Zap Live. A closed ticket is deleted after 12 months; if you delete your account, your tickets are deleted straight away.
Your rights
You can request access, rectification, erasure, restriction and portability of your data, and object to processing. You can carry out erasure yourself, right away, from Settings → Delete account. You can download a copy of your data from Settings → Support and info → Download your data: for each copy we keep only the date, as long as the account exists. For anything else write to info@zaplive.app. You may also lodge a complaint with the Irish Data Protection Commission, the lead supervisory authority for Zap Live, or with the data protection authority of the EU country where you live.
Minors
Zap Live is not for anyone under 14, or under the higher age required by the law of their country, as the terms of use say: when you sign up we ask for your date of birth, and if you are under the minimum age the account is not created. If we find out an account belongs to someone under the minimum age, we close it. More protective rules apply to anyone under 18, explained in the terms of use under «If you're under 18»: to apply them we use the date of birth and, to avoid sending notifications at night, the phone's time zone. Anyone under 18 sees only non-personalised ads, as the «Advertising» section explains. Your date of birth can't be changed in the app: if you got it wrong, ask support to correct it, from Settings → Report a problem or by writing to info@zaplive.app.
If your phone and the store allow it, when you sign up and then at most once a day, we ask Apple or Google for the age range of your store account and, if you are a minor, whether a parent has approved Zap Live. We keep only the age range, how the store determined it, any approval and the date of the request: we use them only to apply the age rules, never for advertising or analytics, and they are deleted with the account. If the store doesn't respond, or you choose not to share it, only the date of birth applies.
Anyone under 18 can't go live. They can only watch lives: no comments, and their name doesn't appear when they enter or in the host's list. Hearts can be sent at any age, as the «Live» section explains.
BlindMatch is closed to anyone under 18: to get in you need to pass age verification with Yoti, and anyone under 18 doesn't even see it («BlindMatch» section).
Family Pairing
If an account is linked through Family Pairing, we process who is linked to whom and since when, the controls chosen by the parent or guardian, and the code used for linking, which is valid for 10 minutes. The parent or guardian sees the teen's username and profile picture and the controls they have set, but not the teen's messages, what they watch, what they search for, who they talk to or how much time they spend on Zap Live, which is counted on the phone. The teen sees the username and photo of the parent or guardian. The parent gets a notification when the link is created, the teen when the controls change, and each of them when the other removes the link.
The legal basis is the service you have chosen to use together, and the legitimate interest in protecting minors. The link and the controls remain until one of the two removes the link, and they are deleted with the account.
Age verification
If we ask you to confirm your age, the check is carried out on our behalf by Yoti Ltd, based in London, in the United Kingdom. With a selfie, Yoti estimates your age from your face and deletes the image as soon as the estimate is made: the estimate isn't used to recognise who you are, and nobody looks at it. With an ID document, Yoti reads its details and uses a selfie to check that the document is yours, then deletes the images and data as soon as it has worked out your age. With a credit card, you enter the card details on Stripe, Yoti's payment provider, and Yoti doesn't keep them. Only the result reaches Zap Live, that is, whether you meet the required age: no photos, no documents and no card details.
We keep the result, the attempts, the dates and the Yoti session ID for as long as the account exists; Yoti keeps only the result for us, for 6 months. Yoti carries out the checks in its own data centres in the United Kingdom or in Amazon Web Services regions in the United Kingdom, the European Union or the United States: when data leaves the European Union, it does so with the safeguards provided for by the GDPR. The legal basis is the same as for the date of birth: legal obligation and the legitimate interest in protecting minors.
Before your first live we may ask you to confirm in the same way that you are at least 18, when that is the only thing still missing for you to broadcast: you start the verification yourself, from «Confirm your age» in the live set-up screen, and if you have already confirmed that you are 18 you don't do it again. We process the same data, plus the fact that you requested it for the live. If you don't pass, the app keeps working, but we use the result to apply to you the rules for people aged 16 or 17, which the terms of use explain in «If you're under 18»: among other things, you can't go live or use coins, tips and subscriptions; messages and calls are only with friends; ads are only non-personalised ones; and your settings switch to those of someone aged 16 or 17, which you can then change. These rules apply until you pass a new verification that you are at least 18, or until a person at Zap Live, after examining the case, archives the verification. The legal basis is the legitimate interest in protecting minors, who can't broadcast on Zap Live.
To enter BlindMatch we always ask you to confirm in the same way that you are at least 18: you start the verification yourself, from «Confirm your age» in BlindMatch, and if you have already confirmed that you are 18 you don't do it again. We process the same data, plus the fact that you requested it for BlindMatch, and if you don't pass it we use the result as explained in the paragraph above. The legal basis is the legitimate interest in protecting minors, who may not chat with strangers in BlindMatch, and the legal obligation to protect them.
If you live outside the European Union
We process everyone's data under the rules of this policy, wherever you live, and the data is kept in the same places. If the law of your country gives you additional rights over your data, you can exercise them by writing to info@zaplive.app.
Below is what changes in some countries. In the others, you can also contact your country's data protection authority.
Canada
You can ask us to show you your data and to correct it, and you can contact the Office of the Privacy Commissioner of Canada; in Québec, the Commission d'accès à l'information. The person in charge of the protection of personal information under Québec law is Sufyan Arif, at info@zaplive.app.
South Korea
You can ask us to show you your data, to correct or delete it, or to stop processing it, and you can contact the Personal Information Protection Commission. The person responsible for protecting personal information (Chief Privacy Officer) is Sufyan Arif, at info@zaplive.app.
Philippines
The Data Privacy Act gives you rights similar to those in this policy: you can exercise them by writing to info@zaplive.app, and you can contact the National Privacy Commission.
Japan
You can ask us to tell you what data we hold about you, to correct it or to stop using it, by writing to info@zaplive.app, and you can contact the Personal Information Protection Commission.
India
You can send a complaint about how we process your data to the Grievance Officer named in the terms of use, with the same time limits.
New Zealand
You can ask us to show you your data and to correct it by writing to info@zaplive.app, and you can contact the Privacy Commissioner.
United Kingdom
We also process your data under the UK GDPR and the Data Protection Act 2018, which give you the same rights as this policy. You can contact the Information Commissioner's Office (ICO), the UK's data protection authority.
United States
The Zap Live website doesn't use cookies or tracking tools, so your browser's «Do Not Track» signals make no difference. In the app, Google may show personalised ads to anyone who is at least 18, and to choose them it may use data collected in other apps and websites too: the «Advertising» section explains how to say no.
Thailand
Thailand's Personal Data Protection Act (PDPA) gives you rights similar to those in this policy: you can exercise them by writing to info@zaplive.app, and you can contact the Personal Data Protection Committee.