Your data stays with you.

Refracted Cortex is an architecture layer, not a data warehouse. Your cognitive architecture lives in a private container you own. AI requests route through RC's no-log proxy — we capture usage metadata (token counts, costs) and nothing else. We couldn't read your conversations even if we wanted to — they aren't here.

How data flows

The architecture is simple by design:

• Session data (CLAUDE.md, memory, history) — lives in your private container, isolated from other users and from RC
• AI conversations — processed by your chosen AI provider (Claude, GPT, or Gemini) via OpenRouter. Not stored for training. Not retained by RC.
• RC's proxy role — routes requests and captures metadata only (token counts, costs). No prompt content logged. No conversation data stored.
• Model choice — you choose from 6 models across 3 providers. Claude Sonnet 4 is the default. Switch anytime.

What we're building toward

• SOC 2 Type II — target Q4 2026. We're building the compliance infrastructure as we grow.
• Formal SLA with uptime commitments — Enterprise tier. Defined in the engagement agreement.
• Status page — status.refractedcortex.ai (coming soon)

We're honest about where we are. RC is early-stage. We don't have SOC 2 yet. We're building toward it with intention, not claiming it prematurely.

What happens if RC goes away

Your cognitive architecture is portable by design. Here's what you keep:

• CLAUDE.md — your complete cognitive profile, plain text, in your repo
• Memory files — all session history, learnings, context — plain text files you own
• Agent configurations — your specialized agents, their instructions, their memory
• Portable architecture — your CLAUDE.md and configuration files are standard Markdown. They work outside RC. The architecture is yours.

RC makes AI dramatically more useful. But if RC disappeared tomorrow, your architecture files are yours, your cognitive profile is portable plain text, and your investment in defining how you think is preserved in files you control.

CoS feedback — privacy by design

Your Chief of Staff may occasionally suggest sharing product feedback with the RC team. Here's how that works:

• Always opt-in — your CoS asks permission before drafting any feedback
• Anonymized by default — all personal information (your name, client names, company names, specific data) is stripped automatically. The RC team sees "A Cloud-tier user reported..." unless you choose to identify yourself.
• You review everything — you see the exact message before it's sent. Edit or reject at any time.
• Permanent opt-out — say "don't ask me again" and the system never prompts you for feedback again
• Rate limited — maximum one feedback prompt per week, regardless of how much you use the system

Company information

Refracted Cortex is a product of Digitally Demented Ventures, an operations and technology consulting firm founded in 2011 by Daniel Walters.

Questions about security, data handling, or compliance? Contact us directly.