Choose where your data lives — and prove it

What a policy says

• Allowed jurisdictions: a country by its ISO 3166-1 code, plus a region
• Residency classes
• The class of the data
• The minimum protection level for the keys

Placement needs a proof

A node accepts data only together with a proof that the placement was checked against the policy. That proof is produced by the check itself and cannot be assembled by hand, so there is no way to place data «just this once» around the rules.

A refusal names its reason

When a placement is refused, the reason is specific:

• The key or node was revoked
• It is not valid yet, or it has expired
• The jurisdiction is not allowed
• The residency class does not match
• The data class does not match
• The key storage is below the required level
• Replicas would end up outside the policy

An example

Tell the platform that this organisation's data lives only in the UAE, with keys at or above a set protection level — and any placement that breaks the rule is refused with the reason.