Orikware / Trust Center
Trust is built into the work.
A clear view of the security design and operational responsibilities behind an Orikware engagement.
This overview is not an audit certification or a guarantee of availability. Contact the studio for deployment-specific evidence and contractual requirements.
Access & separation
Client workspaces use authenticated accounts and role-based access. Database policies and server-side authorization are designed to keep client records scoped to the appropriate account. Account provisioning, permissions, and the policies actually deployed must be verified for each environment.
Data & privacy
The information needed for a project, its authorized users, enabled providers, and retention rules should be established before production use. Voice processing can involve audio, transcripts, and third-party AI services. A privacy notice does not replace a client-specific processing agreement.
Application safeguards
The platform includes request validation, authorization checks, and browser security headers. Production transport, credentials, access policies, and provider settings remain part of deployment operations. Do not send secrets through public forms or support messages.
Reliability & recovery
Availability depends on Orikware and its configured hosting, database, voice, and automation providers. Support coverage, backup retention, restoration procedures, and any service-level commitment must be agreed for the engagement. The Status page distinguishes dated reports from unverified service health.
Raise a concern.
For a privacy, security, or service issue, contact studio@orikware.com or use your client inbox. Include the affected feature and approximate time, with only the information necessary to investigate. Do not include live credentials or another client’s data.