Security and privacy

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

Where your data lives, who can reach it, what is encrypted, and what we will not claim.

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

Where your data is processed

Most AI products in this trade send your cost, your customer and your price to OpenAI, Anthropic or Google. Oluri runs its AI on servers it owns in Nashville. Nothing goes to a third-party AI provider.

Where it runs

Where everything runs

  • 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

The four claims

Credentials

Encrypted at rest, per company

Connector tokens and credentials: AES-256-GCM at rest, under a key specific to your company.

Storage

Disk-level encryption

Customer data volumes: AES-256-XTS at the disk level.

Transport

TLS in transit

Everything in transit travels over TLS.

Processing

Inference on company-owned hardware

Inference on hardware Oluri owns. No third-party AI provider in the path.


Operational integrity

After a write to your books

A write that succeeded is not the same as a write that is correct.

Verify-back

Every write is read back and diffed

Every QuickBooks write is read back and compared to what was proposed. A mismatch raises an alarm. A double click cannot create a second invoice.

Journal

Append-only, including the refusals

Every execution and every refusal lands in an append-only journal.

Per company

Sealed to the company and the purpose

Each company's data is sealed under its own key, bound to the company and the purpose. It cannot be decrypted in another company's context.

Storage

Mirrored as well as encrypted

Customer data is mirrored across two drives.

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

What Oluri is not certified for

Here is the ledger in the other direction.

  • Not SOC 2, ISO 27001 or PCI certified. Our internal policy set is modeled on ISO 27001. Modeled on is not audited against.
  • 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 your customers, ask on the call and you will get a straight answer.

Out of scope on purpose

What Oluri never touches

Payment cards

No card data, no payments, no QuickBooks Payments scope.

Your send button

Oluri drafts. A person approves and sends. There is no setting that lets it email customers by itself.

Money movement

Every movement of money is approved by a person.

Leaving

Disconnecting

Disconnect any integration from Settings. QuickBooks is revoked at Intuit, refresh token included, and you are told whether Intuit acknowledged it.

Stored credentials and tokens can be destroyed on request or at account closure.

Sub-processors

Subprocessors

  • 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.

Security questions

Email or call. You reach the people who built the infrastructure.