Privacy notice

Your local memory, account, and cloud data have separate boundaries.

This notice explains how HeapFile AI handles data. Local memory, account data, support messages, billing events, and optional cloud features are handled separately.

What HeapFile may process

Account details used to sign in, manage membership, and contact support.
Billing and entitlement events handled through the account portal and payment providers.
Support messages, security-review requests, and product feedback you send.
Local app configuration and logs needed to diagnose setup problems when you choose to share them.
Cloud sync, connector evidence, team workspace, or automation data only when those features are explicitly configured and entitled.

What stays local by default

Local memory and local source evidence created by the desktop client stay on the user's device unless a cloud feature is turned on.
Browser sessions and organization connector credentials belong to the user's OS account or chosen provider flow.
HeapFile does not ask users to email passwords, API keys, tokens, private customer files, or other unnecessary sensitive data.

How data is used

Operate account, membership, setup, support, and paid-feature access.
Debug installer, sign-in, entitlement, connector, and security issues.
Improve product reliability and onboarding using feedback and non-secret diagnostic details.
Meet payment, legal, tax, abuse-prevention, and security obligations.

Sharing and providers

HeapFile uses infrastructure, payment, email, and security tooling needed to operate the service.
Connector access is customer-authorized and scoped to the provider and account configured by the user or organization.
HeapFile does not claim universal connector availability or enterprise compliance certification until those flows are deployed and reviewed.

Your choices

You can ask for account help, export/delete help, cancellation, refund review, or a security-review packet by emailing admin@heapfile.com. See the retention, export, and delete page for data-control details.

Do not send secrets or private customer data by email. If support needs diagnostics, send the smallest redacted detail that explains the issue.