Data processing

1. Data enquiries

DAWKOZ’s contact person is Dawid Kozula. Questions about the website and planned implementations: [email protected].

Correspondence and animation preference rules are described in the privacy policy.

2. Data in business solutions

Phone bots, IVR systems and automations may handle information needed for a request, such as addresses, issue descriptions and contact details. Data scope should match the specific process purpose.

Information may go to agreed client tools, such as CRM, email, spreadsheets or messaging apps. SMS and Telegram flows shown on the site are examples, not tools used in every deployment.

3. Parties' roles

Identify the controller, processor and each provider's role before launch. Technical implementation alone does not determine these roles.

If DAWKOZ processes personal data on a client's behalf, suitable arrangements and, where the GDPR requires it, a data processing agreement are needed. The agreement must name the appropriate person or company as a party.

4. Arrangements for each deployment

• Processing purposes, data types and categories of data subjects.
• Data access scope and how instructions are communicated.
• Providers and data storage and processing locations.
• Any transfers outside the European Economic Area and required safeguards.
• Retention periods, deletion or return of data and termination terms.
• Security measures, incident handling and support for data subject rights.
• If call recording or transcription is planned: purpose, legal basis and how callers are informed.

5. Billing data and caller data

Data needed for an invoice may be processed by the actual seller and its authorised accounting service. This does not imply access to requests, calls, transcripts or customer documents.

Before data is made available to any party, its role, purpose, scope of access and appropriate legal basis are defined. The contractor’s identity and billing arrangements need to be confirmed before an order is placed.

6. Scope of this document

Callers should receive clear information that they are speaking to AI. Recording or storing transcripts requires separate arrangements for the purpose, legal basis, retention and information given to callers. Calling a bot is not consent to every use of the conversation.

Invoice automation requires agreement on which data is extracted, who may verify it and how errors are handled. Reading a document with AI does not mean that it has been correctly booked, submitted to Poland’s KSeF system or approved for payment.

This information outlines deployment arrangements. It is not a data processing agreement and does not replace system-specific documentation or notices to people whose data will be processed.