ConcordHA Cockpit for Patroni

Privacy

This page describes how Concord handles data on goconcord.app and via the commercial API at api.goconcord.app. It is a product-oriented draft for MVP hosting in the Russian Federation; final legal wording must be approved by counsel for your operator entity.

1. Operator

Pending entity registration, the operator of personal data processing will be the Concord legal entity (ИП / ООО) named in the published оферта. Contact: [email protected]. Hosting for personal data is planned on infrastructure in the Russian Federation (Reg.ru VPS / managed Postgres) — see docs/hosting-regru-152.md in the repository, or the plain-language Compliance & security page for 152-FZ and FSTEC Order No. 1119 positioning.

2. Categories of data

  • Account / license: email, activation key hash, install_id, license fingerprint, Stripe session identifiers.
  • Support: feedback messages and optional redacted diagnostics you send.
  • Product usage (opt-in in the app): event kinds and safe props only. Forbidden: hostname, DSN, passwords, tokens, and similar secrets (enforced server-side).
  • Web: pageviews / CTA events only after analytics consent; consent choice stored locally.
  • Logs: technical access logs (may include IP) with short retention and restricted access.

3. Purposes and grounds

We process data to provide licensing and checkout, support the product, improve the site (with consent for non-essential analytics), and secure the service. Specific lawful bases (contract, legitimate interest, consent) will be stated in the operator’s final policy.

4. Retention

  • License and entitlement records: for the license term plus a limited archive needed for disputes and revoke lists.
  • Feedback: typically 12–24 months unless a longer dispute holds.
  • Raw usage events: shorter window; aggregates may be kept longer.
  • Access logs: typically 30–90 days.

5. Processors / recipients

Hosting (e.g. Reg.ru) acts as a processor for infrastructure. Payment card data is handled by Stripe (or another PSP) when that path is enabled — Concord does not store full card numbers. Offline / invoice licensing may avoid card processors entirely.

6. Cookies and similar technologies

Categories: necessary (consent record / essential operation), analytics (optional; default off), marketing (not used on MVP). Use “Cookie settings” in the footer to change your choice. Analytics scripts and web.* client events stay gated until you allow analytics.

7. Your rights

Subject to applicable law (including 152-FZ where it applies), you may request access, correction, deletion, or restriction of processing of your personal data by emailing [email protected]. We may need to verify the request and retain data where legally required (e.g. revoke lists, accounting).

8. Product usage vs web analytics

Concord separates web analytics on goconcord.app from product usage flush from the desktop app. Web tags never collect cluster endpoints, DSNs, or license private keys. Product analytics are opt-in in Settings and reject forbidden properties server-side.

This stub is not a substitute for a counsel-approved privacy policy or consent forms. Cross-border transfers, processor contracts, and merchant-of-record terms require human legal review.