Privacy policy
This privacy policy explains how Zenarion (Riya Thai Massage by Kusnirik, the "data controller") handles personal data of website visitors and registered users. It is based on the revised Swiss Federal Act on Data Protection (revFADP, in force since 1 September 2023) and — where applicable — on the EU General Data Protection Regulation (GDPR).
1. Data controller
Riya Thai Massage by Kusnirik
Schaffhauserstrasse 453, 8052 Zürich, Switzerland
Contact: [email protected]
2. What data we process
- Technical access data: IP address, user agent, requested URL, timestamp — solely for operation and abuse detection. For rate limits (protection against spam and abuse) we store an IP address, email address or phone number only as a pseudonymous hash (HMAC-SHA-256 with a secret key) together with a counter. These entries are deleted 48 hours after the last attempt (see §10).
- Audience measurement: aggregate page-view counts via Plausible Analytics (hosted in the EU). Plausible uses no cookies. On each page view your browser sends your IP address and user agent to Plausible. Plausible uses them only briefly to derive an approximate location and the browser and to count visits via a daily hash; the random value (salt) used for this is rotated and deleted every 24 hours. Plausible does not store IP addresses or user agents.
- Salon directory data: business name, address, phone, website, opening hours, photos, Google reviews — sourced from the Google Places API or entered manually by us or by the salon owner.
- Booking requests: first and last name (plaintext), email and phone (encrypted — see §4), requested date and time, duration, massage type, optional note. See §4.
- Native reviews:star rating, review text, optional title and sub-ratings (atmosphere, pressure, cleanliness, value for money), language, date and the link to your account. Verification works either by SMS code (we then store the verified phone number on your account) or through the review link of an actual booking (we then store the link to the booking and the therapist recorded on it) — see §7. Your name is shown publicly only as “First L.”, or as “Guest” if no name is on file (revFADP data minimisation).
- Account data (Auth.js): email, language preference, optional display name and profile picture for Google sign-in. For OAuth sign-in we store the tokens Google issues (access token, refresh token) for session management.
- Salon claim submissions (SalonClaim): listing ID, submitted message, decision and (where applicable) rejection reason.
- Messages to salons (email relay):if you contact a salon through its contact form or its Zenarion email address (…@mail.zenarion.ch), we store the sender name, subject and message text in the salon's Zenarion inbox. Your email address is stored encrypted (see §4); the message is forwarded to the salon's own email address. Replies travel through masked reply addresses, so both sides stay reachable without exposing email addresses. To route replies we additionally store the technical Message-ID of each email we send, linked to the respective conversation or booking; beyond this ID, no content is stored for that purpose.
- Billing data (paid plans): to invoice paid plans we process the business or owner name, billing address, plan, invoice number, amount and payment status. The legal basis is performance of the contract; retention follows Swiss commercial and tax record-keeping duties (10 years). Before a PRO period ends (including a free one) we remind the owner by e-mail and, if a mobile number is on file, by SMS (sent via Twilio).
- Gift card purchases:when a gift card is ordered via a salon page we process the buyer's name, email address (stored encrypted — see §4), amount, recipient name, personal message and the code's redemption balance — to issue, deliver and validate the respective salon's gift cards. Payment goes directly to the salon: by card (card, Apple Pay, Google Pay) on SumUp's payment page through the salon's SumUp account (SumUp processes the payment data on the salon's behalf; Zenarion sends the amount, order reference and salon name and receives back only the payment status and transaction identifier), via the salon's TWINT payment link (processed by TWINT AG on the salon's behalf) or by bank transfer. Zenarion receives no card or account data of the buyer; card payments are confirmed automatically, TWINT and bank transfers are confirmed by the salon in its dashboard. Salons offering card payment store the API key of their SumUp account for this purpose; it is kept encrypted (§4) and can be removed in the dashboard at any time.
3. Purpose & legal basis
Under the revFADP, a private controller needs no legal basis for processing; it must, however, follow the processing principles (art. 6 and 8 revFADP), and we do. In case a processing activity could breach personality rights, we name the ground for justification under art. 31 revFADP below; "legitimate interest" means an overriding private interest (art. 31 par. 1 revFADP). Where the GDPR applies, the basis named is the one under art. 6 par. 1 GDPR; for legitimate interest, lit. f.
- Operating the directory: legitimate interest (art. 31 par. 1 revFADP / art. 6 par. 1 lit. f GDPR).
- Showing public business data about salons: legitimate interest; data already publicly available. Where the salons (or, for Google reviews, their authors) made the data generally accessible themselves, this as a rule involves no breach of personality rights (art. 30 par. 3 revFADP); beyond that we rely on art. 31 par. 1 revFADP / art. 6 par. 1 lit. f GDPR. A salon can object to being shown at any time (contact: see §1).
- AI-assisted salon and page texts, research of public salon information: legitimate interest in a complete and up-to-date directory (see §6).
- Facilitating booking requests: contract performance or pre-contractual steps (art. 31 par. 1 and par. 2 lit. a revFADP / art. 6 par. 1 lit. b GDPR).
- Audience measurement: legitimate interest in aggregate usage data to improve the service.
- Review verification: legitimate interest in authentic reviews and abuse prevention.
- Salon offers to existing guests:salons may occasionally send offers or news via Zenarion to their own past guests (Art. 3 para. 1 lit. o Swiss UCA — advertising one's own similar services to existing customers). Every such email contains a working unsubscribe link; an unsubscribe is honoured permanently. Unsubscribes are enforced via a suppression list that stores a hash of your email address plus the optional reason or feedback you provide; every such email also supports one-click unsubscribe per RFC 8058. As proof of compliance we keep a per-recipient send log. Booking confirmations and appointment reminders are unaffected.
4. Booking requests
When you submit a booking request via a salon's booking form, we collect and store the following data in our database (hosted by Railway, EU-West (Amsterdam, Netherlands)):
- Plaintext: first and last name, requested date and time, massage type, duration and your optional note to the salon.
- Encrypted: your email address and phone number. Both fields are encrypted at rest with AES-256-GCM (256-bit symmetric encryption) and decrypted only when we deliver an email to you or the salon, or when you access your inbox via magic link.
- Pseudonymous hashes: we compute an HMAC-SHA-256 hash of your email and phone with a secret pepper so we can detect duplicates and respond to requests without decrypting the originals.
Phone masking: until a salon explicitly confirms your request, the salon sees your phone number only in masked form (e.g. +41 *********67). The full number is revealed in the salon's inbox only after confirmation.
Salons without an account:salons without a Zenarion account can also receive requests. We send your request to the salon's publicly listed contact details: by email, if the salon has an email address, with your first and last name, the requested time, massage type, duration, an estimated price where available, your optional note and your phone number in masked form; by SMS (via Twilio), if the salon has a mobile number, with a notice of a new request, the time and a link, but without your details. The salon does not receive your email address; replies run through a masked Zenarion address. If we can send the salon neither an email nor an SMS (for example because it only has a landline), we pass the request on to the salon ourselves by phone or WhatsApp; in individual cases we also do this in addition. We then give only your first name, the time and the requested treatment, never your last name, email address or phone number. For WhatsApp, WhatsApp Ireland Ltd. (Meta) receives these details (see §8 and §9).
Cancellation:you may cancel your request at any time via the magic link in the confirmation email in your inbox. Confirmed bookings can be cancelled up to 24 hours before the appointment. If the salon has to call off a confirmed booking and tells us, we record the cancellation and inform you by email. For requests to salons without a Zenarion account we also send you the salon's answer (confirmation, decline or cancellation) by SMS to the number you provided (sent via Twilio).
Reminder: for confirmed bookings we send you a single reminder email (via Resend) before the appointment, by default 24 hours in advance (the salon can adjust the lead time). The salon receives its own copy only if it has enabled that in its settings.
SMS notifications: if the salon has enabled SMS notifications, we send the booking confirmation and the reminder to the phone number you provided by SMS, in addition to or instead of the email. Delivery runs via Twilio (Twilio Ireland Ltd.); your phone number is transmitted to Twilio for this purpose. In our systems, SMS sends are logged only with a hash of the recipient number, never in plain text.
Bookings via AI assistants: guests may also submit booking requests through third-party AI assistants connected to our public booking interface. The assistant transmits your name, email address, phone number, requested slot and optional note on your behalf. The same encryption and phone masking described above apply. The provider of the AI assistant acts on your instruction and is not a sub-processor of Zenarion. Such bookings are rate-limited and marked internally as assistant bookings.
Staff-planning hint (form of address): from the first name of the person booking we derive a probable form of address — based on the public WGND name dictionary — shown to the salon solely for staff planning. This hint is computed on the fly each time it is displayed, never stored, never shown publicly and never shared with third parties. No inference is made beyond the first name.
Cancellations and no-shows: in its customer overview, booking notifications and customer export, the salon sees how many earlier bookings at that salon the person cancelled themselves (and how many of those less than 24 hours before the start) and how often they did not show up. Only bookings at that one salon are counted. The figures are computed from the existing booking records each time they are displayed, never shared between salons, never shown publicly and never used for any automated decision.
The salon's customer overview:for each person who books, the salon sees in its dashboard their visits at that salon, the amount spent there, the last visit, the most-booked treatment and therapist, progress in any loyalty programme, and the salon's own tags and private notes. Only bookings at that one salon are used; nothing of it is shared between salons or shown publicly. Team members the salon marks as manager see the same overview when they open an appointment through their staff link.
5. Public demand display
On the public detail page of salons that have not yet claimed their listing, we display up to five pending booking requests in an anonymous, shortened form. Publicly visible are only:
- The requested massage type and duration.
- The date and the start time rounded to the full hour (e.g. "Fri 12 Apr · 14:00") — without the exact minute.
Not public are and remain: your name (in any form), email, phone and optional note.
Purpose: this display signals real demand to the salon and encourages them to claim the listing so you can receive a response. You are notified of this display before submitting the form.
Right to object: you can withdraw your request at any time from your inbox — your card disappears immediately from the public demand display. As soon as the salon declines, the booking is cancelled or you withdraw it, the card is removed as well.
6. AI-assisted content (OpenAI)
For some content we use an AI model from OpenAI (model gpt-6-luna). We never pass data about visitors to this website, or guest and booking data from Zenarion, to OpenAI.
a) Photo captions (alt text): to make salon photos more discoverable in image search and to give screen-reader users a meaningful description, we generate short alt-text captions automatically.
- What is sent: the public URL of the photo on our image server (
images.zenarion.ch) plus the salon name and city. - What is NOT sent: any customer data, booking data or identifying information about people viewing the photo.
- What is stored: only the generated caption (max. 120 characters) in the field
Photo.caption.
b) Salon descriptions and research of public salon information:we have descriptions of salons drafted in four languages and have publicly available information about the salon researched: services, prices, opening hours and the publicly listed contact email address. For this the model uses a web search, mainly on the salon's own website and in public listings (e.g. Google Business Profile, local.ch, search.ch).
- What is sent:the salon's business data (name, address, phone, email address, website, Google rating and review count or the link to its Google listing) and, for the description, the shortened text, star rating and language of up to five recent public Google reviews of the salon, without the authors' names. The review texts only inform the tone and content of the description; no prices are derived from them.
- What is NOT sent: data about visitors, guest and booking data, and the reviews written on Zenarion itself.
- What is stored:only the texts and details we adopt, on the salon listing. Descriptions and opening hours are adopted automatically only where none exist yet; prices only if they are listed for the respective duration on the salon's own, reachable website; a contact email address only with a source. We check other suggestions by hand before adopting them. Once it has claimed its listing, the salon can change these details itself.
c) Texts for city and massage-type pages: we have the introduction and description texts of these pages drafted. Only place, canton and massage-type names and, where applicable, short editorial notes from us are sent; no personal data.
Legal basis is our legitimate interest in running a complete and up-to-date directory (art. 31 par. 1 revFADP / art. 6 par. 1 lit. f GDPR, see §3); only information that is already publicly available is processed; where the salons published it themselves, this as a rule involves no breach of personality rights (art. 30 par. 3 revFADP). The processor is OpenAI Ireland Ltd. (Ireland); see §8, and §9 for transfers abroad.
7. Verification of native reviews
Only signed-in people can write native reviews. To keep them genuine, we verify every review in one of two ways and check it by hand before it is published.
a) Through the review link of a booking: after an appointment the salon can send you a personal review link by email via Zenarion(sent via Resend): automatically, if the salon has enabled this in its settings and marks the appointment as completed, or by hand via “Request review”. We send at most one such invitation per appointment; for this we store the link code and the time it was sent on the booking. If you review through this link, no SMS is needed. With the review we store the link to the booking and the therapist recorded on it. Such reviews carry the “Verified booking” badge.
b) By SMS code: for all other reviews we verify your phone number before publication with a one-time SMS code. To do this we send your phone number to Twilio Verify (Twilio Ireland Ltd.).
- Twilio sends a one-time code to your number and checks your input.
- On successful verification we store your phone number (plaintext) on your user account (
User.phone) so we can recognise you for future reviews. - Such reviews carry the “Verified” badge.
Ratings per therapist: if a salon has turned this display on, we show on its page, next to each therapist, the average star rating and the number of published reviews assigned to them through a booking. We do not name the therapist on the individual review.
Your phone number and email address are not displayed publicly.
8. Recipients and sub-processors
- Railway — application and database hosting (EU-West (Amsterdam, Netherlands)). Privacy policy.
- Google Maps Platform (Places API) — Salon directory data, ratings, reviews, photos. Privacy policy.
- Google Identity (Sign in with Google) — Optional OAuth sign-in for users + salon owners. Privacy policy.
- Plausible Analytics — Cookie-free page-view analytics, hosted in the EU. Your browser sends each page view (including IP address and user agent) to Plausible, which uses them only transiently to derive an approximate location and browser and a daily visitor hash (with a salt rotated and deleted every 24 hours); raw IP addresses and user agents are never stored — see Privacy §2. Privacy policy.
- Sentry (GmbH, Germany) — Server-side error tracking (no user-supplied PII captured). Privacy policy.
- OpenAI Ireland Ltd. — AI image captioning (public photo URLs only), drafting salon, city and massage-type texts, and researching public salon information (services, prices, opening hours, contact email; Google review texts without author names). No visitor, guest or booking data — see §6. Privacy policy.
- Cloudflare R2 (Cloudflare Inc.) — Object storage for resized salon + city photos and 24-hour salon Stories, served via images.zenarion.ch. Privacy policy.
- Cloudflare Turnstile — Privacy-friendly bot protection on contact, booking and review forms (operated in Invisible mode — see Privacy §8). Privacy policy.
- Cloudflare CDN (reverse proxy, visitor location headers) — Edge-level reverse proxy for every request. Cloudflare forwards the visitor's IP address to our server, which uses it only for abuse protection: for rate limits it is kept solely as a pseudonymous hash and deleted 48 hours after the last attempt (see Privacy §2 and §10), and it is passed to the Turnstile check. Cloudflare also derives an approximate location (country, city, canton, latitude, longitude) from the IP address and forwards it as request headers so the homepage search can pre-select the nearest Swiss city; these coordinates are read once per request and never stored. Privacy policy.
- Resend (Resend, Inc.) — Transactional email delivery (magic links, booking requests to salons, confirmations, reminders, review invitations, claim notifications) and internal notifications to us, e.g. that a review is waiting for its check or was reported (a short excerpt, no contact data). Privacy policy.
- Twilio (Twilio Inc.) — Phone-number verification (Twilio Verify, one-time SMS code) for native review authentication, and SMS notifications (new booking requests to salons, booking confirmations, reminders, salon replies, PRO-expiry reminders to owners). Privacy policy.
- WorkOS AuthKit (WorkOS, Inc.) — Sign-in (OAuth) for AI assistants that book through our MCP interface at zenarion.ch/api/mcp. WorkOS processes the sign-in data of the person authorising the assistant (e.g. email address) and issues the access token; WorkOS stores this data in the US under Standard Contractual Clauses (see §9). Zenarion sends WorkOS no booking data. Privacy policy.
- WhatsApp (WhatsApp Ireland Ltd., Meta) — Manual relay of individual booking requests to salons without a Zenarion account, sent by us from our own WhatsApp account: the guest's first name only (never the last name), the requested time and treatment and a link to the salon's claim page (which shows no guest data) — never the guest's email address or phone number (see Privacy §4). WhatsApp is part of the Meta group and may also process data in the US (see §9). Privacy policy.
Hosting & CI: for automated deployment we use GitHub Actions (GitHub Inc.) (Post-deploy health watchdog (runs a Railway restart if the new container is unresponsive). Processes service metadata only — never user data.) Privacy policy.
Cloudflare Turnstile — Invisible Mode: when you submit a contact, booking or review form on this site, Cloudflare Turnstile runs a silent bot check in the background. There is no visible widget; the verification happens automatically. Cloudflare may collect technical information about your device and browser to perform the check, as described in the Cloudflare Privacy Policy; for the check we also send your IP address to Cloudflare. This processing is also subject to the Cloudflare Turnstile Privacy Addendum. The basis is our legitimate interest in protecting the forms against spam and abuse (art. 31 par. 1 revFADP / art. 6 par. 1 lit. f GDPR).
Database backups: we create a backup of our database every night (without the rate-limit entries, see §10) and store it in a separate, non-publicly accessible bucket on Cloudflare R2 (encrypted at rest server-side there). The encrypted contact fields (see §4) are contained in the backup exclusively in their encrypted form. Every backup run is logged. Old backups are deleted automatically after 30 days; the seven most recent successful backups are always retained regardless of age.
9. International transfers
Some of our recipients and sub-processors are based abroad or process data there: Railway Corporation (US; hosting in the Netherlands), Sentry GmbH (Germany), OpenAI Ireland Ltd. (Ireland), Google (US), Cloudflare Inc. (US), Resend Inc. (US), WorkOS, Inc. (US), WhatsApp Ireland Ltd. (Ireland; Meta group, also US) and Twilio Inc. (US, with EEA data-processing terms). Germany, Ireland and the Netherlands, like all EU and EEA states, are listed in Annex 1 of the Swiss Data Protection Ordinance as providing adequate data protection; disclosures there rely on art. 16 par. 1 revFADP. Since 15 September 2024 the same applies to US companies certified under the Swiss-U.S. Data Privacy Framework. Where a US recipient is not certified under it, we rely on the EU Standard Contractual Clauses recognised by the FDPIC, with the adaptations Swiss law requires (art. 16 par. 2 lit. d revFADP). This applies, for example, to WorkOS: there the clauses are part of the WorkOS Data Processing Addendum and apply mutatis mutandis to transfers from Switzerland; WorkOS stores sign-in data (e.g. email address) in the US. Where the GDPR applies, transfers to the US rely on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework (art. 45 GDPR) or on the EU Standard Contractual Clauses (art. 46 par. 2 lit. c GDPR). Further information on request.
10. Retention
- Server logs: 14 days.
- Salon directory data: for the lifetime of the directory.
- Booking requests: retained indefinitely for follow-up and complaint handling. On request we redact your personal data across all bookings within 14 days (see §11).
- Native reviews: while the salon is listed. On request we delete the content of your review permanently (contact: see §11); it remains in the database backups until they are deleted (see §8).
- Rate-limit entries: pseudonymous hashes of IP addresses, email addresses or phone numbers with a counter (see §2); they are deleted by an hourly job 48 hours after the last attempt. They are not included in the database backups.
- Account data: for the duration of your active account; deleted within 30 days of account deletion.
- Stories: public for 24 hours, then the row and the R2 image objects are hard-deleted by an hourly job.
- Database backups: 30 days; the seven most recent successful backups are retained regardless of age, older ones are deleted automatically (see §8).
11. Your rights
Under revFADP (and, where applicable, GDPR) you have the right to:
- Information about the personal data we process about you.
- Rectification of inaccurate data.
- Erasure of your personal data (right to be forgotten).
- Objection to specific processing.
- Data portability for data you provided to us.
To exercise any of these rights, email [email protected] — using the email address you used with us. We respond within 30 days.
Right to be forgotten for bookings: on receiving an erasure request we redact the encrypted email and phone fields (customerEmailEnc, customerPhoneEnc), delete the corresponding hashes and replace your name in the affected conversations with "[redacted]". This operation runs through a protected admin interface, is audit-logged and is normally completed within 14 days.
Data export by salons: a salon that has claimed its listing can export the booking and contact data of its own guests as a CSV file to maintain its customer relationship independently of Zenarion. The salon is itself responsible for any subsequent processing of that data; Zenarion and the salon each remain responsible for their own processing.
12. Cookies
We use only essential cookies (sign-in session, theme preference, locale choice). No tracking cookies, no advertising cookies. Plausible Analytics operates entirely without cookies. We therefore deliberately do not display a cookie banner. Stories uses sessionStorageonly to deduplicate view counting. A salon's request form also uses it to remember for two hours that you sent a request (only the masked e-mail address, e.g. a****@gmx.ch), so the confirmation stays visible after a reload or a language switch. sessionStorage is not a cookie, never leaves your browser, is cleared when you close the tab and is not used for tracking.
13. Data Protection Officer (DPO)
We are not required to appoint a DPO under revFADP. For any data-protection questions, please contact [email protected].
14. Right to complain
You may report a concern to the Swiss Federal Data Protection and Information Commissioner (FDPIC; art. 49 revFADP): www.edoeb.admin.ch. For GDPR-relevant matters you may contact the data-protection authority in your country of residence.
15. Stories
Salon owners can publish ephemeral "Stories" — a portrait photo that is publicly visible and automatically expires after 24 hours. On expiry the story is hidden immediately, and an hourly background job then permanently deletes both the database row and the associated image files.
- Storage: the image is stored — like regular salon photos — as a resized WebP variant on Cloudflare R2 and served via our image server (
images.zenarion.ch). - Retention: public for 24 hours; hidden immediately at expiry; the hourly job then performs a hard delete of the database row and the image objects on Cloudflare R2.
- View counter: for each story we keep only an aggregate view count, shown to the salon as a simple number. The counter is incremented once per browser session (deduplicated via
sessionStorage). So that it cannot be inflated artificially, we count at most one view per IP address and story per hour; for this we store a pseudonymous hash of the IP address and story ID, which is deleted 48 hours after the last view (see §10). We do not store viewer identity or an event log. - Owner responsibility: salon owners are responsible for the rights and consent of any people depicted. Stories are published without prior moderation (with file type and size validation). You can report a story; we remove flagged content the same day. Reports to [email protected].
sessionStorage is not a cookie and is not used for tracking.
Last updated: 18 November 2026