Biometric Data Processing Terms
Version 2026-11.
1. Roles
For attendance verification, the Customer decides why and how data is processed, and Warka processes it on the Customer's instructions. Warka still carries its own obligations for security, staying within the agreed scope, deletion and transparency. Allocating duties in a contract does not remove those obligations.
2. Data processed
Face images and frames the Customer sends, encrypted templates derived from them, the Customer's external subject identifiers, verification outcomes and technical metadata such as model versions and timings, and client-reported app and device details, which Warka treats as unverified.
3. Customer attestation
By accepting these terms, the Customer's representative attests that the Customer has obtained and keeps the permissions its use requires for the data and purposes it sends to Warka, that excluded people are not enrolled, and that it will promptly tell Warka about changes, withdrawals or erasure requests.
Warka relies on this attestation. Warka has not inspected any individual's signed document, and it does not collect or store employee consent forms or signatures.
4. Security
Warka encrypts data in transit, encrypts templates and stored captures with keys kept out of the database, isolates tenants, restricts staff access, logs access to captures and exports, and keeps an append-only audit log.
5. Retention and deletion
Captures are deleted after the Customer's retention period, 90 days at most by default. Enrollment images are not kept unless a research permission applies. Templates exist only while the identity is active. Deleting an identity destroys its template immediately and purges its captures. Audit records are kept without the external identifier.
Encrypted backups age out on their own schedule, so deleted data may remain in a backup until that backup expires. It is not restored into service in the meantime except as part of disaster recovery, after which deletions are applied again.
6. Sub-processors and locations
Warka uses Contabo for compute and Cloudflare R2 for encrypted object storage. Because data can cross borders in these services, the Customer must confirm that this is acceptable under the law that applies to it. Warka will give notice before adding a sub-processor.
7. Requests from people
Warka does not deal directly with enrolled people. It sends any request it receives to the Customer, and it carries out the Customer's documented deletion and restriction instructions.
8. End of service
When the service ends, Warka deletes the Customer's templates and captures within 30 days unless the law requires otherwise, and can provide an export of non-biometric records on request.