Pre-release privacy notice
Privacy, explained before launch.
This notice describes Flow34’s current local-first design and clearly separates it from payment and licensing features that are not yet active.
Current status: Flow34 is preparing for public release. It does not currently sell Pro access or operate a production licensing service. This notice will be updated before those systems collect data.
1. Scope
This notice applies to the planned Flow34 — Workflow Assistant for X browser extension, published by the independent software brand Zero34 Labs. Flow34 is not affiliated with, sponsored by or endorsed by X Corp.
2. Data Flow34 accesses
On supported X pages, Flow34 processes interface elements visible in your signed-in browser session. These may include visible account identifiers, post identifiers, button states, route information and visible warning or verification states.
Flow34 does not ask for your X password. It is not designed to read X cookies or session tokens for transmission to a remote Flow34 service.
3. Data stored on your device
Flow34 may store the following in browser-local extension storage:
- Language, theme, limits, delays, filters and safety preferences.
- Jobs, schedules and Autopilot plans you create.
- Local audit entries containing action, result, time and a limited target identifier.
- Rolling 24-hour quota records and duplicate-prevention memory.
- Safe technical event summaries used for local diagnostics.
- Versioned JSON backup data you choose to import.
Core workflow data is not automatically sent to Zero34 Labs. You can clear supported local records from the extension. Removing the extension also removes its local extension storage according to normal browser behaviour. You are responsible for files you export.
4. Diagnostics
The production design can operate without a remote diagnostics endpoint. If optional remote diagnostics are introduced, sending will require an explicit user choice and a preview of the sanitised report.
A permitted report may include extension version, browser and operating-system family, interface language, error or action codes, safe counters and technical durations. It is designed to exclude X usernames, post or direct-message text, page URLs, browsing history, cookies, tokens, passwords and Flow34 job identifiers.
5. Planned Pro licensing and payments
Payments and production licensing are not active today. Before Pro sales begin, this notice will name the selected merchant, processors and relevant service providers, their roles, retention periods and any applicable processing locations.
The planned minimum licensing data includes purchase email, Flow34 customer and licence identifiers, plan and entitlement status, a limited payment-provider reference, random installation identifiers and necessary security records. Flow34 will not store payment-card details directly. X content, X session data and local Flow34 workflow history are not planned licensing inputs.
7. Retention and deletion
Local audit and diagnostic records are automatically limited according to documented product settings. You can remove supported local records from inside Flow34. Licensing, payment and support retention periods will be published before those services launch.
8. Security
Flow34 is designed to limit permissions to supported features, avoid remotely hosted executable code, keep payment-card data outside its own systems and verify future licensing requests. No system can guarantee absolute security.
9. Changes
This notice will change when Flow34’s data flows, providers or legal structure change. Material updates will include a revised date and, when appropriate, an in-product notice.
10. Contact
Zero34 Labs is currently an independent developer brand, not a representation of an incorporated company. Privacy and product-support questions can be sent to support@zero34labs.com. Current product and policy status is maintained on the support page.