Review 6 — Privacy policy page (/personvern), NO + EN - #30
Draft
ArneeMe wants to merge 3 commits into
Draft
Conversation
Plain-language personvernerklæring covering the GDPR basics mapped to how the system actually works: controller roles, the 24h submission window, issuance-deletes-data, what remains permanently (hash only), access, anonymous feedback, admin accounts, and rights — pointing out that after issuance there is nothing left to delete server-side. Linked from the landing page's privacy card and cross-linked with /om. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BFHkXUuHJME4cF9AJWbavB
Deploying inf319-certificate with
|
| Latest commit: |
794f246
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://fc0720ad.inf319-certificate.pages.dev |
| Branch Preview URL: | https://claude-review-6-privacy.inf319-certificate.pages.dev |
…feature The privacy policy (/personvern) was written against an earlier product state and no longer matched reality after #29 and #28: - 'Utstedelse uten sletting er teknisk umulig' / 'issuing without deleting is technically impossible' was true under delete-at-issuance, false now — #29 replaced it with the 24h sweep as the sole deletion mechanism, independent of issuance. Rewrote the retention and rights sections to state the actual guarantee: deleted within SUBMISSION_TTL_HOURS regardless of issuance status, deletable manually by the org at any time including after issuance. - 'Etter utstedelse finnes det ingenting å slette hos oss' / 'after issuance there is nothing left to delete' was false for the same reason — a submission can still hold real personal data for up to the TTL window after its certificate is issued. - Dropped the 'Frivillig tilbakemelding' / 'Voluntary feedback' section and the email-notification sentence under 'Who has access' — both describe features #28/#29 removed from the product. This is the legal text users rely on for what the platform actually does with their data, so it can't lag the code it describes. Also restores the SUBMISSION_TTL_HOURS import that a prior merge dropped (the privacy section was the only remaining reference — build was broken on this branch until this commit). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BFHkXUuHJME4cF9AJWbavB
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 6 of the review-ordered stack (on
develop). Content, but worth an actual read: it's the legal text your users will rely on.A plain-language personvernerklæring mapping GDPR basics to how the system actually works: controller roles (the issuing org is controller, attester.no is the platform), the retention window, what remains permanently (hash + metadata only), who has access, and rights. Both languages,
?lang=en, linked from the landing page and cross-linked with/om.Rewritten to match what #29 actually shipped
This PR was originally written against the delete-at-issuance model. #29 replaced that with the 24h regeneration window (sweep-only deletion, independent of issuance) before this PR reached review, so the privacy text was making claims that are no longer true:
"Utstedelse uten sletting er teknisk umulig"/"issuing without deleting is technically impossible"— false now; issuing a certificate does NOT delete the submission. Rewrote to state the actual guarantee: deleted withinSUBMISSION_TTL_HOURSregardless of issuance status, and deletable manually by the org at any time including after issuance."Etter utstedelse finnes det ingenting å slette hos oss"/"after issuance there is nothing left to delete"— also false for the same reason; real personal data can still sit in the submission row for up to the TTL window after a cert is issued.Also restored an
SUBMISSION_TTL_HOURSimport that a prior merge on this branch had dropped — this branch's build was broken until this fix (the privacy section was the only remaining reference to it).Please review the substance: contact address (
hei@attester.no— make sure it exists), the controller framing, and the "juli 2026" date. I drafted it faithfully to the current architecture, but a privacy statement is a commitment you make, not me.Verification: typecheck/lint/119 unit tests/10 E2E/production build — all green.
🤖 Generated with Claude Code
https://claude.ai/code/session_01BFHkXUuHJME4cF9AJWbavB