Privacy notice
How Flow34 handles your data.
This notice explains local workflows, Pro licensing, payments and license recovery.
Use the official store links to check the currently available version. A submitted update is not a published release.
1. Scope
This notice applies to the 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.
This website stores your chosen language locally in your browser (flow34.site-language). This preference is not an identity or analytics identifier. Clearing this site's stored data removes the preference.
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.
Detailed error evidence
Detailed local evidence stays off until you explicitly enable it. Existing bridge preferences do not grant this consent.
During your X runs, this includes account and page identifiers, clicks, pointer/scroll/focus events, control keys (not typed text), interface details and, when permitted, a screenshot at an error. Screenshots may contain personal or private content. Nothing is automatically sent to Zero34 Labs; exports and the optional local bridge are separate choices.
Optional: declining does not restrict Free or Pro. Your choice is remembered and can be changed in Settings. Turning off stops new captures, but does not erase existing records. Clear them in History. Records are pruned on read/write to 20 incidents within 14 days.
Flow34 restricts the use and transfer of user data according to the Chrome Web Store User Data Policy, including its Limited Use requirements. Data serves only the disclosed functionality and support, not advertising, resale, profiling or credit decisions.
5. Pro licensing and payments
Flow34 Pro payments are handled through Whop. Whop may ask you to create or sign in to an account during checkout; its own privacy terms also apply to payment and billing data. Flow34 does not store payment-card details directly.
The licensing system on Cloudflare Workers and D1 processes customer, subscription, license and plan identifiers; entitlement status, limited Whop references, the date of the first successful payment, random installation IDs and security records. Licenses are ordered by purchase date and active installations are shown separately for each license. X content, X session data and local workflow history are not sent to the licensing system.
If you lose your license, you may request a single-use verification code sent to your purchase email address. The code expires after 10 minutes and is delivered through Resend; the license key itself is not emailed. Your email address is processed for matching and delivery; the Flow34 database stores a keyed digest rather than the plain address. The code and IP address are also stored only as digests.
Subscription management
After email verification, a 15-minute authorization lets you stop or resume auto-renewal through Whop from this site. It stays in page memory. To prevent duplicate changes, the server records the membership ID, random action ID, requested setting and time. Daily cleanup removes records older than 24 hours; these records contain no email, license key or authorization token.
Pre-checkout email verification
Before a new purchase, Flow34 may send a one-time verification code to the email address you provide through Resend. The code expires after 10 minutes. The licensing service stores keyed digests of the email address, code and IP address, not the plaintext values, and removes challenge and request-guard records older than 24 hours during daily cleanup. A verified address is kept for up to 45 minutes in a signed, HttpOnly browser cookie. Flow34 checks that address against the email entered in Whop’s payment form and, after payment, against the buyer email returned by Whop. If they differ, automatic license display stops and support is required. Flow34 does not store card details or email your license key.
7. Retention and deletion
Local audit and diagnostic records are limited by product settings; you can remove supported local records within Flow34. License activation attempts and recovery code/attempt records older than 24 hours are removed by the daily cleanup, released installation records after 30 days, and completed webhook processing records after 90 days. The keyed email-to-customer digest is kept during the membership; active license and necessary payment-mapping records are kept for service delivery and applicable legal obligations. Whop’s own retention terms apply to its records. Contact us for access or deletion requests.
8. Security
Flow34 is designed to limit permissions to needed features, avoid remotely hosted executable code and verify licensing requests. Recovery codes are short-lived and subject to attempt limits. 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 [email protected]. Current product and policy status is maintained on the support page.