Privacy Policy — 0xtnp Flow Studio
Last updated: November 15, 2026 (new address, Send to support, order emails)
The website is 0xflow.app and the developer's server is reached at api.0xflow.app. The earlier address, repair.corethea.com, is the same server and still answers for older versions of the extension.
0xtnp Flow Studio helps users operate generation queues in Google Flow, ChatGPT, Gemini or Grok, manage reference images, save results locally, optionally repair refused prompts, and optionally write story packages with the Story Builder. Cloud repair, sign-in and the Story Builder are optional and are operated by the extension developer at https://repair.corethea.com.
Information handled on your device
The extension processes your prompts, selected images, generation page content and status, generated media, filenames, and folders you choose. Preferences, repair configuration, automation tab identifiers, an anonymous installation key, and cloud repair access tokens are stored locally in Chrome. Prompt and image drafts are session data. Cloud access tokens are generated for this service; they are not your Google, ChatGPT, or AI account passwords or session credentials.
Optional background mode asks you to select a browser tab through Chrome's sharing dialog. That stream stays locally inside the extension. It is not recorded, saved, analyzed, or sent to the developer. Audio is not captured. Sharing stops when you stop it, the queue finishes, or the panel closes. Choose only the tab you want to keep running (Flow, ChatGPT, Gemini or Grok); the extension cannot verify which tab you selected.
The extension does not intentionally collect general browsing history, personal communications, location, or account passwords for analytics, and it never asks for card numbers, bank or wallet logins. Payment receipts are only received when you choose to upload one (see "Pro purchases, coffee donations and the free daily limit"). Prompts and reference images may contain personal information that you put there; avoid including sensitive information unless you intend to share it with the generation or repair services you choose.
Optional sign-in with Google or Discord
Sign-in is needed for the Story Builder, Pro purchases and account features such as connected devices. Generation, saving and cloud repair work without it, and repair stays tied to your anonymous installation.
Google. If you choose Sign in with Google, Chrome opens Google's sign-in page and the extension receives a Google ID token, which is sent to the developer's server and checked with Google. The extension asks only for basic sign-in information (the "openid", "email" and "profile" scopes). The server stores your Google account ID, email address, display name, the time you first and last signed in, your plan (Free or Pro) and its end date, and a link between your Google account and your installation. Your profile picture, contacts, Gmail, Drive or other Google data are not requested or stored. Your Google password is never seen by the extension or the developer.
Discord. If you choose Sign in with Discord, Chrome opens Discord's consent page and the server exchanges the result for Discord access, using the "identify" and "guilds.members.read" scopes. The server stores your Discord user ID, your Discord display name, whether you are a member of the developer's community Discord server (used for Discord Pro access), when this was last checked, and a Discord refresh token so membership can be re-checked about once a day. Your messages, friends, other servers and email address are not requested or stored. If you leave the community server or revoke access, the next check returns your account to the Free plan.
Connected devices. While signed in to 0xFlow, the extension registers its browser installation with the server using your optional device name, browser name, operating-system family, extension version and connection timestamps. This lets you view installations linked to your account and sign out an old installation from Settings. A browser profile counts as an installation; this is not hardware fingerprinting. Device labels are self-reported, and no generation-platform passwords or cookies are collected. Removing a device ends its 0xFlow account link; it does not delete local projects or sign out its other websites. Installation metadata may remain until account/service data is deleted.
The extension keeps only your sign-in state for display. Sign out removes the link between your installation and the account. You can also revoke access at any time in your Google Account settings (Security, third-party access) or in Discord (User Settings, Authorized Apps).
Story Builder
When you create a story, the extension sends the template, your topic or plot, and your setup choices (for example niche, language, number of scenes and style) to the developer's server. The server builds the story package with an AI engine: Google's Gemini through the signed-in AGY engine by default; if Gemini cannot finish, Z.ai's GLM model (sent to Z.ai's API through the Claude Code command-line tool, which only relays the text and runs no tools); and OpenAI as the last fallback. A fallback is used only when the previous engine fails, so your story input can reach more than one of these providers for the same build; each processes it under its own policies. Z.ai (Zhipu AI) and OpenAI may process your story input outside your country. Do not put private information in a topic or plot that you would not want an AI provider to process.
The server stores each build job (your inputs, the generated script and prompts, its status and the engine used) linked to your installation and signed-in account, so you can return to it. Finished, failed and cancelled build jobs are deleted from the server automatically 7 days after they end. The server also counts your stories per day for plan limits (Free accounts: 2 stories per day, not counting failed or cancelled builds; Pro and Discord Pro have a higher fair-use limit). When you sign in, the server records the sign-in event with your IP address and the account used, kept for 30 days, to monitor and prevent the creation of many accounts to farm free stories; these records contain no story content. Your saved projects and the images you generate for them are stored locally in your browser (IndexedDB) and are not uploaded to the developer.
Generation services
When you start a generation, prompts and selected reference images are submitted to the platform you selected: Google Flow, ChatGPT, Gemini or Grok. That platform processes your input and creates results under its own terms and privacy policies, using the account you are signed in with on that site. Generated files are saved through Chrome Downloads or to the local folder you choose. If a temporary download is successfully copied and verified in your selected output folder, the extension may remove the temporary copy; your saved output remains.
Optional cloud repair
When you click Connect cloud repair, the extension requests permission to connect to the repair server over HTTPS. Your browser creates a random installation key and the server issues a separate access token. No name, email address, Google login, or manually entered access code is required.
When cloud repair is enabled and Flow refuses a prompt, the extension sends that prompt, its original text, the Flow warning, previous repair revisions and diagnoses, the repair round number, and request/prompt identifiers to the repair server. The server uses its signed-in AGY engine to send this repair context to its configured AI provider (currently Google's Gemini). The provider processes that text under its own policies. The returned revision is checked against references, timing and dialogue constraints before another generation attempt. AI responses are handled as text and are not executed as extension code.
Reference image files, generated videos, and the optional background tab stream are not uploaded to the repair server. Repair is not an offline feature. Cloud repair is associated with your anonymous installation, not a verified person; daily limits and registration restrictions apply.
Pro purchases, coffee donations and the free daily limit
Free daily limit. From version 1.13.37 the free plan includes 20 saved results per day across all engines. After each saved result the extension tells the server that one result was saved, together with the engine name (for example Flow or ChatGPT) and whether it came from a normal queue or a Story Builder project. The server stores only a count per anonymous installation (or signed-in account) and day. No prompt text, images or videos are sent for this count.
Buying Pro. Pro is attached to your signed-in Google or Discord account. When you start an order, the server stores an order with a reference code, your account ID, the e-mail address and name of that account, and later the plan and price you choose. You pay in your own wallet app (Binance Pay, GoTyme or Maya); the developer never receives your card details, wallet login or password. You then upload a screenshot of the payment receipt and may add a short note. The server stores the receipt image, the note, the payment method you chose, the time and the IP address used for the upload (to prevent abuse). The developer checks the payment by hand in the wallet app and approves or rejects the order; the decision and an optional reason are stored and shown on your order page. A receipt may show your wallet name, number or other details: crop anything you do not want to share before uploading.
Coffee donations. The optional form on the Buy me a coffee page lets you send a donation screenshot with a name, e-mail address and message so the developer can thank you and keep records. Donations are separate from Pro.
Who sees it and how long it is kept. Orders, receipts and donation records are stored privately on the developer's server and are visible only to the developer and the developer's support team through a password-protected admin page. The support team does not see the e-mail address of paid orders. They are not sold or shared, except where required by law. They are kept for bookkeeping and tax records. You can ask the developer to delete a receipt image; order records needed for accounting may be kept.
Affiliate program. Members who apply have their account ID, referral code, application status, accepted terms, commission rates and commission/payout records stored for administration and bookkeeping. Affiliates see only their own earnings and payout references, not buyers' names, emails or receipts. If you save payout details, your chosen payment method (GCash, GoTyme, Maya, BPI or BDO), account holder name, account/mobile number and update time are stored privately for manual transfers and are visible only to you and the owner through authenticated pages. You can update or remove these details from your affiliate dashboard while your membership is active or pending; suspended members can contact the owner for changes or deletion. We never request card numbers, bank logins, passwords, PINs or OTPs. When you open a valid referral link, a signed first-party cookie remembers only the referral code and its expiry for 30 days in that browser profile. It fills the optional checkout code, which you may change or remove before sending a receipt. The code attached at submission is stored with the order and its commission rate. This is not general browsing analytics or cross-browser tracking. Clear the site's cookies to remove the remembered suggestion. Referral and payout records needed for accounting may be retained.
Order e-mails. The server sends e-mails about your own orders to the e-mail address of your signed-in account: a receipt (with a PDF) when your Pro order is approved, at most two reminders when you open checkout and do not finish it, and a reminder shortly before and after your Pro ends. Every reminder has a "Don't remind me again" link that stops them. The e-mails are delivered by Resend, an e-mail delivery service, which receives your e-mail address, name and the e-mail content for that purpose.
Send to support
In Debug logs you can choose to send a support report. Before anything is sent you see a preview. The report contains recent debug log lines, the extension version, the platform you use, selected panel settings (for example engine, mode, model, aspect ratio and video length) and your optional note. E-mail addresses, sign-in tokens, keys, web-address details and folder names with your user name are removed before sending. The report is linked to your installation and, if you are signed in, to your account.
The server reads the report with an AI model from Anthropic (Claude) to write an answer and, when a panel setting is the likely cause, to suggest a change. Nothing changes until you press Apply fix, and only panel settings can be changed; the old values are kept in Debug logs. Reports are kept for 30 days and are used to answer you and to find common problems. You can send up to 5 reports a day.
Cloud records and retention
For cloud repair, the server stores hashes of installation keys and access tokens, anonymous installation IDs, daily repair counts, job identifiers, repair results, and repair history containing original/revised prompts, warnings and diagnoses. Repair records are separated by installation. Another installation cannot fetch your repair jobs, and your history is not used as another installation's repair examples. Access tokens expire after 14 days and can be renewed automatically. Reconnects and Disconnect do not reset usage or erase server records.
The web server receives your IP address as part of normal HTTPS traffic and may keep operational access logs. Registration limits use a daily salted hash of the IP address rather than placing the raw IP address in the registration database. These records support repair delivery, sign-in, the Story Builder, troubleshooting, security and usage limits. Repair and usage records, and sign-in account records, remain until removed by the operator or at your request; Story Builder jobs are deleted after 7 days as described above. Contact the developer for questions or a request to remove cloud records. Do not post access tokens or private prompt text in a public support issue.
Optional local companion
If you select Local companion under Advanced connection settings, repair uses the companion installed on your computer and its signed-in AI account. The companion sends the refused prompt, warning, repair context and selected successful local repair examples to its configured AI provider. It stores repair history locally, including prompt text and diagnoses. Outcome records contain prompt fingerprints and metadata; operational diagnostics may be stored in native-host/host.log. Local files remain until you remove them. The optional developer helper can use a local pairing token. Local companion repair does not send requests to the developer's cloud repair server.
User controls
Repair is off by default on a fresh installation. You can enable or disable it in the Repair tab, disconnect cloud access, or select the optional local companion. Disabling repair stops future repair requests but does not retract content already sent to a provider or delete existing records. Disconnect revokes the current cloud access token while retaining the installation identity and usage. Sign out is available in the Story Builder and in Settings.
You can remove the extension through Chrome's Extensions page. Removing it clears its local configuration but does not automatically delete cloud records or saved media. Uninstall Repair.cmd removes the optional companion's browser registration; it does not erase its history or generated files. You may remove local history and logs yourself. Avoid sharing history folders if they contain private prompts.
Use and sharing
The developer uses information to provide generation, saving, repair, sign-in and Story Builder features, manage plans, purchases, access and limits, and troubleshoot the service. Your e-mail address is used only for the order e-mails described above and is not used for other marketing. The developer does not sell user data, use it for advertising or unrelated purposes, or use it for creditworthiness or lending decisions. No advertising tracking or general browsing analytics is included. Transfers to generation and AI providers (Google, Z.ai, OpenAI, Anthropic for support answers, Resend for order e-mails, Discord for membership checks, and the generation sites you choose) support the features you request; those providers have their own privacy policies.
Use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including its Limited Use requirements.
External links and contact
Links to companion downloads, installation documentation and the developer's Facebook page open third-party sites governed by their own policies.
For privacy questions or to arrange a cloud-record removal request, contact the developer at https://github.com/0xtnpxsgt/flow-studio-repair-companion/issues. You can ask for your sign-in account (Google or Discord) and Story Builder records to be deleted. Do not include private prompts, installation keys, passwords or access tokens in a public issue. A private verification method must be arranged before disclosing sensitive information or processing a record removal request.