What is InPolicy?
InPolicy is a policy management platform built for organizations that already have a policy library and need it to stop being shelfware. You write the policies in one place. The platform surfaces them at the moment someone is about to violate one. And it tracks what’s working without turning your people into a dashboard of red flags.
The three surfaces
Section titled “The three surfaces”InPolicy reaches your team in three places:
| Surface | What it’s for | Who installs it |
|---|---|---|
Web app (app.inpolicy.ai) | Authoring, review, administration, analytics | Everyone on the team |
| Browser extension (Chrome) | Detects policy violations as users type in Google Docs, Gmail, and other web apps | End users, or IT via managed install |
| Mac app | Detects policy violations across every native macOS app (Mail, Slack, Notes, etc.) | IT via MDM, or individuals directly |
Each surface is optional. A legal team might stick with just the web app for authoring. A security-conscious org will roll out the extension and the Mac app to everyone.
Core concepts
Section titled “Core concepts”- Policy — a document your team is expected to follow. Policies carry a severity (1–5), a confidence threshold, and metadata like policy area and scope.
- Policy Area — a logical grouping (e.g. “Data Handling”, “Social Media”) that owns a set of related policies.
- Division — a top-level organizational unit. Policy Areas belong to Divisions.
- Policy Inbox — a staging area for AI-extracted policy suggestions from documents, URLs, or pasted text.
- Revision — an immutable snapshot of a policy taken every time it’s saved, published, or restored. Revisions form the audit trail.
- Violation — text that PolicyBot flagged as potentially conflicting with an active policy, surfaced while a user was typing in their browser or on their Mac.
- PolicyBot — the AI system that parses policy documents, detects violations, and suggests fixes. PolicyBot-authored content is tracked separately in revision history.
Who does what?
Section titled “Who does what?”InPolicy ships with four roles. The full matrix is on the Roles & permissions page; the short version:
- Admin — manages users, roles, SSO, and sees analytics.
- Policy Lead — owns a set of policy areas; can approve and publish policies.
- Policy Editor — creates and edits drafts within assigned policy areas.
- User — views published policies and runs the extension and Mac app.
Where to start
Section titled “Where to start”- If you’re an end user: Sign in and install the browser extension.
- If you’re a policy author: Walk through creating your first policy, then skim the editor guide.
- If you’re an admin or IT: Start with users & roles, then SSO and MDM deployment.