Privacy note · November 2026

Your cruises stay yours.

This note is written in plain language. It is the policy for CruiseTrove at cruisetrove.com. It is not a substitute for a lawyer’s review before you spend money on ads.

The short version

The waitlist

If you join the list, we store:

That row is saved in Supabase (a Postgres database). The database is set so the public website can add a signup and cannot read the list back. We use the list to email you about CruiseTrove. We do not sell it. You can ask us to remove your email.

A hidden field on the form catches automated signups. If the operator turns on Cloudflare Turnstile, Cloudflare checks that a person submitted the form. Turnstile is off unless both of its keys are set.

The free logbook

The free CruiseTrove logbook does not need an account. Voyages, itinerary, packing lists, journal entries, travel-partner names and contacts, and photos are stored on that device, in the browser’s private database (IndexedDB). Photos are reduced in size on the device before they are saved. They are not placed in the small localStorage box, and they are not sent to us.

Clearing the browser’s site data, or losing the phone, can erase a free logbook. That is the tradeoff of keeping it only on the device. Export, described below, is the way to keep a copy.

Paid backup and sync

An optional yearly subscription adds sign-in (an email link, or Google), backup of the logbook across your own devices, and a way to invite a travel partner to one voyage. If you turn that on, the cloud copy includes:

Those records are stored in Supabase, in a private database and a private photo bucket. Row-level security limits each signed-in person to their own rows, plus voyages a host has explicitly shared with them. Card numbers never come to CruiseTrove. Payment is handled by Lemon Squeezy, the merchant of record, on their checkout page. They handle tax. We store whether a subscription is active or expired, and the ids Lemon Squeezy gives us, so we know whether backup should run.

If a subscription expires, the copy already on your phone remains. Cloud sync pauses. We do not delete the cloud copy just because a year ended. You can delete it yourself.

A page you choose to share

A voyage is private. If you turn on a share link, people with that link can see the cover, the route, the highlights, and the photos you marked for sharing. The public page does not include travel-partner names or contacts. You can turn the link off, or replace it, and the old address stops working.

Export and deleting an account

From the logbook’s settings you can download a copy of what is on the phone: the written records, and the photos, in one file. If you have signed in, you can also delete the cloud account. That removes the cloud voyages, the photos in storage, the subscription record we hold, and the sign-in. It also clears the logbook on the phone you used to make the request. Deleting the account does not automatically unsubscribe a card; that is done with Lemon Squeezy, and the settings screen links you there when payments are connected.

Pixels and analytics

Version 1 ships with no analytics and no tracking pixel. If the operator sets a Meta Pixel id in the site’s environment, Facebook’s pixel loads and can receive a page view. Until that id is set, the pixel code is not included in the page. We do not use a cookie banner script, a session recorder, or a marketing tag manager.

How long we keep the waitlist

Waitlist rows stay until you ask us to delete yours, or until we no longer need them to announce the product. Cloud logbook data stays until you delete the account, or until we are required to remove it.

Children

CruiseTrove is for adults planning and remembering their own travel. It is not directed at children.

Contact

To export help, a waitlist removal, or an account deletion you can’t finish in the app, write to the address published on cruisetrove.com when the operator sets one. Until then, the in-app export and delete actions are the way to take your data with you or erase the cloud copy.