Privacy policy

Last updated: 30 October 2026

This policy explains personal-data handling for the public informational website at sliepie.dev and correspondence with its operator. It also covers sliepie Training Sync, an optional connected-account service that is in development and not yet publicly available.

Who is responsible

Jarno Nijboer, an individual developer operating sliepie.dev in the Netherlands, is the controller responsible for the personal-data processing described here.

For privacy enquiries or requests, email inquiries@sliepie.dev.

Using this website

These pages provide information about the website’s operator and its software. They have no account creation, sign-in or contact form.

The site code does not set cookies, use browser storage, load advertising trackers or include analytics scripts.

Hosting and security

This website is hosted by GitHub Pages. GitHub logs and stores visitors’ IP addresses for security purposes, whether or not they are signed in to GitHub.

For information about GitHub’s handling of this information, including retention and international processing, see the GitHub General Privacy Statement. The website operator has not configured a separate analytics service.

Purpose

Technical request information is used to deliver and protect the website. This website does not sell personal information. Where the GDPR applies to processing for which I am responsible, the basis for delivering and protecting this website is my legitimate interest in operating a reliable and secure website.

If you email me

Your email address, message and information you choose to include are used to answer your enquiry and handle follow-up. Email is handled using Proton Mail. Correspondence is kept while needed to answer the enquiry, resolve follow-up matters or meet a legal obligation. It is not used for a marketing list.

Where the GDPR applies, responding to enquiries relies on the legitimate interest in communicating with people who contact me.

sliepie Training Sync

sliepie Training Sync is an optional service that connects a run2forty2 training account to Garmin Connect™. It is in development and not yet publicly available. When it is available, it will run at training.sliepie.dev. It is an independent service. It is not a Garmin or run2forty2 product, and it is not approved or endorsed by either company. Visiting this website does not connect any account.

Connections and recipients

When you sign in to run2forty2 through the service, the sign-in email and one-time code you enter are sent to the run2forty2 sign-in backend at appapi.medewerker.app. The credentials it issues are used to obtain a separate training token. The service then reads your identity and planned workouts from the run2forty2 training API at run2forty2.nl. You must also enter and confirm your training email separately. No activity feedback or remarks are sent to run2forty2.

Garmin receives the workouts and schedules that you approve, through the official Garmin Training API. The service receives information about new activities and the original FIT files through the official Garmin Activity API. It does not use the Garmin Health API. You connect Garmin on Garmin’s own authorisation page, where you also choose the sharing permissions. Garmin and run2forty2 handle information under their own privacy notices, including the Garmin Connect privacy policy.

The operator can access retained information to operate the service and handle requests. No other recipients receive information from the service.

Information handled

• Service account: account name, password hash, sign-in sessions and recorded consent (version, time and purpose).
• Connections: protected run2forty2 sign-in and training credentials, Garmin authorisation and refresh tokens, necessary account identifiers, language and status flags, connection stages, and the training profile ID and email needed for confirmation. The sign-in email and one-time code are not retained, and the complete training profile is not stored.
• Workouts: identities and fingerprints of the reviewed source workouts, the targets you chose, Garmin workout and schedule mappings, and the outcome of each action. Agenda reads are not kept as a separate calendar history.
• Activities: activity notifications, original FIT contents and extracted measurements. FIT files can contain heart rate, location and route, timestamps, device information, distance, duration and speed or pace.
• Technical and security information about requests, used to operate and protect the service.

The service uses necessary sign-in and anti-forgery cookies. A sign-in expires after 12 hours unless you sign out sooner.

Purposes and legal bases

Information is used to make the account connections you choose, convert and publish workouts that you reviewed, show your activities privately, and keep records for operation and recovery after interruptions. Workout conversion follows fixed rules.

Optional connected-account processing relies on your consent under GDPR Article 6(1)(a). For health data, explicit consent under Article 9(2)(a) is obtained. Before you connect or approve a publication, the service shows its notice and asks for explicit consent. Each publication also requires your approval of the concrete workout. Account authentication, essential sessions and security processing rely on the legitimate interest in providing and protecting the service and preventing unauthorised access (Article 6(1)(f)).

Your information is not sold or used for advertising. It is not processed by AI services or used to train, evaluate or improve AI models.

Hosting

The service runs on a server that Jarno Nijboer owns and operates in the Netherlands. The service does not make backups of its data. Privacy correspondence uses Proton Mail.

Retention, disconnection and removal

Account and connection records, activities, FIT contents, mappings and action history are kept for operation and recovery until account removal is handled. There is no scheduled age-based deletion.

You can disconnect your training account or Garmin on the Connections page. Disconnecting stops future transfers but keeps historical records. Disconnecting the training account also cancels pending publications and removes its credentials locally. This does not prove that the token is revoked at run2forty2. Actions that were already sent cannot be recalled.

To withdraw consent and request erasure, use account removal in Your account or email inquiries@sliepie.dev. Account removal first revokes your Garmin registration. If Garmin cannot confirm the revocation, removal stays incomplete and its status is shown. After revocation succeeds, the account’s records, FIT contents, notifications, sessions and credentials are deleted. Deletion does not guarantee that the freed disk space is securely overwritten. You can also remove sharing permissions in Garmin Connect. Information already sent to Garmin or run2forty2 stays subject to their controls. Withdrawal does not affect the lawfulness of earlier processing.

To receive a copy of your data, email inquiries@sliepie.dev. There is no self-service export.

Your rights

Depending on applicable law and the processing involved, you may have rights to access, correct or delete personal information, restrict its use, object to processing or request portability.

Send requests to inquiries@sliepie.dev.

You can complain to your local data protection authority. In the Netherlands, this is the Autoriteit Persoonsgegevens.

Changes

This policy will be updated when the website or its processing changes. The date above identifies the current version.