Privacy Policy

Effective: 21 April 2026

This Privacy Policy explains how Trailmark ("we", "our", "the service") handles your information when you use the service to sync Strava activities to Google Calendar.

Data we collect

When you connect your accounts, we store:

• Strava OAuth tokens — used to read your activities from Strava
• Google OAuth tokens — used to create events in your Google Calendar
• Your Strava athlete profile — ID, first and last name, and profile picture URL, shown on your dashboard so you can confirm the connected account
• Mappings between Strava activity IDs and Google Calendar event IDs — so edits and deletions on Strava stay in sync

Activity details (name, date, duration, distance, pace, elevation, heart rate) are fetched from Strava on demand and written directly to your Google Calendar — they are not retained on our servers.

How we use your data

Your data is used only to provide the sync service: reading your activities from Strava and creating, updating, or deleting the corresponding events in your Google Calendar. We do not sell your data, share it with advertisers, or use it for any other purpose.

Third-party services

Trailmark connects to two third-party services on your behalf:

• Strava
• Google

Data exchanged with these services is subject to their respective privacy policies.

Google user data

Trailmark's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use the calendar.events scope solely to create and manage the calendar events generated from your Strava activities.

Data retention and deletion

Your tokens and activity mappings remain stored until you delete them. You can remove all your data at any time from the dashboard:

• Delete my Trailmark data — removes your tokens and mappings from our servers. Your existing Google Calendar events are kept.
• Delete my Trailmark data and all synced calendar events — also deletes every Google Calendar event that Trailmark has created.

Security

Tokens are stored in a private PostgreSQL database accessible only to the service. All traffic to and from Trailmark uses HTTPS.

Contact

Questions or requests about your data can be sent to joachimlefever@gmail.com.

Changes

If we make material changes to this policy, we will update the effective date above.

← Back to Trailmark