1In short
2On the device
When a presentation request arrives, the context unit checks a short, fixed list of signal categories: an active call, screen sharing or recording, remote control, a request from another device without proximity proof, device integrity, and presentation history.
The evaluation happens locally, at that moment. The context unit does not record calls, does not read screen content and does not monitor the device outside a presentation request.
The history category relies on a small local record of past presentations on the device (for example, whether a verifier has been seen before). It stays on the device.
3What leaves the phone
Only the attestation record, inside the presentation response, to the verifier whose request the person is answering. The record contains:
| Contained | Never contained |
|---|---|
| Risk class 0–3 | Phone numbers, caller identity, contacts |
Category flags, such as voice_call | Audio, call content, call duration |
| Timestamp within the consent window | Screen content or screenshots |
| Hashes binding it to the request and presentation | Names of installed or running apps |
| Outcome of the prompt (confirmed, paused, declined) | Location, network or device identifiers |
| Rule-set version and capability vector | Any data sent to BuonaLabs |
4The person stays in control
- The person sees, in plain language, what situation is being recorded before sharing.
- The person can decline the presentation at any point.
- Warnings protect the person; they are not a hidden score about them.
- People who rely on accessibility services are never flagged for using them.
5At the verifier
The verifier receives the record as part of a presentation it requested, processes it in its own systems and keeps it under its own retention rules. The verifier is responsible for its own processing, including the legal basis and information duties towards its customers.
For pilots we provide a data-protection impact assessment template with worked example entries, and support the partner's own assessment remotely.
6No data to BuonaLabs
Calmproof runs on the device and in the verifier's systems. There is no Calmproof cloud service in the presentation flow, no analytics in the context unit and no telemetry to BuonaLabs. In pilots, measurements are produced from the partner's own test scenarios.
7Questions
BuonaLabs UG (haftungsbeschränkt), Maria-Goeppert-Straße 3, 23562 Lübeck, Germany. hello@calmproof.com
This fact sheet describes the design of Calmproof with attestation record v1. It is not legal advice. The privacy notice for this website is a separate document: Privacy.