Public policy

Privacy Policy

This page explains the data Mercurius currently uses to provide its private, shared travel workspace. It describes the product as it works today.

Mercurius is personally operated by Adam Rensch.

Last updated July 30, 2026

Information Mercurius uses

Mercurius uses your name, email address, and authentication identity to sign you in and determine which trips you may open. Within a trip, the service stores information that travelers choose to add, such as trip details, member roles, itinerary items, tasks, expense records, packing items, discussions, and invitation status.

Expense features record and calculate shared costs. Mercurius does not send money or process payments.

Where information is handled

Clerk provides authentication. Mercurius receives the identity details needed to sign you in and authorize access.
Cloudflare D1 stores application records for accounts, trip access, workspaces, invitations, and collaboration features.
Your browser uses localStorage to cache workspace data on that device. This cache can include trip information and is separate from server-held data.
Resend delivers trip invitation emails. Invitation delivery can include the recipient name and email, inviter name, trip name, role, and a link to Mercurius.

Documents and private file storage

Private document storage is retained in the application architecture but is currently disabled. Mercurius blocks document upload, preview, download, and deletion actions that would contact Cloudflare R2. The application may retain document metadata in D1, but it does not present disabled document uploads as an available feature.

Services Mercurius does not currently use

Mercurius does not currently access Gmail. No language-model provider currently receives trip data through Mercurius. Mercurius does not currently process payments.

If Mercurius later offers Gmail, AI, payment, or other integrations, activation will require separate notice and consent.

Sharing and access

Trip information is available only to signed-in people whose email addresses have access to that trip. Roles control which shared information a member can view or change. Personal itinerary items have member-specific access controls. Packing lists are private by default; a list owner may explicitly share a list with selected active trip members, who can then view and change that list. Invitation data is shared with Resend only for email delivery.

Your choices

You can sign out at any time. You can also clear Mercurius site data in your browser to remove that device’s local cache. Clearing browser data does not delete information held on the server.

Account deletion and trip deletion are separate requests. To request either one, or removal of account-private information, follow the account and data deletion instructions or email supportmercuriustravel@gmail.com. Mercurius does not publish a fixed response or deletion timeline.

Policy changes

This policy will be updated when the product’s data practices change. Future integrations require separate notice and consent before activation.