Acceptable use

Use the system lawfully, safely, and without degrading it for others.

This Acceptable Use Policy applies to Last Land websites, products, accounts, APIs, and related technical services. It supplements the Terms of Service and product-specific agreements.

Read the terms Security reporting

Effective 11 July 2026

Permission and impact both matter.

An action can be unacceptable when it exceeds authorization, harms another person, or materially disrupts the service—even if the technique is otherwise common.

If you are unsure whether security testing is permitted, ask before testing. Public availability is not authorization.

Prohibited uses

Do not cross another person's rights or the service boundary.

Examples are illustrative rather than exhaustive. Conduct with the same purpose or effect may also violate this policy.

Illegal or harmful activity

Do not use a service to violate law, facilitate violence, exploit people, distribute unlawful material, or create a credible risk of harm.

Unauthorized access

Do not bypass authentication, probe another user's account, obtain credentials, or access data or systems without permission.

Malicious code or traffic

Do not deliver malware, destructive payloads, denial-of-service traffic, or automation intended to degrade or evade controls.

Resource abuse

Do not consume disproportionate capacity, scrape against instructions, circumvent rate limits, or interfere with dependable service for others.

Deception and impersonation

Do not misrepresent identity or authority, manipulate people into revealing secrets, or present false affiliation with Last Land or another party.

Rights and privacy violations

Do not upload or distribute material that unlawfully infringes intellectual-property, confidentiality, publicity, or privacy rights.

Automated and technical access

Automation must remain authorized, identifiable, and proportionate.

APIs, agents, and scripts

Use documented interfaces and credentials assigned to you. Respect applicable rate limits, access scopes, robots instructions, and product restrictions. Do not rotate identities or infrastructure to evade a limit or suspension.

Content and data collection

Do not systematically extract protected, personal, licensed, or non-public data without permission. Collection that is technically possible may still violate a contract, intellectual-property right, privacy obligation, or this policy.

Security research

Good-faith research must stay within the responsible-disclosure guidance. Use your own account and test data, avoid service disruption, stop when you encounter another person's data, and report the issue privately.

Shared responsibility

You are responsible for activity under credentials and integrations you control. Protect access tokens, remove access that is no longer needed, and tell us promptly when a credential or account may be compromised.

Do not test availability with denial-of-service or destructive techniques.

Load testing, stress testing, social engineering, physical intrusion, and testing third-party providers require prior written authorization from the party that owns the affected system.

Enforcement

Response is based on risk, evidence, and the need to protect the service.

We may investigate suspected violations and request information needed to understand scope and impact.

We may limit, suspend, or terminate access when necessary to protect people, data, infrastructure, or legal obligations.

Where practical and safe, we may provide notice and an opportunity to correct lower-risk conduct before stronger action.

We may preserve relevant records and cooperate with affected parties or lawful authorities when required or appropriate.

A restriction under this policy does not prevent other remedies available under an agreement or applicable law.

Questions and reports

Use the right channel for the issue you are reporting.

Policy question

Ask about a planned use before committing people or infrastructure.

Contact Last Land

Security issue

Use responsible disclosure for vulnerabilities or exposed credentials.

Read security guidance

Harmful activity

Report the URL, account, time, and nature of the suspected violation without repeating harmful content.

Open support guidance

Before you automate or test

If authorization is unclear, pause and ask.

A short scope discussion is safer than an assumption about access, load, data rights, or security testing.

Ask about permitted use Terms of service