Compliance
Compliance, honestly
Where Rocketic and Concord stand on Russian data-protection law and infrastructure security guidance — no inflated claims.
152-FZ — personal data
For customers in the Russian Federation, we plan to host personal data tied to licensing, checkout, and support — email addresses, activation identifiers, feedback — on infrastructure located in the Russian Federation, in line with Federal Law No. 152-FZ. Cookie and consent choices default to analytics off until you opt in, and data-handling practices are published on Concord's own Privacy page, since that's where the personal data actually flows through checkout and support.
FSTEC Order No. 1119 — what we do and don't claim
We make no certification or attestation claim under FSTEC Order No. 1119 or any УЗ (protection class) level. Full attestation is a formal compliance engagement — threat modelling, organizational orders, external assessment — that a small commercial software company has not undertaken. What we do ship: compensating controls in the spirit of a lower protection class for a small internet-facing service — TLS everywhere, least-privilege access, secrets kept out of source control, encrypted backups, and a working revoke path. If you're an enterprise RF buyer, expect straight answers about where data lives, how it's encrypted, and how we back up and revoke access — not a УЗ attestation document we haven't earned.
International customers
Concord is local-first: it runs on the Mac, keeps secrets in the OS keychain, and does not require sending cluster credentials to a cloud backend to operate day-2 — a real advantage on VPN-restricted and air-gapped estates anywhere, not only in Russia. Formal trademark clearance for the Concord name is in progress, not complete; every Concord surface carries a non-affiliation disclaimer in the meantime.
Cookies on this site
rocketic.io itself collects no personal data beyond what you choose to send us by email. Optional, consent-gated analytics (page views and click events only) help us understand which pages are useful — never enabled without your choice, and never mixed with Concord's own product or checkout data.
Questions about compliance
If you're doing procurement due diligence — RF data residency, backup/revoke process, or general security posture — write to us and we'll answer directly, without a sales detour.