Headroom

PRIVACY

Your data stays yours.

This policy explains what Headroom collects, why we need it, and the choices your organization has. Effective September 3, 2026.

Who we are

Headroom is operated by [COMPANY LEGAL NAME], located at [COMPANY ADDRESS]. In this policy, “Headroom,” “we,” and “us” refer to that company.

What we collect

We store account details from Google or Microsoft sign-in, including your name, email, provider identifier, organization, and role. We do not receive your Google or Microsoft password.

Your organization may upload supply-chain data such as parts, bills of material, demand, inventory, suppliers, orders, forecasts, communications, and integration records. We also keep product usage, agent activity, approvals, audit records, and support messages.

Stripe handles payment-card details. We receive billing identifiers, plan status, seat count, invoices, and payment status, but not full card numbers.

How we use data

We use data to provide, secure, support, and improve Headroom; authenticate users; operate forecasting and governed workflows; process billing; prevent abuse; and meet legal obligations. We do not sell customer data or use it for advertising.

Advisory AI features

When an authorized user invokes an advisory feature, the minimum relevant context may be sent to third-party language-model providers. Models advise; deterministic software makes quantities and policy decisions. Headroom does not use customer data to train models, and uses provider business or API terms that prohibit training on submitted customer data.

Service providers

We use service providers for cloud hosting, database and authentication, billing, and advisory language models. Current categories include Google and Microsoft for sign-in, Stripe for billing, and third-party LLM providers for requested advisory features. They process data only to provide their services to us under their applicable contracts.

Retention and deletion

We retain customer data while an account is active and as needed for security, billing, dispute resolution, and legal compliance. An organization owner may request deletion. After we verify authority, we delete or de-identify customer data from active systems and allow protected backups to expire on their normal schedule, except where law requires retention.

Security and choices

We use tenant isolation, role-based access, encryption in transit, audit logs, and approval guardrails. No system is risk-free. Organization owners control membership and may ask to access, correct, export, or delete their organization's data.

Changes and contact

We may update this policy as Headroom changes. We will post the revised date and provide additional notice when a change materially affects your rights.

Privacy questions and requests may be sent to [PRIVACY CONTACT EMAIL]. This policy is interpreted under [GOVERNING LAW].