OrigenStudio wants OpenAI to never see raw client data

A new architecture doc quietly reveals a planned privacy gateway that strips client identifiers before any prompt reaches a commercial AI provider.

securityinfrastructure

On paper it's just documentation - a diagram of how the fork is wired together. But the interesting part is what it telegraphs about where the team is heading. Alongside the known hosting stack, the diagram sketches a privacy layer that hasn't been built yet: a step that scrubs personally identifiable information from requests using a small AI model running on the team's own hardware, so that whatever reaches OpenAI is already stripped of raw client detail.

Nothing here has shipped. The design is explicitly marked as planned, and the team has paused at an internal approval gate. So treat it as intent, not capability. Still, for anyone weighing whether a legal-AI tool can keep confidential matter away from a third-party model, a self-hosted scrubbing step in front of the LLM is a pattern worth watching.

So what Anyone evaluating legal AI on client-confidentiality grounds should watch how this privacy gateway lands.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from OrigenStudio/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
9f7c6f14 docs: add deployment architecture diagram to README Pol Guixe 2026-06-04 ↗ GitHub
commit body
Adds a section at the end of README.md (clearly marked as Origen Studio-
specific so future upstream merges stay clean) covering:

- Status legend (live / staging-only / planned)
- ASCII diagram of the full data flow: browser → Cloudflare Workers →
  Railway backend → Supabase + R2 + (planned) Hey Jude → Ollama / OpenAI
- Why each platform was chosen
- Links to related repos (OrigenStudio/hey-jude, OrigenStudio/mike-ollama)
  and to DEPLOY.md for the full walkthrough

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
de324f4c Merge pull request #4 from OrigenStudio/docs/architecture-diagram PolGuixe 2026-06-04 ↗ GitHub
docs: add deployment architecture diagram to README

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-629.md from inside the repo you want the changes in.

⬇ Download capture-thread-629.md