Expedientia is in private pilot phase. This information describes how the system currently works technically, but does not replace a privacy policy that has been legally reviewed and approved. Real case files must not be uploaded until the data controller has been identified, the necessary contracts have been formalized, and the participating lawyer has accepted the final documentation.
Case-file data is processed to organize evidence, extract citable units, propose facts for verification, and prepare an editable formal-demand response. The system does not make legal decisions on the user’s behalf and requires professional review before the document can be marked as reviewed.
| Provider | Function | Note |
|---|---|---|
| Cloudflare | Application, database, queues and file storage | The service’s D1 and R2 bindings are configured with EU storage jurisdiction. |
| OpenAI | Document extraction, structured analysis and audio transcription | The necessary content is transmitted via API for inference. Applicable location and retention depend on the contract and configuration in force. |
| Resend / Stripe | Transactional email / payments | These only come into play if those functions are enabled and configured for the pilot. |
Although primary storage is configured in the EU, analysis by an external provider may involve processing outside the EEA. Before real data is used, the impact assessment, the data-processing agreement, the final list of sub-processors and the transfer safeguards must be finalized. The lawyer remains responsible for assessing whether a given case file can be uploaded in accordance with their duties of confidentiality and professional secrecy.
When deletion is requested, the case file becomes unavailable and an asynchronous purge is logged. The purge removes the originals, extracted text and product records linked to the case. Residual retention periods held by the AI provider, security logs and infrastructure-managed copies must be set out in the final policy and in the applicable contracts.
A completed or interrupted multipart upload that has not yet been linked to a case file enters automatic reconciliation after 24 hours of inactivity; from that point it is deleted or aborted. A storage failure keeps its record so the deletion can be retried in later cycles.
Access to each case file is checked per user; originals are opened via short-lived links and sensitive operations are logged. These measures alone do not amount to a security certification. Risk assessment and pre-pilot testing with real data remain mandatory.
For questions or requests about personal data, write to info@dathent.com. The complete identity of the data controller and the formal channel for exercising rights will be added before real data is enabled.