Provider-backed access
Operators authenticate through the organization's configured Microsoft Entra ID or Okta environment. The Fctr verification product does not persist customer workforce PII or create a parallel identity directory.
Trust center
Fctr helps organizations verify the person behind a support request before releasing a sensitive account action. This center summarizes our public security posture and links to the policies used in customer review.
Our approach
Fctr is designed for high-risk helpdesk and IT support workflows. The platform uses an employee's existing enrolled factors, applies backend-owned role and action policy, and records privacy-reviewed audit events. Product behavior and deployment configuration are evaluated separately so public claims remain accurate.
Operators authenticate through the organization's configured Microsoft Entra ID or Okta environment. The Fctr verification product does not persist customer workforce PII or create a parallel identity directory.
Caller verification uses supported factors already enrolled with the organization's identity provider. Verification state is time-limited and bound to the active support workflow.
Roles, provider capability, verification state, and customer policy are evaluated by the backend before a support action is exposed or executed.
Security-relevant workflows generate structured audit events designed for operational traceability while excluding secrets, credentials, raw tokens, and unapproved personal data.
Public documents cover our standard posture. Customer-specific architecture, questionnaires, and supporting evidence are handled through the security-review process.
Contact us for customer-specific architecture questions, questionnaires, or available supporting documentation.