Compliance & security

How Concord handles data for buyers inside and outside the Russian Federation — desktop-first, honest about what is and is not certified.

Concord is a local-first macOS app: cluster credentials, DSNs, and operational secrets live in this Mac's Keychain and never transit our servers. goconcord.app and api.goconcord.app only ever see what is needed for licensing, checkout, and support — never your database.

Data residency

Personal data tied to licensing, checkout, and support (email, feedback, install fingerprint, Stripe session refs) is hosted on infrastructure targeted at the Russian Federation (Reg.ru VPS / managed Postgres) as our MVP hosting plan — see the engineering checklist in the repo. Until that migration completes, treat this page as the target state, not a completed attestation.

152-ФЗ — personal data

We built the site and checkout around data minimization: collect only what licensing and support need, gate analytics behind explicit consent, and keep cluster telemetry out of both the web and product-usage contours.

What we collect

Email + optional company name at checkout, for license delivery and receipts
Support / feedback messages you send us, plus optional redacted diagnostics
Install fingerprint / install_id for license binding (pseudonymous unless paired with email)
Web analytics (pageviews, CTA clicks) only after you accept the analytics cookie category
Product usage events only if you opt in inside the app (Settings → Analytics)

What we do not collect

No cluster DSNs, connection strings, hostnames, or credentials — ever, from either the site or the app's usage flush
No marketing pixels or ad-tech trackers on goconcord.app
No selling or renting personal data to third parties
No hidden cross-border transfer beyond the processors listed below

Приказ ФСТЭК России №1119

Order 1119 defines protection levels (УЗ-1…УЗ-4) for information systems processing personal data — a formal compliance track with threat modeling, organizational measures, and often external assessment. It is written for operators of ИСПДн / ЗОКИИ deciding what tools to run, not a certification Concord itself holds.

Honest scope: Concord is not certified or attested under Order 1119 or any УЗ level. We do not claim this compliance in contracts. What we do ship are engineering controls that map to the spirit of the order's lower-УЗ compensating measures — useful context if your organization is evaluating tools under 1119, not a substitute for your own assessment.

Controls we actually ship, mapped to common asks

Control	What we ship
Local-first custody	Desktop app runs on the operator's Mac; cluster secrets stay in macOS Keychain, never uploaded
Контроль привилегированных операций (Safe Ops)	Preflight → typed confirm → progress → audit for switchover, failover, pause, restart, reload
Политика dual-control	Second-approve code for high-impact ops (failover, reinit) — on by default for Team
Журналирование действий оператора	Local append-only audit trail with integrity hash, exportable for postmortems and change review
Шифрование в транзите	TLS/SSH preferred end-to-end; the app warns on plaintext HTTP to Patroni REST
Минимизация телеметрии	Usage flush schema rejects hostnames, DSNs, passwords, tokens server-side — enforced, not just documented
RF-based hosting plan for PD	Licensing/checkout data targeted at RF-hosted infrastructure (Reg.ru) — see Data residency above

Subprocessors

StripePayment processing when live billing is enabled — Concord never stores full card numbers
Reg.ruPlanned RF hosting for the commercial API and entitlement database
Umami / Plausible (optional)Privacy-friendly web analytics, loaded only after you accept the analytics cookie category

Security or compliance questions

Email [email protected] for data requests (access, correction, deletion) or security questions. For procurement / compliance conversations ahead of a regulated deal, use the Partners page — we issue offline signed licenses for air-gapped estates that cannot reach any commercial API.

[email protected]Partners