AloLee (https://meet.alolee.com) is operated by TK Digital Ltd. For any privacy request, contact tomziska@gmail.com.
| Category | What & why |
|---|---|
| Device identity | A per-install cryptographic key (a public key) generated on your device. This is a pseudonymous id - it does not contain your name, phone number, or email. You can use the app without creating an account or giving personal details. |
| Display name (optional) | A name you choose for yourself, shown to the people you call and to the people who call you, once you are connected partners, and to nobody else; stored with your account; erased with it. It is entirely optional: you can leave it empty, change it, or clear it at any time in Settings, and everything in the app works the same way without one. When you set it, the people you are already connected partners with see it at the top of a call with you and on the screen when you ring them. It is never shown to a stranger or to someone who has only typed a room code, and it is not used to identify you anywhere else. |
| Audio you speak / submit | When you use a translation feature, your audio is sent to the translation provider (Google Gemini) to be transcribed and translated, then the result is returned to you. In normal use we do not keep that audio on our servers. In a call without translation - a call in which either of you has turned translation off, whatever languages the two phones are set to, so that you simply hear each other speak - your voice is NEVER SENT TO A TRANSLATION PROVIDER at all: it travels directly between the two phones, encrypted end to end, and when the two phones cannot reach each other directly the encrypted packets pass through a relay server of ours without being decrypted. There is nothing there for the quality-recording mode described below to capture either, because that mode records the audio of each translated utterance and a call without translation has none. Quality recording is switched off in AloLee and cannot be turned on here, so the audio of a call is not saved. |
| Transcripts & translations | The text produced from your speech and its translation. Saved on your device. It is not kept on our server: the text is produced, returned to you, and not retained by us, unless you ask for a copy of the call by e-mail, which is then sent to you. A call without translation produces neither a transcript nor a translation, anywhere, because nothing is transcribed: there is no text for us or for anyone else to hold. |
| Voiceprints (biometric) | If you use the optional "who said what" feature, you record a short voice sample per person to create a voiceprint used to label who spoke. This is biometric data, collected ONLY with your explicit consent, used only for speaker labelling, and deletable at any time. |
| Voice clone (biometric) | If you opt in to "use my voice", we create a synthetic copy of YOUR voice (via ElevenLabs) from a short sample you record with explicit consent, used only to read your own translations aloud in your voice. This is biometric data, collected only with your consent, never used to impersonate you elsewhere, and deletable at any time (deleting it also removes it from ElevenLabs). |
| Connected partners | When you and another signed-in person finish a call together, we save one record so you can call each other again from your list of remembered partners without a new link. That record holds only the pair of pseudonymous account ids, when the pairing was created, and when you last connected; it holds no names. Tapping Forget on a remembered partner removes the pairing for BOTH of you at once. When that happens we keep a permanent note that this pairing was removed (the two ids and the time), so that restoring one of our backups cannot bring a removed pairing back. Delete account on your account screen removes all your pairings the same way, for both sides. |
| Cameras and voice during a call | A call always starts with both cameras OFF. A picture is added only if you tap "Turn on cameras", allow the camera when your phone asks, and the other person says yes; either of you can turn the cameras off at any moment, and the call and its translations carry on exactly as before. While the cameras are on, the picture travels DIRECTLY between the two phones and is encrypted end-to-end (DTLS-SRTP): our servers never see it, never store it, and never process it. If the two phones cannot reach each other directly, a relay server of ours passes the encrypted picture between them - it forwards packets it cannot read, keeps none of them, and runs on our own EU server, so no new outside company is involved in your picture. We do not record what your cameras show and we take no screenshots of it, so there is no picture of you for us to keep or to delete. To use the relay your phone is given a short-lived ticket (valid about an hour) tied to the pseudonymous account id described above and to that one call, so the ticket for one conversation is not a key to another, and the relay keeps only ordinary connection records of the kind covered by "Technical data" below. Connecting two phones directly means each one learns the other’s network address, so nothing about your connection is sent until the other person has said yes - and our server refuses to pass those messages on for an ask that nobody said yes to. THE SAME CHANNEL CARRIES YOUR VOICE in a call without translation: when either of you turns translation off, you hear each other speak, whatever languages your phones are set to, instead of hearing a translation read aloud, and that voice travels directly between the two phones, encrypted end to end, exactly as the picture does. It is never sent to a translation provider. When the two phones cannot reach each other directly the encrypted packets of the picture and the voice pass through the same relay server of ours, which forwards packets it cannot read, keeps none of them, and runs on our own EU server. We do not record your voice in such a call and there is no transcript of it, so there is nothing there for us to keep or to delete. Answering the call is what starts the voice: there is no separate question to answer, because there is nothing extra to agree to. THE SAME CALL CAN NOW BE JOINED IN A WEB BROWSER, from an invitation link, without installing anything, and every promise above is made there too. IN A BROWSER THE CAMERA WORKS DIFFERENTLY FROM THE PHONE AND THIS IS WHAT IT DOES: the camera is on from the start of the call and it is YOUR OWN SWITCH - you turn it off and back on whenever you like, nobody has to agree first, and the other person’s camera is theirs in the same way, so neither of you is ever waiting for the other to say yes. Your browser asks one question for the camera and the microphone, once, as the call starts, and it is the browser’s own question: nothing at all is captured until you allow it there. If you allow the microphone but refuse the camera, the call carries on with voice only and everything else works exactly as before; if you refuse both, nothing is captured at all. While the cameras are on, the picture travels DIRECTLY between the two browsers and is encrypted end-to-end (DTLS-SRTP): our servers never see it, never store it and never process it, and when the two browsers cannot reach each other directly the SAME relay server of ours passes the encrypted picture between them, forwarding packets it cannot read, keeping none of them, on our own EU server, with no new outside company involved. We do not record what your camera shows and we take no screenshots of it, so there is no picture of you for us to keep or to delete. Nothing about your connection - including your network address - is sent to the other person until you are both INSIDE the same meeting: the person who started it has to have sent you its link, and when they have asked to be asked about visitors they have to let you in as well; our server refuses to pass those messages on to anyone who is not in that meeting. What needs nobody’s yes is the CAMERA, which is your own switch as described above. What you SAY in a browser is handled exactly as "Audio you speak / submit" above describes it whenever you are speaking to be translated. AND THE CALL WITHOUT TRANSLATION IS NOW A BROWSER FEATURE TOO, not a phone one: when either of you turns translation off you hear each other’s direct voice in a web browser exactly as you would on a phone, over that same peer-to-peer channel, encrypted end to end, passing unread through our own relay when the two browsers cannot reach each other directly, and it is never sent to a translation provider. We do not record that voice and there is no transcript of it, so there is nothing there for us to keep or to delete. |
| Typed messages during a call | Inside a call you can type a message to the other person instead of speaking. What you type is sent to our server, translated into the language the other person is reading by Google Gemini (the same processor named below for speech), and passed to the people in that call and to nobody else; each of you sees your own line as you wrote it and the other person’s line in your own language. A message may be at most 2000 characters and a longer one is refused rather than cut. WE DO NOT STORE THESE MESSAGES: they are relayed as they are typed, no copy of the text is written to our database, our own log of the call records only how many characters a line had and which language it went to, and when the call ends nothing of the conversation remains on our side. What you can still see on your own screen is held by your browser alone and is gone when the call is closed. |
| Usage & cost metering | Timestamps, a connection id, your pseudonymous account id (derived from your Google account id when you are signed in) and translation/token counts, used to run the service, measure load, and meter usage. These billing rows are kept for up to 400 days and are not erased by Delete account. |
| Technical data | IP address and basic device/app info, used for delivering the service, security, and load balancing. We do NOT use advertising identifiers and we do NOT run advertising or attribution SDKs. |
You do not need to provide your name, email, or phone number to use the core translation features.
We share only the data necessary, over encrypted connections, with these processors. We instruct them to process it only to provide the service and not to train their own models on your content. We do NOT sell your data.
| Processor | Purpose | Data |
|---|---|---|
| Google (Gemini API) | Speech-to-text and translation during a call. The audio you speak to be translated, the text you type, and the chat messages you send in a call are sent to Google’s Gemini API over an encrypted connection, translated, and the result returned. | Audio you speak to be translated, text you type, chat messages |
| ElevenLabs | The server voice: when a translation is read aloud by the server voice, the text to be read aloud is sent to ElevenLabs and the spoken audio comes back. In the listening mode for Vietnamese, when its second check is on, the spoken clip is also sent to ElevenLabs for a second transcription. Voice cloning (a copy of your own voice made from a sample you record with consent) is used only if it is enabled. | Text to be read aloud; for the listening check, the spoken clip; your voice sample only if voice cloning is enabled |
| Our e-mail provider | Sends the copy of a call that you ask to have e-mailed to you. | Your e-mail address and the call copy you asked for |
| Google sign-in | Optional sign-in with your Google account. We keep the e-mail address and the name Google gives us, with the Google account id, linked to your account until you delete it. | E-mail address, name and Google account id |
| DigitalOcean | Hosting of our server in Frankfurt, Germany (EU). The relay used when two browsers in a call cannot connect directly runs on this same server of ours; it passes on a picture and voice that are already encrypted end-to-end and cannot read or keep either. | All data processed by the service, at rest in the EU. For the camera picture and direct voice, only encrypted packets passing through, never decrypted and never stored |
| Sentry (error monitoring) | Error reports, when enabled. They carry technical error details and never the content of a call. | Technical error data |
| Slack | Operational alerts to the operator, including error reports. Never the content of a call. | Operational and error data |
Two optional features use biometric voiceprints, each collected only after you give explicit, specific consent, stored in the European Union (Frankfurt, Germany), and deletable at any time in the app or by contacting us:
Speaker labelling ("who said what") creates a voiceprint from a short recording to label who is speaking. It is used only for speaker labelling.
Voice clone ("use my voice") is OFF by default. If you opt in, you record a short sample of YOUR OWN voice - after passing a liveness check that has you read a randomised phrase, so a covert or pre-existing recording cannot be used - and we create a synthetic copy of your voice via ElevenLabs, used ONLY to read your own translations aloud in your voice. Listeners are told when a voice they hear is AI-generated. You may only clone your own voice; it is never used to impersonate you elsewhere. Deleting it removes it from your phone and from ElevenLabs.
Your data is stored and processed in the European Union (Frankfurt, Germany). Some processors (e.g. Google) may process data in other regions under appropriate safeguards (such as EU Standard Contractual Clauses).
We keep data only as long as needed to provide the service and meet legal obligations. We do not record calls. A connected-partner pairing is kept until either side taps Forget or deletes their account, and the note recording that a pairing was removed is then kept permanently so a backup restore cannot undo the removal. We keep no picture from the cameras and no recording of your voice, so there is nothing there to delete.
Delete account on your account screen erases your Google sign-in (your e-mail address, name and Google account id), your display name and your connected-partner pairings (for both sides), and signs out every browser linked to the account. Three things keep the pseudonymous account id after Delete account: the billing rows described above (up to 400 days), the server's own operational logs (overwritten as they fill), and the note recording that a pairing was removed (kept permanently, for the reason above). For anything else, contact us and we will erase it. Clearing this site's data in your browser removes what the page keeps there.
Subject to applicable law (including the GDPR), you can: access a copy of your data; correct it; delete it; restrict or object to processing; withdraw consent (e.g. for voiceprints) at any time; and request portability. To exercise any right, contact tomziska@gmail.com. You also have the right to complain to your local data-protection authority.
We use encryption in transit, access controls, and EU-based storage. No system is perfectly secure, but we take reasonable measures to protect your data.
AloLee is intended for adults (18+). We do not knowingly collect data from children. If you believe a child has provided data, contact us and we will delete it.
This policy is generated from our live data-practices configuration and updated whenever those practices change; the date above reflects the latest version. Material changes will be highlighted in the app or here.