Privacy

Last updated 22 September 2026. Skiporbook is operated by RC Ventures Group LLC. Questions go to the contact page.

What we collect

Your email address, the checks you run, and whether you've paid. If you write to us through the contact page or a report's "Tell us" box, we keep the message and the address you gave or were signed in with, so we can reply. That's the whole list of what names you. Here is what each of those is, table by table.

Your account is one row: your address as you typed it and in a normalized form, when you first signed in and when you were last here, which listing your free report went on, how many pack checks you have left and when they expire, and the same for Watch. A sign-in link is stored as a hash of the link, never the link itself, with your address, the page it should land you on, and when it expires. It's marked used once you click it. Each check you run is a row with the listing id, when it started and finished, how it came out, what it cost us, and how long each stage took. Each report you unlock is a row with your address, the listing id, and whether the free report or a pack paid for it. A watch is a row with your address, the listing, the date you asked us to watch until, when it stopped, and which version of the report we last emailed you about. A payment is a row with Stripe's id for the checkout, your address, the amount, the plan, and how many checks it granted. Your card details go to Stripe and never reach us. A message is a row with the text, the listing it was about if any, and your address when you gave one. Each time a report is saved we also keep a version row: the verdict, the review count, and the counted reason, so a report can say when its verdict moved. Nothing about you is in that row.

What we count without your name

Your internet address is never stored. What is stored is a code made from it: a hash of the address and a secret only the server holds, cut to 32 characters. The same address gives the same code, which is enough to count with, and nothing can turn the code back into the address or look it up against a list of addresses. That code sits on every check you run, for the limit of three checks an hour. It sits on every message you send, for the hourly cap on messages. It sits on your account as the address it was created from, so one connection can't make more than three accounts a day. And it sits on the funnel events below.

The site also counts a few moments between page views, so we can see where people get stuck: a press on Check listing, a check refused and why, a sign-in link sent, a report viewed and whether it was gated, an unlock pressed, a watch started and from where, and a checkout started and by which method. Each is one row with the event's name, a label or two from a fixed list like those, the listing id, a yes or no for whether you were signed in, and the address code. Never your email address. Those seven are the whole list, and the site drops anything else a browser sends.

One place holds a hash of your email address: the useful or not useful vote under a report, where a signed-in reader is counted by a hash of their address so one person gets one vote. That hash isn't salted with a secret. Nobody can read the address back out of it, but the same address always gives the same code, so somebody who had both your address and our database could match the two. The row holds that code, the listing, and one yes or no. A signed-out vote is counted by the address code instead.

What we refuse to store

We never store reviewer names, reviewer photos, or links to reviewer profiles. We read the reviews, write the report, and throw the review text away. A report may quote a short paraphrase, never a full review. What we do keep for every review we read is one row. It holds Airbnb's id for the review, its date, its star rating, the problem category and severity we assigned, how sure the model was of each, and four yes-or-no scores: whether it complains despite five stars, whether it describes a safety risk, whether it softens a problem, and whether its wording is generic. The rows are stored with the report. They let us change how we weigh a problem later without reading anything again. The report row also holds the listing header as Airbnb showed it, what the check cost us, and how long each stage took.

How long we keep the rows

The rows stay as long as the report does. They are what lets us show our work and answer a host who disputes a report. When a report is removed, its rows go with it. If a report is disputed, or a legal question is raised about it, we keep that report's rows and versions until it is settled. Check rows and funnel events aren't cleared on a schedule. The numbers on /stats are counted from them.

Where your data goes

Reports and email addresses sit in a Supabase database. The public reviews are fetched through Apify, whose output includes the review text and reviewers' first names as Airbnb shows them. We read that output once to label the reviews, then delete it from Apify the same minute, so the words and names are not kept at the vendor either. Each review's text, star rating and date go to TypeSafe, whose model answers the yes-or-no questions behind our labels. It sees the review words and never a reviewer's name. Report text is written by Anthropic's Claude from the label rows and short excerpts of the reviews. The rows are stored with the report. The excerpts are used while the report is being written and never stored. Email is delivered by Resend, payments by Stripe, hosting and page analytics by Vercel, and DNS, mail forwarding and the bot check on the check form by Cloudflare. Each of those companies sees only what it needs to do its job, and none of them get a list of who you are.

Analytics

We use privacy-friendly analytics that set no cookies and build no profile of you. That is why this site has no cookie banner. Page views are counted by Vercel. The moments between them are counted by the site itself, as described under what we count without your name, and those rows hold the address code and never your email.

Your reports are public

Every report has a public link so you can send it to whoever you are traveling with. The link contains the Airbnb listing id and nothing about you.

Deleting your data

Write to us and we will delete your address, your check history, and any messages you sent. Your unlocks, your watches, and your vote under the hash of your email go with them. Rows that hold only the address code stay, because nothing in them says they were yours. Published reports about a listing stay up, because they are about the listing, not about you.