> ## Documentation Index
> Fetch the complete documentation index at: https://legal.doglytdc.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Personal data by product

> Data, purposes, legal bases, and retention criteria for each DoglyTdc product.

> [!NOTE]
>
> Version 1.0 · Draft · Effective date: \[to be filled: date]

> [!NOTE]
>
> The Portuguese (Brazil) version prevails in case of divergence.

> [!NOTE]
>
> **Plain-language summary**
>
> This 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](https://legal.doglytdc.dev/en/privacy/legal-bases.md).

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](https://legal.doglytdc.dev/en/privacy/retention.md).

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Name, email, photo, profile, recovery details | Authenticate and manage accounts and preferences | Contract | During the account; deletion within 30 days, except justified retention. |
| Projects, contracts, leads, prompts, responses | Run tools and generate responses | Contract; rights for specific disputes | During use and subject to deletion; specific period pending for remaining histories. |
| Prompt Error files and history | Analyze errors submitted by users | Contract | Files: 30 minutes; history: seven days. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Instructions, code, project files | Build and edit requested projects | Contract | During the project; account-deletion rule, except justified retention. |
| Cloned websites | Provide the requested copy in the creation workflow | Contract | 14 days. |
| Execution and error records | Diagnose issues and prevent abuse | Contract for diagnosis; legitimate interests for security | Specific period pending; security logs up to five years where justified. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Identity details, documents, PIX keys | Identify recipients and execute operations | Contract; legal obligation where applicable | During the relationship and financial obligations; specific statutory period pending. |
| Balances, transactions, withdrawals, coupons, commissions | Reconcile operations, requests, and payouts | Contract; legal obligation; rights | Financial history remains after disconnection; specific period pending. |
| Two-factor authentication, device signals, operation records | Protect operations and investigate fraud | Contract for authentication; legitimate interests for antifraud | Active data as necessary; security logs up to five years where justified. |
| Integration credentials and webhook events | Authorize integrations and deliver requested events | Contract | While integration is active; financial records follow separate rules. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Membership, messages, acceptance of terms | Operate communities, channels, communications | Contract; rights to demonstrate acceptance | During use; deletion rule, subject to others’ rights and justified retention. |
| Attachments and call metadata | Deliver files and establish voice/video calls | Contract | Attachments expire automatically; specific metadata period pending. |
| Push token and preferences | Send authorized notifications | Consent for optional push | While authorized and necessary; revocable on the device. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Creator profile, scripts, published content | Publish, distribute, and manage content | Contract | While published or licensed; deletion rule and rights exceptions. |
| Purchases, licenses, payment references | Validate access and address purchases and disputes | Contract; legal obligation; rights | During license and applicable duties; specific period pending. |
| CLI/MCP credentials, requests, usage records | Authenticate calls and apply limits | Contract; legitimate interests for protection | Credentials until revocation; specific record period pending. |
| Necessary Discord IDs and access links | Associate accounts, permissions, services, or lessons | Contract | While the link and service are necessary; purchase-record exceptions. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Members, content, permissions, administrator-submitted data | Host and provide the space | Contract for own operations; controller-determined basis for instructed processing | Under valid instructions and contract; deletion subject to legal exceptions. |
| Subscriptions and access records | Manage membership, billing, security | Contract; legal obligation; legitimate interests for protection | During relationship and applicable duties; specific period pending. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Partner identity and referral reference | Attribute signups and manage the relationship | Contract; consent where optional storage requires it | During relationship and necessary attribution; specific period pending. |
| Commissions, reversals, withdrawal details | Calculate and settle amounts and resolve disputes | Contract; legal obligation; rights | During financial obligations and legal defense needs; specific period pending. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| IP, browser, technical access records | Deliver the page and protect availability | Legitimate interests; legal obligation for records covered by the Internet Civil Framework | Access records: statutory minimum of six months where applicable; other specific periods pending. |
| Operational incident information | Report availability and disruptions | Legitimate interests; contract where related to service | Operational history as necessary; avoid personal data; specific period pending. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Identity, messages, attachments, support history | Respond to and resolve requests | Contract; rights for complaints or disputes | During support and evidence needs; specific period pending. |
| Technical context and error-related records | Investigate errors and incidents | Contract; legitimate interests for security | As needed for investigation; security logs up to five years where justified. |

## 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.

| Data | Purpose | Legal basis | Retention |
| - | - | - | - |
| Session, preferences, offline cache | Maintain access and local operation | Contract; consent for optional preferences where required | Until sign-out, local clearing, or as necessary; cache may require removal on the device. |
| Push token and notification preferences | Deliver authorized notifications | Consent | While authorized and necessary; revocable in system settings. |
| Lock configuration and local biometric verification | Unlock the application on the device | Contract for requested protection | Locally while enabled; biometrics are not sent to DoglyTdc. |
| IP, browser/system, country, antifraud identifier | Detect suspicious access and abuse | Legitimate interests; legal obligation for required records | As needed for protection; security logs up to five years where justified. |

## 12. Sharing and limits of this inventory

Feature delivery may require infrastructure, AI, communications, payment, and antifraud providers. See [subprocessors](https://legal.doglytdc.dev/en/trust/subprocessors.md) and [international transfers](https://legal.doglytdc.dev/en/privacy/international-transfers.md). 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.

> [!TIP]
>
> For access, correction, or deletion, identify the product and consult [your rights](https://legal.doglytdc.dev/en/privacy/your-rights.md). 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](https://legal.doglytdc.dev/en/privacy/contact.md) or email [dogly.tdc@gmail.com](mailto: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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.