Security

Report a vulnerability

How to report one, and what to expect when you do.

Avenkin runs on a camera and a microphone you may wear on your face. Reports are welcome and taken seriously.

Reporting a vulnerability

Please do not open a public issue for a security defect. Use either private channel:

It helps to include the version or commit, the device and iOS version, steps to reproduce, what an attacker gains, and whether any data left the device.

Please do not send us other people's data. If reproducing a finding captured someone's face, voice or health information, describe it rather than attaching it.

What to expect

These are the targets of a small team, not a contractual commitment.

StageTarget
Acknowledgement that a person has read it3 business days
Triage: severity, scope and what happens next10 business days
Fix or written mitigation plan, high and critical30 days
Fix or written mitigation plan, everything else90 days

These are New Zealand business days. If a target passes in silence, please chase it. Once a fix ships we publish an advisory and credit you by whatever name you prefer, including none.

Scope

In scope: the iOS app with its extensions, watch app and widgets; the scripts and build configuration in the source repository; and this website and the files it publishes.

Out of scope: Meta's Wearables Device Access Toolkit and Meta's services; third-party AI providers and model hosts; Apple platform defects; findings that need an already-compromised device; and scanner output with no analysis.

Safe harbour

If you research in good faith and within the scope above, we will not pursue or support legal action against you. Good faith means using your own devices and accounts, not accessing or keeping anyone else's data, not degrading the service for others, and giving us a reasonable chance to fix a finding before publishing it.

The full policy is SECURITY.md in the source repository. Machine-readable contact details are at /.well-known/security.txt.