Version of 21 October 2026. These terms cover the hosted service only. An in-house
installation is governed by the agreement made for it.
1. Who we are
The hosted dossier service at app.dossier.technology and its regional instances
(c1–c4.dossier.technology, the “Service”) is operated by
[operator’s legal name, address, registration number and VAT number: to be
completed] (“we”, “us”). Contact:
file@dossier.technology.
2. The service
dossier reads the documents you upload, keeps registers of what is owed and what has arrived,
answers questions with citations, and drafts documents from that material. The Service is the
same application we install inside customers’ own infrastructure, run by us on servers we
rent. It is offered for two purposes: trying dossier on public or non-confidential
documents before an in-house installation, and using it for work whose material
you are content to process in the cloud. It is not designed for confidential material;
for that, an in-house installation keeps every document and every model inside your perimeter.
3. Accounts and sign-up
3.1 An organisation asks for a workspace through the sign-up form and chooses a region. We
confirm the email address, a person reviews the request, and we may decline it without giving
a reason. An approved organisation gets its own workspace on an instance in that region.
3.2 The person who signs up becomes the organisation’s administrator and is responsible
for who else it admits and with which role. Sign-in is by passkey or by a single-use link sent
by email. Keep both under your control; you are responsible for use of the account until you
tell us it has been compromised.
3.3 You must be able to bind the organisation you name to these terms.
4. Acceptable use
Do not use the Service to upload material you have no right to process in this way; to break
the law or the rights of others; to attempt to reach other organisations’ data or our
systems beyond what the Service offers you; to probe, scan or load-test it without our
written agreement; or to resell it. We may suspend an organisation that does, and will tell it
why unless the law prevents us.
5. Your documents
5.1 Your documents, registers, conversations and drafts remain yours. You give us only the
permission needed to store and process them to provide the Service to you.
5.2 Our administrators manage organisations, configuration and billing. The application does
not give them access to your documents, conversations or registers: that needs a membership
your own administrator grants and can see and revoke. People with access to the servers
themselves could technically reach stored data; we do not do so except to keep the Service
running or restore it, or where the law requires, and we limit that access to the people who
operate the Service.
5.3 We do not use your content to train models, and we do not sell it.
6. Where your documents go
6.1 Storage. Your workspace and its files are stored on the instance in the
region you chose. Encrypted backups are taken every hour. During the beta they
are kept on a backup server in another of our regions: the Europe instance’s backups in
the United Kingdom, and the United Kingdom, United States and India instances’ backups in
Europe (Germany). We intend to keep each region’s backups in that region before general
availability, and will update this section when we do.
6.2 Processing by AI models. To read, index, answer and draft, the Service sends
the content each task needs (questions, document text and excerpts, and for scanned pages the
page images) to third-party AI model providers. We route these requests through
OpenRouter, which passes them to the vendor of the model in use. These providers
may process the content in countries other than your region, including the United States, under
their own terms. The Console shows which model each task uses.
6.3 Your own provider. An organisation or project may configure its own model
provider for any task. That task then goes to your provider instead, under your agreement with
it, and does not use credit.
6.4 Do not upload material you are not permitted to send to these providers. If your material is
confidential, use an in-house installation or ask us about one.
7. Who processes data for us
Who
What for
Where
Contabo GmbH
The servers that run every instance, the sign-up service and the backups
Germany, United Kingdom, United States, India
OpenRouter, Inc., and the model vendors it routes to
AI model processing (section 6.2)
United States and the vendors’ locations
Stripe
Card payments for credit. We never see card numbers.
Ireland and the United States
Zoho Corporation
The mailbox that receives your email to us
European Union
Emails from the Service (sign-in links, billing notices) are sent by mail servers we run
ourselves on the instances above. We will update this list before adding a processor.
8. Personal data
8.1 For sign-up and accounts we keep the name, work email address and organisation you give us,
the region you choose, and the state of your request. For billing we keep your credit, top-ups
and per-request usage records. Our web servers keep access logs, including IP addresses, for a
limited period for security and troubleshooting.
8.2 We use this data to provide the Service, to reach you about it (sign-in links, billing
notices, changes to these terms) and to meet legal obligations. We do not use analytics or
advertising trackers, on this website or in the Service.
8.3 Personal data inside documents you upload is processed on your instructions, as described in
sections 5 and 6. If you need a data processing agreement, write to us.
8.4 You may ask us for a copy of your personal data, its correction or its deletion at
file@dossier.technology. Where data protection law
gives you further rights, including complaining to a supervisory authority, they apply.
9. Prepaid credit
9.1 What it pays for. AI model processing done through the providers we
configure (“included inference”). Credit is held in US dollars by the organisation, is
not a deposit, earns no interest and cannot be transferred to another organisation. Fees for the
Service itself, if any are introduced, are billed separately and announced in advance.
9.2 Buying it. By card through Stripe, from US $10 to US $1,000 per
top-up, available once Stripe confirms the payment; or by bank transfer from US $2, available
once it reaches us. We add no card fee; bank charges on a transfer are yours. Taxes are added where
the law requires and shown on the invoice.
9.3 Price. Each request is charged at the price the model provider publishes for
that model at the time, with no markup. Where the provider reports the exact cost
of a request, that is the charge; otherwise it is the tokens processed times the published
per-token prices. Current prices are in the Console under Billing, and every charge is recorded
with its date, project, task, model, tokens and cost, which your administrators can see.
9.4 Allocation. An administrator may set aside part of the organisation’s
credit for individual projects and change that at any time.
9.5 When it runs out, work pauses; nothing is lost. Before each request we reserve
the most it can cost, and do not send it if the credit does not cover it. Background work waits and
resumes by itself when credit is added; a chat question is answered with the reason it could not
be. We warn administrators in the Service and by email when credit falls low and when it runs out.
If an error ever leaves a negative balance, we tell you and take the difference from your next
top-up, and do not invoice it otherwise.
9.6 Expiry. Credit does not expire. If we ever introduce expiry, it will apply
only to credit bought after we give notice of it.
10. Refunds
10.1 A top-up none of which has been used is refunded in full if you ask within 14 days of it.
10.2 Otherwise credit is not refundable, except that we refund or correct: charges caused by our
billing error, or by unauthorised use of your account that was not caused by your failure to
protect it; the unused credit, if we suspend or end the Service for you other than for your breach
of these terms, or stop offering included inference; and anything the law requires.
10.3 If you close your organisation’s account, we refund its unused credit if you ask within
30 days of closing, less the cost of making the payment.
10.4 Refunds go to the account the payment came from, in the currency it was paid in.
11. Availability
The Service is provided with reasonable care but without a service level, and during the beta it
may change, pause for maintenance, or be unavailable. Requests that fail before producing any output
are not charged; requests that fail after producing output are charged for what was processed.
Drafts and answers are produced by AI models and cite their sources so that a person can check
them: check them before you rely on them.
12. Liability
Nothing in these terms limits liability that the law does not allow to be limited. Within that,
we are not liable for indirect or consequential loss, or for loss of profit, business or data that
an ordinary backup practice on your side would have avoided, and our total liability in any twelve
months is limited to the amount you paid us in those twelve months.
13. Ending the service
You may close your organisation’s account at any time by writing to us. We may end the
Service for you with 30 days’ notice, or at once for a serious breach of these terms. Before
an account is closed by either side, we give its administrators their documents and drafts on
request; then we delete the workspace, and it leaves our backups as they are rotated out.
14. Changes, law and contact
14.1 We may change these terms with 30 days’ notice by email to administrators and in the
Service. A change does not affect credit already bought unless the law requires it or it is in
your favour.
14.2 These terms are governed by the law of the country where the operator named in section 1 is
registered, and disputes go to its courts, without limiting any mandatory protection that the law
of your own country gives you.