Aelyra

Controller: TO BE CHANGED: Aelyra Fitness GmbH, Musterstrasse 12, 10115 Berlin, Germany. Privacy contact: TO BE CHANGED: privacy@aelyra.example.

Supervisory authority: TO BE CHANGED: Berliner Beauftragte fuer Datenschutz und Informationsfreiheit, Alt-Moabit 59-61, 10555 Berlin, Germany. You may also contact the authority responsible for your place of residence or work.

Aelyra processes personal data to provide accounts, runner profiles, training planning, activity import, activity analysis, AI-assisted coaching, social features, support, security, and integrations.

Account data: name, email address, authentication identity, session information, settings, legal acceptances, consent history, and account timestamps. Legal basis: contract and legal compliance.

Runner profile data: birthdate, sex, thresholds, max heart rate, lactate threshold heart rate, critical power, threshold pace, race records, training preferences, profile picture, and similar fitness data. Legal basis: explicit consent for health/fitness processing and contract where needed to provide the service.

Activity and FIT data: uploaded FIT files, file metadata, activity summaries, laps, GPS coordinates, timestamps, heart rate, power, cadence, temperature, altitude, grade, maps, generated previews, analyses, stress metrics, and linked workouts. Legal basis: explicit health/fitness, GPS/location, and raw FIT storage consent.

AI data: when AI is enabled, Aelyra sends minimized training context, plan brief, activity summaries, anchors, and user-provided planning notes to the configured AI provider. Exact route coordinates are not sent to AI unless separately enabled. Legal basis: explicit AI consent and explicit health/fitness consent where health data is included.

AI history: full AI traces and plan request/response payloads are redacted by default. Full AI history is stored only if you enable AI history storage or where otherwise clearly disclosed.

Social data: social profile, display name, bio, city/country, discoverability settings, friends, sharing defaults, activity visibility, comments, likes, direct messages, blocks, reports, moderation cases, and notifications. Legal basis: contract, legitimate interest in safety/moderation, and consent for public sharing where required.

Location privacy: routes and exact start times can reveal sensitive routines and places. Activities are private by default. Public activity sharing and public route sharing require explicit controls.

External provider integrations: if connected, Aelyra stores an encrypted API key, token hint, account or athlete ID, selected sync scopes, remote threshold metadata, and sync state. Depending on enabled scopes, Aelyra may import activities/thresholds or export workouts/activities. Legal basis: user-directed connection settings, explicit consent where required, and contract.

Cookies and local storage: Aelyra uses strictly necessary authentication/session cookies and local browser storage needed for the app. Non-essential analytics or marketing cookies are disabled until consent controls are implemented and enabled by the user.

Logs and security: Aelyra processes request IDs, user IDs, route names, status, timing, and redacted diagnostics to keep the service secure and reliable. Sensitive payloads such as tokens, raw FIT contents, precise coordinates, prompts, and health metrics should not be logged.

Recipients and processors: current or planned recipient categories include hosting/infrastructure, database hosting, object storage, authentication, AI processing, connected external training providers, map/tile providers, email delivery, and payment/app-store providers if later used.

International transfers: some providers may process data outside the EU/EEA. Transfers must rely on appropriate safeguards such as adequacy decisions, Standard Contractual Clauses, or other lawful mechanisms. TO BE CHANGED after vendor review.

Retention: account/profile data is kept until deletion; activities/FIT files until activity or account deletion; export files for a short expiry period; logs typically 30-90 days; AI full traces are off/redacted by default unless enabled; billing records only if paid plans launch and as legally required.

Your rights: subject to legal conditions, you can request access, rectification, erasure, restriction, portability, objection, and withdrawal of consent. You can manage consents, export data, and request account deletion in Privacy & Data.

Consent withdrawal: withdrawal is effective for future processing. Some features stop working if consent is withdrawn. You may separately request deletion of previously processed data unless retention is legally required.

Account deletion: deleting your account removes app database records and associated object-storage artifacts where technically available. Production identity deletion requires privileged server configuration.

Children: Aelyra is not intended for users under 16. We do not knowingly process children's data below the minimum age.

Security: Aelyra uses access controls, encrypted integration secrets, security headers, redacted logging, rate limiting, and deletion controls. No internet service can be guaranteed completely secure.

Changes: material privacy changes will be notified in-app or by email where appropriate, and renewed acceptance/consent will be requested where required.