Transparency Report
Version 1.0 · Effective 2026-04-20
1. About this report
This page is our standing, continuously updated record of government requests for user data, account suspensions for legal reasons, and other events where an external authority has asked us to act on user data. It accompanies the Privacy Policy and exists so that Users can see clearly how often — and with what outcome — outside requests touch their data.
We publish this information because we believe that a healthy privacy posture requires visible, checkable numbers, not just promises. If any figure on this page ever becomes non-zero, we will record it here alongside the context needed to understand what happened.
2. Government requests for user data
| Period | Requests received | Requests complied with | Accounts affected | Records disclosed |
|---|---|---|---|---|
| Since Service launch — 2026-04-20 | 0 | 0 | 0 | 0 |
Scope. The figures above include: subpoenas, court orders, administrative orders, informal requests from law-enforcement or tax authorities, and national-security requests — from the Republic of Armenia or any other jurisdiction.
Methodology. A request is counted in the period in which it is received. If a request is withdrawn before any disclosure, it is counted as received but not complied with.
3. Requests to remove or restrict content
| Period | Requests received | Content removed or restricted |
|---|---|---|
| Since Service launch — 2026-04-20 | 0 | 0 |
4. Account suspensions for legal reasons
| Period | Accounts suspended |
|---|---|
| Since Service launch — 2026-04-20 | 0 |
5. Personal data breaches
| Period | Breaches reported to the PDPA / EU authority | Users affected |
|---|---|---|
| Since Service launch — 2026-04-20 | 0 | 0 |
Details on our breach-notification procedure are in Section 7 of the Privacy Policy.
6. Warrant canary
As of the "Effective" date at the top of this page:
- We have never received a secret demand for user data that would prevent us from publishing it here.
- We have never been compelled to weaken the security of the Service or install software that would expose user data.
- We have never handed over the contents of the
vcr-sessioncookie store or decrypted SRC credentials to any third party.
If this statement is ever removed or materially changed, treat that as a signal in its own right.
7. Publication schedule
This page is updated at least annually, and also whenever a non-zero event occurs. Each update bumps the version number and records what changed in Section 8 below.
8. Change log
- v1.0 — 2026-04-20 — Initial publication. All categories reported at zero since Service launch.
9. Contact
Questions or corrections: support@vcr.am with the subject line "Transparency report".