Security, privacy, and governance as the foundation of trust.
Proprietary technology and a Humans + AI operation under rigorous protection, so your company can adopt AI with confidence.
Your data is never used to train AI.
Your content, your strategies, and your business information are yours. Full stop. We never feed our clients' data into AI models for training. This commitment isn't an internal guideline we could quietly change in a release note. It's a contractual clause on Manycontent's side, and it carries through as a bilateral clause in our contracts with model providers (OpenAI, Anthropic, Google, Meta, and others). If the whole chain doesn't honor the same promise, the promise means nothing. That's why the rule holds from the client's signature all the way to the hyperscaler running the model.
Compliance with LGPD and GDPR.
The operation runs in compliance with LGPD in Brazil and GDPR in Europe, respecting data subject rights in every market we serve. In practice, that means three concrete things. Data generated in a Brazilian operation stays in Brazil and is handled under LGPD principles. Data generated in a European operation stays in the European Union and follows GDPR, including the right to access, correct, and delete personal data. A multi-region enterprise client can run operations across distinct jurisdictions without data crossing borders improperly: the architecture knows where each piece of data was created and where it stays.
How we protect your information.
Governance with major AI providers.
We hold strict contracts with the major AI providers, ensuring the technology's use honors the same privacy commitments we've made to you. Every provider in our chain (model vendors, the hosting hyperscaler, data integrations) goes through contract review, security assessment, and ongoing monitoring. Your operation's environment is never used as an internal benchmark, as fine-tuning data, or as a sample for any provider's product. If a provider changes terms or fails a review, it's removed from the chain. Enterprise clients receive a copy of the due diligence package to run their own internal audit.
Frequently asked questions.
No. Client data is never used to train AI models, with no contractual exception. The clause is bilateral with every provider in our chain (model vendors, hyperscaler, integrations), so the commitment doesn't rest only on what Manycontent controls: it's backed by the contract on each link of the chain.
Yes, with LGPD in Brazil and GDPR in Europe. Data generated in a Brazilian operation stays in Brazil; data generated in a European operation stays in the EU. Data subject rights (access, correction, deletion) are handled through a formal channel, with response times aligned to applicable law. Clients with sensitive data (health, financial, legal) can add extra controls to the operation's design.
Encryption in transit (TLS 1.2 or higher) and at rest (AES-256), role-based access controls (RBAC), audit logs for every access to sensitive data, dedicated environment isolation for enterprise clients, and strict contracts with every provider in the chain. Enterprise clients can activate additional controls in the operation's design: a segregated dedicated environment, bring-your-own encryption key (BYOK), corporate single sign-on (SSO/SAML).
That's the standard process for every enterprise client. Our sales team runs it with a ready due diligence package: documented technical architecture, data protection policy, provider contracts available for review under NDA, an LGPD/GDPR responsibility matrix, and an incident response plan. If your committee requests additional analysis (a pen test, code review, cloud vendor assessment), Manycontent handles it.
An incident response plan with notification to affected clients within 72 hours, as required by LGPD and GDPR. The plan covers immediate containment, scope analysis, structured communication (the relevant authority plus affected data subjects when applicable), remediation, and a public post-mortem when warranted. Enterprise clients get a direct channel to Manycontent's security team for real-time follow-up.