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

# Children, teenagers, and guardians

> Best interests, parental consent, underage accounts, and school Workspaces.

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

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

> [!NOTE]
>
> **Plain-language summary:** The minimum age remains to be completed. Children and teenagers require special protection. For children under 12, specific, prominent parental consent is the general rule, subject to applicable legal exceptions.

## 1. Minimum age and scope

**Minimum age: \[to be filled: minimum age].** This draft does not infer an age or authorize accounts below an unpublished threshold. The requirement must be completed and clearly presented. Product rules and legal requirements also matter. Read the [Privacy Policy](https://legal.doglytdc.dev/en/privacy/privacy-policy.md). This page is not a request to submit children’s identity documents or unnecessary family data.

## 2. Best interests under LGPD Article 14

Processing children’s and teenagers’ data must serve their best interests. Consider development, safety, privacy, benefits, risks, and context. Adult permission alone does not make every use appropriate. Information must be simple, clear, accessible, and suitable for the child’s characteristics and understanding. Participation in games, applications, or other activities must not require more personal information than strictly necessary.

## 3. Under-12 parental consent

The under-12 reference follows Brazil’s child/adolescent distinction; it is not a confirmed platform minimum age. As a general rule under LGPD Article 14, processing children’s data requires specific and prominent consent from at least one parent or legal guardian, subject to applicable legal provisions and interpretations. Consent must cover explained purposes, not all future uses. Reasonable efforts must verify parental authorization without disproportionate document collection. We do not claim a universal implemented age or parental-verification system.

Article 14 allows collection without that consent when necessary to contact a parent or guardian, used once without storage, or for protection of the child; in neither case may those data be passed to a third party without the consent required by that provision. These exceptions do not authorize unrestricted commercial use. Other potentially applicable legal bases require assessment under the LGPD and ANPD interpretation, always prioritizing best interests.

## 4. Teenagers and higher-exposure features

Teenagers also receive Article 14 protection. The absence of the identical child-consent rule does not remove the need for an appropriate basis, capacity assessment, and risk safeguards. Contracting and payment features may require adult participation under applicable law.

Messages, calls, public posts, AI prompts, and integrations may reveal school, routines, location, or family details. Avoid publishing documents and sensitive data in shared channels. Guardians and educators should guide use without assuming continuous platform monitoring or automatic detection of all harmful content.

## 5. Accounts below the permitted age

If an account appears below the applicable minimum age or lacks required conditions, we assess the case with priority to protection. Features may be limited or access suspended while age, authorization, and context are clarified. Where necessary and safe, proportionate confirmation may be sought from a guardian or organization.

If use cannot be regularized under the age requirement and law, the account may be closed and data removed or anonymized, subject to lawful retention. A claim of guardianship does not automatically entitle an adult to account contents; authority and safety must be verified. Never ask a child to post credentials or documents publicly.

## 6. School Workspaces

**The school is responsible for obtaining and documenting necessary parental or guardian consents**, where required, and informing students and families. A teacher’s invitation or creation of a Workspace does not prove consent. Schools must assess educational purpose, necessary data, authorized participants, optional features, and withdrawal arrangements before including students.

School decisions do not remove DoglyTdc’s own legal obligations. Roles depend on the operation, and requests should reach the responsible party with cooperation where needed. Schools do not assume every platform liability through this page. Administrators should review invitations, access, public exposure of student lists, and permissions when a student leaves.

## 7. Requests and safety reports

Contact **[dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com)** or dashboard support with the product, issue, and your relationship to the child. Share only what is necessary. Proportionate identity and authority checks may apply; never send passwords or authentication codes. See [your rights](https://legal.doglytdc.dev/en/privacy/your-rights.md) and [retention](https://legal.doglytdc.dev/en/privacy/retention.md) for access, correction, withdrawal, and deletion, including lawful exceptions.

Do not resend intimate or potentially illegal material to prove a report. Describe its location through a private channel. In immediate danger, contact emergency services or competent authorities; support tickets do not replace urgent protective assistance.

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

## 9. Contact

For questions or requests, use the [data protection contact](https://legal.doglytdc.dev/en/privacy/contact.md), email **[dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com)**, or open a dashboard support ticket. Share only necessary information, never passwords or authentication codes.


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