Trust Center
Security at Wavelength
Effective October 6, 2026.
Wavelength turns spoken process descriptions into diagrams. Your calls and your diagrams are business data. This page tells you how we protect them.
How we protect your data
- Encryption. All traffic to Wavelength uses HTTPS (TLS). Our database provider encrypts stored data with AES-256.
- Access control. Your browser cannot read our database directly. Every request goes through our server functions. Each function checks who you are from a verified sign-in before it reads or writes private data. A request without a valid sign-in gets no private data. Public share links, embeds, and client portals open without sign-in, by design. They show only what the owner chose to publish.
- Account isolation. You see only your own flows and the flows that a person shares with you.
- Payments. Stripe processes all payments. We never see or store your full card number.
- Usage limits. Our AI endpoints have per-account and per-minute limits. These limits stop abuse and runaway costs.
- Backups. Our database provider backs up the database every day.
Where your data lives
- We store your account and your flows in the United States.
- Our core infrastructure vendors hold SOC 2 Type II reports. See the full list on our Subprocessors page.
Your call audio and AI
- Read our AI and Data page for the full details.
- In short: we do not store your audio, and we do not train AI models on your content.
Sign-in and connections
- Passwords. Our authentication provider stores your password in hashed form. You can also sign in with Google.
- AI connector. Claude, ChatGPT, and other MCP clients sign in with OAuth. Each tool acts only as you, with the limits of your plan. In Settings, then AI connector, you can turn on read-only mode so that AI tools can read and export your flows but never change them.
- Google Drive. Wavelength asks only for the drive.file scope. It can open only the files that you pick or the files that Wavelength creates.
- Channels and webhooks. Wavelength stores each channel webhook URL encrypted. A channel webhook can post a flow. It cannot read the channel.
- Shared links. A public link shows a read-only copy of one flow. You can stop sharing a flow at any time. Flow image links expire after 30 days.
- Organization sharing. When an organization turns sharing off, its public links, embeds, client portals, and flow image links stop working, and its invite links are cleared. When an organization turns off public publishing, its public pages and client portals stop working.
Deleting your data
- When you delete a flow, its transcript, diagram, and version history are deleted with it.
- You can delete your account and all its data in the app, at any time.
- We post changes to our subprocessor list 30 days before they start.
Compliance
- We are working toward SOC 2. We do not hold a SOC 2 report today. See the status of each item in our Trust Center.
- We sign a Data Processing Agreement (DPA) with customers who ask. Our DPA covers GDPR.
- Contact us for a completed security questionnaire.
- Our support SLA gives our support hours, first response targets, and how we report the state of the service.
Report a security problem
- Email support@wavelengthflow.com with the subject "Security".
- Tell us what you found and how to reproduce it.
- We reply within 2 business days.
- Please do not access, change, or delete other users' data while you test.
Incidents
- If a breach affects your personal data, we tell you without undue delay. We tell you within 72 hours after we confirm the breach.
Questions from your security team?
Email support@wavelengthflow.com or open the Trust Center.