// About Docriva

Who is behind Docriva

Docriva is a tool for the letters you cannot ignore — and this page says who builds it and how the guides are written.

Responsible

Docriva is built and operated by Enock Aimé Jodelle Yonkeu Nyabeo in Allschwil, Schweiz. That means a single person is responsible, not a company with an editorial team — the full details are in the legal notice.

You can reach that person at support@docriva.com. Questions about a guide go to the same address; pointing out a mistake is welcome and gets corrected in the article.

Why Docriva exists

Letters from authorities, invoices and contracts arrive without warning, written in language that was not meant for the recipient, with deadlines that are never printed in bold. Missing one costs money or a right — not through carelessness, but because the letter sat in a pile.

Docriva reads those documents, finds the deadlines in them and reminds you. It does not replace advice and makes no decisions; it makes sure you can still make yours in time.

How the guides are written

The guides explain general rules — which deadline usually applies, when it starts, what a piece of German officialese means. They are not legal advice and do not replace a lawyer or tax adviser in an individual case.

They are written from the statutes themselves and from the information published by the responsible authorities. There is no review by a lawyer — stated here plainly rather than left out.

On deadlines the articles deliberately avoid naming a number of days in the running text: the statutory service-assumption period was extended on 1 January 2025, and an outdated number costs the reader exactly the deadline in question. What counts is always the appeal instructions in your own letter.

Every article carries its publication and its modification date. The modification date only moves when the content actually changed.

What happens to your documents

Every document is tied to your account through Row Level Security; other users technically cannot reach it. Transfers use TLS, storage is AES-256 encrypted.

Text recognition uses Google Cloud Vision via its European endpoint, analysis uses Mistral AI from France. Both process the data within the EU or the EEA, and we have switched off its use for model training. The full list of what goes where is in the privacy policy — including the point at which the encryption of the cloud backup ends.

Get in touchlegal noticeprivacy policy