Privacy
Files stay in your browser. With Strava, Planet Creator's Cloudflare Function reads summaries of your recent weeks, and full detail only for the week you open. With Garmin, it reads only the week you open. It turns what it reads into the planet's activity shape in memory, and Planet Creator's server stores no activity data. Garmin goes through Junction, which keeps what Garmin sends until Planet Creator deletes the connection, 30 days after you connect at the latest.
Effective 8 October 2026
When you use files
FIT files, compressed FIT files and export archives are opened in this browser tab. They aren't uploaded to Planet Creator. The browser reduces GPS tracks to origin-free route shapes before making a planet.
When you connect Strava
Planet Creator asks for Strava's read and activity:read_all permissions. To show your recent weeks, the Function fetches activity summaries for up to a year of weeks. For the week you open, it may also fetch streams containing route coordinates, altitude, heart rate, elapsed time, cadence and temperature. It immediately reduces coordinates to a relative route shape, maps the other values, and returns no latitude or longitude to the page. For a week recorded on a Garmin device, it also returns the model's name. Garmin asks that the planet, its clip and its poster show it.
The Function doesn't write this data to a database, cache, log or analytics store. Strava and Cloudflare still process the request and ordinary request metadata under their own policies. Strava may also collect data about how Planet Creator uses its API, and use it for any purpose of its own. Planet Creator doesn't poll Strava and has no webhook.
When you connect Garmin
Garmin's own developer program isn't taking new apps, so Planet Creator reaches Garmin through Junction, a health data service. Garmin's consent page asks you to let Junction read your Garmin Connect data. Junction collects what Garmin shares with it under that consent, which can include daily activity, sleep and heart rate as well as workouts. Junction stores it in the United States under its own privacy policy.
Planet Creator reads only workouts. For the Monday-to-Monday week you select, the Function asks Junction for its workout summaries and samples. The samples are route coordinates, altitude, heart rate, cadence, temperature and time. It also asks for the model of the Garmin device that recorded them. Garmin asks that the planet, its clip and its poster name it. The Function reduces coordinates to a relative route shape in memory and returns no latitude or longitude to the page.
Planet Creator stores none of it. Junction keeps it until Planet Creator deletes your connection there. That happens when you tap Disconnect Garmin, or when Garmin tells Junction the connection ended, as after you remove the app in Garmin Connect. Otherwise a job that runs every hour does it 30 days after you connected. A deletion ends the Garmin connection at once, and Junction erases the data within 7 days. Junction also stops collecting on day 30 by itself.
Junction's webhook tells Planet Creator when a Garmin connection ends. Planet Creator acts on that one event and keeps no record of it, or of anything else Junction sends. Planet Creator sends Junction no name or email: the user it makes there for your connection is a random ID.
Connection cookies
- A random OAuth check is held for ten minutes in a secure, HttpOnly cookie. For Garmin, the check and the ID of the Junction user made for you are held for 30 minutes while Garmin's consent page is open.
- A secure, HttpOnly Strava connection cookie lasts no more than 30 days. Its encrypted contents are the Strava athlete ID, granted scopes, access token, rotating refresh token and expiry time.
- A secure, HttpOnly Garmin connection cookie lasts until its Junction user is deleted, 30 days at most. Its encrypted contents are that user's ID and the time it was made.
The encryption keys stay in Cloudflare's secret store. Browser JavaScript cannot read these cookies. Planet Creator discards Strava names, profile photo, city and other profile details returned during authorization.
What your browser keeps and shares
A planet link carries a compact copy of the week in the planet's own shape. Copied links and posters omit activity names, provider IDs and absolute coordinates, but they do reveal the painted planet and derived training details to anyone you give them to. A Strava or Garmin week's link also names the Garmin device that recorded it. Saving to Your shelf stores the planet in this browser's IndexedDB. Painting several weeks at once saves each one there the same way, with its painted picture. Until that's done, localStorage holds the dates of its weeks. A small localStorage marker remembers whether this browser has played its reading before.
Disconnect and delete
Use Disconnect Strava on Make yours to ask Strava to deauthorize Planet Creator and clear the connection cookies. If the cookie is already gone, revoke Planet Creator in Strava's application settings. Because no Strava activity data is stored server-side, there is no server record to delete.
Use Disconnect Garmin on Make yours to delete your Junction user. That ends the Garmin connection, and Junction erases what Garmin sent within 7 days. If this browser no longer holds the connection, remove the Junction app under Connected Apps in Garmin Connect. Planet Creator deletes the user when Junction reports it. Either way, the hourly job deletes it 30 days after you connected.
Delete a saved planet from Your shelf, or clear this site's browser data to remove all locally saved planets and reading markers.
Contact
Questions or deletion help: rlfleming93@gmail.com. Planet Creator is made by Ryan Fleming.