Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in the event of divergence.
Plain-language summary: Infrastructure and partners may process data outside Brazil. Transfers need an applicable legal mechanism; we do not claim unverified countries, certifications, or contracts.

1. Scope and possible destinations

Infrastructure and partners may be outside Brazil. Storage, remote access, and service operations can involve other countries even when the interface or customer is Brazilian. This page explains legal criteria, not a confirmed country inventory. Read the Privacy Policy and subprocessors.

2. Operations that may involve transfers

Hosting, storage, authentication, communications, calls, AI, fraud prevention, and payments may involve international infrastructure. The actual flow depends on the feature and choices used; not all providers receive all data. Text and context needed for AI responses may be sent to the generating provider. Optional integrations involve the permissions and purpose selected. Providers may act as processors or independent controllers, especially for payment obligations. Their role must be assessed rather than assumed. Do not submit unnecessary sensitive information or third-party data to prompts and integrations.

3. Processing basis and transfer mechanism

A lawful purpose and processing basis are necessary but do not alone authorize every international transfer. Transfers must fit LGPD Article 33 and applicable ANPD regulations. Accepting general terms is not unrestricted transfer consent. Encryption and a provider’s general compliance statement do not replace a legal mechanism. The country, recipient, data, purpose, and parties’ roles must be assessed. An unverified condition must not be presented as fulfilled simply because this policy has been published.

4. Mechanisms under LGPD Article 33

Available routes include a country or international organization recognized as providing adequate protection, within the scope of the relevant decision. Adequacy is not something we assume for every destination. Other routes include guarantees through specific contractual clauses, standard contractual clauses, binding corporate rules, or legally recognized seals, certificates, and codes of conduct, subject to the applicable requirements. An ordinary commercial contract or technical certificate does not prove these mechanisms are in place. Article 33 also addresses international legal cooperation between public bodies, protection of life or physical safety, ANPD authorization, commitments in international cooperation agreements, and legally specified public-policy or public-service situations. These are not blanket exceptions for routine commercial transfers. Specific, prominent consent may support a transfer when preceded by information about its international nature and clearly distinguished from other purposes. General acceptance or browsing does not supply it. Article 33(IX) also covers necessity for legal or regulatory compliance, a contract or requested preliminary steps, or exercise of rights under its conditions. Necessity must be demonstrated, not equated with convenience.

5. What is not confirmed

This draft does not confirm an exhaustive list of countries, hosting regions, or remote-access locations. Nor does it assert that all providers signed standard clauses, obtained ANPD authorization, or hold a particular certification. Consult subprocessors and ask about your specific flow. Changes of provider or infrastructure may require a new assessment. Missing detail is not permission to transfer without safeguards.

6. Safeguards, GDPR, and your rights

Transfers should respect purpose limits, minimization, appropriate access, security, recipient obligations, and data-subject rights. We do not promise zero risk, immunity from government access, or exclusive Brazilian residence. Transfers do not remove retention limits. Where the GDPR applies, Chapter V also requires an appropriate adequacy decision, safeguard, or strictly applicable derogation. LGPD compliance does not automatically establish GDPR compliance; no unverified European clauses or program participation is claimed. Email dogly.tdc@gmail.com or open a support ticket to ask about recipients, purposes, and safeguards relevant to you. We may verify identity proportionately and protect others’ data and legally protected secrets. Never send passwords or authentication codes. See your rights, including complaints to the ANPD or competent EU authority. Processing abroad does not remove applicable rights.

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

8. Contact

For questions or requests, use the data protection contact, email dogly.tdc@gmail.com, or open a dashboard support ticket. Share only necessary information, never passwords or authentication codes.