Legal

Privacy Policy

Dilinga is built so that the conversation stays with the people having it. This policy explains, in plain terms, what the app handles and why.

Last updated: 3 September 2026

The short version. There is no account and no advertising. You are identified by an ID your own device creates. During calls your phone recognises speech and only the resulting text is translated. Call transcripts never leave your device. We do not sell personal data and we do not build advertising profiles.

Who this policy covers

This policy covers the Dilinga mobile application and the website at dilinga.com. Dilinga is a product of AYARUX. For anything in this policy, write to [email protected].

There is no account

Dilinga does not ask you to sign up. We do not collect an email address, a password or a phone number, and the app does not read your phone's address book.

Instead, the app creates an identifier on your device the first time it runs, and signs in anonymously to our backend so that its requests can be authorised. You also get a short Dilinga ID that other people can use to add you.

What you choose to put in your profile — a display name, the language you read, an optional status or picture — is stored so that the people you talk to can see it.

Messages, media and translations

Messages you send are stored so they can be delivered and so the conversation is still there when you open it again. They are carried over encrypted connections and stored by our infrastructure providers. Dilinga is not end-to-end encrypted: to translate a message, the service has to be able to read it.

Photos, files and voice notes you attach are stored in our file storage so the other person can open them, and are served from there.

Text sent for translation is passed to the translation service, translated and returned. We do not use your messages to train models.

Calls

Voice and video calls run over a real-time calling service. During a translated call, speech recognition runs on your own device: your phone turns what you said into text, and it is that text — not the audio of the call — that is sent for translation and spoken to the other side.

The running transcript of a call is kept only on the device that produced it, so you can look back at what was said. It is not uploaded, and it is dropped as older calls age out.

We keep basic call records — who called whom and when, and short technical diagnostic events — so that call quality problems can be investigated.

Camera, scanning and Ask

The camera is only used while you are on the camera screen. When you take a photo to translate, the text in it is recognised — on the device where the platform allows it, otherwise by our text recognition service — and translated.

When you use Ask, the photograph and your question are sent to an AI provider to produce an answer. Photographs used for scanning and Ask are processed to answer that request and are not kept as part of your profile.

Voice modelling (closed beta)

Dilinga can speak a translation in the speaker's own voice. This is opt-in, currently limited to a closed beta, and it requires a short sample you record yourself together with a spoken consent.

The sample is sent directly to the voice provider that builds the model; we do not keep the raw recording. You can delete your voice model from the app at any time, and deleting it removes it at the provider as well.

Notifications

To tell you about an incoming call or message, the app registers a push token with Apple's or Google's notification service. The token identifies the installation, not you.

Who processes what

Dilinga uses a small number of specialist providers. Each one receives only what its part of the job needs.

ProviderWhat it handles
Google FirebaseAnonymous sign-in, profiles, conversations and messages, push delivery
CloudflareOur API, and storage for photos, files and voice notes
Microsoft AzureText translation, text recognition, and speech for calls
OpenAIHigher-quality translation for some languages, spoken output outside calls, and answers on the Ask screen
StreamVoice and video call transport
CartesiaVoice modelling, for beta participants who opt in
Apple, GooglePush notification delivery, and app distribution

These providers act for us and are not permitted to use your content for their own purposes.

What we do not do

  • We do not sell or rent personal data.
  • We do not show advertising and we do not build advertising profiles.
  • There is no third-party analytics or tracking SDK in the app.
  • We do not read your phone's contact list.
  • We do not listen outside the moments you are actually using a translation feature.

How long things are kept

Messages and their attachments stay until they are deleted. Profile data stays while the account exists. Call records and diagnostic events are short-lived and kept only long enough to investigate problems. Call transcripts live on your device and roll off as new calls replace them.

You can ask us to delete everything associated with you — see Delete your data.

Children

Dilinga is not directed at children under 13, and we do not knowingly collect information from them. If you believe a child has used the app and left data with us, write to [email protected] and we will remove it.

Your rights

Depending on where you live — including under the GDPR in the EU/UK and KVKK in Türkiye — you may have the right to access, correct, delete or export your personal data, to object to certain processing, and to complain to a supervisory authority.

Because there is no account to log into, we may ask you for your Dilinga ID so that we can find the right data. Write to [email protected].

Where data is processed

Our providers operate globally, so your data may be processed outside your own country, including in the United States and the European Union. Where the GDPR or KVKK applies, those transfers rely on the safeguards the providers offer, such as standard contractual clauses.

Security

Traffic between the app and our services runs over encrypted connections. API keys for translation and speech services live only on our server and are never shipped inside the app. Access to production data is limited to the people who need it.

No service can promise perfect security, and Dilinga is not end-to-end encrypted. Treat it as you would any other messaging app for anything unusually sensitive.

This website

dilinga.com is a static site. It sets no cookies, runs no analytics, and loads no third-party scripts or fonts. Our hosting provider processes ordinary request information — such as an IP address and a browser type — to deliver and protect the site. See the Cookie Policy.

Changes

If this policy changes, the updated version is published on this page with a new date. Material changes will also be surfaced in the app.

Contact

Questions about this policy, or a request about your data: [email protected].