Privacy

Your account, on the licence server

When you register, the licence server keeps your email address, your name if you give one, and the time you last signed in.

Your password is never stored. What is stored is a PBKDF2-SHA256 hash of it — a one-way scramble that can check a password but cannot be turned back into one. Nobody at ACADEMIA can read your password, including us.

While you are registering, an unfinished sign-up holds your email, the hash of your password, and the hash of the code we emailed you. It expires, and it is marked used the moment you verify.

Your workspaces and who is in them

A workspace records its name, the licences it holds, and how many seats each has.

Membership records which account is in which workspace and with what role, who added them, and when. An invitation records the address invited, the role chosen, and who sent it.

Activity records what people did in a workspace — a role changed, a licence attached, a build installed, a permission moved — with the address that did it and when. This is deliberately visible to everyone in that workspace: it is the record you need when access changes and nobody remembers why.

Your aircraft

For each drone, the licence server keeps its hardware key and its board serial. The hardware key is a fingerprint — md5 of the CPU serial, the SD card serial and the build's binary name — and it is what a licence seat is counted against.

Every build a drone downloads is recorded: which build, when, from which IP address, and the city, region and country looked up from that IP. That is how a licence is spent and how a download can be traced if something goes wrong.

Names you give drones are stored so they follow the aircraft rather than the laptop that named it.

On this computer

Your sign-in is kept on this machine until it expires or you sign out. So are your preferences: language, theme, which filters you left set, which build and licence you last chose.

Anything the app could not send to the licence server — an action recorded while it was unreachable — waits here until it can be delivered.

Signing out removes the session. Preferences stay until the application is removed.

On the aircraft, which never comes to us

A drone's settings, camera mask, launch point and StabX password live on the aircraft. Link reads and writes them directly over your own network.

None of that is sent to the licence server or to us. When you copy settings from one drone to another, the values go from one aircraft to the other and nowhere else — and the password and launch point are deliberately left behind, because they belong to the aircraft they are on.

What leaves your network

Two things. Requests to the licence server, which carry your session and whatever you are doing. And map tiles, fetched from CARTO and ArcGIS when you open the map — those providers see the request and the IP address it came from, as any website would.

There is no analytics, no usage tracking, no advertising identifier, and nothing sent to any other third party. The application does not report what you look at.

Who can see what

People in a workspace see that workspace: its drones, its licences and its activity. What each role may see is set by the workspace's own permission table, and somebody without permission to view licences sees codes masked rather than in full.

ACADEMIA staff can reach the licence database to operate and support the service.

Nothing is sold, and nothing is shared with anybody else except where the law requires it.

Removing your data

You can leave a workspace at any time from Settings, which removes your membership.

To have an account and its data deleted, write to support@theacademia.tech. Records that a drone downloaded a build are kept as part of the licence history and are not tied to your account once it is gone.