Last updated: 7 November 2026
Valiris SAS is an AI-powered guest communication platform for short-term rental operators. We are registered in France and act as the data controller for the personal data described in this policy.
For our full company registration details, see our Legal Notice.
When you submit your email address via the waitlist form on our website, we collect your email address. Nothing else. We use this solely to notify you when Valiris is available and to send you relevant pre-launch updates.
When you create a Valiris account, we collect your name, email address, company name, and billing information (processed securely via Stripe). We also collect data about how you use the platform to improve the product and provide support.
Billing details and VAT. Before your first payment, we ask you for billing details: whether you subscribe in your own name or as a business, your name or company name, your country and, for a business, its address and its EU VAT number (required for businesses in France and the rest of the EU, not asked outside the EU). We use them to issue your invoices and to apply the right VAT. For an EU business, we check the VAT number live on VIES, the European Commission's public VAT number validation service, to which we send only the country code and the VAT number. We keep the result (valid or invalid), the registered name VIES returns and the date of the check, as proof for our accountant. These details are stored in our database and on your customer record at Stripe, and you can edit them at any time in Settings, Billing. A change applies to future invoices. Legal basis: our legal obligation (invoicing and VAT rules) and contract performance. We keep them for 10 years, like our other accounting records. Each month, the list of paid invoices (date, invoice number, customer name and email, country, VAT number, VAT treatment and amounts) is emailed through Resend to our chartered accountant, C3 Expertise, so that our VAT return can be prepared.
Sending your invoices to your accountant (optional). In Settings, Billing, the account owner can give us their accountant's email address. Each paid Valiris invoice is then emailed to that address through Resend, with the invoice PDF attached, once, and on request the past invoices too. We store the address and, for each invoice sent, the invoice reference, the address it went to, the date and whether the send succeeded, so that no invoice is sent twice. Legal basis: contract performance (you asked for it). The owner can change or remove the address at any time; once it is removed, nothing more is sent. The send log is kept for as long as your account.
You can optionally upload a profile photo. It is entirely up to you: leave it empty and we show your initials instead. If you do upload one, it is visible to the other members of your organisation and to nobody else, and you can remove it at any time from Settings, which deletes it from your profile.
When you connect your Property Management System (Lodgify, Guesty, SuperHote, Smoobu, Node or StayCore), we store a one-way cryptographic hash of your account identifier, never the identifier itself. This lets us confirm a free trial has not already been claimed on that account, without our being able to reverse the hash back to it.
If you reach us through a link on a guest portal (or another referral link), we record the referral tag carried by that link, for example 'portal', against your organisation so we know which channels bring operators to Valiris. The tag is read from the link itself; we set no cookie and use no tracker for this, and we keep it for as long as your account.
When you create an account you can also tell us, in one optional question, how you heard about us (one answer from a fixed list, for example LinkedIn or a friend). We use it only to measure which channels bring customers to Valiris. You can leave it blank, it changes nothing about your account, and we keep it for as long as your account.
You can create or open your Valiris account with your Google account instead of a password. This is optional: email and password works just as well. When you choose Google, you are asked to share your basic profile with Valiris, and Google sends us your name, your email address and a link to your Google profile picture. We ask for nothing else: Valiris has no access to your Gmail, Google Drive, Google Calendar, contacts or any other Google data.
We use your name and email address only to create your Valiris account, sign you in, and show your name to the other members of your organisation. The profile picture link is kept in your sign-in record by our authentication provider (Supabase, servers in the EU), but we do not display or use it. We do not sell this data, we do not use it for advertising, we do not use it to train AI models, and we share it with no one except the service providers that run Valiris for us (listed in section 4), under contract.
Your Google sign-in data stays for as long as your account exists and is deleted when your account is deleted (see section 7). You can ask us to delete it at any time by writing to contact@valiris.io, and you can withdraw Valiris's access from your Google account at myaccount.google.com/permissions.
Valiris's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Valiris processes guest messages and booking information on behalf of operators. In this context, Valiris acts as a data processor, not a data controller. The operator is the data controller for their guests' personal data. We process this data solely to deliver the service the operator has configured.
Guests can also send messages to their host directly through their guest portal link; these messages are processed for the same purpose and in the same way as messages relayed by the booking platform or PMS.
If a guest adds the portal to their home screen, they can choose to turn on notifications. We then store the push endpoint their browser issues, its two device keys and their chosen language, against that booking. This identifies a device, not a person, and we use it only to tell them about their own stay: a reply from their host, something waiting on them, an extra confirmed, and the moment their access codes become available. We never send marketing notifications. The notification itself carries no stay details, no access codes and no message text, because it appears on a lock screen. The subscription is deleted when the portal closes (seven days after departure), as soon as the guest turns notifications off, and when their browser tells us the device is gone.
Some direct bookings have no message thread at the host's booking system. For those stays, on the host's behalf, we use the email address on the booking to send the guest one invitation to their portal, and a short "you have a new message" email when a message reaches them and notifications are not turned on (at most one an hour). These emails come from the host's name, replies go to the host, and they carry no access codes, no message text and no marketing.
A guest can also attach photos or documents to a message, for example a picture of something that has gone wrong in the property. When that happens, Valiris copies the file from the booking platform into its own private storage so the operator can see it alongside the message. These files are readable only by the operator's own organisation, through links that expire, and are kept for as long as the message they arrived on. They are not used to train any AI model and are not sent to our AI providers.
When a guest requests an extra, Valiris also stores the service date and time and, if the guest chooses to add one, a short free-text note (for example a flight number or a pickup address). The note is shown to the operator's team only and is never used by the AI. It is kept with the booking, for the same period.
If you report a problem through the maintenance form, we keep what you wrote, the urgency you chose and any photos or video you attached, and we pass them to your host or to the person your host has chosen to handle repairs.
Some hosts work with local businesses (restaurants, therapists, guides and others) through the Valiris partner portal. Access is by invitation only. For the people who run or represent these partner businesses, Valiris is the data controller. If a host invites you, we receive your email address and business name from that host.
What we collect: your name and email address; the business profile you publish (business name, description, logo, photos, address, opening hours, contact details, links and menu) and your offers; the history of your agreements with hosts (each version of the commission terms, who proposed it, and when it was accepted, declined, paused or ended); and sign-in records (when sign-in links are sent and used, and the technical data of your sessions, such as IP address, held in our authentication provider's logs). You sign in with a password or with a single-use link sent by email. If you choose to set a password, our authentication provider stores it only in hashed form: nobody at Valiris can read it.
Why, and on what legal basis: to run the partner programme, that is to give you access to the portal, show your profile and offers to the hosts you work with, and record the agreements you make with them. Legal basis: contract performance (our Partner Terms).
Who sees it: the hosts you work with or have proposed an agreement to see your profile, your offers and the agreement terms. Your profile and offers are public business information by design: photos you upload are stored at public web addresses so that they can be shown to hosts and to their guests in the Around you section of the guest portal. Our providers process the data for us: Supabase (database, sign-in and file storage, hosted in the EU, Frankfurt) and Resend (sends your sign-in and invitation emails). If you pick a stock photo from the built-in Pexels library, Pexels receives only the search words you type, never your name or email address.
Guest data: when a guest shows you a perk voucher or stay code, or reports a visit, you see the guest's first name and stay dates, nothing else, so that you can honour the perk and confirm the visit. We also record the bill amount you enter and the commission it gives rise to. You may use the first name and the dates only for that purpose (Partner Terms, clause 7.2).
How long we keep it: for as long as your partner account exists, then 3 years after it is closed for the records of your agreements with hosts (evidence in case of a dispute). Your profile, photos and offers are removed when your account is closed. Redemption and visit records are kept for 3 years, or 10 years once commissions are settled through Valiris, as accounting evidence.
Your rights: you have the rights described in section 8 below. You can correct most of your profile yourself in the portal; for anything else, write to contact@valiris.io.
Some Valiris customers recommend us to other hosts and earn a commission (referral partners). When you sign up, if you tell us a friend or partner recommended Valiris, you can type that person's name. We keep it with your account's sign-up details so that we can credit the right person. If you arrive through a referral partner's link, we record the link's short code the same way.
What the referral partner sees: in their partner space, the name of your organisation, your plan, your number of properties and the date you joined. Apart from the booking alert described below, they never see your personal details, your guests, your messages or what you pay. They see only their own total commission. Legal basis: our legitimate interest in running the referral programme and paying commissions correctly, and our contract with the referral partner.
If you book a call through a referral partner's link: we tell that partner your name and the date and time of the call, by push notification and email, so they can follow the introduction they made. We tell them again if you move or cancel the call. Legal basis: our legitimate interest in running the referral programme.
If you are a referral partner: before your partner space opens, the account owner signs our referral agreement online. We record, as proof of signature, the signer's name and email address, the company name, legal form, SIRET number and address entered, the agreement version, the date and time, the IP address and the browser's user agent, and a fingerprint of the exact text signed. A copy of the signed agreement is emailed to the signer and to us through Resend. Legal basis: contract performance and our legal obligations (invoicing and tax declarations of commissions). When you sign, we check the SIRET number against the French State's public business register (recherche-entreprises.api.gouv.fr), sending it only the SIRET, and you tell us whether you charge VAT: your VAT number is derived from your SIRET. Commissions are paid each month by a transfer through Stripe to the Stripe account you connected to Valiris. To do so we send Stripe the amount, your connected account identifier and the month concerned. We issue the commission invoice in your name (self-billing, as the agreement provides), with your company details, VAT regime and VAT number if you have one, and email it to you and to us through Resend. We keep the proof of signature for 5 years after the agreement ends, and commission records and invoices 10 years, as accounting evidence.
How long we keep it: the sign-up details for as long as your account exists; the referral records 10 years after the last commission paid, as accounting evidence. You can object at any time by writing to contact@valiris.io: we will then stop showing your organisation to the referral partner and stop telling them about your calls.
Our website includes a chat widget that lets you ask questions about Valiris. When you use it, the messages you type are sent to Anthropic, Inc. (a third-party sub-processor based in the United States) to generate AI responses. We do not store or retain the content of your chat messages after the session ends. Your IP address is temporarily used for rate limiting purposes during the session only and is not stored. The legal basis for this processing is legitimate interest: providing you with product information before you decide whether to sign up.
Anthropic processes data in accordance with its own privacy policy. By using the chat widget, you acknowledge that your messages will be processed by Anthropic as a sub-processor.
If, and only if, you accept cookies in the banner on valiris.io, we load Google Analytics. Google then collects your IP address, device and browser information, and the pages you view on our site. We use it for one purpose: understanding in aggregate how the site is used and where visitors come from, so we can improve it. We run no advertising and no remarketing. We do not receive your name or email address from Google, and we do not combine this data with your platform account. If you refuse, none of it happens: nothing is downloaded from Google and no cookie is set. See our Cookie Policy for the exact cookies and how to withdraw consent.
When you ask for our catalogue, we collect your first name, last name, work email, company name, the language of the page and the address of the page you came from. We use them to send you the catalogue and, because you are a professional who asked about our service, to follow up with you about Valiris. The request is recorded in our sales records, and if you came from a link we sent you, it is attached to your existing prospect record. Requests that look automated (for example random names) are kept aside and never added to our sales records. You can object to the follow-up at any time by emailing contact@valiris.io.
When we send a link to a named business contact (in an email, a message or a call follow-up), the link goes through valiris.io/l/ and we record what happens next: the time of the click, whether it looks like a person or an automated link preview, which pages or slides of our presentation were reached, and which buttons were clicked (for example "Start the trial" or "Book a call"). When the link was sent to a named person, this is attached to their prospect record so we can follow up at the right moment. We also record a single daily-rotating code, built from technical details of the visit, to count unique visitors on a link; it cannot be traced back to you and cannot follow you from one day to the next. We do not use cookies or pixels for this, we do not store your IP address or your browser identifier, and the presentation page sends these events to app.valiris.io without setting any cookie. Links shared publicly, for example in a social media post, are counted in the same way but are not attached to anyone.
When we write to you as a business contact, the email is sent from one of our team's own Google Workspace mailboxes, for example lucas@valiris.io, through the Gmail API. It therefore sits in that person's Sent folder and your reply goes straight to them. We keep a record of each email sent this way with your prospect record: the date, the subject, your email address and the choices used to compose the message. We do not use open-tracking pixels. Every email ends with a one-line way to opt out: reply "stop" and we stop writing to you.
When you book a demo with us, the booking form asks the same optional question, how you heard about us. We keep the answer on your prospect record, only to measure which channels bring customers, and under the same retention rule as that record. You can skip it.
When you comment a keyword under one of our Instagram or Facebook posts (for example "EXTRA") to receive what the video offers, we reply under your comment and send you that information in a private message on Instagram or Messenger. To do this, Meta passes us your account id, your public name or username and the text of your comment, and we keep a record of what we sent. We send one message per request, only when you ask for it, and we do not add you to any mailing list. When a post asks you to follow our account first, the button you tap in the message lets us ask Meta whether you follow us; we use the answer only to decide which message to send and do not store it. Legal basis: legitimate interest (answering your request and following up with professionals who showed interest). You can object at any time by emailing contact@valiris.io. We keep these records for 12 months, then delete them. Meta processes this data under its own privacy policy.
We publish VALIRIS's own videos on our Instagram account and our Facebook Page from our own tools, through Meta's publishing interfaces, and on our TikTok account through TikTok's Content Posting API, and on our YouTube channel through YouTube API Services (see below). These videos show our founders and our team, never customers, guests or prospects. Before they go out, the video files sit in a private storage area at our hosting provider (Supabase, in the EU) and are deleted 14 days after the last publication of the video is out. To publish a video, Meta, TikTok or Google (YouTube) receives the file and its caption and handles them under its own terms and privacy policy. To post on TikTok, a member of our team signs in to our company TikTok account once; we keep the resulting access token encrypted, use it only to read that account's public profile and to post our own videos to it, and delete it when the account is disconnected. You can read TikTok's privacy policy at tiktok.com/legal/privacy-policy-eea. This step involves no personal data about you. Questions: contact@valiris.io.
Our internal admin tool uses YouTube API Services to publish VALIRIS's own videos on our own YouTube channel. A member of our team connects our company channel once through Google sign-in. We keep the resulting token encrypted and use it only to upload our videos, set their titles, descriptions and thumbnails, post our own comments under them and read their status and statistics. We do not access, collect or store any data about other YouTube users or channels. By watching or interacting with our videos on YouTube, you are bound by the YouTube Terms of Service, and Google handles your data under the Google Privacy Policy. We delete the token when we disconnect the channel, and the access can also be revoked at any time from the Google security settings page.
When a customer agrees to give us a testimonial, we may publish it on our website and marketing material: their first and last name, company, words and, if they recorded one, their voice. We publish a testimonial only with that person's consent, and we take it down if they withdraw it: email contact@valiris.io.
When you use the VALIRIS app, we record which sections you open, how long they stay open and in use, and which features you click. This is linked to your account so we can see which features are used, where people get stuck, and what to improve. We never record what is on your screen, the content of messages, or your guests' data. We keep this data for 12 months, then delete it. Legal basis: our legitimate interest in improving the service.
Waitlist email
Legal basis: consent. You voluntarily submitted your email. You can withdraw consent and be removed from the list at any time by emailing us.
Platform account & billing
Legal basis: contract performance. We need this data to provide the service you signed up for.
Referral tag at sign-up
Legal basis: legitimate interest. Knowing which channels bring operators to Valiris (for example the guest portal link) helps us decide where to invest. It is one short tag from the link you arrived by, with no cookie or tracker involved.
Guest message data
Legal basis: contract performance. Processed strictly to deliver the guest communication service operators have configured (AI replies where their plan includes them).
Audience analytics
Legal basis: consent. Nothing loads until you accept in the cookie banner, and you can withdraw at any time via "Cookie settings" in the footer. Refusing has no effect on your use of the site or the service.
Catalogue requests
Legal basis: consent to receive the catalogue (the box you tick on the form) and legitimate interest (B2B prospecting) for the commercial follow-up that may come after it. You can object to the follow-up at any time by emailing contact@valiris.io.
Prospect engagement
Legal basis: legitimate interest (B2B prospecting, the same basis as our other prospect records). We use it to follow up with professionals who showed interest, at a relevant time. You can object at any time by emailing contact@valiris.io: we then stop contacting you, mark you as not interested and disable the links sent to you.
We do not sell, rent, or trade your personal data. Apart from the local partners described in the next paragraph, we share data only with the following third-party sub-processors, each of whom is bound by appropriate data protection agreements:
Local partners (guests): if your host works with local partners and you show a perk voucher or stay code, or tell us you visited, that partner sees your first name and your stay dates, nothing else, so it can honour the perk and record the visit. This happens only when you act, and the partner is a recipient chosen by your host, not a sub-processor. If the partner has added its Google review link, after it scans your voucher we may send you one notification and, about ten minutes later if you have not answered it, one message in your conversation with that link. If you saved a perk and it was never scanned, we may send you one message on your check-out morning asking whether you made it there, with the same link. We record whether you tapped the link or chose "Not now", nothing more: we never know whether you wrote a review. Once you open the link you are on Google, under Google's own privacy policy. Legal basis: our legitimate interest, and the partners' interest, in collecting feedback on a visit you just made.
| Sub-processor | Purpose | Personal data | Location |
|---|---|---|---|
| Supabase | Database, authentication, file storage | All guest & operator data: messages, bookings, access codes, account data, KB documents | EU (Frankfurt, Germany) |
| Vercel | Website and application hosting | Guest messages & operator sessions in transit; visitor IP addresses in logs | United States |
| Stripe | Subscription payments and Extras payment links, including a reserved amount on the guest's card for extras that need the host's approval; the card is saved by Stripe on the operator's own Stripe account to place that reserve and removed right after (a daily clean-up removes any that failed). The reserve is charged if the host approves and released if the host declines or does not answer in time. When paying an extra, a guest can also tick "Save my card for this stay" (unticked by default): Stripe then keeps the card on the operator's own Stripe account for that stay only, for extras, the minibar where the property has one, and any damage, up to the deposit amount. We record when they agreed, their IP address, their browser and the exact sentence shown. The card is removed from Stripe when the claim period after the stay ends. | Payment card details, billing information, guest name on Extras line items | United States |
| Anthropic | AI message generation | Guest message content; questions typed into the in-app assistants (help assistant, Iris & Val panel); website chat messages | United States |
| OpenAI | Knowledge Base embeddings | Knowledge Base document text; guest question text | United States |
| Cohere | Search-result reranking | Guest question text; Knowledge Base document snippets | Canada |
| Resend | Transactional email | Operator/team email addresses; email body content; for direct bookings with no message thread, the guest's name and email address | United States |
| Upstash | Rate limiting (abuse protection) | IP addresses and organisation IDs only, no message content | United States |
| Cloudflare | Bot protection on sign-up and login (Turnstile) | IP address and browser signals only, no message content | United States |
| MapTiler | Map tiles and address geocoding for the turnover map inside your account, and the map in the Around you section of the guest portal | Operator IP address and the map area viewed; property addresses sent once for geocoding. Guest portal map: loaded only when the guest taps Map; the guest's IP address and the map area reach MapTiler; no cookies. No guest name or message content. | Switzerland |
| Lodgify | PMS integration (user-initiated) | Guest names, guest messages, booking & property data | Spain |
| Guesty | PMS integration (user-initiated) | Guest names, guest messages, booking & property data, guest reviews | Israel / United States |
| SuperHote | PMS integration (user-initiated) | Guest names, guest messages, booking & property data | France (company seat; hosting region being confirmed) |
| Smoobu | PMS integration (user-initiated) | Guest names, guest and host messages, booking & property data | Germany (company seat; hosting region being confirmed) |
| Node | PMS integration (user-initiated) | Guest names, guest and host messages, booking & property data, and, only if you opt in, check-in door codes and Wi-Fi details | France (company seat; hosting region being confirmed) |
| StayCore | PMS integration (user-initiated) | Guest names and contact details, guest and host messages, booking & property data | France (company seat; hosted in the EU, Netherlands) |
| Breezeway | Operations integration (user-initiated, optional) | Maintenance report text and photos, guest name, stay dates, property, PMS booking reference, and links to any videos, valid for 72 hours. VALIRIS also receives from Breezeway the names, roles and departments of the people in your Breezeway team, so you can choose who is tagged; no contact details are stored. | United States (Breezeway Assistant Inc., Boston; hosting region being confirmed) |
| Meta (WhatsApp Business Platform) | WhatsApp messages to the operator's team and contacts (optional, switched on by the operator) | Names and phone numbers of the team members and contacts (for example cleaners or maintenance staff) the operator adds. Message content: property name, the cleaning schedule, extras approval requests, and a short summary of a cleaning, maintenance or urgent problem a guest reported. Never the guest's name, phone number or email address, and never access codes. | Ireland (Meta Platforms Ireland Ltd); may be processed in the United States under the EU-US Data Privacy Framework and Standard Contractual Clauses |
| Cal.com | Demo and onboarding call scheduling (optional) | Name, email address and booking time, sent to us to send a pre-call preparation email | United States |
| Google sign-in (optional) | Google account email and name at sign-in; encrypted push notification payload | United States | |
| Google Workspace (Gmail) | Sending our prospecting emails from our team's own mailboxes | Your name, your email address and the content of the email we send you | Ireland and United States |
Separately, if you accept cookies on this website, Google Ireland Limited receives your IP address, device and browsing information. For Google Analytics it is our processor, handling that data on our instructions. This only ever happens with your consent, and never in the Valiris application itself.
For invoicing, two recipients are not sub-processors. The European Commission (VIES, a public authority) receives the country code and VAT number of an EU business when it is checked, nothing else. C3 Expertise, our chartered accountant, receives the monthly list of paid invoices described in section 2 and uses it to prepare our accounts and VAT returns, under its professional obligations.
Separately again, an operator can connect their own GetYourGuide partner account so their guests see tours and activities near the property on their booking portal. This is not a sub-processor arrangement: GetYourGuide is not processing anything on our instructions, and we send it no personal data. It is a third party the guest chooses to load, and it then acts as an independent data controller under its own privacy policy for the IP address, device signals and cookies it collects at that point. Nothing is requested from GetYourGuide until the guest taps to show the activities, having been told first what will be set and why (see our Cookie Policy). Any commission on a booking is paid by GetYourGuide to the operator, on the operator's own partner account; Valiris is not in that payment path and receives no data back.
If you or an operator enables browser push notifications, alerts are delivered through your browser's own push service: Google (Chrome, Edge, Android, via Firebase Cloud Messaging), Apple (Safari, iOS, via APNs), or Mozilla (Firefox), depending on the browser in use. Valiris holds no direct commercial relationship with these providers for push delivery; your browser's push subscription determines which one is used, and only an encrypted notification payload (title, body, and link) passes through it. When you set or reset a password, we check it against the Have I Been Pwned breached-password database using k-anonymity: only a truncated 5-character prefix of the password's hash is sent, never the password itself or a full hash.
Some of our sub-processors are companies established in the United States. Where personal data is transferred outside the European Economic Area, we rely on safeguards recognised under GDPR: the European Commission's Standard Contractual Clauses (SCCs) and, where the recipient participates, the EU-US Data Privacy Framework (DPF), together with supplementary technical and organisational measures.
For the full list of sub-processors and the transfer mechanism relied on for each, see our Data Processing Agreement.
Guest messages are processed by Anthropic's AI models to generate replies and to analyse sentiment and intent. Knowledge Base documents are converted into searchable embeddings by OpenAI, and search results are reranked by Cohere as part of the AI's retrieval pipeline.
When an operator's team marks one of the AI's replies as unhelpful (a thumbs down, with an optional note), Anthropic reads that reply, the guest messages just before it, the note, and the property's AI settings and knowledge base, and suggests one fix: a change to the AI instructions, a knowledge base document or a property setting. Nothing changes until someone on the operator's team approves it, and an approved fix can be undone for seven days. The suggestion keeps a copy of the rated reply and the guest message it answered, and is deleted with the thumbs down it belongs to. Access codes and passwords are never sent for this. Legal basis: our legitimate interest, and the operator's, in improving the AI's answers.
Under these providers' API terms, data submitted via their API is not used to train their underlying models. The operator stays in control of what the AI can access and what it is allowed to share with guests, through the AI Configuration settings in the platform.
Guest messages are also used to help the operator improve its own service. An operator can ask the AI to read a property's past message history and draft the knowledge base documents that are missing from it. Guest messages that the AI hands over to the operator's team may also be classified by the AI into an issue type and a one-line summary, so the operator can see the problems that keep coming back at a property. Both are for the operator only, and nothing is shown to guests. The AI reads the message text, but it is not sent the guest's name or contact details from the booking, and the report shows guests by first name only. What these features keep, including short quotes from past messages, is retained and deleted under the same rules as the guest messages themselves (section 7).
On the Pro plan, an operator can switch on Val's Midas Touch for a property. Val, the AI's extras persona, then decides when to offer each extra (for example a late check-out) to a guest with a confirmed booking. Every offer is logged with the booking: which extra, at what moment, when it was sent, the message text if one was drafted, and whether the guest bought it, declined it or did not reply. These logs are kept and deleted with the booking. Val also checks the mood of the conversation, using the sentiment analysis described above: if the guest seems unhappy or a problem is still open, no offer is sent. A guest who declines an extra is not offered it again during that stay. A stay receives at most three sales messages (the operator can choose from one to five), and never more than one a day. To learn which moments sell, we count offers and sales for each type of extra and each moment. We also add these counts up across all our customers. The pooled figures are numbers only: they contain no guest data, they do not identify any customer, and demo accounts are left out. We use them to time offers for every customer. Each week, Anthropic writes a short summary of what Val learned, from these counts and the names of the extras only. At launch, Val writes drafts and the operator's team sends them.
Every guest message is also sorted into a few practical topics (access codes, check-in, parking, wifi, how the property works, check-out, directions and local tips), so we know which topic a guest asked about and when. This is done by fixed word rules in our own software: no AI and no third party reads the message for it. It runs on every account, whether or not the operator uses the feature below, and these records are kept and deleted under the same rules as the guest messages themselves (section 7). On the Pro plan, an operator can switch on Iris's Sixth Sense. Iris, the AI's guest-care persona, then sends the guest the practical messages of the stay herself: a welcome after booking, a heads-up on when the arrival details will come, the access codes at the exact moment the guest portal unlocks them (never earlier), a settling-in message after arrival, a check-out reminder and a goodbye after departure. These messages are written by Anthropic from the property's details and knowledge base. Each one is logged with the booking: which message, the moment chosen, when it was sent, its text if it was drafted, and whether the guest still had to ask about the same topic. These logs are kept and deleted with the booking. The notice that an AI may be answering goes out with the first AI message of the conversation, exactly as for any other AI reply. To learn which moments work, we count, for each message and each moment, how often guests still needed to ask. We also add these counts up across all our customers. The pooled figures are numbers only: they contain no guest data, they do not identify any customer, and demo accounts are left out. We use them to time messages for every customer. At launch, Iris writes drafts and the operator's team sends them.
As a resident of the European Union, you have the following rights regarding your personal data:
To exercise any of these rights, email us at contact@valiris.io. We will respond within 30 days.
If you believe we have not handled your data correctly, you have the right to lodge a complaint with the CNIL (Commission Nationale de l'Informatique et des Libertés), the French data protection authority: www.cnil.fr.
The Valiris application uses only essential and functional cookies required for basic functionality, such as keeping you logged in. Our public website additionally uses Google Analytics cookies, but only after you accept them in the consent banner, and refusing takes a single click. See our Cookie Policy for the full list, the retention periods, and how to change your choice at any time.
We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. If the changes are material, we will notify active users by email or via a banner on the platform.
Continued use of Valiris after an update constitutes acceptance of the revised policy.
Questions about this policy?
We're a small team and we read every email. Reach out directly.
contact@valiris.io