Home / Trust & security
Trust & security
Fuel tickets, airline schedules, and the ledger built from them. That is sensitive data. So FuelDeck™ is built on Google Cloud, with each tenant isolated, access set by role, and every privileged action logged.
The foundations
Hosting, encryption and tenancy. The rest of the platform sits on those.
FuelDeck™ is built on Google Cloud and runs there. Nothing to install on your side, no new hardware to buy.
Every ticket and record is encrypted in transit with TLS 1.3 and at rest with AES-256. Customer credentials are stored write-only and encrypted.
Each company's data is walled off from every other tenant's. Inside your company, access goes by role, and your configuration belongs to your company alone.
The controls in place
What stands between your fuel data and anyone who shouldn't see it, from the cloud it runs on down to the record of who changed what.
Built on Google Cloud. FuelDeck™ runs in the cloud, so you install nothing and run no servers of your own.
TLS 1.3 protects data in transit; data at rest is encrypted with AES-256.
Each company's data is kept apart from every other company's. No account can see another's tickets or ledger.
Every user works under a role, so people see and change only what their role allows.
Your field rules and per-customer output mappings are configured for your company alone.
Customer credentials for portals and feeds are stored write-only and encrypted.
Every privileged action is logged. Administrative changes leave a record.
Security at a glance
The things an information-security reviewer asks about first, in one table.
| Hosting | Built on Google Cloud |
|---|---|
| In transit | TLS 1.3 |
| At rest | AES-256 |
| Tenancy | Per-tenant isolation |
| Access | Role-based access control |
| Configuration | Per company |
| Credentials | Stored write-only and encrypted |
| Audit | Privileged actions logged |
| Certifications | None held today. See the FAQ below |
| Single sign-on | Not available today |
Data handling & privacy
FuelDeck™ works with the operational records of fuelling, and nothing beyond what that job needs. Here is what enters the platform and how it is contained.
What FuelDeck™ ingests is fuel records: Excel, CSV and PDF files from portals, feeds and email, plus ticket images, along with the airline schedules and flight data used to check them. We process what it takes to account for fuel. We do not profile people.
Your tickets and ledger sit in your own tenant, and access within your company goes by role. No other customer can read or query your records.
Records stay as the traceable ledger your operations depend on, with the source document, review decisions and delivery status on every line, encrypted at rest with AES-256. Retention follows your agreement. Data can be exported or removed on request. The full detail is in our privacy commitments.
Security FAQ
What security and procurement teams ask us most often.
Talk to our team
We'll take your security and procurement teams through each control in place, encryption, isolation, role-based access and audit logging, and show the platform working, live.
Book a demo