Version: 2026.10.23.1 · Effective: 23 October 2026
Who is responsible
Md shahadat hossin, operating as Nafstudio, Bangladesh, is responsible for UmeCall's handling of personal information. Nafstudio is a business name, not a claim of company registration. Contact telephone: +34 632 850 864. Website: https://umecall.com. You can also use the app's Help & Support tools to send a written request. If you cannot access your account, contact us by telephone to arrange a written request and appropriate identity verification. Never provide your password or verification code to support.
This policy covers the UmeCall app and its supporting services. It does not describe another product previously developed by the operator.
Information we process and why
| Information | Purpose |
|---|---|
| Telephone number, verification state, account identifier and security credentials or proofs | Create and authenticate your account, recover access where supported, and prevent account abuse. |
| Profile name, username, photograph and other profile information you choose to provide | Display your identity to the audience allowed by your settings and support communication. |
| Messages, attachments, voice notes, Stories, Community content and associated delivery or interaction records | Store and deliver the content you choose to send or publish, apply access controls, and provide conversation and sharing features. |
| Call participants, call identifiers, timing/status and network connection information | Set up and route calls, show call history, notify participants and diagnose connection failures. Audio/video is transmitted while you use a call. |
| Device/app identifiers, app version, push-notification tokens, IP/network information and session records | Deliver notifications, keep sessions working, protect accounts and diagnose technical problems. |
| Advertising and consent information, only in a version where ads are enabled: consent status, ad views and taps, IP address, app/device identifiers, approximate location inferred from IP, and advertising diagnostics or fraud signals | Request and record required choices, deliver and limit ads, measure basic ad performance, and prevent invalid traffic. The device advertising identifier is available only where the operating system and required permission allow it. |
| Privacy settings, reports, support requests and relevant security/moderation records | Respect your choices, investigate misuse, resolve requests and meet applicable legal duties. |
We process information needed to provide requested services on the lawful basis applicable to that activity. We seek consent where required, including for optional permissions and protected information. Security, legal obligations and valid legal claims may require processing on another lawful basis. We do not treat acceptance of this policy as permission for unrelated advertising or new optional uses.
Address book and phone discovery
Contact access is optional. If you permit access and use phone discovery, the app sends normalized telephone numbers to the UmeCall server to look for eligible accounts. These are telephone numbers, not anonymous data. The discovery service uses the submitted numbers for that query and does not persist a copy of the submitted address book. Device contact labels are used on the device. A match is returned only when the other account's discovery and blocking rules allow it.
Your own verified telephone number is stored for account and discovery purposes with additional server-side protection. The “Let people with my number find me” setting controls whether people who already have your number can find an eligible profile. It does not publish your number in your public profile. Changing this setting does not erase information someone already knows.
Device permissions and sharing
Microphone and camera access support calls, voice messages and camera features. Photos/files are accessed when you select, capture or save media. Contact and notification permissions support their respective features. Optional location sharing, where available, requires your deliberate action and the applicable permission. You can change permissions in your device settings; the affected feature may then be unavailable.
Recipients and people within your selected audience can see the content you share with them. They may retain or copy it. Review your audience, profile visibility, discovery, read-receipt, blocking and other privacy settings before sharing sensitive information.
Security and encryption
Public service connections use encrypted transport. Media storage and sensitive account fields have additional protection, and administrative access is restricted. However, ordinary UmeCall cloud chats are readable by the service and are not end-to-end encrypted by default. Current calls use encrypted network transport; we do not claim participant-only end-to-end encryption. Do not rely on UmeCall for a level of confidentiality that has not been provided.
The currently configured calling service routes live audio/video without an enabled server call-recording service. This does not stop another participant from recording or capturing a call on their device. No security measure can guarantee absolute security.
Service providers and international processing
UmeCall uses hosting and network infrastructure for its API, databases and self-hosted calling service; Backblaze B2 for media and backups; Google Firebase for supported telephone verification and push delivery; Apple for iPhone push delivery; and ZENDSMS for the configured Bangladesh SMS-verification route. Providers receive the information necessary for their function. For example, verification providers process a number and delivery/security information, storage providers hold stored content, and push providers process device tokens and notification payloads. Notification previews may reveal information on a device's lock screen according to its settings.
Google states that phone numbers provided for Firebase authentication are sent to and stored by Google for spam and abuse prevention across Google services. This applies when the Firebase verification route is used. See Firebase phone authentication.
When you open a map in the map-enabled version, OpenFreeMap supplies the basemap, street tiles, labels and symbols. Requests to its public tile service send your IP/network information and the requested map area. UmeCall does not add your name, telephone number, account identifier, authentication token or private messages to those map-resource URLs. Your selected map area can differ from your actual location. Device location is accessed only through the existing optional location permission and deliberate sharing controls. See the OpenFreeMap Privacy Policy.
Some processing takes place outside Bangladesh, including the configured Backblaze media region in the United States and the international infrastructure used by Google and Apple. Transfers must use the safeguards and lawful arrangements required for the data and countries involved. You may ask us about the providers and safeguards relevant to your information. We do not represent this policy alone as a transfer agreement or proof of local-storage compliance.
The current UmeCall configuration does not enable payment processing or an external generative-AI provider. We do not sell personal information. If a future feature introduces additional recipients or purposes, we will update the notice and obtain any required choice before that processing starts.
We may also disclose relevant information when necessary to comply with a valid legal requirement, address a serious safety issue, or establish or defend legal rights, subject to applicable law. Access is limited to what is needed for the purpose.
Advertising and your choices
UmeCall's next Android closed-test update is being prepared to display clearly labelled Google test advertisements in Stories, between conversations in the Chats list, on another user's Profile and in the ended-call summary. Ads are not shown during an active or incoming call or inside a private conversation. The current iPhone build remains advertising-disabled. Live advertising stays inactive until the applicable Google account/app approvals, store disclosures, consent controls and UmeCall activation checks are ready. A test advertisement is not evidence of live advertising approval.
An advertising-enabled version may use Google Mobile Ads (AdMob). If mediation is enabled later, the approved advertising partners participating in a request will be identified in the consent or advertising-information interface. Depending on the app version, location and choices, Google and participating partners may process an IP address, approximate location inferred from the IP address, app and device identifiers, ad views and taps, diagnostics, and fraud-prevention signals to deliver ads, limit repetition, measure performance and prevent invalid traffic. See how Google uses information from sites or apps that use its services.
UmeCall requests non-personalized advertising only. It does not provide the content of private messages, calls, voice notes, selected files, address-book telephone numbers or precise shared location to advertising providers to select ads. Non-personalized advertising may still process the advertising and consent information described above; it does not mean no data is collected. Ads use Google's general-audience content filter and must be clearly identifiable. Users can report an inappropriate ad through its information controls or Help & Support.
Advertising is available only after an account has declared that its user is 18 or older. This declaration is not identity or age verification. UmeCall checks the account's existing UME age declaration without creating a UME Card. If no adult declaration exists, an optional advertising age choice is stored on this device separately for that account; no date of birth is requested. An existing under-18 account declaration overrides a local adult choice. Choosing Under-18, Skip or leaving age unknown means no advertising. Declining this choice does not block chat or calls. You can revisit the local choice in Advertising settings; changing devices or reinstalling may require choosing again.
The advertising-enabled Android version presents Google's consent interface before requesting ads where required, including in the European Economic Area, United Kingdom and Switzerland, and provides a way to revisit the available advertising choices. Refusing or withdrawing an advertising choice does not block messaging or calling; it may result in non-personalized or limited ads, or no ad. On iPhone, advertising remains disabled until UmeCall has its own iOS identifiers and requests App Tracking Transparency permission before any cross-app tracking or advertising-identifier access that requires it. See Privacy choices for the available controls.
How long information is kept
Account and communication data are retained while needed to provide the account and features you use, unless you delete them or a shorter feature-specific period applies. A displayed expiry or removal from a screen does not necessarily mean every backup or recipient's copy has been erased.
An account-deletion request deactivates the account and starts the 30-day cancellation period shown in the app. After it ends, erasure is subject to the required identity, content, media, provider/backup and legal-retention checks. Some steps require operator review. We do not promise automatic completion on day 30. Security incidents, abuse reports and legal holds can justify retaining limited relevant records for as long as the specific purpose or law requires; they do not justify keeping all information indefinitely.
Routine database backups currently use a seven-day/seven-copy rolling schedule. This is not a seven-day guarantee for every copy: deployment/recovery snapshots and provider-retained copies require separate review. If a backup is restored, completed deletion requests must be applied again. Copies independently saved by recipients are outside our direct control. Ask support about the status and scope of a deletion request.
Your choices and rights
You can review profile and privacy settings, revoke device permissions, block users, review sessions and request account deletion. The Privacy choices page explains these controls and the status of advertising choices. Where applicable, you may ask to access or receive a copy of your information, correct it, withdraw consent, object to or restrict processing, or request erasure and portability. Withdrawing consent does not invalidate earlier lawful processing and may prevent the optional feature from working. Some information may still be necessary for another lawful purpose.
Send a written request through Help & Support, or contact the operator to arrange one. We may ask for proportionate evidence of identity or authority before acting. We will explain a restriction or refusal and respond within the period required by applicable law. You may complain to the competent data-protection authority or seek other remedies available to you; this policy does not waive those rights.
Children and guardians
UmeCall's intended audience includes families, but a child's independent agreement is not sufficient where guardian consent is required. For users under 18 in Bangladesh, a parent or lawful guardian must provide the required consent before the child's information is collected or processed. Other countries may apply additional rules.
Where the required consent cannot be obtained, a child must not open or use an account. Parents or guardians may contact us about an account or information they believe was provided without the required authority. We will review the report and restrict, delete or otherwise handle the information as required by law. A parent's use of UmeCall does not automatically authorize collection of a child's information.
Changes
Published policies will show a version and effective date. We will give notice of material changes and request fresh consent where required. The effective date above identifies this published version.