Data processing
Data Processing Addendum
Effective November 14, 2026
This addendum is part of the Terms of Service between SettleOn AI, Inc. ("SettleOn") and the customer that uses the service ("Customer"). It applies whenever SettleOn handles personal data for Customer and a data protection law requires a contract about that handling. It needs no signature to take effect. Customer may ask for a signed copy at support@settleon.ai.
1. Words used here
- Customer Personal Data means personal data that Customer, or someone using Customer's keys, sends to the service to be put into a form or a document, or attaches to a session as a label.
- Data Protection Law means the law on privacy and personal data that applies to the handling of Customer Personal Data, including the EU General Data Protection Regulation ("GDPR"), the GDPR as it forms part of the law of the United Kingdom ("UK GDPR"), the Swiss Federal Act on Data Protection, and the California Consumer Privacy Act ("CCPA").
- Controller, processor, data subject, personal data, processing and supervisory authority have the meanings the GDPR gives them. Where the CCPA applies, "controller" includes a business and "processor" includes a service provider.
- Standard Contractual Clauses means the clauses annexed to European Commission Implementing Decision (EU) 2021/914.
- Sub-processor means another processor that SettleOn engages to handle Customer Personal Data.
2. Who is what
For Customer Personal Data, Customer is the controller, or a processor acting for its own customers, and SettleOn is Customer's processor. Customer is responsible for having a lawful ground to send the data and for any notice or consent the law requires.
For information about Customer's own account (the people who sign in, keys, the record of use, and payments), SettleOn is a controller, and the Privacy Notice applies.
3. Instructions
SettleOn handles Customer Personal Data only on Customer's documented instructions. The Terms, this addendum, and the calls made with Customer's keys are those instructions. SettleOn does not sell Customer Personal Data, does not use it for any purpose of its own, and does not use it to train any model. If the law requires SettleOn to handle the data in another way, SettleOn tells Customer first unless the law forbids it. SettleOn tells Customer if it believes an instruction breaks Data Protection Law.
4. What SettleOn keeps, and for how long
The service is built so that SettleOn holds as little Customer Personal Data as it can.
- Values. A value to be put into a form is held in the memory of one session's own browser while the session is open. It is not written to SettleOn's database, logs or backups, and it is gone when the session closes.
- Documents. A document handed over or fetched for Customer is held in that session's sealed working space and is gone when the session closes.
- Labels. A label that Customer attaches to a session is kept with the record of that session while Customer's account exists.
- The record of use. The name of the site, the names of the fields asked for, what came of each and what it cost are kept as Customer's record of use and of charges. The record holds no value.
At the end of the agreement, or earlier when Customer asks, SettleOn deletes the Customer Personal Data it holds within 30 days. Each backup is deleted when it is 30 days old. SettleOn may keep what the law requires it to keep, and protects it under this addendum for as long as it does.
5. People
Everyone SettleOn allows to reach Customer Personal Data is bound to keep it confidential and reaches it only as far as the work requires.
6. Security
SettleOn keeps the measures in Annex 2. It may change them as the service improves, and it will not make the protection weaker overall.
7. Sub-processors
Customer authorises SettleOn to engage the Sub-processors in Annex 3, and others under this section. SettleOn puts each Sub-processor under a contract that protects Customer Personal Data to the standard of this addendum, and remains responsible for what each one does.
SettleOn posts a new Sub-processor on this page at least 15 days before the Sub-processor begins to handle Customer Personal Data. A customer that asks at support@settleon.ai is told of each change by e-mail. Customer may object on reasonable data protection grounds within those 15 days. If the objection cannot be met, Customer may end the agreement, and SettleOn returns the unused part of the balance Customer paid for.
8. Help with rights and duties
Taking into account that SettleOn does not keep values, SettleOn gives Customer reasonable help:
- to answer a data subject who uses a right under Data Protection Law. If such a person writes to SettleOn about Customer Personal Data, SettleOn passes the request to Customer and does not answer it itself;
- with a data protection impact assessment, or a consultation with a supervisory authority, that concerns the service.
9. A breach
If SettleOn learns of a breach of security that leads to the loss, alteration, disclosure of, or access to Customer Personal Data, it tells Customer without undue delay and in any case within 72 hours of learning of it. It says what happened, what data and whom it concerns as far as it knows, and what it is doing about it, and it adds to that as it learns more. It takes reasonable steps to contain the breach and limit its effects. Telling Customer of a breach is not an admission of fault.
10. Showing that this is kept
SettleOn gives Customer the information reasonably needed to show that this addendum is kept. Once a year, and also after a breach or when a supervisory authority requires it, Customer may send SettleOn a security questionnaire, and SettleOn answers it. Where Data Protection Law gives Customer a right to an inspection that the answers do not satisfy, Customer may carry one out, or have an independent auditor bound to confidentiality do so, on 30 days' written notice, in working hours, at Customer's cost, and without reaching other customers' data.
11. Sending data to other countries
SettleOn handles Customer Personal Data in the United States.
- From the European Economic Area. Where Customer sends Customer Personal Data that is subject to the GDPR, the Standard Contractual Clauses are part of this addendum: Module Two where Customer is a controller, and Module Three where Customer is a processor. In them, the optional docking clause 7 and the optional wording in clause 11 are not used; clause 9 is by general authorisation with the 15 days of section 7; under clause 17 the law is that of Ireland, and under clause 18 the courts are those of Ireland. Annex 1 below gives the details for their Annex I, Annex 2 for their Annex II, and Annex 3 for their Annex III. The competent supervisory authority is the one for Customer's establishment in the European Economic Area, or otherwise the Irish Data Protection Commission.
- From the United Kingdom. Where the UK GDPR applies, the United Kingdom's International Data Transfer Addendum to the Standard Contractual Clauses, version B1.0, is part of this addendum, completed with the same details. Either party may end it as its table 4 allows.
- From Switzerland. Where the Swiss Federal Act on Data Protection applies, the Standard Contractual Clauses apply with references to the GDPR read as references to that Act, and the Federal Data Protection and Information Commissioner as the supervisory authority.
If the Standard Contractual Clauses and the rest of this addendum differ, the Standard Contractual Clauses prevail.
12. California
Where the CCPA applies, SettleOn is Customer's service provider. SettleOn handles Customer Personal Data only for the business purpose of providing the service. It does not sell or share that data. It does not keep, use or disclose it outside its direct business relationship with Customer or for any purpose other than providing the service. It does not combine it with personal data from other sources, except as the CCPA allows a service provider to do. SettleOn understands these limits and will keep them, and tells Customer if it can no longer do so. Customer may take reasonable steps to stop and put right any use of the data that is not allowed.
13. Health information
This addendum is not a business associate agreement under the U.S. health privacy law HIPAA. A customer that needs one asks for it at support@settleon.ai before sending protected health information.
14. How this sits with the Terms
The limits of liability in the Terms apply to this addendum, except where Data Protection Law does not allow a liability to be limited. If this addendum and the Terms differ about the handling of Customer Personal Data, this addendum prevails. It lasts as long as SettleOn handles Customer Personal Data.
Annex 1: The processing
- The parties. Customer, as the party sending the data: the account's name and the e-mail address of its owner, as held in the console. SettleOn AI, Inc., as the party receiving it: support@settleon.ai.
- What it is about. Filling forms and documents for Customer.
- What is done. The data is received over an encrypted connection, put into the form or document Customer names, read back to confirm it, and, when Customer asks, sent to the form's owner. It is then discarded.
- Why. To provide the service to Customer.
- How long. For the life of each session. Labels attached to sessions: while the account exists.
- How often. Whenever Customer uses the service.
- Whose data. The people whose details Customer puts into forms: Customer's own customers, clients, employees, applicants and other people Customer acts for.
- What data. Whatever Customer chooses to put into a form or a document. It may include names, contact details, identifiers issued by governments, and details of money, work, family, immigration and health. SettleOn does not need to know which, and does not look.
- Sensitive data. Customer may put special categories of data into a form. The same measures apply to all of it: it is held only for the session, in that session's own sealed browser, and is not kept.
Annex 2: Security measures
Keeping sessions apart
- Each session runs in a browser of its own, inside a sandbox of its own that is walled off from the machine it runs on and from every other session. The browser and the sandbox are destroyed when the session closes.
- A session can reach only public addresses on the internet, or the one proxy Customer names for it. It cannot reach SettleOn's own network or another session.
- A document is worked on with no network connection at all.
Keeping as little as possible
- Values put into forms are held in memory for the session and never written to the database, the logs or the backups.
- Logs record that an operation happened and how it ended, never a value a caller gave or a page held.
- The record of a session holds the site's name, never the full address of a page.
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 stored on disks that Google Cloud encrypts at rest.
Access
- An API key is stored only as a one-way fingerprint. It is shown once, carries the permissions it was given (read, fill or send; test or live), and can be revoked at once.
- People sign in to the console with a link sent to their e-mail or with Google. There are no passwords to steal. The sign-in cookie cannot be read by scripts and is sent only over HTTPS.
- 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 SettleOn staff, are written to a record of who did what and when.
- Only the staff who operate the service can reach its machines.
Payments
- Card details are entered on Stripe's own page. No card number reaches SettleOn.
Keeping the service running
- The database is copied every night to private storage. Each copy is deleted when it is 30 days old.
- The machines, the network rules and the storage are defined in code and can be rebuilt from it.
If something goes wrong
- SettleOn tells affected customers of a breach within 72 hours of learning of it, as section 9 says.
- Reports of a weakness in the service go to support@settleon.ai.
Independent audit
- SettleOn has not yet had an independent security audit and holds no security certification. It answers customers' security questionnaires, as section 10 says.
Annex 3: Sub-processors
- Google LLC (Google Cloud). Runs the machines on which sessions run, and stores the database and its backups. United States (Iowa).
No other company receives Customer Personal Data from SettleOn. Stripe (payments) and Google's sign-in service handle information about Customer's own account, for which SettleOn is a controller, and receive nothing that is put into a form.
The website or document that Customer names, and a proxy that Customer names, receive what Customer has put into the form. They are chosen by Customer and are not Sub-processors.