DAWKOZ / INFORMATION

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
Contact address
ul. Wolności 123, Chorzów
Email
[email protected]

The contracting party's full identity and billing arrangements are agreed before accepting a project.

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

Website prices marked “from” are starting prices. The final quote is agreed individually before work begins and depends on conversation flows, integrations, usage and support scope.

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 performs the work. Under the indicated billing arrangement, invoices are intended to be issued by Kozbud, NIP 6272742701. The tax number belongs to Kozbud. Before work starts, the client receives the full contracting party details, the entity responsible for the service and agreed billing terms.

Kozbud's full name and address and the basis of cooperation between Dawid Kozula and the invoicing company remain to be added. Kozbud's accounting team should confirm this billing model before it is used.

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.

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.