Apilift Acceptable Use Policy

Effective date: 19 August 2026

This Acceptable Use Policy (AUP) forms part of the Apilift Terms of Service. It applies to the Apilift software, browser extension, website, shared interface library, contributions and reports.

1. Use only what you are authorised to use

Use Apilift only with accounts, systems, browser sessions, data and actions you are legally and contractually authorised to access and automate. Respect third-party product terms, intellectual-property rights, privacy and data-protection duties, confidentiality, employment obligations, access controls and usage limits.

Do not represent that Apilift, an interface or a contribution is approved by a third-party product unless you have documented authority to do so.

2. Prohibited conduct

Do not use Apilift to gain unauthorised access; evade authentication, payment, entitlement, sanctions, geographic or rate controls; distribute malware; exploit vulnerabilities; interfere with a service or another user; conduct credential theft, phishing, surveillance, stalking, harassment, discrimination or fraud; facilitate unlawful trade; violate privacy or confidentiality; send unlawful spam; or create a material risk to safety, rights or infrastructure.

Do not expose passwords, session tokens, private keys, raw authentication headers or unnecessary personal data to an agent, contribution, report or public interface. Do not intentionally defeat Apilift’s privacy preparation, acceptance, contribution, restriction or entitlement mechanisms.

Do not scrape, enumerate, mirror, reconstruct or download the shared library in bulk; use automated access beyond documented product behavior; continue using registry-sourced interfaces after access expires; or resell or redistribute Apilift or shared-library coverage without written permission.

3. Contributions

Contribute only material you have the right to provide and that can lawfully be published and commercially reused under the licence in the Terms. Interface names, descriptions, examples and validation evidence must be accurate to the best of your knowledge and must not include secrets, raw captures, response bodies, concrete account values, personal data that is not strictly necessary, misleading claims or content designed to harm later users.

Automatic privacy preparation reduces risk but does not replace your responsibility to use authorised, suitable data. Report an exposed secret or unlawful contribution immediately and do not reproduce it in the report.

4. Sanctions and restricted locations

You must not use the Service where doing so would cause you or Apilift to violate applicable sanctions, export controls or trade restrictions. You must not conceal your location, ownership or identity to bypass a restriction. We may block countries, persons, organisations, products or transactions when required by a provider, authority or reasonable compliance assessment.

5. Security research

Do not test Apilift or a third-party product in a way that accesses another person’s data, degrades availability, sends destructive requests or violates law. Before security testing Apilift infrastructure, request written permission at security@apilift.dev. A report does not itself authorise continued testing.

6. Reports and notices

Use the structured instructions at apilift.dev/report to report illegal content, exposed secrets, infringement, privacy violations or abusive use of Apilift. Include specific URLs or service and revision identifiers, the reason for the report, supporting facts, your contact details and a good-faith statement. Do not include the secret or harmful content itself when a locator is sufficient.

We can ask for clarification, preserve relevant evidence, notify an affected contributor, restrict access during review and share the report where legally necessary. Knowingly false, abusive or duplicative reports can themselves violate this AUP.

7. Enforcement and appeals

Depending on severity, reliability and urgency, we may reject a contribution; hide an interface or revision; restrict an installation; suspend access; preserve evidence; notify affected parties or providers; or refer conduct to an authority. We consider the nature, context, recurrence, likely harm and available mitigation. Urgent security or legal risks can be restricted without advance notice.

Where legally and practically permitted, we will provide the affected person with the action, principal reason, scope and available appeal route. To appeal, reply to the notice or email support@apilift.dev with the notice identifier, the decision challenged and supporting facts. A person not involved in the original decision will review the appeal where reasonably possible.

Restrictions are restored when the reason is resolved or the decision is reversed. We retain an internal audit record of restrictions, restorations, notices and reasons.