Skip to content

Control and permissions

Can AI change my POS or accounting records?

A simple guide for owners who want to know whether connecting an AI puts their records at risk, how read-only is enforced, and how a deliberate write is set up if you ever want one.

Concept guideApplies to The Edge and your connected systems · Claude

Short answer

Not unless you set it up that way. The connections we build are read-first, and the AI can only run pre-vetted queries, never free SQL. The connection we run on The Edge today reads a one-way export and does not write back. The Edge can also be set up to write back, deliberately, through its data-transfer connection, if you want it, and we have verified that path. That is a choice you make, not something the AI turns on. For your other systems, access is set up for what you need and stays adjustable: read-only to start, and any write is turned on deliberately, for you.

An owner weighing whether to let an AI reach the POS, the books, or another system of record, who wants to know what it can and cannot do to the data.

  • A clear idea of which systems you are connecting.
  • A decision, up front, about whether any path may write, or read only.
  • A gateway that keeps reading the default and makes writing a separate, deliberate choice.
  1. Read-first, enforced on the server. The AI can only run pre-vetted queries, never free SQL. Read-only is enforced on the server, not by good behavior.
  2. The Edge connection we run today is read-only. It reads a one-way export and does not write back. Write-back to The Edge is a separate, deliberate setup you choose, through its data-transfer connection, and we have verified that path.
  3. Other systems are set up by need. Access is set up for what you need and stays adjustable. We provision conservatively, read-only to start.
  4. A write is a deliberate choice, made for you. Any write is turned on deliberately, for a specific task. It is not something the AI enables in the moment, or that a reworded question turns on.

It can

  • Answer questions from your records without changing them.
  • Run only pre-vetted queries, never free SQL, with read-only enforced on the server.
  • Stay read-only for as long as you want, and add a specific write later only if you decide it is worth it.

It cannot (as we run it today)

  • Run free-form SQL, or a query it was not given. Read-only is enforced on the server, not left to good behavior.
  • Turn its own writing on. Any write, including a write back to The Edge, is set up deliberately, for you, never enabled by the AI in the moment or by a reworded question.
  • Do anything to a system it was never connected to.

Is read-only really enforced, or just asked for?

Section titled “Is read-only really enforced, or just asked for?”

Enforced. The AI can only run pre-vetted queries, never free SQL, and read-only is enforced on the server rather than left to the AI’s good behavior. Rewording a question does not widen what it can do, because the limit lives on the server, not in the phrasing.

The connection we run today does not write back; it reads a one-way export. The Edge can be set up to write back, deliberately, through its data-transfer connection, and we have verified that path. If you ever want a write, it is a separate setup you choose, turned on for a specific task, never something the AI enables on its own.

EvidenceSupported capability under gate

The connection in production on The Edge reads a one-way export: the data leaves The Edge and lands in a copy we host, and the connection we run does not write back. We last verified it running on August 27, 2026. Read-only is enforced on the server, and the AI can only run pre-vetted queries, never free SQL. For your other systems too, access is set up by need and stays adjustable, read-only to start, with any write turned on deliberately for you.