Revision of · 01.11.2026
1Who the personal-data operator is
The operator of personal data in the tezfin app and on tezfin.uz is individual entrepreneur Устинов Антон Викторович (state registration certificate of an individual entrepreneur No. 7269869 of 14.11.2025; Tashkent, Republic of Uzbekistan). The operator’s full address and PINFL are provided on request at privacy@tezfin.uz. tezfin is the name of the app and the website, not of a legal entity. Processing follows Law of the Republic of Uzbekistan No. ZRU-547 "On personal data".
tezfin is a personal finance tracking and financial-passport app; the Baraka Town game lives inside it. Loans are issued by microfinance organisations under their own contracts; tezfin is not a lender and does not take deposits.
2What this covers
The tezfin mobile app including the Baraka Town game, the tezfin.uz website, and the forms you use to send us applications, enquiries and feedback.
The microfinance and merchant cabinets are separate products for the staff of those organisations. Data handling there is governed by the contracts with those organisations, not by this document.
3What we collect
The list is exactly this and nothing more:
- Account details: the email address the account is registered to, and your date of birth. The address is confirmed with a one-time code; the date of birth is self-declared and not checked against a document — the product has no document-verification step. A name is stored only if you gave one earlier: version 1.0 does not ask for it.
- Phone number — optional: you enter it in your profile yourself. It is not verified and is used so that a family member can invite you by number.
- Financial-passport questionnaire answers: income source and amount, income currency, employment sector, social status, housing type, rent amount, household size and number of dependants. Sector and status are stored as dictionary codes, not free text.
- Ledger entries: income and expenses with amounts and dates, categories, recurring plans and contracts, cost centres, goals and your own notes on them — including a phrase you dictated by voice.
- Loan details: the ones you entered yourself (lender name, amounts, schedule) and, if your account was linked to a microfinance organisation earlier, the ones it sent in. Version 1.0 of the app does not offer to link an account to an organisation.
- A credit-bureau summary — if you uploaded a KATM report yourself in the "Passport" section: bureau score, longest overdue period and number of open disputes. The app itself does not query KATM/KIAC.
- The financial-passport score on the 300–850 scale and the components computed from everything above.
- Learning and task data: completed financial-literacy lessons, points for tasks, hints you dismissed, and your mahalla number in the game.
- Technical data: the device push-notification token, the platform (Android or iOS) and the interface language. Every consent record also carries the interface language and the app version.
- Enquiries and feedback you send from the app, with a technical note — the contents are described in the "Feedback" section.
- Anonymised app crash reports — their contents are described in the "App crash reports" section.
- The days on which you opened the app — the date only, without the time, screens or actions. We use them to compute overall usage statistics: how many people use the app and come back to it. No individual person is visible in these statistics.
We do NOT collect passport number, PINFL (JSHSHIR), bank card number, home address or employer name: the data schema has no field for any of them. Of your location only the country is stored, as a two-letter code. The app does not ask for location, camera or photo access.
4Consents and purposes
The consent catalogue has six purposes, each its own switch. Version 1.0 of the app offers four of them:
- "Processing of personal data" — mandatory: the account does not work without it. It cannot be withdrawn on its own; you can delete the account instead.
- "Credit history request (KATM/KIAC)" — not offered in version 1.0. If you accepted it in an earlier build, it is shown in the consents section and can be withdrawn; withdrawal deletes the bureau summary from your account immediately.
- "Building and sharing the scoring result with partners" — not offered in version 1.0, and the system does not share the score with partners. A consent accepted earlier is shown in the consents section and can be withdrawn.
- "Cross-border processing of anonymised analytics" — optional, withdrawable. No live scenario performs the processing it allows today.
- "Marketing and notifications" — optional, withdrawable. Version 1.0 sends no advertising. Service push notifications do not depend on this consent: you can turn them off in the phone settings, and contract payment reminders also in the app settings.
- "Shared household budgeting" — optional, withdrawable. Withdrawal takes you out of the family at once and erases your contributions to shared goals.
No consent is pre-ticked. Every acceptance and every withdrawal is recorded together with the purpose, the revision of the text, the date, the interface language and the app version. The consent log cannot be rewritten after the fact — that is enforced by the database itself.
5Who we share with
Data leaves tezfin only in these cases:
- Apple and Google — if you take part in the closed test of the app: your email address goes to TestFlight or Firebase App Distribution so an install invitation can be issued.
- Google Firebase Cloud Messaging, and on iPhone also the Apple notification service: your device token and the push text. Notifications are service messages — a contract payment reminder, a family invitation, a loan update; their text carries no amounts, contract names or names of people.
- The email services Resend and — if Resend does not accept a message — Mailjet: emails with a one-time code for sign-in and for account deletion, and closed-test invitations. They receive your email address and the message text, including the code.
- Cloudflare — the app downloads game graphics from cdn.tezfin.uz through its network. Cloudflare sees the phone’s IP address and the name of the file; the request carries nothing about your account.
- The phone’s speech-recognition service — when you dictate an entry: Apple on iPhone, the provider of the system recogniser on Android (usually Google). Details are in the "Voice input" section.
- Members of your family in tezfin — under the "Shared household budgeting" consent. There are no hiding settings inside a family: members see everything the app shows in the family section — the budget with who added each entry, goals, contributions, cost centres, ratings and challenges. Family membership is taken into account in the score.
- Google Firebase Crashlytics — anonymised app crash reports. They carry nothing about your account.
- Version 1.0 does not pass your data to microfinance organisations, credit bureaus or other partners. If such a transfer appears, the app will ask for a separate consent, and this policy will be updated before it starts.
Account data is stored on servers in Tashkent, Republic of Uzbekistan. Only what is listed above goes abroad, and only to these recipients: Google LLC (USA) — Firebase Cloud Messaging, Firebase Crashlytics and Firebase App Distribution; Apple Inc. (USA) — TestFlight, notification delivery to iPhone and speech recognition on iPhone; Resend, Inc. (USA) and Mailjet SAS (France) — emails; Cloudflare, Inc. (USA) — game graphics delivery; the provider of the system speech recogniser on Android. They process this data on their own servers, including outside the Republic of Uzbekistan. Installing the app from the App Store and Google Play is handled by Apple and Google under their own rules. We do not send your questionnaire answers, ledger entries or score abroad.
6App crash reports
If the app crashes or hits an unexpected error, it sends a crash report to Firebase Crashlytics, a Google LLC service. The report is used only to find and fix the fault.
- A report contains the stack trace and error type, the device model, the operating-system version, the app version and build number, technical device parameters at the moment of the crash (screen orientation, free memory and the like) and the time of the crash.
- The app strips the error message text before sending, because it could contain something you typed.
- A report is tagged with a random installation identifier generated by Crashlytics itself; it is not linked to your account. Your user ID, email address, phone number, amounts and entry texts never go into the reports.
- Reports are processed on Google servers, including outside the Republic of Uzbekistan.
The app contains no analytics — not Firebase Analytics, not Google Analytics, not any other. It does not collect the device advertising identifier (Android Advertising ID, IDFA on iOS), does not track you across apps and websites, and shows no ads.
7The Baraka Town game
Baraka Town is a game inside the tezfin app, not a separate app. This is how it treats data:
- The game save is kept only on the phone, in the system’s secure storage, and is not sent to a server. It is erased when you sign out and when you delete the account; it cannot be moved to another phone.
- To build the town, the game takes your ledger entries and categories from the tezfin server, or from the cache on the phone when offline. The game does not send its own progress to a server.
- Game graphics are downloaded from cdn.tezfin.uz through the Cloudflare network: Cloudflare sees the phone’s IP address and the file name. Downloaded graphics stay in the app cache.
- Mini-games open from files inside the app and do not visit other websites.
- Feedback from the game goes to support with a technical note about the game and the phone: game version, device model, operating-system version, screen size, frame rate, memory use. You can switch the note off before sending.
- There is no advertising in the game.
8Feedback
Shake the phone or open "Feedback" to send us an enquiry. Along with your text we receive:
- the category (bug, feedback or question) and the name of the screen you were on;
- a technical note: the screen address in the app (it may contain the internal number of the record you had open), the app version and build number, the operating-system version and the app language;
- the link to your account — the server takes it from your sign-in; your name and phone are not added to the enquiry;
- the app takes and attaches no screenshots.
Enquiries are kept in the tezfin support service. The system sets no retention period for them, and deleting the account does not erase them: you can ask for them to be deleted at the address given at the end of this document. Shaking can be switched off in the app settings. You can also write to support at support@tezfin.uz; all the ways to reach us are on https://tezfin.uz/support.
9Voice input
You can dictate a ledger entry. Speech is recognised not by tezfin but by the phone’s own service:
- on iPhone — Apple’s speech recogniser. The app does not require on-device recognition, so the audio may be processed on Apple’s servers under Apple’s rules;
- on Android — the on-device recogniser if it supports the language (Android 12 and later); otherwise the system recogniser, which may send the audio to its provider, usually Google;
- the audio is not sent to tezfin servers. Only the recognised text reaches tezfin: it is saved in the note of the entry (“By voice: …”) together with the entry itself;
- you can also add an expense through Siri: Apple processes the phrase, and tezfin receives only the entry type, category, amount and date.
Microphone and speech-recognition access is granted and withdrawn in the phone settings.
10What stays on the phone
Some information the app keeps only on the phone and does not send to a server:
- the "Data and storage" section: the graphics cache size, the game traffic counter and the auto-download settings are counted and kept on the phone;
- loan payment reminders the app schedules itself: they may contain the amount and the date, and they are created on the phone, without the server;
- Face ID or fingerprint sign-in is checked by the phone’s system; the app has no access to biometric data;
- the shake for feedback is detected by the phone’s motion sensor.
11What we never do
These statements rest on how the system is built, not on a promise:
- Passport number, PINFL and card number can be neither stored nor shared: there is no field for them.
- One-time codes and link tokens are never stored as such — only as an irreversible fingerprint with a secret pepper. A code cannot be reconstructed from the database.
- In logs the phone number and email address are masked, and a person is identified only by a pseudonymous account identifier. Metric labels are the route, the outcome and the response code — never your identifier.
- We do not sell personal data and do not pass it to third parties for advertising. The app has no third-party analytics, no ads and no device advertising identifier. We compute usage statistics ourselves, on our own servers in Tashkent, look at them only in aggregate and share them with no one. The only third-party diagnostic service is the anonymised crash reporting described above. The merchant you buy from in instalments never sees you — a dedicated build check enforces that.
12The tezfin.uz website
The site works without a login and without tracking:
- The locale cookie remembers the chosen language. Other cookies are set only in sign-up-by-invitation-link flows — so that one invitation cannot be spent twice.
- The server counts page requests: route, method and response code. Who made the request is not recorded in those counters.
- The visitor IP address is passed to the gateway to rate-limit requests and stop automated form abuse.
The site carries no web-analytics counters, ad pixels or third-party scripts: the content security policy forbids the browser from loading foreign code.
13How long we keep it
The periods that actually apply:
- While the account exists, the account data is kept. A questionnaire answer you withdraw is deleted straight away.
- After the account is deleted, records that cannot be erased by law or by the design of the system are retained for 1825 days (5 years) from the deletion date: the consent log, the score history, the ledger edit history and the links to microfinance organisations. The itemised list with grounds is on the "Account deletion" page; the end of the retention period is recorded at the moment of deletion.
- A one-time code lives for 5 minutes, is spent by the first correct entry and allows no more than five attempts.
- Support enquiries are kept with no set period and are not erased by account deletion — they can be deleted on request.
- The game save is erased from the phone when you sign out. When you delete the account, the app also erases the cache, the PIN code and the biometric sign-in setting from the phone.
- Days of app use — 400 days; erased immediately when the account is deleted.
Withdrawing a consent takes effect at once: "Credit history request" deletes the bureau summary from the account, "Shared household budgeting" takes you out of the family and erases your contributions. Version 1.0 passes no data to partners, so there is nothing to erase on their side.
14How we protect it
Measures that are always on:
- Traffic to the app and the site runs over TLS only, through a gateway that rate-limits requests.
- Sign-in is confirmed with a one-time code sent by email and a password; one-time codes and link tokens are stored only as an irreversible fingerprint with a secret pepper.
- The consent log, the score history, the ledger edit history and the deletion journal are protected from rewriting by the database itself.
- Operator-initiated account deletion is off by default. When it is switched on it requires a stated reason and lands in a separate immutable journal.
- What the app keeps on the device — loans and the payment schedule, the profile, ledger entries, the financial passport, enquiries — sits in an encrypted SQLCipher database (AES-256). The encryption key is held in the system’s secure storage: Keychain on iOS, AndroidKeyStore on Android. The game save is kept in secure storage too.
- Sign-in tokens are kept in the device secure storage. System backup of the app is disabled on Android, and on iOS the local data is excluded from iCloud backup.
15Your rights
Under ZRU-547 you may:
- learn what data of yours we hold and receive a copy of it;
- correct inaccurate data — account details, questionnaire answers and ledger entries are editable right in the app;
- withdraw any consent except the mandatory one — in the app, in the "Consents and data" section;
- delete the account, from the app; the procedure is described on a separate page.
The mandatory consent to personal-data processing cannot be withdrawn on its own: the account does not work without it. The only way to stop the processing is to delete the account.
16Age
A tezfin account can be opened only from the age of 18: registration requires a date of birth, and the full 18 years are counted against the civil date in Tashkent. There are no accounts for children or teenagers in the product.
17Changes to this document
A new revision is published on this same page, with the revision date at the top. If the wording of a consent changes, the app asks you to confirm it again: every consent is recorded together with the revision of the text it was given under.
18How to reach us
Requests are answered by the operator, individual entrepreneur Устинов Антон Викторович. If you disagree with how we handled your request, you may approach the authorised state body for personal-data protection of the Republic of Uzbekistan.
Personal-data requests, questions about these documents and account-deletion requests are handled by the operator, individual entrepreneur Устинов Антон Викторович, at privacy@tezfin.uz. Include the email address the account is registered to: otherwise we cannot identify you.