ReinPact

Privacy policy

Valid from 13/09/2026 · last changed on 09/10/2026 (handovers, terms, hidden health entries)

This is a translation. The German version is authoritative.

ReinPact is an app that a stable uses to organise riding shares: sessions, cancellations, recurring sessions, horses and handovers. This page explains what data is created in the process, who sees it, how long it is kept and how to get rid of it.

The short version. ReinPact has no advertising, no analytics tools and no trackers. No data is passed on to third parties for advertising, and no data is sold. What is stored is what the app needs in order to work.

Controller

Fabian Pelleschi
Baumschulstrasse 28
8542 Wiesendangen
Switzerland
Email: info@cf-labs.dev

What data is created

WhatWhat forWhere from
Email address, password (only as a hash), optionally a second factor Signing in and protecting the account From the person themselves when registering
Display name and role in the stable (stable management or rider) So that the calendar shows who booked, and so that it is clear who may change what From the person themselves or from stable management when inviting
Profile picture (optional) Recognition in the calendar From the person themselves; the app removes location and device data from the picture before uploading it
Picture of a horse (optional) Recognition in the calendar From stable management; the app removes location and device data before uploading it
Sessions, recurring sessions, cancellations, absences, notes The actual purpose of the app From using the app
Handovers Recording what happened during a session From using the app
Details about the horses: name, health entries, blocks, prices, ownership Planning From stable management
Emergency contacts for a horse (optional): name and phone number of the vet practice, farrier, owner or another person, plus a note So that someone can be called in an emergency at the horse From the horse's owner or from stable management
Standing instructions for a horse, and who confirmed which version as read, and when So that important instructions get through Instruction from the owner or stable management; the confirmation from the person themselves
Invitation codes, optionally with the address a code is valid for Bringing someone into the stable From stable management
Timestamps: when something was created or changed Traceability Automatically
App feedback (optional): the text from the form and its type (bug, idea, other), together with the account's address and ID, display name, stable, role, app version, platform and language Finding bugs and improving the app; replying, if permitted From the person themselves via “App feedback”; the details about the device automatically, and the form shows them before sending

What is explicitly NOT collected: location, address book, the users' own phone numbers, payment data, advertising IDs, usage statistics. Phone numbers only appear in emergency contacts that someone enters for a horse (see above). The app contains no analytics or advertising library.

Health data concerns the horses, not the people

ReinPact keeps health entries about horses. These are not health data of persons and therefore not sensitive personal data. Who sees a horse's entries follows ownership: stable management always does. If the horse belongs to the stable, everyone in the stable sees them while it is kept there; if it belongs to an owner, the owner and the people assigned to the horse see them. Stable management and the horse's owner can hide individual entries; a hidden entry is then seen only by stable management and the owner — not by the people assigned to the horse, nor by anyone else in the stable. This is enforced by the database itself, not only by the app.

Who sees what

The data belongs to a stable. Anyone who does not belong to that stable sees none of it — this is enforced by the database itself (Row Level Security), not only by the app. Within a stable, everyone who belongs to it sees the shared sessions and horses, including who entered or cancelled a session and who blocked a horse. The master data is changed by stable management.

Emergency contacts for a horse are visible to the owner, stable management and the people assigned to the horse; if the horse belongs to the stable, is still kept there and nobody is assigned to it, to everyone in the stable. Only the owner and stable management may enter and change them. The numbers are not passed on and not used for anything else; the app only dials a number when someone taps “Call” themselves. Who has read an instruction is visible to the owner and stable management — everyone sees their own confirmation.

Legal basis

Processing is based on the contract for using the app (Art. 31(2)(a) of the Swiss Federal Act on Data Protection (FADP), Art. 6(1)(b) GDPR) and, where it concerns protecting the accounts, on the legitimate interest in secure operation (Art. 6(1)(f) GDPR).

Where the data is stored

ReinPact does not run its own servers. The following are used:

ServiceWhat forWhere
SupabaseDatabase, accounts, file storage for profile and horse pictures Zurich, Switzerland (region eu-central-2)
Cloudflare PagesDelivery of the web interface; receives app feedback and forwards it Global network, delivered from the nearest location
Resend, Inc., USASending the sign-in emails and the app feedback —
Google PlayDistribution of the Android app Under Google's terms

These providers process the data as processors, that is, only on instruction and not for their own purposes.

On the device

Without an account, everything entered in ReinPact stays on the device (in the web version, in the browser's storage) and goes nowhere.

With an account, the app keeps the most recently loaded state of the stable on the device so that it can still show something without a network. It is labelled as possibly out of date; nothing can be changed without a connection. It contains only what the person is allowed to see anyway.

When someone opens an invitation link, the app keeps its code on the device until it is redeemed or set aside — so that it survives the way through the confirmation email. The code sits in the link after “#” and is not sent to the server when the link is opened.

How long

Rights

Every person can request information about their data, have it corrected, deleted or handed over, and object to the processing. An informal message to info@cf-labs.dev is enough; we reply within 30 days. Anyone who wishes to complain can contact, in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC) and, in the EU, the supervisory authority at their place of residence.

Security

The connection is encrypted throughout. Passwords are never stored in plain text. A second factor can be switched on. Access to other stables is prevented in the database and is checked automatically with every change to the app.

Children

ReinPact is not aimed at children under 13. Younger riders are looked after through the account of an adult.

Changes

If anything significant changes, it appears here with a new date. The date at the very top says which version applies.