Privacy notice · ODDBOUT

Who provides this plugin

The public plugin is published by 정환 고 for ODDBOUT. The ODDBOUT service is operated by Lucas Foundation. Contact turbo08@gmail.com for privacy questions or data requests.

Information received

Google sign-in provides your account identity, basic profile and email. Provisioned email accounts can also sign in; their passwords are sent directly to Supabase Auth over HTTPS and are not included in connector requests. The connector receives OAuth authorization and the tool arguments and files selected for an operation: fighter metadata, manifests, animation assets, submission identifiers and status requests. It does not require your Google password, generation-provider credentials or a local PC installation.

Why we use it

We use this information to identify the owner, enforce access to their own submissions, validate packages, process registration, serve registered fighters and investigate service failures or abuse. The connector’s authorization cannot be used as a general database or storage login.

Registration analytics

If you previously supplied an eligible Analytics context while signed in on the ODDBOUT website, a completed registration may send Google Analytics the existing Analytics client ID, an eligible session ID, event name and registration time. Sign-in email, account/submission/fighter IDs, authentication tokens and character files are not Analytics event fields. These website-to-registration records measure usage; they are not required to register. An authenticated website visit with Analytics opted out clears the saved link and cancels pending events.

Providers and public data

Google provides social sign-in. Supabase hosts authentication, registration data and storage. Render forwards the public MCP requests, including OAuth access tokens, to the fixed Supabase MCP server and processes package validation. GitHub Pages hosts the connection and information pages. OpenAI operates Dots and the connector host. These providers may process data outside your country. Registered character profiles, artwork, animation and gameplay packages are public; sign-in email and authentication tokens are not part of a public fighter package.

Retention periods

Account and ownership records, uploaded manifests and files, registration results, match history and deletion receipts currently have no scheduled automatic erasure. They are retained without a fixed time limit, including after a rejected or expired upload and after fighter deletion. An upload closes after 24 hours; this closes further uploads and does not erase files. Deletion confirmations are usable for 10 minutes and signed asset links expire within at most 10 minutes; expiry does not erase the underlying records or files. Registration analytics context and delivery-queue records in the ODDBOUT database are cleaned hourly once their last update or creation is more than 29 days old. This database cleanup is separate from any copies already processed by infrastructure or analytics providers.

Deletion and erasure requests

Fighter deletion in Dots removes the character from your active list, public rosters and new matches, and releases its slot. Private originals and history remain. To request access, correction or permanent erasure of account data or original files, contact turbo08@gmail.com. We verify ownership and review the requested scope, affected match history and any applicable preservation obligations before carrying out and confirming the request. A request, disconnection or deletion confirmation is not proof that files were erased. There is no automatic erasure deadline; data remains until erasure is actually completed. We explain any retained items in our response. Downloaded public copies cannot necessarily be recalled.

Contact safely

Include only the affected account email, public fighter ID and a short description. Never send passwords, OAuth callbacks, access tokens or signed download links. Changes to this notice will be published here.