OPS Guide / Proposed product
Know what to ask.
Know what to build.
PLANNED — NO LIVE MCP ENDPOINT YET
Privacy guidance for the person building the app—and the person whose business depends on it.
OPS Guide would turn an app's context into plain-language explanations, source-linked rules to investigate, and concrete tasks for its builder.
01 / The experience
“I'm building a booking app.
What should I check?”
- Describe the app. Where does the business operate? Where are its users? What information is collected, for which purposes, by which providers? What do we know about scale and age groups?
- Find candidate rules. Explain why each rule might matter, which facts are missing, and which exceptions or thresholds need review.
- Turn findings into work. Produce tasks for access controls, notices, preferences, retention, deletion, provider configuration, and tests, with each task labeled as a legal requirement to confirm or an engineering recommendation.
- Keep the evidence. Attach official sources, the edition and effective date of each rule, the source-check date, and the limits of the answer.
The output would identify what to investigate. It would not certify compliance or treat an unknown answer as an exemption.
02 / Guidance where the work happens
An MCP for your coding agent.
MCP is a way to connect an AI tool to an external source of information. Here, it would let your coding assistant ask OPS about privacy while helping you build.
- discover_rules
- Return candidate rules based on business context, user locations, data types, and intended uses. Explain the match and list missing facts.
- get_rule
- Retrieve a versioned rule, its plain-language summary, official sources, effective dates, and review status.
- build_checklist
- Turn a reviewed set of findings into implementation tasks and suggested verification steps.
One maintained knowledge base, two ways to use it: a website for people and an MCP interface for their tools.
03 / What makes the guidance trustworthy
The answer needs a source.
- Official legislation and regulator guidance linked to every legal summary.
- Enacted rules, future effective dates, proposals, and regulator guidance clearly distinguished.
- Version history, review status, corrections, and stale-source warnings.
- Explicit uncertainty and a path to qualified review for consequential decisions.
- Synthetic app descriptions and minimal input data; no customer records needed to ask a question.
04 / The first useful version
Start narrow. Earn confidence.
Begin with a small, reviewed set of US rules and common app patterns. Test the explanations with first-time builders and business owners before expanding jurisdictions.
The initial law library is an editorial prototype. A reviewed rule database, applicability logic, and live MCP service remain to be built.