Who we are
StayParity runs this site and decides what happens to the personal data it collects. Under the GDPR, that makes us the controller. For anything about your data, write to hello@stayparity.com.
When you visit
Cloudflare serves this site. To deliver a page and protect it from attacks, it handles your IP address, what your browser tells it and the address of the page you asked for. We keep short-lived request logs to find faults.
When you choose a language, the site remembers it in a first-party cookie (sp_locale) for one year. The walkthrough calendar is a frame from Cal.com, which sets its own cookies and browser storage.
We measure how the site is used with PostHog, on its EU cloud. Until you choose in the cookie banner, and if you decline, it stores nothing on your device: it counts the pages you view and when you leave one, how fast each page loads and responds, which buttons led you to the request form, its steps, your cookie choice, and whether you booked a walkthrough, telling visits apart by a server-side hash that changes every day. If you accept, it also keeps a random ID in your browser's local storage, so a return visit is linked to the last, and records heatmaps and session recordings of how pages are used, without recording what you type. Where the cookie banner says cookies, it also means similar browser storage, such as this ID. When the page hits an error, it receives the error message, with anything you typed taken out, where in the code it happened and, if you accepted, the random ID. It never receives your name, email, hotel, website or message, and does not store your IP address. Your choice stays in your browser's local storage for 12 months, and you can change it any time with Cookie settings at the foot of every page.
When you ask for a check or write to us
The form sends us:
- What you type: your name, work email, what kind of business you run, its name and booking engine and, if you give them, your website, how many rooms, hotels or units you have and your message.
- About the request: the page's language, the page you started the request from, and the site address it was sent from.
- Where you came from: if you arrived through a link with campaign tags (utm_ or ref) or from another website, those tags and that website's address, never the page you were reading there. If you came from one of our Google ads, also the click ID Google adds to the link (gclid, gbraid or wbraid).
- Your IP address, hashed: we store a keyed hash of it, never the address itself, use it to limit how often one sender can use the form, and delete it within about two days.
Before the form sends, Cloudflare Turnstile checks that you are a person. Its script loads only on the form's last step, reads technical signals from your browser, and receives your IP address from us with the check.
If you tick the box for occasional product news, we record that you did and when.
When you run the free parity check
The free parity check sends us the hotel name and town you type. We look it up in Google's hotel search from our own servers, and read the prices Google shows for three nights for the hotel you pick. Google receives what you typed, never your IP address or anything else about you.
- What we keep: the search and the hotels it found, and the hotel you checked, with its town, its own website and the prices for the three nights. We delete the check within 8 days, and the search within about a week.
- Your IP address, hashed: our limits on how often one address can run checks keep it for about two days.
Before the check runs, Cloudflare Turnstile checks that you are a person. It reads technical signals from your browser and receives your IP address from us when we confirm its result.
Nothing ties a check to you.
PostHog counts that a check was started, how it ended and whether a request followed it, and for its result only numbers: how many nights were read and compared, on how many another seller was cheaper, and whether the result was a recent one we already had. It never receives the hotel, what you typed or the check itself.
When you start a free trial
To start a trial on this site, you find your hotel, tell us who you are and confirm your email address with a code we send it.
- Finding your hotel: if you search by name, we look up what you type in Google Maps from our own servers, then read the hotel you pick in Google Hotels. Google receives what you typed, never your IP address or anything else about you.
- What a request holds: once you enter the code: your name, email address and its domain, whether you want product news, the hotel you picked with its booking sites, rooms and time zone, where you came from, and a keyed hash of your IP address, so we can see other requests from the same connection. Until then we keep only keyed hashes of your email address and of the code, the report or check you started from, and your language.
- Your VAT ID: if your hotel is in the EU, you add it in the app with your billing details during the trial. We check it with VIES, the European Commission's VAT number service, and send it to no one but Stripe, which bills you.
- Your hotel's website: if your email address isn't on your hotel's own domain, we may read your hotel's website from our servers for the email addresses it publishes, keep up to three of them, and send a code to one so the hotel can confirm the request.
Before we send a code, Cloudflare Turnstile checks that you are a person. It reads technical signals from your browser and receives your IP address from us when we confirm its result. Your browser keeps a key to your request, so you can come back to it; the key holds nothing else about you.
A request you don't send gets one reminder email a day after your last change. If your trial starts, we copy your name, email address and language into your invitation and delete the rest of the request's personal data at once.
- Telling repeats apart: we keep keyed hashes of your email address and inbox, and of your VAT ID once you save it, never the values themselves, to see a second trial for the same hotel, inbox or VAT ID.
Why, and on what basis
- Answering your request and following up: steps you asked us to take before a possible contract (GDPR Art. 6(1)(b)), and our legitimate interest in replying to business enquiries (Art. 6(1)(f)).
- The free parity check: our legitimate interest in showing hotels how their prices compare (Art. 6(1)(f)).
- Starting a free trial: steps you asked us to take before a contract (Art. 6(1)(b)), and our legitimate interest in checking a hotel is who it says and in seeing a repeat trial (Art. 6(1)(f)).
- Measuring our ads: telling Google Ads which clicks on our ads led to a request rests on our legitimate interest in knowing which ads work (Art. 6(1)(f)).
- Keeping the site and the form safe: the request logs, the bot check and the limits on how often one address can use the form or the free parity check rest on our legitimate interest in running a secure service (Art. 6(1)(f)).
- Support reports: our legitimate interest in supporting our customers and fixing problems with the service (Art. 6(1)(f)).
- Error reports and usage events in the app: our legitimate interest in keeping the service working and improving it (Art. 6(1)(f)).
- Product news: your consent (Art. 6(1)(a)). Withdraw it any time by writing to hello@stayparity.com. That doesn't affect what we sent before.
- Measuring the site: counting visits without storing anything on your device rests on our legitimate interest in knowing how the site is used (Art. 6(1)(f)). The random ID, heatmaps and session recordings rest on your consent (Art. 6(1)(a)), which you can withdraw with Cookie settings as easily as you gave it.
We don't sell your data, use it to show you ads or make automated decisions about you.
Who else handles it
These services process data for us, only on our instructions:
- Cloudflare: serves the site and runs the bot check.
- Convex: our database and backend, where your request, your trial request, the free checks run on this site and any support report are stored.
- Resend: sends the emails about your request, the codes and reminders for a trial request, and the emails about your support reports.
- Stripe: bills hotels that use the app, and receives their billing contact (legal name, billing email, address and VAT ID) and the card or bank details they pay with.
- Cal.com: runs the walkthrough calendar, and receives your IP address when the calendar loads, and your name, email and answers when you book.
- PostHog: receives the app's error reports and usage events, from its EU cloud.
- PostHog: measures how the site is used, from its EU cloud.
- Anthropic: provides the Claude models that draft a triage and a suggested reply for each support report, and that write the app's likely causes, the notes to a seller it drafts, the Monday note on your week, the opening line of your summary email and the answers in Ask. It processes what we send in the United States, and keeps it under its own API retention terms.
- Linear: tracks the issue we open for each support report. It is based in the United States.
- Google Workspace: runs our email: the emails about your request that reach our inbox, the emails we send hotels from our own mailboxes, and the replies. It is based in the United States.
- Slack: carries notes to our team's own channels: the business name, size and source of each request from the form, never your name, email or message; and for a trial request, the hotel, its rooms and your email's domain, never your name or address. For hotels that use the app, it also tells us of a new account, a new member and their role, billing changes, and problems with their checks, named by the company or hotel. The notes stay in Slack after we delete a request. It is based in the United States.
Some of these providers are based in the United States or use servers outside the European Economic Area. Where data leaves the EEA, it is protected by safeguards the GDPR recognises, such as the European Commission's standard contractual clauses or the EU–US Data Privacy Framework. To get a copy of these safeguards, write to hello@stayparity.com.
A walkthrough you book also goes into our Google Calendar, and the call runs on Google Meet. If you came from one of our Google ads, we may tell Google Ads, by its click ID, that your click led to a request, and when. Google handles that data under its own terms, as its own controller, set out in the Google Privacy Policy.
How long we keep it
We delete a request 12 months after it arrives, or sooner if you ask. We delete a walkthrough booking from our calendar 12 months after the call, and ask Cal.com to erase its copy. Request logs are deleted automatically within days.
We delete a free parity check within 8 days, and its search within about a week. The hashed IP addresses we keep to limit how often one address can use the form, the free parity check or the trial sign-up are deleted within about two days.
A trial request you don't send loses its personal data 14 days after your last change, and an unused code a day after it was sent. A request you withdraw, or that we turn down, loses it 30 days later. Once your trial starts, the request keeps only the hotel, its rooms and the hashes. We delete a request that lapsed within 8 days, and one withdrawn or turned down after a year. The hashes stay for as long as your hotel's account does, and a year after it is deleted.
If your hotel uses StayParity
When your hotel uses StayParity at app.stayparity.com, we also process account data (names, email addresses, sign-in details, and the profile photo of the Google account you sign in with, if you use Google), hotel data (properties, rooms and settings) and the rates we collect for you, to provide the service. We keep only the photo's address: the app shows the photo to your team and to us, and each browser loads it straight from Google. Ask us at hello@stayparity.com about anything this doesn't cover.
PostHog, on its EU cloud, receives the app's error reports: the error, where in the code it happened, the page's address and your browser's type, screen size and time zone, with email addresses, sign-in details and the address's query taken out. PostHog never links them to you, at most to your organisation, but a problem report you send (below) points to the ones behind its recent error messages. It also receives a record of events in your account, such as an invite accepted, an alert saved or an undercut opened or fixed, with internal IDs and fixed values only, never a name, email address, hotel name or message. Events you cause are keyed by your internal user ID.
If you report a problem from the portal, the report holds what you write, a screenshot if you add one, the address of the page you were on, the record you were looking at, your browser and app version, your screen size, browser language and time zone, and recent error messages from the app. It is linked to your account, your organisation, hotel, role and plan, and keeps your later replies. The app never adds passwords, sign-in tokens or card details.
We store the report in Convex, in the EU, and use it to fix the problem and reply to you. Anthropic's Claude reads the report and its context to draft a triage and a suggested reply. To spot duplicates, it also gets one-line summaries of up to 20 other reports your organisation sent in the last 30 days. A person on our team approves every reply before it is sent. We also open an issue in Linear with what you wrote, Claude's triage and the report's context, and add your replies and ours to it as comments, to track the fix.
We delete a report, and its issue in Linear, 365 days after it is closed, when your account is deleted, or when your hotel's account is deleted.
When the app's likely causes, the notes to a seller it drafts, or Ask are on for your hotel, we send Anthropic's Claude your hotel's own data: the undercuts, the prices, rooms and terms we read, your sellers, room names and your past decisions on undercuts. Likely causes can be on while we test them, before your team sees them. Ask can also read your hotel's name, your alert settings, your badge's views and your recent checks, and gets your question, with email addresses, phone numbers, IBANs and card numbers removed first. We can't detect a guest's name you type into a question, so it is sent as written. The Monday note and your summary email's opening line get only counts and your hotel's name.
Anthropic doesn't train its models on this data. An operator may turn one of your readings into a worked example the model sees for other hotels, only after removing every price, date and name from it. To test the likely causes before hotels see them, an operator may replay readings they have labelled, with their prices, stay and seller, through the model, and some through a second model that judges the answers. Nothing is replayed from an account while its AI is switched off. Everything the model writes is marked as written by AI, and can be wrong.
We keep an Ask conversation for 90 days after its last message, an explanation for as long as the undercut it explains, and a Monday note for 30 days. Deleting a hotel deletes every conversation that read it. An account admin can switch every AI feature off in Settings, and from then on nothing from your account is sent to Anthropic for them.
Our team can see and change your account's data and settings in our admin tools, to run the service and to help you. Every change made there is recorded internally, with who made it and when, and we keep that record for up to 365 days. Our staff never sign in as one of your users, never change your billing except through Stripe, and never read your Ask conversations.
Your rights
Under the GDPR you can ask us for:
- Access: a copy of the data we hold about you.
- Correction: to fix anything wrong or incomplete.
- Erasure: to delete it.
- Restriction or objection: to pause using it, or to stop a use that rests on our legitimate interest.
- Portability: what you gave us, in a format a computer can read.
- Withdrawing consent: to stop product news, at any time.
Write to hello@stayparity.com. We reply within a month, and may ask you to confirm it's you.
You can also complain to a data protection authority. In Greece that is the Hellenic Data Protection Authority, www.dpa.gr.
Changes
If we change this notice, the date at the top changes with it.