Privacy policy

SoloTrainer.net is operated by Igor Cirlan Trohin, a sole proprietorship at Rue Pré de la Cava 2, 1852 Roche VD, Switzerland. We handle account administration, platform security, support and our own communications. Contact us at contact@solotrainer.net. Our phone number and postal details are also in the legal notice.

Your trainer decides why they collect client information, which questions they ask and how they use your answers. SoloTrainer.net stores and displays those records to provide the tools your trainer uses. The trainer who shared a booking or form link receives the information you submit through it.

Forms, notes and training records can contain sensitive health data, including injuries, health screening answers, bodyweight and symptoms. Before sharing health details, ask your trainer about their privacy notice, the purpose of each question, who can access your answers and how long they keep them. Use the contact channel through which they shared the form or booking link. Contact us if you need help identifying the responsible trainer.

Trainers must have the permissions and legal grounds needed for their use of personal data. This includes any additional requirements for health information and for children or a parent or guardian. Accepting platform terms or submitting a form does not provide blanket consent to marketing or every later use of health information.

• Accounts: name, email, authentication details, language and workspace settings let us create accounts, sign you in and control access.
• Trainer and client records: contact details, notes, health intake, invitations and access relationships let trainers manage their work with clients.
• Training: workouts, exercise choices, logs, sets, reps, weights, progress and notes support coaching and training history.
• Bookings and forms: availability, selected times, guest contact details and submitted answers let trainers receive requests and manage sessions and questionnaires.
• Payments: offers, pack sales, payment status, method labels, receipts, refunds and billing records support purchases and accounting. Stripe handles online payment details; we do not receive full card numbers through checkout.
• Support: messages, attachments and device details you send help us answer questions and handle account or privacy requests. Do not send passwords or full card details.

The website uses authentication cookies to keep you signed in, a language cookie to remember your choice for up to one year, and interface preferences such as the navigation layout. A checkout verification cookie can last up to one day. These serve the feature you use; creating an account does not subscribe you to the newsletter. You can clear site data in your browser, which may sign you out or remove unfinished work.

Form answers are saved in this tab to recover unfinished work. Drafts expire after 24 hours without changes and are cleared when you submit successfully or choose Clear answers. A restored browser tab may also restore its storage. Older form drafts kept across tabs are removed when you visit a form. Free Tools can keep an unfinished calculation in this tab for up to 30 minutes when you leave to sign in and save it. These drafts are separate from answers or results you have submitted.

The mobile app stores session and training data on your device to support loading and unfinished work. Training timers can use local notifications and sounds. The app does not collect microphone recordings.

The production marketing site uses self-hosted Rybbit analytics at st.skilltrees.net to understand visits and use of the site. Free Tools send a limited event when a published tool is calculated, printed, bookmarked or saved, or a save fails. That event contains the tool identifier and action, not the entered values, result, client identity or free-text notes. Loading a script or sending an event also makes a network request to that service.

When error reporting is configured, the Sentry software sends error details to our GlitchTip service. These can include error messages, stack traces, page or request context, browser and device information. We remove request bodies, cookies and most headers, and redact known sensitive values before sending reports. Performance tracing and browser session reporting are disabled. These filters reduce exposure but do not make all diagnostic data anonymous.

Servers and hosting services handle connection details, including IP addresses, to deliver and protect the service. Public bookings, forms and checkout use hashes derived from an IP address to limit abuse. Newsletter request limits use hashes of the IP address and email. Where enabled, our self-hosted Cap service checks a short-lived proof-of-work token to prevent automated submissions.

Signup sends your email address, language, signup source, consent-text version and request time to the configured Plunk email service. It requests a confirmation email and does not create a platform account. New subscribers must confirm through the email link. A signup request record alone is not proof that you confirmed.

Use the unsubscribe link in a newsletter to stop marketing emails. You can also ask us at contact@solotrainer.net. Unsubscribing from marketing is separate from account, security and other service emails.

When a trainer uses an AI feature, the instructions and context for that request are sent to OpenRouter and the selected model provider. Workout generation can include training preferences, bodyweight, persistent client notes, training history and health flags or restrictions. Other AI tools can send the text or files the trainer chooses to use with them.

Workout generation excludes dedicated client name, contact and address fields from its client context. Notes and other free text may still identify someone or contain health information. A recorded health-consent check applies to structured health flags and restrictions; it does not cover every note or training-history field. Trainers must review what they send and have the required permissions.

Requests to the listed supported models ask for zero-data-retention routing. Custom model choices may not include that preference. A routing request is not a guarantee about a provider’s practices; applicable terms and the selected provider determine downstream handling. Ask your trainer which AI features and providers they use with your information.

• Supabase provides authentication, database storage, file storage and server functions for account and product records.
• Stripe processes online payments and connected payment accounts, including the buyer, order and payment information needed for checkout.
• Plunk handles SOLO Minute contacts and confirmation email. Email delivery also uses the delivery provider configured for that service, which can include Amazon SES. Account email uses the provider configured for authentication.
• OpenRouter and the chosen model provider receive optional AI requests, as described above.
• Self-hosted Rybbit, GlitchTip and Cap handle analytics, diagnostics and abuse prevention respectively. Hosting providers handle the infrastructure and connection data for these services and the website.
• Expo and EAS support mobile app builds and updates. Data sent when using a mobile service depends on the feature and configuration.
• Expo, Google Firebase Cloud Messaging and Apple Push Notification service deliver app notifications. When a client finishes a workout, the trainer's notification includes the client's name, the workout name and the opening words of the client's workout note.

The services used depend on the feature and its configuration. A trainer may also share information with services they choose. Ask us for the current recipients, processing countries and transfer safeguards that apply to the SoloTrainer.net services you use. Ask your trainer about their separate services and disclosures. We do not sell personal data.

Account and product records support your account and the trainer’s ongoing work. Retention also depends on support needs, security, accounting obligations and unresolved disputes. Removing access or archiving a client does not erase that client’s history.

Deleting a client login through the mobile app disconnects the login from the trainer’s records; it does not delete the trainer’s client, booking, training or payment history. Contact the trainer about those records, and contact us for account closure or help with a deletion request. Trainer account closure is handled through support.

Accounting vault uploads have a minimum retention through the end of the tenth year after their recorded year. This does not set the retention period for health forms or other client records. Browser draft periods are described above. Contact us about retention for other records, including email, diagnostics and backups, or to request deletion. We assess which records can be erased and which must be retained for a specific obligation or claim.

Contact contact@solotrainer.net to request access, correction, a copy or export, deletion, or account closure. Tell us which account or service your request concerns. We may need to verify your identity before disclosing or changing records. For records controlled by your trainer, contact them directly; we can help route a request.

Depending on the law and processing involved, you may also request restriction, object to processing, or receive portable data. Where processing relies on your consent, you can withdraw it for future processing without affecting the lawfulness of earlier processing. Tell the trainer about consent for their use of your information; contact us about our own use. A withdrawal does not by itself erase records kept on another lawful ground.

You can raise a concern with the Swiss Federal Data Protection and Information Commissioner. Where the GDPR applies, you can also complain to a competent EU/EEA data protection authority, including in your place of residence, work or the alleged infringement. You do not need to contact us first.

For app help, see the support page.