Privacy notice
How data is handled: browser-local by default, with the static-host, user-selected-integration and support boundaries disclosed. Formal controller details are being finalized.
Application-managed API specifications, mappings, scenarios, run history, evidence and settings are stored in your current browser profile by default. There is no default vendor workspace-sync account service. Browser storage can be cleared; export an encrypted recovery bundle and test restore.
This local-first default does not remove other processing boundaries:
- the static host can process ordinary request metadata such as IP address, time, path, user agent and response status;
- explicit REST, GraphQL, realtime, URL-import/watch and Companion operations contact destinations you select or configure;
- configured webhooks can run while the application is active;
- external navigation and mail actions leave the application only after your action;
- the first-party error boundary creates a minimized local diagnostic and has no remote sink by default.
The ordered Trust manifest — not a global “no network” claim — is the technical source of truth. See the Trust Center for the audited boundary inventory.
Browser-local workspace access, rectification, export and erasure are available in Settings. These product controls do not replace a controller’s formal response process for hosting, support, sales or licensing records — that process is part of the pending sign-off.
No advertising or cross-site tracking cookie is declared by the application. The product is professional integration tooling and is not designed for children; the final notice will define any applicable age restriction.
A verified privacy intake channel and identity-verification procedure are being finalized. No response-time or delivery promise is published yet, so an active contact address is intentionally not shown here.