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

# Legal bases for processing

> LGPD grounds, GDPR equivalents, and criteria for consent and legitimate interests.

> [!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**
>
> Every purpose needs its own ground. Consent is not blanket authorization: we use contract to deliver requested services, legal obligation for specific duties, and legitimate interests only with necessity and safeguards.

## 1. What a legal basis means

A legal basis authorizes a processing purpose. Brazil’s LGPD (Law 13.709/2018) does not permit selecting a ground merely to bypass a refusal. We assess purpose, context, necessity, expectations, and rights. The same email may support account authentication under contract and an optional communication under consent; each operation needs its own basis and retention. This page complements the [privacy policy](https://legal.doglytdc.dev/en/privacy/privacy-policy.md) and [product inventory](https://legal.doglytdc.dev/en/privacy/data-by-product.md). It does not mean every ground applies simultaneously. Future operations require assessment before implementation.

## 2. Purpose and basis mapping

| Activity | LGPD Article 7 | GDPR Article 6 where applicable | Condition |
| - | - | - | - |
| Account, login, recovery, necessary profile | V — contract | 1(b) — contract | Necessary for the requested relationship. |
| Dashboard, Build Studio, ChatTdc, content sent to AI | V — contract | 1(b) | Execute instructions; no unrestricted secondary use. |
| Hub messages, calls, attachments | V — contract | 1(b) | Respect audiences and permissions. |
| Pay, PIX, balance, withdrawals, reconciliation | V; II for an identified duty | 1(b); 1(c) only for GDPR-recognized obligations | Separate service delivery from documentary duties. |
| Scripts, licenses, CLI, MCP, Discord linking | V — contract | 1(b) | Necessary credentials and IDs; never personal Discord user tokens. |
| Spaces subscriptions and own operations | V — contract | 1(b) | Instructed processing follows the responsible controller’s basis. |
| Partners, attribution, commissions | V — contract | 1(b) | Consent for optional storage where required. |
| Support and troubleshooting | V — contract | 1(b) | Assess litigation records separately. |
| Fraud, abuse, limits, security | IX — legitimate interests; Article 10 | 1(f) | Necessity, proportionality, ability to contest restrictions. |
| Mandatory application access records | II — legal obligation | 1(c) only if valid under GDPR; otherwise assess another appropriate basis | Law 12.965/2014, Article 15: six months for covered providers. |
| Required financial/tax documents and valid orders | II — legal obligation | 1(c), subject to 6(3) | Identify duty, scope, recipient, period; Brazilian law is not automatically an EU basis. |
| Acceptance evidence and legal proceedings | VI — exercise of rights | Generally 1(f), after assessment | Only necessary evidence. |
| Optional cookies and preferences | I — consent | 1(a), plus device-storage rules | Prior choice where required, granular and revocable. |
| Optional push | I — consent | 1(a) | Specific device permission, revocable in settings. |
| Status page and availability protection | IX; II for mandatory logs | 1(f), or 1(c) when requirements are met | Avoid personal data in public incident reports. |

## 3. Contract necessity and legal duties

LGPD Article 7(V) covers contract performance and preliminary steps at your request. It supports authentication, requested features, licensing, and necessary support, not everything commercially convenient. Excessive collection, optional advertising, and unrelated reuse need separate assessment. If essential data is withheld, a feature may not work; essential services must not be conditioned on unrelated optional processing. Your contract with DoglyTdc does not automatically establish a basis for other people’s data you upload.

Article 7(II) requires an identifiable legal or regulatory duty. The Internet Civil Framework (Law 12.965/2014, Article 15) requires six months of application access records in the circumstances it specifies, not all messages, attachments, or prompts. Longer retention needs separate justification. Article 7(VI) supports necessary evidence for judicial, administrative, or arbitration proceedings, with limited access and purpose-linked retention. Authority requests require validity and scope assessment.

Brazil’s Consumer Protection Code (Law 8.078/1990, Article 49) preserves withdrawal rights where applicable. Cancellation and refund records do not authorize removing those rights. GDPR Article 6(1)(c), read with 6(3), requires an obligation under EU or Member State law. A Brazilian duty cannot simply be relabeled as a European legal obligation; overlapping regimes require a separate basis and safeguards assessment.

## 4. Legitimate interests: balancing summary

Fraud prevention and protection of accounts, users, and service availability are concrete legitimate interests. LGPD Article 7(IX) must be read with Article 10 and fundamental rights. These are assessment criteria, not a claim that a formal report has already been approved for every flow.

**1. Identify the interest**

Define the actual risk: unauthorized access, abusive automation, transaction fraud, or service compromise. Security is not a label for unrelated commercial purposes.

**2. Test necessity**

Use relevant signals such as IP, browser, inferred country, device identifier, and request frequency. Limit scope and duration and consider less intrusive alternatives.

**3. Balance effects**

Assess reasonable expectations, interference, consequences of blocks, inference errors, and vulnerable users. An IP address or country alone is not infallible proof of fraud.

**4. Safeguard and reassess**

Limit access, justify retention, protect data, and provide a way to contest restrictions. Reassess changes in technology, purpose, or impact. Reduce or stop processing if individuals’ rights prevail.

Security logs may be kept for up to five years where justified, not automatically because legitimate interests are invoked. You may challenge unlawful processing and request review of solely automated decisions affecting your interests under LGPD Article 20, including fraud and rate-limit restrictions. GDPR Articles 21 and 22 apply when their conditions are met.

## 5. Consent, cookies, and push

Consent must be freely given, informed, unambiguous, and specific. Refusal and withdrawal must be possible; simply visiting is not acceptance. Withdrawal does not invalidate earlier lawful processing but ends future processing relying solely on that consent. We do not retroactively switch grounds simply to defeat withdrawal.

Optional functional cookies, analytics, and marketing depend on applicable choices. Analytics and marketing default to off, and no tools in those categories are currently loaded. Strictly necessary authentication and security technologies are assessed under their essential purpose and applicable rules, not fictional consent. See [cookies](https://legal.doglytdc.dev/en/cookies/cookie-policy.md) and [choices](https://legal.doglytdc.dev/en/cookies/your-choices.md).

Optional push needs specific authorization, revocable through device settings without deleting the account. Revoking push does not end essential in-service communications. Push consent is not blanket marketing consent, and cookie preferences do not replace operating-system permission.

## 6. Sensitive data, children, and limits

Article 7 grounds do not replace LGPD Article 11 requirements for sensitive personal data. Documents and PIX keys need stronger protection without automatically becoming legally sensitive data. App-lock biometrics remain on the device; we do not receive biometric templates. Avoid unnecessary sensitive data in prompts and tickets.

Children’s and adolescents’ data requires their best interests and LGPD Article 14 compliance. Minimum age: \[to be filled: minimum age]. Parental consent is required where the applicable legal condition demands it; no single basis is asserted for every operation involving minors. See [children and adolescents](https://legal.doglytdc.dev/en/privacy/children.md). We do not claim routine reliance on research, vital interests, healthcare, or public-policy grounds without a verified corresponding activity.

## 7. GDPR, transfers, and rights

The GDPR applies under its territorial criteria, including covered offers to people in the European Economic Area or covered monitoring; nationality alone is not decisive. Article 6 equivalents are guidance, not automatic substitutions. Consent, contract, and legitimate interests each have their own requirements.

A processing basis does not itself authorize international transfers: LGPD transfer rules and, where relevant, GDPR Chapter V must also be met. See [transfers](https://legal.doglytdc.dev/en/privacy/international-transfers.md) and [retention](https://legal.doglytdc.dev/en/privacy/retention.md). You may ask which ground applies to your data and exercise [your rights](https://legal.doglytdc.dev/en/privacy/your-rights.md). If a duty prevents erasure, we will explain the data category, reason, and retention criterion, subject to legitimate limits. Responsibility for demonstrating compliance is not transferred to you.

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

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