Privacy
What the Tartib app collects, why it collects it, and the things it deliberately does not touch.
Last updated 8 October 2026 · applies to the Tartib Team app and the Tartib app for iOS and Android, and to team.tartib.app
The short version. Tartib is a tool your employer gives you for work. It holds the work you record in it — counts, assets, tickets, leave, shifts — and the identity you sign in with. It reads your location only at the instant you check in or out of a shift, and Tartib Team takes one photo then, which your employer's own system compares with your HR photo. It carries no advertising SDK, no analytics SDK and no tracker of any kind, and nothing in it is ever sold.
Who is responsible for your data
Tartib is built and operated by DataTech. Each company that uses Tartib has its own separate workspace and its own database, and that company decides what is recorded in it, who may see it and how long it is kept. In data-protection language your employer is the controller and DataTech is the processor acting on their instructions.
This means requests about your own record — a correction, a copy, a deletion — are normally answered by your employer's Tartib administrator, because they hold the decision. If you cannot reach them, write to hello@tartib.tech and we will help you find the right person.
What the app collects
| Data | Why, and when |
|---|---|
| Identity | Your name, work email and the workspace, branch and role your employer assigned you. Received when you sign in, so the app knows what to show you and who to attribute your work to. |
| The work you record | Stock counts and quantities, asset scans and condition reports, maintenance tickets, checklists, leave requests, shift check-ins and any note you type. This is the point of the app; it is stored in your employer's workspace. |
| Location | Latitude, longitude and an accuracy figure, read once at the moment you tap check in or check out, to confirm the shift was started at the branch. There is no background tracking, no location history and no reading of your position at any other time. If you decline the permission the rest of the app still works. |
| Camera and photos | Used to read barcodes and QR codes — decoded on your device, the video is never uploaded — and to take a photo you choose to send: an item, an asset, a ticket, a checklist answer, a branch log entry or a team post. A photo from your library is only ever the one you pick in the system's own picker. The attendance photo is the next row. |
| Attendance photo and face check | When you check in or out, Tartib Team takes one photo with the front camera, after your check-in is recorded. It is kept with that attendance record in your employer's private storage, and Tartib's own face-matching service — run by DataTech on Google Cloud, never by a third party — compares it with your HR photo to confirm it is you. Only a similarity score and a verdict are kept; no face template is stored, and the photo is not used to identify you anywhere else. You, your manager and your employer's HR can see it. A photo that does not match is flagged for a person to look at; it never cancels your attendance. |
| Face ID / biometrics | Used by your phone to unlock the session already saved on it, and to confirm it is you before a check-in or check-out. The biometric itself is held by the operating system, never reaches the app, and is never transmitted. |
| Notification token | The push token Apple or Google issues for your device, so an approval, a task or a reply in the branch log can reach you. A notification carries a title and one line — a name, a leave type, dates — never pay or a document number. |
| Problem reports (diagnostics) | When something goes wrong in the app — a save or a photo that does not go through, a sign-in that fails, a screen that stops, or a crash — the app writes a short report, keeps it on the phone until it reaches us, and sends it to our server: what failed (the screen or the step, with record numbers taken out), the message on the screen or the error, our server's answer, how long it took and the kind of connection. Every request the app makes also says which version of the app is asking and the phone's system and model (for example, an iPhone 16 on iOS 26). A report is tied to your account so one failure can be followed through our log; it carries no name, amount, photo, message content or location. |
What stays on your device
Some things never leave the handset. They are cleared when you sign out or remove the app.
- dt_keep — your signed-in session, so you are not asked to sign in every shift.
- team_home, team_home_default — which screen you prefer to open on.
- team_lang — whether you read the app in English or Arabic.
- Counts you enter while offline, held on the device until the connection returns and they reach the server. This is why a count is never lost in a cold room with no signal.
What the app does not do
- No advertising identifier, no ad network, and no advertising of any kind.
- No third-party analytics, attribution or crash-reporting SDK. Nothing about your use of the app is sent to anyone but us.
- No tracking across other companies' apps or websites, in the sense Apple's App Tracking Transparency defines it.
- No access to your contacts, microphone, health data, calendar or messages, and none to your photo library beyond the one photo you pick.
- Your data is never sold, rented, or shared with advertisers or data brokers.
Where it is kept
Tartib runs on Google Cloud in the me-central1 region (Doha, Qatar). Every workspace has its own database, so one company's records are not stored alongside another's. Traffic is encrypted in transit, and data is encrypted at rest by the platform.
The only outside services involved are the ones that make the app work: Google Cloud for hosting and storage, Apple and Google — through Expo's push service — for delivering notifications, and Cloudflare for serving the web pages. None of them are given your records for their own purposes. If you connect your own AI assistant (Settings → Connections → Your AI), it reads — and, only if you allowed it, writes — as you, and what it receives is then governed by that assistant's own policy.
How long it is kept
Work records stay in your employer's workspace for as long as that company keeps them, which they set and which may be governed by the labour and tax rules of their country. Problem reports are kept in our service log for 30 days; the summary of a problem we fix — what failed, how often, on which app versions and phone models, never who — stays with the record of its fix. When a company closes its Tartib workspace, its database is deleted.
Your choices
- Location and camera permissions can be refused, or withdrawn later in your device settings. Check-in will then record no position or photo, and scanning will ask you to type the code instead.
- Notifications can be turned off in your device settings at any time.
- Signing out clears the saved session and everything queued on the device.
- To see, correct or delete what is held about you, ask your employer's Tartib administrator, or write to us and we will route it.
Children
Tartib is a workplace tool issued by an employer to its staff. It is not directed at children and we do not knowingly collect anything from them.
Changes
If this policy changes in a way that affects what is collected, we will change the date at the top and, where the change is material, say so in the app.
Contact
Questions about this policy, or about your own record: hello@tartib.tech, or use the contact form. Messages reach a person, and you will hear back within a working day.