Privacy and data use

Accounts and saved information

Supabase provides account authentication and stores app records. Signed-in research, saved trips and their private notes belong to the account. Public community names, approved posts and verified identity links are visible to other visitors. Revocable trip-share links expose the selected itinerary projection to anyone holding the link; do not put private information in shared day notes.

AI research and safety review

AI questions, relevant public evidence and conversation context are sent to OpenAI to produce answers. Itinerary suggestions use your selected cities, dates, interests, party size and budget. Submitted community text and photographs are sent to OpenAI to assist human safety review. Do not include secrets or private identity documents in these inputs.

Guest AI questions

The two-question guest allowance uses a server-side hashed network identifier and a separate conversation identifier. Guest transcripts are scheduled for deletion after seven days. The network quota record is retained to enforce the two-question allowance; clearing a browser does not reset that allowance.

Bookings and travel partners

Places to stay shown on OneTipOneHand are booked through Stay22 with partners such as Booking.com and Expedia. You book with the partner, under its prices and terms, and OneTipOneHand may receive a commission on bookings made this way. Match tickets always link to the official seller; we do not sell or resell tickets.

Business contacts and enquiries

Researched business email addresses and routing contacts are private operator records. Buyer enquiries are shared with operators and verified representatives of the selected business with the permission captured in the enquiry form. Replies stay in that enquiry conversation. Campaign approval currently does not send email.

Photographs and retention

Community images remain in private storage. Approved post images are delivered through a publication check. Unattached uploads become eligible for cleanup after one day; removed or rejected post images after thirty days. Failed cleanup is retried. Restricted review, verification and audit records can remain for operational follow-up.

Experience measurements

We collect page-group counts and browser performance measurements without analytics cookies, full page URLs, search text, account IDs or saved-trip content. Browser Do Not Track and Global Privacy Control signals disable browser reporting. A daily hashed network identifier limits submissions and is retained for up to three days; raw IP addresses are not stored in these measurement tables. Performance samples are retained for seven days and daily aggregate counts for ninety days. Private account, operator and saved-trip pages are excluded from browser reporting.

External providers

Opening a hotel, transport or ticket-provider link takes you to that provider. Search parameters can include destination, dates and party size. Their availability, booking and information handling are controlled by that provider. A saved plan is not a booking.

Your controls and requests

Use your account to manage saved trips, research, public profile details and hidden authors. Sign out on shared devices; itinerary browser drafts are cleared by the account sign-out button. Use the feedback control to request correction, account-data assistance or review of retained information. Download an account export and submit or cancel a deletion request from the account-data page. Deletion requests require operator handling; automated deletion is not available. Cricket follows are private, and inbox preferences control cricket, enquiry and assigned-work updates. Inbox entries are retained for up to 180 days. Email notifications are not active.