Terms of service

1. Person operating DAWKOZ

DAWKOZ is the brand under which Dawid Kozula communicates with clients and works on websites, phone bots, IVR systems, integrations and automation.

Person operating DAWKOZ

Dawid Kozula

Email

[email protected]

DAWKOZ is a brand. Before entering into a contract, the customer must receive the seller’s full business name or personal name, address, and relevant registration and tax details. The contact person is not necessarily the contracting party.

2. Scope of cooperation

Solutions are tailored to client processes. Work may cover websites, AI phone bots, IVR systems, tool integrations, process automation, maintenance and further development.

Scope, operating scenarios, integrations, schedule and acceptance criteria are agreed before work starts.

3. Contact and project agreement

1. The client describes their needs and current process.
2. The scope, operating approach and quote are prepared.
3. The parties agree on cooperation and billing terms.
4. The solution is built, tested and launched within the agreed scope.

Sending an enquiry or browsing the site does not itself conclude a contract or order a paid service.

4. Prices and billing

Amounts in the current price list are final amounts payable, including VAT if applicable. A price stated as “from” requires confirmation of the scope and final quote. The seller’s VAT status and details are specified in the offer and contract.

Current services and pricing show the available options. Each project should specify the final amount, taxes, payment dates, external service costs and any subscription terms.

Dawid Kozula may perform the work under the actual collaboration arrangements. The seller, contractor responsible to the customer and invoice issuer must match the contractual arrangements; an invoice issued by another company alone does not establish that the arrangement is valid.

The seller’s full details and the basis of collaboration with the person performing the work still need to be confirmed. This website does not attribute consent to sell, responsibility or an invoicing obligation to another company.

5. Delivery, acceptance and changes

The client supplies information and access needed for the agreed scope. Tests cover agreed scenarios. Launch follows approval under the agreed acceptance procedure.

Before a bot is activated, its scenarios, handoff to a person and handling of incorrect answers are tested. AI can make mistakes. Actions requiring a binding decision, booking confirmation or document approval must be explicitly agreed and tested.

Additional work or changes outside scope require agreement on price and schedule implications. Rights to materials, code, licences and external services should be defined in the contract.

6. Support and subscription

Maintenance, changes and development may be provided monthly after deployment. Support scope, fees, issue reporting, response times and termination are agreed for each project.

A subscription description does not mean automatic charges or a contract through browsing alone.

7. Reports and complaints

Send questions and reports about cooperation to [email protected], stating the project and issue. Reports should reach the entity responsible for the contract.

Complaint procedures and deadlines, liability and termination terms must be adapted to the actual contracting party and client type.

8. Client rights and personal data

Agreements cannot limit mandatory statutory client rights. Where consumer or withdrawal rules apply, the required information should be supplied before contracting.

Website and correspondence rules are described in the privacy policy. Deployments processing other people's data require separate arrangements described in the data processing information.