Privacy Policy
Choose an app: what data is collected, how it is used and protected.
This Privacy Policy describes what personal data the Saraf Sales mobile application (the "App") collects, how it is used, shared, stored, and protected. By using the App you confirm that you have read this Policy and agree to its terms.
Short summary (TL;DR)
| Data category | Collected | Background | Purpose |
|---|---|---|---|
| Precise location (GPS) | Yes | Yes | Tracking the sales representative's route during working hours, verifying visits to retail outlets |
| Photos (camera) | Yes | No | Capturing merchandising photos, payment receipts, delivery proof |
| Account credentials | Yes | No | Authentication with the corporate server |
| Business data (orders, payments, deliveries) | Yes | No | Performance of work duties |
| Delivery recipient data (name, phone, signature) | Yes | No | Confirming goods handover by a courier |
| Device identifier and hardware fingerprint | Yes | No | License binding to a single device, anti-piracy protection |
| Firebase Cloud Messaging (FCM) push token | Yes | No | Delivery of order-status notifications from the corporate server |
The App does not use advertising, third-party analytics SDKs, does not share data with data brokers, and does not sell user data. Firebase is used exclusively for push notification delivery (Cloud Messaging); Firebase Analytics, Crashlytics, Performance Monitoring, and other Firebase products are not integrated.
01 Collection and use of Location data
This is the key section. Please read carefully.
1.1. What location data is collected
The App collects the device's precise GPS coordinates, including:
- latitude and longitude;
- accuracy of the position fix (in meters);
- speed and direction of movement (if provided by the GPS module);
- timestamp of each fix;
- identifier of the user the fix relates to.
Android permissions used:
ACCESS_FINE_LOCATION— precise GPS coordinates;ACCESS_COARSE_LOCATION— approximate coordinates (fallback);ACCESS_BACKGROUND_LOCATION— collection of coordinates while the App is minimized or in the background;FOREGROUND_SERVICE_LOCATION— running a foreground location service.
1.2. When location data is collected
- Only during working hours explicitly configured by the employer on the server (e.g., 09:00–18:00 on workdays).
- If the employer has not configured working hours, background GPS collection is fully disabled. The App does not collect location in the background "around the clock by default."
- Collection stops when the current time falls outside the configured hours (within the precision of the device system clock).
- Collection resumes automatically after device reboot only if the user previously acknowledged the Prominent Disclosure and the employer has configured working hours.
- Before collection starts the user sees an Android permission request AND an in-app Prominent Disclosure screen explaining the purpose.
- The user can revoke the permission at any time in Android settings — collection stops immediately.
1.3. How location data is used
Coordinates are used exclusively for the following purposes:
- Sales representative route monitoring — the employer can see where the employee was during the workday.
- Verification of retail outlet visits — matching coordinates against client addresses in the database.
- Generation of work reports — statistics on routes traveled and time spent at outlets.
- Logistics optimization — analyzing routes to improve efficiency.
Location data is NOT used for:
- advertising or targeting;
- selling to third parties;
- tracking outside of working hours;
- profiling of the employee's personal life.
1.4. Storage of location data
- Locally on the device: coordinates are cached in a secure Room database in the App's internal storage (inaccessible to other apps) until successful upload to the server.
- On the employer's corporate server: the retention period is determined by the employer's internal policy (typically 6 to 24 months).
- On App uninstall all locally cached coordinates are removed together with the App.
1.5. Sharing location data with third parties
Coordinates are shared only with:
- The employer's corporate server over a secure connection.
- Mapping services (Google Maps, Yandex Maps, Yandex Navigator) — only at the moment the user explicitly taps "Build route" to a client, and only the destination coordinate, not movement history.
- Google Play Services Location — Android system API used to obtain coordinates from the GPS receiver.
Coordinates are NOT shared with advertising networks, analytics SDKs, data brokers, or social networks.
1.6. Consent for location collection
When tracking features are first invoked the App displays a Prominent Disclosure screen with the following text:
"Saraf Sales collects your location data, including in the background while the App is minimized or closed, during the working hours configured by your employer. This data is sent to the corporate server for route monitoring and verification of visits to retail outlets. No collection is performed outside of working hours. By tapping 'Allow' you consent to the collection of location data."
Only after the user confirms this screen does the App request Android system permissions.
02 Purpose of the App
Saraf Sales is a corporate Android application for field sales representatives. The App is intended exclusively for business use by employees of the developer's client companies and is not intended for personal use.
Core features:
- collecting and placing customer orders;
- tracking visits and routes with GPS attribution;
- capturing merchandising photos at retail outlets;
- tracking the employee's GPS location during working hours;
- synchronizing data with the employer's corporate server.
03 Data Controller
The data controller is the user's employer company that issued the App credentials. The controller defines purposes and retention periods in its internal policies.
The App developer (Mirico Systems LLC) acts as a technical processor and does not use user data for its own purposes, does not share it with third parties, does not use it for advertising or analytics.
04 Full list of collected data
4.1. Location data
See section 1.
4.2. Account credentials
- Login (username) issued by the employer.
- Password — stored locally in encrypted form; transmitted to the server only at authentication time over a secure connection.
- User identifier issued by the server after authentication.
- Session token.
4.3. Business data created by the user
- Orders (items, quantities, prices, client, date).
- Payments (amount, method, client).
- Warehouse shipments.
- Visits to clients (start time, end time, coordinates, comments).
- Reports generated within the App.
4.4. Reference data downloaded from the server
- Client list (name, address, coordinates, contacts).
- Product list and prices.
- Warehouse list and stock levels.
- User list (for collaborative features).
4.5. Photos and signatures
The App uses the built-in camera (CAMERA permission) for the following scenarios:
- Merchandising photos during visits to retail outlets.
- Receipt / proof-of-payment photos when accepting card-transfer payments.
- Proof-of-delivery photos taken by a courier closing a delivery.
The CAMERA permission is requested on the first tap of a "Take photo" button in the relevant scenario, not at App startup.
- Photos are saved to the App's internal cache, accessible only to the App itself.
- Uploaded to the corporate server during synchronization.
- The App DOES NOT read the device photo gallery, DOES NOT request
READ_MEDIA_IMAGESorREAD_EXTERNAL_STORAGE.
4.6. Delivery recipient data (Courier mode)
When closing a delivery in Courier mode the user may capture:
- Recipient full name (entered by the courier).
- Recipient phone (entered by the courier).
- Recipient signature — drawn on screen with a finger and saved as PNG.
- Proof-of-delivery photo — captured via the device camera.
- GPS coordinates at the moment of handover.
This data is sent to the employer's corporate server as part of the shipment document and is used exclusively to confirm the fact of goods handover. It is not shared with third parties or used for marketing. The courier must collect recipient data only with the recipient's consent.
4.7. Device identifier and hardware fingerprint (licensing)
To verify license authenticity and prevent piracy, the App transmits the following data to its license server on activation and periodic checks:
- Unique device identifier (UUID, generated by the App on first launch and persisted locally).
- Widevine ID — a stable Widevine DRM identifier.
- Android ID —
Settings.Secure.ANDROID_ID. - Device model, build fingerprint, Android SDK version, locale, time zone, first install time.
- License token (JWT).
This data is sent to https://license.saraf.uz/, owned by the App developer, for the sole purpose of binding the license to a specific device and detecting unauthorized transfers. It is not used for marketing and is not shared with third parties.
4.8. Technical and diagnostic data
- App version, Android version, device model.
- Network connection status (Wi-Fi / mobile / none).
- Error logs (without user personal data) — used for technical support.
4.9. Push notifications (Firebase Cloud Messaging)
The App uses Google's Firebase Cloud Messaging (FCM) service to deliver push notifications from the employer's corporate server to the user's device (e.g., order status changes, new courier assignments).
Data processed:
- FCM device token — a long identifier issued by Google for a specific App install on a specific device. Acts as the "address" used to route notifications. The token is generated by the Firebase SDK on first launch and periodically rotated by Google.
- Firebase Installations ID (FID) — an internal technical identifier required for FCM to function. Managed by Google.
- Notification data payload — contains only the following fields: document identifier (order UUID), document type (
ORDER, etc.), notification title and body text (which may include the client name and order number). These are service messages composed by the employer's corporate server and delivered through Google's infrastructure.
Where the FCM token is sent:
- To the employer's corporate server so it knows which device to notify for a given user.
- To Google servers (
fcm.googleapis.com,firebaseinstallations.googleapis.com) — unavoidable, since FCM is a Google service. Google acts as a processor routing notifications; the payload contents transit Google's infrastructure.
Data NOT transmitted via FCM:
- Location data, photos, recipient signatures, payment credentials — are not delivered in push notifications. The notification contains only a document identifier and a short message; the full content is fetched by the App directly from the corporate server.
- Analytics of user behaviour — are not collected or sent to Google or anyone else (Firebase Analytics is not integrated).
Retention:
- The FCM token on the employer side is retained until the user logs out, uninstalls the App, or explicitly de-registers. On logout the App sends an
unregister_fcm_tokenrequest to stop further delivery. - On Google's side tokens are managed per Firebase Cloud Messaging policy.
Jurisdiction:
Firebase Cloud Messaging servers may be located in multiple countries (including the United States and the EU) as part of Google's infrastructure. Transmission to these servers is a necessary condition for push notifications to work; opting out while keeping the feature is technically not possible. The user may disable notifications in Android system settings — that stops their delivery, though the FCM token itself may continue to exist until the App is uninstalled.
Google Privacy Policy:
https://policies.google.com/privacy
Firebase Terms of Service:
https://firebase.google.com/terms
05 Full list of Android permissions used
| Permission | Purpose | Required |
|---|---|---|
ACCESS_FINE_LOCATION | Precise GPS coordinates for route tracking | Yes |
ACCESS_COARSE_LOCATION | Fallback approximate location | Yes |
ACCESS_BACKGROUND_LOCATION | Collection while App is minimized / closed during working hours | Yes |
FOREGROUND_SERVICE | Running a foreground location service with persistent notification | Yes |
FOREGROUND_SERVICE_LOCATION | Foreground service type — location (Android 14+) | Yes |
CAMERA | Capturing merchandising photos | Yes |
INTERNET, ACCESS_NETWORK_STATE | Transmitting data to the corporate server | Yes |
POST_NOTIFICATIONS | Notifications for background work, sync, and FCM push messages | Yes |
WAKE_LOCK | Keeping the device awake during synchronization | Yes |
RECEIVE_BOOT_COMPLETED | Auto-starting the location service after device reboot | Yes |
06 Sharing data with third parties
Full list of data recipients:
| Recipient | Data | Purpose | When |
|---|---|---|---|
| Employer's corporate server | All collected business data, GPS, photos, recipient signatures | Storage, processing, reporting | Continuously when internet is available |
Developer's license server (license.saraf.uz) | Device UUID, hardware fingerprint, license token | License anti-piracy enforcement, device binding | On license activation and periodic checks |
| Google Play Services Location | Coordinate request | Obtaining coordinates from the GPS receiver | While the location service is running |
| Google Maps | Destination coordinate | Building a route to a client | Only when the user explicitly chooses |
| Yandex Maps / Yandex Navigator | Destination coordinate | Building a route to a client | Only when the user explicitly chooses |
Google Firebase Cloud Messaging (fcm.googleapis.com, firebaseinstallations.googleapis.com) | FCM device token, Firebase Installations ID, notification payload (document id, title, body) | Routing push notifications from the corporate server to the device | Continuously in the background while the App is installed and notifications permission has not been revoked |
The App DOES NOT share data with:
- advertising networks and targeting platforms;
- third-party analytics SDKs (Firebase Analytics, Yandex AppMetrica, Facebook SDK, etc. — note that of the entire Firebase suite only Cloud Messaging is used, see §4.9);
- data brokers;
- social networks;
- any third parties for commercial purposes.
07 Data storage and security
7.1. Local storage
- Data is stored in a Room database within the App's private internal storage, accessible only to the App (Android sandbox).
- The password is stored encrypted using the Android Keystore.
- All local data is removed when the App is uninstalled.
7.2. Network transmission
- All data is transmitted to the corporate server over network channels configured by the employer (HTTPS recommended).
- Debug builds may have an option to use plain HTTP — used only during testing in isolated corporate networks.
7.3. Server-side storage
- Server-side retention periods are determined by the employer as the data controller.
- Server storage security is the responsibility of the employer.
08 User rights
Subject to applicable data protection law (including the Law of the Republic of Uzbekistan "On Personal Data," Federal Law No. 152-FZ of the Russian Federation, and GDPR where applicable) the user has the right to:
- Request access to their personal data;
- Request correction of inaccurate data;
- Request deletion of data upon termination of employment;
- Withdraw consent for processing (which makes further use of the App impossible);
- Lodge a complaint with the supervisory authority;
- Disable location permission in Android settings at any time.
Requests should be directed to the employer as the data controller. The controller's contact details are provided by the employer.
09 Account and data deletion
Because the App is a corporate tool and accounts are issued by the employer:
- To delete an account, contact the employer (the data controller).
- To delete locally cached data, uninstall the App or clear its data via Android system settings (Settings → Apps → Saraf Sales → Storage → Clear data).
- To delete server-side data, contact the employer.
10 Children
The App is not intended for individuals under 18. Accounts are issued only to employed staff of the employer. The App does not knowingly collect data relating to children.
11 Changes to this Policy
For material changes, the effective date and document version are updated. The current version of this Policy is always available at:
Continued use of the App after changes constitutes acceptance of the updated Policy.
12 Developer contact
Mirico Systems LLC
- Email: privacy@saraf.uz
- Website: https://saraf.uz
- Address: 18 Ko'shbegi Street, Yakkasaray District, Tashkent
For questions about the processing of a specific employee's personal data, please contact the employer (the data controller).
This Privacy Policy describes what data the Saraf POS Android application (the "App") collects, how it is used, shared, stored, and protected. The App is a mobile cash-register terminal for the Saraf POS cloud service (pos.saraf.uz): a point-of-sale workplace for businesses. By using the App you confirm that you have read this Policy and agree to its terms.
Short summary (TL;DR)
| Data category | Collected | Where processed | Purpose |
|---|---|---|---|
| Account credentials (email, password) | Yes | Saraf servers only (my.saraf.uz, pos.saraf.uz) | Organization owner / administrator sign-in; the password is not stored |
| Cashier PIN | Yes | Verified on the server; not stored on the device | Cashier sign-in on the terminal |
| Biometrics (fingerprint, face) | No | Android OS on the device only | Optional App unlock |
| Organization business data (products, prices, receipts, shifts) | Yes | Saraf POS cloud (pos.saraf.uz) | Point-of-sale operation and reporting |
| Camera frames | No | Recognized on-device (ML Kit); frames are not stored | Scanning barcodes and marking codes |
| Terminal binding token | Yes | Encrypted storage on the device | Binding the device as the organization's cash register |
| Server logs (IP address, request time) | Yes | Saraf servers | Security and diagnostics |
| Customers' personal data | No | — | Not collected in the current version |
The App contains no advertising or ad SDKs, uses no third-party analytics SDKs, does not share data with data brokers, and does not sell data. The only transfer outside the Saraf infrastructure is the legally required fiscalization of receipts via a fiscal data operator (OFD), and only if the organization has enabled fiscal mode (see section 6).
01 Camera and code scanning
The camera is used only as a scanner. Frames are not stored and are not transmitted anywhere.
1.1. What the camera is used for
The App uses the device camera (CAMERA permission) exclusively for:
- scanning product barcodes at the time of sale;
- scanning DataMatrix marking codes when a product is subject to mandatory digital marking.
1.2. How camera frames are processed
- Code recognition happens entirely on the device using the Google ML Kit library (on-device).
- Camera frames are not stored — neither in the App's internal storage nor in the device photo gallery.
- Images are not transmitted to Saraf servers or to any third parties; only the recognized code value (barcode or marking code) is sent to the server as part of the receipt.
1.3. Consent and working without the camera
- The
CAMERApermission is requested when the scanner is first opened, not at App startup. - Without this permission the point of sale keeps working: products can be added to a receipt manually via catalog search or with an external barcode scanner.
- The permission can be revoked at any time in Android settings.
02 Purpose of the App
Saraf POS is a "mobile cash register" Android application: a point-of-sale workplace for businesses — selling goods, issuing receipts, managing cash shifts. The App is a client of the Saraf POS cloud service (pos.saraf.uz) and is intended exclusively for business use by employees of a client organization (owner, administrator, cashier); it is not intended for personal use.
Core features:
- selling goods and issuing receipts;
- accepting payments and calculating change;
- scanning barcodes and marking codes;
- printing receipts to a network printer;
- opening and closing cash shifts, shift reports;
- viewing and reprinting receipts of the current shift.
03 Data Controller
The controller of the business data processed in the App is the client organization — the owner of a my.saraf.uz account who subscribed to the Saraf POS service and granted its employees access to the point of sale. The organization defines the catalog contents, the list of employees, and the purposes of processing its data.
The App developer and cloud service operator (Mirico Systems LLC) processes the organization's data on its behalf — storing it and keeping the point of sale and reporting running. The developer does not use organizations' data for its own purposes, does not use it for advertising, and does not share it with third parties except as described in section 6.
04 Full list of collected data
4.1. Account credentials
- my.saraf.uz account email and password — used by the owner or an administrator to sign in. Transmitted only to Saraf servers (
my.saraf.uz,pos.saraf.uz) over a secure HTTPS/TLS connection. The password is not stored by the App. - Session tokens — issued by the server after sign-in and kept on the device in encrypted storage (Android Keystore / EncryptedSharedPreferences); they enable "remembered sign-in."
4.2. Cashier PIN
A cashier signs in to the point of sale with a 4-digit PIN issued by the organization. The PIN is sent to the server over a secure connection for verification and is not stored on the device.
4.3. Biometric data
Optional App unlock by fingerprint or face is performed by the Android system mechanism (BiometricPrompt). Biometric data is processed only by the operating system on the device: it is not accessible to the App or to Saraf servers and is never transmitted anywhere. The feature can be enabled or disabled in the App settings at any time.
4.4. Organization business data
The App processes the client organization's data:
- product catalog, prices, and stock levels;
- receipts and sales amounts;
- cash shifts and shift reports;
- names of the organization's employees (for point-of-sale sign-in and cashier attribution on receipts).
This data belongs to the client organization, is stored in the Saraf POS cloud (server pos.saraf.uz), and is processed on behalf of the organization's owner to operate the point of sale and reporting. The App does not collect customers' personal data in its current version.
4.5. Receipt printing and the local network
- To print receipts the App connects to a network ESC/POS printer over TCP. The printer address is set by the user in the App settings.
- Only the data of the receipt being printed is sent to the printer; the transfer happens within the local network and does not leave it.
4.6. Technical data
- Terminal binding token — a random identifier that binds the device to the organization as a cash register; kept in the device's encrypted storage.
- Standard server logs (IP address, request timestamps) — kept on Saraf servers and used for security and diagnostics.
05 Full list of Android permissions used
| Permission | Purpose | Required |
|---|---|---|
INTERNET | Communication with the Saraf POS cloud service | Yes |
CAMERA | Scanning barcodes and marking codes | No — requested on first use of the scanner; the point of sale works without it |
VIBRATE | Vibration feedback on scanning | Yes (granted automatically by the system) |
The App does not request access to location, contacts, microphone, SMS, files, or the device photo gallery.
06 Sharing data with third parties
Organization and user data is not shared with third parties, with one exception:
- Fiscal data operator (OFD) — if the organization has enabled fiscal mode, receipt data is transmitted to the fiscal data operator (
ofd.soliq.uz) to the extent and in the manner required by the legislation of the Republic of Uzbekistan on fiscalization of payments.
The App DOES NOT share data with:
- advertising networks and targeting platforms;
- third-party analytics SDKs;
- data brokers;
- social networks;
- any third parties for commercial purposes.
The App contains no advertising or ad SDKs; user and organization data is not sold.
07 Data storage and security
7.1. On the device
- Session tokens and the terminal binding token are kept in encrypted storage (Android Keystore / EncryptedSharedPreferences).
- The password and PIN are not stored on the device.
- When the App is uninstalled, all of its local data is removed.
7.2. Network transmission
- All connections to Saraf servers use the secure HTTPS (TLS) protocol.
- Receipt printing happens only within the local network (see section 4.5).
7.3. In the cloud
- Organization data is stored on Saraf servers — the same protected infrastructure that runs the other Saraf services.
- Access to organization data is segregated by employee role (owner, administrator, cashier).
- The business data retention period is determined by the organization's owner; data is deleted upon the owner's request (see section 9).
08 User rights
Subject to applicable data protection law (including the Law of the Republic of Uzbekistan "On Personal Data," Federal Law No. 152-FZ of the Russian Federation, and GDPR where applicable) the user has the right to:
- Request access to their personal data;
- Request correction of inaccurate data;
- Request deletion of data;
- Withdraw consent for processing (which makes further use of the App impossible);
- Lodge a complaint with the supervisory authority.
Requests concerning your organization's data (catalog, receipts, employees) should be directed to the organization's owner — the data controller. Questions for the developer and cloud service operator — privacy@saraf.uz.
09 Account and data deletion
The App uses a my.saraf.uz account; the organization's data is managed by its owner:
- To delete the my.saraf.uz account and the organization's data (catalog, receipts, shifts, employees), the organization's owner sends a request to the developer at privacy@saraf.uz.
- For an employee (cashier, administrator): point-of-sale access is revoked by the organization's owner or administrator; for questions about your data, contact your employer organization.
- To delete local data from the device, uninstall the App or clear its data via Android system settings (Settings → Apps → Saraf POS → Storage → Clear data).
10 Children
The App is not intended for individuals under 18. Point-of-sale access is granted only to employees of the client organization. The App does not knowingly collect data relating to children.
11 Changes to this Policy
For material changes, the effective date and document version are updated. The current version of this Policy is always available at:
https://saraf.uz/privacy#saraf-pos
Continued use of the App after changes constitutes acceptance of the updated Policy.
12 Developer contact
Mirico Systems LLC
- Email: privacy@saraf.uz
- Website: https://saraf.uz
- Address: 18 Ko'shbegi Street, Yakkasaray District, Tashkent
For questions about the processing of your organization's data, please contact the organization's owner (the data controller).
This Privacy Policy describes what data the Saraf Manager Android application (the "App") collects, how it is used, shared, stored, and protected. The App is the owner's and administrator's dashboard for the Saraf POS cloud service (pos.saraf.uz): reports, stock levels, and inventory documents of an organization. The App does not process sales and does not print receipts. By using the App you confirm that you have read this Policy and agree to its terms.
Short summary (TL;DR)
| Data category | Collected | Where processed | Purpose |
|---|---|---|---|
| Account credentials (email, password) | Yes | Saraf servers only (my.saraf.uz, pos.saraf.uz) | Owner / administrator sign-in; the password is not stored on the device |
| Session cookies | Yes | Encrypted storage on the device | "Remembered sign-in" without re-entering the password |
| Biometrics (fingerprint, face) | No | Android OS on the device only | Optional App unlock |
| Organization business data (reports, products, stock, receipts, shifts, employees) | Yes | Saraf POS cloud (pos.saraf.uz) | Viewing reports and managing the organization's inventory |
| Server logs (IP address, request time) | Yes | Saraf servers | Security and diagnostics |
| Location, contacts, camera | No | — | Permissions are not requested |
| Customers' personal data | No | — | Not collected in the current version |
The App contains no ads or advertising SDKs, uses no third-party analytics SDKs, does not share data with data brokers, and does not sell data. All network requests go exclusively to Saraf servers over HTTPS.
1. Purpose of the App
Saraf Manager is a working tool for the owner, administrator, and store manager of an organization that uses the Saraf POS register: a sales dashboard, reports (profit, P&L, ABC, shifts, receipts), stock levels, inventory documents (goods receipt, write-off, transfer), employee management, and license overview. The App only works with the data of organizations you have access to and mirrors the permissions assigned by the owner in the back office: a store manager sees only their own store.
2. Data Controller
Business data (products, receipts, shifts, employees, reports) belongs to the organization; the controller of this data is the organization's owner. Mirico Systems LLC processes it as a processor on the organization's behalf as part of the Saraf POS service. The my.saraf.uz account is processed by Mirico Systems LLC as a controller.
3. Collected data
- Account credentials: the email and password are sent to my.saraf.uz only at sign-in (plus a verification code if two-factor protection is enabled). The password is not stored on the device; the session is kept as a cookie in encrypted storage.
- Employee profile: name, role, email, assigned store — fetched from the server and cached on the device for fast startup.
- Organization business data: reports, products, stock, documents, receipts, shifts, employees, license status — loaded from Saraf servers on demand and not permanently stored on the device.
- Technical data: server logs (IP address, request time and path) — for security and diagnostics.
4. Android permissions
The App requests a single permission — INTERNET (HTTPS communication with Saraf servers). Optional biometric unlock uses the Android system dialog: biometric data is processed by the operating system only and is never available to the App. Camera, location, contacts, microphone, files — not requested.
5. Sharing with third parties
The App does not share data with third parties. All requests go exclusively to the Saraf infrastructure (my.saraf.uz, pos.saraf.uz). The App contains no advertising or analytics SDKs; data is not sold or shared with data brokers. The subscription renewal button opens the my.saraf.uz dashboard in the browser — payment happens outside the App.
6. Storage and security
- On the device: session cookies and the profile cache are kept in encrypted storage (Android Keystore, AES-256); they are removed on sign-out or when the App is uninstalled.
- On the servers: organization data is stored in the Saraf infrastructure data center; access is segregated per organization and per store (a store manager cannot access another store's data — enforced server-side).
- Transport: HTTPS (TLS) only; passwords are stored server-side as irreversible hashes.
7. User rights
You may request access to your personal data, its correction or deletion, and withdraw consent to processing — via the organization's owner (the controller of business data) or directly at privacy@saraf.uz (account data). Biometric unlock and "remembered sign-in" can be disabled in the App itself.
8. Account deletion
The my.saraf.uz account is deleted upon request to privacy@saraf.uz sent from the account's registered email address. An employee's access to the App is revoked by the organization's owner in the back office (clearing the email or deactivating the employee) — instantly. The App's local data is removed on sign-out or when the App is uninstalled.
9. Children
The App is a business tool not intended for persons under 18. We do not knowingly collect children's data.
10. Changes
The current version of the Policy is published on this page with its effective date. We will announce material changes in the App or by email.
11. Contact
Mirico Systems LLC
- Email: privacy@saraf.uz
- Website: https://saraf.uz
- Address: 18 Ko'shbegi Street, Yakkasaray District, Tashkent
For questions about the processing of your organization's data, please contact the organization's owner (the data controller).