Skip to main content
Vitrina

Privacy policy

Version of November 18, 2026

This policy explains how we process the personal data of visitors to vitrina.cafe: the technical data our host receives when you open a page; the data you leave in our forms (the demo call request and the venue launch application); and, only with your consent, the data Google receives through advertising cookies.

Who is responsible for the data

The data controller is Complete solution s. r. o., Ulica Jozefa Adamca 9983/24, 917 01 Trnava, Slovak Republic, IČO 56693371. For any question about personal data: privacy@complete-solution.eu.

What data we receive

When you open any page, our host Vercel receives your IP address and technical browser data in order to deliver the page and protect the site from attacks. Required: your name, venue name and phone number. Neither law nor contract obliges you to give us these details; without the required fields we simply cannot answer your request. Optional: email, city and country, number of locations, type of venue, what you are interested in, which delivery aggregators you work with, which software you use for orders or accounting now, whether you want a test drive (your own login to the demo café), and your comment. Collected automatically: the page language and market (Ukraine or EU), campaign tags (utm) from the page address, if any, and technical data needed to protect the form from spam, namely your IP address (held temporarily to limit repeated attempts) and the result of the Cloudflare Turnstile check. The Turnstile widget loads only when you start filling in the form: Cloudflare checks your IP address and technical browser data to tell a person from a bot. The form cannot be sent safely without this check, so we do not ask for consent to it. Test drive, only if you tick the box: your email is then required, because the login is sent to it. We pass our demo stand the request number, the page language and a keyed fingerprint of your email (HMAC) from which the address cannot be recovered; the stand receives no name, phone number, venue name or the address itself. The stand issues a login to your own outlet, and we email it to you right away. Venue launch application. Required: the venue name and type, country and city, website languages, where the website will live (our address or your name), palette, fonts and home page layout, plan, your name, phone and email, and your confirmation that you may apply on behalf of the venue. Optional: the venue’s own domain, your own main colour, a logo (a PNG, JPEG or WebP file), a separate phone and email of the venue for guests, details for the contract (company name or the name of the sole trader, legal form, registration number, VAT number, registered address), what the venue needs, which delivery platforms you work with, which software you use now, and a comment. Collected automatically: the same as for the demo request. While you fill in the application, the venue name, country, languages, palette, fonts, layout and colour are sent to our server to show a preview of the website; we do not store these requests. AI logo, only if you click “Create an AI logo”: the name on the logo (the venue name, which you can shorten), the venue type, the chosen style and the colours are sent to our server and from there to the Google Gemini API service to draw logo variants. Your contact details and other application data are not included, and drawing the logo itself needs no personal data. To keep the spending limit, our server writes into its spending log, for every variant, the wizard session tag (a random string your browser creates for this application), a daily pseudonym of your IP address (the site passes the server not the address itself but a code that changes every day, so different days cannot be linked), the chosen style and colours, and the variant number; the name on the logo is not written to the log. Paying for the launch on the site, if you choose it. You enter your card details, company name, billing address and, if you have one, your tax number on the Stripe payment page. We do not receive the card details; Stripe sends us the confirmation of the payment, its amount, the payment’s risk assessment, the Stripe customer ID and, for invoices, the company name, address and tax number. Before payment or before sending the application for approval: your acceptance of the Express Terms on behalf of the venue. For the acceptance we record the version, language and text of the Terms, the time, the IP address from which you accepted them and your email and, if you pay, also the number of the Stripe payment session. Free start on the Express plan (“On my own, free”), if you choose it: there is no payment on this path, so there are no card or payment details either, and a person on our team reviews the application together with the record of acceptance of the Terms. Separately from the record we keep your email and a daily pseudonym of your IP address (a code, different every day, in place of the address itself; we keep the address itself only in the record of acceptance of the Terms) to count how many applications without payment arrived in a day. For the review we record the decision (approved or rejected) and its time and, if the application is rejected, the reason, which we send you by e-mail. Google advertising cookies, only after you click “Accept” in the cookie banner. The Google Ads tag stores a cookie with a random identifier in your browser and tells Google which pages of the site you opened (the address without parameters, except utm campaign tags and the gclid ad click identifier), which ad brought you here and whether you sent a request. Google does not receive your name, the venue name, your contact details, or the content or number of your request; like any server your browser contacts, it sees your IP address and technical browser data.

Why we process it

To respond to your request, give you a demo and prepare a commercial offer. For a test drive: to set up your outlet on the demo stand and email you the login right away; the keyed fingerprint of your email lets us give one free trial per address. For a launch application, also to prepare the setup of your venue’s website, send you a confirmation of the application by email and, once a contract is signed, launch the website; the phone and email for guests appear on the venue’s website only after the launch. We pass on the name, venue type, style and colours for the AI logo only to draw logo variants for your application at your request. The AI logo log is needed to keep the spending limit (at most three attempts per application and a limited amount per address per day) and to protect the service from abuse. If you pay for the launch on the site, we also need this data to accept the payment, check it for fraud, issue invoices and launch the website. The record of your acceptance of the Express Terms is needed to conclude the contract with the venue itself, to send you the text of the accepted Terms by email and, if needed, to prove who concluded the contract, when and on what terms. We process an application without payment so that a person on our team can check it before the launch and decide on it: after approval, to conclude the contract, email you its text, launch the website and collect the fee on online payments (withheld through Stripe or invoiced); after a rejection, to send you an e-mail with the reason and a link to the wizard, so that you can send a corrected application. Your email and the daily pseudonym of your IP address, kept separately from the record, are needed to limit the number of applications without payment per day from one email and from one address and to protect the review from spam. This limit only postpones the next application; the decision on the application itself is made by a person, not by a program. The nightly encrypted copies of our panel database are needed to restore the database after a failure and to check that restoring works. We don’t use this data for advertising, don’t sell it and don’t make automated decisions about you. Google advertising cookies, if you consented to them, let us count how many visitors and requests our Google ads bring and show our ads to people who have already been on the site.

Legal basis

We answer your request and prepare an offer: these are steps taken at your request before entering into a contract (Art. 6(1)(b) GDPR). Everything else rests on our legitimate interests (Art. 6(1)(f) GDPR): delivering the pages and protecting the site and the form against attacks and spam; knowing which campaign or page brought the request (utm tags in the page address); and keeping the request when no contract follows, so we can pick up the conversation if you come back. A test drive at your request is likewise a step towards a contract (Art. 6(1)(b) GDPR). The keyed fingerprint of your email rests on our legitimate interests (Art. 6(1)(f) GDPR): protecting the free trial from abuse. The launch application, its confirmation and preparing the website setup are likewise steps towards a contract at your request (Art. 6(1)(b) GDPR). We draw the AI logo only at your request, and this too is a step towards a contract (Art. 6(1)(b) GDPR). The AI logo log (the session tag and the daily address pseudonym) rests on our legitimate interests (Art. 6(1)(f) GDPR): keeping AI spending within limits and protecting the service from abuse. Paying for the launch on the site and invoicing are entering into and performing a contract (Art. 6(1)(b) GDPR); we keep the payment data and invoices because accounting law requires it (Art. 6(1)(c) GDPR), and checking the payment for fraud rests on our legitimate interest (Art. 6(1)(f) GDPR). The record of acceptance of the Express Terms is needed to conclude the contract (Art. 6(1)(b) GDPR); we keep the record because we have a legitimate interest in being able to prove that the contract was concluded and to defend our rights (Art. 6(1)(f) GDPR). An application without payment, its review, the decision and the e-mail about it are steps taken at your request before entering into a contract (Art. 6(1)(b) GDPR); the approval concludes the contract, and withholding the fee through Stripe or the invoices after it perform the contract (Art. 6(1)(b) GDPR). The daily limit on applications without payment (your email and the daily pseudonym of your IP address) and keeping a rejected application together with the reason for the rejection rest on our legitimate interests (Art. 6(1)(f) GDPR): protecting the review from spam and abuse, seeing the earlier decision when you send a corrected application, and explaining it if needed. The nightly encrypted copies of the panel database rest on our legitimate interest (Art. 6(1)(f) GDPR) in being able to restore the service and the data after a failure, which Art. 32 GDPR on the security of processing also requires. Google advertising cookies and everything the Google Ads tag reports to Google rest solely on your consent (Art. 6(1)(a) GDPR), which you give with the “Accept” button in the cookie banner. You can withdraw it at any time with the “Cookie settings” button at the bottom of every page; this does not affect the lawfulness of processing before the withdrawal.

How long we keep it

Your request (the e-mail in our mailbox) is kept for 24 months after you last contacted us, if no contract follows; then we delete it. If you ask, we delete it earlier. If a contract is signed, we keep it as long as the contract and the law (including accounting rules) require. The copy in the Resend sending log is deleted automatically after 30 days. The request logs that our host Vercel shows us are kept for no more than 1 day; service data that Vercel keeps itself are kept under its own rules. On the site, the IP address used to limit attempts is held only in server memory for up to 10 minutes and never written to disk; our panel counts the daily limit on applications without payment differently, by the daily pseudonym of the address (below). Cloudflare keeps Turnstile check data under its own rules (link under “Who receives the data”). The test drive login closes by itself when its term ends. The stand keeps the keyed fingerprint of your email for 90 days after issuing it, then erases it. The request number on the stand names no one by itself: it can be linked to you only through the request e-mail, which we keep under the rules for demo requests. We keep a launch application, together with its logo, under the same rules as a demo request. AI logo variants you did not take are not stored anywhere, and the one you take becomes the application’s logo. We keep the AI logo log entries (the session tag, the daily address pseudonym, the style, the colours and the variant number) for 30 days; then the server erases them, and only data about the call itself remain in the log, such as its time, model and cost, linked to no one. Google does not use these requests to improve its products and keeps them for a limited time solely to detect violations of the rules for using the service (link under “Who receives the data”). We keep the application card in our client management panel under the same rules; we keep the data of a payment made on the site and the invoices for as long as accounting law requires. Stripe keeps the payment, customer and invoice data under its own rules (link under “Who receives the data”). We keep the record of acceptance of the Express Terms, with the IP address, for as long as the contract runs and for 4 years after it ends, so that we can prove the contract if needed; if the payment is not completed, or an application without payment is rejected or not yet approved, no contract arises and we keep the record under the rules for applications. We keep the email of an application without payment, the decision on it and the reason for a rejection under the same rules. The server erases the daily pseudonym of the IP address used for the limit on applications without payment after 2 days. Every night we copy the database of our client management panel into separate encrypted storage: we keep the daily copies for 30 days and the copy of the first day of each month for 12 months. Data we have erased or de-identified in the panel (including the AI logo log entries and the daily address pseudonym) therefore remains in copies made earlier until those copies expire. We use the copies only to restore the database after a failure or to check that restoring works. Google keeps the data it receives through the Google Ads tag under its own rules (link under “Who receives the data”); how long the cookies last is set out under “Cookies”.

Who receives the data

Processors acting on our instructions: Vercel Inc. (website hosting and form handling) under its terms of service, as Vercel offers no separate data processing agreement on our plan; under a data processing agreement: Plus Five Five, Inc., operator of Resend (sending the e-mail with your request); Cloudflare, Inc. (receiving and forwarding e-mail to our addresses and the Turnstile bot check). The e-mail with your request is stored in our Gmail mailbox, which Google Ireland Limited (Ireland) provides under its own terms, without a separate data processing agreement; Google may transfer the data to Google LLC in the USA under adequacy decision (EU) 2023/1795 (Google LLC is on the EU-US Data Privacy Framework list). Vercel, Resend and Cloudflare are in the USA. Transfers there rely on the European Commission adequacy decision (EU) 2023/1795 (EU-US Data Privacy Framework; these companies are on its list) and, for Resend and Cloudflare, also on the EU standard contractual clauses (Decision (EU) 2021/914) in the processing agreements; we will send you a copy on request at privacy@complete-solution.eu. Separately, as independent controllers: Vercel for service usage data about its own platform (https://vercel.com/legal/privacy-policy), and Cloudflare for Turnstile technical signals it uses to improve bot detection (https://www.cloudflare.com/turnstile-privacy-policy/). Separately, our team receives a Telegram notice of a new request containing only its number, the city, the number of locations, what you are interested in, the page language and the market, with no name, venue name or contact details; Telegram (Telegram Messenger Inc., British Virgin Islands, and Telegram FZ-LLC, UAE) handles these messages as an independent controller under its own terms. We send the confirmation of a launch application to your email through the same Resend; the Telegram notice of such an application contains only its number, the country and city, the venue type, the plan, what the venue needs, the page language and the market, with no name, venue name, contact details or logo. We also enter a launch application as a card in our client management panel, Vitrina Control: the card holds your name, phone and email, the venue’s website settings from the application (including the venue’s contact details and company details, if you gave them) and a short summary of the application, while the logo stays only in the e-mail. The panel runs on the servers of Railway Corp. (USA), a processor under a data processing agreement; transfers to the USA rely on the EU-US Data Privacy Framework if Railway is on its list, and otherwise on the EU standard contractual clauses (Decision (EU) 2021/914). Encrypted nightly copies of the panel database are stored in the Cloudflare R2 storage of the same Cloudflare, Inc., on the same transfer terms; Cloudflare does not have the key to the copies. For a test drive, the request number, the page language and the keyed fingerprint of your email go to our demo stand, which runs on the servers of the same Railway Corp. on the same terms; we send you the login e-mail through the same Resend. If you click “Create an AI logo”, the panel passes the name, venue type, style and colours to the Gemini API service of Google Cloud EMEA Limited (70 Sir John Rogerson’s Quay, Dublin 2, Ireland), a processor under the terms of the Gemini API paid tier and Google’s data processing addendum: https://ai.google.dev/gemini-api/terms. Google may process this data in any country where Google or its subprocessors maintain facilities, including the USA; transfers there rely on the EU-US Data Privacy Framework (Google LLC is on its list) and, where it does not apply, on the EU standard contractual clauses in Google’s data processing addendum. If you choose to pay for the launch on the site, the panel opens a Stripe payment page for you and passes Stripe your email, the application number, the venue key, the plan and the amount; you enter your card details, company name, billing address and tax number directly on the Stripe page. Stripe keeps them in the customer record and prints them on invoices: we issue the document for the first payment and the invoices for the following months through Stripe, and an invoice with a fee on online orders also carries the venue’s online turnover by day. Stripe Payments Europe, Limited (Ireland) accepts the payment and checks it for fraud as an independent controller; how Stripe processes this data and transfers it to the USA is set out in its policy: https://stripe.com/privacy. A note of the acceptance of the Express Terms goes into the application e-mail, and the full record of acceptance is kept in the panel together with the payment record and the Stripe session number; Stripe does not receive them from us. We send you the text of the accepted Terms by email through the same Resend. After the payment, the panel sends you the launch e-mail through the same Resend. Apart from the application e-mail and the Telegram notice, as for any launch application, the site passes an application without payment (“On my own, free”) only to our Vitrina Control panel on the servers of the same Railway Corp.: the panel holds the record of acceptance of the Terms, the email and the daily pseudonym of the IP address for the limit on applications, the decision and the reason for a rejection, while a note of the acceptance goes into the application e-mail, as on the path with payment. Stripe does not receive such an application. We send you the contract after approval, the rejection e-mail with the reason and the launch e-mail through the same Resend. After approval we issue the invoices for the fee on online payments through the same Stripe or manually; for an invoice through Stripe, Stripe receives the venue name, your email for invoices, the venue key, the invoice amounts and the venue’s online turnover by day. If the venue accepts online payments in the “Stripe via Vitrina” mode (section 2 of the Terms), Stripe withholds the fee from each payment and it does not have to be paid separately: Stripe runs the venue’s Stripe account under the venue’s own contract with Stripe, our platform account at Stripe sees the ID of the venue’s connected account and the fee withheld from each payment, and our panel receives the online turnover, refunds and withheld fees by day from the venue’s server. If you consent to advertising cookies, the Google Ads tag data is received by Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) as an independent controller, to measure the results of our ads and to show them; Google may transfer it to Google LLC in the USA under the same adequacy decision (EU-US Data Privacy Framework; Google LLC is on its list). How Google uses this data: https://policies.google.com/technologies/partner-sites.

Your rights

You may ask for access to your data, its rectification or erasure, restriction of processing or portability. Write to us at privacy@complete-solution.eu. You also have the right to lodge a complaint with a supervisory authority: the Úrad na ochranu osobných údajov Slovenskej republiky (Galvaniho 7/⁠B, 821 04 Bratislava, dataprotection.gov.sk) or the authority of the EU country where you usually live, work or where you believe the infringement took place.

Your right to object

Where we process your 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 (Art. 21 GDPR). Write to privacy@complete-solution.eu and we will stop unless we can demonstrate compelling legitimate grounds that override your interests.

Cookies

Technical cookies that need no consent: NEXT_LOCALE appears only if you change the site language yourself, keeps that choice and is deleted when you close the browser; vitrina_consent remembers your answer in the cookie banner for 180 days. Google advertising cookies appear only after you click “Accept” in the banner; until then the site loads no Google script at all. These are _gcl_au and other cookies prefixed _gcl_ on our domain (up to 90 days) and Google cookies on Google’s own domains, such as doubleclick.net and google.com (under Google’s rules). You can change your answer at any time with the “Cookie settings” button at the bottom of every page. After “Reject”, we delete the _gcl_ cookies from our domain and send nothing more to Google; cookies on Google’s domains can be deleted in your browser settings.

The Vitrina app

This section is about the shared Vitrina app. To show the list of venues, the app contacts our server, which, like any web server, receives the IP address of the request: the app cannot work without it (Art. 6(1)(f) GDPR). Your choice of venue and the list of recently opened venues are kept only on your phone. The app asks for location only when you tap “Nearby” in the venue list or the locate button on the map where you choose a delivery address. For “Nearby”, the distance to venues is calculated on the phone and is sent nowhere. The locate button moves the map to where you are; the app sends the point on the map to the venue’s server to find the address, and the venue receives the chosen delivery point together with the address and the order. Once you open a venue, the app works with the server of that venue: sign-in, orders, addresses, the delivery point and contacts are processed by the venue as controller under its own privacy policy, available in the app after you choose the venue, and we act as its processor. One exception: if the venue offers the Treasure Chest game, we, Complete Solution, run it as the organiser under the game rules. Which chest you opened, which discount you got and how many times you used it, we process as the organiser of the game, not as the venue’s processor (Art. 6(1)(b) GDPR); the discount is applied to your order by the venue. Maps in the app (choosing the delivery address, the map on the venue’s contacts page and the courier map in an order) are shown by the Google Maps SDK on Android and by Apple Maps on iPhone: to load a map, the phone sends Google LLC (USA) or Apple its IP address and the part of the map you are viewing, and they process this data under their own terms; the transfer to Google LLC relies on the EU-US Data Privacy Framework (Google LLC is on its list). Each time it starts, the app asks the update server of Expo (650 Industries, Inc., USA) whether we have published a newer version of its code; the request carries the IP address, the app version and a random installation identifier, and nothing about your account or the venue. We process these requests as controller so that the app receives fixes (Art. 6(1)(f) GDPR); Expo is our processor, and the transfer to the USA relies on the EU-US Data Privacy Framework (650 Industries, Inc. is on its list) and on the standard contractual clauses in section 3.2 of the Expo Terms of Service. Apple and Google distribute the app under their own rules. Your rights and contacts are the same as in this policy.

Deleting your account in the Vitrina app

A guest account exists separately at each venue, so it is also deleted separately at each venue. Open the venue in the Vitrina app, go to “Profile”, then “Settings”, tap “Delete account” and confirm by entering the phone number of that account. If after signing in the app asks you to confirm your phone number, you can delete the account without doing so: tap “Delete account” below that step and enter the phone number of the account or, if the account has none, the word shown in the confirmation window. If you no longer have the app or cannot sign in, write to the venue (its contacts are in its privacy policy) or to us at privacy@complete-solution.eu, and we will pass the request on to the venue. The venue anonymises profile data, addresses, saved cards and the contact details of completed orders immediately. Correspondence, bookings, contacts in reviews and the data in payment records are deleted or anonymised later, after the periods in the venue’s policy. The total, contents and payment document of orders stay in the venue’s books for as long as the tax law of its country requires, and an irreversible fingerprint of the phone number is kept for 12 months so that one-time offers are not received twice. Our server holds no guest accounts, and your choice of venue and the list of recently opened venues are kept only on your phone and disappear with the app.

Notices of illegal content

If you report content through the “Report illegal content” form or by email, we process your name or the name of your organisation, your email address, your explanation, the addresses (URLs) of the content and the other details you give, the mark that the content concerns child sexual abuse, your confirmation of good faith, the page language, the notice number and the time of receipt. We need them to handle the notice under Article 16 of Regulation (EU) 2022/2065 (the Digital Services Act): to confirm receipt, to take a decision and inform you of it, and, where we restrict the content, to give the one who placed it a statement of reasons under Article 17. The legal basis is our legal obligation (Art. 6(1)(c) GDPR). If you tick the mark about child sexual abuse, you may leave out your name and email. The notice is stored in our client management panel, Vitrina Control, at Railway Corp. (see “Who receives the data”); if the panel is unavailable, it reaches our team by email through Resend, and a notice sent by email is also kept in our mailbox. We may forward the notice to the venue whose content it concerns without your name and email; where strictly necessary, the statement of reasons may name you (Article 17(3)(b) of the Regulation). We keep the notice for 12 months after the final decision on it; then we delete it. The bot check and the limit on attempts work as for the other forms on this site.

This policy is available in several languages; all versions have the same content. If you notice a discrepancy, write to us at privacy@complete-solution.eu and we will correct the translation.