Skip to main content

Privacy Policy

1. Who we are and what this covers

Tidepass is run by Tyler Jardine, a sole proprietor doing business as Tidepass (“Tidepass”, “we”, “us”). We are the business responsible for the personal information described in this policy. Our contact details are in section 13. This policy explains what personal information we collect through gettidepass.com and related services, why we collect it, who we share it with, and the choices you have.

It covers four groups of people:

  • Guests: people who get a pass. Guests don’t need an account, but can make a free one.
  • Venues: businesses that list experiences on Tidepass, and the people who manage their accounts.
  • Partners: creators, vacation-rental hosts and Business Partners (businesses such as hotels, gyms, employers, apartment communities and cafes that offer Tidepass to their guests, members, residents or staff) who recommend venues and earn on verified visits.
  • Visitors: anyone browsing the site.

California privacy law. Tidepass is a small business. As far as we can tell, we are below the size thresholds that make a business subject to the California Consumer Privacy Act, as amended by the California Privacy Rights Act (“CCPA”): we don’t have more than $25 million in yearly revenue (as adjusted by the state), we don’t buy, sell or share the personal information of 100,000 or more people or households, and we don’t make money from selling or sharing personal information. We follow the California Online Privacy Protection Act, and we choose to give everyone the CCPA-style rights and notices in this policy anyway. This policy also works as our notice at collection. If we ever become subject to the CCPA, we’ll follow it in full.

Venues run their own businesses. When you book with a venue, use its booking site, sign its waiver or pay it, that venue’s own privacy policy applies, not this one.

2. What we collect

2.1 Guests

  • Pass details: pass code, venue, experience, date, party size, estimated visit value, pass status and check-in time. (CCPA category: commercial information.)
  • Email, only if you ask us to email your pass: we send the pass and keep a hashed version (to enforce pass limits). We also keep an encrypted copy, which no one reads, so we can ask you once to confirm your visit total (or, if the pass wasn’t checked in, whether you went), tell you if the venue disputes your visit, and ask for your receipt if the venue enters a total well below your pass estimate. We delete the encrypted copy once the visit is settled and we’ve asked, or 14 days after your pass date at the latest. (CCPA category: identifiers.)
  • Your answers about a visit, if you give them: your “Confirm your visit” answer (whether your bill was about the total we showed), your reply if a venue disputes your visit (and any note you add), whether you undid a check-in, for a pass that wasn’t checked in, whether you went (we also record whether a pass was missed, to apply the missed-pass rule in our Terms), whether you told us a venue was full, and, for a pass with a member perk, whether you got it. Each is kept with the time. We use them to check what the venue is billed and to spot fraud. The venue isn’t told your answers, except that a visit is under review or was undone, or that we’re following up on a missed member perk. (CCPA category: commercial information.)
  • Account, only if you make one: your email address, your first name if you give it, the date you agreed to the Terms with a hashed IP address, sign-in records, the passes in your account and your Tidepass Rewards history (visits counted, points, rewards redeemed, used and expired), member perks and Rewards Marketplace rewards put on your passes, and whether you got them. We use it to run your account and rewards and to prevent reward fraud, such as one person with many accounts. Venues and partners don’t see your account or email. (CCPA categories: identifiers; commercial information.)
  • Invites, only if you share or use an invite link: if you have an account, your invite code, the hashed device IDs and IP addresses we see while you’re signed in to My passes (the last 40), and the invites linked to you with their status. If you open someone’s invite link, a cookie remembers it for 30 days; if you then grab a pass, we record that your pass came through their invite, with the hashed IP address already on your pass. To decide the reward we compare the hashed email, device ID, IP address and card fingerprint already on your pass with earlier passes and with the inviter’s. We use these only to check that a friend is new to Tidepass and isn’t the same person as the one who invited them, and to spot invite fraud. The person who invited you sees only how many of their invites are waiting or earned, never who you are. (CCPA categories: identifiers; commercial information.)
  • Receipt, only if you choose to add one: a photo or PDF of your receipt and the total you enter. We use it only to check the visit total the venue is billed on. Only our team can see the photo. The venue doesn’t see the photo, but if we use it to correct a total, we tell the venue the receipt total. Receipts can show part of a card number or a name; please cover card numbers. We don’t use anything else on the receipt. (CCPA category: commercial information.)
  • Gifts, only if you buy or receive one: the buyer’s name and email, the recipient’s name and email, and the buyer’s message, all stored encrypted. We use them to deliver the gift on the chosen date, send the buyer’s receipt, remind the recipient if the gift isn’t booked after 60 and 180 days, send booking updates, and handle refunds. The venue sees only the booking, as for any paid booking. When the recipient books, their email is used for that booking like any paid booking. (CCPA category: identifiers.)
  • Time slots, only if the venue takes bookings by time: the slot you pick. If the venue books through its own booking system (such as Acuity Scheduling, Square Appointments, Calendly, Bookeo, Peek Pro, Xola, Ventrata or Zaui), we also ask for your first and last name, and we send your name, email address and slot to that venue’s account in that system so the venue holds your time. We also send the pass code and party size, and for most systems whether you paid online. No phone number is sent to any of these systems. Square keeps you as a customer of that venue in its records. We keep your name encrypted only until the booking is made, and for no more than 2 days. If the venue only connected a calendar link, nothing about you is sent to its calendar; the venue can see its Tidepass bookings (pass code, experience, time and party size) in a private calendar link we give it. (CCPA categories: identifiers; commercial information.)
  • Waitlist, only if you join one: your email address, party size, the experience and date, and your preferred time if you pick one, plus how many times we’ve emailed you about it. We store your email encrypted, with a keyed hash so the same email can’t join the same date twice, can’t be on more than 3 waitlists at once, and so we can tell when you book that date. We use it only to tell you if a time opens up. The venue doesn’t get your email from the waitlist. To stop abuse we count waitlist joins per hashed IP address (for an hour) and per hashed email (for a day). (CCPA categories: identifiers; commercial information.)
  • Likes, comments, saves and itineraries, only if you use them with an account: the creators’ posts you like, your comments and replies with the time, comments you report and why, your collections (their names, the posts in them, and a share link if you make one) and your itineraries (their names, the places and experiences in them and any dates you add). If you turn an itinerary into a Day Plan, its experiences go into the Day Plan list on your browser (the tp_dp cookie in section 9). If we stop an account from commenting, liking and reporting, we note that on the account. To stop abuse we count comments, likes and saves per account for a short time. (CCPA categories: identifiers; commercial information; internet or other electronic network activity.)
  • Hashed IP address and device ID: used to spot fraud, such as many fake check-ins from one phone. The device ID is a random code your browser stores; it is not your name, phone number or advertising ID. (CCPA categories: identifiers; internet or other electronic network activity.)
  • Referral credit: which creator or host link or code brought you, if any. (CCPA category: internet or other electronic network activity.)
  • Reviews, if you choose to leave one: your first name or initial and what you write. Reviews are public. (CCPA category: identifiers; commercial information.)
  • Guest reviews of a stay, if you leave one: your first name, last initial, the month you stayed, your rating, what you write, whether you said you know the host, which pass the review link came with, and a hashed IP address and device ID (to stop fake and duplicate reviews). The name, month, rating and text are public on the host’s page. (CCPA categories: identifiers; commercial information.)
  • Return-stay email sign-ups, if you join a host’s list: your email address, optional first name, the property, the consent wording you agreed to with the date, whether you confirmed or unsubscribed, and a hashed IP address. We keep this email address readable, because the host needs it to email you. (CCPA category: identifiers.)
  • Guest Guide unlock: if you enter a host’s stay PIN, we set a cookie on your device for 12 hours so the private section stays open. We don’t record which guest unlocked it.
  • Group requests, if you send one: your name, email, optional phone, the event type, party size, date or “flexible”, city, activity type and any notes, the time you confirmed, and a hashed IP address (to stop spam). Your email and phone are stored encrypted. We share your name, email and phone only with venues (up to 3) that pay to unlock your request, so they can contact you about it; that’s the purpose of the request, and you confirm it before we send anything. Venues see the rest of the request without your contact details. (CCPA categories: identifiers; commercial information.)
  • Messages you send us, such as a support email, including your email address and anything you include.
  • Short-lived hashed IP addresses in counters that stop abuse (for example, too many check-in or PIN attempts). They expire within a day.

2.2 Venues

  • Account details: account email and the names and contact details of the people who manage the account. (Identifiers; professional information.)
  • Business and listing details: business name, address, phone, hours, experiences, prices, photos, booking link and redemption settings. (Commercial and professional information.)
  • Visit and billing records: confirmations, adjustments, disputes, invoices, strikes and trust score. (Commercial information.)
  • Screening answers: your answers to our eligibility questions (business type, alcohol license type) and your certification that they’re true, with the date, the question version and a hashed IP address. We keep them as a record of what you certified. (Commercial and professional information.)
  • Payment card: held by Stripe. We never see or store full card numbers.
  • Bank account, only if you add one for fees: you connect it through Stripe (Stripe Financial Connections), under Stripe’s privacy policy. We keep only the bank name, the last 4 digits and Stripe’s reference for your debit authorization. We never see or store your bank login or full account number.
  • Messages with other businesses: messages you send to and receive from venues or partners through your account, with the time sent. They’re private between the two businesses. We also keep your setting for who can start a conversation with you, and any block or report you make. We read a conversation only if it’s reported, to investigate suspected fraud or a breach of our terms, or when the law requires it. (Identifiers; professional information.)
  • Partner deals: deals offered, accepted, declined or ended between a venue and a partner, with their terms, any note, the dates and who ended them. (Commercial information.)
  • Insurance details: your insurer, policy expiry date and, if we ask, your certificate of insurance. (Commercial information.)
  • Booking system details, only if you connect one or send them to us: the account IDs, logins and keys you enter to connect your booking system. Keys, passwords and tokens are stored encrypted and never shown again. If you send details for a system marked “Available soon”, we store them encrypted and use them only to test that connection (and, if you allow it, make one test booking and cancel it right away) and to set it up for you. (Professional information.)
  • Support records: a log of changes our support team makes in your dashboard (shown to you) and our internal notes about support requests, kept to provide support and for security. (Commercial information.)

2.3 Partners (creators, hosts and businesses)

  • Account details: account email. You sign in with a link we email you, so there is no password. (Identifiers.)
  • Profile details: handle, display name, photo, bio, social links, your picks and notes. Your public page shows what you choose to publish. (Identifiers; professional information.)
  • Business details, for Business Partners: business name, category, website, phone, address, booking link, brand color, headline and intro text. Most of it appears on your public co-branded page. (Identifiers; professional information.)
  • Logos and images you upload: for example, a business logo or hero photo. We store them and show them on your page and printables. (Identifiers, if an image shows a person.)
  • Portfolio, for creators: the posts you add (the link, title, caption, tagged venues and experience, the “Gifted visit” label, a creator visit you link it to, whether it’s public or private, its order and whether it’s featured), photos and cover images you upload, your portfolio settings and your private share link. We re-encode uploaded photos, which removes location (GPS) and camera details. For a TikTok link, our server asks TikTok for the post’s cover image and keeps a copy; nothing about visitors is sent. If you use a portfolio post as your post for a venue, it’s added to your Posts tab under the Partner Terms. We email you at most once a day about new comments on your posts. (Identifiers, if an image shows a person; professional information.)
  • Messages with other businesses: messages you send to and receive from venues or partners through your account, with the time sent. They’re private between the two businesses. We also keep your setting for who can start a conversation with you, and any block or report you make. We read a conversation only if it’s reported, to investigate suspected fraud or a breach of our terms, or when the law requires it. (Identifiers; professional information.)
  • Partner deals: deals offered, accepted, declined or ended between a venue and a partner, with their terms, any note, the dates and who ended them. (Commercial information.)
  • Performance and earnings records: codes and links, campaign codes for each placement (for example, a QR card, poster or email), claims, verified visits, tier, earnings and payout history. (Commercial information.)
  • Screening answers: your answers to our eligibility questions (business type, professional licenses, alcohol license type and, if it applies, your agreement to tell clients you earn), your certification that they’re true, the date, the question version and a hashed IP address. We use them to decide whether you can join and earn, and keep them as a record of what you certified. (Commercial and professional information.)
  • Team members and property owners: if an account owner adds you to their team, your email, name and sign-in records, and what you do in the account. If a host adds a property owner for monthly reports, that owner’s name and email, used only to send those reports. (Identifiers; professional information.)
  • Shipping details for a printed kit: name and address, used to print and ship it. (Identifiers; commercial information.)
  • Payout and tax details: collected and held by Stripe through Stripe Express. We never see your bank account numbers or full tax ID. We receive payout status from Stripe.

2.3A Corporate accounts

  • Account details: the company’s name, the contact person’s name, work email and phone, a billing email if you give one, the date you agreed to the Corporate Account Terms, with a hashed IP address. (CCPA categories: identifiers; professional or employment-related information.)
  • Payment method and authorization: Stripe holds the card or bank account; we keep only the card brand and last 4 digits (or bank name and last 4), Stripe’s reference ids, and when the authorization to charge it was given. (CCPA category: commercial information.)
  • Bookings and invoices: each booking’s venue, experience, date, time, party size and amounts, each invoice’s due date, status and charge attempts, and any credit limit you ask for and our decision on it. (CCPA category: commercial information.)

2.4 Visitors

  • Basic technical information needed to load pages and keep the site secure.
  • Sponsored placement counts: when a Sponsored listing is shown or clicked, we record an event with the listing, the page type and the time, so we can count impressions and clicks for the venue that paid for it. These events don’t include your name, email, IP address or device ID, and we don’t use them to build a profile of you.
  • First-party, aggregate analytics: counts such as how many people viewed a page. These counts don’t store your IP address, device ID or any cookie, and we don’t build profiles of individual visitors.
  • Google Analytics and Google Ads measurement: to learn which pages and marketing bring people to Tidepass, and to count purchases and sign-ups, we use Google Analytics and Google Ads conversion measurement. Google’s code sets its own cookies on your browser (see section 9) and receives your IP address, browser and device details, the pages you view and, when you claim a pass, start a checkout, buy something or apply, that event (with the experience and venue for a booking). We set Google’s ad personalization, Google signals and remarketing to off and turn on Google’s restricted data processing setting, so we don’t build advertising audiences from your visits and Google doesn’t use this data to show you ads on other sites. When an account holder buys something, we also tell Google that the purchase happened (the order number, amount, what was bought and a scrambled account ID) from our server, and, for Google Ads conversions, Google may match the account email, which your browser hashes before sending. We don’t send names or addresses. None of this loads if you have opted out or your browser sends Global Privacy Control. You can turn it off on Your Privacy Choices or with the cookie notice.
  • Venue and creator videos, only if you press play: some venue pages and creators’ posts have a video. Nothing loads from the video provider until you press play. Then the video or post loads from the platform it’s on: YouTube (in its privacy-enhanced mode), TikTok, Instagram, Facebook or X for creators’ posts, or, on venue pages, YouTube or Vimeo (with its “do not track” setting). That platform receives your IP address and may set its own cookies or storage under its own privacy policy. We don’t store these videos; they play from the platform.
  • Creators’ posts on other sites: a post on TikTok, Instagram, Facebook or X shows as a card with a picture we store. Nothing loads from that site unless you tap the card, which opens the post on that site under its own privacy policy.

2.5 Sensitive personal information

We do not ask guests, visitors or partners for sensitive personal information as defined by the CCPA, and we do not use any to infer characteristics about you. Stripe collects the payout and tax details it needs (which can include a tax ID) directly, under its own privacy policy.

3. What “hashed” means, in plain words

Hashing runs a piece of information, like an email address, through a one-way math formula. Out comes a scrambled string of letters and numbers. The same email always makes the same string, so we can tell “this is the same person as before” (for example, to stop someone claiming dozens of passes). But we can’t read the scrambled string back into your email.

Hashing makes information much harder to misuse, but it isn’t magic. We still treat hashed information as personal information, protect it, and delete it on schedule.

4. Where we get it

  • From you, when you claim a pass, check in, write a review, apply as a venue, join as a partner or contact us.
  • From your device, automatically, when you use the site (for example, the device ID and IP address, which we hash).
  • From venues, when they confirm, adjust or dispute a visit linked to your pass.
  • From partners, when you use their link or code (we learn which partner referred you, not anything else about you).
  • From Stripe: whether a payment went through, refunds and disputes, and a card fingerprint for guest payments; and payment and payout status for venues and partners.

5. Why we use it

  • To create, deliver and show your pass, and let you check in.
  • To confirm visits, check visit totals (including with receipts you choose to add), bill venues and pay partners correctly.
  • To credit the right creator or host for a visit, and to reward guests for invites that qualify.
  • To prevent and investigate fraud and abuse, such as fake check-ins, self-referrals, or venues not honoring passes. This includes our automatic watchdog checks, venue trust scores and mystery shops.
  • To show verified reviews.
  • To show creators’ portfolios with their comments and like counts, keep your saved posts and itineraries, and moderate comments.
  • To run, secure, fix and improve the site, using aggregate analytics.
  • To measure which pages and ads bring people to Tidepass, using Google Analytics and Google Ads conversion measurement (section 2.4).
  • To count impressions and clicks on Sponsored placements and show venues and partners their totals.
  • To answer your messages and send service emails (like your pass, sign-in links, invoices and payout notices).
  • To meet legal, tax and accounting duties, and to enforce our terms.

We don’t use your information for purposes that don’t fit these without telling you first.

6. Who we share it with

We do not sell personal information, and we do not share it for cross-context behavioral advertising. We haven’t done either in the past 12 months. We use Google only to measure our own site and purchases, as described in section 6.4, with its advertising features off. We share information only as follows.

6.1 With the venue on your pass

When you claim a pass, you are asking us to pass it to that venue so it can honor your discount. The venue receives: pass code, experience, date, party size, estimated value and check-in time, and for a paid booking the time you asked for and the amount paid. If you add a receipt and we use it to correct the visit total, the venue is told the receipt total (not the photo). If a partner’s exclusive deal is on your pass, the venue sees that it’s a partner-deal pass. The venue does not receive your email address from us, with one exception: if the venue books time slots through its own booking system (such as Acuity Scheduling, Square Appointments, Calendly, Bookeo, Peek Pro, Xola, Ventrata or Zaui), we send your first and last name, email address and slot (with the pass code, party size and whether you paid online) to that venue’s scheduling account to hold your time, and you’re told this before you book. That copy is held by the venue and its scheduling provider under their own policies. Our Venue Partner Agreement forbids venues from using pass data to market to you without your consent.

For a corporate booking, the venue also receives the company’s name. If the venue books times through its own booking system (such as Acuity Scheduling, Square Appointments, Calendly, Bookeo, Peek Pro, Xola, Ventrata or Zaui), the name for the booking, the company’s billing email and the time go to that system to hold the time.

For a booking with stops at more than one venue (a collab or a trip), each venue receives the details above for its own stop and the names of the other venues on the trip. It doesn’t receive what you paid the other venues. If a venue books times through its own booking system (such as Acuity Scheduling, Square Appointments, Calendly, Bookeo, Peek Pro, Xola, Ventrata or Zaui), the name for the booking, your email and that stop’s time go to that system to hold your time.

Day Plans work like other bookings with several venues: each venue receives the details for its own stop and the names of the other venues. If you give a Day Plan, we store the recipient’s name and email and your message encrypted, and use them only to send them the plan. If you share your plan’s link, anyone with it sees the date, party size, stop times, venues and addresses, but not your passes, prices, name or email. For a company booking we send a receipt to the company’s billing email. The recommended stops on a trip page are chosen by the city of your stops; we don’t send those businesses anything about you.

To suggest venues that might work well together, we count, for each venue, how often guests visited another venue on the same day (matched by account, email or device, in the last 180 days). Venues see only these counts, and only when there are at least 3. They never see who the guests were.

6.1A Group requests

When you confirm a group request, you direct us to give your name, email and phone to up to 3 matching venues that choose to unlock it. Those venues pay us a fee for this. Venues that don’t unlock it see the request without your contact details. Each venue that unlocks it then handles your details under its own privacy policy.

6.2 With creators, hosts and Business Partners

Partners see counts (claims, check-ins, verified visits), the venues and dates involved and what they earned. They never see who you are.

Exception: return-stay email lists. If you join a host’s list and confirm, that host receives your email address, first name (if you gave it), the property and the date you confirmed, so they can email you. You’re directing us to give it to them, so this isn’t a sale or sharing of your information. The host becomes responsible for it as an independent business, under its own privacy policy. Hosts must include an unsubscribe link, and you can unsubscribe at any time. Apart from group requests you send (section 6.1A) and host lists you join, we don’t give your personal information to other businesses for their own marketing. Hosts also see the guest reviews you post about their property, as everyone can.

Creators see the comments on their posts, with the name shown publicly, and how many likes each post has. They don’t see who liked or saved a post, or anyone’s email.

If a creator gives someone their private portfolio link (for example, a venue they ask for a higher rate), that person sees the creator’s posts, private ones too, and the creator’s overall totals: link clicks, QR scans, passes claimed, visits and the value of confirmed visits. A venue that gets the link with a rate request also sees the creator’s totals at that venue, never at other venues. These are totals. They never show who the guests were.

Business Partners see totals only, by campaign, placement and venue. To keep anyone from being picked out (for example, one employee or one hotel guest), any group with fewer than 5 visits is hidden or combined.

Venues see totals of views, impressions, clicks, claims and visits in their Insights, by source, partner and campaign. They don’t see who you are.

6.3 Between venues and partners

When a venue and a partner message each other or make a deal, each sees the other’s business or display name, handle or listing, the messages and the deal terms. They don’t see each other’s account email from us unless someone shares it in a message. Guests can’t send or receive these messages. Each business sets who can start a conversation with it, and can block or report a conversation. A report sends that conversation to our team.

6.4 With service providers

We use service providers who handle information only to provide services to us, under contracts that limit how they can use it:

  • Stripe: guest payments for paid bookings (in Stripe’s secure payment form on our own payment pages), venue card payments, bank debits and payouts, corporate account payments, partner plan payments and partner payouts (Stripe Express), and preparing and delivering partners’ tax forms. Stripe’s own script runs on those payment pages, and on the card pages of venue, partner and corporate accounts, and may set cookies and collect device information to prevent fraud, under Stripe’s privacy policy.
  • Google (Analytics and Ads measurement): counts visits, pass claims, checkouts, purchases and sign-ups, as described in section 2.4. Google acts for us under its own terms, with ad personalization and remarketing turned off. Google Analytics keeps event-level data for no more than 14 months. It isn’t used for the fraud checks or deal credits described above.
  • An email delivery provider: to send passes, sign-in links and service emails.
  • Hosting and infrastructure providers: to run the site and store data.

6.5 Publicly

Reviews (with your first name or initial) and partner public pages, including Business Partners’ co-branded pages with their logo and images, are visible to anyone.

Creators’ public portfolio posts, the comments on them (with the commenter’s first name, or “Tidepass member”) and their like counts are visible to anyone. A shared collection is visible to anyone who has its link. A private portfolio post is visible to anyone the creator gives their private link to. Photos in private posts are stored at an unlisted web address, and anyone who has that address can open the photo.

We may disclose information if the law requires it, to protect people’s safety, to protect our rights or to fight fraud. If the Tidepass business moves to another entity (for example, a company its owner forms to run it) or is merged, sold or otherwise transferred, personal information moves with it to the new operator. This transfer is not a sale. The new operator becomes the business responsible for it, is named on this page and in the site footer from the date of the move, and must keep the promises in this policy. If it ever wants to use or share your information in a way that’s materially different from this policy, it must tell you before it does.

7. How long we keep it

We keep personal information only as long as we need it for the reasons in section 5. These are the periods we use:

  • Pass records: the hashed IP address, device ID and card fingerprint linked to a pass are erased 24 months after the pass was claimed. After that, the pass record (code, venue, experience, date, party size and amounts) is kept for billing and tax records but can’t be tied to a person or device.
  • Hashed email: on a pass, deleted 90 days after collection. For a collab or Day Plan, a hashed copy is also kept on the order record and deleted 90 days after the order.
  • Day Plan gifts: the recipient’s name and email and your message are deleted 90 days after the plan date.
  • Gifts: the buyer’s and recipient’s names and emails and the message are deleted 90 days after the gift is booked or refunded (90 days after a checkout that was never paid). While a gift is unused, we keep them so it can still be delivered, booked or refunded. A booking made with a gift then follows the rules for paid bookings.
  • Your name for a time-slot booking: deleted once the booking is made in the venue’s booking system, and within 2 days at the latest. The slot stays with the pass record.
  • Waitlist: your email address, party size and preferred time are deleted when you leave the list with the link in our email, or once we’ve emailed you 3 times for that date. If we had emailed you about that date, we then keep only the keyed hash of your email with the experience, the date and how many emails we sent, so you can’t get more than 3 emails for that date by joining again. Everything, including that note, is deleted when the date passes (within about an hour) or when you book that experience for that date with the same email.
  • Corporate accounts: while the account is open; then as for venue and partner accounts (contact details deleted or de-identified 24 months after closing). Corporate invoices, charges and authorizations are billing records (7 years).
  • Encrypted email (to ask you to confirm your visit or for a receipt): deleted when the visit is settled and we’ve asked, or 14 days after the pass date, whichever comes first.
  • Invites: the hashed email, IP address, device ID and card fingerprint stored with an invite are erased about 13 months (395 days) after the invite was made, or when either account is deleted. The invite record itself (who invited, the pass, the status and any reward) is kept with the inviter’s rewards history while their account is open. The hashed devices and networks we note for an account holder are deleted with the account.
  • Guest accounts and rewards history: while your account is open. Delete it any time from My passes; the account and its rewards history are deleted, and your passes stay only as the pass records described above.
  • Receipt photos: deleted 90 days after check-in, or after we finish reviewing that visit’s total if that’s later. The total you entered stays with the pass record.
  • Venue reviews: for as long as they’re published, unless you ask us to delete yours.
  • Guest reviews of a stay: for as long as the host’s page exists, unless you ask us to remove yours or we remove it under our content rules. The hashed IP address and device ID stored with a stay review are erased 24 months after it was posted. Removed reviews are kept as a moderation record until 24 months after they were posted, then deleted. Ask for removal at support@gettidepass.com.
  • Likes, collections and itineraries: until you delete them, or your account. A collection’s share link lasts until you turn it off.
  • Comments: until you, the creator or we delete them. When a comment is deleted, its words are erased right away; if it had replies, a “Comment deleted” note stays in its place. Comments our team removes for breaking the rules are kept as a moderation record for 24 months, then deleted. A report is deleted when the comment is deleted or when our team has reviewed it and kept the comment, and after 24 months at the latest.
  • Creator portfolios: until the creator removes a post. When a creator removes a post, its likes, comments and saves are deleted with it. A post our team takes down is hidden and kept for 24 months as a moderation record, then deleted with its likes, comments and saves. When a partner account closes, its portfolio comes down right away and is deleted 24 months after closing. A private share link works until the creator turns it off or makes a new one.
  • Return-stay sign-ups: while you’re on the list. If you never confirm, we delete the sign-up after 30 days. If you unsubscribe, we keep only your address and the date for 24 months so you aren’t added again by mistake, then delete it.
  • Group requests: your email and phone are deleted 90 days after the event date (or 120 days after the request if your date was flexible). Unconfirmed requests lose their contact details after 3 days. The rest of the request, without contact details, is kept with the venues’ lead records. Venues that unlocked your request are responsible for the copy they have.
  • Aggregate analytics and Sponsored counts: deleted after about 13 months (400 days).
  • Abuse counters: expire within a day.
  • Booking system details: deleted when you disconnect the system. Details sent for a system marked “Available soon” are deleted when you withdraw them, when we decline the connection, or when they become your connection. The record of each connection test keeps no keys or logins.
  • Venue and partner accounts: while the account is open. When an account closes, its public page or listing comes down right away. Profile and contact details are deleted or de-identified 24 months after closing (kept that long for disputes, fraud checks and unpaid amounts), except what’s in the records below.
  • Billing, payout, tax and agreement records (invoices, statements, charges, payouts, plan subscriptions and the consent you gave to them, agreement acceptances, partner deal records, screening answers and certifications, strikes and the audit log): 7 years after the end of the year they relate to, to meet tax, accounting and legal duties, then deleted.
  • Messages between venues and partners: 24 months after the last message in the conversation. If a conversation was reported, we keep it until 24 months after the report, so we can deal with it.
  • Support messages: 24 months after our last reply, unless they’re part of a dispute or legal matter, in which case until it’s resolved.

Backups: we keep backup copies of the site so we can recover from failures. Information deleted from the live site can stay in a backup until that backup is replaced, which takes up to about 5 weeks. We don’t use backups for anything except recovery.

8. Security

We collect as little as we can. We hash guest emails, IP addresses and device IDs, and encrypt the short-lived email copy described above. Receipt photos are stored where they can’t be opened from the web, and only our team can view them. We never handle card or bank numbers for payments. Stripe does. We use encrypted connections, limit staff access to what each job needs, and use reasonable safeguards for the kind of information we hold. No system is perfectly secure, so we can’t promise that information will never be accessed without permission. If a breach affects you, we’ll notify you as the law requires.

9. Cookies and local storage

We use a small number of cookies and browser storage items. Ours are not used for advertising. Google’s measurement cookies, listed in the table, only count visits, pass claims, checkouts and purchases, and don’t load if you’ve opted out or your browser sends Global Privacy Control.

Cookies and browser storage used on gettidepass.com
Name Type What it does How long
tp_ref Cookie Remembers which creator, host or business link or code brought you, so they get credit (and you get any deal they have) if you claim a pass within 60 days. A code you type yourself takes priority. 60 days
tp_gref Cookie Set only when you open a guest’s invite link. Remembers which guest invited you, so they can earn an invite reward if your first visit qualifies. Holds their account number and the date, signed so it can’t be changed. 30 days
tp_spc Cookie Set only when you click a listing marked Sponsored. Lets the venue see that a pass came from its sponsored placement. Holds the placement number, not who you are. Not set if you opted out. 7 days
tp_dev Cookie A random device ID, set the first time you do something that needs it, such as opening a partner link, claiming a pass or gift, booking a collab or Day Plan, signing up for an account, checking in or leaving a review. Links the passes you grab on this browser and helps us spot fraud, such as self-referrals or insider reviews. We store only a hashed copy on our side. 1 year
Saved passes (tp_passes) Browser storage Lists the passes you grabbed on this browser so “My passes” can show them. Stays on your device. Until you clear your browser data
Day Plan list (tp_dp) Cookie Remembers the experiences you added to your Day Plan on this browser. Doesn’t say who you are. 14 days
Guest Guide unlock (tp_gpin_ followed by a number) Cookie Set only after you enter a host’s stay PIN. Keeps that host’s private Guest Guide section open on this browser. Doesn’t say who you are. 12 hours
Google Analytics (_ga, _ga_ followed by an ID) Cookie (set by Google) Tells Google Analytics that two page views come from the same browser, so visits and purchases are counted once. Not set if you’ve opted out or your browser sends Global Privacy Control. Up to 2 years
Google Ads measurement (_gcl_au, _gcl_aw) Cookie (set by Google) Only used if we run Google Ads. Lets us tell whether a pass claim, purchase or sign-up followed a click on one of our ads. Not used for ad personalization or remarketing. Not set if you’ve opted out or your browser sends Global Privacy Control. Up to 90 days
Privacy choice (tp_privacy, tp_privacy_seen) Browser storage Remembers your analytics choice (which also covers Google measurement) and that you’ve seen the privacy notice. Stays on your device. Until you clear your browser data
Opt-out signal (tp_optout) Cookie Tells our server your analytics choice, so it stops counting your page views and Sponsored views and clicks, and stops sending purchases to Google. 1 year
Dashboard view (tp_mode, tp_venue) Cookie For signed-in venue and partner accounts only: remembers which dashboard and venue you last opened. 1 year
Viewing options (tp-a11y-prefs) Browser storage Remembers your accessibility settings (text size, contrast, read-aloud speed and so on). Stays on your device; never sent to us. Read aloud uses your browser’s built-in voice, so the text it reads isn’t sent to us. (Some browsers use their maker’s online voices; that’s covered by your browser’s own privacy terms.) Until you reset them or clear your browser data
Wi-Fi printables (tp_wifi: followed by your handle) Browser storage For hosts and business partners only, and only if you tick “remember”: keeps the Wi-Fi details you typed on the print page. Never sent to us. You can forget it with one click. Until you forget it or clear your browser data
Sign-in session (WordPress cookies whose names start with wordpress_logged_in_ and wordpress_sec_) Cookie Keeps you signed in after you use a sign-in link (guest, venue, partner and corporate accounts). 14 days, or until you sign out
Stripe (set by Stripe) Cookies On payment pages: where guests pay for a booking, and the card pages of venue, partner and corporate accounts. Stripe uses them to prevent fraud and keep payments secure. See Stripe’s cookie policy. Set by Stripe

Our own analytics is first-party and aggregate, and it doesn’t set any cookie or storage of its own. The Google cookies above are the only analytics or measurement cookies on the site. You can turn all of it off on Your Privacy Choices or with the cookie notice. If you clear your browser data, “My passes” on that browser will be empty, so keep your pass code or emailed pass. A venue or creator video you choose to play may set the video provider’s own cookies (see section 2.4).

9.1 Do Not Track

Some browsers send a “Do Not Track” signal. There is no common standard for it, so we don’t respond to it differently. We don’t track you across other sites over time. We don’t allow advertising companies to collect information about your activity on Tidepass for their own use or to target ads. The only other companies that can collect information on Tidepass pages are Google (Analytics and Ads measurement, unless you’ve opted out), Stripe, on payment pages and account holders’ card pages (for fraud prevention), and the video platforms (YouTube, Vimeo, TikTok, Instagram, Facebook and X), only if you press play on a venue or creator video or post; each does so under its own privacy policy. We do honor Global Privacy Control (see section 10.1).

10. Your California privacy rights

If you live in California, you have these rights. (As explained in section 1, we give them voluntarily even though the CCPA may not yet apply to us.)

  • Right to know: ask what personal information we have collected about you, where it came from, why we use it and who we disclosed it to, and get a copy.
  • Right to delete: ask us to delete it, with some legal exceptions (for example, records we must keep for billing, tax or fraud prevention).
  • Right to correct: ask us to fix information that is wrong.
  • Right to opt out of sale or sharing: we don’t sell or share, but you can still record your choice, and we will honor it if our practices ever change.
  • Right to limit use of sensitive personal information: we don’t use sensitive personal information for anything beyond what the law allows, so there is nothing to limit. You can still contact us.
  • Right to non-discrimination: we won’t deny you a pass, charge you differently or give you worse service for using your rights.

We try to give the same choices to people outside California too.

10.1 Global Privacy Control

If your browser sends a Global Privacy Control (GPC) signal, we treat it as a request to opt out of sale and sharing for that browser, and we turn off optional analytics, including Google measurement. You don’t need to do anything else.

10.2 How to make a request

We’ll confirm we got your request within 10 business days and answer within 45 calendar days. If we need more time (up to 45 more days), we’ll tell you why.

10.3 How we check it’s you

Guests don’t need an account, so for a guest without one we match what you send us against what we hold. That usually means your pass code(s), and if you had a pass emailed, the email address you used (we hash it and compare). For guests with an account, venues and partners, we’ll ask you to confirm from your account email. We’ll ask only for what we need, and we use it only to verify you. If we can’t verify you, we’ll tell you why. Opt-out requests don’t need verification.

Because we keep so little about guests, we often can’t link information to you without your pass code. If you’ve lost it and didn’t have it emailed, we may have nothing we can tie to you.

10.4 Authorized agents

You can have someone else make a request for you. We’ll ask for signed permission from you, and we may ask you to confirm your identity with us directly, unless the agent has a valid power of attorney.

11. Children and teens

Tidepass is not for children under 13. It is not directed to them, businesses mainly for children under 13 can’t join, and we don’t knowingly collect personal information from children under 13. You must be 18 or older to claim a pass, leave a review or open an account; children can come along on a pass an adult claims for the party. If we learn we collected information from a child under 13, we’ll delete it. Write to support@gettidepass.com if you think this happened.

We do not sell or share the personal information of anyone, including consumers under 16.

12. Changes to this policy

We may update this policy. We’ll change the “Last updated” date at the top and, for big changes, post a notice on the site and email account holders. We won’t use information we already have in a materially different way without telling you first and, where the law requires, getting your consent.

13. Contact us

Tyler Jardine, a sole proprietor doing business as Tidepass
1906 Oceanside Blvd, Ste WX, Oceanside, CA 92054
Email: support@gettidepass.com