SigmaClose
Get started

Security

How your books are handled

Updated

SigmaClose reads your QuickBooks books and never changes them. This page says how the product works today, in plain words, including what we don't have. For the legal documents, see the privacy policy and the terms.

Your QuickBooks books

  • QuickBooks gives every app one kind of access, which allows both reading and changing the books. SigmaClose only sends read requests. It never creates, edits or deletes anything in QuickBooks.
  • The connection QuickBooks gives us is stored encrypted, with a key that is kept apart from the database. It is never shown in the app, never written to logs and never given to an AI assistant.
  • You can cut the connection at any time from the apps list in your QuickBooks settings.

What we hold

  • For each company: its name, its list of accounts and each account's monthly totals. No individual transactions, customers, suppliers, bank details or card numbers.
  • The database is in the United States.
  • Payments happen on our payment processor's own checkout page. We never see or store card details.

Signing in

  • Sign-in is through Google, or through a one-time link and code sent to your email. Customers have no SigmaClose password to lose or reuse.
  • Sign-in codes and links are stored scrambled (hashed), work once and expire.
  • One cookie keeps you signed in, for up to 7 days. It is sent only over an encrypted connection and can't be read by scripts on the page.

Who sees what

  • Each group's numbers are kept apart. Every page, export, connector tool and API route reads only the group you are signed in to, and automated tests check that for each one.
  • People in a group are admins, editors or viewers. Removing someone also revokes the keys they made.

AI assistants, scripts and other automated access

  • Automated access is welcome through the MCP server and the REST API. Nothing either can do changes anything in QuickBooks. Every REST route and every connector tool but one only reads. The one exception, refresh, pulls the latest numbers from QuickBooks into SigmaClose, as the Refresh button does. It needs an editor or admin, and a connection you allowed to refresh.
  • An assistant connects through your own sign-in and sees the one group you approve. A key for a script is shown once, stored scrambled, and can be revoked on the Agents page.
  • One key is public on purpose: the demo key on the Connector and API page. It reads made-up sample data only and can't reach any customer's group. The same sample data can be read at a demo address with no key.
  • Both are limited to 120 requests a minute per address and per key, counted across the whole site, and every call is recorded with who made it.
  • Company and account names come from QuickBooks and are typed by people. They are handed to an assistant as data, never as instructions.
  • The connector and the API are the supported way for software to read your numbers. The website's pages are made for people.

The website

  • Everything is served over an encrypted connection (HTTPS), and browsers are told to refuse anything else.
  • Pages run no scripts from other sites inside the app, forms are protected against requests forged from other sites, and sign-in is rate limited.
  • Error reports sent to our error tracker have cookies, sign-in headers, form contents and query strings removed first.

What we don't have

  • No SOC 2 or other outside security audit, no penetration test report, no bug bounty and no public status page. SigmaClose is a small product from PerfSpot LLC, first released in November 2026.

Deleting your data, and reporting a problem

  • To have a company's numbers, or everything, deleted, ask through the contact page. What stays afterwards is set out in the privacy policy.
  • If you think you've found a security problem, tell us through the contact page. A person reads every message.
  • For how assistants and scripts connect, see Connector and API.