Acceptable use policy

Last updated: 15 July 2026

This policy forms part of our terms of service and sets out how the plaingraph service may and may not be used. Words defined in the terms have the same meaning here.

1. Who this applies to

This policy applies to everyone who uses the service — you, anyone using your account or API keys, any automated system or AI agent acting for you, and any end user of a product you build on the service. You are responsible for making sure they all use the service in line with this policy and the terms.

2. Automated and agent access

The service is built for automated and AI-agent use through the MCP server and the REST API — that is the intended way to use it, not a misuse. In return, you agree that:

• you are responsible for every request made with your account or keys, including requests an agent or automated system makes on your behalf;
• you will stay within your plan's rate limits and metering, and will not use automation, extra accounts, or multiple keys to get around a limit, the watched-set metering, or any access control;
• your client will identify itself honestly and will not impersonate another client, user, or plaingraph itself; and
• your client will back off when the service returns a rate-limit or error response (for example HTTP 429 or 5xx) rather than retry aggressively.

3. Prohibited uses

You must not use the service — or let anyone use it — to:

• break any law that applies to you, including data-protection law;
• unlawfully profile, harass, or discriminate against any individual, or make a legally significant decision about someone by automated means alone where the law requires human involvement;
• resell, redistribute, sublicense, or otherwise make the data available to others as a standalone dataset, feed, or data product, or build, train, or populate a dataset or model that substitutes for or competes with the service (incorporating the output into your own value-added service is allowed — see section 6 of the terms);
• run people-search, or KYC, AML, sanctions, or other compliance-screening decisions off the service — it is a company-fundamentals data product and is neither built nor licensed for screening people;
• scrape, overload, probe, reverse-engineer, or try to break the service or its security, or get around any limit or access control; or
• misrepresent plaingraph's output as a guarantee, as advice, or as your own original source data.

4. Sanctions, export controls, and restricted parties

You confirm that you, and anyone you give access to, are not subject to applicable sanctions (for example under EU, UK, UN, or US measures) and are not on a restricted-party or denied-persons list. You must not use the service, or make it available:

• in breach of any applicable sanctions or export-control law;
• in or for the benefit of a country or territory subject to comprehensive sanctions; or
• to or for the benefit of any person you are prohibited from dealing with under those laws.

We may suspend or refuse access where we reasonably believe it is necessary to comply with sanctions or export-control law.

5. Protecting the service and other users

Do not do anything that degrades, disrupts, or places an unreasonable load on the service for other users, and respect the rate limits and metering that apply to your plan. Keep your account details and API keys secret, and tell us promptly at hello@plaingraph.com if you think a key has been exposed.

6. If this policy is breached

Breaking this policy is a breach of the terms. We may suspend or end your access — or the service as a whole — as set out in the terms, especially to protect the service, other users, or to comply with the law.

7. Contact

Questions about this policy: hello@plaingraph.com.