Do you publish full architecture details publicly?

No. Public pages explain what data is collected and how access is controlled. Qualified prospects can request deeper security material during procurement.

Does Kyrospect support employee transparency?

Yes. Kyrospect is designed so employees can view their own activity and HR records and understand the policies their workspace owner has applied.

Do you hold SOC 2 or ISO 27001 certification?

No. Kyrospect is in private beta and does not currently hold third-party security certifications. We will update this page if that changes.

Yes. A Data Processing Agreement is available for teams that need formal processor terms before rollout.

How should teams roll out tracking responsibly?

Start with notice, policy clarity, employee visibility, and role-based access. Kyrospect is built to support those rollout practices.

Security & Compliance

What we collect, what we control, and what is still beta.

Kyrospect is in private beta. This page is written for the person who has to answer for the vendor: what data moves, who can see it, and where we are still maturing.

What is collected

Data in scope for HRMS and Tracking

Employee record: name, role, department, and organization structure (HRMS)
Screenshots at a workspace-set interval, with privacy blur applied before storage if enabled
App and active-window titles, sanitized
URL activity, when enabled by workspace policy
IP-based location context — city, region, country, and network — never GPS or device location
Idle time, from OS-level idle polling and lock-screen detection
Automation-pattern signals, a set of specific heuristics available on Windows today

Uniform privacy blur

Blur is a single workspace-level on/off setting applied to the full screenshot before it is stored. It does not detect or target passwords, credentials, or specific fields, and has no intensity levels.

Employee transparency

Team members can see their own tracked records and HR data, and the policy their workspace owner configured for them.

Owner and member roles

Kyrospect ships Owner and User as system roles. Manager-style access is achieved through custom roles that a workspace owner defines and scopes.

Procurement-ready materials

A security overview, DPA, and current control notes can be shared with qualified teams during review.

Honest about beta

Still maturing — said plainly, not buried.

We would rather list what is not finished than let a reviewer discover it later. None of the items below are dealbreakers for a private beta, but they should shape your rollout plan.

Not yet available

Retention windows are stored as a workspace setting, but no automated purge job enforces them yet — treat retention as a stated policy, not a guaranteed control
Single sign-on and data residency selection do not exist yet
Automation-pattern signals are Windows-only; macOS and Linux are not covered today
The HRMS organization-structure screen is still being built; the underlying record is real
No third-party security certification is held or in progress at this time

Need to share this with a founder, client, or security reviewer?

Request a security conversation and we will share the right level of detail for your stage.

Request security pack Review DPA

Loading…

Data in scope for HRMS and Tracking

Employee record: name, role, department, and organization structure (HRMS)

Screenshots at a workspace-set interval, with privacy blur applied before storage if enabled

App and active-window titles, sanitized

URL activity, when enabled by workspace policy

IP-based location context — city, region, country, and network — never GPS or device location

Idle time, from OS-level idle polling and lock-screen detection

Automation-pattern signals, a set of specific heuristics available on Windows today