Privacy policy
In short: we process only what stock counting needs: your account details, entered by your company's administrator; the count entries you record; and limited technical data that keeps the service safe. We do not collect your location, we use no trackers or ads, and we never sell data. We plan to keep the platform's data inside Saudi Arabia.
1. What this policy covers
This policy applies to these InventWise services:
- The InventWise field app for Android and iOS, used to count stock.
- The admin web app (app.inventwise.app) and the API both apps connect to (api.inventwise.app).
- This website (inventwise.app).
InventWise is a service for companies. Individuals cannot create accounts themselves; each company's administrator creates the accounts of its staff.
2. Who is responsible for your data
The company you work for, which created your account, decides why your data is collected in the platform and how it is used. It is the "controller" in the sense of the Saudi Personal Data Protection Law (PDPL). InventWise processes this data on your company's behalf and on its instructions, to provide the service. For that reason we may refer some of your requests to your company, or coordinate with it before acting on them.
3. Data we process
| Category | What it includes | Source |
|---|---|---|
| Account data | Full name, e-mail address, mobile number (optional), preferred language, role and permissions in the company, account status, and the time of your last sign-in. | Your company's administrator when creating the account; the service when you sign in. |
| Sign-in and security data | Your password, stored only as an Argon2id hash from which the text cannot be recovered; your two-step verification secret, encrypted; recovery codes, stored as hashes; and a record of sign-in attempts and password-reset requests (e-mail address, IP address, time and outcome). | You, and the service during sign-in. |
| Device data | A random installation identifier created by the app (not a hardware identifier), a device name that by default is the system name and the registration date, the platform (Android or iOS), the app version, and the time of the last sync. | The field app when it registers the device with your company. |
| Work (count) data | Count entries: product, quantity, unit, location, and batch, expiry date and serial number where needed, the scanned code, who recorded the entry, the device used, the device time and the time the server received it. Also voids with their reasons, and location start and finish steps. | You when counting; your company (products, balances, locations). |
| Audit log | Who performed an action, what changed and when, with the IP address, device identifier and request identifier. | The service, automatically, for every significant action. |
| Server technical logs | User and company identifiers and technical request details. Passwords, tokens, barcode contents and request bodies are redacted automatically. | The service, automatically. |
| Support messages | Whatever you send us by e-mail. | You. |
4. What we do not collect
- No location. The app does not ask for location access, and location permissions are explicitly removed from the Android build.
- No camera images are kept. The camera is used only to scan barcodes. The app receives the text of the code; it does not save or send images.
- No access to your contacts, photos or files, and no biometrics.
- We use no analytics or crash-reporting tools of our own, no tracking tools and no advertising identifiers, and the app shows no ads. The only exception is the barcode-scanning component from Google, described in section 7.
- Neither the admin web app nor this website uses cookies.
- We do not sell or rent personal data.
5. Why we process data
- To provide the service: sign-in, showing your assignments, recording and syncing count entries, and producing your company's count reports.
- To keep counts trustworthy: linking each entry to the person who recorded it, their device and the time, so your company's supervisors and auditors can review and verify it.
- Security and abuse prevention: limiting repeated sign-in attempts, detecting stolen session tokens, blocking devices your company has stopped, and investigating incidents.
- Support: answering your questions and requests.
- Legal obligations: meeting the requirements of the laws that apply in Saudi Arabia.
We rely on our contract with your company, on our legitimate interest in protecting the service and our customers' data, and on legal obligations.
6. Where data is stored
On our servers
We plan to host the platform's servers, database, backups and logs with a cloud provider inside Saudi Arabia. If that plan changes before or after launch, we will update this policy and say where the data is kept.
On your device (field app)
- Count entries and downloaded count data are kept in an on-device database encrypted with SQLCipher; its key is kept in the system's secure storage.
- The session token is kept in the system's secure storage (Keychain on iOS, Keystore on Android). No secret is stored in the database.
- On Android, the app's data is excluded from cloud backup and from transfer to another device, so it stays on the device.
In your browser (admin web app)
The session token is kept in the tab's session storage (sessionStorage) and is erased when you close the tab. Your language choice and alert-sound preference are kept in the browser's local storage (localStorage) until you clear your browser data.
7. Who we share data with
- Your company: your company's administrators and supervisors see your data in the platform according to their permissions. No other company can see your company's data; the platform separates companies' data at the database level.
- Service providers working for us: the cloud hosting provider, the e-mail delivery provider (for password-reset messages), and the provider that hosts this website and its domain. They get only what they need to provide their service.
- Google (barcode scanning with the camera): camera scanning uses Google ML Kit, on Android through Google Play services. Barcodes are recognised on the device, and the app receives only the text of the scanned code and its format; no image is sent. As Google states for ML Kit, the component itself sends Google diagnostic data: device information (such as the model and system version), the app's name and version, installation identifiers that are not intended to identify a user or a device, performance metrics and error codes. Google uses this data to maintain and improve ML Kit.
- Authorities: when a law or an order from a competent authority requires it.
8. How long we keep data
| Data | How long |
|---|---|
| Account data | As long as your account exists in your company, or the period your company sets (see "Your rights"). |
| Session tokens | Access tokens last 15 minutes. Refresh tokens last at most 30 days, are replaced on every use, and are stored on the server only as hashes. |
| Password-reset links | Valid for 30 minutes, single use. |
| Sign-in attempts and reset requests | 90 days, then deleted. |
| Server technical logs | 90 days. |
| Count entries and the audit log | As long as your company's account exists, or for the period agreed in the contract with your company. The audit log cannot be edited and single records cannot be deleted from it, because it is what makes a count verifiable. |
| Backups | Daily backups 30 days, weekly 12 weeks, monthly 12 months. Deleted data remains in older backups until they expire; we never restore a backup to bring back deleted personal data. |
| Entries on your device | An entry the server has received stays on the device for 30 days, then it is deleted. An unsent entry stays on the device, encrypted, until it is sent; it is never deleted before that, so no count is lost. |
| Count data downloaded to your device | Deleted when you sign out or your session ends, together with the cached profile and its permissions. Uninstalling the app deletes all its data from the device. |
9. How we protect data
- Encrypted connections: the field app accepts only server addresses that start with https://, and sends a session token only to the server that issued it.
- Passwords hashed with Argon2id, a password policy, and a block on very common passwords.
- Optional two-step verification (TOTP), which your company can make mandatory for its administrators.
- Each company's data separated from every other company's at three levels: the sign-in token, the application and the database.
- Fine-grained permissions, with sensitive data such as costs, balances and variances behind their own permissions.
- Rate limits on requests and sign-in attempts, and detection and revocation of re-used (stolen) session tokens.
- An encrypted database on the device, with tokens in the system's secure storage.
- An audit log that cannot be edited or deleted.
- Notification of the competent authority and of affected people after a personal data breach, as the law requires.
No protection is perfect, but we work to reduce risks and keep reviewing our measures.
10. Your rights
The Saudi Personal Data Protection Law gives you rights over your data. In plain terms:
- To be informed: to know what data we collect and why, as this policy explains.
- To access: to see your data and get a copy of it.
- To correct: to have inaccurate data corrected or incomplete data completed.
- To have it deleted: to ask for your data to be deleted once it is no longer needed, unless a law or contract requires us to keep it.
- To withdraw consent: where any processing relies on your consent.
- To complain: to file a complaint with the Saudi Data and AI Authority (SDAIA).
How to use your rights
Your account is created by your company's InventWise administrator, and your company is the controller of your data. Requests to use these rights therefore go to your company's administrator, who can stop your account at once and change your details, role and permissions. For questions about this policy, write to support@inventwise.app.
Count entries and the audit log are your company's business records and are kept for the period your company sets or a law or contract requires.
11. Children
InventWise is a work tool for company staff. It is not directed to children, and we do not knowingly collect data from anyone under 18.
12. Changes to this policy
We may change this policy when the service or the law changes. We will publish the new version on this page with a new effective date, and tell our customer companies about any material change before it takes effect.
13. Contact us
For any question about this policy or your data, write to support@inventwise.app.