How We Handle Your Business Data

Useful reporting and service workflows require some access to business information. A salon may need appointment history, service totals, missed-call outcomes, or scheduling rules to understand what is happening. The question is what access is authorized, what data is necessary, how it is used, and when it is removed.

Do not infer a software provider's data practices from its price or marketing language. Review the current contract, privacy notice, provider list, and settings for the product and plan actually used. Ask specifically about ownership, approved use, access, model training, retention, exports, and deletion.

A clear data boundary is more useful than a blanket promise that no information is processed.

Use Data for the Agreed Purpose

When Adaptiv Stratum processes calls or business records for a client, the client determines the business purpose through its agreement and instructions. Our role is to support that purpose, not to convert one client's confidential records into an asset for another business.

A call workflow might need contact details and approved service rules; an operations report might need appointment and outcome records. The permitted fields, actions, reviewers, and providers should be defined for that implementation.

• Purpose-bound use: We seek only information reasonably necessary for agreed work and do not repurpose one client's confidential records to benefit another business.

• No sale or rental of confidential client records: Authorized service providers may receive the information needed for their function under applicable agreements and terms.

• No public-model training: We do not use client or caller content to train public or general-purpose AI models. Provider involvement and controls vary by deployment and should be reviewed before use.

Questions to Ask Before Connecting Systems

For a shop owner, the client list, visit history, and service preferences are valuable operating records. Before approving a connection, ask which records are read or updated, who can view them, what leaves your system, and how access can be revoked.

If calls are transcribed or recorded, document the caller notice, permitted reviewers, provider settings, and retention period. If an AI service is involved, identify its task and the human review boundary. Price alone does not answer any of these questions.

Retention depends on the agreed purpose, support and security needs, provider settings, and legal obligations. Information that is no longer reasonably necessary may be deleted, anonymized, or securely disposed of, subject to backup cycles, technical limits, and documented client instructions.

A Reviewable Implementation

Map the flow from the booking or phone system through each necessary provider to the report or action. Limit permissions, define who can access the information, and test export, revocation, and deletion behavior where available. No system or transmission method is risk-free.

Our Privacy Policy explains our roles, service providers, AI processing, retention, and privacy request path. The project agreement and deployment settings determine the specifics for your operation. Ask to review those specifics before sharing client records.

The goal is not zero data. It is enough information to do the agreed work, with clear boundaries and a way to inspect them.