Privacy Policy
Feature Detail
Description
The Privacy Policy page on the Meander Sales Website publicly documents how personal data is collected, processed, and protected during sales interactions. As a static legal page, it establishes GDPR compliance before any commercial relationship begins, covering data categories from demo request forms, legal basis for processing, retention periods, and visitor rights under EU data protection law. It is linked from the site footer and all data-collecting forms, and is a prerequisite for the cookie consent mechanism on the site.
Sources & reasoning
Explicitly listed under the Fase 1 MVP scope for the Sales Website as 'Privacy policy og vilkår' and again in the Product 4 static site feature list. GDPR mandates a privacy policy for any website collecting EU visitor data. Both references confirm MVP target release; phase 1 ordinal maps to MVP.
No source references — this artifact was included based on reasoning alone (see above).
Analysis
A publicly accessible privacy policy is a legal requirement under GDPR for any website collecting visitor data, including demo request submissions and analytics. For a platform managing health-adjacent personal data across four regulated Norwegian non-profits, demonstrating privacy governance from the sales funnel itself builds institutional trust. Procurement reviewers at NHF, HLF, Blindeforbundet, and Barnekreftforeningen - organizations acutely sensitive to data handling - will verify compliance independently before signing; a clear policy directly reduces procurement friction and shortens the sales cycle materially.
Implemented as a static page on the Next.js static export (or Astro) Sales Website with no backend dependency. Content authored in markdown or MDX and rendered at build time, ensuring zero runtime data processing on the page itself. The page requires a permanent, crawlable URL and must be linked from the global footer and every form collecting personal data. Norwegian Bokmål is the primary language. No authentication, database access, or shared runtime with operational products. Updates require a new static build; a visible effective date and version indicator are recommended for change tracking.
Components (46)
Shared Components
These components are reused across multiple features
Service Layer (11)
Data Layer (23)
Infrastructure (7)
User Stories
No user stories have been generated for this feature yet.