Frequently Asked Questions

Common questions about how StackCheck works and how to get better results.

How does StackCheck determine where data goes?

StackCheck performs automated infrastructure analysis through multiple methods:

  • DNS analysis - SPF records, MX records, TXT verification records
  • IP geolocation - Where servers are physically located
  • ASN ownership - Which company owns the IP ranges
  • HTML scanning - Third-party scripts, tracking pixels, widgets
  • Privacy policy parsing - Disclosed services and sub-processors

For each third-party service detected, we also scan their infrastructure, because data sovereignty depends on who controls the servers — not just where a company is headquartered.

Does StackCheck find my /subprocessors page?

Yes! StackCheck automatically looks for sub-processor disclosure pages at common paths:

  • /subprocessors
  • /legal/subprocessors
  • /privacy/subprocessors
  • /vendors
  • /third-party

We also check your sitemap and scan links on your homepage that mention "subprocessor", "third-party", or "vendors".

Didn't find yours? After a scan completes, you can submit up to 3 privacy or subprocessor page URLs from the results page, and we'll parse them for services.

Why is a service I use not showing up?

StackCheck can only detect services that leave a visible footprint:

  • Backend-only services with no DNS/HTML presence won't be detected
  • Services not in our signature database won't be recognized
  • Services mentioned only in PDFs or images won't be found

You can manually add missing services using the "Suggest edit" button on any scan result. Your suggestion will be reviewed and added to the listing.

What's the difference between EU and EU-hosted?

EU means both the company and its infrastructure are in the EU. This offers the strongest data protection under GDPR.

EU-hosted means data stays on EU infrastructure, but the company or its cloud provider is non-EU (e.g. a US company with EU data residency, or an EU company on a US-owned cloud region). While the data physically stays in the EU, a non-EU company may still be subject to foreign laws like the US CLOUD Act.

For maximum data sovereignty, prefer services marked as EU over EU-hosted.

How do I verify my listing?

Click the "Suggest edit" button on your scan result. You can:

  • Add services that weren't automatically detected
  • Confirm that you don't use certain service categories
  • Correct any misidentified services
  • Mark services as self-hosted

After review, approved changes will update your listing and can improve your score. Verified listings are marked with a badge.

How is the score calculated?

The score (0-100) reflects data sovereignty risk based on where data flows. Infrastructure findings are weighted most heavily, followed by backend services, then frontend integrations.

Each layer is scored by its worst finding, so a single non-EU infrastructure finding pulls the whole infrastructure layer down, because that's where your data physically goes. See our methodology page for the full scoring formula.

What if I self-host a service?

When suggesting edits, you can mark any service as "self-hosted". This automatically sets the EU status based on your own infrastructure rather than the service provider's.

For example, if you self-host Matomo analytics on your EU servers, it counts as EU even though the Matomo company is based elsewhere.

Still have questions?

Can't find what you're looking for? Get in touch.

hello@stackcheck.eu