Version: 1.0-draft Last Updated: 2026-05-07 Effective Date: 2026-05-07 Canonical Source: This document is the source text for any future acceptable use policy page, onboarding acknowledgement, or enterprise policy appendix.
Read This First
This Acceptable Use Policy explains what users may and may not do with Clerica. We are not trying to make normal use feel risky. We are trying to stop abuse, fraud, interference, and misuse that could harm users, third parties, or the Service itself.
1. Scope
This Policy applies to all use of the Service, whether by individual users, teams, or enterprise customers.
Plain-English Summary
If someone uses Clerica, this policy applies to that use, regardless of account type.
2. Permitted Use
You may use the Service only for lawful, authorized purposes consistent with the Clerica Terms of Service and any applicable customer agreement.
Plain-English Summary
Normal, lawful product use is fine. This section makes that baseline explicit.
3. Prohibited Conduct
You may not use the Service to:
- Violate law, regulation, or third-party rights.
- Attempt unauthorized access to systems, accounts, or data.
- Interfere with Service availability, performance, or security.
- Introduce malware, malicious code, or harmful automation.
- Use the Service for spam, fraud, phishing, impersonation, or deceptive conduct.
- Reverse engineer or probe non-public parts of the Service except as allowed by law.
- Harvest, copy, or republish Service content or outputs in a way that violates law, contract, or third-party rights.
- Use the Service to build or train a competing service from protected non-public materials or internal outputs where such use is not authorized.
Plain-English Summary
This is the core anti-abuse list. It exists so we can stop clearly harmful behavior before it damages the product or other people.
4. Third-Party Content and Rights
Because Clerica interacts with third-party policy materials and related content, users must respect copyright, contractual restrictions, and other legal rights relating to that content.
Plain-English Summary
We monitor third-party policies, but that does not mean users get a free pass to misuse third-party content.
5. Security and Testing Restrictions
You may not attempt to bypass security controls, scan for vulnerabilities in production systems without authorization, or test the Service in a way that could degrade performance or expose data.
Plain-English Summary
Security research should be coordinated, not improvised against live systems.
6. Fair Use of Product Resources
You may not use the Service in a way that places unreasonable load on infrastructure, circumvents usage limits, or undermines plan-based restrictions.
Plain-English Summary
We need the platform to remain usable for everyone, so users cannot treat shared resources like they are unlimited.
7. Enterprise and Team Responsibility
If you administer a team or enterprise account, you are responsible for making reasonable efforts to ensure your users comply with this Policy.
Plain-English Summary
Admins do not need to police every click, but they do need to manage access responsibly.
8. Investigation and Enforcement
We may investigate suspected violations of this Policy and may suspend, restrict, or terminate access where necessary to protect the Service, users, third parties, or legal compliance.
Plain-English Summary
This gives us room to act when there is real abuse instead of waiting until the damage is done.
9. Relationship to Other Agreements
This Policy supplements, and does not replace, the Clerica Terms of Service, Privacy Policy, and any applicable customer agreements.
Plain-English Summary
This is one layer of the rules, not the only one.
10. Changes to This Policy
We may update this Policy from time to time. Non-material updates may take effect upon posting. Material changes will be communicated through reasonable channels.
Plain-English Summary
If we need to tighten or clarify use restrictions later, we will communicate those updates clearly.
11. Contact
Questions about this Policy can be sent to legal@clerica.io.
Plain-English Summary
If a user is unsure whether something is allowed, asking first is better than guessing wrong.