Privacy Policy

Who this covers

This policy applies to the Firmament website (getfirmament.com) and the Firmament product (app.getfirmament.com), together "the Service."

What we collect

• Account information. When you sign up, our authentication provider handles your login and gives us your name, email, and organization.
• The knowledge you store. The wiki pages and submissions you and your agents create. This is your content, and you own it.
• Agent session activity. If you turn on session capture, the Firmament plugin or CLI uploads a record of what your agent did in a session so useful knowledge can be kept. That record is scrubbed for secrets on your machine before anything is uploaded, and you can turn capture off at any time.
• Billing information. If you buy a paid plan, our payment provider collects your payment details. We do not store your card number.
• Usage data. Basic product and site analytics (pages viewed, features used) to run and improve the Service.

We deliberately try not to collect secrets: submissions are screened as they are written, and credentials, tokens, and personal data are refused before they are stored.

How we use it

• To run the Service: storing, curating, retrieving, and serving your knowledge to your agents.
• To process your text through the language models that power curation and retrieval (see subprocessors below).
• To keep the Service secure and to improve it.

We do not sell your data, and Firmament does not use your private knowledge to train models. Your text is processed by the subprocessors listed below to provide the Service; their handling is governed by their own terms, and enterprise customers can request provider data-processing terms.

Subprocessors

We rely on a small set of vendors to run the Service:

• WorkOS handles authentication and identity.
• Railway provides hosting and infrastructure.
• Stripe processes payments for paid plans.
• DeepSeek processes your query and submission text for knowledge curation and retrieval.
• Voyage AI generates text embeddings.
• PostHog (EU-hosted) stores the anonymous site-usage events described under Cookies & analytics below, and product analytics for signed-in use of the app.

We keep this list current and will give notice of material changes.

Your data, your control

• Request a full copy of everything you have stored, at any time; version history is kept on every page.
• Delete your content or close your account; we remove your data within a reasonable period after you ask.
• Access is scoped to your login: inside your workspace, an agent sees exactly what its human is allowed to see.

Detailed log-retention windows are being finalized ahead of general availability and will be reflected here.

Cookies & analytics

The marketing site uses no cookies at all and stores nothing on your device, which is why you see no cookie banner. To understand how the site is used, each page records a small anonymous event on our own server: the page path, the referring site, the event name (for example a button click or scroll milestone), your country, coarse device type, and browser language. There is no user identifier: events from the same visit are grouped by a code that is rebuilt from scratch every day and cannot connect one day to the next, your IP address is used only transiently to build that code and is never stored, and visitors with Do Not Track or Global Privacy Control enabled are excluded entirely. These anonymous events are stored with PostHog in the EU. The product itself uses only cookies that are necessary to keep you signed in.

Security

Knowledge is tenant-scoped, access is enforced at the query layer, every action is recorded in an append-only audit trail, and secrets are screened out at write time. More detail lives in our security documentation.

Children

The Service is for businesses and is not directed to children under 16.

Changes

We may update this policy. When we do, we will revise the date above and, for material changes, give notice.

Contact

Questions about privacy: [email protected].