CorbaCount

Security at CorbaCount.

If you are evaluating us as a vendor, this page answers the questions your DPO will ask. No certifications we do not hold, no vague promises - just what we do, where the data sits, and who can touch it.

GermanyWhere all data and backups are hosted
No IPsStored with pageviews, not even as a hash
1 cookieFirst-party, random id, no ad networks
2FA & passkeysOn every account

What data does CorbaCount store about my visitors?

Per pageview we keep the page URL and title, the referrer, UTM tags, the derived country and network (ASN), browser, OS and device type, screen resolution, preferred language and Core Web Vitals. No IP address, not even a hash of it. That is it - the full list is in our privacy policy.

IP addresses

Used, then deleted

  • Used on our own servers to derive a country code from a local MaxMind GeoLite2 database - no per-visitor lookup goes to MaxMind
  • Pageviews never store the IP, not even as a hash
  • For a new session the raw IP waits in a short queue for a reverse-DNS check that flags datacenter traffic; each entry is deleted right after the check, normally within minutes and never later than 24 hours

One first-party cookie

Set on the customer's own domain

  • A single _cc_vid cookie containing a random UUID, expiring after 365 days
  • It only stitches one visitor's pageviews into a session on that one site; a coarse device fingerprint (timezone, language, screen, platform) is the fallback when the cookie is missing
  • No cross-site profiles, no ad networks, no data sold or shared for advertising - ever

More on what that means for consent on our cookie banner page.

Where is the data hosted?

Everything - customer data, visitor data, backups - lives on servers physically located in Germany, inside the European Union. Germany applies both the GDPR and the German Federal Data Protection Act (BDSG), one of the strictest data protection regimes in the world. There is no US cloud region, no "EU-ish" CDN edge node, no exception.

Is there a DPA?

Yes. For visitors of your website you are the data controller and CorbaCount acts as your data processor - that split is spelled out in the privacy policy. A data processing agreement covering this relationship, including the sub-processor list below, is available on request: ask via the contact page and we will send it over.

How is data protected in transit and at rest?

TLS 1.3 in transit

Every connection - from the tracking beacon on your site to the dashboard in your browser - is encrypted with TLS 1.3. Plain HTTP is not served.

Hardened accounts

Passwords are stored as salted bcrypt hashes - we never see the plaintext. Two-factor authentication and passkeys are supported on every account.

Encrypted backups

Backups are encrypted at rest and stored in Germany alongside the primary data, under the same EU-only rule.

Operator-only access

Access to production data is limited to a small set of operators bound by confidentiality. CorbaCount is run by a small team - meet us on the about page - which means a short, auditable list of people who can touch your data.

Which sub-processors does CorbaCount use?

This list is updated before any new sub-processor with access to personal data is added.

Sub-processorWhat forWhat they receive
MaxMindGeoLite2 database, used locally to translate IPs into country codesNothing per visitor - the database is downloaded to our servers
PusherChannels service that pushes real-time visitor events to logged-in customer dashboardsThe anonymised visitor identifier and minimal pageview metadata
DataForSEOSEO data: backlinks, anchors and ranked keywordsOnly the customer's own domain name - no visitor data
Google Search ConsoleSearch queries for a property the customer connectsNothing - Google sends us aggregated stats; visitor data is never sent to Google
MolliePayment processing for subscriptionsCustomer billing details - no visitor data
Total InvoiceCreating and sending invoicesCustomer name, email and billing details - no visitor data

How long is data kept?

Raw pageviews are rolled into pre-aggregated daily and hourly counts that the dashboard reads from. Retention per type of data:

DataKept for
Real-time "who is online" entries5 minutes
Raw IPs waiting for the datacenter checkAt most 24 hours
Raw pageviews and sessions flagged as bots30 days, after that only daily bot counts remain
Raw pageviews and aggregated statsAs long as the site is in your account - deleting a site deletes its data
Customer account dataDeleted immediately when you delete your account (invoices stay 7 years, as Dutch tax law requires)

Are you SOC 2 or ISO 27001 certified?

No, and we will not pretend otherwise. CorbaCount is a small pre-launch product, and a certification audit at this stage would be theatre. What we offer instead is radical transparency: this page, the privacy policy and the small amount of data we collect are all verifiable from the outside. If your procurement process strictly requires a certification, we are honestly not the right vendor yet.

How do I report a security issue?

If you believe you have found a vulnerability in CorbaCount, please tell us before telling anyone else. Send the details through the contact page - a real human reads it, and we will acknowledge your report within one business day.

  • Give us reasonable time to fix it before public disclosure
  • We keep you informed and credit you if you want to be credited
  • We never threaten legal action over a good-faith report

Questions your DPO still has?

Send them over - security and privacy questions get the same one business day reply as everything else.

Contact us