POLICY / VERSION 1.0

Privacy

Codex Deck minimises data collection and exists only to operate the private EpicEncore Codex bridge.

Effective 28 July 2026.

What the deck processes

The deck processes the bridge token you provide, project paths, task instructions, thread and run identifiers, status, agent messages, command summaries, changed-file paths, errors and timestamps returned by the bridge.

Where data goes

The web server sends authenticated requests to mcp.epicencore.io. The bridge operates local Codex under D:\projects. This interface does not use advertising, marketing trackers, product analytics, Supabase or AI-training data collection.

Storage and retention

The token is stored only in a secure, HTTP-only, same-site cookie that expires after eight hours or when you disconnect. The interface does not create its own durable copy of task or run history. Local Codex and bridge records follow their separately documented operational retention.

Your control

Disconnect to remove the browser cookie. For access, correction or deletion questions about bridge records, email support@epicencore.io after removing sensitive details from the message.

Changes

Material changes will be reflected here with a new version and effective date. Previous policy versions remain in repository history.