Security and privacy

Your pricing can't train somebody else's model.

This is the reason the company exists, so it gets a real page instead of a line in the footer. Here is where your data lives, who can reach it, what we encrypt, and the claims we will not make.

  • AI on hardware we own, Nashville TN
  • No third-party AI provider receives your data
  • Encrypted per company
The whole thesis

Every competitor sends your data to an AI company. We don't.

When another product in this trade quotes a part for you, your cost, your customer and your price go out to OpenAI, Anthropic or Google, get processed on their machines, and come back as an answer. That is how nearly all of it is built, because it is cheap and fast.

Foreman runs its AI on servers Oluri owns and operates in Nashville, Tennessee. Not rented cloud capacity. Hardware in a building. Your financial records, your customer list, your pricing and your email are processed there and are never sent to a third-party AI provider.

It is a slower and more expensive way to build a company. It was chosen on purpose.

Where it runs

One answer, and it does not have footnotes.

  • AI inference: Oluri-owned hardware, Nashville, Tennessee.
  • Your accounting and email data: the same hardware.
  • Third-party AI providers with access: none.
  • Your data used to train any model for anyone else: never.

What we do

Four claims, stated exactly.

These are specific because vague security language is how you get lied to. Each one is a thing you can hold us to.

Credentials

Encrypted at rest, per company

Connector tokens and credentials are encrypted at rest using AES-256-GCM under a key specific to your company. One company's key does not open another company's data.

Storage

Disk-level encryption

The volumes holding customer data are encrypted at the disk level with AES-256-XTS.

Transport

TLS in transit

Data moving between your browser, your connected services and Foreman travels over TLS.

Processing

Inference on company-owned hardware

AI inference runs on hardware Oluri owns. No third-party AI provider receives customer data at any point in that path.


Operational integrity

What happens after Foreman writes to your books.

Most software tells you the write succeeded. That is not the same as the write being correct, and your accounting system is the wrong place to find out later.

Verify-back

Every write is read back and diffed

After each QuickBooks write, the object is read back and compared against what was proposed. A mismatch raises an alarm rather than passing quietly. Idempotency keys make a double-tap a no-op, so a nervous second click cannot create a second invoice.

Journal

Append-only, including the refusals

Every execution and every refusal lands in an append-only journal. The things Foreman declined to do are as auditable as the things it did.

Per company

Sealed to the company and the purpose

Each company's data is sealed under its own key, and both the company and the purpose are cryptographically bound into the seal. One company's data cannot be decrypted in another company's context, before the separate-key guarantee even applies.

Storage

Mirrored as well as encrypted

The volume holding customer data is mirrored across two drives, so a single drive failure is not a data event.

Freshness is measured on outcomes, not on processes. The system watches whether new data actually landed, not whether a job ran. A job that runs is not a job that worked, and the gap between those two is where stale numbers come from.
What we do not claim

The honest part of a security page.

A vendor who will overstate their certifications will overstate other things too, so here is the ledger in the other direction.

  • Foreman is not SOC 2 certified. It is not ISO 27001 certified. It is not PCI certified. Oluri maintains an internal security policy set modeled on the ISO 27001 framework. Modeled on a framework is not the same thing as being audited against it, and we are not going to blur that line on a page where you are deciding whether to trust us with your books.
  • We do not publish a penetration testing cadence, an uptime guarantee, or a 24/7 monitoring claim.
  • If a certification is a hard requirement for you or for one of your customers, tell us on the call and we will tell you plainly where we stand rather than after you have signed.

Out of scope on purpose

What Foreman never touches.

Payment cards

Foreman does not touch payment card data, does not process payments, and does not request the QuickBooks Payments scope. Card data never enters the system because the system was never built to take it.

Your send button

Foreman drafts outbound email. A person on your team approves and sends it. There is no configuration in which it emails your customers by itself.

Money movement

Every movement of money is approved by a person. Foreman writes accounting records; it does not decide to pay or collect on its own.

Leaving

Disconnect, and the access is actually gone.

You can disconnect any integration at any time from Settings inside the app. When you disconnect QuickBooks, Foreman revokes the refresh token, which takes the access tokens with it. Revoking only the access token would leave the grant renewable, which is not a disconnect.

The disconnect also reports back whether Intuit acknowledged it, so you are told what actually happened instead of being shown a clean-looking result that did not land. Our side completes either way, because a disconnect that can fail is a disconnect nobody can perform.

Every stored credential and connector token is encrypted at rest and can be destroyed on request or on account closure. Ask by email or from inside Foreman and it reaches the person who built it.

Sub-processors

The short list.

  • Oluri's own infrastructure in Nashville, Tennessee. Where all customer data and all AI processing lives. This is the primary one and it is the point.
  • The marketing website host and CDN/DNS provider for this website only. No customer data passes through them.
  • A transactional email service for account notifications.

No third-party AI provider is a sub-processor, and none receives customer data.

QuickBooks, Microsoft and Google are connections you authorize to your own accounts. They are not our sub-processors. You grant us access to your data at those services; we do not hand your data to them.

Ask the hard version of the question.

Tyler built the infrastructure and will answer at that level of detail, including the parts that are inconvenient.