Data processing terms
Data processing terms
How we handle personal information on a customer's behalf.
Last updated November 18, 2026
These terms are part of the agreement between a customer and Iron Rod Systems LLC, a Utah limited liability company ("we", "us") for MIDAAS, whether that is our terms of use or a signed order. They apply wherever a customer's workspace contains personal information and data protection law makes the customer its controller and us its processor. They take effect when the customer starts using MIDAAS. Nothing more needs signing, and we will sign a counterpart if a customer's process wants one.
1. Which information this covers
- Customer content is what a customer and its people put into MIDAAS: documents uploaded or synced from a connected source, what MIDAAS makes from them (text, tables, page images, descriptions, extracted facts, search index), questions, answers, saved conversations and remembered notes, and the people in the workspace. The customer is the controller, we are its processor, and these terms govern.
- Our own records are who the customer's contacts are, the agreements and invoices, and the security records we keep to run the service. We are their controller, and our privacy notice governs instead.
Where a term is defined in the GDPR, the UK GDPR or the CCPA, it carries that meaning here.
2. What we do with it, and why
We process customer content only to provide MIDAAS to that customer, to keep it secure and running, and to support the customer when asked. We do not sell it, share it for advertising, use it to serve another customer, use it to train models, or mine it for statistics beyond the usage metering needed to bill the customer.
3. The customer's instructions
We process customer content only on the customer's documented instructions. The agreement, these terms, and what the customer's people choose to put in, ask and configure are those instructions. We will tell the customer if an instruction appears to break data protection law, and may pause that processing while it is sorted out. If a law we are subject to compels us to go beyond the instructions, we will tell the customer first unless that law forbids it.
4. Who can see it
Our staff do not enter a customer's workspace unless its administrators allow it, for a time they choose; every visit is recorded and emailed to them. Everyone at Iron Rod Systems with access is under a written duty of confidentiality that outlasts their time with us. Administrative actions are logged in a tamper-evident audit trail.
5. Security
We keep the measures in Annex II, judged against the risk to the people the information is about. We may change a measure as MIDAAS changes, but not in a way that materially weakens overall security. Our security page carries the working detail.
6. Subprocessors
The customer gives us general authorization to use subprocessors. Those that may handle customer content are named in Annex III. Each is bound by written terms no less protective than these, and we remain responsible to the customer for what they do. Before adding or replacing one, we give at least 30 days' notice by email to the workspace's administrators. If the customer has a reasonable data protection objection and we cannot offer an alternative, the customer may stop using the affected service and we refund fees prepaid for the unused part.
7. When someone asks about their information
People whose information is in a workspace deal with the customer, because the customer is the controller. If one of them comes to us directly, we tell them to contact the customer, and tell the customer promptly. We will help the customer answer, including by finding, correcting, exporting or deleting what we hold, without charge for reasonable help. Much of this the customer can do itself in the workspace.
8. If there is a breach
If we become aware of a personal data breach affecting customer content, we notify the customer without undue delay, and aim to within 72 hours. The notice says what we know: what happened, the kinds and rough number of records, the likely consequences, what we are doing, and who to talk to. We send what we know first and add to it as we learn more. We do not notify regulators or the people affected on the customer's behalf unless the customer asks us to in writing.
9. Assessments
If the customer needs to carry out a data protection impact assessment or consult a regulator about our processing, we will give the information reasonably needed.
10. Getting it back, and deletion
The customer can delete documents and conversations at any time; deletion removes them and everything made from them. When the customer asks us to close its workspace, we delete all customer content within 30 days. Copies the law requires us to keep, and copies in our database provider's backups until they roll off, remain protected by these terms.
11. Showing our work
On written request, no more than once a year unless there has been a breach, we will answer a reasonable security questionnaire and provide the information needed to show we meet these terms. If that is not enough to meet a legal requirement, we will agree a proportionate audit, at the customer's cost, on reasonable notice and without access to other customers' information.
12. Sending information across borders
We and our subprocessors process customer content in the United States. Where customer content comes from the EEA, the UK or Switzerland, the European Commission's standard contractual clauses (module two, controller to processor, and module three, processor to processor, as the roles require), with the UK addendum where it applies, are incorporated into these terms, with the details in the annexes. If the clauses and these terms conflict, the clauses control.
Annex I: Details of processing
| Item | Detail |
|---|---|
| Parties | The customer (controller); Iron Rod Systems LLC, Utah, United States (processor) |
| Subject and purpose | Providing MIDAAS: reading the customer's documents, making them searchable, and answering its people's questions with citations |
| Duration | For as long as the customer uses MIDAAS, then until deletion under section 10 |
| People concerned | The customer's users; anyone named in the documents the customer puts in |
| Kinds of information | Users' names, email addresses, roles and activity; whatever personal information the customer's documents and questions contain |
| Special categories | None intended. The customer agrees not to upload them unless a signed agreement covers them |
| Frequency | Continuous, while the service is in use |
Annex II: Security measures
- Passwordless sign-in by one-time link or code; a passkey or authenticator app required for administrators; optional single sign-on.
- Role-based access with per-collection overrides.
- Every record, index entry and file scoped to one workspace; every request limited to the workspace it came to.
- Support access only when the customer allows it, time-limited and recorded on both sides.
- Append-only, hash-chained audit trail.
- HTTPS for every request; encryption at rest by our providers; secrets encrypted again with a key held outside the database; files delivered by expiring signed links.
- Rate limits, input guardrails and per-workspace AI spending limits.
- Full deletion of documents and workspaces, including search index entries, files and derived AI output.
Annex III: Subprocessors
| Provider | What it does for MIDAAS | Where |
|---|---|---|
| Cloudflare, Inc. | Runs the service and this website, stores uploaded files and page images, sends sign-in and notification email | Global network; files in the United States |
| Neon, Inc. (on Amazon Web Services) | The database: workspaces, people, document text, search index, conversations, audit trail | United States (AWS us-east-1) |
| Anthropic, PBC | Claude models: understanding questions, writing answers, and the assistant on this website | United States |
| Google LLC | Gemini models: describing images, diagrams and scanned pages so they can be searched | United States |
| Cohere Inc. | Embeddings that make passages searchable by meaning, and ranking passages by relevance to a question | United States |
Plausible Analytics counts visits to our public website only and never receives customer content, so it is not a subprocessor.