Privacy Policy

My Status ("we", "our") is a social network and services marketplace built for users in Uzbekistan. The app provides posts, stories, short videos (reels), private and group messaging, channels, the Ad Window, targeted advertising campaigns, and the ability to get in touch with professionals in various trades (Servis). This policy explains what data is collected when you use our mobile app or our website, where it is stored, who it is shared with, how it is protected, and what your rights are.

1. Data is stored in Uzbekistan

All user data (profiles, posts, messages, media files) is stored on a server located in the Republic of Uzbekistan (a data center in Tashkent). This complies with the data localization requirement of the Law of the Republic of Uzbekistan "On Personal Data". Our backend infrastructure:

• PostgreSQL 17 — structured data (profiles, posts, messages, comments, reports)
• MinIO (S3-compatible object storage) — media files (images, videos, voice messages, avatars, stories, reels)
• Redis — caching and queues
• NestJS API — business logic and the real-time (WebSocket) service
• Content safety classifier — a model on our own server that checks images and videos (it does not send them outside)
• Nginx — TLS 1.2/1.3 + HSTS

The primary copy of your data is not transferred abroad. However, for some features to work, a limited portion of data is sent to services abroad: Google (Firebase Authentication, Firebase Cloud Messaging, Firebase Crashlytics, Gemini AI), Telegram and Anthropic (error reports), and map services (OpenStreetMap, Yandex). Exactly what is sent to each is set out in section 7.

2. Data we collect

Account data. Registration and sign-in are done only through a Google account (Google Sign-In). We receive your email address, name, and profile picture from Google. There is no sign-in by SMS or phone number.

Profile data (optional). First name, last name, username, profile picture, bio, profession(s), business details (name, description, address, map location, working hours), contact phone number, Telegram username, region (province), gender, and year of birth. Region, gender, and year of birth are used to show advertising campaigns to a suitable audience; if you do not provide them, ads are shown to you without restriction.

User content. Posts (images and text), reels (short videos), stories (images/videos that last 24 hours), comments, reactions, advertising videos. All media is stored in our MinIO object storage (in Uzbekistan).

Messages. Messages in private (1:1) chats, groups, and channels: text, images, video, voice and round video messages, files, location, contact cards, polls. Messages are stored on our server and delivered to you and the people you chat with. In the current version, messages are not end-to-end encrypted — details in section 5.

Link previews. If you add a link to a message, our server (not your device) downloads that page in order to display its title and image.

Location (optional). Collected only when you grant permission and start the action yourself: sending your location in a chat or marking your business profile address on the map. This is a one-time coordinate — there is no background tracking.

Camera and microphone. Used only when you create media for a post / reel / story / ad, or record a voice or round video message. They are never used in the background or without your permission.

Gallery. If you grant permission, the in-app gallery shows the photos and videos on your device so you can pick them — this happens only on the device itself. Only the files you select are uploaded to the server.

Activity indicators. Likes, saved items, subscriptions, read marks, views, ad views and clicks. These are necessary for social features, tiers (status), and the coin balance.

Coins and payments. Coins are awarded for in-app activity (views, likes, followers), and additional coins are added only by an admin; they are spent only on advertising and are not exchanged for money. There is no in-app payment (in-app purchase). Payment for paid slots in the Ad Window is made outside the app, via USSD, and is confirmed by an admin. We do not receive or store bank card details; only the payment amount and its confirmation status are recorded.

Push notifications. When notifications are enabled, a Firebase Cloud Messaging (FCM) token is stored for each of your devices. When you sign out, that device's token is deleted.

Reports. If you report a user, post, comment, or chat, the reason, the reported object, and your ID are stored (for admin review).

Diagnostics. If an error occurs while the app is running, an error report is sent to our server: the error text and stack, app version, platform and OS version, your user ID, the name of the open screen, a list of recent screen transitions and server requests (address, status code, time), and a short excerpt of the request/response. Before sending, tokens, keys, and phone numbers are masked. The server forwards the report to a closed Telegram group of developers. In addition, in release versions, Firebase Crashlytics sends information about app crashes (stack, device model, OS version) to Google.

3. How we use data

The data above is used for the following:

• Running the core features (feed, messaging, profile)
• Finding and contacting specialists in the Servis section
• Showing advertising campaigns to the selected audience (region, age, gender)
• Combating spam, violence, and other violations (content moderation, section 4)
• Fixing errors and improving quality and stability
• Push notifications about new messages and activity

We do not sell or transfer your personal data to advertisers. The owner of an advertising campaign only selects audience conditions (region, age range, gender); our server decides whom to show it to. The advertiser sees only aggregate numbers (views, clicks) for their campaign. Third-party ad networks and advertising SDKs are not used.

4. AI and content moderation

Caption and hashtag suggestions (Google Gemini). When you press the AI assistant button, the text you wrote and (if you selected one) an image are sent through our server to the Google Gemini API. The result is published only after you confirm it.

Content safety. Posts, reels, stories, ads, messages in public groups/channels, and content forwarded to another chat are checked in three stages:

1. On the device. Before an image or video is uploaded, if a small model on your device detects explicit sexual content, the upload is stopped — the file is not sent to the server.
2. On our server. Uploaded images and video frames are checked by a classifier on our own server, and text is checked using rules. At this stage no data leaves our systems.
3. Google Gemini. Only in borderline cases where the previous stage could not reach a clear decision, that image, those video frames, or that text are sent to the Google Gemini API for analysis.

Depending on the result of the check, the content is published, held so that only its author can see it until an admin reviews it, or rejected. The decision (not the content itself: type, category, reason) is stored in the moderation log.

Private messages (1:1 chats) and closed groups are not put through automatic moderation and are not sent to AI — with the exception of messages forwarded from another chat.

5. Messages and encryption

All messages are transmitted between your device and our server over a channel encrypted with TLS (HTTPS/WSS). Since 6 October 2026, message text, file names, contact cards, polls, and location data are also stored encrypted (AES-256-GCM) on our server, and database backups are also encrypted. However, this is not end-to-end (E2EE) encryption: the encryption key is held on our server, so the service decrypts messages for delivery, notifications, and search, and in the cases listed below our team can read them. The images, videos, voice messages, and files themselves remain unencrypted in media storage.

• Reason: there is not yet a way to back up a personal key. If the phone were replaced or the app reinstalled, the entire message history would be irreversibly lost along with the key. For this reason, from August 2026 new messages are not encrypted
• Previously encrypted messages: some text messages sent in 1:1 chats before August 2026 remain encrypted with X25519 + HKDF-SHA256 + AES-256-GCM, and only a device that holds the key can open them
• Access: we do not analyze messages for advertising or profiling. There is no feature in the admin panel for reading private chats; a message may be reviewed only when investigating a report or when legally required
• Push notifications: in group and private message notifications, the sender's name and a short text of the message are delivered to your device through Google FCM

We plan to turn end-to-end encryption back on once key backup is ready; we will announce this on this page.

6. Data retention periods

7. Third-party services

We use the following services — each has its own privacy policy:

• Firebase Authentication (Google) — sign-in via Google Sign-In. Sent: Google account data (email, name, profile picture), Firebase UID. Purpose: authentication.
• Firebase Cloud Messaging (Google) — push notifications. Sent: the device FCM token and the notification content (sender name, short text of the message). Purpose: delivering the notification.
• Firebase Crashlytics (Google) — crash reports in release versions. Sent: error stack, device model, OS version. Purpose: stability.
• Google Gemini API — AI caption suggestions and content moderation in borderline cases (section 4). Sent: the text/image you gave to the AI; in moderation — the image, video frames, or text being checked. Purpose: content assistance and safety.
• Telegram — error reports and messages about the moderation queue are sent to a closed group of developers. Sent: the diagnostic data in section 2 (with the user ID); in moderation messages, only the content type, ID, and reason (not the content itself).
• Anthropic (Claude) — an AI programming assistant our developers use when analyzing error reports. Sent: the diagnostic data in section 2. Purpose: finding and fixing errors.
• OpenStreetMap and Yandex Maps — sending/viewing a location and determining an address. Sent: the coordinates shown on the map (map tiles and address search are loaded from OpenStreetMap, and the map image from Yandex, directly through your device). Purpose: displaying the map.

We do not use any other third-party analytics, advertising SDKs, or tracking services.

8. Data sharing

We do not sell, rent, or trade your personal data. It may be shared only in the following cases:

• The services listed in section 7 (only to the extent stated there)
• When there is a mandatory legal request from an authorized body under the legislation of the Republic of Uzbekistan
• Your public content (posts, profile, public channel/group content) is visible to its audience

9. Public and private data

Visible to others: posts, reels, stories, public channels and groups; on your profile, your name, username, picture, bio, tier, profession, business details (address, map location, working hours), contact phone, Telegram name, region, and gender. The share link of a post, reel, or story can also be opened on the website, without the app.

Visible only to you (and the service): your email address, year of birth, coin balance, saved items, and reports. Private messages and the content of closed groups/channels are visible only to their participants.

Media files are delivered through a long link that cannot be guessed. Anyone who obtains such a link (for example, one passed on by the person you chat with) can open the file — this applies to all images, videos, and chat files.

10. Use by children

My Status is not intended for people under 18. We do not knowingly collect data from minors. If you know that a minor has opened an account, write to us — we will delete the account. Our rules on child safety: Child Safety Standards.

11. Your rights

• Right of access. You may request all the data that relates to you (by email)
• Right to rectification. You can correct it yourself on your profile page, or write to us
• Right to erasure. See below (section 12)
• Right to portability. You may request the data that relates to you in a machine-readable format (JSON)
• Right to object. You may send your objection to how data is processed by email

12. Deleting your account

You can delete your account and all related content through the app:

1. Open the app → Profile → Settings
2. Press the "Delete account" button
3. To confirm, type the word O'CHIRISH and confirm

After confirmation, immediately your profile, posts, reels, stories, the messages and files you sent, comments, subscriptions, advertising slots and campaigns, coin balance, and device tokens are deleted, and the app also deletes your Firebase account; media files are also deleted from the server. Full clearing from backups happens within 90 days. Details: Delete account.

If you cannot access the app, email us: erkinovbegzod.45@gmail.com.

13. Security measures

• Transport: TLS 1.2/1.3 + HSTS (HTTPS only)
• Authentication: a 15-minute session token + a 30-day refresh token (with rotation and a list of revoked tokens); the option to "sign out of all devices"
• Moderation and blocking: reports, blocking a user, and the automatic checks in section 4
• Limits: the number of requests for sign-in, comments, and reports is limited
• Encryption: message text is stored on the server encrypted with AES-256-GCM (not end-to-end, see section 5)
• Backups: a daily database backup, encrypted (GPG; the decryption key is not stored on the server)
• Server access: SSH by key only (password sign-in is disabled), fail2ban, UFW firewall

14. Changes

We update this policy from time to time. The date at the top of the page reflects the latest version. If there are major changes, we will notify you in the app. Continuing to use the app signifies your agreement to the updated policy.

15. Contact

For questions or to exercise your data rights, write to the following address:

• Email: erkinovbegzod.45@gmail.com
• Website: my-status.uz