Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in case of divergence.
Plain-language summaryThis inventory explains data by feature. Legal bases depend on purpose, and retention differs by record; where an exact period is unconfirmed, we identify the criterion and the outstanding detail.

1. How to read this inventory

The tables describe processing when you use a feature, not mandatory collection across all products. “Contract” means LGPD Article 7(V); “legal obligation,” Article 7(II); “rights,” Article 7(VI); “legitimate interests,” Article 7(IX); and “consent,” Article 7(I). Consent is reserved for genuine optional choices, not essential service delivery. See legal bases. These periods do not authorize excessive retention. Account deletion generally triggers removal or anonymization within 30 days, subject to justified exceptions. “Specific period pending” means [to be filled: retention period], not unlimited retention. See retention.

2. DoglyTdc dashboard and ChatTdc/AI

The dashboard brings together accounts, projects, and tools. ChatTdc sends text and context needed for a response to AI providers; do not assume automatic anonymization or zero retention. Anyone entering third-party information in contracts or leads must have a basis and minimize that data.

3. Build Studio

Projects may contain code, website content, and instructions. Import only third-party personal data you may legitimately use. Cloned-website retention does not automatically determine retention for every project.

4. Pay

Pay processes wallet, PIX, and BRL and USD balance information. It is not an income or investment product. Withdrawals undergo administrative review. Identity documents and PIX keys receive server-side encryption; disconnecting an integration does not automatically erase financial history.

5. Hub

Communities, channels, and direct messages have different audiences and permissions. Calls use communications infrastructure such as LiveKit and Cloudflare; this does not imply recording. Avoid unnecessary personal information in open channels.

6. Scripts, CLI, MCP, and Discord bot

Scripts supports publication, purchases, licenses, and integration access. CLI and MCP use DoglyTdc access credentials; protect them like passwords. The bot keeps Discord IDs necessary for linking and service delivery, never personal Discord user tokens. Bot credentials and DoglyTdc credentials are not personal Discord user tokens.

7. Spaces

Spaces may be public or private and operated by third parties. Administrators determine their own purposes for submitted data and must provide appropriate notices. DoglyTdc acts as processor when following their instructions, while remaining controller for its own account and security operations.

8. Partners and affiliates

Referral links support conversion attribution and commission calculation. Refunds may require adjusting financial records. A referral code does not grant a partner unrestricted access to buyer data.

9. Status page

The page publishes operational information and incidents through an incident.io integration. It is not intended for publishing customer personal data. External pages are also subject to their operators’ notices.

10. Support tickets

Send only data needed to explain the issue. Do not include passwords, authentication codes, or complete documents unless requested through an appropriate channel. Minimize or redact irrelevant third-party details in attachments.

11. Desktop and mobile applications

Local locking protects the device but does not replace account security. Biometrics remain on the device; DoglyTdc does not receive biometric templates. PIN preferences use a protected representation, not plaintext PIN storage. Optional permissions can be revoked through system settings.

12. Sharing and limits of this inventory

Feature delivery may require infrastructure, AI, communications, payment, and antifraud providers. See subprocessors and international transfers. We do not sell personal data. DoglyTdc does not store card data; checkout partners handle their own pages. Brazil’s Internet Civil Framework (Law 12.965/2014, Article 15) requires six months of application access records for covered providers, not indiscriminate message retention. The LGPD (Law 13.709/2018) requires purpose limitation, necessity, and security. Where the GDPR applies to users in the European Economic Area, its requirements also apply. Cancellation and dispute records may be needed to apply Brazil’s Consumer Protection Code (Law 8.078/1990, Article 49), without restricting consumer rights.
For access, correction, or deletion, identify the product and consult your rights. Do not send credentials or unnecessary third-party data.

13. How we notify you of changes

We will publish updates in this Trust Center with a version and effective date. Material changes will be highlighted in the service and, where appropriate, communicated through registered contact channels. If a new purpose requires consent, we will ask for a new choice before that processing; publishing a policy does not replace consent.

14. Contact

For privacy questions, rights requests, or personal data incidents, visit the privacy contact page or email dogly.tdc@gmail.com. Identify the product and context, without sending passwords, authentication codes, or unnecessary documents. We may request proportionate identity verification before disclosing data or changing an account.