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

# Data protection officer and contact

> Privacy channels, rights requests, identity verification, and response periods.

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

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

> [!NOTE]
>
> **Plain-language summary.** Email [dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com) or open a dashboard ticket. Never provide passwords. A complete confirmation or access statement is subject to LGPD article 19’s 15-day period.

## 1. Responsibility and identification

This page provides privacy and rights-request channels. Missing institutional details do not prevent requests or remove the responsible party's obligations.

| Information | Identification |
| - | - |
| Responsible party | DoglyTdc Team (independent team, no legal entity incorporated yet) |
| Correspondence | [dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com) |
| Data protection officer | \[to be filled: officer name] |
| Email | [dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com) |
| Available authenticated channel | Dashboard support tickets |

A data subject is the individual concerned; a controller decides how data is processed. Under Brazil's LGPD, the officer provides a communication channel between the controller, individuals, and Brazil's National Data Protection Authority, ANPD. This page does not confirm a formal appointment whose identification remains pending, overseas representation, or certification.

## 2. Channels and request types

Email **[dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com)** or open a dashboard support ticket. A subject such as “Privacy — data access” helps but is not mandatory. Email remains available if you have no account, cannot sign in, or requested deletion. Do not publish requests in communities, Hub channels, or third-party spaces.

Ask about collection, use, sharing, retention, transfers, suspected exposure, or statutory rights. For billing or technical issues, explain any privacy aspect. A refund request is not automatically an account-deletion request; deletion does not necessarily end statutory retention. The officer helps route communications but does not replace authorities, courts, or external service operators. Identify any third-party space or integration so responsibilities can be assessed without improperly shifting DoglyTdc's obligations.

## 3. What to include

**1. Provide a contact**

Give your name, account email if applicable, and a safe response address. Explain lost access without sending credentials.

**2. Describe the request**

State whether you want confirmation, access, correction, deletion, or sharing information. Legal citations are not required.

**3. Identify the context**

Give the product, approximate period, and necessary ticket or transaction reference. Avoid full conversations or other people's data when a reference is enough.

**4. Explain specific needs**

Mention representation, accessibility needs, or suspected account compromise. Arrange further steps privately.

Do not send identity documents unsolicited. An adequate description and account connection may allow assessment without additional copies. For correction, identify the incorrect and correct information and provide only necessary evidence. Prefer transaction references over complete financial information.

## 4. Identity verification without passwords

Before disclosing data or performing irreversible actions, proportionate identity or authority verification may be necessary. Use the minimum information appropriate to the risk and existing channels such as the account email or authenticated ticket. Being signed in helps but does not resolve every fraud or representation scenario.

> [!WARNING]
>
> DoglyTdc should not ask for passwords, temporary authentication codes, recovery codes, private keys, integration secrets, or remote account access to process a privacy request. Never include them in messages or attachments.

If further evidence is necessary, its purpose, scope, and suitable delivery method should be explained. A complete identity document should not be the automatic requirement where less intrusive evidence suffices; redact irrelevant information where possible. Explain lost access rather than bypassing security or using someone else's account.

Representatives may need proportionate proof of authority. Requests concerning children require assessment of representation and best interests. Minimum age remains \[to be filled: minimum age]; see [children and teenagers](https://legal.doglytdc.dev/en/privacy/children.md).

## 5. Rights and lawful limits

Brazil's LGPD (Law 13,709/2018), particularly articles 18 and 19, provides confirmation, access, correction, and, where legally applicable, anonymization, blocking, or deletion of unnecessary, excessive, or unlawfully processed data. It also provides sharing and consent information, withdrawal, portability subject to regulation and protected commercial and industrial secrets, and other applicable rights.

Rights requests do not require marketing acceptance or a paid plan. Withdrawal does not automatically invalidate earlier processing or prevent processing under another valid basis. Deletion may be limited by legal duties, legal claims, or other authorized grounds. Responses should explain concrete restrictions rather than use generic reasons to refuse everything. See [rights](https://legal.doglytdc.dev/en/privacy/your-rights.md), [legal bases](https://legal.doglytdc.dev/en/privacy/legal-bases.md), and [retention](https://legal.doglytdc.dev/en/privacy/retention.md).

## 6. Response periods and format

| Request or situation | Relevant rule |
| - | - |
| Simplified confirmation or access | Immediately, under LGPD article 19 |
| Clear and complete confirmation or access statement | Within 15 days of the request, under LGPD article 19 |
| Other LGPD rights | Applicable right, regulations, and circumstances determine procedure; 15 days is not universal |
| GDPR request | Generally information on action within one month; extension by up to two further months under article 12(3), with reasons and notice within the first month |

The complete statement should identify data origins, absence of records, criteria used, and processing purposes, subject to commercial and industrial secrets. Data may be supplied electronically by secure and suitable means or in printed form according to the individual's choice and legal requirements. LGPD rights are exercised free of charge.

Identity checks or clarification do not automatically suspend or restart legal periods. If immediate action is impossible, relevant grounds should be communicated under the LGPD. The 15-day statement period is not a promise to erase all data or resolve every commercial complaint within that time.

For European Economic Area users, the GDPR applies when its territorial and material requirements are met. Its identification, communication, rights, and deadline rules require their own assessment rather than replacing all Brazilian procedures with one period.

## 7. Security and follow-up

Keep copies of your request, replies, and ticket reference when available. Prefer supplementing an existing communication to duplicating requests across channels. This page does not promise automatic acknowledgment, continuous staffing, or an unconfirmed dedicated channel.

Request-handling data should be used compatibly with assessment, security, and evidence of compliance, under appropriate grounds and retention. Article 15 of Brazil's Internet Civil Rights Framework (Law 12,965/2014) requires covered application providers to retain application access logs for six months; it does not require indefinite identity-document retention. Consumer rights under the CDC (Law 8,078/1990), including article 49 where applicable, remain separate from data-access procedures.

## 8. If the answer does not resolve your request

Ask for clarification, identify the unresolved issue, and refer to the earlier reply. You may approach ANPD under applicable procedures, other competent bodies, or courts without waiving rights by using these channels. Where GDPR applies, supervisory-authority complaints and judicial remedies remain available. This page does not generally require exhausting internal steps before seeking legal protection.

## 9. How we notify you of changes

Officer, channel, or procedure changes should appear here and in the [version history](https://legal.doglytdc.dev/en/version-history.md), with appropriate notice for material changes. Updates should not erase pending requests or turn your contact into consent for another purpose. This edition remains a draft with no completed effective date.

## 10. Contact

Email: **[dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com)**. Support: **dashboard tickets**. Officer: \[to be filled: officer name]. This is the reference page for [Data protection officer and contact](https://legal.doglytdc.dev/en/privacy/contact.md). Read the [Privacy Policy](https://legal.doglytdc.dev/en/privacy/privacy-policy.md) for processing information. Do not send passwords, authentication codes, or excessive attachments.


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