Acceptable Use Policy

Effective: 22 September 2026 · Last updated: 22 September 2026

This policy is part of the Terms of Service for legivel, operated by Strimium S.R.L. It applies to every use of the editor, the API and the MCP server, whether by you directly or by tools and agents acting under your keys.

1. Lawful use

You may not use legivel to create, convert or distribute content that is unlawful, including:

You must not use the service in breach of applicable sanctions or export-control laws.

2. Remote resources

You warrant that you have the right to use every remote resource (image or other file) referenced in a document. legivel fetches remote resources only on your instruction, holds them in memory for that conversion, and stores none of them. You must not reference resources you are not permitted to use, and must not use the fetcher to probe, overload or attack third-party systems. Details of how our fetcher identifies itself, and how site owners can block it or complain, are on the fetcher page.

3. Seals

You may seal documents only with certificates you own or are authorised to use. You must not use the sealing feature to impersonate another person or organisation, or to misrepresent a document's origin.

4. Service integrity

You must not circumvent metering, plan limits, rate limits or access controls; probe or attack the service's infrastructure; share one account's keys across unrelated organisations to evade plan limits; or resell access without our written agreement. Automated use through the API and MCP server is welcome within your plan's limits.

5. Enforcement

Accounts used to fetch or convert unlawful content are blocked, and abuse reports are acted on. Blocking is a human decision; where the violation is remediable and made in good faith, we will normally contact you first. We cooperate with authorities where legally required.

6. Reporting abuse

Report abuse to report@legivel.com. We answer within two working days. If your report concerns our resource fetcher, include the fetch id from the request's User-Agent header so we can trace the request — see the fetcher page.