Privacy Policy — 0xtnp Flow Studio

Last updated: October 6, 2026

0xtnp Flow Studio helps users operate generation queues in Google Flow or ChatGPT, manage reference images, save results locally, and optionally repair refused Flow prompts. Cloud repair is optional and is 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 your Flow tab; the extension cannot verify which tab you selected.

The extension does not intentionally collect general browsing history, personal communications, payment records, location, or account passwords for analytics. 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.

Generation services

When you start a generation, prompts and selected reference images are submitted to the platform you selected: Google Flow or ChatGPT. That platform processes your input and creates results under its own terms and privacy policies. Flow repair is not used for ChatGPT generation. 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.

Cloud records and retention

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, troubleshooting, security and usage limits. Current server repair/usage records remain until removed by the operator; there is no automatic deletion period for those records in this release. 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.

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 and repair features, manage access and limits, and troubleshoot the service. 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 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. 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.