Privacy Policy
Last updated: November 5, 2026
1. Introduction
HorseGirl (“HorseGirl,” “we,” “us,” or “our”) is operated by Piotr Morawski, Ulmer Straße 1, 89264 Weißenhorn, Germany, who is the controller of your personal data. This Privacy Policy explains how we collect, use, disclose, and protect information when you use the HorseGirl mobile application (the “App”), the Apple Watch and Wear OS apps, this website, and any related services (together, the “Service”).
The App works offline first: your data is stored on your device first and synced to our server in the background, so it is available on all your devices and to the people you share it with. This Policy is also available in German, French and Spanish; for users in Germany, France or Spain, that version prevails.
2. Information We Collect
We collect information you provide directly, information generated by your use of the Service, and information from third-party services you choose to connect.
Account and authentication
We use Clerk, a third-party identity provider, to manage sign-up and sign-in. Depending on how you register, this includes your email address, a securely hashed password, your name, your profile photo, a phone number (only if you enable SMS-based multi-factor authentication), and identifiers from social sign-in providers (Google, Apple). Your Clerk profile also holds your app language, so notifications reach you in your language, and your notification choices. We record whether sign-in emails were delivered, never their content.
Before you sign up
Before creating an account, you can tell the App a little about yourself and your horse (for example breed, age, or riding style) to see first insights. These answers are sent to our server and to OpenAI without being linked to any account.
Rider profile and body data
Information you provide about yourself as a rider, such as your general region, riding disciplines, experience level, years riding, goals, and how often you ride or compete. If you choose, you can also add body data such as height, weight, and age, for example so we can estimate the energy you use while riding. We treat body data as health data and process it only with your consent, which you withdraw by removing it.
Horse, stable, and care-provider records
Information you enter about your horses and stable, which may include: a horse's name, nickname, and photos; ownership details; insurance provider and policy number; microchip, registration, and passport numbers; health information such as allergies, conditions, medications, vaccinations, health visits, lab results, and wound photos from health watching; feeding plans, equipment, costs, tasks, calendar events, mucking rota, and turnout plan; and the name, phone number, email, and clinic name of veterinarians, farriers, dentists, or other care providers you add. When you measure something with the camera (for example the size of a wound), the camera image is analysed on your device; only the photo you take is stored. Some of this information may identify third parties (for example, a horse's owner or a care provider), whom you are responsible for having the appropriate basis to share with us.
Shared workspaces and horse shares
You can share data in a workspace or share a horse with someone by their email address. We store the invited person's email address and notify them once they have an account with it. Everyone with access sees the shared data and, depending on their role, can edit it. A horse's costs are only visible to a share if you switch that on.
Rides, training, and location
When you record a ride, lunge session, walk, or other training, we collect precise GPS location (latitude, longitude, altitude, speed, and accuracy) and your phone's or watch's motion sensors (acceleration, rotation) for its duration, including while the App is in the background or your device is locked, so the recording continues. From this, the App and our server work out gaits, distance, pace, and seat, hands, rhythm, and collection analysis. A ride's raw data is stored as an encrypted file. If you set an address or drop a pin for your stable, we store that location and use it for weather forecasts and map display.
Heart-rate data
With your permission, we read heart-rate data from Apple Health or Google Health Connect, from your watch, or from a paired Bluetooth heart-rate monitor during a recording. We only read this data; the App never writes data back to Apple Health or Google Health Connect. We do not use, and will never use, this health data for advertising, marketing, or any other use-based data mining purpose, and we do not sell or share it with data brokers or advertising platforms.
Ride safety and emergency (SOS) alerts
If you add emergency contacts, we store their names and phone numbers (optionally picked from your address book) and your own phone number, so your contacts can call you. When you add a contact, we send them a text message telling them you added them and record whether they confirm.
While you record, the App reports your location, battery level, and whether you are moving to our server about every 30 seconds. If the App detects a possible fall, a drag, or a stand-still you don't respond to, if you call for help yourself, or if your phone unexpectedly goes silent during a ride, our server alerts your emergency contacts by text message and phone call through Twilio. The alert includes your name, your horse's name, the kind of alert, a low-battery warning if relevant, your last known location and its time (as a Google Maps link), your phone number, and a link to an emergency page that keeps your location up to date. If you cancel, contacts who were already alerted get an all-clear. We record which messages and calls went to whom and whether they were delivered, opened, or confirmed. Emergency services are not alerted automatically.
Improving fall detection
Only while "Help improve fall detection" is switched on in the SOS settings, we use your data to train our detection model: the detailed sensor data of your rides (motion sensors, compass, GPS points, heart rate if you record it, and battery level), for every alarm a recording of the motion sensors and GPS points from 30 seconds before it was raised until it ended (at most five minutes), your answers in the App (for example whether you really fell), your SOS settings (without your contacts' names or numbers), your device model and the app version. For accounts created before November 5, 2026, the switch is on until you switch it off; for newer accounts it is off until you switch it on.
While the switch is off, we keep neither alarm recordings nor your rides' detailed sensor data for training, and none of your data is used for training, including what you shared before. A model already trained keeps what it learned. Your rides themselves, and alarms and alerts to your contacts, work the same either way. For training we only use this data pseudonymised, without names, contacts, or account identifiers, in an isolated environment at Amazon Web Services in Frankfurt. We never sell it or use it for advertising.
Photos and files
Photos and documents you upload, such as horse or equipment photos, task attachments, and horse documents (for example, insurance or passport files).
Push notifications and emails
We use OneSignal to deliver push notifications and emails, which receives a device push token, an internal account identifier, your name, email address, and language so it can target and personalize notifications to you.
Usage analytics and crash reports
We use PostHog for product analytics, which receives in-app interaction events (for example, screens viewed or steps completed) together with an internal account identifier. Analytics events never contain text you typed, names, or precise locations: for example, we record that you filled in an emergency contact, not its contents, and that you set a stable location, not its coordinates. PostHog also receives crash and error reports (the technical details of what went wrong and the screens and actions just before it) and app performance measurements, such as how long the App takes to start, so we can find and fix problems. We do not record your screen. Analytics providers also automatically collect standard technical data, such as device type, operating system, app version, and IP-derived approximate location. You can switch off usage analytics and crash reports at any time in the App under Profile → About → “Share usage analytics”; once off, the App sends none.
Operational logs
Our server and the App write technical logs about requests, errors, and warnings, which we store with Axiom. They contain machine values such as identifiers, status codes, durations, app version, and platform, never content, email addresses, or names. The App's warnings are also sent when you are signed out, then without any account link.
Feedback and problem reports
When you send feedback in the App, report a sign-up problem, or email us, we process your message, your contact details, and technical details such as app version and platform to handle it. We keep feedback after you delete your account, but no longer linked to you.
Purchase data
Subscriptions are purchased through the Apple App Store or Google Play and managed with RevenueCat, which receives an internal account identifier and your purchase/subscription status. We never receive or store your payment card details.
3. How We Use Your Information
- To provide and sync the Service's features (horses, stables, tasks, calendar, health, rides, and training) across your devices and with the people you share with, including while you are offline.
- To run the ride safety feature: detecting possible falls, drags, and stand-stills, and alerting your emergency contacts.
- To improve the reliability of fall detection.
- To send you notifications you have requested or enabled.
- To provide weather forecasts for your stable and rides, maps, and address search (using Open-Meteo, OpenStreetMap, and Mapbox).
- To offer AI-assisted features through OpenAI's API, such as identifying equipment from a photo, feeding, rug, and weather advice, weight insights, feedback on rides and training, and answers to questions about your horse's health. Inputs include only what the feature needs, for example the photo, horse attributes (such as breed, weight, or clip type), ride figures, or your question. OpenAI states it does not use API data to train its models. These suggestions are informational only and are not a substitute for veterinary or professional advice.
- To process subscriptions and manage entitlements.
- To maintain, secure, and improve the Service, including through product analytics and logs.
- To comply with legal obligations and enforce our terms.
4. Legal Bases for Processing (EEA/UK Users)
If you are located in the European Economic Area or the United Kingdom, we rely on the following legal bases: performance of a contract (to provide the Service you request); your explicit consent for health data such as heart rate and body data (Art. 9 (2)(a) GDPR); your consent for using your data to improve fall detection (Art. 6(1)(a) GDPR, and Art. 9(2)(a) GDPR for heart rate), which you can withdraw with the "Help improve fall detection" switch; our legitimate interests (for example, holding third parties' details you enter, alerting your emergency contacts, improving fall detection for accounts created before November 5, 2026 that have not made a choice, securing the Service, and understanding how it is used); the protection of vital interests when an emergency alert goes out; and compliance with legal obligations (for example, tax record keeping). Where we rely on consent, you may withdraw it at any time through your device or in-app settings, without affecting the lawfulness of processing before withdrawal. Where we rely on legitimate interests, you may object at any time on grounds relating to your particular situation.
5. How We Share Information
We do not sell your personal information, and we do not share it for cross-context behavioral advertising. We share it with the people you share data with or add as emergency contacts, and with the service providers who help us operate the Service, each acting on our behalf and under contractual confidentiality and data-protection obligations:
- Vercel: hosting of this website and the app's server.
- Prisma: database hosting.
- Amazon Web Services: encrypted, private storage of photos, documents and ride files, and training of the fall-detection model, in Frankfurt, Germany. Files are never public and are only served through short-lived signed links.
- Clerk: sign-up, sign-in and account management.
- Twilio: text messages and phone calls to your emergency contacts.
- Upstash: timing of emergency alert escalation.
- OneSignal: push notifications and emails.
- PostHog: product analytics, crash and error reports, app performance data and feature switches (hosted in the EU).
- Axiom: technical server and app logs.
- RevenueCat, together with the Apple App Store and Google Play: subscription and purchase management.
- OpenAI: AI-assisted features.
- Mapbox: address search and satellite maps.
- OpenStreetMap: standard map tiles.
- Open-Meteo: weather forecasts.
We may also disclose information if required by law, to protect the rights, safety, or property of HorseGirl or others, or in connection with a merger, acquisition, or sale of assets, in which case we will require the recipient to honor this Privacy Policy or provide comparable protection.
6. International Data Transfers
We primarily store your data in the European Union (our file storage is located in Frankfurt, Germany). Some of our service providers listed above are based in, or process data in, the United States, the United Kingdom, Switzerland, or other countries outside your own. For the UK and Switzerland, the European Commission has issued adequacy decisions. For US providers, we rely on their certification under the EU-U.S. Data Privacy Framework or, where they are not certified, on the European Commission's Standard Contractual Clauses. You can ask us for a copy of these safeguards.
7. Data Retention
We retain your information for as long as your account is active or as needed to provide the Service. If you delete your account, we delete your rider profile, emergency contacts and safety data, alarm recordings, and notifications, and we delete your workspace data (horses, tasks, rides, health and training records, and related files) once no other member remains on that workspace. Pseudonymised training data already used for the fall-detection model is kept for as long as the model trained on it is in use. Some information may persist for a limited period in encrypted backups before it is permanently purged, and we may retain limited records where necessary to comply with legal obligations (such as tax record keeping), resolve disputes, or enforce our agreements.
8. Your Privacy Rights
European Economic Area, UK, and Switzerland
You may request access to, correction of, deletion of, or a copy of your personal information in a portable format; you may object to or request restriction of certain processing; and you may withdraw consent at any time. You also have the right to lodge a complaint with a data protection authority, in particular the one where you live.
California (CCPA/CPRA)
If you are a California resident, you have the right to know what personal information we collect, use, and disclose; to request deletion or correction of your personal information; and to non-discrimination for exercising these rights. We do not sell or share personal information as those terms are defined under California law, so there is no opt-out to provide. You may submit a request, including through an authorized agent, using the contact details below.
Other jurisdictions
Regardless of where you live, you may contact us using the details below to ask what personal information we hold about you, request that we correct or delete it, or ask questions about this Policy, and we will respond in accordance with applicable law (including, where relevant, Canada's PIPEDA or Brazil's LGPD).
9. Children's Privacy
The Service is meant for people aged 16 and over. Teenagers aged 13 to 15 may only use it with a parent's or guardian's permission. Children under 13 may not use the Service, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us and we will promptly delete it.
10. Security
We use industry-standard safeguards to protect your information, including encryption in transit (TLS), encryption at rest for stored files, private (non-public) file storage accessed only through short-lived signed links, and access controls limiting who can reach your data. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
11. Cookies, Device Storage, and Permissions
This website uses only the minimal cookies or local storage needed for it to function; we do not use cookies for cross-site advertising or tracking. Because there is no common industry standard for responding to browser “Do Not Track” signals, we do not currently respond to them differently.
The App stores your data in a local database on your device so it works without a connection, and removes your account's local data when you sign out. It only asks for a permission (location, including in the background; motion and fitness; camera; photos; contacts; Bluetooth; Apple Health or Health Connect; notifications) when you use a feature that needs it. You can refuse or revoke any permission in your device settings; the rest of the App keeps working.
12. Automated Decision-Making
We do not make decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. Automatic emergency alerts exist only to protect you, and you can switch them off in the App.
13. Changes to This Policy
We may update this Privacy Policy from time to time. We will update the “Last updated” date above, and if a change is material, we will provide additional notice through the App or by email.
14. Contact Us
If you have questions about this Privacy Policy or wish to exercise any of the rights described above, please contact:
Piotr Morawski
Ulmer Straße 1
89264 Weißenhorn
Germany
Email: piotr.morawski@syncflux.io