Privacy Policy

Effective September 3, 2026.

Two groups of people are affected by what bookingcomp does: our customers, and the tour operators whose public calendars we read and who we sometimes write to. This page covers both. The short version: we collect little, we never see anyone's end customers, and anyone can have themselves removed by email or at /remove.

Customers: what we collect

• Account: email address, business name, a salted hash of your password (never the password), when you signed up and last signed in, and which competitors you track.
• Billing: handled by Stripe. Card numbers go straight to Stripe and never touch our servers; we store Stripe's customer and subscription identifiers and the subscription status.
• Usage logs: standard web-server logs (IP address, browser, pages requested) kept by Cloudflare for a short period for security and debugging.
• Cookies: one session cookie so you stay signed in, and — only if you arrived through a partner link — a 60-day attribution cookie that credits that partner if you subscribe. No advertising or third-party analytics cookies.

Customers: how we use it

To run the service, bill you, answer your emails and send transactional messages about your account (receipts, trial reminders, failed payments, security notices). We do not sell or rent customer data, and we do not use one customer's own-company data to seed anyone else's dashboard. We never disclose who tracks whom.

Operators whose calendars we read

The core of the service reads public booking availability: how many spots a booking calendar shows as remaining on each departure, and the advertised prices. This is business inventory data, visible to any member of the public. It contains no personal information: we never see who booked, their names, emails, phone numbers or payment details, and we never log in to anything or hold a seat. Details are on the Methodology page.

Operators we write to (prospect outreach)

To find operators who might want the product, we collect from public websites and public booking-platform listings: business name, website, city, the booking platform in use, the publicly listed business contact email, and a public Google Business Profile rating where available. We use this to send one short email introducing the service, with a link to a private preview page and a one-click unsubscribe. Every such email carries our postal address and identifies who sent it.

• Retention: prospect records are kept until you ask us to remove them or we drop the prospect ourselves; there is no automatic purge on a timer. Unsubscribe addresses are kept on a suppression list so we do not write to you again.
• Never sold or shared with anyone else. Prospect data is used for nothing except that one introduction and, if you reply, the conversation you start.
• Deletion: use /remove or email taylor@bookingcomp.com. A /remove request puts your address and website domain on the suppression list at once and marks any outreach record with that address or domain as unsubscribed, so nothing further can go out; a human then deletes the rest of the record within 24 hours, keeping only the suppression entry so we cannot contact you again.

Services we rely on

• Cloudflare — hosts the site and database and receives all web requests.
• Stripe — payments, subscriptions and billing portal.
• Resend — sends transactional and outreach email; receives recipient addresses and message content.
• Google Places — public business profile details (rating, review count, location) for operators.
• Anthropic (Claude) — drafts outreach text from an operator's public facts and helps triage replies. No customer account data is sent.

Each processes data only to provide its service to us. We do not use advertising networks.

Your rights

Whether you are a customer or an operator we hold a record about, you can ask what we hold, ask for a correction, or ask for deletion, at taylor@bookingcomp.com. We answer within 30 days and usually much sooner. If you are in a jurisdiction with specific privacy rights, they apply to you as written — we do not wait to be compelled.

Security and retention

Traffic is encrypted in transit; passwords are stored as salted hashes; production access is limited to the founder. Customer account data is kept while the account exists and for 90 days after closure for billing reconciliation, then deleted. Competitor availability history (which is not personal data) is kept indefinitely because its value is in the record.

Children

The service is for businesses and is not directed at anyone under 18.

Changes and contact

Material changes are announced by email to account holders at least 14 days before they take effect. The controller is Taylor Marean, 403 Portway Ave Unit 300, Hood River, OR 97031 — taylor@bookingcomp.com.