This is the English translation of the Turkish privacy notice (gizlilik-politikasi.md), prepared under Turkish Law No. 6698 on the Protection of Personal Data ("KVKK"). In case of any discrepancy, the Turkish version prevails.
0. Who is this app for?
Develi Gross is not a consumer shopping app. It is an internal business application used by Develi Gross employees and its business partners (supplier company representatives, field sales reps, etc.) to carry out company work processes.
- Accounts cannot be created inside the app. Accounts are created only by a company administrator when an employment or business relationship begins.
- A person who downloads the app but has no relationship with Develi Gross cannot sign in, and no personal data about them is processed — apart from the security record described under "Sign-in attempt logs" below.
- The app is a shell that displays the company's live business panel (
https://api.develigrossapps.com). Which screens a user can see depends on the permissions the company has assigned to that user. Develi Gross Saha Satış is a native app used only by the field sales representatives the company has assigned to it; it gets its data from the same server (see 2.10).
1. Data controller
| Legal name | DeveliGross Toptan ve Perakende-Selahattin Kolsuz |
| Address | İbrahim Ağa Mah. İnönü Cad. No:1, 38400 Develi/Kayseri |
| Tax office / number | DEVELİ / 16976432592 |
| MERSIS number | 1697643259200001 |
| Registered e-mail (KEP) | selahattin.kolsuz@hs01.kep.tr |
| develigross@gmail.com | |
| Phone | 0352 606 05 18 |
2. What we collect and why
The table below reflects the actual fields in the source code. Modules you do not have access to do not process data about you.
2.1. Identity and account data
| Data | Where | Why |
|---|---|---|
| Turkish national ID number (TCKN) | In the personnel/HR record the company keeps as employer | Payroll, social security and labour-law obligations; matching the self-service HR screens (leave, timesheet, payslip, shifts) to your own record. The Develi Gross Çalışan and Develi Gross Supplier apps never ask for your TCKN at sign-in. |
| Mobile phone number (Develi Gross Çalışan app) | You type it at sign-in; it is matched against the company's personnel record | Finding your account without showing a user list, and sending the sign-in code to your registered number (see 2.2.1) |
| Full name | Account record, on-screen display, work records | Authorisation and audit |
| Internal user ID | Account record | Linking records |
| Password | Only an irreversible cryptographic hash (scrypt) is stored — never the password itself | Authentication |
| Job role, assigned branch, permission template | Account record | Determining access rights |
Important: In Develi Gross Çalışan you sign in with your mobile number, and in Develi Gross Supplier with your username. The national ID number is not requested at sign-in, is not written to the sign-in logs and is not stored on your phone.
2.2. Sign-in, session and security data
| Data | Why |
|---|---|
| Sign-in attempt log: timestamp, success/failure, failure reason, user, IP address, country code, platform (ios/android/pc), device name, user agent | Detecting unauthorised access, account security, audit trail |
| Failed-password counter and account lock status (last attempt IP and time) | Brute-force protection |
| Active session: session ID, device/machine name, sign-in time, last seen | Preventing account misuse, enabling "sign out of all devices" |
| Blocked IP address list | Blocking attacking IPs |
| If a WhatsApp/SMS one-time code (OTP) is used: mobile phone number — in Develi Gross Çalışan you type your number at sign-in and the code is sent only if it matches the number in the company's personnel record (to that registered number); in the older Staff / Manager apps the number is taken from the personnel record and you do not enter it — hash and expiry of the generated code, and for "remember this device" a device ID with a 30-day validity record | Two-factor authentication and phone sign-in (see 2.2.1) |
Sign-in attempt logs are automatically deleted after 30 days (server setting RETENTION_GUN, default 30).
2.2.1. Phone sign-in and recognised device (Develi Gross Çalışan and Develi Gross Saha Satış apps)
The Develi Gross Çalışan and Develi Gross Saha Satış apps never show a list of users. Only field sales representatives assigned by the company can sign in to Saha Satış; no Saha sign-in code is sent to a number that is not assigned. You sign in as follows:
- Phone + one-time code: you enter your mobile number. If it belongs to an employee in the company's personnel records, a 6-digit code is sent only to that registered number via WhatsApp, or by SMS (NetGSM) if WhatsApp is unavailable. The code is valid for 3 minutes and can be used once. The screen shows the same answer whether or not the number is registered.
- Phone + password: you can also sign in with your number and the password issued by the company.
- Manager accounts: on a new device both the password and a code sent to the registered number are required.
- Recognised device: after a successful sign-in the server gives your device a random device key. The key itself stays on your device; the server keeps only its irreversible hash (SHA-256), issue date, last use, device name/platform, and your own name with a masked number. On later launches the screen shows only your name and masked number and asks for your password. "Sign in with another account" deletes the key from the device and revokes it on the server; "sign out of all devices" revokes it too.
- Records: for every code request we store only a masked form and an irreversible keyed hash (HMAC) of the number, the IP address, delivery channel and attempt count; the code itself is never stored (only its hash, for 3 minutes). These records limit abuse (SMS flooding, code guessing) and are deleted after 30 days.
- When employment ends: access is closed. On a recognised device the app shows a "you are no longer Develi Gross staff" screen and clears business data from the device; unsent work records are kept for delivery to headquarters. If you are re-employed, access reopens automatically. This message is shown only to an authenticated person (valid session, device key, correct code or password).
2.2.2. Biometric sign-in — Face ID / Touch ID / fingerprint (Develi Gross Çalışan, Develi Gross Saha Satış and Develi Gross Supplier)
After your first password sign-in the app asks whether you want to sign in on this device with Face ID, Touch ID or Android fingerprint / face unlock. This is optional; if you do not turn it on you keep signing in with your password, and you can turn it off at any time.
- Your biometric data never leaves your device. Face or fingerprint matching is performed by your phone's operating system. The app and our servers never see, receive or store your face image, fingerprint or any template of them; the app only receives a "verified / not verified" result.
- When you turn biometric sign-in on, a random biometric sign-in key is generated. The key itself is kept only in your phone's secure store (iOS Keychain / Android Keystore) and can only be unlocked by biometric verification; it becomes invalid if a new face or fingerprint is enrolled on the device.
- Next to your recognised-device record the server keeps only an irreversible hash (SHA-256) of that key, the time biometric sign-in was turned on, the number of consecutive failed attempts (after 5 failures biometric sign-in is switched off on that device) and the time of your last password sign-in on that device. Manager and supplier accounts must re-enter the password every 30 days.
- The server-side hash is deleted when you turn biometric sign-in off, choose "sign in with another account", when the device key is revoked, or when your employment (or supplier account) is closed.
2.3. Device and notification data
| Data | Why |
|---|---|
| App-generated device identifier (a random UUID — not an advertising identifier) | Recognising the device, delivering notifications, session security |
| Device name, operating system (ios/android), app version, last-seen time | Support, version tracking, notification targeting |
| Push notification token (Expo Push Token; on Android backed by a Firebase Cloud Messaging registration) | Delivering work notifications |
| Notification delivery log (title, message, status) | Tracking whether a notification was delivered — deleted after 30 days |
Notification permission is optional. If you decline it, no push token is generated and nothing is sent to the server. On Android, notifications are delivered via Google Firebase Cloud Messaging (FCM). Firebase is used only to deliver notifications; Firebase Analytics, Crashlytics and advertising services are not used.
2.4. Location data
| Data | Why |
|---|---|
| Latitude, longitude, accuracy (metres) — current location only | (1) Verifying that a clock-in/clock-out (attendance) stamp was made from within the workplace geofence; (2) automatically selecting the branch you work at on screens (stock count, labels, transfers, returns, order receiving); (3) verifying that an end-of-day cash entry and a price-label confirmation were made at the branch; (4) only for authorised managers and only while the related screen is open: vehicle location on the delivery-route screen (about every 5 minutes), field-sales visit location, "use my location" when defining a branch location |
| Branch name of the stamp, distance to branch (metres), inside-geofence flag, stamp type (in/out/break), timestamp, device info | Attendance and working-time records |
Location in Develi Gross Saha Satış (details in 2.10): when you start and finish a customer visit, your current location is sent to the server and stored with your visit record (your manager can see it); a customer's business location is saved with "Konumu Gir" (Set location) or on the first visit; while a visit is open and the app is in the foreground, your location is checked on the device only every 45 seconds, and when you move about 150 m away from the customer the visit is closed automatically and that location is sent as the visit's end location.
Location rules:
- In Develi Gross Çalışan, before location is read for the first time, an in-app notice explaining these purposes is shown; your phone then shows its own location permission prompt. If you choose "Vazgeç" (Cancel) in the notice, your location is not read. Develi Gross Saha Satış likewise shows its own notice explaining its purposes before reading location for the first time.
- Location is read only at the moment you perform an action or open the related screen (exceptions: while the delivery-route screen stays open, about every 5 minutes; in Saha Satış, while a visit is open and the app is in the foreground, every 45 seconds, on the device only). Location sent for branch detection is not stored in the database; location is stored only in attendance stamps, end-of-day entries, label confirmations, delivery routes and field-sales visit records.
- Location is not collected in the background and there is no continuous tracking. Your location is not monitored while the app is closed or in the background.
- If you decline location permission, the rest of the app keeps working; location-verified attendance stamping is unavailable (a branch QR code can be used instead) and the branch is selected manually on screens.
- This data is never shared with third parties or sold, and never used for advertising, profiling or marketing.
2.5. Camera and microphone
| Permission | Purpose | Does data leave the device? |
|---|---|---|
| Camera | Scanning product barcodes (stock count, goods receipt, labels, expiry-date entry) and, where needed, photographing a document/receipt | For barcode scanning, no — frames are processed on-device and only the decoded barcode number is used. If you upload a document/receipt photo, yes, that file is sent to the server. |
| Camera (Develi Gross Saha Satış) | Scanning product barcodes; taking a shelf/display photo and a photo of the customer's signature during a customer visit | Barcodes: no. Shelf and signature photos: yes — stored on the server with the visit record (see 2.10). |
| Microphone | In-branch push-to-talk radio feature (only for users who use it). Develi Gross Saha Satış does not use the microphone. | Audio is transmitted to other users on the channel while you hold the button. Conversations are not recorded; audio is relayed live only and is not stored on the server or the device. |
| Bluetooth (Android only, Develi Gross Saha Satış) | Printing a receipt on a Bluetooth receipt printer you have paired | The receipt content goes only to the printer; no additional data is sent to the server. |
2.6. HR data (only for employees using HR modules)
Through the HR modules the company, acting as employer, may process: attendance records, timesheets and shift plans, leave requests and balances, assigned equipment, announcement read receipts, survey answers, suggestions/complaints, performance evaluations and disciplinary records, and personnel file documents.
Special categories of personal data: Personnel documents may include health reports, disability reports or criminal record certificates. These are special categories under Article 6 of KVKK and are processed only to meet obligations arising from employment, occupational health and safety, and social security legislation, by a limited set of authorised staff. Every download and deletion is separately logged (who, when, from which IP).
Payroll and pay data: Payslip/salary information, advance and bonus payments, wage garnishments (enforcement deductions) and OKS/BES (private pension) deductions are processed. Each employee sees only their own payslips and deductions; bulk payroll, garnishment and pension operations are carried out only by authorised HR/accounting staff. This data is processed to perform the employment contract and to meet tax, social security and enforcement obligations; it is never shared with third parties for marketing.
Work files uploaded by authorised users: Authorised users may upload business documents as part of their job: receipt/invoice and bank statement PDFs, fault and end-of-day photos, advertising videos for the checkout customer display, and music files for the in-store radio. These files are business records and are not expected to contain personal data; if they do, they are processed only for the related business purpose by authorised staff.
2.7. Offline data stored on your device
(For the offline copy and offline sign-in of Develi Gross Saha Satış, see 2.10.)
The Develi Gross Çalışan and Develi Gross Supplier apps have no offline sign-in. These two apps keep no password hash, user/staff list or offline business data on the device; only the session token, the recognised-device key, the biometric sign-in key (if you turned it on — see 2.2.2), the push token and your display preferences are stored. The rest of this section applies only to the older Staff / Manager / Terminal apps.
So these older apps can work without internet, some data is kept on your phone:
- In the device secure store (iOS Keychain / Android Keystore): session token (JWT), device ID, your name and user number, assigned branch, theme preference, push token, offline sign-in PIN.
- Offline sign-in password hash: Your password itself is never stored. Only a salted, 2,000-iteration SHA-256 derivation is written to the secure store and used to verify you when there is no internet. The offline window is 30 days; if you do not sign in online for 30 days, offline sign-in closes.
- In a local database (app-local SQLite, protected by the device's own encryption): product catalogue, stock mirror, stock-count tasks assigned to you and the lines you scanned, goods-receipt / branch-request / expiry-date records, a queue of operations waiting to be uploaded, customer list.
When is this deleted?
- When you uninstall the app.
- When your relationship with the company ends: on the next online request the server closes your account; the app first delivers any unsent work records to head office, then deletes your document and personal data from the device and destroys the offline password hash. (Non-personal data such as the product catalogue may remain.)
2.8. Audit trails
When you create, update or delete records in the panel, the acting user's ID and name, the timestamp and — in some modules — the IP address are recorded, to meet legal obligations and to establish or defend legal claims.
2.9. Supplier portal users (Develi Gross Supplier app)
The Supplier app is for representatives of companies that supply products to Develi Gross. Accounts are opened only by Develi Gross when a business relationship is established; accounts cannot be created in the app.
| Data | Why |
|---|---|
| Username, the company (customer/supplier account) it belongs to, permitted screens and branches | Defining the account and its access scope |
| Password — never the password itself, only an irreversible hash (scrypt) | Authentication |
| Mobile number (if defined) and the hash of the SMS verification code (3 minutes) | Two-factor authentication (NetGSM SMS) |
| "Remember this device" record (hash of a random key, device name) | Not asking for an SMS code for 30 days |
| Sign-in/sign-out records: timestamp, success, IP address, user agent | Account security and audit trail |
| Push token and device information | Notifying you when an order is placed with your company. The device is removed from the notification list when you sign out, or when your account is deactivated or deleted |
| Order requests and consignment delivery/waste records you create | Running the commercial process |
You only see your own company's data (orders placed with your company, sales and stock of your products, and — if enabled — your account statement). Repeated failed sign-in attempts in a short time are temporarily blocked. You can request account closure or deletion via the Account deletion page or at develigross@gmail.com; commercial records (orders, invoices) are retained for the statutory period (10 years under Turkish commercial and tax law).
2.10. Develi Gross Saha Satış (tr.com.develigross.saha) — field sales representatives
Saha Satış is used by the field sales representatives the company has assigned to it, to handle customer visits, orders, collection records and returns. Sign-in works as described in 2.2.1 and 2.2.2 (phone + code/password, recognised device, optional biometrics). A representative sees only the customers assigned to them.
Data about you (the representative)
| Data | Why |
|---|---|
| Visit record: customer, start and end time, start and end location (latitude/longitude), outcome (order/collection/return), visit note, skip reason | Running the field-sales process and verifying the visit took place at the customer; visible to your manager |
| 45-second location check during an open visit | Automatically ending the visit when you move ~150 m away from the customer. These readings stay on the device and are not sent to the server; only on automatic ending is that location sent as the end location. It does not run while the app is in the background |
| Orders, collection records (amount, payment type, cash/bank account), returns and receipts you create | Recording the commercial transaction. A collection is only a record; the app moves no money and takes no card or payment details |
| Monthly target and actuals (visits, sales, collections) | Performance tracking |
Data about customers (third parties)
| Data | Source and purpose |
|---|---|
| Customer (business) name, customer code, phone and e-mail, account balance, credit limit, account statement, purchase history | Comes from the company's accounting/ERP records; used for orders, collections and customer follow-up. The representative can only correct the phone and e-mail; corrections are written to the company's records |
| Customer's business location | Saved with "Konumu Gir" or on the first visit; used for directions and visit verification |
| Shelf/display photo and a photo of the customer's signature | Documenting the visit and delivery. Stored on the server with unguessable file names; only the representative and authorised field-sales managers can view them, via a time-limited signed link |
Customer data is processed to perform the commercial relationship with the customer (KVKK Art. 5/2-c) and for the company's legitimate interests (Art. 5/2-f); where the customer is a natural person (e.g. a sole trader) this information is personal data and is protected in the same way. It is never sold or used for advertising.
Offline copy on your device
So it can work without internet, Saha Satış keeps in the app's database on your phone: the product catalogue (prices and stock quantities), the list of customers assigned to you (name, code, balance, credit limit), customer locations, routes, targets and campaigns, cash/bank account names, and visits, orders, collections, returns and photos created on the device that have not yet been uploaded. The copy is refreshed on each online sync; uploaded records leave the queue.
- Offline sign-in is possible only for the person who last signed in on this device, and only with biometric verification; neither your password nor a hash of it is written to the device. Offline sign-in closes 7 days after your last online sign-in.
- When you choose "sign in with another account", pending records are uploaded first (if they cannot be, the action is blocked); then the customer, route, location and catalogue copy is deleted from the device.
- When your working relationship ends and your access is closed, on the first online launch the app delivers any unsent records to head office, then deletes the customer copy, documents and queue from the device; the recognised-device and biometric sign-in keys are deleted too.
- Uninstalling the app deletes all Saha data on the device.
3. What we do NOT collect
For the avoidance of doubt, the app:
- Does not collect advertising identifiers (IDFA / GAID).
- Contains no advertising, analytics (Google Analytics, Firebase Analytics, Facebook SDK, etc.) or crash-reporting third-party SDKs.
- Does not sell personal data and does not share it for advertising.
- Does not access your contacts, SMS messages, call history or photo library without your action and permission.
- Uses no cookies of its own. Session data is kept in the device secure store and in the in-app web view's local storage; there are no advertising or tracking cookies.
- Does not track users across apps or websites.
- Does not collect biometric data (face images, fingerprints or their templates); Face ID / Touch ID / fingerprint verification happens entirely on your phone (see 2.2.2).
- Does not collect location in the background (see 2.4).
4. Legal bases (KVKK Art. 5)
| Processing activity | Legal basis (KVKK Art. 5/2) |
|---|---|
| Account creation, authentication, running business processes | (c) Directly related to the conclusion or performance of a contract (employment / commercial contract) |
| Attendance (clock-in/out), timesheets, working-time tracking | (a) Expressly provided for by law and (ç) compliance with a legal obligation (Labour Law No. 4857, Law No. 5510, Law No. 6331) |
| Branch detection by location; verifying on-site end-of-day, label confirmation, delivery and field-sales visits | (f) Legitimate interests (running work processes at the correct branch; the in-app notice and the device location permission are obtained separately) |
| Saha Satış: customer (third-party) data, order/collection/return records, visit and signature photos | (c) Conclusion and performance of the commercial contract with the customer; (f) legitimate interests (documenting the sales process) |
| Biometric sign-in (optional) | No biometric data is processed (verification happens on the device); for the server-side key hash, (f) legitimate interests — information security |
| Personnel file and document retention | (ç) Compliance with a legal obligation |
| Sign-in logs, IP records, account lockout, session management, device registration | (f) Legitimate interests of the controller (information security, prevention of unauthorised access) |
| Audit trails, disciplinary and dispute records | (e) Establishment, exercise or protection of a right |
| Push notifications | (f) Legitimate interests — running the workflow (device notification permission is also obtained) |
| Health reports and similar special-category documents | KVKK Art. 6/3 — obligations under employment, occupational health and safety, and social security law; otherwise explicit consent |
(For EU/UK readers: the app is not directed at the EU/UK market and is distributed for use in Türkiye. Where GDPR nevertheless applies, the equivalent bases are Art. 6(1)(b) contract, (c) legal obligation and (f) legitimate interests, with Art. 9(2)(b) for health-related employment documents.)
5. Retention periods
| Data | Period |
|---|---|
| Sign-in attempt logs | 30 days (automatic deletion) |
| Notification delivery logs | 30 days (automatic deletion) |
| Active session record | Until the session ends |
| SMS/OTP code | 3 minutes |
| Phone sign-in request record (masked + hashed number, IP, attempt count) | 30 days (automatic deletion) |
| Hash of the recognised-device key | Until revoked ("sign in with another account" / "sign out of all devices"); deleted 30 days after revocation |
| Hash of the biometric sign-in key (SHA-256) | Until biometric sign-in is turned off, the device key is revoked or the account is closed; then deleted immediately |
| "Remember this device" record | 30 days |
| Offline sign-in hash on the device | Max. 30 days; deleted immediately when the working relationship ends |
| Session token (JWT) | Web/desktop 24 hours, mobile 30 days, branch terminal open-ended (revoked via device approval) |
| Account and permission records | For the duration of the relationship plus 5 years (labour-law limitation period) |
| Attendance, timesheet, leave records | 10 years (social security and labour law) |
| Personnel documents | 10 years after the relationship ends |
| Accounting / commercial records | 10 years (Tax Procedure Law No. 213, Commercial Code No. 6102) |
| Saha Satış orders, collection records and returns | Commercial records: 10 years (Tax Procedure Law / Commercial Code) |
| Saha Satış visit records (including location) and visit/signature photos | Kept as business records for the duration of the customer relationship and the representative's working relationship; deletion can be requested as described in section 9 |
| Saha Satış offline copy on the device | Refreshed on each sync; deleted when the account changes, when access is closed or when the app is uninstalled |
At the end of the period data is deleted, destroyed or anonymised.
6. Data transfers
6.1. Within Türkiye
| Recipient | What | Why |
|---|---|---|
| The company's own ERP and HR systems | Identity, personnel and transaction data | Running business processes |
| SMS provider (NetGSM — Türkiye) | Mobile number and one-time code | Sign-in code and two-factor authentication SMS |
| Competent public authorities (social security, tax offices, courts, law enforcement) | Requested data | Legal obligation (KVKK Art. 8/2-a) |
| Accountants, legal counsel and auditors | Records required by law | Meeting legal obligations, protecting rights |
6.2. Outside Türkiye (KVKK Art. 9)
| Provider | What is transferred | Purpose |
|---|---|---|
Expo / Expo Application Services (USA) — exp.host, u.expo.dev | Push token, device platform; the device's IP address when downloading an app update | Push notification delivery and over-the-air app updates |
| Apple (USA) — APNs | Push token and notification content | iOS push notifications |
| Google (USA) — Firebase Cloud Messaging | Push token and notification content | Android push notifications |
| Cloudflare (USA) | Connection metadata: IP address, country code, user agent | Secure access to the server, attack and bot protection |
| SendPulse — e-mail delivery service | Recipient e-mail address and message content | Delivering system e-mails (notifications, documents, verification) |
| WhatsApp (Meta Platforms) | Mobile number and a message containing the one-time sign-in code | Delivering the sign-in code from the company's WhatsApp line (falls back to SMS when WhatsApp is unavailable) |
These transfers are made under KVKK Art. 9, relying on the providers' standard contractual terms and appropriate safeguards, and are limited to the minimum data needed for the service to work. Transferred data is never used for advertising or profiling.
7. Your rights (KVKK Art. 11)
You have the right to: learn whether your personal data is processed; request information if it has been processed; learn the purpose of processing and whether it is used accordingly; know the third parties to whom it is transferred in Türkiye or abroad; request rectification if it is incomplete or inaccurate; request erasure or destruction within the conditions of Art. 7; request that rectification/erasure be notified to third-party recipients; object to an adverse outcome produced solely by automated analysis; and claim compensation for damage arising from unlawful processing.
Note: Records that must be kept by law (attendance, personnel files, accounting records) cannot be deleted before their statutory retention period expires. In that case your request will be answered in writing with reasons.
8. How to contact us / make a request
Under the Turkish Communiqué on Application Procedures to the Data Controller, you may apply:
- In writing, with identity documents: İbrahim Ağa Mah. İnönü Cad. No:1, 38400 Develi/Kayseri
- Via registered electronic mail (KEP): selahattin.kolsuz@hs01.kep.tr
- With a qualified electronic signature / mobile signature, or from the e-mail address already registered in our systems: develigross@gmail.com
- Online: Account & data deletion page
Requests are answered free of charge within 30 days at the latest. If the process incurs a cost, the tariff set by the Turkish Personal Data Protection Board may apply.
9. Account and data deletion
Accounts cannot be created in this app; they are created by a company administrator. You may nevertheless request deletion of your account and associated data.
Account deletion request page: Account & data deletion
That page explains which data is deleted, which data is retained because of legal obligations, and how long the process takes. Requests are completed within 30 days at the latest.
10. Security
- All traffic is encrypted with HTTPS/TLS; server access is routed through a Cloudflare tunnel.
- Passwords are stored server-side as irreversible scrypt hashes.
- Saha Satış visit and signature photos are stored under unguessable file names and open only through a time-limited signed link generated for an authorised person.
- In the older Staff / Manager / Terminal apps, session tokens and sensitive values are kept in the iOS Keychain / Android Keystore on the device. In Develi Gross Çalışan and Supplier, the session token and recognised-device key are kept in the in-app web view's local storage (protected by the device's own encryption), while the biometric sign-in key is kept in the Keychain / Keystore and can only be unlocked by biometric verification.
- Accounts lock automatically after repeated failed passwords; sign-in endpoints are rate-limited per IP and per identity.
- Suspicious IP addresses can be blocked; access can optionally be restricted to Türkiye.
- Access rights are role/template based — users see only the screens assigned to them.
- When a working relationship ends, server-side access is cut immediately and device-side data is wiped.
11. Not directed at children
The app is not directed at persons under 18 and does not knowingly collect personal data from children. It is available only to Develi Gross employees and business partners, whose accounts are created by an administrator.
12. Changes
This policy may be updated. The current version is always published at /privacy. Material changes are announced in-app. The "Last updated" date at the top indicates the version in force.
13. Contact
| develigross@gmail.com | |
| Phone | 0352 606 05 18 |
| Address | İbrahim Ağa Mah. İnönü Cad. No:1, 38400 Develi/Kayseri |
| KEP | selahattin.kolsuz@hs01.kep.tr |