feat(0pt): record legitimate-interest stance — B2B contacts, company-linked only
CI (SIAX Cloud) / quality (push) Successful in 45s
CI (SIAX Cloud) / security (push) Successful in 24s
Security Scan (SIAX Cloud) / security (push) Successful in 34s

Recorded decision (Simon 2026-08-31): personal data may be stored under
legitimate interest ONLY as business contacts bound to a company/org entity.
Gate enforces it: legitimate_interest requires purpose=business_contact and
entity_linked_only=true; recordStored() requires entity_id (orgnr/rgs/LEI,
hashed) and refuses person-only rows. +1 test; suite 167 pass | 1 skip;
typecheck clean.
This commit is contained in:
2026-08-31 01:18:03 +02:00
parent c94987fa60
commit 52bd89d119
4 changed files with 116 additions and 3 deletions
+19
View File
@@ -16,6 +16,23 @@ first byte is stored**.
(`0pt.pii_policy_created | pii_data_retained | pii_erased |
pii_retention_purged`).
## Recorded legitimate-interest stance (Simon, 2026-08-31)
> "Vi får lagra dem om dem är kopplade till företagen i affärssyfte."
Personal data may be stored under **legitimate interest (art. 6(1)(f))** ONLY
as **business contacts bound to a company/org entity** (`entity_linked_only`).
The gate enforces this mechanically:
- `legal_basis: legitimate_interest` ⇒ `purpose` MUST be `business_contact` and
`entity_linked_only` MUST be `true`. A lazily-written policy is rejected.
- `recordStored()` refuses person-only rows for such policies: an `entity_id`
(orgnr/rgs-nummer/LEI) is REQUIRED; only its hash is ever stored.
- Stand-alone personal records (no backing company) are not permitted under LI.
This is the recorded business-policy decision — a written LIA should be kept
and its id referenced in `basis_ref` (`lia-YYYY-MM-b2b-NN` naming is fine).
## GDPR article mapping
| Requirement | Implementation |
@@ -35,6 +52,8 @@ first byte is stored**.
- [x] Write the **Legitimate Interest Assessment** (or record consent /
contract / legal obligation) and store its id in `basis_ref`.
LIA minimum: purpose, necessity, individuals' rights impact, mitigations.
For LI: purpose `business_contact` + `entity_linked_only` (see recorded
stance above — an LIA referencing `lia-YYYY-MM-b2b-NN` is good practice).
- [x] **VERIFY current terms + robots.txt + availability** on the live site.
Do not hardcode "catsit.com allows" — re-check each enable.
- [x] Set `robots_and_rate_confirmed: true` + a `SourceRatePolicy` matching