Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in the event of divergence.
Plain-language summary: Different data categories have different lifetimes. Some records must remain for legal reasons. Unconfirmed periods are explicitly marked rather than invented.

1. Retention criteria

We retain personal data as needed for the purpose, service, legal duties, and lawful defense of rights. An account’s lifetime does not determine every record’s lifetime. Read the Privacy Policy and data by product. Placeholders below identify unresolved details, not an authorization for indefinite retention.

2. Retention table

3. Understanding the periods

File expiry does not mean related history, messages, or security records expire at the same moment. Hub attachment expiry is automatic, but the exact interval remains unconfirmed. Keep lawful copies of important documents in appropriate storage; do not rely on attachments as an archive. Article 15 of Brazil’s Internet Civil Framework, Law 12.965/2014, requires covered providers to retain application access records for at least 6 months under confidentiality and security. It does not require retaining all message or project content. Further lawful preservation needs its own justification. Up to 5 years for security logs is a possible maximum, not a universal minimum for all data. Connect and Pay financial history may remain after disconnection to meet financial obligations. Specific legal periods still require confirmation.

4. Account deletion process

Request deletion in account settings. If you cannot use that option, email dogly.tdc@gmail.com or open a dashboard support ticket. Identify the account and product without sending passwords or authentication codes. Proportionate identity verification may be necessary. We identify the scope and distinguish data eligible for removal or anonymization from records that must remain. Removal or anonymization takes place within 30 days, subject to lawful exceptions. Anonymization must prevent identification under applicable law; merely hiding a name or pseudonymizing a record is not necessarily anonymization. Deletion is different from editing a profile, withdrawing a particular consent, or disconnecting an integration.

5. Exceptions, backups, and external copies

Legal duties, valid preservation orders, or justified defense of rights can prevent immediate deletion of specific records. Retention must remain limited to the necessary data, purpose, and duration. The backup cycle remains [to be filled: backup retention and disposal cycle]. We do not promise immediate rewriting of every backup. Disposal and restoration procedures must respect deletion requests and avoid reintroducing data without a lawful basis; unverified technical details are not presented as implemented guarantees. Independent controllers, especially payment providers, may have their own obligations. See subprocessors. Account deletion cannot automatically recall screenshots, downloaded files, or content copied outside our control. You may ask about retention criteria and request deletion, blocking, or anonymization where available. See your rights; access-response deadlines are separate from account-deletion processing.

6. How we notify you of changes

We will publish an updated version here with its version and effective date. Material changes will be highlighted in the service and, where appropriate, communicated through registered contact details. New purposes requiring consent need a new choice; publishing a policy does not replace consent.

7. Contact

For questions or requests, use the data protection contact, email dogly.tdc@gmail.com, or open a dashboard support ticket. Share only necessary information, never passwords or authentication codes.