COUNTRY IS PART OF THE REQUIREMENT

A fit for your work.
And where you work.

A product can have the right features and still fail your access, data or procurement requirements.

Five different questions

  1. Where is it used? Select the buyer country and other user locations. Billing history and restricted territories may also matter.
  2. Who supplies it? Check the contracting legal entity separately from the brand, founder nationality, reseller and parent company.
  3. Can you contract and pay? A working website or a free signup is not evidence of local purchasing support.
  4. Where does data go? Distinguish stored content from backups, account metadata, support access, integrations and AI processing.
  5. What can this organization procure? Check the exact edition, registry record, purchasing procedure, sector and required certifications.

What the result means

Evidence found: a current source covers the selected check and plan. Conditions apply: migration, configuration or another explicit condition remains. Needs verification: evidence is missing, out of date or does not cover the selected edition. Does not meet requirement: a documented restriction conflicts with your selection.

The finder excludes documented conflicts from matching candidates and keeps them in an expandable explanation. Unknown evidence is never converted into permission. Public, state-owned and regulated purchases remain subject to a human procurement/security review.

Real examples

Notion’s Russia policy distinguishes user location and workspace billing history. ClickUp’s access policy lists restricted countries and specific territories; we do not extend territorial restrictions to an entire country.

Notion’s regional storage requires an eligible Enterprise workspace and excludes several data categories. ClickUp’s AI FAQ explains that EU workspace hosting does not establish EU-only AI processing.

Russia and public procurement

Choose the buying entity type and the register required by the procurement team. Russian and EAEU software registers are distinct evidence sources. Verify the current record, rightsholder, software class and edition; review exceptions and the applicable procedure separately. We do not infer registry membership from a Russian-language interface or local office.

The Russian government’s procurement documentation describes registry identifiers in the context of national treatment under Resolution 1875. The US Treasury’s software-services guidance illustrates why service category, supplier and exceptions also require review. Neither source is a universal decision for a particular purchase.

European data requirements

Select an EU/EEA region or a particular country when your organization requires it. EU storage is not automatically GDPR compliance, and GDPR is not a blanket ban on non-EU vendors. The European Commission describes mechanisms for international data transfers. Your data flows, contract and subprocessors still matter.

Current coverage

The selector accepts ISO countries and territories; this does not mean we have verified every country. Our initial country evidence covers specific facts for Notion, ClickUp and OpenProject. Other combinations are unverified. No product has been awarded a procurement approval or a checked Russian/EAEU registry badge.

Sources were checked on 26 September 2026. Positive country facts need rechecking after 30 days. A known restriction is retained until an editor reviews and supersedes it. This is preliminary software screening, not a legal or security certification. Entity-level sanctions screening, certification validation and full procurement decisions are not automated.

Check your requirements