Skip to content

Account security and acceptable use

Customer access is scoped to the authenticated account and its active rentals. Protect every access credential and use aimlib only for lawful, authorized activity under the applicable agreement.

Credential handling

The following values grant access and must be treated as secrets:

  • Customer API keys.
  • Credential-bearing proxy URLs.
  • Browser connect_token values and authenticated connection URLs.

Store them in a secret manager or environment variable. Never place them in source control, support screenshots, browser content, URLs, analytics, or logs. Revoke a customer API key if it may have been exposed and retrieve current proxy credentials after a rental is reprovisioned.

Supported use

Use the documented customer API and SDK for your integration. Availability and limits can vary by account, rental, and service plan; values returned by the API take precedence over examples. Contact support before relying on a capability that is not part of the published customer interface.

Operational records

aimlib may retain operational and security records needed to provide the service, investigate incidents, and enforce the applicable agreement. Access and retention are governed by that agreement and aimlib's privacy terms. Contact support for questions about the terms attached to your account.

Customer responsibilities

  • Access only systems and data you are authorized to use.
  • Follow site terms, privacy law, and applicable anti-abuse rules.
  • Do not interfere with the service, other customers, or third-party systems.
  • Stop sessions promptly and keep dependencies current.
  • Report suspected account or credential failures through support.

Reporting a security issue

Create a support ticket with the approximate time, rental or session ID if available, and a concise description. Do not include secrets, personal data, or exploit payloads in the first message. Support will provide a safer channel when sensitive evidence is required.