HeapFileAI

Terms

Use HeapFile AI within your permissions and available features.

These terms cover HeapFile AI account access and use. Broader commercial terms, enterprise agreements, or DPAs must be approved separately before a governed rollout.

Access

  • HeapFile AI accounts, downloads, and paid features are provided through the account portal or direct support.
  • Published installers and extensions are distributed through official HeapFile channels under their applicable terms. Repositories and release artifacts remain private except for final customer-facing packages authorized for official distribution; unpublished release artifacts remain restricted.
  • Users are responsible for protecting their device, OS account, browser profiles, and configured provider sessions.

Acceptable use

  • Do not use HeapFile AI to access systems you are not authorized to use.
  • Do not submit secrets, regulated data, or third-party customer data unless your organization has approved that use.
  • Do not redistribute installers, private docs, or repository content without written approval.

Feature availability

  • Feature availability varies by client and platform; use each feature's current setup and status in the product.
  • Paid cloud connectors, team services, and managed automation require current entitlement checks by the relevant service. Local settings and operating-system choices cannot grant paid access.
  • HeapFile does not promise universal OS, mobile, AI-client, connector, or enterprise-compliance parity.

Accounts and billing

  • The account portal manages sign-in, membership, checkout, cancellation, and billing status.
  • Support can help investigate entitlement mismatches, failed payments, cancellation issues, and refund requests.
  • See the refund policy for refund handling.

Security and support

Report security concerns or account problems to admin@heapfile.com. Do not include credentials, API keys, tokens, or private customer records in email. For organization use, request a security-review answer set before rollout.