Trust
Data processing
A processing agreement should describe who operates the system, whose data it holds and what work is being performed.
Buyer-operated software
Providing a codebase does not, by itself, make Avrosh the operator of your call database. The deployment operator determines the applicable controller and processor relationships with its clients and providers.
When Avrosh processes customer data
If separately agreed customer services involve Avrosh handling personal data, request the applicable data processing agreement before that work starts. It should identify the parties, instructions, data categories, processing locations, providers, access and end-of-service arrangements.
Define retention by data type
Call audio, transcripts, saved requests, account records and backups are different data categories. Optional 7- or 30-day audio expiry does not define the retention of the other records.
Agree who handles access requests, deletion, backup retention and restore reconciliation for the actual deployment. See privacy and providers and data flow.
Request the applicable agreement
Contact hello@avrosh.com with the service you are considering and your processing requirements. This overview is not an executed data processing agreement.
Existing purchases and signed agreements remain governed by their applicable terms. This page does not replace an agreement you already have.