01
Private by default
Buckets are private, downloads use short-lived signed URLs, and each request is checked against the owning practitioner account.
Trust Center
/ Last reviewed 07 Oct 2026
Clinical data deserves a clear answer.
This is how LogHeal handles the records, documents, and account information entrusted to it by independent healthcare professionals. No inflated badges. Just the controls, providers, and policies we can explain.
Data region
EU-first infrastructure
Primary application, database, and document storage are configured for Europe.
Clinical fields
AES-256-GCM
Designated health fields are encrypted before database storage.
AI training
Not used
Patient and clinical data are not used to train AI models.
Access model
Single-practitioner
Each professional is isolated from every other customer’s records.
How we operate
Fewer promises. Better boundaries.
LogHeal is built for a single practitioner working across one or more clinics. That shape matters: it keeps ownership explicit and avoids shared patient pools by default.
We do not claim SOC 2, ISO 27001, HIPAA certification, or another
independent certification unless it is listed here with evidence.
02
Useful access, not open access
LogHeal personnel do not have routine access to clinical records. Exceptional support access is limited to the operational need and protected by confidentiality obligations.
03
Deletion with a recovery boundary
Patient deletion removes the record from normal access and enters a 90-day purge process. Account closure removes active database records and associated R2 document objects.
04
No secondary clinical use
Clinical data is not sold, advertised against, profiled, or used to train AI models. Product views that calculate information for the practitioner are part of the service.
Infrastructure map
Who helps LogHeal run?
These providers support specific parts of the service. They do not receive a general-purpose license to use clinical data.
ProviderRoleLocationData boundary
Neon
Role
PostgreSQL database and backups
Location
Frankfurt, EU
Data boundary
Account records, encrypted clinical records, appointments, metadata
Render
Role
Application hosting
Location
Frankfurt, as documented
Data boundary
Requests in transit, runtime infrastructure, operational logs
Cloudflare R2
Role
Private document storage
Location
EU region to verify
Data boundary
Clinical documents and temporary export files
Paddle
Role
Subscription billing
Location
Ireland
Data boundary
Billing identifiers and subscription status; no card data stored by LogHeal
Resend
Role
Transactional communication
Location
United States
Data boundary
Account email and non-clinical service messages only
Sentry
Role
Consent-gated error monitoring
Location
United States
Data boundary
Technical error data; patient data is stripped before transmission
Twilio
Role
Appointment SMS reminders
Location
Europe reported; routing to verify
Data boundary
Telephone number, reminder text, and delivery metadata
Google OAuth
Role
Optional sign-in
Location
Role and region to verify
Data boundary
Email address, Google account identifier, and basic profile data
Exact provider contracts, transfer safeguards, and current sub-processor records are available for customer due diligence on request. Google OAuth’s role and exact provider routing remain under review.
Due diligence kit
Start with the documents that matter.
Read the public policies first. If you are evaluating LogHeal for real patient work, request the customer DPA and the current provider register from support.
Trust is a process, not a badge.
This page changes when our processing, providers, or controls change.