Privacy notice

1. Who we are

Clear Air Stays LLC (“we”) operates clearairstays.com and decides how the personal information described here is used. Our separate Consumer health data policy covers information that the health-data laws of Washington, Nevada and Connecticut may treat as consumer health data.

2. What we collect

• Account. Name, email address, password (stored only as a one-way hash), and optionally a phone number, photo, short bio, pronouns, where you live, your work and languages. If you sign in with Apple or Google, we receive from them your name, your email address and an account identifier, and store the identifier with your account; we receive no password.
• Safety. If you choose to, one emergency contact (a name and phone number). Only our staff can read it, to follow up on a reported incident; hosts never see it, and it is in the file you can download. We also keep the people you have blocked, and any report you file about another account (its category and your note), which staff read.
• Stay preferences. The features you want in a home, chosen from a list (for example no carpet, windows that open, an air purifier), the starting answer you chose for sharing them, and, for each booking request, whether you chose to share them with that host.
• Stays and payments. Booking requests, dates, party size, the price breakdown, payment status, refunds and cancellations. Card details are handled by Stripe; we keep the card brand and last four digits.
• Content. Messages, reviews (including whether you noticed fragrance in the home and where), listing text and photographs, problem reports and their photographs, and support requests. When a photograph is uploaded we remove its location and other camera data before storing it.
• Identity verification. To book a stay or list a home, we verify a government document and selfie through Stripe Identity. Stripe compares your face with the photo on your document; that comparison uses biometric data, which Stripe collects, stores and deletes under the Stripe Privacy Policy and the consent it asks for in its own screens. Before the check starts we also ask you to tick that you agree to that comparison, and we keep a record that you did (when, and which wording). Stripe states that it removes biometric identifiers within one year; you can ask it to delete your verification data or withdraw consent at privacy@stripe.com. We never receive or store the images or any face data. We receive the verdict and the document type and issuing country; we compare the name on the document with your account name and keep only whether it matched. Any account holder can be asked to verify, not only hosts.
• Use of the site. Searches you run, with the filters used and any words you type, linked to your account if you are signed in, or to a session identifier if one is sent with the search. Listing pages you view are counted for the de-identified figures in section 6 by a counter that is not linked to your account or session (the separate records of how you use the site, below, are linked). So is each step toward a booking: a listing shown in search results, dates chosen on a listing page, and the checkout page opened. Counts we keep and show are aggregated and de-identified (section 6); the per-person search records are used for nothing else.
• How you use the site. Which listings were shown to you and for how long they were on screen, which you opened and from what position, how long you spent on a listing page, how far you scrolled and which parts you reached, where you went next, searches you ran (the place, as a recognised town or state, dates, party size and filters), and the steps you reached toward a booking. Each is recorded with the page, the time, your device type and screen size, the kind of site that sent you (for example a search engine) and any campaign tags in the link, never the full address you came from. These records are linked to a random identifier stored in a cookie on your browser, to a random identifier for the visit, and to your account when you are signed in. They never include message, review, note or profile text, or anything else you type except the place you searched for. We use them to run and improve the site and for the aggregated figures in section 6. If your browser sends a Global Privacy Control or Do Not Track signal, we set neither cookie and record these events without your account or either identifier.
• Waitlist. Your email address, whether you joined as a guest or a host, and, if you said, how many homes you run, plus any referral note sent with the signup.
• Device and log data. IP address and browser type for each signed-in session, and technical details of errors on the pages you visit.

3. Where it comes from

From you; from your use of the site; from hosts and guests you book with (for example a message or review); and from our service providers (for example a payment or identity verification result).

4. What we use it for

• Running your account and your stays: requests, payments by the host, cancellations, messages and notices.
• Ordering search results by how well each home matches your stay preferences. This runs on our server for you alone.
• Reviewing listings and acting on reports.
• Security, fraud prevention, fixing errors, and meeting legal obligations.
• Measuring the marketplace with de-identified, aggregated data (section 6).
• Sending you email or texts you have not turned off (section 9).
• Featuring a home on our social media accounts, only if its host has turned this on for that listing: the listing’s photographs and title, with a link to the listing.

5. Who receives it

• Your host, for a stay you request: your name, dates, party size and messages, and the average score other hosts have given you after past stays. Your stay preferences are included only if you choose to share them for that booking. That choice is recorded with the booking request. If you said yes, the host of that booking sees the home features saved on your profile at the moment you made the request; later changes to your profile do not reach that host. If you said no, they see none. Once the host accepts, they also see your email address and phone number, for that stay only.
• Guests, for a host: your public host profile, listing and reviews, and, once a stay is confirmed, the phone number on your account and the listing’s street address, arrival instructions and directions. Before a stay is confirmed, the listing’s map shows an approximate area, not its exact location.
• The host who referred you, if you started hosting through their referral link: how many of your stays have completed, up to five. Not your name or anything about the stays themselves.
• Service providers who process it for us under contract:
  • Stripe (payments, host payment accounts, and identity verification of guests and hosts). Stripe processes data as described in the Stripe Privacy Policy;
  • Resend (sending email);
  • Twilio (sending text messages and phone verification codes);
  • Cloudflare (hosting the site and stored photographs, running scheduled jobs, and the network every request to the site passes through). Its Turnstile check also runs when you sign up or sign in with a password, ask for an emailed sign-in link, ask for a password reset or join the waitlist: your browser sends Cloudflare technical signals about the visit, and we send Cloudflare the check’s token and your IP address to confirm a person is using the form;
  • Neon (hosting our database);
  • GitHub (storing our nightly, encrypted database backups for 90 days);
  • OpenFreeMap (map styles and map tiles; your browser contacts OpenFreeMap directly when it draws a map, which gives it your IP address);
  • Anthropic, PBC (an AI model provider). Our staff use an AI assistant to help work through the listing review queue, and it sends Anthropic what it reads from our read-only admin interface: the titles and markets of listings awaiting review, the host name shown on each listing, the result of each listing’s eligibility check, counts, de-identified totals from our marketplace figures (section 6), and record ids. It never receives a guest’s identity, the text of any message, or payment data.
• Social media platforms where we post (such as Instagram), for a listing whose host has turned on social media features: that listing’s photographs and title, which become public on the platform under its own privacy policy.
• Authorities and others where the law requires it, to protect someone’s safety, or to enforce our terms; and a successor if our business is transferred.

We do not sell personal information, and we do not share it for cross-context behavioural advertising. The site loads no advertising or third-party analytics tracker.

6. De-identified and aggregated data

We measure which home features matter to guests and how features relate to price and occupancy. For this we use data that is de-identified and aggregated, in the ways below.

Demand counters. How often each stay preference or search filter is used in a region and month, how many views and requests listings with a given feature receive, and how many reviews of a listing noticed fragrance. These counts are stored in cells that carry only a month, a region, a metric name and a feature key — no account, session, IP address or free-text column — so they cannot be joined back to a person. No demand figure is shown to a host, to staff, or published unless it is drawn from at least 10 records, and a cell below that is dropped entirely, never rounded or estimated. When you send a booking request, we count, for each feature you saved, whether the home has it; only the monthly total per state and feature is stored, and only staff see it. How many guests have saved each feature is counted from profiles when the figure is shown, and it is shown only when at least 10 guests stand behind it. A host sees how often each filter was used in searches in the states where they list, over the last 12 months, and the national share of guests who saved each feature.

Marketplace analytics. How views, requests and accepted bookings relate to a home’s features, nightly price and market, and how each attribute a host can declare lines up with revenue — two views on a page that requires a staff sign-in. Listing page views are counted without any account or session identifier, and views from an obvious bot, from the home’s own host and from our staff are not counted at all. On the price and bookings view, a figure is shown only when at least five distinct listings and five distinct hosts stand behind it; a smaller figure is hidden, and if hiding it could still let a nearby row or column total reveal it, a neighbouring figure is hidden too, and the export blanks suppressed cells. On the attributes view, each cohort is compared only with listings that answered the same question differently, and a comparison is shown only when at least the reader’s selected minimum number of listings — the smallest choice is three — stands behind it; that rule counts listings, not hosts, and drops a small cohort rather than hiding a neighbouring figure. The same view’s market-by-market rows and worked example keep their own five-listing floor, with markets below it counted in a note instead of shown. The downloadable exports follow the same rules as the views they come from.

Host earnings figures. A signed-in host sees, beside each of their own listings, the average revenue per available night of other hosts’ listings in the same city, and which home features go with higher revenue across the marketplace or in a market where they have a listing. A host setting a nightly price sees the median rate and its middle range of comparable listings in the same city and, where enough stand behind it, their median occupancy; a signed-in host’s own listings are left out of those comparables, and the price figures are also available without signing in. These figures are drawn from listings and their bookings, never from a guest’s account, preferences or searches. A feature finding is shown only when at least three listings with the feature and three without it, and at least 20 booked nights, stand behind it; the median rate and its middle range only when at least three comparable listings do, and the occupancy and revenue only when at least 10 do. The city average shown beside a host’s own listing leaves out that host’s listings and is shown only when at least 10 other listings in the city stand behind it.

Booking funnel. How many times each listing was shown in search results, viewed, had dates chosen, had its checkout page opened, received a booking request and had a request accepted, counted per listing and day, so staff and hosts can see where visits stop. The steps that searches and listing pages add are stored in cells that carry only a day, a listing, a step and a count — no account, session, IP address, browser or free-text column; views, requests and acceptances are the counts described above. Visits from an obvious bot, from the home’s own host and from our staff, and bookings made by the host or our staff, are not counted. Staff see the totals across the marketplace and per listing; a host sees them only for their own listings, for the last complete calendar month, and only once one of their listings has a step that reached 10. A step is shown only when at least 10 visits reached it, and the share that went on from one step to the next only when at least 10 reached each of the two steps.

Message bodies, problem-report text, review text and other free text are never used for this, except that when a destination you type into search ends in a two-letter US state code (such as “NC” in “Asheville, NC”), that state code is counted with the search, and a search counts toward a market’s total when the destination typed is that market’s town name; nothing else you typed is used. We do not derive any conclusion about any person’s health from preferences or searches. We maintain this data in de-identified form, we do not attempt to re-identify it, and we contractually require anyone we share it with to make the same commitment.

7. How long we keep it

• Sessions expire after 30 days, and all of them end when you reset your password.
• Your account, profile and stay preferences: until you delete them or close the account.
• Bookings, payments and refunds: as long as we must keep financial and tax records.
• Messages, reviews and reports: as long as the account or listing they belong to, and longer where needed to resolve a dispute or meet a legal obligation.
• Search records linked to your account when you are signed in, including any words you typed into search: 12 months, after which they are deleted automatically.
• The record of each signed-in session (IP address and browser): no fixed deletion period has been set yet.
• Records of how you use the site (section 2): 13 months, after which they are deleted automatically.
• Records used to limit repeated requests and stop abuse, which hold a keyed hash rather than your IP address or account: deleted within about a day after their time window closes.
• Database backups: 90 days.
• De-identified aggregate counts: indefinitely.

8. Security

Passwords are stored only as one-way hashes, the session cookie is http-only so page scripts cannot read it, traffic is encrypted in transit, and our database and file storage are managed services. No system is perfectly secure; if a breach affects you we will tell you as the law requires.

9. Email and texts

Email about a stay you are on (confirmation, cancellation, refund, password reset) is transactional, and so are security notices about your account: a sign-in from a browser or device not used on it before, a change to its email (told to the old address), password, phone number or payout bank account, or a download of its data. Everything else is a preference you control on your account page, every non-transactional email has an unsubscribe link, and we honour it within 10 business days. Texts are sent only for time-critical booking updates, only to a number you have verified, and only if you have turned them on.Sign-in codes are the exception: once your phone is confirmed, we text a code when you sign in on a device you have not told us to trust, whether or not booking texts are on. Reply STOP to any text to stop them, and we will confirm. A notification email says that a message arrived, not what it says.

10. Your choices and rights

• Change or clear your stay preferences, and stop sharing them with hosts, on your account page. The account setting is only the starting answer; each booking request asks again. On a booking where you said yes, the host keeps seeing the features you had saved when you made that request; changing or clearing your profile afterwards does not change what that host sees, and applies to your future requests.
• Sign out of every device from your account page.
• Turn on Global Privacy Control or Do Not Track in your browser to stop us linking records of how you use the site to you (section 2).
• Download a copy of your account data (profile, stays, messages, reviews, the scores hosts have given you, and saved lists) as a file from your account page.
• Ask to close your account from your account page. We sign you out everywhere, pause your listings and hide your host page, then handle deletion as described below.
• Ask to access, correct, delete or receive a portable copy of your personal information through help and support or privacy@clearairstays.com. Depending on where you live, state law may give you these rights. We verify your identity before acting, and you may use an authorized agent. Where we must keep a record, we will say which one and why.
• If we decline your request, you may appeal by replying to our decision; we will answer the appeal in writing and tell you how to contact your state attorney general if you disagree.
• We will not treat you differently for exercising these rights.

11. Children

The service is not directed to anyone under 18, and we do not knowingly collect personal information from children under 13. If you believe we have, contact us and we will delete it.

12. Where data is processed

We operate in the United States. Our hosting provider runs the site on a global network, so a request may be handled in a data centre outside the United States, usually the one nearest you. If you use the service from elsewhere, your information is transferred to and processed in the United States.

13. Cookies and similar technology

• cas_session: a cookie holding an opaque session token that keeps you signed in. Scripts cannot read it. It lasts up to 30 days.
• cas_trusted_device: set only when you get a sign-in code and tick “Don’t ask again on this device”. It names your account and lasts 30 days.cas_signin_pending and cas_oauth_state hold a sign-in in progress for up to 10 minutes. Scripts cannot read any of them.
• cas_ref: set only when you open a host’s referral link. It holds that link’s code, lasts 30 days, and is read once, when this browser’s account starts hosting. Scripts cannot read it.
• cas_vid: a random identifier for this browser, so records of how the site is used (section 2) can be told apart. It lasts 13 months. cas_sid: a random identifier for one visit, replaced after 30 minutes without activity. Scripts cannot read either, and neither is set when your browser sends Global Privacy Control or Do Not Track.
• While you book, this browser tab keeps your dates, party and message to the host so they survive a detour to verify your ID. It never keeps card details and is cleared when the request is sent or the tab closes.
• Your browser’s local storage keeps the amenity filters you last selected on the search bar and, for hosts, an unsaved listing draft and the step you reached.
• On checkout and payment pages, Stripe’s payment script sets its own cookies and collects information about your device and how you use the page, to prevent fraud, under the Stripe Privacy Policy. On sign-in, password recovery and the waitlist, Cloudflare Turnstile checks from browser signals that you are a person, not a bot.

We use no advertising cookies.

14. Changes

We will post any change here with a new “last updated” date and tell you by email before a material change takes effect.

15. Contact

privacy@clearairstays.com or help and support.