The data controller
The controller of your personal data is Siopa sp. z o.o., ul. Smukalska 33, 85-565 Bydgoszcz, entered in the register of entrepreneurs of the National Court Register under KRS number 0000854451, registry court: District Court in Bydgoszcz, 13th Commercial Division of the National Court Register, tax identification number (NIP) 9671438308, statistical number (REGON) 386748185, share capital PLN 5,000. Below we refer to it as Siopa.
For anything concerning personal data, write to kontakt@dyzio.taxi. The same address is used for every request described in this policy.
What this policy covers
This policy covers the Dyzio website at https://dyzio.taxi and the free demo conversation in the browser. The rules on cookies are set out in the cookie policy and the rules for using the website and the demo in the terms of service. GDPR means Regulation (EU) 2016/679 of the European Parliament and of the Council.
Contact form
- What data: name, company name, phone number or e-mail address, the content of the message, as well as the IP address, the time of sending, the page language and campaign parameters, if you open the page from a link that contains them.
- Why: to answer your question, prepare an offer and contact you about it.
- Legal basis: Article 6(1)(b) GDPR, that is steps taken at your request before entering into a contract, and Article 6(1)(f) GDPR, that is our legitimate interest in answering an enquiry from a company's representative and protecting the form against abuse. By ticking the box in the form you also consent to being contacted by phone or e-mail about the offer (Article 398 of the Polish Electronic Communications Law). You may withdraw this consent at any time.
- How long: the enquiry is saved in the demo journal described below and kept for as long as it is needed to answer you and discuss the offer, at most until you withdraw your consent or successfully object, unless we need it to defend against claims. No fixed number of months has been set. If we conclude a contract, any further period follows from the contract and the law.
- Who has access: Siopa's authorised employees and collaborators who handle enquiries, and server providers. We notify a member of our staff of each new enquiry by text message, so the name, company name, phone number and e-mail address also reach the SMS operator (SMSAPI).
If you write to us by e-mail, we process your address and message for the same purposes and on the same legal bases.
Phone number verification and SMS code
- What data: your mobile phone number, IP address, the chosen city and conversation language, and a one-time code, which we store only as a hash.
- Why: to confirm that the number is yours and to open a demo session. The code is sent by text message to the number you give. We do not use your phone number for marketing.
- Legal basis: Article 6(1)(b) GDPR, that is performance of the contract for using the demo, which you conclude on the terms set out in the demo rules.
- How long: verification data is kept only for the validity of the code (10 minutes). After your number is confirmed, the demo session lasts 6 hours, unless you sign out sooner. Your phone number is also saved in the course of the conversation and in the demo journal described below, and a hash of it in the counters.
- Who has access: SMSAPI, the SMS operator, which receives the number and the text of the message with the code, and server providers.
The demo conversation and its record
Sound from your microphone is sent in real time to OpenAI, the provider of the voice model that conducts the conversation. We do not save a recording of your voice. We do save the transcript, that is the text of what you and the automated system say, and the course of the conversation: the time, phone number, city, language, addresses and other data given in the conversation, the details of the simulated order, the system's decisions and technical events.
During the conversation the system analyses the content of what you say in order to understand your request and to choose how it speaks, for example more calmly. The result of this analysis forms part of the course of the conversation.
- Why: to conduct the conversation you ask for and to be able to explain how it went if something goes wrong.
- Legal basis: Article 6(1)(b) GDPR as regards conducting the conversation, and Article 6(1)(f) GDPR as regards its record, that is our legitimate interest in handling complaints and abuse and defending against claims.
- How long: the conversation record is kept for as long as it is needed for these purposes and for the development of the service described below, at most until a successful objection or the withdrawal of your acceptance of the record. No fixed number of months has been set. Simulated orders are additionally held in the server's memory for one hour, so that questions about the status of a ride and its cancellation work.
- Who has access: Siopa's authorised employees and collaborators, server providers and the providers listed under “Who receives the data”.
Demo journal
- What data: every request for an SMS code and its outcome, the confirmation of the number, the start and end of a demo conversation and an enquiry sent through the contact form: the time, phone number, IP address and the network it belongs to, the chosen city and language, the outcome or the reason for a refusal, and the link to the conversation record. The SMS code itself is not saved in the journal.
- Why: to know who uses the demo and how often, to protect it against abuse and excessive costs, and to look into enquiries and faults.
- Legal basis: Article 6(1)(f) GDPR, that is our legitimate interest in the security of the service and in understanding interest in the demo.
- How long: for as long as it is needed for these purposes, at most until a successful objection, unless we need it to defend against claims. No fixed number of months has been set.
- Who has access: Siopa's authorised employees and collaborators and server providers.
Protection against abuse
- What data: the IP address and the network it belongs to (/24 or /48), a hash of the phone number, counters of codes sent, enquiries and conversations started, and the server's technical logs, which may contain the phone number, IP address, event times, the content of an enquiry and the course of a conversation.
- Why: to protect the demo and the form against automated use, mass sending of text messages and excessive costs, and to detect and fix faults.
- Legal basis: Article 6(1)(f) GDPR, that is our legitimate interest in the security of the service and protection against abuse.
- How long: the counters per IP address and network run for one hour or one day, depending on the limit. The counter of conversations per phone number runs for 30 days. Technical logs are kept for as long as they are needed for diagnostics and the security of the service; no fixed period has been set for them.
- Who has access: Siopa's authorised employees and collaborators and server providers.
Development of the service
- What data: the transcripts and course of demo conversations described above.
- Why: to check how the automated system works, find faults and improve its understanding of speech and addresses and the quality of conversations. We do not use this data to send advertising.
- Legal basis: Article 6(1)(f) GDPR, that is our legitimate interest in developing and improving the service. Before the conversation you tick a box in which you accept that the conversation is saved for this purpose.
- How long: for as long as needed for this purpose, at most until a successful objection or the withdrawal of your acceptance of the record. To do so, write to kontakt@dyzio.taxi. We will then delete the record of your conversations, unless it is needed to defend against claims.
- Who has access: Siopa's authorised employees and collaborators and server providers.
Who receives the data
We pass data only to these recipients and only to the extent needed for the purposes described:
- OpenAI (provider of the voice model and language services): the sound of what you say, its transcript and the content of the conversation, needed to conduct the conversation and understand your requests.
- Google (the Places API service for finding addresses and places): the words naming an address or place that you give in the conversation.
- SMSAPI (SMS operator): the phone number and the text of the message with the code and the data from the contact form in the notification of a new enquiry.
- Providers of servers, databases and e-mail: store data on our behalf.
- Public authorities: when the law requires us to pass on data.
Transfers outside the European Economic Area
OpenAI and Google may process data outside the European Economic Area, in particular in the United States. Such a transfer is based on Chapter V GDPR: on a European Commission decision finding an adequate level of protection (Article 45 GDPR) or on standard contractual clauses (Article 46(2)(c) GDPR). You can obtain a copy of the safeguards applied by writing to kontakt@dyzio.taxi.
When Dyzio works for a taxi corporation
When a taxi corporation uses Dyzio, that corporation is the controller of its passengers' data. Siopa processes this data on its behalf, under a separate data processing agreement (Article 28 GDPR).
If you call such a corporation, contact it about your data. This policy does not describe those conversations.
Your rights
You have the right to:
- access your data and obtain a copy of it (Article 15 GDPR),
- rectification of inaccurate data (Article 16 GDPR),
- erasure of data (Article 17 GDPR),
- restriction of processing (Article 18 GDPR),
- data portability, for data we process under a contract or consent (Article 20 GDPR),
- object to processing based on our legitimate interest (Article 21 GDPR),
- withdraw your consent at any time, which does not affect the lawfulness of processing before the withdrawal (Article 7(3) GDPR),
- lodge a complaint with the President of the Personal Data Protection Office in Poland (uodo.gov.pl).
To exercise these rights, write to kontakt@dyzio.taxi and give the phone number or e-mail address the matter concerns. If we have reasonable doubts about your identity, we will ask you to confirm it. We will reply without undue delay and within one month at the latest.
Do you have to provide data
Providing data is voluntary. Without a phone number we cannot send a code or start the demo, and without a phone number or e-mail address in the form we cannot reply.
Automated decisions
We do not take decisions about you based solely on automated processing that would produce legal effects or similarly significantly affect you. The automated system conducts the conversation, and the limits and safeguards of the demo work automatically, but they are technical in nature.
How we protect data
- The connection to the website and the demo conversation are encrypted.
- We store the SMS code only as a hash and delete it once it has been used or has expired.
- The verification and session cookies are not accessible to scripts running on the page.
Changes to this policy
We change this policy when the law or the way the website works changes. The current version is always on this page, and the date of the last change is given below.
Last updated: 9 November 2026