How Alisios handles your project documents
This overview describes how the system works today, not how it is meant to work one day. What is not yet in place is listed in the section "What we do not have yet".
The key points in brief
- Your documents are kept in a private, access-protected database and file store in the EU (AWS Ireland, operated by Supabase).
- Only people you invite to your project can see them. There are no public links and no self-registration.
- The AI step runs on an OpenAI model operated by Microsoft Azure. Access goes through OpenRouter. We require zero data retention, and your content is not used to train models.
- Every AI finding is backed by a verbatim quotation from your page. The review is automated: nobody at Alisios checks a result before you see it. Your own reviewer confirms, corrects or discards each item and signs.
- On your request we delete your project data and confirm the deletion in writing.
Data flow
Your browser
│ HTTPS (TLS) the web application is static and is served via Cloudflare Pages;
│ documents are uploaded directly to Supabase, not to Cloudflare Pages
▼
Supabase project, AWS region eu-west-1 (Ireland)
├─ private file bucket "dossier-uploads" originals (PDF, Excel, Word, photos)
├─ Postgres database page text (incl. OCR), requirements, AI results with quotations,
│ review decisions and signatures, job and log data
└─ private file bucket "dossier-evidence" image excerpts of the quoted page passages
▲
│ TLS, server certificate checked against the Supabase CA
▼
Alisios processing service ("worker"; during the pilot, the founder's Windows workstation in the Netherlands)
│ text extraction and OCR run locally on the worker
│ sends page text and, for individual pages, a page image to the model (see next section)
▼
OpenRouter (routing) ──► Microsoft Azure (model inference)
Settings: Azure as the only provider, no fallback to other providers,
data collection prohibited, zero data retention mandatory
What is sent to the AI model
Your original files are never sent as files. The worker extracts the page text locally (including OCR). Depending on the function started, it sends the following:
| Function | What the model receives |
|---|---|
| Full package review ("Full sweep") | The extracted text of every readable page, document by document. Page images (JPEG) of pages whose scan could not be read reliably. |
| Review against requirements | Only the pages found for each requirement. Page images of signature and approval pages. |
| Question to the project assistant | At most 8 pages found. |
| Suggesting requirements | The specification pages of the package. |
Every request also contains the document's file name, the project context you entered (facility, construction period) and your list of requirements. If as few pages as possible should reach the model, the pilot can be limited to the review against requirements, without the full package review.
Retention in the AI step. Every request demands OpenRouter's zero-data-retention routing. Under OpenRouter's data processing agreement, inputs and outputs are deleted immediately after the response is generated (OpenRouter names the exceptions: legal obligations, abuse, logging enabled by the customer). OpenRouter classifies the Azure endpoint as zero retention. Microsoft states that inputs and outputs are not used to train models. OpenRouter stores operational data such as token counts, costs and timestamps, but no document content.
Region of model processing. Since 16 November 2026, every model request is pinned to Azure's EU endpoint (azure/eu), with no fallback to other endpoints: if the EU endpoint is unavailable, the request fails rather than leaving the EU. A test call through this endpoint was completed successfully on 16 November 2026. The request itself is routed with zero data retention through OpenRouter, a US company (see "What we do not have yet").
Who can see your data
- Your project members. You decide whom you invite and in which role: administrator, editor or reader. The database's row-level access control (Row-Level Security) restricts every page, every result and every file to the members of the respective project. Accounts are created by invitation only; self-registration is switched off.
- Alisios technical administration. The worker and the system administrator hold a service key with access to all projects. We use it only to carry out your jobs, for support you request, and for deletions. Today one person has this access: the founder, bound by an NDA and a data processing agreement (DPA).
- Service providers process data only as described above and in their data processing agreements (see the list of sub-processors in the draft DPA).
Security measures in place
- HTTPS throughout. The web application sends HSTS and a restrictive Content Security Policy.
- Supabase encrypts data at rest (AES-256) and in transit (TLS), according to Supabase's own documentation.
- The file buckets are private. Users read files through their project membership, never through public links.
- The worker verifies the database's TLS certificate. Its credentials are stored encrypted for exactly one operating-system user (Windows DPAPI) and appear neither in the code nor in logs.
- The worker log is designed to capture only job identifiers and error codes, no document content.
- Cost caps apply per request, per review run and per project. Before any model use, a cost estimate is shown and must be confirmed.
Your reviewer decides
The AI delivers a draft. Before a review run, an editor approves the review criteria. A finding stands only if it quotes a verbatim passage of the cited page; otherwise it becomes "insufficient evidence". Anything read from images is marked as such. Alisios does not review the result. Your own reviewer checks every item, can correct or discard it and signs. Only the review signed by your reviewer becomes the report for the client.
Deletion
At the end of the pilot or at any time on your request, a project administrator (or we, on your instruction) deletes all dossier data of the project:
- The database records (documents, page text, requirements, results, signatures, jobs) are deleted immediately in a single transaction.
- A deletion job then removes the uploaded files, the image excerpts and the local copy on the worker. It checks that nothing remains and records in the audit log what was removed.
- You receive a written confirmation of deletion. It states what was deleted and what is retained.
What is retained is the project name, the list of members and the audit log. The audit log records who deleted what and when, but contains no document content. Reports that you downloaded yourself remain with you.
Options for the pilot
- Confidentiality agreement on request. A mutual NDA is available on request (template available).
- Data processing agreement. A draft DPA under Art. 28 GDPR, with technical and organisational measures and a list of sub-processors, is ready for review by your legal department.
- Anonymised package. You can redact names, signatures and client or site names before uploading. The reviews work with the technical content.
- Limited scope. Review against requirements only, without the full package review, if fewer pages should reach the model.
- EU model endpoint. Model inference runs on Azure's EU endpoint (see "Region of model processing").
- Deletion after the pilot with written confirmation, on a date agreed in advance.
What we do not have yet
This is what you should hear from us:
- No ISO 27001 or SOC 2 certification of Alisios itself. Supabase states SOC 2 Type 2 and ISO 27001; Microsoft Azure holds its own certifications. Alisios is a young company and has not yet been audited.
- Routing through a US company. Model inference takes place in the EU (Azure's EU endpoint), but the request is forwarded by OpenRouter, a US company, with zero data retention. A route that stays entirely within the EU (OpenRouter's in-region routing or a direct Azure Data Zone EU deployment) is possible on request.
- Payment. Unlocking a full review is paid on a payment page operated by Stripe (Stripe Payments Europe, Ltd., Ireland; Stripe, Inc. is a US company). Card and bank details are entered at Stripe: Alisios never sees or stores them. Stripe receives the contact, billing and payment details you enter there and the identifier of the analysis you pay for; no document and no finding is sent to Stripe. Alisios receives from Stripe the confirmation of the payment and the details needed for the invoice.
- Companies outside the EU in the chain. OpenRouter, Supabase and Cloudflare are US companies. Stored data stays in the EU region, but these companies, and where applicable their staff and operating systems in the USA, are part of the processing chain. Transfers rely on the providers' standard contractual clauses.
- The pilot worker is a single workstation, not a redundant data-centre server. A dedicated EU server is prepared but not yet in operation.
- No multi-factor authentication for user accounts. Sign-in is so far by password only.
- No independent penetration test yet.
- No commitment on backup and recovery during the pilot. Please keep your originals yourself.
Questions: directeur@alisiosconsulting.nl