Privacy Policy
Version 2.3 · Revised: 17 November 2026
What data we use, why, and how to exercise your rights.
In this document
1. Who processes your data
QUANTEMI S.R.L. · CUI 54694424 · Trade Register J2026031979003
Năvodari, Jud. Constanța, Str. Liniștii nr. 8, România
contact@rezervatio.ai · Data protection: privacy@rezervatio.ai
Rezervatio is controller for account administration, personal Book features, the website, support, security and its own commercial relationship. The selected organization is controller for its services, customers and staff. Rezervatio acts as processor under the DPA for data managed on the organization’s behalf through Business. The role follows the particular purpose, not just the app being used.
2. Data and sources
Data comes from you, the organization you interact with, a person representing you, your use of the service and, if selected, Apple/Google authentication. Not every category applies to every user.
- Account and organization: name, phone, email, authentication identifiers, roles, invitations, business and billing details, settings and relevant operation logs. Apple may provide a relay email address.
- Bookings and Business: service, date, time, participants, specialist/resource, confirmed price and offer, status, notes, messages, photos chosen as attachments and change history. Customer and garage work records may contain contact details, vehicle information, registration plate, mileage and work/parts.
- Book and public content: favorites, follows, requested alerts, reviews and ratings, reactions/saves, event requests and reports. Reviews and content chosen for publication are visible according to the feature, with the display name and information shown when publishing. Booking messages and private photos have authorized recipients, not a public audience.
- AI calls, only when used: phone, voice, transcript/summary, date, duration, outcome and booking details. At the start of the call, the assistant introduces itself as the business’s AI assistant and announces that the call is recorded and processed. For healthcare organisations, the conversation summary is not kept. The basic Starter plan has no AI agent; app use or a digital booking does not itself involve an AI conversation.
- Support and security: request contents, information needed to resolve it, recorded IP, technical session/device information and records of submitted declarations. Depending on the flow these may include declaration type, document version, language, date/time and account/organization context.
- Payments, where available: billing information, amount, status and transaction reference. The provider and data required by the payment method are presented before the transaction. Accepting terms does not authorize a charge.
Required fields are identified in the flow. Without necessary data we cannot provide the requested feature; declining optional data or permissions does not block unrelated features.
2.5 Demo call
If you request a demo call, we process your phone number, OTP verification, anti-abuse information and the conversation needed for the demonstration. Your voluntary request concerns that demonstration, not later marketing. AI and conversation-processing information must be provided before the interaction. Demo requests are kept for 30 days; OTP expires after 5 minutes, with related records cleared after 24 hours.
2.6 Founding Business application
If you submit the Founding Business form, we process the company name, the contact person’s name, telephone number, email, business type, city, website, the Facebook, Instagram or TikTok profiles you indicate and your message. Mandatory fields are needed to assess the application; without them we cannot process it. For security and to know where applications come from, we also record the browser type, the referring page, campaign parameters (UTM) and a pseudonymised value (hash) of the IP address, instead of the IP address in clear.
We use this data to assess the application and to contact you by telephone or email about the program. Our team records in an internal register the status of the application (for example, contacted or no reply) and notes on contact attempts, with the author and date of each note. The legal basis is our legitimate interest in administering the program and the relationship with business representatives (Article 6(1)(f) GDPR). The checkbox in the form confirms your request to be contacted; it is not consent within the meaning of Article 6(1)(a) GDPR. You can object at any time by writing to privacy@rezervatio.ai; in that case we delete the application, its status and the associated notes without undue delay, within one month at most, and we no longer contact you. The data is hosted and transmitted through the providers in section 5 (for example Hetzner, Cloudflare, Scaleway). Your other rights are described in section 8, and complaints to the authority in section 13.
The application, including its status and notes, is deleted automatically 180 days after submission. If the business receives a Founding place, we keep the record of the place (place number, company name, tax identification number (CUI), confirmation details and, where applicable, the date and reason the place was lost) in order to apply and evidence the rate (Article 6(1)(b) GDPR and, for representatives of legal entities, Article 6(1)(f)). When the organization’s account is deleted, the record is anonymised: only the place number, status and calendar dates remain.
3. Purposes and legal bases
- Contract with the individual — Article 6(1)(b) GDPR: Book accounts, bookings and requested features; necessary communications; pre-contractual steps requested by the person.
- Legitimate interests — Article 6(1)(f): managing relationships with organization representatives, security and abuse prevention, complaint handling and defending rights. We assess necessity, impact and objection rights; this basis does not replace consent required for optional statistics or marketing.
- Legal duties — Article 6(1)(c): tax records, lawful authority requests and applicable platform obligations.
- Consent — Article 6(1)(a): the AI demonstration requested with agreement in that flow, optional website statistics, marketing and features for which we separately request agreement. Refusal or withdrawal does not affect features independent of that purpose.
For processing on the organization’s instructions, it determines the lawful basis concerning its customers and staff; the DPA and B2B subscription do not replace that basis. Accepting terms or receiving a policy is not general consent.
4. Permissions, communications and sensitive data
- Location: optional for nearby search; coordinates may be sent to the service for results. You can choose a town manually.
- Camera and photos: QR scanning may occur locally; photos selected as attachments are uploaded when you submit the request. The entire photo library is not sent.
- Calendar: at your request the app identifies an available calendar and adds/removes the booking event. Other events are not sent to Rezervatio.
- Push: the token and necessary content pass through delivery services. Device permission is not general marketing consent. Confirmations and requested alerts are distinct from commercial promotion.
Device permissions can be changed in settings. Backup email: if notifications in the Book app are turned off, we send the appointment confirmation and reminder to the account’s verified email address, with the business, date and time, address and code, without the service, specialist or price. You can turn them off in the app, under Settings → Notifications. Marketing and optional statistics have separate choices under Romanian Law 506/2004 and GDPR. Following a business or requesting a demo does not itself authorize unsolicited commercial messages.
Health data can occur in clinic appointments, allergies, messages or photos, including outside clinics. An Article 6 basis, an Article 9 GDPR condition and appropriate safeguards are required. Spontaneous disclosure does not remove protection. Do not send medical records or sensitive information that is unnecessary. Neither the platform nor the AI agent is intended for diagnosis, triage or emergencies.
5. Recipients and providers
The recipient business and authorized staff receive data needed for your request. Published data is publicly accessible according to the feature. Our providers receive data only for services actually used; using a shared SMS or hosting provider does not enable AI. Professional advisers or authorities may also receive data where there is a lawful basis.
Providers fall into the following categories:
- Hosting and infrastructure: servers and databases in the European Union.
- Security and traffic: protection against attacks and abuse, content delivery.
- Email: sending account and appointment emails; our contact and support mailboxes.
- Telephony, SMS and AI voice: telephone numbers, calls and SMS messages; the conversation with the AI Assistant, only when the feature is used.
- Sign-in and notifications: signing in with Apple or Google and delivering notifications to your phone.
- Maps and location: displaying the map, place suggestions and the coordinates of the business address.
- Payments: processing card payments for subscriptions, once payments are enabled.
The list of providers by name, with each provider’s role, processing country and purpose, is in Annex 1 — Our providers.
Social sign-in and Apple/Google’s own services also follow those providers’ conditions. For organizational data, sub-processor lists and change procedures are in the DPA. We do not sell personal data.
6. EEA processing and transfers
Core infrastructure is hosted in the EU. International providers may also process data outside the EEA depending on service, support and configuration. An EU server location alone does not prove that no transfer occurs.
Transfers require an applicable GDPR Chapter V mechanism: an adequacy decision covering the recipient and processing, or appropriate safeguards such as standard contractual clauses with necessary assessments and supplementary measures. DPF certification may be relied on only for the entity and service actually covered. You can request destination information and a copy of applicable safeguards at privacy@rezervatio.ai, protecting others’ data.
7. Data retention
We retain data for as long as needed for its purpose. Active accounts and preferences are retained during use; organizational data follows its instructions and the DPA. Records needed for a legal duty or dispute are separated and limited to necessity. Retention periods by data category are in Annex 2 — How long we keep data.
Public content, reviews and reports are retained as needed for publication, resolution or defending rights; requests may result in deletion, restriction or anonymization as appropriate. Customer and garage work records do not automatically become unnecessary when a booking expires: the organization determines necessity and retention instructions. Backups have restricted access and a separate replacement cycle; active deletion does not mean immediate deletion from every copy. Criteria for a particular category can be requested at privacy@rezervatio.ai.
8. Your rights
Under GDPR conditions you may request access and a copy, correction, erasure, restriction, portability of eligible data and object to legitimate-interest processing. Direct-marketing objections are honored without balancing overriding interests. Consent can be withdrawn at any time without affecting previous lawful processing.
Contact privacy@rezervatio.ai or use account tools. The available app export can be supplemented on request with personal data absent from the file while protecting others’ rights. We verify identity proportionately and do not request unnecessary documents. We respond without undue delay and within one month; complexity or request volume may justify two further months, with an explanation in the first month. Requests are generally free.
Account deletion has a seven-day grace period, followed by deletion or anonymization and legal exceptions. Deleting Book does not remove every copy held by the service business. For processing on its instructions, we forward the request and assist it. You can also exercise rights directly with that organization.
9. Security
We apply risk-proportionate measures: encrypted communications, authentication and authorization checks, separation of organizational data, restricted administrative access, relevant logs, backups and recovery/deletion procedures. Measures are reviewed for the service and risk; we do not claim incidents are impossible. Protect your device and credentials and avoid sensitive data in notifications or public content.
10. Incidents and automation
As controller we assess incidents and notify the authority without undue delay, where feasible within 72 hours of awareness, when Article 33 GDPR requires it. Individuals are informed without undue delay under Article 34 conditions. As processor we notify the organization under the DPA and assist it.
Availability rules and business settings may automatically confirm or reject requests; search and News use filters, distance, ratings, follows and recency depending on the feature. These operations do not automatically involve AI. We do not take decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you, within the meaning of Article 22 GDPR. You can request human review of data and outcomes from the business or, for Rezervatio’s own features, at privacy@rezervatio.ai.
11. Cookies and storage
Storage for authentication, security and requested choices is separate from optional statistics. The latter requires separate consent, changeable through “Cookie preferences”. See the Cookie Policy.
12. Updates
We update this notice when features or processing change. Significant changes are communicated through available channels before new processing where required by law. New consent is requested separately when needed. Publishing a policy does not retroactively create a lawful basis.
13. Supervisory authority
You may complain to ANSPDCP or the competent authority in the EU state of habitual residence, workplace or alleged infringement. You do not have to contact us first. Judicial remedies remain available.
14. Contact
privacy@rezervatio.ai · QUANTEMI S.R.L.
Identify the feature and data category concerned; do not send passwords, OTP codes or unnecessary sensitive data.
Annex 1 — Our providers
This Annex forms part of the Privacy Policy and has the same version. Each provider receives data only for the service indicated and only when that service is used.
| Provider | Possible role | Head office / processing regions | Purpose |
|---|---|---|---|
| Hetzner Online GmbH | Processes data on our behalf | Germany, European Union | Hosting the primary infrastructure, backend services and databases managed by Rezervatio |
| Cloudflare Inc. | Processes data on our behalf; controller for certain services of its own | United States / global infrastructure | Security, DDoS and abuse protection, content delivery and traffic management |
| Scaleway SAS | Processes data on our behalf | France, European Union | Transactional and operational emails, including confirmations, invitations and account notices |
| Telnyx LLC | Processes data on our behalf | Storage in Germany (EU), according to our account setting; the provider is based in the United States, and processing, routing and support may also involve the United States or other regions | Telephone numbers, call routing and SMS delivery |
| ElevenLabs Inc. | Processes data on our behalf | United States / infrastructure under the applicable configuration and agreement | Conversation processing for the AI voice agent: speech recognition, voice-response generation and technical transcription |
| Apple Distribution International Limited / Apple Inc. | Service provider and independent controller for its own operations | Ireland / United States and other regions identified in Apple’s documentation | Sign in with Apple and push-notification delivery to Apple devices |
| Google Ireland Limited / Google LLC | Service provider and independent controller for its own operations | Ireland / United States, with global infrastructure | Google sign-in, Android notification delivery through FCM, and maps in Rezervatio Book on Android through the Google Maps SDK. |
| Expo / 650 Industries, Inc. | Processes data on our behalf | United States / global infrastructure | Relaying Book and Business notifications to Apple/Google; EAS services for app and update distribution. |
| Proton AG | Processes data on our behalf | Switzerland (European Commission adequacy decision) | Hosting Rezervatio’s mailboxes (contact, support, data protection): the messages you send us and our replies |
| Komoot GmbH (Photon service) | Service provider and independent controller for its own operations | Germany, European Union | Place suggestions when you search manually for a location in Rezervatio Book: the search text and the technical data of the request, including the IP address, are sent directly from the app to the service |
| OpenStreetMap Foundation (Nominatim service) | Service provider and independent controller for its own operations | United Kingdom (adequacy decision) / international infrastructure | Determining map coordinates for the business address when the profile is set up; the business address is sent, not customer data |
| Stripe Payments Europe, Ltd. / Stripe, Inc. | Processes data on our behalf; independent controller for its own obligations | Ireland / United States | Processing card payments for subscriptions, only once payments are enabled and only for businesses that pay; card details are entered directly with the provider |
Google Maps in Book on Android: the SDK sends Google the IP address, request and device metadata, an SDK-specific pseudonymous identifier, and SDK crash data. When map camera functions are used, it also sends interactions such as panning and zooming. Google uses this data to measure usage, improve SDK stability and improve its services. This technical data is distinct from the optional coordinates used for nearby searches.
Annex 2 — How long we keep data
This Annex forms part of the Privacy Policy and has the same version. Unless stated otherwise, deletion or anonymisation is carried out automatically, through a daily check.
| Data Type | Retention Period | Justification |
|---|---|---|
| User account (active) | For the entire duration of the active account | Necessary for service provision |
| Reservations and related operational data | 12 months after the date of a completed/cancelled/no-show booking; future bookings do not expire before service | Reduction of booking identifiers; deletion of associated messages, history and photos. The business’s own customer records have separate purposes and retention. |
| Call metadata and summaries | 12 months | Deletion or anonymisation under the applicable policy |
| Full audio and transcripts processed by the AI voice provider | 30 days for audio/transcripts, with periodic provider deletion | Deletion under provider settings and procedures; details available on request |
| Technical and security data, including IP addresses and logs | Statistical visits: 90 days, raw IP: 30 days; call sessions/webhooks: 30 days; SMS: 6 months. Other security logs: until incident resolution and expiry of justified need. | Deletion, truncation or anonymisation, as applicable |
| Account after a confirmed deletion request | 7 days (access-restoration grace period) | Afterwards, the active identity is removed and operational data is deleted or anonymised, subject to legal exceptions |
| Consent, export and deletion-request records | Export logs: 12 months; closed deletion requests: 5 years; acceptance/consent history: at most 5 years, retaining the latest status while the account relies on it | Restricted access; deletion when no longer necessary or legally required |
| Billing and tax data | Generally 5 years from 1 July of the year following the financial year; other legal duties may require separate periods | Legal obligation — Tax Code, Accounting Law |
| Demo calls (phone, IP and anti-abuse data) | 30 days | Deletion or anonymisation under the operational procedure |
| Demo OTP codes | Valid for 5 minutes; records cleaned after 24 hours | Invalidation at expiry and subsequent cleanup |
| Push notification logs and appointment email records | 90 days | Deletion |
| Founding Business applications, with status and internal notes | 180 days from submission | Deletion; the record of confirmed Founding places is anonymised when the organization’s account is deleted (section 2.6) |
| News posts published by businesses | 14 days after expiry; abandoned or rejected drafts: 30 days | Deletion, together with the photos |
