Vipy is operated by Denis.pt, Unipessoal Lda, Estrada Monumental 277, Vila Formosa, Bloco 5, 1E, 9000-250 Funchal, Madeira, Portugal ("we", "us"). Contact: [email protected].
Account data — email, a hashed password or a linked Google/Apple identity, locale, timezone.
Your conversation with the coach — messages, transcribed voice, and any photos you send.
Fitness and health records you log or that we derive from what you tell us — workouts, sets, nutrition, supplements, recovery, body measurements, and, if you connect it, Apple Health data.
Device and usage data needed to operate the service — crash logs, request metadata.
Photo originals are short-lived and deleted shortly after processing. EXIF location/device metadata is stripped on your device before upload. Only a sanitized thumbnail is retained in your journal.
Voice messages are streamed directly to OpenAI for transcription and are not stored by us — we keep only the resulting text transcript. Live voice sessions connect from your device directly to OpenAI over a short-lived credential and never pass through our servers.
Account, billing, security, and device data — to create your account, provide and secure the service, and meet our legal obligations. Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR), our legitimate interest in keeping the service secure and working (Art. 6(1)(f)), and compliance with legal obligations (Art. 6(1)(c)).
Health and fitness data — your workouts, nutrition, body measurements, recovery, symptoms, supplements, and any Apple Health data you connect are special-category health data. We process them only on the basis of your explicit consent (Art. 6(1)(a) together with Art. 9(2)(a) GDPR), which you give through a separate checkbox when you create your account, distinct from your acceptance of these terms. Giving this consent is your choice, not a condition of having a Vipy account: if you decline, you keep your account, and we simply do not process health data — the journal and coaching features that depend on it will not be available to you.
You can withdraw your health-data consent at any time, for the future only — withdrawal does not affect processing that already happened, and it does not require you to delete your account. A self-service control in the app is planned but not yet live. Until it ships, email [email protected] with the subject "Withdraw health data consent". We will stop all health-data processing, delete or irreversibly anonymise your existing health records without undue delay, keep your account and non-health data intact, and confirm to you by email when it is done. This is the same manual process we use today for export and deletion requests (see "Your rights"). Withdrawing consent is free and requires nothing more than that email.
OpenAI, to process your messages, transcriptions, photos, and any Apple Health data you've connected, and generate coaching responses. Our S3-compatible storage provider, to host thumbnails and encrypted backups. We do not sell your data, and we do not share it for advertising.
Your data is processed in the EU and, where our providers operate there, in the United States. Sending your messages, transcripts, photos, and health data to OpenAI for processing involves a transfer outside the EU/EEA.
We use OpenAI's API under OpenAI's published Data Processing Addendum. Under that addendum, OpenAI Ireland Limited is the processor for EEA data, and transfers to the United States are covered by the European Commission's Standard Contractual Clauses (Art. 46(2)(c) GDPR). OpenAI is also self-certified under the EU–US Data Privacy Framework, an adequacy decision under Art. 45 GDPR; the Standard Contractual Clauses apply regardless, so the transfer stays covered even if that framework's status changes. OpenAI's published terms state it does not use API data to train its models.
You can ask us for more detail about these safeguards at [email protected].
Your journal data is kept for as long as your account is active. Raw message logs and AI processing traces are retained only as long as needed for support and debugging, then deleted. Photo originals are deleted shortly after processing — only the sanitized thumbnail stays in your journal. Deleting your account, or withdrawing health-data consent, removes the corresponding data; some encrypted backups may retain a copy for a limited rolling period before being overwritten.
Under GDPR you have the right to: access your data (Art. 15); have inaccurate data corrected (Art. 16); have it deleted (Art. 17); restrict how we process it (Art. 18); receive it in a portable, machine-readable format — data portability (Art. 20); object to processing based on our legitimate interests (Art. 21); and withdraw any consent you've given, at any time, with effect for the future (Art. 7(3)).
Self-service tooling for these requests is planned but not yet live. Until it ships, email [email protected] and we'll handle your request manually, free of charge and within one month; we'll tell you if we need up to two further months for a complex request.
We do not use your data for automated decisions that produce legal or similarly significant effects about you — coaching suggestions are informational and never determine access to any service or benefit.
We have not appointed a Data Protection Officer: given the size of our operation, we are not currently required to under Art. 37 GDPR. Data protection questions go to [email protected].
If you believe we've handled your data unlawfully, you can complain to a supervisory authority (Art. 77 GDPR) — ours is the Comissão Nacional de Protecção de Dados (CNPD), Av. D. Carlos I, 134 — 1º, 1200-651 Lisbon, Portugal, [email protected]. You may instead complain to the authority in your own country of residence.
Certain red-flag health statements (e.g. chest pain, severe difficulty breathing) trigger an automatic safety message directing you to emergency care, independent of the AI's judgment. This check exists to protect you and is not a substitute for medical care.
We'll update this page as the product evolves and note the date of the latest revision here.
Questions about this policy: [email protected].