Workspace access
FaceX checks the signed-in user and current workspace membership before protected dashboard operations. Organization-scoped access and database policies separate workspace records.
Management actions have role-specific permissions. Platform administration has a separate access check; workspace ownership alone does not grant platform-admin access.
Credentials and sessions
FaceX server API keys are displayed once when issued. The gateway uses stored key digests for authorization, and revoked keys stop authorizing requests. Authorized workspace members can rotate or revoke keys in Developer settings.
Keep server, provider and service-role secrets out of websites, mobile apps and public repositories. Browser applications use the public project configuration and a signed-in user session for supported console operations.
Private documents and support
Business-compliance documents are stored in a private bucket and accessed through permission-checked, short-lived links. The application limits document types and sizes before upload.
Public contact-form messages are stored in a private request queue. Anonymous visitors can submit a request but cannot read that queue. Workspace tickets are available through the authorized support workflow.
Verification controls
Identity checks depend on the provider, model service and capture pipeline configured for the integration. The backend must make the verification decision; a completed upload or capture animation is not an approval.
Use issued sessions, real camera evidence and the returned timing and attempt limits. The API reference identifies available endpoints and their current service boundaries.
Payment reconciliation
Configured wallet payments are reconciled on the server before a credit is applied. Payment references, amounts, currency and provider responses are checked; a browser return page does not credit the wallet.
Repeated payment callbacks are handled through the saved payment state. Payment notifications and verification-event delivery are separate integrations.
Report a concern
Email support@facexverify.com with the affected service, relevant time and a redacted description. Keep active credentials and applicant identity evidence out of the initial message.
For a vendor assessment, tell us which deployment and controls you need to review. See our Compliance and Privacy pages for the related policies.