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

# Subprocessors and external services

> Providers, purposes, data involved and optional integrations.

> [!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.** We use external services to operate our products. Not every provider receives data about every user. Optional integrations depend on your connection or use of the corresponding feature.

## 1. Scope and roles

This list explains services with identified operational integrations. A subprocessor processes data on behalf of another processing party. Not every listed service necessarily has that role: payment providers and connected platforms may act as independent controllers for their own legal duties, fraud prevention and account management. The applicable role depends on the operation and contract, not just this page’s title.

Listing an integration does not mean it runs on every visit, is available on every plan or receives all account data. Features may depend on provider configuration and availability. This list is not blanket authorization for new purposes.

## 2. Services by purpose

Processing locations may vary by contract, infrastructure region and supply chain. Where the region has not been verified, we state **\[to be confirmed]** rather than infer processing location from company headquarters. A service may operate in multiple countries.

| Service | Purpose | Data involved | Where | Product |
| - | - | - | - | - |
| Lovable Cloud / Supabase | Database, authentication, files and server processing | Account, content, files and technical logs | \[to be confirmed] | DoglyTdc, Pay, Hub, Scripts, Spaces |
| Lovable | Service infrastructure and hosting | Requests, IP, processed content and technical logs | \[to be confirmed] | DoglyTdc |
| Cloudflare | TURN connectivity and calls | IP, connection metadata and relayed media traffic | \[to be confirmed] | Hub |
| LiveKit | Voice and video calls | Participant identifiers, room, connection and media | \[to be confirmed] | Hub |
| Firebase Cloud Messaging | Push notifications, when authorized | Device token and notification content | \[to be confirmed] | DoglyTdc, Hub |
| Resend | Authentication and transactional email | Email address, recipient and message content | \[to be confirmed] | DoglyTdc, Pay |
| Cakto | Checkout and payment confirmation | Buyer identification, order and payment status | \[to be confirmed] | DoglyTdc, Scripts |
| Stripe | Checkout and billing management | Buyer identification, order and payment status | \[to be confirmed] | DoglyTdc, Scripts |
| PerfectPay | Receipt of sale and access notifications | Name, email, product and sale status | \[to be confirmed] | DoglyTdc |
| OpenRouter | Model catalogue and optionally configured AI | Technical queries; prompts and context when selected as provider | \[to be confirmed] | DoglyTdc, ChatTdc |
| Perplexity | Business and public-information research | Query, search location and public contact information | \[to be confirmed] | DoglyTdc |
| Lovable AI | Response and content generation | Prompts, context and files included in the request | \[to be confirmed] | DoglyTdc, ChatTdc, Spaces |
| ElevenLabs | Speech synthesis, transcription and voice interaction | Text, authorized audio and session metadata | \[to be confirmed] | DoglyTdc, ChatTdc |
| Firecrawl | Web search and page extraction | Query, URLs and content of requested pages | \[to be confirmed] | DoglyTdc |
| Google | Optional sign-in and Maps queries | Authorized profile data; queries and searched location | \[to be confirmed] | DoglyTdc |
| GitHub | Optional: sign-in and repository connection | Authorized profile, permissions, code and metadata of selected repositories | \[to be confirmed] | DoglyTdc, Scripts |
| Canva | Optional: account connection and design resources | Profile, authorization and requested resources within granted permissions | \[to be confirmed] | DoglyTdc |
| Discord | Optional: bot, support and lessons in connected servers | Identifiers, messages and data needed for the selected support service | \[to be confirmed] | Scripts |
| incident.io | Status page and availability alerts | Technical incident data and public-page requests | \[to be confirmed] | DoglyTdc |
| Modal | Project execution in an isolated environment | Code, files, commands and execution output | \[to be confirmed] | DoglyTdc |
| ProxyCheck | IP-based anti-fraud checks | IP address and proxy or VPN indicators | \[to be confirmed] | DoglyTdc |
| RapidAPI / ExerciseDB | Exercise catalogue queries | Catalogue parameters; no intentional transmission of personal account data | \[to be confirmed] | DoglyTdc |

## 3. Optional integrations and choices

> [!TIP]
>
> GitHub, Canva and Discord apply only when you connect an account, authorize access or use the corresponding feature. Google sign-in is optional. Connected-account permissions do not authorize indiscriminate access to all your resources.

Review requested permissions before connecting, and avoid unnecessary access to repositories, servers or documents. You may revoke authorization at the provider and disconnect where supported. Revocation stops new authorized access but does not automatically erase previously received data or records that must be retained. See [retention](https://legal.doglytdc.dev/en/privacy/retention.md) and [rights](https://legal.doglytdc.dev/en/privacy/your-rights.md).

AI and voice services receive content needed for your selected request. Do not include secrets, excessive information or third-party data without a lawful basis. Audio processing depends on feature use and device permissions. Web-search queries and URLs can reveal personal information even when seeking public information.

Checkout providers process their own pages under their own policies. DoglyTdc does not store payment-card data. Listing a payment provider does not expand Pay functionality. The exercise catalogue does not require personal account data; direct requests to external content can nevertheless expose IP addresses and connection metadata.

## 4. Partner selection and review

Selection and review criteria include suitability for purpose, data minimization, access controls, available security, contractual terms, processing locations and support for rights and incident handling. Review should be proportionate to service risk and data sensitivity, with particular attention to private content, authentication and financial operations. Inclusion is not certification or an independent audit of a provider.

Reviews consider changes in scope, permissions, terms, availability and security information. Material incompatibilities may require restricted use, replacement or suspension. We do not claim an unverified audit schedule, certification or specific agreement. Formal review frequency and responsible owners remain **\[to be filled: supplier governance]**.

## 5. Data protection and transfers

Engaging providers does not remove the obligation to establish purposes, lawful bases and safeguards under Brazil’s LGPD (Law 13,709/2018). Processing concerning people in the European Economic Area that falls within GDPR scope must also satisfy the relevant GDPR requirements, including processor engagement and transfers where applicable. We do not claim all providers operate only in Brazil or offer identical safeguards.

See our [privacy policy](https://legal.doglytdc.dev/en/privacy/privacy-policy.md), [data by product](https://legal.doglytdc.dev/en/privacy/data-by-product.md) and [international transfers](https://legal.doglytdc.dev/en/privacy/international-transfers.md). For a question about a particular recipient, identify the product and activity without sending unnecessary content. Answers depend on the circumstances and may require proportionate identity checks.

## 6. Limits of this list

Independent providers have their own terms; this does not remove DoglyTdc’s legal responsibilities for its own processing. Visiting a third-party page, voluntarily connecting an account and contracted processing are distinct situations. Making a complaint or exercising a right should not require acceptance of incompatible new purposes.

We do not disclose credentials, infrastructure-access details or other users’ content to explain an integration. Unverified contract, region and security information must be clarified before final publication of this draft.

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