Privacy

Your account: your username and email address. Your password is not stored in readable form; it is protected using one-way password hashing.

Your travel logs: what you choose to add, including titles, summaries, notes, tips, dates if you provide them, places, events, and photos.

Drafts are not visible to other users.

A published log uses the visibility you choose:

• — Public: available on the public web and eligible for ROAMCORD discovery and search.
• — Unlisted: available to anyone with the link, but not listed in ROAMCORD search, destination results, your public profile, or the sitemap. ROAMCORD also marks it noindex, nofollow.
• — Private: not publicly accessible and not available to other users through the service.

Your saved list: the travel logs you save. It is not visible to other users.

ROAMCORD currently uses only necessary first-party cookies.

Session cookie (travelog_session): keeps you signed in. It contains a random token; the server stores only a hash of that token. The cookie lasts up to 45 days, is httpOnly, and uses SameSite=Lax.

Language cookie (travelog_locale): remembers whether you chose English, Korean, or Japanese.

Password-reset cookie (travelog_reset): a short-lived httpOnly cookie used while you complete a password reset. It lasts about 15 minutes and is limited to the reset flow.

ROAMCORD does not currently use advertising cookies, analytics cookies, or third-party tracking cookies.

Attempt and rate-limit records: used to limit repeated sign-in, sign-up, password-reset, reporting, uploads, and similar requests. Identifiers used for these controls are stored in digested form rather than readable form. These records are kept for about one day.

Search queries: ROAMCORD records what people type into destination search so we can understand what places people are looking for and whether searches return useful results. No account or IP address is stored with a search query. These records are kept for 90 days.

Travel-log views: individual view records are used to maintain aggregate view counts. They are not linked to a profile and are removed after 90 days.

Your account, travel logs, and photos remain until you delete them.

Some operational records have shorter retention periods:

• — 1 day: attempt and rate-limit records.
• — 60 days: expired or signed-out sessions.
• — 90 days: search-query records and individual travel-log view records.
• — 365 days after a decision: reports that have been acted on or dismissed.

Open reports are kept until a decision has been made. Active sessions are not removed simply because they are old.

ROAMCORD removes time-limited records through periodic automated cleanup. Because cleanup does not run at one exact hour, a record may be removed shortly after its stated retention period rather than at the precise moment it reaches that age.

Before an uploaded image is stored, ROAMCORD removes photo metadata, including EXIF data and GPS coordinates.

ROAMCORD also attempts to remove this metadata in your browser before upload when the browser can do so, but the server-side removal before storage is the guarantee.

If you mark a place as a home or private address, ROAMCORD does not publicly show its exact location. The coordinate is blurred to a broader area, the street address and provider link are withheld, and no map link is shown.

ROAMCORD does not guess whether a place is a home. You choose whether to mark it private.

Private addresses are also left out when somebody uses your public trip as the starting point for their own Plan.

Photos attached to drafts, private logs, or logs that have been taken out of public view are served only when ROAMCORD determines that the requester is allowed to see them. They are not exposed as permanent public-storage links.

ROAMCORD currently uses the following providers to operate the service:

Supabase — database hosting and private photo storage.

Vercel — website hosting and server logs.

Google Places and Routes — helps resolve destinations and places and calculate routes. Search text you enter may be sent to Google, and route calculations may send location coordinates. Your ROAMCORD account is not sent with those requests.

MapTiler — provides map tiles. Those map requests are made by your browser, so MapTiler receives the requests needed to display the map.

Resend — delivers ROAMCORD’s automated account emails, currently email-verification and password-reset messages. ROAMCORD does not currently send marketing email.

These providers process information as needed to operate ROAMCORD.

ROAMCORD does not sell personal information or share it for another company’s advertising.

ROAMCORD does not use your content to train AI models, and we do not provide it to others for that purpose.

ROAMCORD currently carries no advertising of its own.

You can delete your account from your profile.

Deleting it removes your profile, sign-in credentials, sessions, outstanding verification or reset links, travel logs, photos and their stored image files, along with events and custom places you created when nothing else still depends on them.

Some information can remain when removing it would affect somebody else’s independent content or undo a moderation record.

A place or event another person’s travel log still relies on may remain as shared reference data. A copy another person previously made from one of your public logs remains theirs, although its attribution to you disappears. Reports you submitted also remain so that deleting an account does not undo a moderation record.

Those surviving records do not retain your name.

Anyone can report a published travel log, with or without an account.

A report that says a log exposes private information takes that log out of public view immediately while it is reviewed. The creator can still access it. Beginning the review does not restore it; an operator must make an explicit decision.

Other reports enter the review queue without automatically removing the log from public view.

Email support@roamcord.com.

This page describes how ROAMCORD operates today. If those practices change, this page and the date above it will be updated.