This Privacy Policy applies to the mobile application Tello (the application name may be displayed as "Tello" or "TelloLive" on certain screens; hereinafter "Tello", "this App", "we", "us", or "our").
This Privacy Policy is published by SALIS ATEBOR ZUBAIR (the Operator). We respect your privacy. This Policy explains what information we collect, how we use, store, and share it, and what choices you have. If you do not agree with this Policy, please do not use Tello.
When you register, log in, complete your profile, or use features such as voice and social services, we may collect information you voluntarily provide, such as your display name, avatar, bio, account-related details, and contact information where necessary to create and maintain your account and to deliver the services.
To keep the service stable, secure, and compliant, we may automatically collect, within lawful limits, information related to your device and use of the service, such as: device identifiers and model, operating system and version, network type, application version, logs and crash data, and aggregated or non-precise usage statistics. Some of this data may be collected through third-party SDKs integrated in the App (see Section 12).
Where applicable, we may use cookies, local storage, and similar technologies to collect basic usage and access data to improve experience and security. You can manage some of these through device or browser settings. Restricting them may limit certain features.
Unless a specific feature requires it and you give separate consent, we do not require precise location as a condition of general use. Some integrated libraries (for example instant messaging components) may declare location-related permissions in the merged application manifest; Tello does not use location as a core feature in its primary permission settings screen. If we ever need location for a feature, we will ask for applicable permissions and explain the purpose in the product.
To provide and maintain Tello, we may process text, images, audio, and other content you upload or post, and we may use it as permitted by law to operate the service, perform safety and compliance review, and improve the experience.
When you use sign-in with a third party (e.g. Google), we may receive from that provider the account identifier and basic profile information that you authorized. Their processing of your data is governed by their own policies.
When you contact us for support, we may process the contact and message content you provide in order to respond, resolve issues, and improve our service.
Subject to law and on a lawful, fair, and necessary basis, we may use the information for purposes including:
With your consent or where law allows, we may send you promotional or operational information via in-app messages, email, SMS, or push notifications. You can opt out of marketing or adjust notification preferences in system settings or in-app controls where available. Refusing marketing does not affect core non-marketing features, but you may miss optional updates you previously opted into.
We may share, disclose, or make information available to third parties in the following cases:
We use reasonable measures (such as contractual terms and, where appropriate, de-identification) to govern recipients. We do not control every independent use of your data by third parties outside our instructions.
In principle, we store personal information collected for services provided in a given jurisdiction within the territory required by applicable local law. If cross-border transfer becomes necessary, we will comply with applicable law (e.g. standard contractual clauses, certification, or assessment where required) and provide additional notice and, where required, obtain your separate consent, unless a legal exemption applies.
Tello offers in-app purchases and coin top-ups through Google Play Billing. Payment card and wallet data are processed by Google Play in encrypted form. We do not store your full card number, CVV, or payment passwords on our servers. Please refer to Google Play's terms and privacy documentation.
We implement reasonable organizational and technical measures designed to protect information against unauthorized access, loss, or misuse. No system is 100% secure. Please also protect your account credentials.
Tello is generally intended for users who are 18 or older. If we learn that we have collected personal information from a child without verifiable parental consent as required by law, we will delete it or take other steps as required. Parents and guardians should supervise minors' use of online services.
We retain information only for as long as needed for the purposes described in this Policy, unless a longer period is required or permitted by law, dispute resolution, or contract. When retention is no longer needed, we will delete or de-identify the data, subject to legal exceptions (e.g. legal holds, security logs).
To the extent provided by law in your jurisdiction, you may have the right to access, rectify, update, delete, restrict or object to certain processing, withdraw consent, port data, and lodge a complaint with a supervisory authority. We may need to verify your identity before acting on a request. To exercise your rights, please contact us as described in Section 11. We will respond within a reasonable time as required by law.
We may update this Policy to reflect changes in the App, the law, or our practices. If a change materially affects your rights, we will notify you by a reasonable method such as in-app notice, pop-up, or the contact method you provided. Your continued use after the effective date of an update, where allowed by law, may constitute your acceptance. If you do not agree, you should stop using the App and, where available, close your account.
For questions, complaints, suggestions, or to exercise your privacy rights, please contact us at:
We will respond within a reasonable time. You may also have the right to complain to a data protection authority in your region.
Tello integrates third-party software to provide sign-in, networking, instant messaging, real-time voice, push notifications, media display, attribution, risk control, payments, and related functions. The table below reflects SDKs present in the current Android application build (release dependencies and bundled libraries). Integrated components and versions may change between releases. Each provider's official privacy policy and documentation govern the details of their processing.
| SDK / Service | Provider | Purpose in Tello | Typical data involved |
|---|---|---|---|
| Agora RTC Voice SDK | Agora, Inc. | Real-time voice in voice rooms and related audio features | Device information, network information, audio stream data, performance logs |
| NetEase Yunxin IM / ChatKit / CoreKit | NetEase, Inc. | Instant messaging, chat UI, message delivery, session management, related push sync | Account identifiers, device and network data, messages and attachments metadata, logs |
| Firebase (Analytics, Cloud Messaging, Crashlytics) | Google LLC | Push notifications, crash reporting, aggregated usage analytics | Device identifiers, app instance IDs, crash stack traces, event parameters |
| Google Play services — Sign-In | Google LLC | Optional Google account sign-in | Account ID, basic profile fields you authorize |
| Google Play Billing | Google LLC | In-app purchases and coin top-ups | Purchase tokens, order status (payment instruments handled by Google Play) |
| Google Play Install Referrer | Google LLC | Install attribution support alongside marketing SDKs | Referrer URL / install referrer string |
| OpenInstall | OpenInstall / associated operator | Deferred deep linking, install attribution, campaign measurement | Device identifiers, install/channel parameters, deep-link payload |
| NetEase HTProtect | NetEase, Inc. | Device fingerprinting and risk / anti-fraud signals | Device identifiers, environment signals, security tokens |
| NetEase Alive (liveness) | NetEase, Inc. | Face liveness verification for account recovery and related security flows | Camera capture for liveness check, verification result codes |
| OkHttp / Retrofit | Square, Inc. (open-source) | HTTPS communication with Tello backend APIs | Request/response metadata necessary for networking (payloads are app-controlled) |
| Protocol Buffers / gRPC-JSON utilities | Google LLC (open-source) | Structured API request/response encoding with our servers | Application data you send or receive through Tello features |
| Coil | Open-source (Coil contributors) | Loading and caching images in the UI | Image URLs and cached image bytes on device |
| AndroidX Room | Google LLC (open-source) | On-device structured cache / local database where used | Locally stored app data on your device |
| AWS SDK for Android (S3 Transfer Utility) | Amazon Web Services, Inc. | Uploading user-selected images (e.g. profile photos, feedback attachments) to cloud storage | Files you choose to upload, upload metadata, credentials issued for scoped upload |
| SVGAPlayer | Open-source / YYUED | Playing SVGA animation assets in the App | Animation files downloaded or bundled by the App |
| libpag (Tencent PAG) | Tencent | Playing PAG animation effects where used in UI | Animation resources loaded by the App |
External apps (not SDKs): Tello may open third-party apps such as WhatsApp when you tap customer-support or seller contact actions. Data shared with those apps is governed by their own policies, not this Policy.
We may publish a separate "Third-Party SDK List" page with version numbers if required in your jurisdiction. When in doubt, refer to each provider's official documentation and the Google Play Data safety form for the published build.
Android combines permissions declared by Tello and by integrated libraries into a merged manifest in the published APK/AAB. Sensitive permissions are requested at runtime where required by the OS. If you refuse a permission, related features may be unavailable or degraded.
The App provides a privacy permissions screen that reflects permissions we actively ask users to manage:
POST_NOTIFICATIONS, Android 13+): Deliver push notifications for messages, system notices, and service alerts.CAMERA): Take photos for profile pictures, chat attachments, and face liveness verification flows.READ_MEDIA_IMAGES and/or READ_MEDIA_VISUAL_USER_SELECTED on Android 14+): Let you pick images from the gallery where the system requires explicit media access. Where supported, we also use the system Photo Picker so you can share only selected items.RECORD_AUDIO): Voice chat, voice rooms, and other audio capture features.INTERNET: Network access for all online features.ACCESS_NETWORK_STATE: Detect connectivity to improve networking behavior.MODIFY_AUDIO_SETTINGS: Audio routing, volume, and call/room audio behavior.VIBRATE: Haptic feedback for notifications and in-app events where enabled.READ_EXTERNAL_STORAGE (maxSdkVersion 32): Legacy storage read access on older Android versions when required for media pickers or library compatibility.com.android.vending.BILLING: Google Play in-app purchases and top-ups.The following permissions may be merged into the published application from third-party modules (especially instant messaging / RTC components). Tello may not request all of them at runtime in every release; they are listed for transparency and Google Play disclosure alignment:
ACCESS_WIFI_STATE / CHANGE_WIFI_STATE: Network quality and connectivity helpers used by communication SDKs.READ_PHONE_STATE: May be declared by communication SDKs for device/network identification; we do not use this as a standalone Tello feature permission.BLUETOOTH / BLUETOOTH_ADMIN (and BLUETOOTH_CONNECT on Android 12+ where merged): Route voice audio to Bluetooth headsets when supported by the audio stack.ACCESS_COARSE_LOCATION / ACCESS_FINE_LOCATION / ACCESS_LOCATION_EXTRA_COMMANDS: Declared by some IM/RTC libraries; Tello does not list location among its primary in-app permission toggles. If a future feature requires location, we will request it at runtime with an in-product explanation.READ_MEDIA_VIDEO / READ_MEDIA_VISUAL_USER_SELECTED: May be merged for chat media pickers on newer Android versions.WRITE_EXTERNAL_STORAGE (maxSdkVersion 32, if merged): Legacy write access for caches or attachments on older Android versions.Please align the Google Play Console "Data safety" and permissions declarations with the merged manifest of each release build. If a permission is removed from a future release, we will update this section accordingly.