App secrets are write-only and encrypted with AES-256-GCM. Most destructive actions require explicit confirmation. dFlow redacts tokens and passwords in logs. Compliance status comes from the dFlow trust center.
Sections below describe how this control plane handles secrets, confirmation, and access. Compliance badges and cloud attestations still refer to dFlow Cloud at app.dflow.sh until this plane publishes its own.
You set a secret, but you can't read it back. We encrypt it with AES-256-GCM in our database. At deploy, we inject it as a Kubernetes Secret. A database password, a connection URL, and a saved GitHub token use the same cipher. A kubeconfig uses a separate key, also AES-256-GCM. Plain env vars are stored as text and are not encrypted.
02
Tokens and expiry
A workspace API token expires after 90 days by default. You can set that from 1 minute to 365 days. It cannot be set to never. A login access token lasts 15 minutes. The refresh token lasts 30 days.
03
Confirmation for destructive actions
Deleting an application or a database sends the header Confirm-Name, and it must equal the name. The CLI flag is --confirm-name. A restore uses that same header, and it must equal the source service name. Deleting a volume or a job sends confirm_name in the body. The CLI flag for those is --confirm, equal to the name. Revoking a token sends confirmation equal to the display prefix. Removing a member sends confirm_email. An MCP route delete checks confirm_host before the call. The HTTP route delete does not.
04
What we redact in logs
dFlow redacts bearer tokens, URL passwords and kubeconfig secrets.
05
Database backups
You can create a PostgreSQL backup on demand, list backups, and restore one. A restore sends Confirm-Name, and it must equal the source service name. When the object store driver is s3, a new PostgreSQL database also gets a daily backup at 02:00 UTC, kept for 7 days. An empty driver, or the filesystem driver, leaves a new database on the machine. Deleting the database does not delete a bucket copy. Valkey has no backup command.
06
What we don't promise yet
We offer no SLA and no uptime promise in the beta. A daily PostgreSQL backup runs only when the object store driver is s3. That copy is not an uptime promise.
07
Report a security issue
The trust center says: "Privacy or security questions? Email hello@dflow.sh." Read how to report a security issue. Email security concerns to hello@dflow.sh until a dedicated security mailbox is published.
08
Compliance status
From the dFlow trust center, read Nov 19, 2026: dflow.sh/trust ↗
SOC 2 is coming soon. Australian DPA and GDPR are compliant. Formal attestations apply to the surfaces dFlow operates. Customer cloud accounts and workload design remain your responsibility unless a signed agreement says otherwise.
SOC 2Coming soon
SOC 2 is a voluntary compliance standard for service organizations, developed by the American Institute of CPAs (AICPA), which specifies how organizations should manage customer data. The standard is based on the following Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy.
Australian DPACompliant
The Australian Data Protection Act outlines privacy requirements and data protection obligations for organizations operating within Australia.
GDPRCompliant
The General Data Protection Regulation, a comprehensive data protection law in the EU, governs how organizations must protect personal data and privacy.
Privacy and data processingAvailable
Our Privacy Policy describes how dFlow handles personal data. Contact hello@dflow.sh for privacy and data-processing questions.
Customer cloud and workload complianceCustomer responsibility
Workloads run in accounts, regions, and networks you select. Provider attestations and regulated workload design remain your responsibility.
Scope
dFlow Cloud is the control plane at app.dflow.sh. This page covers GDPR, the Australian DPA, privacy, subprocessors, and how to reach us. SOC 2 is coming soon. Australian DPA and GDPR are compliant.
The published trust center describes dFlow Cloud. This site is the new control plane; its security notes are on /security/ and /trust/.
09
Monitored controls
Here are the controls implemented at dFlow to ensure compliance, as a part of our security program.
Product security
Situational Awareness For Incidents
Vulnerability Remediation Process
Centralized Management of Flaw Remediation Processes
Data security
Termination of Employment
Inventory of Infrastructure Assets
Data Backups
Network security
Limit Network Connections
Transmission Confidentiality
Capacity & Performance Management
Data used in Testing
App security
Conspicuous Link To Privacy Notice
Secure system modification
Endpoint security
Malicious Code Protection (Anti-Malware)
Full Device or Container-based Encryption
Endpoint Security Validation
Corporate security
Code of Business Conduct
Organizational Structure
Roles & Responsibilities
Competency Screening
Personnel Screening
Security & Privacy Awareness
Performance Review
Automated Reporting
Incident Reporting Assistance
Assigned Cybersecurity & Privacy Responsibilities
Internal Audit using Sprinto
Segregates Roles and Responsibilities
Asset Ownership Assignment
10
Security policies
Here are the important security policies and documents which are a part of dFlow’s compliance program.
Data Classification Policy
Personal Data Breach Notification Procedure
Vendor Management Policy
System Acquisition and Development Lifecycle Policy
Incident Management Policy
Operations Security Procedure
Business Continuity Plan
Endpoint Security Policy
SDLC Procedure
Asset Management Procedure
HR Security Procedure
Data Retention Policy
Compliance Procedure
Access Control Procedure
Incident Management Procedure
PHI Data breach Notification Procedure
Vendor Management Procedure
Network Security Procedure
Asset Management Policy
Compliance Policy
Encryption Policy
Media Disposal Policy
Data Breach Notification Policy
Operation Security Policy
Organization of Information Security Policy
Access Control Policy
Information Security Policy
Communications & Network Security Policy
Acceptable Usage Policy
Risk Assessment & Management Policy
HR Security Policy
Physical & Environmental Security Policy
Code of Business Conduct Policy
Physical and Environmental Security Procedure
Business Continuity & Disaster Recovery Policy
System Description
The policy documents are listed on the trust center. They are not reproduced here. Trust center ↗
11
Subprocessors
The trust center lists 18 subprocessors for dFlow Cloud and shared platform services. See the list →
Get a beta invite.
The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.