Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in case of divergence.
Plain-language summary: Do not harm others, commit fraud, intrude into systems or violate rights. Scripts must comply with third-party platform rules. Enforcement can include warnings, removal, suspension or bans, with ticket-based appeals.

1. Scope and definitions

This Policy supplements the Terms of Use across DoglyTdc, ChatTdc, Build Studio, Pay, Hub, Scripts, Spaces and integrations. It protects people and service integrity without prohibiting lawful criticism or competition. Content includes prompts, code, messages, attachments and submitted data. Automation includes programmatic actions by scripts, bots and integrations. Community and integration administrators must act diligently and inform people they manage of applicable rules. Additional community rules cannot authorize unlawful conduct. Delegating an action to a bot, collaborator or alternate account does not make prohibited conduct permissible.

2. Prohibited content and conduct

2.1 Harm to people

Do not make credible threats, stalk, harass, extort, encourage violence or expose personal data to intimidate someone. Child sexual exploitation material, grooming and nonconsensual intimate material are prohibited. Do not promote unlawful discrimination or violence against protected groups. AI may not be used to facilitate these activities, fabricate harmful evidence or impersonate someone for fraud. Context and lawful permissions matter, but a research or humor label does not authorize real harm.

2.2 Fraud and identity

Phishing, scams, identity misuse, false documents, sham transactions and deceptive communications are prohibited. Do not use Pay to circulate illicit funds, conceal beneficiaries or evade security and withdrawal reviews. Do not manipulate credits, coupons, affiliate arrangements or refunds through deceptive accounts or fabricated purchases. Good-faith payment disputes and exercise of withdrawal rights are not abuse.

2.3 Privacy, intellectual property and communications

Do not disclose confidential information, personal data or protected material without permission or another lawful basis. Do not sell unlawfully obtained databases or extract other users’ private messages or credentials. Spam, deceptive invitations and mass communications that disregard lawful refusals are prohibited. Prospecting tools do not remove transparency or legal-basis obligations. Lawful quotation, criticism and statutory exceptions remain permitted.

3. Security testing and responsible disclosure

A public feature is not authorization to test intrusions. Security testing requires prior authorization within an agreed scope through responsible disclosure.
If normal use reveals a possible vulnerability, stop actions that could expand access and report it by ticket or through the security contact. Obtain permission before active testing; silence is not permission. This Policy does not promise a paid bounty. Do not access other accounts, escalate privileges, bypass authentication, use leaked credentials or extract information to prove a finding. Malware, ransomware, password harvesting, denial-of-service attacks and destructive tests are prohibited. Provide only the minimum evidence needed, protect it and avoid unnecessary personal data or complete secrets. Coordinate public disclosure to avoid additional exposure, without restricting legally protected reports to authorities.

4. Automation, scraping and API limits

Use authorized mechanisms and respect permissions, authentication, displayed limits and the API and MCP rules. API access does not authorize copying the entire service or accessing content outside your account permissions. Do not bypass quotas, blocks, credit metering or access restrictions, including by distributing requests among accounts. Unauthorized scraping of private or authenticated areas, unlawful bulk personal-data collection and rights-infringing extraction that compromises services are prohibited. Do not automate spam, engagement manipulation or resource overload. This Policy sets no universal numerical request rate: the relevant integration and plan limits apply. Contact support before expanding beyond permitted scope. The absence of a technical block is not legal authorization. You are responsible for checking whether scripts are permitted on the sites, games, educational environments and other services where you use them. A DoglyTdc listing, purchase or license is not the destination platform’s permission and does not guarantee protection against sanctions or account loss. Cheating-related tools must comply with the affected platform’s terms. Do not use scripts or lesson orders to evade assessment rules, anti-cheat mechanisms, authentication, payment requirements or access controls. Do not encourage others to violate those rules. Use tools only in environments where you have valid permission. Creators must accurately describe purpose, permissions and risks, without hidden data collection, additional code installation or financial actions. Do not claim a tool is undetectable or officially authorized without verifiable grounds. See the Scripts terms. Discord lesson orders do not authorize improper access; never provide third-party passwords.

6. Reporting and assessment

Report through a ticket with product, context and references needed to locate the issue. Identify immediate risks where possible. Do not redistribute illegal material as evidence or publicly expose people to demand punishment. Personal-data issues may also go to the privacy officer. Assessment considers severity, impact, context, repetition, evidence reliability and opportunities to correct the issue. A report is not automatic proof. Necessary evidence may be preserved for security, legal obligations and claims under the Retention Policy.

7. Enforcement ladder

1

Warning

Notice and guidance to correct conduct where appropriate.
2

Removal

Removal or restriction of problematic content, transactions or integrations.
3

Suspension

Temporary restrictions to contain risk or investigate.
4

Ban

Termination for serious, persistent or safety-incompatible conduct.
Not every stage is required. Serious threats, fraud, child exploitation, security incidents or valid orders may require immediate action. We may restrict only the affected feature where sufficient. Do not evade measures through alternate accounts. Where lawful and feasible, notice will explain the measure, scope and reason sufficiently for a challenge. Details may be withheld to protect reporters, other people’s data, safeguards or protected investigations. Suspicion does not authorize indiscriminate retention of money or automatic loss of mandatory refund rights.

8. Appeals and authorities

Appeal by dashboard ticket, identifying the measure, disputed facts, relevant permission or account compromise and supporting evidence. Do not send unnecessary credentials or third-party documents. Review may uphold, narrow or revoke a measure; no unconfirmed fixed deadline or outcome is promised. Good-faith reporting and exercise of rights are not grounds for retaliation. Deliberately false reports may be abuse. Authority requests are assessed for validity and scope under law and the authority guidance.

9. Applicable law

Brazilian law applies, including the CDC (Law 8.078/1990), LGPD (Law 13.709/2018) and Brazilian Internet Civil Framework (Law 12.965/2014). Article 15 requires covered application providers to retain application access logs confidentially and securely for at least six months. The GDPR applies concerning European Economic Area users when its territorial requirements are met. Mandatory remedies and access to authorities remain protected.

10. How we notify changes

We publish updated versions and effective dates here and communicate material changes through the service or registered contacts, with reasonable notice where feasible. Changes will not retroactively invent a violation, without preventing lawful urgent protective action.

11. Contact

Use dashboard tickets for reports, testing authorization and appeals. General contact: dogly.tdc@gmail.com. For personal-data matters, contact the privacy officer.