Less collection.
Fewer surprises.
This note describes the code in the current concept-site preview. Hosting, entity, and contact details must be completed before riposte.no is publicly deployed.
No cookie banner because the current site code sets no cookies.
No analytics, advertising pixels, session replay, or behavioural profiling.
No forms or subscriptions collect information in this preview.
No local storage, tracking identifier, or preference record is written.
02 / WHAT IS SERVED
A static reading experience.
The concept site is generated as static HTML, CSS, JavaScript, and local assets. The visible product transcript is HTML rather than an embedded third-party demo. Fonts are packaged with the built site, so a visitor's browser does not contact a font vendor to render a page.
The current code does not request your name, email address, company, security targets, credentials, or product data. It does not include a consent-management platform because there is currently nothing optional to consent to.
03 / OPERATIONAL DATA
Hosting still creates a boundary.
A public hosting or content-delivery provider may process ordinary request data such as IP address, timestamp, requested path, user agent, and error information to deliver and protect the site. No production provider or retention period has been selected for this candidate, so neither is claimed here.
Before launch, this section must name the hosting provider, processing purpose, location or transfer basis where relevant, log retention, access controls, deletion path, and accountable privacy contact.
04 / CHANGES
Collection does not appear by implication.
If the site later adds a contact form, design-partner application, update subscription, or justified measurement, the relevant purpose, fields, recipients, retention, and choices will be documented before collection begins. Sensitive vulnerability details will never be routed through a general marketing form.
Material revisions will carry a new effective date and a short change summary. The public policy will also identify the responsible legal person or entity and a monitored privacy contact.