TrekBound
Privacy policy

Your journey belongs to you.

This policy explains what TrekBound collects, why it is used, and the choices you control.

Who operates TrekBound

TrekBound is operated by Christopher Joseph Kaye, a New York sole proprietor doing business as TrekBound. Privacy questions and requests may be sent to christopherkaye25@gmail.com.

The short version

  • You can explore without creating an account.
  • Location is optional and used for nearby history and active journey guidance.
  • TrekBound does not intentionally store precise location in product analytics.
  • Account data synchronizes only the information needed for features you choose.
  • TrekBound does not sell personal information or use it for targeted advertising.

Information you provide

This may include your email and authentication information; saved places, Passport activity, trips, lesson progress, preferences, and private notes; notification and accessibility choices; and support messages, corrections, photographs, or field notes you intentionally submit. Passwords are handled by TrekBound’s authentication provider and are not stored in readable form by TrekBound.

Location

TrekBound asks before using device location. If allowed, coordinates may be processed to center the map, find nearby history, guide an active walking or driving journey, and recognize arrival. TrekBound does not intentionally place precise coordinates in product analytics or retain a live GPS trail.

You may decline or revoke location and search manually. Journey guidance is educational assistance, not emergency or safety navigation.

Device, usage information, and analytics choice

TrekBound may receive ordinary technical information needed to operate and protect the service, including browser and device category, operating system, requested pages, error and performance reports, referral source, a random session identifier, and interaction events. Local storage, Cache Storage, and IndexedDB support saved progress, preferences, offline packs, and recovery. Product analytics are optional and do not intentionally include precise coordinates.

Checking this device…

Accounts and synchronization

If you sign in, TrekBound may synchronize your email-linked account, saved places, Passport activity, trips, preferences, and learning progress through Supabase. Some information remains only on your device unless you submit or synchronize it. Public exploration does not require an account.

Payments

When paid membership opens, Stripe will process checkout and payment details. TrekBound expects to receive payment status, plan, customer and transaction identifiers, billing email, and limited billing details needed for support, accounting, refunds, fraud prevention, and access control. TrekBound will not directly store complete card numbers or card security codes.

How information is used

  • Provide maps, stories, journeys, learning, accounts, offline access, and support.
  • Save and synchronize requested progress.
  • Measure reliability, prevent abuse, and improve TrekBound.
  • Process memberships and maintain Premium access.
  • Review corrections and contributions before publication.
  • Meet legal, security, and accounting obligations.

Providers and outside links

Netlify provides hosting and private forms. Supabase provides authentication, synchronized account data, contribution storage, optional analytics, and notification infrastructure. Stripe is planned for payments but is not active. Map, search, and routing requests may use OpenStreetMap services, Nominatim, Overpass, Photon/Komoot, OSRM, and Esri; search text, coordinates used for the request, IP address, and ordinary request metadata may reach the selected provider. Google Maps, Apple Maps, Waze, archives, museums, agencies, universities, and media sources receive ordinary browser request information only when their outside link or resource is opened. Production providers and retention settings will be reverified before paid launch.

Sharing

TrekBound may share information with providers working under instructions; when you request a public contribution; to protect users, rights, security, or the service; when legally required; or in a business transaction with appropriate safeguards. TrekBound does not sell personal information or use precise location for advertising.

Retention and deletion

Local data remains until you erase it, clear site data, or an expired cache is removed. TrekBound’s working limits are: product analytics and security logs up to 13 months; closed support matters up to 24 months; rejected or withdrawn contributions generally 12 months; published-contribution consent evidence while published and generally 3 years after removal; copyright and material-correction records 5 years; and payment/accounting records 7 years after a transaction. Restricted backups target rolling expiration within 35 days. Provider settings must be verified before paid launch.

Use the data and account deletion page to export or erase device data and request access, correction, cloud export, contribution withdrawal, or account deletion. A documented legal, security, fraud, safety, accounting, or active-dispute requirement may temporarily require limited records to remain.

Children under 13

TrekBound is a general-audience educational and travel service, not a service directed to children under 13. A child under 13 may explore public educational material only with a parent, legal guardian, school, or authorized educator. A child under 13 may not independently create an account, buy a membership, submit a contribution or media, provide a precise location, or send personal information to TrekBound. If we learn that we received personal information from a child under 13 without valid parental authorization, we will delete it. A parent or guardian may request review or deletion at christopherkaye25@gmail.com.

Schools and institutions remain responsible for required student-privacy notices, permissions, contracts, and supervision.

Security, transfers, and rights

TrekBound uses administrative, technical, and physical safeguards appropriate to the information involved, including limited access, private review queues, transport encryption through production providers, row-level account controls, data minimization, and an incident-response plan. No online service can promise absolute security. Information may be processed in the United States and other countries where providers operate. Depending on where you live, you may have rights to access, correct, delete, restrict, object, or receive a portable copy of personal information.

Changes and contact

Material changes will be dated here and, when appropriate, explained in the product. Contact christopherkaye25@gmail.com. A separate business mailing address will be added before paid public launch; no private residential address is published.

Effective and last updated: September 2, 2026