Privacy & trust¶
This site is for documentation. The procurement-officer page — sub-processors, data residency, encryption, retention, GDPR posture, DPA, security contact, vulnerability disclosure, audit signing key, methodology change protocol, steward-ownership status, constitution — is at trust.vettedinference.com.
Quick pointers¶
| If you need... | Go to |
|---|---|
| Sub-processor list | trust.vettedinference.com/#sub-processors |
| Data residency declaration | trust.vettedinference.com/#residency |
| Encryption posture | trust.vettedinference.com/#encryption |
| Retention policy | trust.vettedinference.com/#retention |
| GDPR DSR workflows | trust.vettedinference.com/#gdpr |
| DPA template | trust.vettedinference.com/#dpa |
| Security contact + PGP | trust.vettedinference.com/#security-contact |
| Vulnerability disclosure policy | trust.vettedinference.com/#vulnerability-disclosure |
| Audit-signing PGP key | trust.vettedinference.com/#audit-signing |
| Methodology change protocol | trust.vettedinference.com/#methodology-change |
| Regional coverage posture | trust.vettedinference.com/#regional-coverage |
| Steward-ownership status | trust.vettedinference.com/#steward-ownership |
| The 12 Selma constitutional principles | vetted.eco/governance |
| The 8 Articles of Association | GitHub |
| The Charter-to-Code mapping | Constitution → Charter to code |
Why the split¶
The trust page is read by procurement officers and security reviewers. The marketing site is read by buyers and the press. The docs site (here) is read by engineers and methodologists. Each surface serves a different reader; embedding everything in one document would corrupt the tone of all three.
Regional coverage posture¶
The current procurement-safe regional coverage posture is:
live-ready: none todayfresh-but-not-live:FR,FI,GB,DE_LUfallback-dominant:DK_1,DK_2,SE_1,SE_2,SE_3,SE_4,ES
These buckets are based on the strict methodology rule, not on generic service uptime:
live-readymeans the source observation is consistently within the strict+/-15 minutereceipt windowfresh-but-not-livemeans the signal is recent and auditable, but not consistently inside that strict live windowfallback-dominantmeans current production reality often pushes the receipt outside the near-time window
For the underlying methodology and receipt provenance fields, see the carbon intensity sources page. For operational service health, incidents, and future bucket movements, see status.vettedinference.com.
For Nordic routing specifically, we now distinguish between:
- operational live inputs used to improve routing quality in Denmark and Sweden
- receipt-grade live evidence used in the conservative audit trail
That means an operational Swedish or Danish routing decision may use an official forecast or provisional control-room signal, while the final receipt still records only the stricter measured/fallback methodology result.
Status¶
For service status, incidents, and post-mortems, see status.vettedinference.com.