Call Translate Live Privacy Policy
Last updated: 2 November 2026 · Android package: it.stanzaamici.app
Call Translate Live (previously TalkOrbit) is provided by Spina Giovanni Emanuele. This policy explains the data used for group calls, room chat, captions and translations, including the closed-test version. Contact the developer at creo.app.app@gmail.com. Website: spinagiovanni.com.
No server recording: Call Translate Live does not record or store call audio or video on its servers. Room chat and captions are different: their text is temporarily processed to provide the conversation and optional translation. Participants may save received captions on their own devices.
1. Room profiles and connection data
Ordinary users do not create a registered account or provide an app password. To join a room you choose a display name and spoken language. A profile picture and country are optional. The app reduces a selected profile picture to a small thumbnail locally before sharing it with the room; it does not upload the original profile photograph.
The room service handles the room code and title, display names, thumbnail pictures, languages, optional countries, participant and readiness status, chat, captions, and connection-signalling messages. These are shared with participants in that room as needed. A random session token identifies the app session; it is not an advertising identifier. The service also receives network information such as your IP address and connection timings to connect devices, estimate connection quality, and limit abusive requests.
Rooms and their contents are held in the application server's memory rather than a conversation database. A room expires after six hours and closes when its creator leaves, or after the creator remains disconnected beyond the reconnection grace period (normally 60 seconds). Closing a room removes its in-memory state. The lobby keeps at most the latest 50 messages. Live captions and their translation cache are normally retained on the room server for about two minutes. Technical connection services can process operational information separately; call media is not included in application logs.
2. Microphone, camera and calls
The app asks for microphone or camera permission when you choose a function that needs it, such as getting ready for a call or opening a camera preview. Browsing the home page, changing settings and checking speech languages do not start microphone or camera capture. You can turn the microphone and camera off, leave the call, and revoke permissions in Android settings.
Call audio and video use encrypted WebRTC connections. Video travels directly between participants. If a direct connection fails, an audio-only relay can forward encrypted audio packets while the call needs it, subject to capacity limits. The relay does not record or save the audio. The service also uses STUN connection discovery (Google's public STUN service); connection infrastructure can see network addresses needed to establish or relay a connection. Participants in a direct call may learn one another's network address through the connection.
Other participants receive the audio and video you enable and may independently record, copy or take screenshots using their own devices. Call Translate Live cannot prevent this. Do not share a room code or sensitive information with people you do not trust.
3. Captions, language models and translation
Optional speech recognition runs on your device where a supported local speech recognizer and the required language model are available. Call Translate Live does not fall back to cloud speech recognition. When you enable captions, the resulting text is shared with the room. Your audio is not sent to the text-translation provider.
Speech recognition uses the compatible local service on your device. Updated Android builds can use an integrated Vosk recognizer when the system service is unavailable. Speech models are downloaded only when you request them and are kept locally. System-service models come from the device service provider; integrated Vosk models are downloaded from Alphacephei over HTTPS. These providers receive ordinary download request information, such as an IP address. No call audio is uploaded for recognition. Each participant prepares their own spoken language.
Updated Android builds: chat and caption text is translated on the device with Google ML Kit after you explicitly prepare the necessary translation-language models. Speech and translation models are separate downloads. The text and its translated output are not sent to Google or to our server for translation inference, and there is no automatic fallback to an online translation service. Original chat and captions are still shared temporarily with room participants through the room service as described above.
ML Kit can contact Google for language-model downloads, updates, compatibility information and operational metrics. Google documents collection of device and app information, API performance and usage diagnostics, including installation identifiers where applicable. This is distinct from uploading your conversation for translation. See ML Kit Terms and Privacy, ML Kit Android data disclosures and Google Privacy Policy.
Compatible updated iOS builds: text translation uses Apple's on-device translation models, prepared through the device's download controls where supported. Availability depends on the iOS version and installed language models. Model preparation can contact Apple's services under Apple's privacy practices.
Older app builds and the web version: optional text translation may use MyMemory, provided by Translated, through the room service over HTTPS. In that path, the submitted text, source and target languages and request information are processed by the provider under its own practices. See MyMemory and Translated's privacy policy. Retention by a translation provider is separate from the room service's temporary retention. No audio is sent to MyMemory.
4. Virtual backgrounds and local information
Virtual-background effects use a segmentation model included with the app and run on the device. The effect does not upload camera frames to an image-recognition service. A personal background is resized and saved locally; its original file is not uploaded to the room service. Other participants receive the resulting call video. Segmentation can make mistakes, so check the preview before enabling video.
Profile preferences, layouts, private participant labels, settings and a personal background are stored locally. Private labels are not sent to the room. The app can keep the display awake while it is in the foreground; this is enabled by default and can be disabled in Settings. Optional sound and vibration alerts are local and are not a cloud push-notification service.
5. Saved transcripts and deletion
During a call, received captions are available in the local call history. If you choose to save a transcript, the app stores a local archive containing its chosen name, participants, call duration, caption text and available translations. You can manage the saved transcript in the app or export a TXT file to your device. The transcript archive is not uploaded to the developer's servers.
Leave or close a room to stop participating. Remove a saved personal background in Settings. Clear the app's storage in Android settings to remove the local transcript archive and other app data. Exported files are separate copies: delete them using your device's file manager. Removing your local copy cannot remove copies already saved by other participants. For questions or deletion requests concerning data the developer holds, email creo.app.app@gmail.com. There is no registered Call Translate Live account to delete.
6. Advertising, consent and remote controls
The Android app includes Google AdMob (Google Mobile Ads SDK) and Google's User Messaging Platform (UMP). Advertising supports the free app. Banner and interstitial availability depends on the app version, your location and consent choices, eligibility rules and the current remote configuration. Test builds can display Google's demonstration advertisements. Test advertisements do not mean that the SDK makes no network requests.
Google's advertising SDK can collect and share an IP address (which can be used to estimate approximate location), advertising identifiers and other device or installation identifiers, interactions with the app or advertisements, and technical diagnostic/performance data. Google uses these data for advertising, measurement/analytics and fraud prevention. Advertising partners may process data according to their own privacy practices and your applicable choices. We do not provide your call audio, video, room chat, caption text, saved transcripts, profile photograph or private labels to AdMob for advertising.
Where applicable, UMP presents consent information and choices before advertising requests. You can accept, refuse or manage the options offered. Where Google requires the privacy-options entry point, it is available as Ad privacy in the app settings. Depending on the choices and applicable requirements, advertising may be personalized, non-personalized or limited, or unavailable. Refusing personalized advertising does not prevent you from using the call features. You can also manage or delete your advertising ID through Android's privacy settings.
The app requests a small remote configuration to determine whether advertising is enabled and which formats are allowed. Our server receives the requesting connection's IP address and can estimate a country using a locally hosted DB-IP database. The country filter does not use GPS, contacts, the country entered in your profile or the language of your phone. This configuration service does not build an IP-address history or receive your conversation. The remote rules cannot override an active ad-removal entitlement.
The app suppresses banner and interstitial requests while preparing call media and during calls, in landscape orientation and while the app is in the background. In Android build 18 and later, Standard mode keeps the last cryptographically signed advertising configuration in the app’s private storage. When our configuration server is unavailable, the app continues using that configuration; an explicitly disabled format remains disabled. A valid bundled demonstration configuration is used only when there is no saved configuration. Optional Protected mode additionally requires a signed session permission valid for at most 120 seconds; advertisements stop when it expires. Earlier builds can stop advertisements when their temporary configuration is unavailable. No audio or video is saved on our servers for advertising or other purposes.
Limited advertising diagnostics and selective controls (Android build 18 and later): the app creates random identifiers dedicated to this app installation and session, independently of advertising IDs, hardware identifiers, contacts or any device fingerprint. When technical monitoring or explicitly enabled controls are active, the app sends application-initiated ad-load counts, SDK success/error/no-fill and impression/show callbacks, an approximate country, configuration confirmation and last-contact time to our own service over HTTPS. We cannot directly count the SDK’s internal refresh requests. Diagnostics are retained for up to seven days with a limit of 500 recent session records. Our advertising-control service does not store an IP-address history, conversation contents, audio or video. Authorized administration can suspend only the ads of a particular installation or session, with a reason and expiration (at most 30 days), or remove that suspension; this does not block use of the app or affect purchases. An already received manual block expires locally even when offline. Monitoring does not by itself authorize automatic blocking: automatic load-threshold blocks and per-session quotas are separate, initially disabled controls. Low fill rates, countries and cities do not automatically classify a user as abusive. Devices receive new controls only when they can reconnect.
See Google Privacy Policy, How Google uses advertising information, AdMob Android data disclosures and DB-IP. These providers' retention periods and choices are separate from our room service's short-lived data.
7. Pro purchases, ad removal and advanced features
Call Translate Live Pro is a one-time, non-consumable purchase, with no subscription. Pro removes all advertisements permanently, lets the room creator host calls with up to six people, and unlocks saving, viewing and exporting text transcripts on the purchaser's device. Free rooms support up to three people; live translated captions remain available without Pro. The creator's entitlement controls room capacity, so guests do not need Pro merely to join a six-person room. Each person's saved-transcript access depends on their own entitlement. The store purchase screen confirms the applicable price, payment and product availability for your platform, build and country.
Google Play processes Android payments; RevenueCat provides purchase verification, entitlement management and restoration. We do not receive or store your full payment-card number, banking password or Google account password. The billing integration does not receive your room audio, video, captions, messages, profile photo, room display name or personal background images.
The app creates a random, pseudonymous customer identifier locally for billing. RevenueCat processes this identifier, technical context such as platform/app/OS version, locale and currency, relevant timestamps, product identifiers, purchase tokens or receipts, transaction identifiers and purchase/refund status. Purchase history is used to deliver and restore paid features, provide purchase and revenue analytics, prevent fraud, handle support and refunds, and meet applicable legal obligations. Purchase-status processing is part of the billing integration and cannot be separately disabled while using purchase verification. We disable RevenueCat's automatic advertising-identifier collection and optional SDK diagnostics; the separate advertising integration is described in section 6.
Our room service can check the creator's active Pro entitlement with RevenueCat before allowing a six-person room or increasing a room's capacity. It uses a small, bounded verification cache and does not disclose the billing identifier to room participants. This check does not upload conversations or media. Verified purchase information can also be cached locally for access to purchased benefits; creating a new room still requires a network connection.
Use Restore purchases in the app with the store account used for the original purchase when needed after reinstalling or changing devices. Restoring and transferring eligibility follow the store and RevenueCat rules. Purchase records are retained as needed to provide the lasting entitlement, support transactions and comply with applicable accounting/legal obligations; store and provider records are separate from the temporary room contents. Uninstalling the app does not automatically refund a purchase.
For purchase support or a request concerning billing data, contact creo.app.app@gmail.com with the app name and the minimum transaction information needed to locate the issue. Do not send full card numbers or passwords. Deletion requests may require confirming the relevant transaction and are subject to records that must be retained by law. See RevenueCat Privacy Policy, Google Privacy Policy and Google Play Terms.
Restricted store-review access: authorized Google Play reviewers may use dedicated developer-issued review credentials to inspect paid features without a purchase. These credentials are sent over HTTPS only to our room service for authentication; the app does not save the password. The server holds a password hash and a signing key in a private configuration, not call contents. A signed review authorization is stored in the app’s private storage for at most one hour, is checked when the app resumes and periodically while foregrounded, and is removed by signing out of review. This technical access can be revoked and does not create a payment, registered personal account or lasting purchase entitlement. Review credentials and authorizations are not shared with other call participants or RevenueCat.
8. Purposes, security and your choices
Data is processed to provide the room and call features you request, deliver optional captions and translations, maintain connections, provide advertising and purchase-related functionality as described above, and protect the service. Optional permissions and features are controlled by your choices. Where applicable, processing relies on providing the requested service, consent for optional functions, and legitimate interests in service security. Data may also be disclosed when required by law.
AdMob advertising/measurement processing is described in section 6 and ML Kit operational metrics in section 3. The app does not include a separate general-purpose analytics SDK or a cloud crash-reporting SDK. It does not read your contacts, request your precise location or upload your address book when you share an invite. Native sharing opens your device's sharing interface, where you choose the recipient and destination app; that app applies its own privacy rules.
Call media is encrypted in transit. Public room services must use HTTPS/WSS; local developer testing over USB uses a local development connection. No system can guarantee absolute security. Third-party connection, translation, advertising and purchase providers (including RevenueCat and Google) may process requests in countries other than yours, under their own safeguards and policies.
Depending on your location, you may have rights to request access, correction, erasure, restriction or portability of personal information, object to certain processing, withdraw consent for optional processing, or complain to your data-protection authority. Contact the developer using the email above to exercise applicable rights. The app is not directed to children under 13. If you believe a child has supplied personal information contrary to the applicable age requirements, please contact the developer.
9. Changes and contact
This policy will be updated when the app's data practices change. The date above identifies the latest revision. Material changes will be disclosed in the app or its store information as appropriate.