Data controller for the HAVYT service:
Daniel Denis Golaszewski (operating as "HAVYT"), self-employed professional (autónomo) established in Spain.
NIF: Z3964150J · VAT/NIF-IVA (ROI): ESZ3964150J
Address: Avinguda d'Alexandre Rosselló 15, 6 D, 07002 Palma de Mallorca, Illes Balears, Spain.
Email: support@havyt.app
This policy supplements our Privacy Policy (which describes all processing, legal bases and your other GDPR rights) and the Terms & Conditions.
2.1 Delete Account. Requests deletion of your account and the covered live data described in Section 3. Backup expiry, retained records and third-party copies are explained below.
2.2 Restart Onboarding. Reopens setup so you can update your profile and plan. It keeps your recorded history and is not an account-deletion or health-consent withdrawal request.
Both are available in the app: Settings → Account.
3.1 How it works. Deletion requires re-authentication (you must confirm your password) so nobody can wipe your account from an unlocked phone. It then runs a catalog-driven hard-delete server-side, followed by an automated verification step that checks no user rows remain.
3.2 What is erased — everything, including:
The deletion process uses a maintained catalog of account-linked records and storage locations. New features must be reviewed for inclusion; this is not a fixed table count or a claim that every future feature is covered automatically.
3.3 Cycle and pregnancy/postpartum records are included in deletion from live HAVYT systems. Restricted backup and provider copies follow the limits described in Sections 5–7; live deletion is not a promise of immediate erasure of every residual copy.
3.4 Wearable connections. HAVYT no longer offers a direct Oura, WHOOP or Huawei Health connection. If you made one in an earlier version, deletion removes any access token we still hold, which cuts off our access. We recommend you also revoke HAVYT's access inside the provider's own app or account settings (and in iOS Settings → Health → Data Access & Devices for Apple Health) — that revocation happens on their side and only you can do it.
We keep the minimum set of records that the law requires or that a legitimate, documented interest justifies (GDPR Art. 17(3)):
| What | Why | How long |
|---|---|---|
| Admin audit log (a record that a deletion was requested and executed, and security-relevant admin actions) | Security, accountability, proof of erasure | For the applicable statutory limitation periods under Spanish law |
| Tax and billing records (AI-credit purchase/revenue events; Apple holds the actual payment records) | Legal obligation — Spanish tax and commercial retention | The statutory retention periods under Spanish tax and commercial law |
| Anonymized references — your invite codes are dissociated, your contributions to the shared food database (e.g. products you added) are kept with authorship nulled, support email thread subjects may be kept with your identifiers removed | Keeping shared/aggregate systems consistent without identifying you | Indefinite (no longer personal data once anonymized) |
Nothing in the retained set includes your health logs, photos, chat content or metrics.
Deleting your account removes account-linked legal acceptances, health-consent records, event-saving consents and newsletter-consent history from the live database. This policy does not claim that those records are all kept after account deletion. A separately applicable legal retention obligation applies only to the particular record it covers; it does not permit blanket retention of your health logs, photos or conversations. Newsletter withdrawal suppresses the subscription independently. Residual backup copies are covered by Section 5.
Our current managed database-backup configuration provides seven days of daily physical-backup history in the Ireland (eu-west-1) region; point-in-time recovery is not enabled. This describes database snapshots, not a guarantee that every residual provider copy is erased at exactly seven days. Database backups contain Storage metadata, not uploaded object files. Deleted data may remain in restricted disaster-recovery backups until the relevant copies expire. Restored data must remain out of normal service until later withdrawals, deletions and newsletter suppression have been reconciled. An older snapshot does not grant permission to reuse erased data or restart marketing. Deletion from live systems and backup expiry are separate steps.
Be aware of the limits — deletion removes data from our systems:
If you can't use the in-app flow (lost device, can't sign in), email support@havyt.app from your registered address, or provide enough information for us to verify you are the account holder. We will verify identity, then perform the same deletion, and confirm to you when it is done — at the latest within one month (GDPR Art. 12(3)).
Deletion is one of several GDPR rights (access, rectification, restriction, portability, objection, withdrawal of consent). These, and your right to complain to the Agencia Española de Protección de Datos (AEPD, www.aepd.es) or your local supervisory authority, are described in our Privacy Policy.
We may update this policy as the product or the law changes. Material changes are notified in-app and versioned through our legal-acceptance system (see the Terms & Conditions, Section 4).
HAVYT — Daniel Denis Golaszewski (autónomo, Spain)
NIF: Z3964150J · VAT/NIF-IVA (ROI): ESZ3964150J
Address: Avinguda d'Alexandre Rosselló 15, 6 D, 07002 Palma de Mallorca, Illes Balears, Spain.
Email: support@havyt.app