Security
What happens to what you put in a form.
Three things first, because they are what people ask.
- No value put into a form is kept. It is held in the memory of one session’s own browser while the session is open, and is gone when the session closes. It is never written to our database, our logs or our backups.
- It goes to the form you name, and nowhere else. It is not sold, shared, or sent to any other company.
- No outside AI sees it. Fields are set by our own code and our own small model, on our own machines. Nothing put into a form goes to an AI company, and none of it is used to train any model.
Documents
A PDF that you hand over, or that the service fetches for you, is worked on with no network connection at all, in that session’s sealed working space. It is gone when the session closes.
One session, one browser
Each session has a browser of its own, in a sandbox of its own, walled off from the machine it runs on and from every other session. Both are destroyed when the session closes.
A session can reach only public addresses on the internet, or the one proxy you name for it. It cannot reach our own network or another session.
Nothing of ours is installed on your machine or your network. The service runs on our machines, in the United States.
Encryption
The API, the MCP server and the console are served only over HTTPS, with TLS 1.2 or later. There is no unencrypted way in.
The database and its backups are on disks that Google Cloud encrypts at rest. Values from forms are never written to either.
Keys and sign-in
A key is stored only as a one-way fingerprint and shown once. It carries the permissions you give it (read, fill or send; sandbox or live), and you can revoke it at once.
There are no passwords. People sign in with a link sent to their e-mail. The sign-in cookie cannot be read by scripts.
Each account’s rows in the database are walled from every other account’s by the database itself, not only by the application. Changes to an account, and every action by our own staff, are written to a record of who did what and when. Your account’s own record is in its console.
Payments
Card details are entered on Stripe’s own page. No card number reaches us.
What the record of a session holds
The site’s name, never the full address of a page. The names of the fields asked for, what came of each, and what it cost. Never a value.
What the service will not do
- It does not send a form because it was filled. It presses a button only when asked. A file you ask it to attach goes to that form, and the answer says where it went.
- It does not accept a pop-up.
- It does not fill a field that a person cannot see: the traps that sites set for robots stay empty.
- It does not type a card number, sign for a person, or work a CAPTCHA.
This website
It sets no cookie and has no analytics, trackers or pixels.
Reporting a weakness
Tell us at support@settleon.ai.
Passwords
A password given in a call is typed into that one form and never kept. If you would rather not give one at all, keep it in your own 1Password and let the assistant name where it is kept: how to set that up.
The notices
The Privacy Notice says what we keep about an account and its use. The Data Processing Addendum says how we handle personal data for customers. The Terms of Service are the agreement.