BalkanReg

Privacy

What we collect, why, and how to have it removed.

Sources, per country

  • Romania: the ANAF web services (public and free; we identify ourselves with a User-Agent that carries our contact) and the ONRC open data on data.gov.ro under the Romanian open licence, attributed on every answer that uses it.
  • Not yet collected: Bulgaria, Croatia, Slovenia, Greece, Serbia, Hungary, Slovakia.

What we store

  • Company records from those registries, together with the raw upstream answer.
  • Officer names and roles as published by the registry, with source attribution.
  • Your account: the Clerk user id, and no email unless you give it to us or buy credits (then Stripe passes us the payer email).
  • Payment records from Stripe when you buy credits: the Stripe event with payer name, email and billing address, the pack, the amount and refunds or disputes.
  • API key hashes and key prefixes (never the key itself).
  • A request log: tool, country, the identifiers you sent (company id, VAT number, year, or the name you searched for), credits and timestamps.
  • For sanctions screening (screen_sanctions and kyb_report): the cached OpenSanctions answers, served for at most 7 days and deleted after 90 days. The name you screened is not stored; the cache is keyed by a keyed hash of it, the answer has the echoed query and identifier fields (ID and passport numbers, birth data, addresses, contacts) removed, and the request log keeps only a hash and the length of the name.
  • Per-call (MPP) payments, which need no account: the Stripe PaymentIntent id and the amount, kept with the request log and with payment records. No name, email or card detail reaches us.

What we never store or serve

  • Personal identification numbers such as the Romanian CNP.
  • Birth dates and residence of representatives.
  • Phone, fax, IBAN and fiscal domicile of sole traders: these are stripped before storing.

Retention

  • Request log: 12 months.
  • Cached registry answers are refreshed after 24 hours (ANAF) and after 30 days (balance sheets).
  • Monthly ONRC snapshots are kept with personal numbers and representatives' birth and residence data blanked before storing.
  • Our own log of requests to the registries: 90 days.
  • Payment records: as long as accounting and tax law requires.
  • Account data: until you ask us to delete it at support@balkanreg.app.

Deletion and objection

Write to support@balkanreg.app. For registry data, the registry is the source: we point you to it and remove our copy on request.

Processors

  • Clerk: sign-in.
  • Stripe: payments, acting as merchant of record.
  • Cloudflare: hosting and DNS.
  • Railway: api hosting.
  • Sentry: error reports from the api (no request bodies or keys).
  • OpenSanctions (api.opensanctions.org, Germany/EU): receives the name, and the country if you give one, that you submit to screen_sanctions, and the company name and the officer names on file for kyb_report, to match them against sanctions and watch lists. Sanctions screening is provided through the OpenSanctions API; results are cached per query for 7 days.
  • PostHog (optional): page views with IP address, browser and page path; no account or company identifiers.