← Back to Tkahk3

Privacy Policy

Last updated: 2026-06-05

Overview

Tkahk3 is a hiking trip planner. It helps you discover trails, schedule weekends, and (when you opt in) record your completed hikes. This policy describes what data we store, the third parties that receive it, and how you can request deletion.

What we collect

  • Account. Your Google email address and (optionally) display name, from Google OAuth at sign-in.
  • Profile. Optional preferences you provide: home address (geocoded to coordinates), maximum drive time, fitness level, preferred weekend day, minimum elevation gain.
  • Hike plans. Trails you schedule, the dates, your per-calendar visibility and busy-check preferences, and any notes you attach.
  • Calendar tokens. The OAuth access and refresh tokens issued by Google so the app can create and update calendar events on your behalf. Stored encrypted at rest.
  • Activity tracks. If you upload a GPX file from Garmin or AllTrails, we store the file, the parsed geometry, and the computed stats (distance, elevation, duration).

Third parties that receive your data

Supabase

Hosts the database that stores your account, profile, hike plans, calendar tokens, and activity tracks. Subject to Supabase's privacy practices.

Google APIs

Google Calendar, accessed under the https://www.googleapis.com/auth/calendar scope, for reading and writing your calendar events on your behalf when you schedule hikes. See the "Google API services" section below for specifics.

OpenWeather

Receives the latitude and longitude of a trail when you view it, in order to return a forecast. No user-identifying data is sent to OpenWeather.

Vercel

Hosts the application. Request logs (IP addresses, user agents, paths) are subject to Vercel's privacy policy.

Google API services

Tkahk3 requests the https://www.googleapis.com/auth/calendar scope at sign-in. With this scope the app:

  • Creates and updates calendar events on the calendar you designate as the default destination, whenever you schedule, replace, or unschedule a hike.
  • Reads existing events on calendars you mark as “count as busy” in order to detect conflicts when proposing weekends for hikes.
  • Reads the list of calendars attached to your Google account so you can choose which to display, which to count as busy, and which to write events to.

Tkahk3 does nottransfer Google user data to third parties for advertising, audience targeting, credit determination, or any purpose unrelated to the planner's user-facing features. Tkahk3 does not use Google user data to train generalized machine-learning models. Tkahk3 does not sell Google user data.

You can revoke Tkahk3's access at any time by removing it under myaccount.google.com/permissions. Revocation immediately invalidates the stored tokens.

Data retention and deletion

Your data is retained while your account is active. To request full deletion of your account and associated data, email support@tkahk3.com. We will delete your records within 30 days of receipt. Revoking Google access (above) prevents future calendar interaction but does not delete data already stored.

Cookies

Tkahk3 uses a session cookie issued by Supabase Auth to keep you signed in. No third-party advertising or analytics cookies are set.

Changes to this policy

We may update this policy as the app evolves. The “Last updated” date above reflects the most recent revision. Material changes will be surfaced in-app.

Contact

Questions about this policy or requests related to your data: support@tkahk3.com.