Dutch Telecommunicatiewet & ePrivacy Directive Compliance

Cookie & Local Storage Policy

Complete transparency regarding terminal storage hygiene, strictly necessary functional cookies, zero commercial tracking scripts, and client-side PWA tokens.

Updated: September 2, 2026Dutch Tw Art. 11.7a & ePrivacy DirectiveZero Commercial Trackers
Zero Tracking Pixels

No Google Analytics, Meta Pixel, or ad-tech trackers. No cross-site profiling or data monetization.

Strictly Necessary Only

Tokens limited to secure HttpOnly JWT session cookies and CSRF protection (Dutch Tw 11.7a exempt).

PWA Local Storage

Local shell caching via service workers for offline resilience. Never caches unencrypted user data.

Ephemeral Handshakes

Rotating 60-second QR codes and doorstep arrival nonces self-terminate immediately upon verified meeting.

Terminal Equipment Data GovernanceAmsterdam, The Netherlands
Corporate Body:Silkly B.V. (in formation)
Primary Compliance & Privacy Desk:hi+compliance@silkly.top
Section 1

Statutory Framework & Strict Privacy-by-Design

1.1 Statutory Scope & Legislative Authority: This Cookie & Local Storage Policy ("Policy") governs the utilization of cookies, web storage, browser caching, and terminal storage technologies across silkly.top (the "Site") and its associated Progressive Web Application ("PWA"). Silkly B.V. (in formation) ("Silkly," "Platform," "we," "us," or "our") establishes this framework in accordance with:

  • Article 11.7a of the Dutch Telecommunications Act (Telecommunicatiewet - Tw).
  • Directive 2002/58/EC of the European Parliament and of the Council (ePrivacy Directive), as amended by Directive 2009/136/EC.
  • Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation - GDPR).
  • Regulatory standards published by the Dutch Data Protection Authority (Autoriteit Persoonsgegevens - AP) and the Authority for Consumers and Markets (Autoriteit Consument & Markt - ACM).
1.2 Absolute Zero-Tracking Mandate:Silkly is engineered under strict privacy-by-design and privacy-by-default architecture. Silkly does NOT deploy, host, execute, or permit third-party commercial advertising trackers, behavioral profiling pixels, remarketing tags, cross-site identity graphs, or surveillance ad-tech scripts (such as Google Analytics, Meta Pixel, TikTok Pixel, or external programmatic advertising cookies). The platform does not sell, trade, license, or broker user browsing telemetry to data brokers or advertising consortiums.

1.3 Terminal Equipment Scope: This Policy applies to all information stored on, or accessed from, the user's terminal equipment (including smartphones, tablets, laptop computers, desktop workstations, and mobile browsers running our PWA). Terminal storage encompasses HTTP cookies, HTML5 Local Storage, HTML5 Session Storage, IndexedDB, CacheStorage, and Service Worker registration caches.

Section 2

Classification & Legal Bases under Dutch and EU Law

2.1 Statutory Consent Exemption for Strictly Necessary Storage: Under Article 11.7a, Paragraph 3 of the Dutch Telecommunicatiewet and Article 5(3) of the EU ePrivacy Directive, prior user consent is NOT required for the storage of information, or gaining access to information stored in terminal equipment, if:

  • The sole purpose is carrying out the transmission of a communication over an electronic communications network.
  • It is strictly necessary in order to provide an information society service explicitly requested by the subscriber or user.

2.2 Core Operational Exemption: All cookies and client-side storage technologies utilized by Silkly qualify as strictly necessary technical mechanisms required to facilitate secure user authentication, prevent session hijacking, maintain decentralized cryptographic state, ensure responsive mobile PWA rendering, and enforce anti-scraping security. Because no tracking cookies or invasive third-party analytics are deployed, platform access does not subject users to manipulative cookie walls or deceptive consent-banner nudging.

2.3 Information Duty & GDPR Alignment: Where client storage involves the processing of pseudonymous identifiers, processing is grounded in GDPR Article 6(1)(b) (performance of a contract) and GDPR Article 6(1)(f) (legitimate interest in platform integrity and cybersecurity).

Section 3

Strictly Necessary Authentication & Security Cookies

3.1 Authenticated Session Identifiers (auth_token and session):

When an adult user authenticates as a Searcher, Lister, or Administrator, the platform issues cryptographically signed JSON Web Tokens (JWT) stored in HTTP cookies to maintain authenticated session integrity across requests:

  • Cookie Names: auth_token and session.
  • Technical Purpose: Authenticating the user across protected API endpoints (/api/*), personal dashboards (/dashboard/*), and administrative consoles.
  • Storage Mechanism: HTTP-only cookies delivered with HttpOnly, preventing client-side JavaScript execution or XSS exfiltration.
  • Secure Transmission: Configured with Secure in production, ensuring cookies are transmitted strictly over encrypted TLS/HTTPS connections.
  • Cross-Site Request Handling: Configured with SameSite=Lax to protect against CSRF attacks.
  • Lifespan: 7 calendar days (maxAge: 604,800 seconds), unless invalidated earlier through active logout or security locks.

3.2 Cryptographic Token Versioning & Global Session Invalidation:

The signed session JWT contains an integer tokenVersion counter. Upon password modification, 2FA reconfiguration, or selecting "Log Out of All Devices," the database-level token counter increments atomically, revoking access across all devices in real time.

3.3 Security Nonces & Dynamic State Protection:

Cryptographic CSRF tokens validate form mutations, and ephemeral handshake tokens coordinate 60-second time-sensitive rotating HMAC QR codes and 4-digit mutual arrival PINs during in-person doorstep verification.

Section 4

Local Storage, Client-Side Caching & Progressive Web Application (PWA) Tokens

4.1 PWA Installation State & Dismissal Preference: Key silkly_pwa_dismissed_at stored in HTML5 LocalStorage records a UNIX timestamp when a user dismisses the install prompt, establishing a cooldown window to prevent repetitive prompts.

4.2 Service Worker Cache & Offline Application Shell: Browser CacheStorage executed by sw.js caches static, pre-compiled application shell assets (CSS, WebP icons, client JS) to facilitate sub-second loads. The service worker cache is strictly restricted to public static assets and never stores unencrypted profile data or credentials.

4.3 Native Web Push Notification Tokens (VAPID): Cryptographic push endpoints stored locally enable device lock-screen alerts for critical escrow events via APNs and FCM under RFC 8292 VAPID.

4.4 Transient UI Preferences: SessionStorage retains active search filter parameters (distance radius, sort order) during an active browsing session to preserve interface continuity without external tracking.

Section 5

Doorstep Handshake Ephemeral State & Cryptographic Nonces

5.1 Rotating HMAC Handshake Nonces: Maintained strictly in volatile browser application memory (window state) and encrypted server cache. Nonces refresh every 60 seconds and are never written to permanent disk storage or persistent cookies.

5.2 Instant Post-Verification Purge: Upon successful mutual arrival verification (via camera QR scanning or 4-digit PIN entry), the active handshake nonce is consumed atomically and permanently destroyed across client memory and backend session state.

Section 6

Third-Party Script Shielding & Zero Ad-Tech Guarantee

6.1 Exclusion of Third-Party Ad-Tech: Silkly completely excludes third-party behavioral analytics, cross-site identity trackers, fingerprinting scripts, and advertising pixels. All application fonts, design tokens, and interface icons are served directly from platform infrastructure and cached via our European CDN pull zone (Bunny.net).

6.2 Web3 Wallet Injections & EIP-1193 Providers: When interacting with non-custodial smart contracts on Base, client browsers interact with injected Web3 provider objects (e.g. window.ethereum). Silkly does not store or track browser extension signatures within persistent terminal cookies.

Section 7

Complete Storage Audit Matrix & Lifespan Inventory

Silkly maintains an exhaustive inventory of all client-side storage mechanisms:

auth_tokenHTTP-Only Cookie

Primary JWT authenticating user across protected endpoints. HttpOnly, Secure, SameSite=Lax. Lifespan: 7 days.

sessionHTTP-Only Cookie

Auxiliary session verification token to prevent session desynchronization. Lifespan: 7 days.

silkly_pwa_dismissed_atHTML5 LocalStorage

Records timestamp of install prompt dismissal to establish a cooldown window. Never sent to server.

push_subscription_tokenIndexedDB / PushManager

Browser push notification endpoint for lock-screen alerts. Activated strictly upon explicit user opt-in.

service_worker_cache (sw.js)CacheStorage API

Pre-compiled static interface assets, CSS stylesheets, and WebP icons. Updated on each deployment.

Section 8

Browser Controls, Revocation & GDPR Erasure Rights

8.1 Autonomous Browser Management: Users maintain full autonomy to inspect, block, or delete cookies and terminal storage items directly through client browser settings (Chrome, Safari, Firefox, Edge, or mobile browsers). Note that disabling session cookies prevents login and dashboard access.

8.2 Alignment with GDPR Article 17 Account Deletion: When a user initiates account deletion via /dashboard/security, the account enters a 72-hour reversible grace period. Eligible closure revokes sessions. Retained records remain identifiable for purpose-based review, and irreversible deletion is disabled pending appropriate approvals.

Section 9

Sub-Processors, Storage Residency & CDN Caching

9.1 Sovereign European Domicile: All server compute, database clusters, and cloud storage operate strictly within EU data centers: Scaleway S.A.S. (Paris & Amsterdam), Bunny.net (Slovenia Anycast DNS/CDN), Proton AG (Switzerland zero-access SMTP), and Didit Me S.L. (Spain AML KYC).

9.2 Edge CDN Cache Invariants: Edge caching across Bunny.net pull zones is strictly confined to publicly published, privacy-sanitized WebP media assets stripped of all EXIF/GPS telemetry. Edge nodes do not cache or inspect authentication cookies.

Section 10

Digital Services Act Compliance, Dark Pattern Prohibition & Defensive Integrity

10.1 Dark Pattern Prohibition (DSA Article 25): Silkly eliminates manipulative cookie banners, deceptive pre-ticked consent toggles, and asymmetric choice architectures designed to coerce tracking acceptance. Directory browsing is 100% accessible without tracking scripts.

10.2 Bot Defense & In-Memory Rate Limiting: Sliding-window rate limit counters operate in volatile server memory without tracking cookies, canvas scanning, or device fingerprinting.

10.3 Defense Against Session Hijacking & CSRF: Cookies enforce HttpOnly, SameSite=Lax, and Secure flags with synchronized CSRF tokens for all state-changing mutations.

Section 11

Policy Amendments, Audits & Technical Interoperability

11.1 Ongoing Technical Audits: Silkly conducts regular code audits to ensure zero extraneous storage keys or third-party analytics libraries are introduced into production builds.

11.2 Privacy Sandbox Interoperability: Structures terminal storage to align with CHIPS (Cookies Having Independent Partitioned State) and modern browser context partition standards.

Section 12

Supervisory Authorities, Governing Law & Statutory Contact

12.1 Regulatory Lead Authorities: Compliance is subject to the administrative oversight of competent regulatory authorities in The Netherlands:

Telecommunications Lead:
Autoriteit Consument & Markt (ACM)
Bezuidenhoutseweg 73, Den Haag
acm.nl
Data Protection Lead:
Autoriteit Persoonsgegevens (AP)
Bezuidenhoutseweg 30, Den Haag
autoriteitpersoonsgegevens.nl

12.3 Corporate Domicile & Privacy Desk Contacts:

  • Operating Corporate Entity: Silkly B.V. (in formation)
  • Physical Registered Office: [Registered Office Address in Amsterdam, The Netherlands – to be updated upon KVK registration]
  • Primary Compliance Desk: hi+compliance@silkly.top
  • General Operational Inquiries: hi@silkly.top