Trust
Privacy overview
This page describes the main categories of data OKRunit uses to operate the product and route approvals. It is a product overview for customers evaluating the platform and should not be treated as legal advice.
Data categories used by the product
OKRunit processes the information required to create approval requests, route them, and keep an auditable decision trail.
Account and organization data
User identity, organization membership, role assignments, and configuration needed to control access to the dashboard and approval flows.
Approval request content
Titles, descriptions, metadata, source identifiers, and other context supplied by your automations so reviewers can make a decision.
Audit and activity history
Approvals, rejections, comments, route changes, and related events used to explain what happened over time.
Connection and notification settings
Connection names, API key metadata, and routing or messaging settings used to deliver requests and callbacks.
How that data is used
The product uses data to operate core workflow controls, not just to display screens.
Product controls that support privacy
Several parts of the product are designed to limit unnecessary exposure of sensitive workflow details.
Scoped access
Teams can use org membership, approval routing, and role controls so only the right reviewers see the right requests.
API key handling
Connection keys are issued for server-to-server workflows and are not shown again after creation in the product UI.
Traceable changes
Audit history helps teams review who changed routes, who approved a request, and what context was attached.
Questions and requests
If you need clarification about the way OKRunit handles product data, contact support with your organization and use case.
Email support@okrunit.com for product privacy questions. For implementation details, see the API reference and webhook documentation.