Privacy Policy
Dabaza is built so that typing works on your device. The keyboard layouts and the built-in dictionary are bundled locally, and no account and no network connection are required for everyday typing. This policy explains which optional features send data, what is sent, and how you stay in control. The policy is available in Arabic, Uyghur, Chinese and English; the English text is the reference version if a translation is unclear.
1. Who is responsible
The Dabaza project publishes the Dabaza keyboard for Android (application ID com.dabaza.ime) and the Dabaza writing assistant for Windows. The project is the data controller for the optional services described below. Questions and requests: see section 9.
2. What we process
Nothing below is required for basic typing. Each optional capability is off by default and is enabled only by your explicit choice in the app settings.
| Data | When | Why |
|---|---|---|
| Keyboard layouts and the built-in dictionary | Always, on device | Typing. Never leaves the device. |
| Words learned from your own typing | On device only | Better suggestions. Stored in the app's private storage. |
| Random installation identifier, app version, selected input language, event counters | Only after you turn on input-record sync / analytics | Service health, dictionary update checks, aggregate usage statistics. The identifier is generated on the device and is not an advertising ID. |
| Typed phrases (the text you actually entered, up to 4000 characters per record) | Only after you separately turn on input-content collection | Improving dictionaries and suggestions. Off by default, independent from analytics. |
| Mobile phone number | Only if you choose to create a phone account | Sign-in and account recovery, verified by a one-time code. |
| Notice and advertisement impressions, clicks and dismissals | Only after you turn on notices/advertisements | Showing sponsored notices inside the app and measuring them in aggregate. |
| Feedback you submit | Only when you press send | Answering your report. |
We do not collect your contacts, SMS or call logs, photos, files, precise location, calendar, or the contents of password fields. Password fields are always excluded from learning and from any collection.
3. What we never do
- We do not sell your data.
- We do not embed third-party advertising networks or third-party analytics SDKs in the Android app. Sponsored notices are simple text and images delivered by the Dabaza service with your consent.
- We do not read your messages, contacts or files, and we do not use accessibility capture of other apps.
- We do not transmit sensitive content over plain HTTP. Any account, consent, dictionary-acknowledgement, advertising and feedback traffic uses HTTPS only.
4. Legal basis and consent
Optional processing relies on your consent, which you give separately for each capability and can withdraw at any time in the app settings. Basic typing, the local dictionary and on-device learning do not depend on any consent because no data leaves your device. Account features rely on the performance of the service you asked for.
5. Sharing and transfers
Data from the optional services is stored on servers operated for the Dabaza project. We do not share it with third parties for their own purposes. Where a hosting provider processes data on our behalf, it does so under our instructions. Data is transmitted over TLS.
6. Retention and deletion
On-device learning data stays on your device until you clear it in the app or uninstall the app. For the optional services, records are kept only while your consent is in force and are deleted when you withdraw that consent: withdrawing input-content consent immediately stops collection, clears the local pending queue and removes previously stored content and derived data on the server. Account and consent records are kept while the account exists; deleting the account removes its records. Operational database backups are rotated within 30 days.
You can ask for access to, correction of, or deletion of your account data at any time using the address in section 9, or delete a customer account from inside the app.
7. Children
The app is a general-purpose keyboard and is not directed at children under 13. We do not knowingly collect data from children. The optional network features are off by default.
8. Security
Optional traffic uses HTTPS. Dictionary updates are only installed after the version, entry count and SHA-256 checksum have been verified. Sessions are stored on the server in hashed form, and one-time login codes are short-lived.
9. Contact and changes
Privacy questions, access and deletion requests can be sent to the contact published on the Dabaza product website. If this policy changes in a way that affects you, the new version will be published on this page with a new effective date, and material changes will also be described in the app's release notes.
Effective date: 2026-10-12 · This page is the official privacy policy referenced by the Dabaza app store listing.