Security & Privacy
Security and data privacy for fleet operators
How Axons Mobility protects your fleet data, your riders' personal data and your money. Every operator has its own workspace, every device has its own encryption keys, and roles decide who sees what.
At a glance
- A separate workspace for every operator
- Riders can download their data and delete their account
- Every device has its own encryption keys
- Rider phone numbers always stored encrypted
- Four role levels and permission groups
- AI actions need a person to confirm
- Card details handled by Stripe
Your own workspace
Your data stays in your own workspace
Every operator works in a separate workspace, and people from one workspace cannot see another's vehicles, riders, trips or money.
Workspaces kept apart
Each operator logs in at its own address, and its data is kept apart from every other operator's.
Private trial fleets
During the free trial your fleet sits in a shared trial workspace, and other companies on the trial cannot see your data.
GDPR tools
GDPR tools for riders and operators
Privacy requests are handled inside the product: riders act on their own data, and operators track requests in one place.
Download my data
Riders can download a copy of their personal data from the rider app.
Delete my account
Riders can delete their account in the app. The account is anonymised: personal details such as name, email and phone number are removed.
GDPR request queue
Operators see riders' privacy requests in one queue in the console.
Consent
Riders' acceptance of the terms and privacy policy is recorded, and promotional notifications go only to riders who opted in.
Encryption & devices
Encrypted devices and encrypted rider data
The connected device on each vehicle can lock, unlock and switch ignition, so the link to it needs strong protection.
Keys for each device
Every device has its own encryption keys, and the messages between the vehicle and the Axons Mobility cloud are encrypted.
Replayed messages rejected
A message that is copied and sent again is rejected, so a recorded command cannot simply be played back.
Approval for new devices
A new device cannot connect to your fleet until it is approved.
Keys rotated or revoked remotely
A device's keys can be rotated or revoked from a distance, for example when a device is lost.
Phone numbers always encrypted
Rider phone numbers are always stored encrypted, for every operator.
Extra layer for app requests
An optional extra encryption layer for rider app requests can be switched on for each app build.
Access control
Everyone sees only what their job needs
Large teams, franchise partners and sub-operators can share one console without seeing each other's money or riders.
Four role levels
Axons Mobility has four role levels, so each person gets the level that fits their job.
Permission groups
Fine-grained permission groups decide what each person can see and do.
Sensitive actions locked
Actions such as remote unlock and refunds work only for people whose permissions allow them.
Money and personal data hidden
Revenue figures and riders' personal data can be hidden for a whole permission group.
Limited to chosen fleets
A user can be limited to the fleets you choose, and does not see the others.
Isolated workspaces
Each operator's workspace is kept apart from every other workspace on Axons Mobility.
Activity log
A record of who changed what, and when
When something changes in the console, you can see who did it and when.
Activity log
Changes in the console are recorded with the person who made them and the time.
Activity per user
Open any team member to see the changes they have made.
Timelines
One searchable history of every vehicle, device, rider and staff change.
AI rules
AI that follows your permissions
The AI assistant works inside the same rules as your team, and a person stays in charge of every action.
Sees only what the user may see
The assistant answers from the data the person asking is allowed to see, and nothing more.
Every question logged
Each question asked of the assistant is recorded.
A person confirms actions
The assistant can propose an action, but nothing runs until a person presses Confirm.
Outside AI needs approval
Connecting an outside AI, such as your own Claude or ChatGPT, needs approval before it can reach your workspace.
Unchangeable consent record
The approval is kept as a consent record that cannot be edited afterwards.
Full call log
Every call an outside AI makes to your workspace is logged.
Payments
Card payments handled by Stripe
Rider payments go through Stripe, straight to the operator.
Card details handled by Stripe
Riders' card details are handled by Stripe, the payment provider.
Your own Stripe account
Riders pay into the operator's own Stripe account, so the operator is the seller and the money reaches it directly.
FAQ
Security questions
Have a question this page does not answer? Email tejal@axonsmobility.com or book a demo.
All FAQsWho handles riders' card payments on Axons Mobility?
Stripe. Riders' card details are handled by Stripe, and riders pay into the operator's own Stripe account, so the operator is the seller and the money reaches the operator directly.
What happens when a rider deletes their account?
The rider deletes the account from the rider app and the account is anonymised: personal details such as name, email and phone number are removed. Riders can also download a copy of their data from the app.
How does Axons Mobility stop fake or replayed commands to vehicles?
Each device has its own encryption keys and its messages are encrypted. A message that is sent a second time is rejected, a new device needs approval before it can connect, and a device's keys can be rotated or revoked remotely.
Can we connect Claude or ChatGPT to our fleet data?
Yes, as a paid add-on ($99 / month). The connection needs approval, Axons Mobility keeps a consent record of that approval that cannot be changed, and every call the outside AI makes to your workspace is logged.