1. Right to erasure
You can request erasure where provided by the GDPR. The Beta offers JSON export and deletion in authenticated Settings; uninstalling the app or sending credentials to the operator is not required.
2. How to request deletion
- Export: Settings → “Esporta i tuoi dati”,
/api/account/export. JSON includes account and interaction records, not passwords or MFA secrets. It is not a complete photo, key or local private-history archive. Schema 22 also implements owner-authorized private photo export; its controls are available to the authenticated account. Users are not given access to the operator’s Drive. Its message list selects the historical body field, empty for new encrypted messages; decrypted text and complete envelopes are not exported. Contact the controller for further access/portability requests. - Deletion: Settings → “Elimina il mio account”, confirm password and MFA code if enabled. Never send credentials or codes to the operator.
- Email: contact zaditalialibera@zulianarchitetturadigitale.eu with username and request, avoiding unnecessary data. Proportionate ownership verification may be needed.
3. What happens to content
Once authenticated, the operation disables the account and revokes sessions. Cleanup removes media in bounded batches and then the user; database relationships remove associated posts, comments, relationships and conversations. Incomplete cleanup returns “deletion_pending” for maintenance retries. This is not confirmation that deletion is complete or a maximum completion time.
Reports, decisions, appeals and audits can remain with user links nulled and other text/references still present; anonymization is not guaranteed. Deleted operational data may survive in backups, exports and recipients' devices. Server deletion does not automatically remove local IndexedDB history/keys or other users' copies. Screenshots and independent publications cannot be guaranteed erased.
4. Active subscriptions
The Beta is free. The Stripe backend and webhook are connected; Support ZAD shows whether new support is available. Planned monthly support is optional and cancellable through personal history in “Sostieni ZAD”. Uninstalling neither cancels renewal nor deletes the account. Before erasing an account the backend reconciles Checkout and recurring support; if it cannot confirm their management, it keeps the request pending rather than falsely declaring deletion complete. Support grants no privileges. Receipts and records needed for applicable duties may be retained separately from the account; retention follows applicable accounting duties and periods with the operator’s accountant.
5. Approved retention and remaining copies
Periods approved on October 21, 2026: moderation cases, decisions and appeals 12 months after final closure; administrative audit 12 months; ordinary technical logs 30 days; support 12 months after closure and privacy requests 24 months after closure. 30-day cycle for new backups after policy activation, with daily backups; temporary restore drills and operational exports at most 7 days after verification. Account cleanup target: within 7 days of a valid request, subject to justified exceptions.
These periods are not all automatically enforced today. Automated controls and manual procedures are described in Privacy section 7 are required. The new policy does not automatically discard historical copies, which require individual review. Immediate erasure of every copy is not promised. Post-snapshot deletions must be reapplied before restored service resumes. The separate deletion ledger, schema 22 restoration and quarantine before restart have been tested. This does not immediately erase every historical copy.
Daily VPS → Google Drive backups are encrypted and restoration has been tested; private operational snapshots without application-level encryption also exist. Access and copies must be minimized; exceptional retention requires documented grounds, duration and review. Initial owner recovery material is neither deleted nor made public. Clearing browser data may lose keys and local history and does not replace account deletion.
6. Handling requests
GDPR rights requests are handled within the periods required by law, generally within one month unless a permitted extension is duly communicated. For assistance: zaditalialibera@zulianarchitetturadigitale.eu.