Skip to content

Privacy Policy

Last Updated: November 10, 2026

1. Responsible Party (Data Controller)

The party responsible for the processing of personal data on this platform — the “controller” within the meaning of the General Data Protection Regulation (GDPR) and other national data protection laws — is:

Ypsilon.dev UG (haftungsbeschränkt)
Abensstraße 8
93059 Regensburg

Represented by: Omar Ijbara
Phone: +49 941 94223991
Email: info@ypsilon.dev

The controller is the natural or legal person who, alone or jointly with others, determines the purposes and means of processing personal data (such as names, email addresses, and similar).

2. Information We Collect

We collect information you provide directly, such as when you create an account, submit a review, or contact us. This may include:

  • Personal identifiers (name, email address)
  • Business information (shop name, address)
  • Usage data and analytics
  • Device and browser information

3. How We Use Your Information

We use the information we collect to:

  • Provide, operate, and maintain the Platform.
  • Process your transactions and send related information.
  • Send promotional communications (with your consent).
  • Improve our services and develop new features.
  • Detect and prevent fraudulent activity.

We only process your personal data where we have a valid legal basis under Article 6(1) GDPR:

  • Consent (Art. 6(1)(a) GDPR) — for example for marketing emails, SMS or WhatsApp notifications, and non-essential cookies. You can withdraw your consent at any time.
  • Performance of a contract (Art. 6(1)(b) GDPR) — to create and operate your account and provide the services you request.
  • Legal obligation (Art. 6(1)(c) GDPR) — for example to meet statutory retention, tax, and accounting duties.
  • Legitimate interests (Art. 6(1)(f) GDPR) — for example to keep our platform secure, prevent fraud, and monitor service stability, provided your rights and interests do not override ours.

5. Sharing Your Information

We do not sell your personal information. We may share your information with:

  • Service Providers: Third parties that help us operate the Platform (e.g., payment processors, hosting).
  • Legal Requirements: When required by law or to protect our rights.
  • Business Transfers: In connection with a merger, sale, or acquisition.

6. Hosting

Our production servers are hosted by netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany, in a data centre in Vienna, Austria (EU). Backups are stored in the EU with Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany (Storage Box); Hetzner does not host the platform itself. Both providers process personal data only on our behalf and solely to provide the hosting and backup infrastructure. The legal basis is our legitimate interest in a secure and reliable platform (Art. 6(1)(f) GDPR).

Service providers (sub-processors)

We engage the following service providers to operate RevYoMe. They process personal data only on our instructions and for the purposes stated. The privacy policies of the shops on our platform list the same providers, generated from the same source.

  • netcup GmbH (Daimlerstraße 25, 76185 Karlsruhe, Germany)
    Purpose: Hosting of the production servers: application, databases, file storage and the services we operate ourselves.
    Data: All data processed on the platform (account, contact, booking, order, loyalty, payment status and message data).
    Location: Vienna, Austria (EU)
    Third-country safeguard: None — processing takes place within the EU.
  • Hetzner Online GmbH (Industriestr. 25, 91710 Gunzenhausen, Germany)
    Purpose: Off-site backup storage (Storage Box) and storage of offline map packages. Hetzner does not host the platform itself.
    Data: Backup copies of the databases and files listed for netcup.
    Location: EU
    Third-country safeguard: None — processing takes place within the EU.
  • Zoho Corporation B.V. (Zoho Mail) (Utrecht, Netherlands)
    Purpose: Sending the platform’s e-mails: account and sign-in e-mails, order and booking confirmations and notifications. A shop that connects its own mail server sends its customers’ e-mails through that server; ours is used only if that server fails.
    Data: Name, e-mail address and the content of the e-mail.
    Location: EU
    Third-country safeguard: None — processing takes place within the EU.
  • Stripe Payments Europe, Limited / Stripe, Inc. (Dublin, Ireland / San Francisco, USA)
    Purpose: Online card and wallet payments for shops that enable Stripe, and billing of platform subscriptions.
    Data: Name, e-mail address, payment details, amount and transaction data.
    Location: Ireland (EU) and USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • ShamCash (Syria)
    Purpose: Payment of platform fees (subscription, message credits, ads budget) by shop owners who pay with ShamCash.
    Data: Payment amount, payment reference and the payer’s ShamCash account details.
    Location: Syria
    Third-country safeguard: No adequacy decision exists for Syria; the transfer takes place only to carry out a payment the payer initiates (Art. 49(1)(b) GDPR).
  • Twilio Inc. (San Francisco, USA)
    Purpose: Sending SMS and WhatsApp messages: confirmations, reminders and sign-in codes.
    Data: Mobile phone number, message content and delivery status.
    Location: USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Meta Platforms Ireland Limited (WhatsApp Business Platform) (Dublin, Ireland)
    Purpose: Delivering WhatsApp messages (directly through the WhatsApp Business Cloud API or through Twilio) and the WhatsApp assistant.
    Data: Mobile phone number, WhatsApp profile name, message content and delivery status.
    Location: Ireland (EU) and USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Google Ireland Limited / Google LLC (Firebase Cloud Messaging) (Dublin, Ireland / Mountain View, USA)
    Purpose: Push notifications to the customer app and the merchant app (for example order and booking updates).
    Data: Device push token, app instance identifier and notification content.
    Location: Ireland (EU) and USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Push service of the subscriber’s browser (Google, Mozilla, Apple or Microsoft)
    Purpose: Delivering web push notifications, only to browsers that subscribed to them: order alerts for shop staff and order-status updates from the order-tracking page.
    Data: The browser’s push subscription address and the notification, whose content is encrypted so the push service cannot read it.
    Location: Depends on the browser vendor; mainly USA
    Third-country safeguard: The push service is part of the subscriber’s browser and is determined by the browser, not by us. Where it is located in the USA, the EU–US Data Privacy Framework (adequacy decision of the European Commission) applies where the vendor is certified under it.
  • OpenStreetMap Foundation (Cambridge, United Kingdom)
    Purpose: Fallback only: map images (raster tiles) from tile.openstreetmap.org, loaded by your browser directly when it cannot draw our own map (no WebGL), and on the shop owner’s Ads map.
    Data: IP address, browser information and the map area being viewed.
    Location: United Kingdom
    Third-country safeguard: None needed — the European Commission has adopted an adequacy decision for the United Kingdom (Art. 45 GDPR).
  • Google Ireland Limited / Google LLC (reCAPTCHA) (Dublin, Ireland / Mountain View, USA)
    Purpose: Protection of the merchant sign-in, registration and password-reset forms against automated abuse.
    Data: IP address, browser information and interaction data on those forms.
    Location: Ireland (EU) and USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Cloudflare, Inc. (Turnstile) (101 Townsend St, San Francisco, CA 94107, USA)
    Purpose: Security check (shown only when needed) before a verification code is sent for signing in or for a booking, against SMS toll fraud.
    Data: IP address and browser and device characteristics, only while the check is shown.
    Location: USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Anthropic, PBC (San Francisco, USA)
    Purpose: AI features, only when they are switched on: importing a menu, catalogue or price list from files the merchant uploads (AI import); the assistant that answers a shop owner’s or manager’s questions about their own shop and prepares changes to it (owner assistant, also called the workspace agent — it only proposes changes, and a change is applied only after the owner or manager accepts it); the guided chat that helps a new owner with setting up their shop (AI onboarding — nothing is saved until the owner confirms it); translating the shop’s own texts (menu, item and settings texts) into the languages the shop offers, when the owner asks for it (AI translation); comparing candidate product photos to the product, when the owner asks the assistant for a photo of an item (product-image comparison — the owner chooses each photo); and, where a shop switches it on, the assistant that answers its customers’ questions in the customer app (customer assistant). Anthropic processes this content on our behalf and, under its commercial terms, does not use it to train its AI models. We use zero-data-retention settings wherever Anthropic offers them to us.
    Data: AI import: the files and text the merchant uploads (menus, price lists, photos, documents); contact details are never extracted from them. Owner assistant (workspace agent): the shop’s catalogue (items, categories, services, prices, barcodes, allergens and dietary tags), settings, opening hours and design, a summary with totals that identify no one, and the conversation itself, with phone numbers, e-mail addresses and bank details removed before it is sent — never customer, user or staff records, orders, bookings, messages, payments or loyalty balances. Files the owner attaches in the assistant’s chat (photos and PDFs, such as a menu or price list) are sent as they are, so the items can be read from them; contact details are removed from what is read out of them. What the assistant remembers about the shop: short notes the owner confirmed with Yes about how the shop names, prices, groups, pictures or writes its items (for example “prices end in .90”) — never contact details, links or details about people. AI onboarding: what the new owner types and uploads while setting up their shop (what it sells or offers, opening hours, style, menus); the address, phone number and e-mail are typed into a form and never sent, and phone numbers or e-mail addresses typed into the chat are removed before it is sent. AI translation: the shop’s own texts only (menu, item and settings texts) — never customer, order or message data. Customer assistant, where a shop switches it on: the customer’s question and the shop’s public catalogue, opening hours and policies — never the customer’s account, orders or appointments. A photo or short video the customer attaches to find a similar product is sent as still images (for a video, at most 4 stills taken on our server, without its sound) so the assistant can compare the product with the catalogue; it does not analyse or identify people or faces, and the photo or video is deleted as soon as the answer is given. Product-image comparison: the item’s name and the candidate photos found in free image libraries — no shop, owner or customer data. No payment card data.
    Location: USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
    Retention: Prompts, AI answers and uploaded files: 30 days. Owner-assistant conversations are stored encrypted and are also deleted after 30 days. How the owner or manager answered the assistant’s proposals (which proposal, accepted or declined; no typed text): 2 years. Files attached in the assistant’s chat: deleted after 2 hours without use, or at once when the conversation is deleted. What the assistant remembers about the shop: until the owner deletes it (one note or all at once) or the shop is deleted; a suggestion the owner did not confirm is deleted after 24 hours. Usage and billing records of each AI run, and the change history (revisions) of shop settings: 2 years. Photos and videos a customer attaches in the customer assistant: deleted as soon as the answer is given. These periods apply to the copies we keep.
  • OpenRouter, Inc. (USA)
    Purpose: AI features for merchants: importing a menu or catalogue from photos, documents or web pages, translating shop content and SEO research. Requests are forwarded to the AI model provider selected for the feature. OpenRouter is never used for the owner assistant or the customer assistant.
    Data: Content the merchant submits for the feature (menu photos, documents, catalogue and shop texts). No customer data is sent for these features.
    Location: USA
    Third-country safeguard: EU Standard Contractual Clauses (Art. 46(2)(c) GDPR); in addition, the EU–US Data Privacy Framework where the recipient is certified under it.
  • Open Food Facts (France)
    Purpose: A non-profit association: its open product databases (Open Food Facts, Open Beauty Facts, Open Products Facts) are searched for photos of a packaged product, by barcode or name, when a shop owner asks the AI assistant for a photo of an item. The owner chooses each photo; none is added automatically. The same databases are also asked for the product facts of a packaged product (brand, size, ingredients, allergens, labels), by its barcode only, when the owner asks the assistant to write a description; the assistant uses these facts, writes the text itself, and the owner reviews it before anything changes.
    Data: Only the product’s name, its barcode if it has one, and a language code, sent from our server (for product facts, only the barcode and a language code). Never customer, user or staff data, and never the shop’s name or address.
    Location: France (EU)
    Third-country safeguard: None — processing takes place within the EU.
  • Wikimedia Foundation, Inc. (Wikimedia Commons) (San Francisco, USA)
    Purpose: Wikimedia Commons, a free media library, is searched for photos of generic products, dishes and ingredients when a shop owner asks the AI assistant for a photo of an item. The owner chooses each photo; none is added automatically.
    Data: Only the product’s name and a language code, sent from our server. Never customer, user or staff data, and never the shop’s name or address.
    Location: USA
    Third-country safeguard: None needed — no personal data is sent: only a product’s name (and, where stated, its barcode) and a language code, from our server.
  • Openverse (an open-source project of WordPress.org)
    Purpose: Openverse, a search engine for openly licensed images, is searched for product photos when a shop owner asks the AI assistant for a photo of an item. Only images under licences that allow their use in a shop are offered. The owner chooses each photo; none is added automatically.
    Data: Only the product’s name, sent from our server. Never customer, user or staff data, and never the shop’s name or address.
    Location: USA
    Third-country safeguard: None needed — no personal data is sent: only a product’s name (and, where stated, its barcode) and a language code, from our server.

Operated by us on our own servers (no third party involved):

  • GlitchTip — error tracking and crash reports from the website, the merchant apps (Android, Windows, /staff-2) and the customer app, at sentry.ypsilon.dev (stack trace, app version, device model and OS, a pseudonymous identifier — no name, e-mail address or phone number)
  • Map tiles, address search and route calculation — map tiles (tiles.revyome.com), address search while an address is typed (geocoder.revyome.com) and delivery route calculation (OSRM)

International transfers

Some of the providers listed above are located in, or may access data from, countries outside the EU/EEA, in particular the USA. Where personal data is transferred to such a country, the transfer is based on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) and, where the recipient is certified under it, on the EU–US Data Privacy Framework (adequacy decision of the European Commission). Where a different safeguard applies, it is named next to the provider above.

7. Data Security

We implement appropriate technical and organizational measures to protect your personal data against unauthorized or unlawful processing and against accidental loss, destruction, or damage. However, no method of transmission over the Internet is 100% secure.

8. Error Tracking & Service Monitoring

We use automated error tracking to monitor the stability and performance of our platform. When a technical error occurs in your browser, diagnostic information is automatically sent to our self-hosted error tracking system, hosted within the European Union. This data is limited to:

  • The error message and the page URL where the error occurred
  • Browser type, version, and screen size
  • A pseudonymised user identifier (no name or email is transmitted)
  • No cookies are set by this system
  • Legal basis: Legitimate interest in service stability (Art. 6(1)(f) GDPR). Error data is deleted after 90 days.

Our apps report crashes and errors in the same way: the merchant apps (Android, Windows and the /staff-2 web console) and the customer app and customer web app send crash and diagnostic reports containing the stack trace, the app version, the device model and the operating system. Default personal-data collection is switched off and the reports are scrubbed before they leave the device: they carry no name, e-mail address or phone number, only a pseudonymous identifier. They go to our self-hosted GlitchTip (sentry.ypsilon.dev) on our own servers in a data centre in Vienna, Austria (EU) — no third party receives them.

Crash reports from the merchant apps

The RevYoMe merchant apps for shop staff (Android, Windows and the /staff-2 web console) send a crash report when the app crashes or hits an unexpected error. The only purpose is finding and fixing those crashes.

  • What a report contains: the crash log (error message and stack trace) and diagnostics: app version and build, platform, device model, operating system and the screens opened just before the crash.
  • What it never contains: customer names, phone numbers, e-mail addresses or addresses, and no order contents. Default personal-data collection is switched off, and every report is scrubbed on the device before it is sent; the only identifier is a random installation ID (in the web console, the pseudonymous account ID).
  • Where it goes: only to our self-hosted GlitchTip (sentry.ypsilon.dev) on our own servers in a data centre in Vienna, Austria (EU); no third party receives it.
  • Your choice: on Android and Windows, the switch “Send crash reports” under “This device” (on by default) stops crash reports from that device at once; in the web app (/staff-2), the same switch in its Settings stops them from that browser.
  • Retention: crash reports are deleted after 90 days. Legal basis: legitimate interest in a stable app (Art. 6(1)(f) GDPR).

Server log files

Whenever you open a page or use one of our web apps, the web server of our platform automatically records the request in a server log file. Each entry contains:

  • The IP address the request came from, including the address passed on in the X-Forwarded-For header
  • The date and time of the request and the full request line (method, requested address including any query parameters, and protocol)
  • The response status code, the size of the response and how long the server took to answer
  • The referring page (referrer) and the user-agent string of your browser or app (for example browser, version and operating system)

We use these log files only to keep the platform secure (to detect and trace attacks and misuse) and to diagnose errors and outages. We do not use them to build user profiles, we do not combine them with other data, and we do not pass them on to third parties. They are stored on our own servers in the data centre in Vienna, Austria (EU).

Legal basis: our legitimate interest in a secure and working platform (Art. 6(1)(f) GDPR). Each day's log file is deleted automatically after 14 days.

Protection against abuse (Cloudflare Turnstile)

When you request a verification code for signing in or for a booking in a shop on RevYoMe, a security check may be shown first, to protect against the abusive sending of verification codes by SMS (SMS toll fraud). For this check we use the Cloudflare Turnstile service of Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. Turnstile is loaded only when this check is shown. When it is shown, technical data such as your IP address and characteristics of your browser and device are transmitted to Cloudflare so that it can tell whether the request comes from a person.

The legal basis is our legitimate interest in protecting the platform, its shops and their customers against fraud and automated abuse (Art. 6(1)(f) GDPR). Access to information on your device requires no consent under § 25(2) No. 2 TDDDG (the German Telecommunications Digital Services Data Protection Act), because it is strictly necessary to send the code you requested. The transfer to the USA is based on the European Commission’s adequacy decision for the EU-US Data Privacy Framework (Art. 45 GDPR) where Cloudflare participates in it, and otherwise on the EU standard contractual clauses (Art. 46(2)(c) GDPR).

Website analytics (Matomo, without cookies)

To understand which pages of the RevYoMe website (revyome.com) are useful, we measure their use with Matomo, an open-source analytics tool that we run ourselves on our own server in Vienna, Austria (EU). The data never leaves our server and is not shared with Matomo's makers or any other third party.

  • No cookies are set and nothing is stored on your device for analytics. We do not fingerprint your device: page views from one visit are grouped only by a short-lived, anonymised identifier that changes every day and cannot be linked across days.
  • Your IP address is anonymised (shortened by two bytes) before it is stored, so a visit cannot be traced back to you.
  • We record the page you view, the page you came from, the time of the visit and the browser, operating system and device type your browser reports.
  • If your browser sends a "Do Not Track" or "Global Privacy Control" signal, nothing is recorded.
  • Analytics run only on the public pages of the RevYoMe website: never on a shop's pages or in a shop's app, and not while you are signed in.

Legal basis: our legitimate interest in understanding how our website is used so we can improve it (Art. 6(1)(f) GDPR). Raw visit records are deleted automatically after 180 days; only anonymous totals are kept after that.

You can object at any time. Turn analytics off for this browser here; your choice is kept in your browser's local storage, and it is the only thing stored, because you asked for it.

Analytics are on for this browser.

9. Data Retention

We keep your personal data only for as long as necessary for the purposes described in this policy, or for as long as required by law. Account data is retained while your account is active; when an account is closed or becomes inactive, the associated personal data is anonymised or deleted after the applicable grace period, unless a longer statutory retention obligation (for example under tax or commercial law) applies. Error-tracking data is deleted after 90 days. Server log files are deleted after 14 days.

10. Your Rights

Depending on your location, you may have rights regarding your personal data, including:

  • The right to access your data.
  • The right to correct inaccurate data.
  • The right to delete your data ("right to be forgotten").
  • The right to data portability.
  • The right to object to processing.
  • The right to withdraw consent at any time, without affecting the lawfulness of processing carried out before the withdrawal.
  • The right to lodge a complaint with a data protection supervisory authority.

For how to request erasure of your account and its data, see our Account & Data Deletion page — with the steps, what is deleted, and the retention periods.

To exercise these rights, please contact us at privacy@revyome.com.

11. Right to Lodge a Complaint

Without prejudice to any other remedy, you have the right to lodge a complaint with a data protection supervisory authority if you believe that the processing of your personal data infringes the GDPR — in particular in the EU member state of your residence, place of work, or the place of the alleged infringement. The authority responsible for us is:

Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18
91522 Ansbach
https://www.lda.bayern.de

12. Cookies

We use cookies and similar tracking technologies to track activity on our Platform and hold certain information. You can instruct your browser to refuse all cookies or to indicate when a cookie is being sent.

Our website analytics set no cookies (see "Website analytics" above).

Our Platform may contain links to third-party websites. We are not responsible for the privacy practices or content of these external sites.

14. Children's Privacy

Our Platform is not intended for children under the age of 16. We do not knowingly collect personal information from children.

15. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date.

16. Contact for Privacy Inquiries

If you have any questions about this Privacy Policy, please contact us at privacy@revyome.com.

17. Third-Party Services & Communications

To provide our services, including SMS and WhatsApp notifications, we utilize third-party providers such as Twilio Inc. By opting into these communications, you acknowledge that your phone number and related message data will be processed by Twilio and Meta (WhatsApp) in accordance with their respective privacy policies.

18. Connected Facebook & Instagram Accounts

If you use RevYoMe as a business and choose to connect your Facebook Page or Instagram account, we access those accounts only through Meta's official APIs and only to provide the features you turn on.

Action button (pages_manage_cta): When you use our action-button feature, we read and update your Facebook Page's action button — its type and destination link — so it points to your RevYoMe booking or ordering page. We do this only for Pages you administer and have connected, and only when you choose to set the button. This permission is used solely to manage your Page's own action-button configuration; we do not access, collect, or store your or your customers' personal data through it.

Comment auto-reply (optional): If you enable comment auto-reply, we read comments on your connected posts and send public replies and direct messages on your behalf, using the relevant Facebook Page and Instagram permissions. We process the content of those comments and messages only to generate and send the replies you have configured, and not for any other purpose.

To operate these features we store your Page access token in encrypted form. You can disconnect your Facebook Page or Instagram account inside RevYoMe at any time, which removes our access and deletes the stored token; you can also remove RevYoMe under your Facebook Settings → Business Integrations (or Apps and Websites). Your use of connected Meta accounts is additionally governed by Meta's Privacy Policy.

19. Connected AI apps (MCP)

If you run a shop on RevYoMe, you can connect an AI app of your choice to your own shop — for example ChatGPT, Claude or another app that supports the Model Context Protocol (MCP). Only the shop’s owner can connect one, either by approving it on our consent page (which names the app, the shop and what it may do) or with a connection token the owner creates. Each connection works for one shop only. We send nothing to an AI app until you connect it.

Purpose: so that the AI app can read your shop’s catalogue and settings and prepare changes for you. A connected AI app can only propose: every change waits in RevYoMe as a proposal until you accept it there, and nothing in your shop changes through the connection itself.

Data: your shop’s catalogue (items, categories, prices, services), opening hours, design and non-personal settings, and the proposals the app has made. Never customer, user or staff data, orders, bookings, messages, balances or payment data. Phone numbers, e-mail addresses and bank details are removed from texts before they are sent, and contact texts such as receipt headers and footers are never sent.

Recipient: the AI app you connect and its provider (for example OpenAI for ChatGPT or Anthropic for Claude). You choose that app and use it under its own terms and privacy policy; it receives the data at your request and is not our processor for it, and we do not control how it uses or keeps it.

What we keep: each connection (the app’s name, its permissions, when it was connected and last used) for as long as it exists; the proposals, like every proposed change in RevYoMe; and one log entry per request (which function, when, the result size and outcome — never the content), kept 90 days. You can disconnect an app, or pause every AI app of your shop, at any time in RevYoMe; its access ends at once. Changing your password, your role or the shop’s owner also ends it. Legal basis: the performance of our contract with you (Art. 6(1)(b) GDPR).

20. Product photos from free image libraries

If you run a shop on RevYoMe, the AI assistant can look for photos of your products in free image libraries and show you a few to choose from. You choose each photo yourself; no photo is added to your shop automatically. The search runs on our server, not on your device or your customers’ devices.

Purpose: finding product photos that you, the shop owner, choose for your catalogue.

Data: only the product’s name, its barcode if it has one, its category and a language code. Never customer, user or staff data, never your shop’s name or address, and nothing that identifies you or anyone else.

Recipients: the image libraries we search, each on its own: Open Food Facts (with Open Beauty Facts and Open Products Facts; a non-profit association in France), for packaged products found by barcode or name; Wikimedia Commons (Wikimedia Foundation, USA); and Openverse (an open-source project of WordPress.org). A general web image search is switched off; it would only ever be used for a photo after you confirm that you have the right to use it, and we will name its provider here before we switch it on.

What we keep: the photo you choose, with its licence, its author and its source URL, for as long as the photo is in your catalogue. We only offer photos under licences that allow their use in a shop (CC0, CC BY or CC BY-SA) and credit the author where the licence requires it. Photos you do not choose are deleted within 24 hours.

21. Anonymous catalogue patterns for the AI assistant (opt-in)

If you run a shop on RevYoMe, you can allow your shop’s catalogue structure to count towards anonymous patterns that help us improve the AI assistant’s built-in guidance for every shop of your kind. It is off unless the shop’s owner switches it on in the shop’s privacy settings, and only the owner can switch it.

Purpose: to learn, across many shops, how good catalogues are structured — for example which category usually comes first in a café, or how long a beard trim usually takes — and to write that into the guides the assistant follows. No AI reads your shop for this: our own server code counts the patterns, and a person on our team reviews the result before any of it is used.

Data: only the structure of your catalogue: how many categories and items there are, which kind of category comes first (sorted into fixed groups such as “hot drinks”), how prices are set up (fixed, from, on request), whether items have pictures, units, allergens or dietary tags, in how many languages names are written, and service durations in ranges. Never the names or descriptions you wrote, never prices, pictures or any other text, and never customer, user or staff data, orders, bookings or messages. A pattern is kept only when at least 20 shops show it and no single shop accounts for more than 10 % of it; the result never names or identifies a shop.

Recipient: nobody outside RevYoMe. The anonymous patterns stay with us, and the AI assistant only ever sees the reviewed guide texts, never the counts and never your shop’s data.

What we keep: the anonymous pattern report, until the next one replaces it; per shop, only whether its owner switched this on, and when. You can switch it off at any time; from the next run on, your shop no longer counts. Legal basis: your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.