ChatGPT Duel privacy

Controller and purpose

Lennard Bugajski, Sigmund-Bergmann-Str 1, 13587 Berlin, Deutschland; contact [email protected]. The service processes the data needed to connect your guest, operate and record your requested fictional Duel, secure the service and answer support requests.

Service processing is based on the requested service (GDPR Art. 6(1)(b)); proportionate security/diagnostics on legitimate interests (Art. 6(1)(f)); legally required processing on Art. 6(1)(c). Technically necessary browser storage supports the explicitly requested connection and archive. Optional processing requiring consent must remain separate.

What Sol Sandbox receives

A random guest identity; OAuth client/connection information, token verifiers, expiry/revocation state; narrowly scoped tool inputs; fictional order sizes and IDs; confirmed executions, chart history, results and Match Review; necessary browser/seat binding and private Trading Memory ownership. The server receives tool calls, not your entire ChatGPT conversation or private model reasoning.

Process-level operational metrics count connections, phases, tool latency/errors, capacity and health. They do not include chats, secrets, invitation tickets or behavioral advertising. Hosting/security providers may process IP addresses and request metadata separately for delivery and abuse protection.

Providers and transfers

Railway hosts the service and persistent storage; Cloudflare provides the existing website’s delivery/security layer. OpenAI operates your ChatGPT client and applies its own privacy terms. The production application and PostgreSQL run in Railway’s sfo region (United States); the independent PostgreSQL backup bucket is in sjc (United States). Provider processing agreements and applicable safeguards are described in Datenschutz.

Cloudflare Web Analytics is disabled. No Web Analytics measurement beacon is automatically inserted for this website. Cloudflare continues to process delivery, traffic and security information for the existing CDN and abuse protection; disabling Web Analytics does not disable those services or delete their separate records. Any previously collected Web Analytics data remain subject to Cloudflare’s existing retention: seven days of unsampled measurements and up to six months of accessible reduced history. This is separate from our internal 31-day game-event statistics. Cloudflare Web Analytics information.

Internal gameplay and reliability statistics

When enabled, our limited server-side statistics help us understand Normal Mode and Duel usage, interrupted games, repeat rounds and technical problems, and improve the simulator. Existing Trading Memory records also contribute separate aggregate archive figures; these represent recorded games rather than all usage.

We record keyed pseudonymous run/round and event identifiers, an optional rematch link, fixed event category, game mode, regular/test/unknown classification, server timestamp and duration at explicit completion. Human executions, MCP-controlled rivals and participating bots are counted separately. Separate Normal runs are not linked into a visitor profile. Rematches can be linked. These data are pseudonymised, not claimed to be anonymous.

The internal event statistics contain no IP address, user agent, names, profile/wallet IDs, ChatGPT conversations or hidden reasoning, simulated balances or order amounts, OAuth tokens or session secrets. The existing canonical game records and hosting logs remain separate. This server-side recorder adds no consumer analytics cookies, browser identifiers or tracking scripts. Cloudflare Web Analytics is disabled; ordinary delivery and security processing remain separate.

Processing is based on GDPR Article 6(1)(f). Our legitimate interest is understanding and improving gameplay adoption and technical reliability through limited statistics. There is no advertising profile, sale, individual ranking decision or connection to your activity on other websites. Estimated interaction time is not precise screen time.

New event records expire after 31 days in an hourly cleanup, with up to one additional hour in normal operation. Operational configuration and overwritten health counters remain while the feature is operated. Canonical game-record retention is unchanged. Automatic PostgreSQL recovery backups retain four weekly full backups and fourteen differential backups, with archived WAL: approximately four weeks of rolling recovery. Deleted events may therefore remain in backups for approximately four additional weeks. Separate encrypted maintenance/recovery exports are outside this automatic rotation and are retained for at most 30 days from their backup cut. A documented, restricted extension is permitted only while verified safe recovery would otherwise be lost or a legal exception requires it. Deletion from the live database does not delete those copies. Recovery requires reapplying due deletions before public activity resumes.

Railway hosts the statistics on the existing infrastructure. The recipient and international-transfer information on this page applies. The operator dashboard is restricted to local aggregate reads through an authenticated connection. Small counts can still allow inferences. Local snapshots are replaced on refresh and are not a public statistics archive.

Use the controller contact on this page to exercise access, rectification, erasure, restriction and applicable rights, including objection to processing based on legitimate interests. We use available lawful ownership information; do not send credentials or full invitation links. We do not collect extra permanent identity data solely for statistics. Complaint rights remain unchanged.

Actual retention contract

• Authorization requests: 10 minutes; authorization codes: 2 minutes.
• Access tokens: at most one hour. Refresh inactivity: 30 days; connection absolute lifetime: 90 days. Rotation/revocation checks apply.
• Initial invitation claim: 5 minutes. Game grants: fixed 30 minutes; a round remains 180 seconds.
• Human archive browser access: 30 days. Local recovery keys remain until you clear/delete browser storage.
• Completed/void canonical public match worlds and their records: 90 days after the last retained activity, with active/shared timelines protected.
• Pending execution intents: at least the configured 24-hour operational window; committed receipts remain with the canonical match.
• Independent production PostgreSQL PITR backups: four retained weekly full backups with daily differential backups and archived WAL, giving approximately four weeks of rolling recovery history. Deletion is not immediate in backups. Before a restored database can accept public games, the recovery runbook requires reapplying deletions and invalidating old write permissions. Separately held encrypted maintenance/recovery exports are outside this automatic rotation and normally expire no later than 30 days from the backup cut. Only documented legal exceptions or preservation of otherwise unavailable verified recovery permit a restricted extension; live deletion does not remove these copies.
• Railway provider logs, including HTTP request logs: 90 days according to its support information; the Hobby plan exposes seven days of history. No external application log forwarding is configured. Support mail: normally no more than 6 months after resolution, unless legal obligations or claims require longer.

Production PostgreSQL PITR is enabled in a separate backup bucket. The automatic recovery rotation is distinct from live-record deletion; additional maintenance exports require their own deletion handling.

Your controls and rights

Use guest management in your OAuth browser to export your latest 100 recorded model-seat matches, revoke connections or delete the guest/private model archive. Delete individual human runs in Trading Memory. Shared canonical gameplay may remain for the other participant. Complete export, lost access, correction, erasure, restriction, portability and objection requests can be sent to the operator. Backup deletion is not instantaneous. You may complain to the competent data-protection authority; the existing Berlin operator information appears in Datenschutz.

Do not send access tokens, capabilities, recovery secrets or complete invitation links to support. We use the minimum reasonable ownership evidence for requests. No advertising trackers or sale of this game data are introduced by the plugin.

Datenschutz auf Deutsch

Verantwortlich ist Lennard Bugajski unter der oben genannten Anschrift. Verarbeitet werden pseudonyme Gast-/OAuth-Daten, notwendige Browserbindungen, konkrete Tool-Eingaben, simulierte Ausführungen sowie Match Review und Trading Memory. Ganze ChatGPT-Chats und verborgenes Modell-Denken werden nicht angefordert.

Die Verarbeitung dient dem angeforderten Spielbetrieb, der Dokumentation und angemessener Sicherheit. Die Rechtsgrundlagen und Fristen sind oben aufgeführt. Railway und Cloudflare werden als Hosting-/Sicherheitsanbieter eingesetzt; Produktionsregion und Transfermaßnahmen sind oben und in der allgemeinen Datenschutzerklärung beschrieben.

Gastverwaltung ermöglicht Export, Widerruf und Löschung; menschliche Archivläufe werden in Trading Memory gelöscht. Gemeinsam genutzte Spielaufzeichnungen des anderen Teilnehmers und geschützte Sicherungskopien unterliegen den beschriebenen Fristen. Für vollständige Auskunft, Berichtigung, Löschung, Einschränkung, Datenübertragbarkeit oder Widerspruch kontaktiere [email protected]. Gesetzliche Beschwerderechte bleiben bestehen.