Privacy policy
For Tera Drive, operated by Aethera, Aotearoa New Zealand.
Version 1.0 ·
This is a draft and has not been reviewed by a lawyer. It describes what the product does today, accurately and in plain words, which is the right starting point — but vehicle tracking of staff is one of the more closely examined things you can do under the Privacy Act 2020, and the wording below should be checked by someone qualified before you rely on it publicly.
Tera Drive records where a workspace's vehicles go. Where a vehicle is driven by a person, that is information about a person, and the Privacy Act 2020 applies to it. This page says what we collect, why, who can see it, how long we keep it, and what you can ask us to do about it.
Who we are
Aethera is the agency for the information described here, and can be reached at privacy@aethera.co.nz.
Your employer is usually the one making the decisions. If you drive a vehicle fitted with a Tera beacon, the business you work for chose to fit it, chose whether to record position history, and decides who in that business can see it. We hold the information on their behalf. Ask them first — and if you cannot get an answer, write to us.
What we collect
| Vehicle positions | Latitude, longitude, speed, heading and accuracy, sent by the beacon in the vehicle, with the time each was recorded. This is the record of where a vehicle — and so usually a person — has been. |
|---|---|
| Daily totals | Distance, driving time and any speeding or harsh-driving events, summarised per vehicle per day. |
| Drivers | Name, and the record of which driver was assigned to which vehicle. |
| Accounts | Email address and display name for people who sign in. |
| Vehicles | Registration plate, make, model, year, odometer, and warrant and registration dates. |
| Places | Sites a workspace has named, and which vehicles visited them. |
| Beacon health | Battery, charging state, signal and uptime for the device in the vehicle, so we can tell a flat phone from a fault. |
| Faults | When the console hits an error it reports the message, where in the code it came from, and a stack trace. It deliberately does not send the page address, anything you typed, or anything on screen — the address alone would carry vehicle identifiers, so only the name of the view is recorded. |
Position history can be switched off
Recording where vehicles have been is a per-workspace setting. With it off, the console shows no positions at all. With it on, anyone signed in to that workspace can see where its vehicles are and where they have been. We keep a consent record against each driver — including which version of the notice was acknowledged, and whether the driver acknowledged it themselves or their employer attested that they were told.
Why we collect it
- To show a fleet operator where their vehicles are and what they have been doing — the purpose the product exists for.
- To work out distance, fuel and running costs.
- To warn about warrants and registrations falling due.
- To flag speeding and harsh driving.
- To keep the service working, and to fix it when it breaks.
We do not sell it, we do not use it for advertising, and we do not use it to train machine-learning models.
Who else sees it
These are the only parties outside Aethera that receive anything, and what each one gets:
| Who | What they get | Why |
|---|---|---|
| Supabase | All of the above — they host the database, sign-in and server functions. | Storage and authentication. |
| Vercel | The usual web-server record: IP address, browser, and which files were requested. | Serving the console. |
| Toitū Te Whenua LINZ Basemaps |
Which map tiles your browser asks for, which indicates roughly where on the map you are looking. | The map imagery. |
| OpenStreetMap (Overpass) |
A coordinate, asked for the posted speed limit there. Your browser asks this one directly, so it also sees your IP address. | Speed limits, to tell speeding from normal driving. |
| Our geocoding provider (today OpenStreetMap's Nominatim) |
A coordinate, turned into a street name — and only when we have not already asked about that place. Our server makes this request, not your browser, so the provider sees a place and not a person: no IP address, no session, nothing tying one lookup to another. | Showing “Penrose yard” instead of a pair of numbers. |
| unpkg, jsDelivr | Your IP address and browser, when your browser fetches the mapping and 3D libraries. | Code delivery. |
Some of these are outside New Zealand. Where that is so, we rely on the protections in section 11 of the Privacy Act and the providers' own contractual commitments.
How long we keep it
| Individual positions | Three days. The detailed breadcrumb trail is deleted after that — so the map can show you last week's distance, but not the exact route taken to earn it. |
|---|---|
| Daily totals | Kept while the workspace exists. These are figures, not routes. |
| Vehicles, drivers, places | Kept while the workspace exists, or until deleted. |
| Fault reports | Kept while they are useful for fixing the fault, then removed. |
Your rights
Under the Privacy Act 2020 you can ask to see the information we hold about you, and ask for it to be corrected if it is wrong. Write to privacy@aethera.co.nz. We will answer within 20 working days.
If the information is held for an employer, we will usually need to involve them — they decided to collect it, and they are the ones who can say why.
You can delete your account from the console's settings. What that removes depends on whether anyone else is in the workspace: if there is, you are removed from it and the workspace and its vehicles stay with the other members; if you are the only one, the workspace goes with your account — vehicles, beacons, drivers, consent records and every position recorded. Nothing in that second case can be recovered afterwards, and the console says so, by name, before it will let you confirm.
If you are not satisfied with how we have handled a privacy matter, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.
Security
Traffic is encrypted in transit. Access to a workspace's data is enforced in the database itself rather than only in the application, so a signed-in user cannot read another workspace's vehicles. Changes to significant settings are recorded in an audit log.
Cookies
Tera Drive sets two cookies. Both exist so that signing in once works across Aethera's products, one lasts sixty seconds and the other twenty, and neither carries an identifier that would follow you to another website. There are no advertising or analytics cookies. All of it, including what the console keeps in your browser's own storage, is itemised in the cookie policy.
Changes
If we change what we collect or who receives it, we will update this page and its version number. Where the change is significant and position history is involved, drivers are asked to acknowledge the new version.