Privacy policy
Last updated: November 2026
1. Overview
BotPark is software that companies use to build AI chatbots from their websites, documents and databases and offer them on their own websites or under their own address. Pursuant to Articles 13 and 14 of the General Data Protection Regulation (GDPR), this policy explains which personal data we process when you
- visit our website botparkai.com,
- create an account as a customer or team member and use the dashboard (app.botparkai.com), or
- chat with a chatbot operated by one of our customers using BotPark (chat.botparkai.com, embedded chat windows and customers' own addresses).
2. Controller
Nils Oborny Sole proprietorship Rippoldsauer Str. 3 70372 Stuttgart Germany
Phone: +49 152 3207 1777 Email: info@orderpark.de
We have not appointed a data protection officer as there is no legal obligation to do so (Art. 37 GDPR, Section 38 BDSG). For data protection questions, please contact us at the email address above.
3. Roles: when we are controller and when we are processor
We are the controller within the meaning of Art. 4(7) GDPR for our website, customer accounts, contract handling and the security of our service.
Chatbot content and conversations with visitors, however, are processed on behalf of the customer operating the chatbot (processing on behalf pursuant to Art. 28 GDPR, see section 12). The controller for these data is the company on whose website or under whose name the chatbot is offered. Please therefore direct requests regarding your chat data primarily to that company; we support it in responding. If you send your request to us, we forward it to the company concerned.
4. Hosting and server logs
The website, dashboard and chatbots run on a server operated by IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, in a data centre in Germany. All connections are encrypted with TLS; certificates are issued by the non-profit certificate authority Let's Encrypt, to which no visitor data is transmitted.
The database (accounts, knowledge content, conversations and contact requests) and uploaded files are also stored on this server. Every six hours we create an encrypted backup of them, which is automatically deleted after twelve months at the latest. Deleted data may remain in a backup until then; backups are only used to restore the service after an outage.
When you access our services, the server necessarily processes your IP address, date and time, the requested address, the status code and browser and operating system information. These data are stored in error and operating logs in order to detect and fix malfunctions and attacks, and are automatically deleted after no more than 14 days. The legal basis is our legitimate interest in secure and stable operation (Art. 6(1)(f) GDPR).
5. Our website
On botparkai.com we do not use cookies, analytics or tracking tools, or advertising services. Fonts and all other components are loaded from our own server; no data is transferred to third parties such as Google when you visit. The only exception is the booking page with the calendar (see below).
If you contact us by email or phone, we process your details to answer your enquiry (Art. 6(1)(b) GDPR for enquiries relating to a contract, otherwise Art. 6(1)(f) GDPR). We delete them once the enquiry has been dealt with and no statutory retention obligations apply.
On botparkai.com you can ask questions to our own AI assistant, which runs on BotPark. The chat window is loaded from our own server (chat.botparkai.com). If you chat with the assistant or leave a message via the contact form in the chat, we process your messages and details as the controller as described in sections 7 to 9 in order to answer your questions (Art. 6(1)(b) GDPR for questions relating to a contract, otherwise Art. 6(1)(f) GDPR). We delete conversations and contact requests after 90 days.
On the booking page (botparkai.com/en/termin), which you open via “Book a call” or “Choose a time”, you can book a call with us. The calendar there is provided by Cal.com, Inc. (USA); only on this page is content loaded from Cal.com's servers; Cal.com processes your IP address and details about your browser and device and may set cookies or similar storage. If you book a call, you enter the details in the booking form (in particular name, email address and chosen time) directly with Cal.com; we receive them to prepare and hold the call and invite you to a video conference (Zoom). The legal basis is the performance of pre-contractual measures at your request (Art. 6(1)(b) GDPR); access to storage on your device takes place insofar as it is necessary for the booking you requested (Section 25(2) no. 2 TDDDG). Data may be transferred to the USA in the process. We delete booking data once it is no longer needed for the call and a possible collaboration.
6. Customer account and dashboard
When you create an account or are invited to a team, we process:
- account data: email address, name, password (only as a cryptographic hash) and, for each sign-in, the time, IP address and browser – to keep you signed in; deleted when you sign out, at the latest 30 days after last use,
- organisation data: the company's name, chosen address and logo, plan, settings, and team members' roles and permissions,
- usage data: which bots, knowledge content and settings you create or change, a change log (who changed what and when), your availability for live chats and the messages you send to visitors as an agent; your name is shown to visitors as their contact person,
- invitations: the role, a note and – if the invitation is sent by email – the invited person's email address; the invitation link is stored only as a hash and expires automatically.
The purpose is to provide the dashboard and perform the contract with your company (Art. 6(1)(b) GDPR). If you are invited as a team member, processing is based on your company's and our legitimate interest in the joint use of the service (Art. 6(1)(f) GDPR). The change log serves traceability and security (Art. 6(1)(f) GDPR).
Emails to confirm your address and to reset your password, security notices (for example after a password change), team invitations, notices about your plan's usage and reminders about the end of the free trial are sent via our mail server at IONOS. We keep a record of which email went to which address and when for 30 days.
Payment: you subscribe through our payment service provider Stripe. For this we transmit to Stripe the name of the organisation, the email address of the person subscribing and the chosen plan. Payment details (such as card number or IBAN), billing address and VAT ID are entered directly at Stripe; we do not receive them. We only store the identifiers of the customer and subscription at Stripe, the plan, the billing period and the status of the subscription (for example active, cancelled or payment failed). The legal basis is the performance of the contract (Art. 6(1)(b) GDPR); we retain invoices because of legal obligations (Art. 6(1)(c) GDPR). For the free trial we record per account that it has been used, so that it is only available once (Art. 6(1)(f) GDPR).
Payments for bookings in the chat: if your company wants guests to pay for bookings in the chat, it connects its own Stripe account. For this we create a connected account at Stripe and transmit the email address of the person setting up the connection. Details about the company, its authorised representatives and its bank account are entered directly at Stripe; we do not receive them. We only store the account identifier and its status (for example whether payments and payouts are enabled or details are missing). We store the credentials of connected booking systems encrypted. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR).
We store account data for as long as the account exists. When a company deletes its organisation, all associated bots, knowledge content, conversations and memberships are deleted immediately. Records we must keep for tax and commercial law reasons (in particular invoices) are retained for up to ten years (Section 147 AO, Section 257 HGB).
7. Cookies and browser storage
In the dashboard we only use technically necessary cookies that keep you signed in. In addition, we store settings such as your chosen appearance (light/dark) and recently opened views in your browser's local storage.
In chat windows we store a random visitor ID, your appearance choice and – only if the operating company has enabled it – your previous conversations in your browser's local storage so that you can continue them on your next visit. The embedded chat window also remembers for the duration of the session whether you closed the hint next to the chat button. If you agreed to the company's guest profile when booking, we additionally store a random identifier by which the chat window recognises you on your next visit; “Not you?” in the chat removes it. We do not set advertising or analytics cookies.
This storage is strictly necessary for the functions you explicitly request (Section 25(2) no. 2 TDDDG); we only store the guest profile identifier with your consent (Section 25(1) TDDDG). You can delete this storage in your browser at any time; in the chat window you can also remove your conversations yourself.
8. Chatbots: visitor data
Chatbots for visitors are labelled as AI. When you chat with such a chatbot, we process on behalf of the operating company:
- the messages you enter and the chatbot's answers including the sources used,
- a random visitor ID, the language, the channel (embedded or chat page), the address of the website where the chat is embedded, and timestamps,
- an automatic evaluation of the conversation (topic, sentiment, whether the question was answered) and questions the chatbot could not answer – so that the company can improve its service,
- if you are handed over to an agent: the conversation with the company's agent,
- if you fill in a contact form in the chat: the details the company asks for in it – always your email address and, depending on the form, for example your name, phone number, company, your request and further fields defined by the company,
- if you fill in another form in the chat (for example to check the status of an order or to create, change or cancel a booking): the details you enter in it,
- if you book in the chat: the details the chat asks for to make the booking (depending on the offer, for example offer, date, time, number of people, choices and extras as well as name, email address and phone number), your acceptance of the company's terms, a discount code if you enter one, the quote with price from the company's booking system, the booking number and the status of the booking and payment,
- if you buy a gift voucher in the chat: the voucher and amount chosen, your name and email address, your phone number if the company's booking system requires it, if you wish the name of the recipient and a message, the voucher code and the status of the voucher, payment and redemptions,
- if you sign up for or unsubscribe from the company's newsletter in the chat: your email address, if you wish your first name, the text of your consent, the language and when you signed up, confirmed and unsubscribed,
- if you agree to a return-visit reminder when booking: your email address, the text of your consent, the language, the related booking, the send date, the discount code sent with it if any, and the times of sign-up, confirmation, sending and unsubscribing,
- if you agree to the company's guest profile when booking: your name, email address and phone number, the answers the company has selected for the guest profile (such as a child's name or birthday), your bookings with this company, the text of your consent with its time and an identifier of your browser (stored by us only as a hash).
We do not store your IP address. To protect against abuse (e.g. mass requests or manipulation attempts), it is merely converted into a salted, irreversible hash used to count requests and temporarily block attackers. These counters are deleted after one day at the latest. The legal basis is our and the company's legitimate interest in a secure service (Art. 6(1)(f) GDPR).
Companies can choose to mask email addresses, phone numbers and IBANs in messages before they are stored and before they are passed on to AI services.
Conversations, contact requests and open questions are automatically deleted after the period set by the company, by default after 90 days. The company can delete or export conversations at any time before then.
Bookings in the chat: available times, prices and the booking itself come from the company's booking system; BotPark is not a booking system. A booking is only made once you have confirmed the summary. We then transmit your details to the booking system the company has connected (for example pretix, Regiondo, ROLLER, bookingkit or the company's own system) and – if the company has set this up – to an interface it has specified (webhook).
If the company has not connected a booking system, you send a request in the chat: when you send it, we email your details to the addresses the company has specified, with your email address as the reply-to address so that the company can get back to you directly. It is sent via the mail server of IONOS SE. Until it is sent, the details are stored encrypted with us; we only store to which address the email was sent and whether it was delivered. A time offered in this case is a preferred time – the company confirms to you whether it is available.
If the company uses a booking link, you book on its own booking page: when you click “Continue to booking”, we open that page and pass the details the chat asked for (such as offer, date, time and number of people) in the page's address so that they are already filled in there. The company decides which details these are. We do not learn whether and how you book and pay there; the terms and privacy policy of the company or its booking system apply. We store that you were forwarded and to which page.
If the booking requires payment, you pay on a Stripe page directly to the company, via its own Stripe account. For this we transmit to Stripe the amount, the name of the booking, the booking number and your email address. Payment details (such as your card number) are entered directly at Stripe; we do not receive them. The amount is first only authorised and only collected once the booking system has accepted the booking – otherwise the authorisation is released or the amount refunded.
We only keep the details of a booking for as long as we need them for the handover: about ten minutes after the booking has been created in the company's system, the emails with a request have been sent or you were forwarded to the company's booking page – or after it was cancelled or expired – we delete your name, contact details, free-text answers and the contents of the log of requests to the booking system. What remains is the booking number, a summary without personal details (for example offer, date, number of people, time), the amount and the status of the booking and payment. If a paid booking does not go through or the email with your request is not delivered, your details remain until the conversations' deletion period ends so that the company can reach you. Bookings that were started but neither booked nor paid are deleted completely after 30 days. The legal basis is the contract you conclude with the company or the steps taken prior to it (Art. 6(1)(b) GDPR).
Gift vouchers: if you buy a gift voucher in the chat, you pay the company via Stripe, as for a booking. We then issue the voucher on behalf of the company – in our system or, if the company has set it up that way, in its booking or till system (for example as a gift card in pretix or ROLLER, as a voucher in Regiondo or in a system of the company's own). For this we transmit the voucher with amount and code as well as your name, your email address, your phone number where required, the recipient's name and the message to that system. We email you the code and a link to view and print it (via the mail server of IONOS SE) – unless the company's system sends the voucher itself. Anyone who knows the link or the code can see or redeem the voucher. We keep the voucher with your details as long as it can be redeemed; one year after it has been fully redeemed, cancelled or has expired we delete your name, your email address, your phone number, the recipient's name and the message. The code, the value and the history of redemptions remain. The legal basis is the contract you conclude with the company (Art. 6(1)(b) GDPR).
Newsletter: if the company offers its newsletter in the chat, you only sign up by ticking the checkbox for it yourself – on a card in the chat, when booking or when buying a gift voucher; the booking or purchase works without it too. You then confirm your sign-up via a link in an email (double opt-in). We send this email on behalf of the company (via the mail server of IONOS SE) – or, if the company has set it up that way, its newsletter tool does. We store your email address, your first name if given, the text of your consent and when you signed up and confirmed as proof for the company and, if it has set this up, pass the sign-up on to its newsletter tool (for example Mailchimp, Brevo, CleverReach or rapidmail) or via webhook to an interface it specifies. If the newsletter tool sends the confirmation itself, we delete your email address and first name as soon as the sign-up has arrived there. If you do not confirm, we delete the sign-up after 30 days. The newsletter itself is sent by the company; its privacy policy applies. You can withdraw your consent at any time – via the unsubscribe link in the newsletter, in the chat or by contacting the company. We record your unsubscribe, pass it on to the company's newsletter tool or interface and keep your email address with the proof as a block note so that you do not receive the newsletter again, until the company deletes the entry; if the newsletter tool holds the proof, we delete the address as soon as the unsubscribe has arrived there. If you unsubscribe in the chat with an address that was not signed up via the chat, we store it only to pass the unsubscribe on to the company. The legal basis for the sign-up is your consent (Art. 6(1)(a) GDPR); for the block note and passing on the unsubscribe it is the company's legal obligation to respect and prove your withdrawal (Art. 6(1)(c) GDPR).
Return-visit reminders: if the company offers an email reminder when you book in the chat – for example in good time before the next birthday or a few days after your visit – you only receive it if you tick the checkbox for it yourself; the booking works without it too. You then confirm the reminder via a link in an email (double opt-in), which we send on behalf of the company via the mail server of IONOS SE. We calculate the send date from the booked day or a date from the booking (such as a child's birthday). For the reminder we store your email address, the language, the send date (not the date it was calculated from) and, as proof for the company, the text of your consent with the times of sign-up and confirmation. If you do not confirm, we delete the reminder after 30 days. On the send date we send you exactly one email with the company's texts, where applicable with a new discount code, and then delete your email address from the reminder; the dispatch log shows which email went to which address and when for another 30 days. If by then the booking has not gone through or has been cancelled, or the company no longer offers the reminder, no email is sent and we delete your address as well. You can withdraw your consent at any time – via the unsubscribe link on the confirmation page and in the reminder, or by contacting the company; we then delete your address immediately. The link also unsubscribes all other open reminders for the same address with this company. Without the address, we keep the entry (for example send date, status and code) for another two years for the company's statistics. The legal basis is your consent (Art. 6(1)(a) GDPR).
Discount codes: the company issues discount codes itself or has them sent with a reminder; the codes contain no details about you. If you enter a code when booking in the chat, we check whether it is valid and transmit it with the discount to the company's booking system or, with your request, to the company. We record with the code when and with which booking it was redeemed. The legal basis is the contract you conclude with the company (Art. 6(1)(b) GDPR).
Guest profile: if the company offers a guest profile when you book in the chat, we only remember your details on its behalf if you tick the checkbox for it yourself; the booking works without it too. With the guest profile your details are already filled in at your next booking with this company (you see and change them in the summary), the chat window in the browser in which you booked recognises you, and the company sees your bookings with it together and can tailor its offers accordingly. We do not send you any emails for this; whether you receive advertising by email depends on your newsletter sign-up. We store your name, email address and phone number, the answers the company has selected for it, the link to your bookings and, as proof, the text of your consent with its time; your browser only holds a random identifier, and we only its hash. The guest profile only applies to this company, never to other companies that use BotPark; we do not pass it on to AI models. We delete it automatically 24 months after your last booking or your last visit to the chat. You can withdraw your consent at any time – with “Delete profile” in the chat or by contacting the company; we then delete the guest profile immediately. “Not you?” in the chat only removes the identifier from your browser. The legal basis is your consent (Art. 6(1)(a) GDPR, for the identifier Section 25(1) TDDDG).
The legal basis for processing chat data is the relationship between you and the operating company, usually answering your enquiry (Art. 6(1)(b) GDPR) or its legitimate interest in customer communication (Art. 6(1)(f) GDPR). Details can be found in the company's privacy policy. Please do not enter particularly sensitive data (e.g. health data) in the chat unless necessary for your request.
9. Use of AI services
To enable the chatbot to answer, your message, the conversation so far and matching excerpts from the company's knowledge are transmitted to AI services. The language model that writes the answer (DeepSeek V4.1 Flash, an open model operated in Europe – no data goes to its developer) is provided by GreenPT BV (Netherlands) via its EU endpoint in data centres in France and Finland. If it does not respond in time or is disrupted, a backup model (Qwen) at Scaleway SAS or OVH SAS (both France, data centres in France) handles the same request. Search vectors (embeddings) are generated by the Generative APIs of Scaleway SAS, during disruptions by OVH SAS. Berget AI AB (Sweden) checks messages and answers – for example for manipulation attempts and whether an answer is covered by the company's content – as well as ingested content, and evaluates completed conversations (resolved, sentiment, topic). A model at IONOS SE (Germany) assesses which excerpts of the knowledge match your question. These two kinds of requests are routed by EUrouter B.V. (Netherlands), exclusively to data centres in the European Economic Area. Each provider only receives the data it needs for its task.
The AI generates answers based on the company's content. It does not make decisions that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). Answers may be inaccurate; binding information is available from the company itself.
10. Recipients and sub-processors
We only share personal data with service providers we need for operation and with whom we have concluded data processing agreements pursuant to Art. 28 GDPR. For customer data, these providers are also sub-processors within the meaning of section 12:
- IONOS SE, Elgendorfer Str. 57, 56410 Montabaur, Germany – server operation including database, files and backups (hosting), sending of emails (forwarding of contact requests, emails about accounts, invitations and plans, and emails to guests such as vouchers, confirmations and reminders) and, via EUrouter, assessing matching knowledge excerpts (reranking). Location: Germany.
- EUrouter B.V., Jacob van Lennepstraat 78H, 1053 HM Amsterdam, Netherlands – routing of requests for checks and reranking exclusively to data centres in the European Economic Area. Location: Netherlands.
- Berget AI AB, Götgatan 18, Stockholm, Sweden – checking messages, answers and ingested content and evaluating completed conversations (via EUrouter). Location: Sweden.
- GreenPT BV, Plompetorengracht 4, 3512 CC Utrecht, Netherlands – language model (EU endpoint). Location: data centres in France and Finland.
- Scaleway SAS, 8 rue de la Ville l'Évêque, 75008 Paris, France – embeddings (Generative APIs) and backup for the language model when GreenPT does not respond in time. Location: France.
- OVH SAS, 2 rue Kellermann, 59100 Roubaix, France – backup for the language model and embeddings (AI Endpoints) when Scaleway does not respond in time. Location: France.
For subscription payments we use Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland (payment processing, invoices, subscription management). Stripe only receives data about the customer account and payment, no data from the chatbots or the customers' knowledge, and is therefore not a sub-processor within the meaning of section 12. To verify payments and prevent fraud, Stripe also processes data as an independent controller; details can be found in Stripe's privacy policy (stripe.com/privacy).
For payments for bookings and gift vouchers in the chat, Stripe is the payment service provider of the respective company: payment goes to the company's own Stripe account on the basis of its contract with Stripe. We only transmit to Stripe what is needed for the payment (amount, name and number of the booking or voucher purchase, the guest's email address) and only receive the payment status from Stripe. Here too, Stripe processes data to verify payments and prevent fraud as an independent controller.
Within a customer company, the team members authorised by the company can see conversations and contact requests. Where the company has set this up, we also send contact requests by email to the addresses it has specified and to an interface it has specified (webhook, such as its CRM), and transmit details that visitors confirm in the chat (for example a booking) to the company's database or booking system or – without a booking system – by email to its addresses. The email contains all details from the contact form and gives your email address as the reply-to address so that the company can reply to you directly; it is sent via the mail server of IONOS SE. For this we only store to which address the email was sent and whether it was delivered – this information is deleted together with the contact request. What arrives in the recipient's mailbox is the responsibility of the company. In all cases the recipient is the company itself or a body designated by it. Beyond that, we only disclose data where we are legally obliged to do so.
11. Transfers to third countries
Data from the chatbots, the knowledge and the conversations are not transferred to countries outside the European Union; we process them exclusively in data centres in the European Union (locations in sections 4 and 10). Which booking system a company connects and where that system processes data is determined by the company; details can be found in its privacy policy.
For payment processing, Stripe may transfer data about the customer account and payment – including payments for bookings in the chat – to Stripe, Inc. in the USA. It is certified under the EU-US Data Privacy Framework, for which an adequacy decision of the European Commission exists (Art. 45 GDPR); standard contractual clauses also apply (Art. 46(2)(c) GDPR).
12. Processing on behalf of our customers (Art. 28 GDPR)
For companies using BotPark, the following terms apply to the processing of personal data on their behalf. They form part of the contract for the use of BotPark.
- Subject matter and duration: provision of the chatbot software including storage of knowledge content, conversations, contact requests, bookings, gift vouchers, discount codes, return-visit reminders, guest profiles and newsletter sign-ups from the chat for the term of the contract.
- Nature and purpose: storing, searching and evaluating content, generating answers with AI, routing conversations to agents, forwarding contact requests by email and webhook, handing over bookings to the customer's booking system, forwarding booking requests by email or guests with their details to the customer's booking page and initiating payment via its Stripe account, issuing, sending and redeeming gift vouchers (also in the customer's booking or till system, for example as gift cards in pretix or ROLLER), receiving newsletter sign-ups with confirmation by email and passing them on to the customer's newsletter tool, issuing, checking and redeeming discount codes (also when booking in the chat), receiving return-visit reminders with confirmation by email and sending them with the customer's texts and, where applicable, a discount code, keeping guest profiles with the guests' consent (prefilling bookings, recognising guests in the chat, selection and export for the customer), deletion according to the configured periods and after a booking has been handed over.
- Data subjects: chatbot visitors, the customer's contact persons and staff, and persons whose data are contained in content provided by the customer (websites, documents, databases).
- Types of data: chat messages, details from forms in the chat (e.g. name, email address, phone number, company, request and fields defined by the customer), booking details (offer, date, time, number of people, choices, contact details, amount, status of booking and payment), gift voucher details (code, value, balance, buyer's name, email address and phone number where required, recipient, message, redemptions), newsletter sign-up details (email address, first name, consent text, when signed up and confirmed), discount code details (code, discount, validity, status, redemption with booking), reminder details (email address, language, consent text, send date, when signed up, confirmed, sent and unsubscribed), guest profile details (name, email address, phone number, answers selected by the customer, bookings, consent text and time, browser identifier as a hash), email addresses of the recipients of contact and booking requests specified by the customer, visitor IDs, usage and evaluation data, and any personal data the customer stores or connects as knowledge.
- Instructions: we process the data only on documented instructions from the customer; the contract, the dashboard settings and instructions in text form count as instructions. If we believe an instruction infringes data protection law, we will inform the customer.
- Confidentiality: persons with access to the data are bound to confidentiality.
- Security: we implement the technical and organisational measures described in section 13 (Art. 32 GDPR) and adapt them to the state of the art.
- Sub-processors: the customer authorises the providers listed in section 10. We inform customers of intended changes in advance by email; the customer may object within 14 days for an important data protection reason and, if no solution is found, terminate the contract. We contractually bind sub-processors to the same data protection obligations.
- Assistance: we assist the customer with data subject requests – in particular through the export and deletion functions in the dashboard – and with its obligations under Art. 32 to 36 GDPR.
- Personal data breaches: we notify the customer without undue delay after becoming aware of a breach affecting its data.
- End of processing: after the contract ends or when the customer deletes its organisation, all of the customer's data are deleted unless there is a legal obligation to retain them. The customer can export its data beforehand.
- Evidence and audits: we provide the customer with the information necessary to demonstrate compliance with these obligations and allow audits by prior arrangement.
13. Technical and organisational measures
- Encrypted transmission of all connections (TLS); credentials of connected databases and booking systems are stored encrypted.
- Strict separation of different customers' data: every access is checked against organisation, role and assigned bots; the database cannot be reached from the internet.
- Role and permission concept for team members, passwords and invitation links only as hashes, change log.
- Server access only via cryptographic keys, regular security updates.
- Storage in a data centre in Germany, encrypted backups every six hours, automatic deletion periods, export and deletion functions.
- Abuse protection: request limits, detection of manipulation attempts, quarantine of suspicious content, checking of all answers.
- Connected databases are used only with queries and actions defined by the customer. Reading takes place in read-only transactions; writing is limited to what a visitor has confirmed in a form, capped per conversation and logged.
- Bookings: a booking is only made after the guest has confirmed the summary and the price has been checked again with the booking system, each booking exactly once; requests via BotPark's booking interface are signed. Personal details are deleted after the handover.
14. Your rights
Vis-à-vis the respective controller, you have the right to
- access to the data stored about you (Art. 15 GDPR),
- rectification of inaccurate data (Art. 16 GDPR),
- erasure (Art. 17 GDPR) and restriction of processing (Art. 18 GDPR),
- data portability (Art. 20 GDPR),
- withdraw consent with effect for the future (Art. 7(3) GDPR),
- lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). The authority responsible for us is the State Commissioner for Data Protection and Freedom of Information of Baden-Württemberg, Lautenschlagerstraße 20, 70173 Stuttgart, Germany.
Right to object (Art. 21 GDPR)
Where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you may object at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, or the processing serves the establishment, exercise or defence of legal claims.
An informal message to info@orderpark.de is sufficient for all requests.
15. Obligation to provide data
An email address and password are required to use the dashboard; without them we cannot create an account. Using a chatbot is voluntary; you only provide details in a contact form if you wish to be contacted. For a booking in the chat we need the details the chat asks for; without them the company cannot accept the booking.
16. Changes
We update this privacy policy when our service or the legal situation changes. The version published here applies.