Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in the event of divergence, subject to mandatory applicable law.
Plain-language summary. APIs, MCP, and CLI can act on your account. Protect credentials, grant only necessary permissions, and review agent requests. Limits and approvals must not be bypassed. A pending request is not a completed operation.

1. Scope and contractual relationship

These terms cover the Pay and Scripts APIs, Model Context Protocol (MCP) connections, and the Scripts command-line interface (CLI). They supplement the Terms of Use, Pay terms, Scripts terms, and Privacy Policy. Technical documentation describes available features, not permission to exceed account rights. Operator: DoglyTdc Team (independent team, no legal entity incorporated yet; contact: dogly.tdc@gmail.com). Minimum age: [to be filled: minimum age]. When connecting on behalf of an organization, you must have authority to authorize data access, resource consumption, and requested actions.

2. Credentials and least privilege

Keys, tokens, and secrets are confidential. Do not expose them in public code, messages, agent instructions, screenshots, third-party-accessible logs, or distributed applications. Pay API credentials must remain server-side, not embedded in browsers or client applications. Store secrets shown only once securely; do not assume they can be recovered. Use separate credentials per integration and grant only required access. Immediately revoke exposed or unused credentials and review permissions when changing staff or vendors. Read permission does not authorize writing, publishing, user administration, or movement of funds. Do not share one account’s credentials to simulate authorized access to another. Scripts credentials limited to one script may provide broad access within that script; do not distribute them to end users as public keys. Session, OAuth, or key authentication depends on the interface and operation. Revocation does not erase data copies already lawfully delivered to an external client.

3. Features and authorization boundaries

Pay supports queries of products, orders, subscriptions, and balances, webhook integrations, and requests for supported actions. Scopes distinguish reading, writing, and resource categories. Withdrawal requests require appropriate permission and in-app confirmation; withdrawals remain subject to staff review. Scripts may support code, branches, commits, releases, backend functions, collections, user management, and AI, subject to scopes and policies. AI use may consume the account holder’s credits. Possessing a key does not transfer rights to code, data, or third-party services.

4. AI agents, identity, and responsibility

Connecting an agent authorizes it to act on your behalf within granted permissions. You are responsible for choosing the client, configuring permissions, giving instructions, and authorizing actions, including publication, data changes, and resource use. This does not exclude statutory responsibilities of DoglyTdc or third parties. Agents may misunderstand instructions or act on malicious content. Review results before production use. An agent name or logo identifies a connection; it does not certify vendor identity, model quality, or a commercial partnership. Scripts MCP identity may be set automatically by the agent or manually by the account holder. Work tools follow configured policies; connection identity, context, and help resources have distinct treatment and may operate without approval to edit scripts. Do not assume every call requires human confirmation.

5. Approvals and sensitive actions

Scripts policies permit always allowing, always asking, or always denying. A tool-specific rule overrides its group rule and the connection default. Automatic permission permits execution without individual confirmation within those boundaries. A Scripts approval applies to the same tool and arguments, within the same connection, once, and is valid for ten minutes. Changed arguments require a new approval. The server may wait up to 25 seconds; after that, a request may remain pending and require a status check or authorized retry. The request summary does not necessarily include complete file contents: review the change context before confirming. In Pay, API or MCP refund and payment-link requests require in-app confirmation. Authorized balance, sales, and product queries may execute immediately. User confirmation and administrative withdrawal review are separate controls. Two-factor authentication continues to apply where required for sensitive operations.
An acknowledged or pending request is not a completed payment, refund, or publication. Check final status before delivery, retrying an action, or recording it as complete.

6. Limits and integration behavior

Additional resource-specific limits apply. These values describe current documentation, not guaranteed reserved capacity. Respect rate-limit responses and waiting periods where provided. Use progressive backoff, queues, caching, and duplicate prevention instead of aggressive retries. Scripts limits must not be assumed to apply to Pay MCP. Scripts CLI connection codes last ten minutes and can be used once. Do not approve unfamiliar codes initiated by others. Check the account and client before authorizing.

7. Acceptable use and no circumvention

Unauthorized data access, testing others’ credentials, exploiting vulnerabilities, distributing malware, spam, and intellectual property infringement are prohibited. Do not use multiple accounts, keys, addresses, or connections to evade limits, blocks, approvals, charges, or antifraud controls. Do not automate human confirmation, fabricate approvals, or present harmless arguments to execute a different action. Do not overload services or try to extract secrets through agent instructions. Technical accessibility does not override law or the acceptable use rules.

8. Webhooks, data, and logs

You are responsible for endpoint security, integration administrators’ access, and copies received. Use HTTPS, verify notification signatures and freshness under each product’s documentation, and avoid duplicate processing. A notification alone does not replace necessary transaction-state checks. Do not transfer personal data to external clients without an appropriate purpose and legal basis. Brazil’s LGPD, Law 13,709/2018, and the GDPR apply where relevant to users in the European Economic Area. An external agent may subject data to its provider’s terms; review them before connecting. Calls and decisions may generate activity and security logs. Article 15 of Brazil’s Internet Civil Framework, Law 12,965/2014, provides a minimum six-month retention period for application access logs of covered providers. Other retention depends on purpose and applicable obligations; see the retention policy.

9. Availability, technical changes, and revocation

There is no guarantee of uninterrupted availability, fixed latency, or permanent compatibility with every external client. Handle transient failures, retain copies of your data, and test changes before production. Do not retry sensitive actions without checking whether the previous attempt executed. We may correct, version, replace, or discontinue features. Material changes will be communicated through available channels, with migration guidance and reasonable advance notice where possible; urgent security fixes or legal requirements may take immediate effect. Specific contractual deprecation notice period: [to be filled: documented notice period]. Indefinite support for old versions is not presumed. You may revoke credentials and disconnect clients. We may restrict or revoke access for compromise, abuse, contractual breach, security risk, or legal obligations, explaining reasons where permitted. Restriction does not erase existing obligations. Where a consumer relationship applies, rights under Brazil’s CDC, Law 8,078/1990, including article 49 in legally applicable circumstances, remain protected. Non-excludable liabilities remain unaffected.

10. How we notify you of changes

We will publish new versions in this Trust Center with their effective dates. Material changes will be communicated through available channels, with reasonable advance notice where possible. Urgent security or legal measures may take immediate effect. Changes will not apply retroactively to remove accrued rights or restrict mandatory rights.

11. Contact and questions

Use dashboard support tickets for operational issues or email dogly.tdc@gmail.com. For privacy, rights, and the data protection contact, see Data protection contact. Do not send passwords, authentication codes, or integration secrets. Brazilian law governs these terms, subject to mandatory rules applicable in other jurisdictions. Venue: [to be filled: forum city], without prejudice to consumers’ legally protected venue rights.