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

# Security and responsible disclosure

> Controls, limitations, responsible research and incident response.

> [!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.** Security is an ongoing responsibility, not a promise of zero risk. We use layered controls. Report vulnerabilities privately and never access other people’s data.

## 1. Scope and limits

This overview covers DoglyTdc, Pay, Hub, Scripts and Spaces. Controls depend on the product, operation and device. A control in one workflow does not imply identical coverage everywhere. We do not claim certifications, independent audits, invulnerability, end-to-end encryption or uninterrupted availability. This page is not a penetration-test report.

Security combines technical safeguards, access decisions and responsible use. Content in Spaces or communities may be accessible under the selected visibility settings. Authorized members can copy content they legitimately see. Deletion or access revocation cannot guarantee deletion of third-party copies. Review product rules before publishing confidential information.

## 2. Technical safeguards

| Layer | Measure and limit |
| - | - |
| Transport | Service connections use HTTPS/TLS to protect data in transit. This does not protect a compromised device or content after delivery to its recipient. |
| Stored data | Sensitive fields are encrypted on the server, including personal information and credentials in specific workflows. Infrastructure encryption-at-rest coverage and regions remain \[to be filled: infrastructure confirmation]. We do not claim every file and copy is encrypted identically. |
| Per-user isolation | Authentication, authorization and ownership checks restrict resource access. Shared spaces follow member and administrator permissions; isolation does not mean exclusive access to intentionally shared resources. |
| Sensitive operations | Pay uses TOTP two-factor authentication for sensitive operations covered by its workflows. We do not claim universal enforcement for every operation across every product. |
| Local lock | App PIN and biometrics, when available and configured, add local protection. Availability depends on the device and does not replace server authentication. |
| Abuse prevention | Request limits and security checks reduce abusive automation. They may temporarily restrict use and do not prevent every attack. |
| Anti-fraud | Device, IP, browser and connection signals help identify abuse. A single signal is not conclusive proof of fraud. |

### 2.1. Secrets and integrations

Integration permissions should be limited to what is needed. Never send third-party passwords to support or to receive a lesson. API keys and authorizations can allow actions on your behalf: protect them, revoke them if compromise is suspected and do not publish them in scripts or repositories. Local locks cannot protect an already exposed key.

### 2.2. Your precautions

Use a unique password, keep devices updated, protect your recovery email and enable available controls. Check origin and permissions before authorizing bots, webhooks or integrations. If a device is lost or unauthorized access is suspected, contact support and revoke sessions and integrations where possible. Never share TOTP codes with anyone claiming to be staff.

## 3. Monitoring and availability

Technical logs and security signals support investigation of abuse, failures and suspicious transactions. We do not claim continuous human surveillance, detection of every threat or universal resolution deadlines. Our public [status page](https://status.doglytdc.dev) provides availability and disclosed incident information; it should not expose personal information or exploitable details. Operational status does not establish the absence of privacy incidents.

Application-access logs are retained for the applicable period: Article 15 of Brazil’s Internet Civil Framework (Law 12,965/2014) requires six months for providers meeting its conditions. Other records have their own purposes and periods; this does not justify indefinite retention. See [retention](https://legal.doglytdc.dev/en/privacy/retention.md).

## 4. Responsible vulnerability disclosure

**1. Report privately**

Use the [data protection contact](https://legal.doglytdc.dev/en/privacy/contact.md) or [dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com) with subject “Security — vulnerability”. Identify the product, affected domain, time and time zone, impact and minimum reproduction steps.

**2. Minimize evidence**

Use your own account and synthetic data. Provide minimal evidence with credentials redacted. Do not send databases, other people’s content or evidence requiring further violations.

**3. Stop and coordinate**

If unexpected access occurs, stop, retain only minimal evidence and report it. Arrange a safe channel for sensitive details and coordinate any public disclosure after assessment and mitigation.

### 4.1. Authorized scope

Research must be limited to DoglyTdc services under our control at doglytdc.dev and its subdomains, doglytdc.app and doglytdc.lovable.app, only where actually operated by us. Third-party domains, spaces, external checkouts, provider infrastructure and customer projects are not authorized merely because they connect to the platform. Ask before testing when uncertain. This policy does not grant administrative access or authorize bypassing limits to obtain private content.

### 4.2. Conditional safe harbor

As a responsible-disclosure commitment, we will not pursue legal action against good-faith research complying with this policy and the law: minimal testing on your own account, no harm, no exploitation beyond what is needed to demonstrate the issue, private reporting and cooperation. This conditional protection does not bind third parties, authorities or rights holders and does not authorize unlawful conduct. No reward, employment or payment is promised.

> [!WARNING]
>
> Do not access, copy, change or delete other users’ data. Do not perform denial of service (DoS), load testing, brute force, social engineering, phishing, malware deployment, extortion, persistence or lateral movement. Do not use a vulnerability to move real funds, obtain benefits or disrupt calls and services.

If another person’s data appears accidentally, do not expand the query or disclose it. Report the exposure and await safe-disposal instructions. Demanding payment as a condition of confidentiality is outside this policy. Good-faith technical discussion and criticism are different from threats or continued exploitation.

### 4.3. Response targets

| Stage | Target pending confirmation |
| - | - |
| Acknowledgment | \[to be filled: acknowledgment deadline] |
| Initial triage | \[to be filled: triage deadline] |
| Researcher updates | \[to be filled: update frequency] |
| Remediation | Based on severity, scope and dependencies; \[to be filled: severity-based targets] |

Research targets do not replace statutory incident deadlines. We may request additional information without requiring access to third-party data. Acknowledgment does not confirm a vulnerability. Disclosure decisions must account for affected people’s protection.

## 5. Personal-data incidents

We investigate incident signals, seek to contain unauthorized access, assess affected data and individuals, preserve necessary evidence and reduce recurrence. Response may involve temporary feature restrictions or access revocation. Immediate disclosure of exploitable details during containment may be inappropriate.

Under Article 48 of Brazil’s LGPD (Law 13,709/2018), controllers must notify the ANPD and affected individuals of security incidents that may result in relevant risk or harm, following applicable regulatory criteria and deadlines. Where appropriate, notice addresses the nature of affected data, information about affected individuals, safeguards, risks, reasons for any delay and mitigation or reversal measures. Not every operational error is automatically notifiable, and mandatory notification is not conditional on completing the entire investigation.

Where processing involving people in the European Economic Area falls under GDPR, its separate assessment and notification criteria and deadlines also apply. A status update does not replace required notices to individuals or authorities. Affected people will receive relevant guidance through available channels, without requests for passwords or authentication codes.

## 6. Privacy and transparency

Report information is used to assess issues, respond and meet obligations, with need-based access. Minimal details may be shared with remediation providers or authorities where lawfully justified. We do not publish researchers’ identities as recognition without prior agreement. See the [privacy policy](https://legal.doglytdc.dev/en/privacy/privacy-policy.md) and [external services](https://legal.doglytdc.dev/en/trust/subprocessors.md).

## 7. How we announce changes

We update this page and the [version history](https://legal.doglytdc.dev/en/version-history.md), identifying the version and effective date. Where a material change requires additional notice by law or materially affects your rights, we will use available contact channels as appropriate. We do not promise a fixed notice period that has not been established. Changes do not override legal duties or retroactively legitimize unlawful conduct.

## 8. Contact

Questions, requests and follow-up: [Data protection officer and contact channels](https://legal.doglytdc.dev/en/privacy/contact.md). You may also write to [dogly.tdc@gmail.com](mailto:dogly.tdc@gmail.com). Do not send passwords, authentication codes or unnecessary documents.


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