Dieses Dokument ist auf Englisch und Rumänisch verfügbar. Unten steht die englische Fassung.
Privacy Policy
Last updated: 28 October 2026
1. Who we are
Rezvy and AnyReserve are provided by CODE SCRYPT STACKER S.R.L. (CUI 46111937, Bulevardul Cetății nr. 1/2, sc. A, et. 2, ap. 10, 300390 Timișoara, jud. Timiș, Romania). For questions about this policy or your data, write to [email protected]. We have not appointed a data protection officer; that address reaches the people responsible.
2. Our two roles
- We are the controller for the data of the people who use our websites and the AnyReserve app (business owners and their team), of the people who contact us, and for billing.
- We are a processor for the data a business puts into AnyReserve about its own customers and staff: bookings, contact details and messages. For that data, the business is the controller, and we process it only on its instructions, under our Data Processing Agreement. If you booked with a business, see section 5.
3. What we collect, why, and on what legal basis
Your account. Email address, name, password (stored only as a one-way hash by our authentication provider), language and chosen plan, and the business details you enter. We use them to provide the Service. Legal basis: the contract with you (GDPR art. 6(1)(b)). An email address is needed to create an account; without it we cannot provide the Service. Other details are optional unless a form marks them as required.
Signing in with Google or Apple. If you choose it, we receive your name and email address from that provider (with Apple, possibly a private relay address that forwards to yours). Legal basis: the contract with you (art. 6(1)(b)).
Your team. The names, email addresses, phone numbers and roles of the people a business adds as staff or invites to its account. We use them to provide the Service to that business. Legal basis: the contract with the business, and its legitimate interest in organising its team (art. 6(1)(b) and (f)).
Activity log. For each business we keep a log of changes made in its account: bookings created, confirmed, moved or cancelled, changes to services, staff, opening hours and settings, the team and billing. Each entry records which member did it (their account and role) and when. Entries never contain customers' names, contact details or notes: a booking a customer made appears only as "a customer" with the booking number. Only the business's owners and admins can see it. If a member deletes their account, their entries remain without their account. Legal basis: the business's and our legitimate interest in knowing who changed what, for accountability and security (art. 6(1)(f)).
Billing. Business name, billing email address, plan and payment status. Card payments are handled by Stripe; we never receive full card numbers. Legal basis: the contract, and our legal obligations to keep accounting records (art. 6(1)(b) and (c)).
Security and usage records. When the app, the widget or a booking page calls our servers, we record the IP address, the browser's user agent, the website the request came from, the time, and, for AI features, the model used and its token counts. We use these records to prevent abuse and fraud, to enforce plan limits, to bill correctly and to keep the Service secure. The IP address is removed from these records after 30 days. For rate limiting we keep only a one-way hash of the IP address, for a few minutes. Legal basis: our legitimate interest in a secure, fairly used service (art. 6(1)(f)).
Messages read by the AI. When a business pastes a message into its Inbox, or a visitor types a request into the booking widget, the text is sent to our AI provider to be turned into a draft booking. Our AI provider does not use it to train its models. We keep the text for 30 days so that we can check the results and fix errors in the Service. After that we keep only a record of how well it worked, without the text, the customer's name or the notes. We do this for the business, as its processor (see section 2). No decision with legal or similarly significant effects is made about anyone by automated means alone: a person always checks and confirms the booking.
Feedback. Ratings (1 to 5) and optional comments that customers and users leave about a visit or about the Service. We do not attach an IP address or contact details to them. Legal basis: legitimate interest (art. 6(1)(f)).
Calendar sync. If a business connects a Google Calendar, we store the access tokens encrypted (AES-256) and copy bookings into a calendar we create for that purpose. Events contain the service, the staff member and a booking number. The customer's first name and phone number are added only if the business turns that option on; email addresses, notes and prices are never included. We ask Google only for permission to create calendars and manage the ones we created; we cannot see the business's other calendars or events. Legal basis: the contract with the business (art. 6(1)(b)).
Google user data. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use it only for calendar sync and sign-in, do not share it with anyone except the providers needed to run those features, and never use it for advertising or to train AI models.
Product analytics, only with your consent. If you agree in the cookie banner, we measure how our websites and the app are used: pages, clicks and screen recordings in which everything you type and every customer detail is hidden. The service, PostHog, stores this data in the EU. Legal basis: your consent (art. 6(1)(a)), which you can withdraw at any time under Cookie settings.
Error reports. When something breaks in the app, our servers or our websites, a technical report goes to our error-tracking service, Sentry, which stores it in the EU (Germany): what failed and where in our code, the page address without its query string, and the browser and operating system. Reports are built to leave out customer content: no form input, no booking details or notes, no email addresses, no IP address and no account. Nothing is stored in your browser for this. Legal basis: our legitimate interest in a service that works and is secure (art. 6(1)(f)).
Booking confirmations and reminders. If a business turns them on, we send its customers an email and/or a text message (SMS) when a booking is confirmed and before it starts, with a link where they can see the booking and cancel it. We do this for the business, as its processor (see section 2), using the contact details given with the booking. We keep a record of which messages were sent, with neither the email address nor the phone number, for 400 days; it also shows how many SMS a business used, which is how they are billed.
Emails. We send emails that the Service needs: address confirmation, sign-in links and password resets, team invitations, trial and payment reminders, and, when a business sends one, a request to rate a visit. We do not send marketing emails without your consent.
4. Who receives data
We share data only with providers that help us run the Service, under contracts that oblige them to protect it, and only as far as each one needs:
- Supabase (database and sign-in), hosted in Frankfurt, Germany.
- Hostinger (servers), data centre in Frankfurt, Germany.
- Cloudflare (network, TLS encryption, protection against attacks); traffic passes through its global network.
- Anthropic (AI that reads booking messages), USA.
- Resend (sending emails), USA.
- Twilio (sending text messages, only for businesses that turn SMS on), USA.
- Stripe (payments), Ireland.
- PostHog (product analytics, only with consent), hosted in the EU.
- Sentry (error reports, without customer content), hosted in the EU (Germany).
- Google (calendar sync and Google sign-in, only if a business or user chooses them).
- Apple (Sign in with Apple, only if you choose it).
We do not sell personal data and do not use it for advertising. We may disclose data where the law requires it, or to protect our rights.
5. If you booked with a business {#bookings}
When you book through a business's Rezvy widget or AnyReserve booking page, that business is responsible for your data; we store and process it for the business. The business receives your name, phone number, email address if you give it, the time and service you chose, and any notes or message you write. If you typed a request in the widget, the text was read by our AI provider to prepare the booking form, as described in section 3. If you used voice input, your browser converts speech to text; some browsers use their maker's online service for this.
If the business turned them on, you get a confirmation and a reminder by email or SMS. Each has a link where you can see the booking (business, time, service and place) and cancel it until it starts. Anyone who has the link can do the same, so do not forward it. To stop these messages, ask the business.
For questions about your booking data, or to exercise your rights, contact the business first. We help businesses answer such requests. You can also write to us, and we will pass your request on.
6. Transfers outside the EU
Some of our providers are based in the USA (Anthropic, Resend, Twilio, Cloudflare, and the parent companies of some others). Where data leaves the European Economic Area, the transfer is protected by the EU-US Data Privacy Framework where the provider is certified under it, or by the European Commission's standard contractual clauses.
7. How long we keep data
- Account and business data: while the account exists. Closing a business or deleting an account in the app deletes the data at once; if you ask us by email, we do it within 30 days. A business that nobody has signed in to for 12 months and that has no paid subscription is deleted, and so is an account in no business after 12 months without a sign-in; we email a warning 30 days before. To know when someone was last active, we record the time of their latest signed-in visit.
- Bookings and customer details: until the business deletes them or closes its account.
- Messages read by the AI: the text for 30 days; the record without the text for up to 400 days.
- Security and usage records: up to 400 days; the IP address in them, 30 days.
- Activity log: 12 months.
- Feedback: up to 400 days.
- Record of booking confirmations and reminders sent (without the email address or phone number): 400 days. The link in them stops working a day after the booking.
- Hashed IP addresses used for rate limits: a few minutes.
- Error reports: up to 90 days.
- Invoices and accounting records: as long as Romanian accounting law requires.
- Backups: deleted data can remain in database backups until they are overwritten, at most 30 days later.
8. Cookies and local storage
We use only what the Service needs to work, plus analytics if you agree:
- Needed: your sign-in session, the business you have open, your language and your cookie choice (in your browser's local storage); on the Rezvy site, a language cookie (`rezvy_lang`, one year); in the widget, your language. Cloudflare may set a short-lived security cookie to tell visitors from bots.
- Analytics, only with consent: PostHog's storage, as described in section 3.
You can change your choice at any time under Cookie settings at the bottom of the page.
9. Your rights
You have the right to access your data, to have it corrected or deleted, to restrict or object to its processing, to receive it in a portable format, and to withdraw consent at any time, without affecting what was done before. Write to [email protected]. We answer within one month. In the app, business owners can export their business's data and close the business, and anyone can delete their own account (Account in the account menu).
You also have the right to complain to the Romanian data protection authority, ANSPDCP (dataprotection.ro), or to the authority of the EU country where you live or work.
10. Security
Connections are encrypted (TLS). Data is stored in the EU. Access is limited to each business's own members, enforced in the database. Calendar tokens are encrypted, and share and calendar links are stored only as one-way hashes. Only a small number of authorised people at our company can access data, and only to run and support the Service.
11. Children
The Service is not intended for anyone under 18, and we do not knowingly collect children's data for our own purposes. A business may book appointments for children, for example at a clinic; in that case the business is responsible for that data.
12. Changes
If we change this policy, we publish the new version here with a new date. For important changes we also tell account holders by email.
Also available in Română. If the two versions differ, the English text prevails, except where Romanian consumer law requires the Romanian text.