While a shift is running
Your position is recorded
- One location fix roughly every 30 seconds
- Latitude, longitude, speed and GPS accuracy
- The time the fix was taken
- An odometer photo at the start and the end
Outside a shift
Nothing is recorded
- Evenings, weekends, your own time
- Before you start a shift and after you end it
- If you never accept tracking, no position is ever accepted
01Who holds your data, and who we are
Wejhatak is fleet management software sold to transport companies. Your employer decides what is collected about you, why, and for how long it is kept. They are the ones who can answer a question about their own fleet's records.
JTS builds and operates the software on your employer's behalf. We hold the data so their system can run; we do not sell it, rent it, or use it for advertising.
Each company's data is separated inside the system at the database layer, so one company's staff cannot read another company's vehicles, drivers or journeys — a request for another company's record is answered as though the record does not exist.
02Location: only while a shift is running
The driver app records your position only during a driving shift that you started yourself. There is no background tracking outside a shift, and there is no way for your employer to switch tracking on remotely.
While a shift is running the app takes a location fix about every 30 seconds and stores these fields:
| Field | What it is |
|---|---|
| latitude, longitude | Where the vehicle was, to about a metre |
| speed | Kilometres per hour, where the phone reports it |
| accuracy | How precise the GPS fix was, in metres |
| recorded_at | When the fix was taken on the phone |
| received_at | When it reached the server — different if you were offline |
| source | Always phone today; reserved for vehicle hardware later |
Fixes are written to a private database on your own phone first, then uploaded in batches. If you drive through an area with no signal, nothing is lost — the app keeps the queue and sends it when the connection returns. That is why a journey can appear in the system hours after you drove it.
A notification stays visible on your phone the whole time tracking is active. If you can see it, you are being tracked; if you cannot, you are not.
03Consent, and taking it back
Before your first shift the app shows you what it does and asks you to accept. Until you accept, the system refuses every position the app tries to send and refuses to start a shift at all.
When you accept, three things are written: that it was you, the exact time on our server, and the version of the text you were shown. Keeping the version is the point — it means what you agreed to can still be produced later, rather than being an unprovable claim that you "agreed to tracking".
If you decline
You can still sign in and see the vehicle assigned to you. You cannot start a shift. You will be asked again next time you sign in.
If you withdraw later
Withdrawal is in the app's Settings, and it takes effect immediately: any shift in progress is ended, and no further position is accepted.
Withdrawing does not erase the journeys you have already driven. Those journeys have already been costed and reported against your employer's vehicles. Existing history is kept — section 08 explains for how long.
If the consent text is ever revised, you are asked to accept the new version. The record of the earlier one is kept.
04What else the app records
Odometer photos
You photograph the vehicle's odometer when you start a shift and again when you end it. The photo is stored privately — it is not published and has no public link. Stored with it are the reading, the time, and the location and GPS accuracy at the moment the photo was taken, so a reading can be matched to where the vehicle actually was.
Your device
So that one phone's access can be revoked without signing you out everywhere, each install is named by the phone's model plus a random identifier generated once on that install and kept in the phone's secure storage.
We deliberately do not use the Android ID, the IMEI, the advertising ID, or any other permanent hardware identifier. A reinstall produces a new identifier, because a reinstall is a new install.
Sign-in
You sign in with your phone number and a one-time code sent by SMS. The code itself is never stored — only an unreadable hash of it, which expires. Records of the messages sent to you are kept so your employer can see whether a code was delivered.
Nothing else on your phone
No contacts, no call log, no SMS inbox, no photo gallery, no microphone, no browsing, no other apps. The camera is used only for the odometer photo you take yourself. The app contains no advertising network, no analytics tracker and no third-party crash-reporting service.
05Phone permissions, and why each one exists
| Permission | Why |
|---|---|
| Location (precise & approximate) | Recording the route of a shift. Requested the first time you start one. |
| Location in the background | So the route keeps recording while your phone is locked or the app is behind your map or music. It is only ever used during a shift you started. |
| Foreground service | Keeps the recording alive during a shift, and is what makes the persistent notification appear. |
| Notifications | The tracking indicator that tells you recording is on. |
| Camera | The odometer photo at the start and end of a shift. Nothing else. |
| Start on boot Keep awake | If your phone restarts mid-shift, recording resumes instead of silently stopping. |
| Battery optimisation | Opens your phone's own settings screen so you can exempt the app. The app cannot grant this itself. |
| Internet, network state | Uploading the queue, and knowing when there is a connection to upload on. |
You can refuse or withdraw any of these in your phone's settings. Location refused means a shift cannot record, which is separate from your tracking consent — the app tells the two apart and says which one is missing.
06What your employer holds about you
Your employer's office staff maintain a record for each driver. What it contains is their decision, and the system can hold:
| Held | Notes |
|---|---|
| Name, staff number | Identifying the driver record |
| Phone, email | Contact, and the phone number is your sign-in |
| National ID number and a photo of it | Optional. Stored privately, never returned in a public link |
| Licence number, class, expiry | So an expiring licence can be caught before it lapses |
| Employment status | Active, inactive or suspended |
| Preferred language | Arabic or English |
| Shifts, distance, duration | Derived from your shifts |
| Pay, advances, deductions | Where your employer uses the driver-pay features |
| Traffic violations | Where your employer records them against a driver |
Records are archived rather than deleted, so that a vehicle's cost history does not develop holes when a person leaves.
07Who can see what
Access is decided by role, and three limits are built into the system rather than left to office practice:
- Drivers cannot browse location history — not other drivers', and not their own. The one exception is the route of a single shift you drove yourself.
- Pay records and traffic violations are visible to an administrator only — never to a manager, and never to another driver.
- What a journey earned is never shown to a driver. The value of a trip is removed from every response the driver app can receive.
Fleet managers at your company see vehicle positions and journey history, which is what the product is for. Every change to a record, every sign-in, and every export of data is written to an audit log with the person, the time, and the network address it came from — including exports, which record what was exported and how many rows.
08How long it is kept
Position history is kept for as long as your employer's account is open. Automatic deletion of routes after a set period is designed into the product but is not switched on yet. Nothing is currently deleted on a schedule.
When it is switched on, your employer will choose the window — anything from a week to ten years, or none at all — and this page will say so before it takes effect. The shift itself is stored separately from the route it took, so that when routes do start expiring, the date, distance and duration of your work survive.
Odometer photos, driver records, journeys, costs and audit entries are kept for as long as your employer keeps their account, and are held under their record-keeping and tax obligations.
09Where it is stored, and who else is involved
The system runs on DigitalOcean infrastructure in Frankfurt, Germany. DigitalOcean has no data centre in Egypt, the Gulf or Africa, so data about Egyptian drivers is stored in the European Union. All traffic between your phone and the server is encrypted in transit.
| Service | What reaches it |
|---|---|
| DigitalOcean | Hosting and database, Frankfurt. All of the above. |
| VictoryLink | Egyptian SMS gateway. Your phone number and the sign-in message. No location data. |
| OpenStreetMap | Map images for the office web app only. The driver app does not use it. |
No other company receives your data. There is no advertising partner, no data broker and no analytics vendor.
10How it is protected
- Everything travels over an encrypted connection. Positions and credentials are never sent unencrypted.
- Passwords are stored as one-way hashes. They are never written to a log and no part of the system can return one.
- One-time codes are stored as hashes and expire. The readable code is never logged.
- Access tokens are per-device and can be revoked individually; deactivating an account revokes its tokens.
- On your phone, tokens and the install identifier are kept in the platform's secure storage, not in ordinary app preferences.
- Separation between companies is enforced in the data layer, and is covered by its own tests because it is the most consequential thing that could go wrong.
11Your choices and your rights
- Withdraw tracking consent at any time, in the app's Settings.
- Turn off location in your phone's own settings, independently of the app.
- See or correct your driver record — ask your employer's fleet administrator, who maintains it.
- Ask what is held about you, or ask for it to be corrected or removed — the request goes to your employer, because it is their record, and they can reach us if they need to.
Where Egyptian personal data protection law applies to your employer's processing, these requests are theirs to answer and ours to support.
12Children
Wejhatak is workplace software for employed drivers and office staff. It is not directed at children and we do not knowingly hold data about anyone under 18.
13Changes, and questions
If this policy changes in a way that affects what is recorded about drivers, the consent text in the app is given a new version and you are asked to accept it before your next shift. The date at the top of this page always states when this version took effect.
Your employer's fleet administrator is the person to ask. About your own records — your shifts, your pay, your licence details — about anything on this page, and about a request to see, correct or remove what is held about you. They maintain the record, and they can reach us.