Antessia privacy notice
This page explains who is responsible for your personal data when you use Antessia, what we handle, why, who sees it, how long we keep it, and what your rights are.
1. Who we are
Antessia is provided by VSixtyFour Labs Limited, a company registered in England and Wales (company number 17268872). Registered office and postal address: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom.
We are registered with the Information Commissioner's Office (ICO), registration number ZC253151. Privacy contact: [email protected].
We have not appointed a Data Protection Officer. We have assessed the legal test and keep that decision under review as Antessia grows. Questions go to [email protected].
Controller and processor: who is responsible for what
For some data VSixtyFour Labs Limited is the controller: it decides why and how the data is used. This applies to your account, sign-in, security and push-notification data (section 5), including a verified mobile number (section 4), your private saved places (section 2) and your driver app settings (section 5).
For the operational data of a transport company, such as the location of its drivers and vehicles, the transport company is the controller and VSixtyFour Labs Limited is its processor: we handle that data on the company's behalf and on its documented instructions. If you drive for a company that uses Antessia, that company's own privacy notice, linked in the app, also applies.
2. Driver location
Who is responsible
When you drive for a transport company that uses Antessia, that company is the controller of your location data. VSixtyFour Labs Limited is its processor and handles the data on the company's behalf and on its instructions.
What we collect and when
While you are on shift we collect latitude, longitude, accuracy, heading, speed and the time of each reading, about every 15 seconds and sometimes more often. This includes times when the app is closed or not in use. Your shift runs from the moment you tap Start shift until you tap End shift. A notification is shown on your phone the whole time.
- Many transport companies run multi-day ("tramping") trips. On those trips sharing is continuous by default: it includes rest periods and nights spent in the vehicle, unless you end your shift.
- Your company may instead set a maximum shift length of 12, 24 or 48 hours. The shift then ends automatically that many hours after Start shift or after your last trip confirmation in the app, and no later than 12 hours after the limit while a load is in progress.
- We do not collect your location when you are off shift.
- We do not collect advertising identifiers, and we do not use your location for advertising, analytics or profiling.
Why, and the legal basis
Your location is used to let your company see where its vehicles are, assign and manage loads, handle delays and disputes, and protect drivers, vehicles and cargo. On multi-day trips the vehicle and its cargo stay at risk while you rest. The legal basis is your company's legitimate interests (UK GDPR Article 6(1)(f)). If your company's own notice says it relies instead on your contract with it, the basis is performance of that contract (Article 6(1)(b)). Your location is not used to score your driving or to make automatic decisions about you, unless your company has told you so in its own notice.
Ending your shift
You can tap End shift at any time, including before you rest. Ending a shift stops location sharing only. It does not stop your company booking your truck: bookings follow the vehicle. You can stop sharing completely in Settings > Location & privacy > Stop sharing completely.
Who can see it
- Your company's dispatchers and administrators.
- VSixtyFour Labs Limited staff, only for support or security. Access through Antessia is logged.
- Our service providers (sub-processors), listed in section 7.
Retention
- Current position: removed within 2 days after your shift ends.
- Route history: 30 days by default. Your company may choose a shorter period, never longer than 90 days.
- If you leave a company: sharing with it stops immediately, and existing history is deleted on the same schedule. If you join another company that uses Antessia, the new company cannot see anything captured before you joined it, and that earlier history is still deleted on your earlier company's schedule, not the new company's.
- Stopping sharing does not delete your history. You can ask for it to be deleted (section 8).
- Records of notices you accepted and of shift and tracking settings (these contain no locations): we do not currently delete them automatically. We keep them as evidence of what you were told, and delete them on request (section 8), unless we must keep them to establish or defend a legal claim.
Saved places (when Places is turned on)
We turn Places on company by company. When it is on for a company you drive for, and your driver app includes it, your company can save places such as depots, parking and fuel stops and send them to you. Where we also turn on private places, you can save your own.
- What a place holds: a name, a type (for example parking or fuel), map coordinates and, if added, an address and notes, with when it was created and last changed.
- Your private places: only you see them in the app; your company's staff cannot see them in Antessia. VSixtyFour Labs Limited is the controller of your private places and keeps them to provide this feature to you. The basis is contract (Article 6(1)(b)). Our staff access them only for support or security.
- Sharing a place: you can share one of your places with a company you drive for. Sharing makes a copy that belongs to that company: its staff and its drivers see the copy, and your notes only if you choose to include them. Deleting your own place does not delete the company's copy. If you delete your driver account, the company keeps the copy and we remove its internal links to your account, but its name or notes may still show who made it.
- Company places: your company's places, the copies shared with it, and the records of places it sent to you are your company's data. Your company is the controller and VSixtyFour Labs Limited is its processor. Your company uses them to organise its drivers' work. The basis is your company's legitimate interests (Article 6(1)(f)). A place sent to you is shown for 7 days or until you dismiss it. The record that it was sent to you is then deleted, normally within a day; the company keeps its place.
- Your location while you use Places: while the Places screen is in front of you during your shift, the app checks your location about every 3 seconds to tell whether the truck is parked. Some actions work only while it is parked. These extra readings are used on your phone, kept only in the app's memory while it runs, and not sent to us, with one exception: if you choose "Save where I am", the app sends us the place's name, its type and the coordinates of a recent reading, and we save them as your private place.
- Navigation: if you tap Navigate, the app passes the place's coordinates to the navigation app you choose (Google Maps or Waze), which handles them under its own terms.
- Retention: places are not deleted automatically. You can delete your own places at any time. Deleting your driver account deletes your private places and the records of places sent to you.
3. Stop check-ins and transport documents (drivers)
If your company uses stop check-ins, the driver app records your progress through the stops of a trip. Your company is the controller of this data and VSixtyFour Labs Limited is its processor.
What we collect
- Stop check-ins: when you arrive at a stop, record Loaded, No goods or Unloaded, and depart. Each record has its time, whether it was automatic or manual, the reason you chose for a manual check-in and any note you typed, and the distance and accuracy the phone measured to the stop. The phone sends the distance, never your coordinates. For a manual check-in our server also works out your distance from the stop using the location you were already sharing on shift (section 2), taken within 5 minutes of the check-in. Automatic check-in uses the location the app already collects on shift; it collects nothing extra.
- Transport documents: when you record No goods at a pickup, you can photograph the CMR or other transport document. A transport document may show names, addresses, signatures and phone numbers of the sender's and the receiver's staff. Only JPEG photos are accepted. Before a photo is stored, our server removes the information the camera embedded in it (Exif and XMP data, which can include the place the photo was taken), so a stored photo carries no location.
Why, and the legal basis
Your company uses this data to follow the trip, prove what happened at each stop, and handle delays and disputes. The basis is your company's legitimate interests (UK GDPR Article 6(1)(f)).
Who can see it
- Your company's dispatchers and administrators. If a trip moves to another company, that company sees only the state of the stops you recorded (for example "Loaded"), never their times, reasons, notes or your photos.
- You, in the app: your own trips, and your own photos for 7 days after the trip.
- VSixtyFour Labs Limited staff, only for support or security. Each time anyone opens a transport document, it is logged.
Retention
- Transport document photos: deleted automatically 6 years after they were uploaded, because they are transport records. A photo that never arrives in full is not kept.
- Stop check-in records: we do not currently delete them automatically. They are kept as your company's trip records. You can ask for them to be deleted (section 8); your company decides, because it is the controller.
- Deleting your driver account does not delete these records or photos: they are your company's transport records.
4. Phone numbers
A phone number is an optional contact field on a driver's or user's record. We do not check a number typed into this field. If a console user verifies a mobile number (see below), we also write that number into their contact field, and it stays there if the verification is later removed; a driver's contact field is never changed by verification. Dispatchers use a driver's number to contact the driver, and it is part of the booking configuration our own systems build for the booking engine. It is visible to your company's administrators and dispatchers and to VSixtyFour Labs Limited support staff. For a driver, your company is the controller and VSixtyFour Labs Limited is its processor. We keep the number while the account exists, and delete it on request (section 8).
Phone verification by text message (when turned on)
We may turn phone verification on for some or all accounts. When it is on for your account, we ask you to confirm a mobile number with a code sent by text message, and we may then use that number to send you sign-in, verification and password reset codes. If the number on your account is changed, we send a security message to the old number where we can, and an email to you. We do not use the number for marketing. VSixtyFour Labs Limited is the controller of the verified number, as part of your account and security data (section 5). We use it to let you sign in and recover your account and to keep it secure. The basis is contract (Article 6(1)(b)) and our legitimate interest in preventing account takeover and fraud (Article 6(1)(f)).
- What we keep: the number, its country, whether and when it was verified, and a record of earlier changes that holds only a hashed (one-way scrambled) form of earlier numbers. If we cannot yet send texts to your country, we keep the number you gave, unverified, until we can.
- Codes: a code expires after 5 minutes and allows at most 5 attempts. We store only a hashed form of each code, never the code itself. A used code is deleted at once; an unused one is deleted the next time our code records are saved, once it has been expired for a day.
- Security records: our record of each text shows your account, the country, the purpose and, when the provider returns one, its message reference. It never shows the number or the code.
- Preventing abuse: to limit how many texts are sent, we keep records linked to your account, the country, a hashed form of the number and your internet (IP) address (for IPv6, only its network part). We delete these records as they age, after 1 to 30 days depending on their purpose, the next time we process a text. We also keep monthly totals that are not linked to you.
- Testing before it is turned on: we may test phone verification before turning it on, using the contact number on your record. We send nothing. Each test writes a security record, and a test that would have sent a text also keeps the records described above, including the hashed number.
- After a number change: for 7 days, your password cannot be reset with a text message. A driver can still reset by email. A console account that needs a text message to reset (section 5) must ask for help during those 7 days.
- Delivery: texts are sent through AWS End User Messaging (section 7). To deliver a text, AWS passes it to the mobile network that serves your number. If that network is outside the UK, the number and the text go to that country. For a country covered by a UK adequacy decision (for example the countries of the European Economic Area), the transfer relies on that decision. For any other country, we have no separate agreement with the network: the text reaches it only because it serves your number. A sign-in, verification or reset code is sent there because you asked for it, and a security message about a number change is sent there to protect your account. Ask us at [email protected] for more about these transfers.
- Retention: we keep the number while it is on your account. It is removed when you change it, when an administrator removes it, or when your driver account is deleted. We do not otherwise delete it automatically, and we delete it on request (section 8).
Facility phone numbers
We keep a directory of business phone numbers for pickup and delivery sites (for example a gate or goods-in desk), added by us or by dispatchers, and show them to dispatchers in the load details and in booked WhatsApp messages. For each number we also keep how many times and when it was last tapped to call from the console; only we see this. We do not record the names of the people who answer. If a number in it is your personal number, ask us to remove it (section 8). Numbers we remove from use are kept in our records until you ask us to delete them.
5. Account and security
VSixtyFour Labs Limited is the controller of your account, sign-in, security and push-notification data.
Data
- Your name, email address and, if given, phone number, and a verified mobile number if phone verification is on (section 4).
- A password hash, any authenticator registration, and recovery codes.
- Sessions, and push-notification registrations.
- For drivers: your private saved places (section 2) and your driver app settings (below).
- Security and audit records.
The legal basis is contract (Article 6(1)(b)) and our legitimate interest in security and fraud prevention (Article 6(1)(f)). Where the law obliges us to keep records, the basis is legal obligation (Article 6(1)(c)).
Password reset
You can reset your password with a link sent by email. A reset signs you out everywhere and removes trusted devices.
Drivers: when phone verification is on for your account, you may be sent a reset code by text message instead of the link, and we then email you to say your password was reset. For 24 hours after such a reset, these are not available: deleting your account in the app, adding or changing your phone number, completing a number that was saved unverified, and leaving a company.
Console accounts: owner and master administrator accounts cannot reset their own password. Another master administrator of the same company, or we, can reset a master administrator's password; an owner account is reset only by us. When phone verification is on for your account, any other console account that signs in with an emailed sign-in code or an authenticator needs both the emailed link and a code sent by text message to its verified number. Without a usable verified number, including for 7 days after that number was changed, it cannot reset its own password and must ask a master administrator of its company or us.
Sessions and retention
- Sessions for user accounts end after 12 hours without use, and after 7 days at most. Driver app sessions last up to 30 days.
- Account data and security and audit records: we do not currently delete them automatically. They are kept until deleted on request, unless we must keep them for a legal obligation or claim.
Driver app settings and trip reminders
Our server can also keep a home time zone, quiet hours and a choice of how you are alerted to new trips, if your driver app sets them. The current driver app does not set them, and Antessia does not use them yet. If any are kept, they stay until they are changed or your driver account is deleted.
If trip reminders are available to you and you turn them on, we keep your reminder choice (how long before a pickup to remind you) and any departure time you enter for a trip. A departure time is deleted once it is 2 days in the past, the next time your settings are saved. We use these to remind you when to leave for a pickup; the basis is contract (Article 6(1)(b)). For each reminder we keep which trip and vehicle it is for and when it is due. We normally delete it about a day after it stops applying (30 minutes after the planned pickup, or when the trip ends if that is later). Reminders do not use your location. The push message that wakes your phone carries no name, vehicle, place or load details; the app builds the reminder from the trip details it already has. Deleting your driver account deletes your settings and reminders.
Deleting your account
Drivers can delete their account in the Antessia driver app (version 25 and later), or at antessia.com/delete-account, which explains what is deleted, what is kept and why, and how long it takes. You can also request deletion by email to [email protected]. Company console accounts are closed through your company administrator or by email.
6. Operational messages on WhatsApp (dispatchers and company owners)
Antessia may post operational messages to your company's WhatsApp group. These messages are not marketing.
- Booked messages (a vehicle was booked) contain the vehicle plate and the booked load: the pickup and delivery site names, site codes and business addresses (towns and postcodes included), the pickup depot's map coordinates as numbers, the planned start time, the distance and a Google Maps link to the pickup depot. A booked message also names the vehicle's driver when the group that receives it opted into the Driver field. A group can switch the load details off. They are posted to the company's own WhatsApp group, which its dispatchers read. Payout and the booking session id appear only in the VSixtyFour Labs owner channel.
- Alert messages (a double booking, a booking delay) go to the VSixtyFour Labs owner channel only. They name no vehicle.
- Change messages (a dispatcher changed a vehicle's booking or availability) state the vehicle and the new values that were set, for example the new pickup time or status. The new driver's name appears only when the driver assignment changed, and only in a group that opted into the Driver field (a company group, or the VSixtyFour Labs owner channel). No message names the dispatcher. Change messages posted to company groups do not contain the payout; the VSixtyFour Labs owner channel does receive payout lines.
- Booked messages may contain a business phone number of a pickup or delivery site, taken from our facility directory. They never contain the phone number of a driver or a user, or the live position of a vehicle or a driver.
Who is responsible
Your company decides which group receives the messages, and VSixtyFour Labs Limited sends them for it. The messages are sent through a linked consumer WhatsApp account that we operate with an unofficial client, not through the WhatsApp Business Platform. WhatsApp is run by Meta, which processes the messages under its own terms and privacy policy as an independent provider (WhatsApp privacy policy). It is not our sub-processor.
Basis and retention
The basis is the company's legitimate interest in coordinating its operations (Article 6(1)(f)). Copies stay on the WhatsApp devices of group members under WhatsApp's terms. A message that cannot be delivered within 24 hours is discarded. One that fails repeatedly, or whose company's WhatsApp group changed, is moved to a failure file, kept for 30 days, then deleted from the live system (backup copies follow the backup policy). We also delete it on request (section 8). We keep only a status showing whether the latest message was sent.
7. Service providers and transfers
We use these providers to run Antessia. They receive data only as described here.
- Amazon Web Services (hosting, Ireland, eu-west-1): all Antessia data. Amazon SES (SMTP, eu-west-1) delivers the emails we send, such as invitation and password reset links, so the recipient's email address and the message pass through it.
- Amazon Web Services, AWS End User Messaging: delivers the text messages for phone verification when it is turned on (section 4), so the mobile number and the message pass through it.
- Google, Firebase Cloud Messaging: push notifications to your phone. Google Maps draws the map in your company's dispatcher console.
- Cloudflare: network security and delivery.
- WhatsApp (Meta): operational messages, through a linked consumer account (section 6). Meta acts as an independent provider.
Some of these providers are US companies. Where a provider is certified under the UK Extension to the EU-US Data Privacy Framework, we rely on that certification. Otherwise, transfers are protected by the ICO's International Data Transfer Addendum to the EU Standard Contractual Clauses. A text message to a mobile network outside the UK is covered in section 4.
8. Your rights, objection and complaints
Your rights
You can ask for access to your data, for its correction or erasure, for its use to be restricted, or, for data you gave us under a contract, for a copy in a portable format (data portability).
Your right to object
You can object at any time to processing based on legitimate interests, including location sharing. Contact your company, or write to us at [email protected] and we will pass your objection to the company.
Requests about location
Requests about location go to your company, because the company is the controller. We pass them on within 3 working days and help the company respond.
Complaints
Contact us first at [email protected]. This is also our complaints route under section 164A of the Data Protection Act 2018: we acknowledge complaints within 30 days and respond without undue delay.
You can also complain to the Information Commissioner's Office at ico.org.uk.
VSixtyFour Labs Limited, company number 17268872, ICO registration ZC253151. Registered office: 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ. This notice is in English.