Trust and data
REMI sits next to a clinical relationship — a practitioner's recommendations, and a person's daily life. That only works if the data question is answered before the first client is onboarded, not after.
This is the honest version: what is decided, what is intent, and what has not been chosen yet. Every commitment here is one you can hold us to in the pilot conversation, and none of it is a certification we do not have.
GDPR by design
Protection built in while the schema is still being designed is a different product from protection retrofitted after launch. REMI is built by a Belgian company, so GDPR is the floor here, not the ambition.
Lawful basis, purpose limitation and a person's rights over their own data are design inputs to each feature — not a checklist run once, shortly before launch.
Only what the accompaniment actually needs. A field that would be interesting to have, but is not needed to help someone, does not get collected.
A practitioner sees the people they support, and nobody else. Access is scoped to the relationship that justifies it, and ends when that relationship does.
Personal data is not sold, not traded, and not used to train models that serve anyone but the person it belongs to. That is a product decision, not a setting.
What is stored, why, for how long and who processes it — recorded as it is built. Sub-processors get named: a vendor we cannot describe is a vendor we do not use.
REMI is not the medical record. Diagnoses, prescriptions and clinical history stay in the practitioner's own system; REMI works from the recommendations that come out of it.
Data residency
No storage vendor is committed yet. That is deliberate — and it is exactly why residency can still be a selection criterion rather than a migration project.
The safety model
The usual answer to a health AI's safety question is a longer filter list. Ours is structural: REMI holds no clinical opinion of its own, and everything it says has to sit inside a frame the practitioner set.
What may be suggested, what must be avoided, and for whom. The frame comes out of the consultation, belongs to the practitioner, and can be tightened at any moment.
Meals, steps and encouragement are generated within the frame. Outside it, REMI does not improvise: it says that it cannot, and points back to the practitioner.
A symptom, a medication question, something that has changed — REMI routes it to the practitioner instead of answering it. And what REMI has suggested stays visible to the practitioner, so it can be corrected rather than discovered.
The limits
Product boundaries, not caveats buried in a terms page. If a feature would blur one of these lines it does not get built — and the same commitment sits at the bottom of every page on this site.
Never diagnoses. REMI forms no clinical opinion and offers none.
Never treats or prescribes. No dosages, no supplements of its own initiative, no change to anything a practitioner or doctor has set.
Never replaces professional care. It is a wellness companion between consultations, built to send people back to their practitioner rather than to keep them in an app.
Never invents its own programme. Without a practitioner's recommendations behind it, there is no plan for REMI to support.
Never turns a person's data into someone else's product. Not sold, not traded, not a training set.
Questions we welcome
These are what practitioners, clinics and legal teams ask, and not one of them is unwelcome. Where the answer is not decided yet, you get “not decided” and the reason — not a reassuring sentence.
Where exactly will our patients' data live, and under whose control?
What is sent to an AI model, to which provider, and what is deliberately kept out of it?
Is REMI a medical device — and what would push it into that category?
Can we sign a data processing agreement before a pilot starts?
Who is responsible for what, between the clinic, the practitioner and REMI?
What happens to our data if we stop — or if REMI does?
The data question is easier to answer before a pilot than during one. Bring your DPO, your legal counsel, or your own list.