Who operates this plugin
Lucas Foundation operates AI Fighter Creator and the connected ODDBOUT fighter service. This notice covers the plugin, its policy pages and connected registration features. Privacy contact: turbo08@gmail.com.
Codex, your generation providers and other independently operated services have their own policies. Installing a local plugin does not mean that everything you share with the assistant stays only on your computer.
Data stored on your computer
The plugin keeps project briefs, reference and artifact file paths, copied asset versions, selected versions, review evidence and feedback, game-context revisions, profile drafts and job records. Job records may contain command arguments (including prompts), provider choices, input/output hashes, file sizes, timestamps, process status and diagnostic output.
These records let you resume a project, preserve decisions, inspect uncertain jobs and validate the actual files. The default workspace is ~/.ai-fighter/creator/workspace/; a configured workspace may differ. Bundled runtime files are stored separately under ~/.ai-fighter/creator/runtimes/.
If you sign in to ODDBOUT, access and refresh tokens plus public service configuration are stored in ~/.ai-fighter/client.json, or a configured session path. Provider credentials remain in the locations managed by the provider tools. Do not include these files in fighter packages, public issue reports or screen recordings.
What the assistant receives
MCP tool inputs and responses are exchanged with the host assistant. Depending on the request, responses can include project briefs, profile text, file paths (including absolute paths), job commands and logs, review notes, evidence paths, versions, timestamps, checksums, validation errors, fighter identifiers, submission status and registered fighter records. These fields can contain personal information you put in a brief, filename, prompt or diagnostic message.
The assistant may also open files or previews you ask it to inspect. OpenAI handles conversation content and tool output according to the product, account settings and terms you use. This plugin does not override those controls. OpenAI privacy policy.
The creator-homepage tool can return a one-use sign-in link, valid for ten minutes. It is sensitive account access information: open it yourself and do not publish or forward it.
When information leaves your device
| Action | Information and destination | Purpose |
|---|---|---|
| Read current requirements | Public game-context requests to the configured GitHub or ODDBOUT endpoint; ordinary request metadata. | Use current game rules and review gates. |
| Set up generation tools | Package requests and technical connection metadata to the relevant package registries. | Install the required local environment. |
| Generate an image or video | Prompts, selected reference files and request/account metadata to your chosen provider, such as OpenAI or xAI. | Produce the assets you requested, under that provider’s policies and usage terms. |
| Sign in | Google account identifier, email and basic profile information, which may include a name or picture, to ODDBOUT authentication through Supabase. | Authenticate and associate submissions with their owner. We do not receive your Google password. |
| Register a fighter | Manifest, profile, artwork and animation files, ownership, timestamps, hashes and validation/moderation records to ODDBOUT through Supabase and its validation worker. | Validate, publish, run and moderate your fighter. |
| Contact support | Your address, message and attachments to the support mailbox. | Respond to your request. |
Preparing a job records a proposed command; it does not itself run generation. Generation requires a separate local execution step. The plugin does not automatically submit every project to ODDBOUT.
What becomes public
When a fighter is successfully registered, its public profile, artwork, animations and game configuration can be displayed, downloaded and used in the game. Fighter identifiers and public match/ranking records may also be visible. Your sign-in email and authentication tokens are not public fighter profile fields.
Only register material you intend to share. Removing a fighter from the service cannot recall copies already downloaded or shared by others. Local drafts are not automatically registered.
Service providers and locations
The connected service uses Supabase for authentication, database, storage and APIs; GitHub Pages for static hosting; Render for package validation; and Google for sign-in and support email. The provider you choose processes generation inputs separately. Hosting and service providers may process IP addresses, user-agent data, request times and operational logs.
Supabase · GitHub · Render · Google · OpenAI · xAI
Processing may occur outside your country. The relevant location and safeguards depend on the configured service and the provider account you use. Contact us for information about our service arrangements. We may disclose information when required by law or necessary to address fraud, abuse or a security incident.
These policy pages contain no analytics scripts, advertising trackers or embedded third-party media. The plugin has no separate analytics telemetry collector. Ordinary hosting logs and your host/provider’s data practices still apply. We do not sell personal information or collect payment-card details through this plugin.
Retention and deletion
- Local projects and job history: remain until you remove them. There is no automatic project expiry. Uninstalling the plugin does not by itself erase the separate workspace, runtime copies or provider data.
- Local sign-in: logging out removes the session file and attempts server-side session revocation. It does not delete your account, projects or registered fighters.
- Service account, fighter and match records: retained while needed to provide the service, maintain match history and handle support, security or moderation. Request removal or account deletion through support; remaining legal, security or record-integrity needs are assessed when processing the request.
- Logs, support messages and backups: retention depends on the purpose and relevant provider settings. Backups may expire later than active records. An expired upload or hidden fighter is not a guarantee that all underlying files have been erased.
We do not promise a fixed deletion deadline or claim an automatic account-deletion feature that the service does not provide.
Your choices and requests
You can use local project tools without ODDBOUT sign-in, decline generation, stop before registration, remove local files, log out or disconnect Google access. Disconnecting an account does not erase data already stored by ODDBOUT or other providers.
For access, correction, a copy of your data, fighter removal or account deletion, email turbo08@gmail.com from your account address. Include relevant fighter IDs or public links. We may ask for information needed to verify ownership; never send a password, token or a copy of your session file. We explain any retention that prevents fulfilling a deletion request in full.
Depending on applicable law, you may have additional rights to object, restrict processing, withdraw consent or complain to a data protection authority. Requests about your Codex conversation or generation-provider account should also be directed to that provider.
Children and changes
This service is not directed to children under 13. Applicable local age requirements and the requirements of your host and generation providers also apply. Contact turbo08@gmail.com if a child has supplied personal information.
Changes to these practices will be reflected in the notice date. Material changes will be communicated through the service or another appropriate channel.