REKORD Get REKORD →
Trust

Security overview

REKORD captures conversations that do not belong on a consumer gadget. The security model starts on the endpoint, stays inside a perimeter you choose, and assumes your security team will ask for evidence before they say yes.

On the device

REKORD Go writes to 128 GB of AES-256 encrypted storage. There is no camera, no speaker, and no wake word. Microphones open when the button is pressed and close when it is pressed again. Capture state is shown on the monochrome display, readable from across a table. If the network is gone, the conversation is still on the device.

In transit and at rest

Uploads to REKORD Cloud use TLS. Data at rest is encrypted. Customers can bring their own KMS. Revoke the key and the data is unreadable, including to REKORD. On a customer-cloud or on-premise deployment, your VPC, your logging and your key material stay in your tenancy.

Where it runs

REKORD Cloud runs in Paris and Frankfurt. Nothing on that path is processed, stored or backed up outside the European Union, including the models. There is no US subprocessor in the product path. Air-gapped on-premise is supported. Models ship as signed artefacts.

What we refuse to do

Customer audio, transcripts and summaries are never used to train or fine-tune a model. That sentence is in the contract, not only on this page.

Certifications and tests

REKORD is audited against ISO 27001, ISO 27701 and SOC 2 Type II. We publish a penetration-test summary every year. The GDPR pack (DPA, TIA, records of processing) is available before signature. Reports that contain control detail are available under NDA.

Admin controls

Administrators can set retention limits, restrict recording by location or calendar, and require participant consent capture. Every deletion is logged. The log is exportable. Leaving the service is an API call, not a project.

Vulnerability reports

If you find a security issue in the website, the device, or the service, email [email protected]. Please give us a chance to fix it before you publish. We will acknowledge receipt and tell you when the issue is closed.