Trust & Security
Client data, protected
at every layer.
Fueld runs on Google Cloud in the European Union. Every record is encrypted in transit and at rest, and our database denies access to any request that isn't explicitly permitted. Nothing is left to chance.
AES-256
Encryption at rest
TLS 1.2+
Encryption in transit
Google Cloud
Infrastructure
EU
Data residency
Deny by default
Row-level access
How data travels
From device to database, encrypted the whole way.
There is no point in the journey where client data sits unencrypted.
Client device
Wearables, food diaries and questionnaires are captured in the Fueld app.
Encrypted in transit
Data is encrypted before it leaves the device and stays encrypted end to end.
Google Cloud, EU
Processed on Google Cloud infrastructure hosted within the European Union.
Encrypted at rest
Stored with AES-256 encryption and protected by row-level security rules.
Built on Google Cloud's enterprise-grade infrastructure, hosted within the European Union.
Access control
No permission? No access.
Our database enforces security rules row by row. Every read and write is checked against explicit permissions before a single byte is returned.
Sarah M.
Your client · consent granted
James R.
Your client · consent granted
Another practice
Another practice
No relationship
Security rules evaluated on every request · deny by default
Deny by default
A request with no matching permission is rejected. There is no fallback and no generic read access.
Explicit permission only
You see a client's record because that client granted your practice access — and for no other reason.
Enforced at the database layer
Security rules are evaluated on every row, on every request, by the database itself — not by application code that could be bypassed.
No back doors
The same rules apply to everyone, including Fueld staff. Nobody browses client health data.
Data residency & GDPR
Stored in the EU. Governed by GDPR.
Client health data is stored on Google Cloud infrastructure within the European Union and processed under GDPR-compliant regulatory guidelines. It stays under European jurisdiction — full stop.
Lawful, fair and transparent processing
Data minimisation — collect only what's needed
Right to access and data portability
Right to erasure when data is no longer needed
Explicit client consent for every connection
Appropriate technical and organisational measures
Data Processing Agreement
You remain the data controller for your client relationships; Fueld acts as a processor. We provide a DPA for practitioners who require one.
Fueld is not a law firm and does not provide legal advice. You remain responsible for your own compliance with applicable privacy laws.
Security measures
The measures behind the promise.
Security isn't a feature we added. It's how the platform was built.
Encryption everywhere
AES-256 encryption at rest and TLS 1.2+ in transit. Client data is never stored or transferred in the clear.
Row-level security rules
Permissions are enforced per record by the database itself. Deny by default, on every request.
Google Cloud infrastructure
Built on Google Cloud's enterprise-grade infrastructure, hosted within the EU.
Authenticated requests
Every request is tied to a verified identity. Anonymous access to client data does not exist.
Backups & recovery
Automated encrypted backups with monitored disaster recovery, held to the same EU residency standard.
Deletion on demand
Client data can be securely and permanently deleted when it's no longer needed, supporting the right to erasure.
Common questions
Asked by practitioners like you.
All client health data is stored on Google Cloud infrastructure within the European Union, under GDPR-compliant regulatory guidelines. It is encrypted at rest with AES-256 and does not leave EU jurisdiction.
Only people with an explicit permission for that specific record. Our database enforces row-level security rules on every request — access is denied by default, and the same rules apply to Fueld staff. There are no back doors and no generic read access.
Yes, always. Data is encrypted with TLS 1.2+ from the moment it leaves a client's device, and stored with AES-256 encryption at rest on Google Cloud. There is no point in the journey where it sits unencrypted.
Fueld stores and processes data in the EU under GDPR-compliant regulatory guidelines. You remain the data controller for your client relationships; Fueld acts as a processor. A Data Processing Agreement is available on request.
Client data can be securely and permanently deleted when it is no longer needed, supporting the right to erasure under GDPR. Backups are held to the same standard.
No. Marketing and attribution systems are designed without transmitting health information. Where conversion tracking is used, only hashed identifiers are sent — never health data.
Have another question? Contact us