Data Use & Security

Your accounts stay yours.

Soku connects the systems you choose so its agents can analyze information and run authorized workflows. Your source accounts and business assets remain under your control.

You control the connection. Soku accesses only the accounts and permissions you authorize. Where a platform supports OAuth or partner authorization, you do not give Soku the source-account password. You can revoke future access through the source platform and separately request deletion of information held by Soku.

Each client uses a separate Organization. Each direct customer and each unrelated agency end client should use a separate Soku Organization. Organization-level access controls keep users in another Organization from accessing that client's raw connected data, conversations, files, or agent activity.

Choose the data-use terms that fit the deployment. Unless an Order states otherwise, a direct-customer Organization uses Standard, under which eligible data may improve Soku models, agents, and product features used across Organizations. Qualifying paid plans can include a written No-Training commitment for the identified Organization.

Agency deployments. For Agency-managed end-client Organizations, the applicable data-use option and the Agency's authority are recorded in the Agency Addendum before live data is connected.

Start small. A pilot can begin with one account, a short time range, limited permissions, test or lower-sensitivity data, and analysis-only access where supported. Write-capable workflows must be enabled separately and follow the approvals or automation rules configured for that workspace.

For a live deployment, Soku and the customer can record the connected accounts, read/write scope, data-use option, and revocation path in a one-page confirmation. Any deployment-specific commitment is stated in the applicable Order.

See also our Privacy Policy and Terms & Conditions.

• Company: About Intelligence Inc.
• Privacy contact: [email protected]