Step 1
Start with the boundary
PortalKinetic is the Relief Operating System for overloaded professionals: clear your head, see what matters, and take one next step. The employee workspace is private. The organization receives only aggregate, cohort-safe support patterns.
Step 2
Review the example payload
Buyer-facing telemetry contains event type, event count, unique-user count, day-level date, reporting period, and suppression metadata.
Step 3
Check what is excluded
No user IDs, raw email, private text, task titles, raw payloads, sub-day timestamps, individual scores, or per-user output exhaust are returned in buyer-facing telemetry.
Step 4
Verify cohort suppression
Small cohorts are suppressed before display. Reports are designed to answer adoption questions, not identify one employee.
Step 5
Inspect regression gates
Copy audits, biometric-ingestion checks, EU AI Act language guards, and focused route tests protect the boundary from drift.
Step 6
Book pilot review
Use the same packet to align security, People Ops, works-council, and executive stakeholders before a pilot decision.