Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in case of divergence.
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
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 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.4. Responsible vulnerability disclosure
1
Report privately
Use the data protection contact or 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. 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
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.

