Known Constraints & Non-Goals

1. Infrastructure Provisioning

Status: Out of Scope. Detail: The "Infrastructure Provisioner" (a generic Hetzner-based microfunction) handling ROUTING_MAP updates is an external dependency. This documentation covers the consumption of that map, not its creation.

2. Client-Side Consent UI

Status: Non-Goal. Detail: The platform does not provide a Cookie Banner or CMP. It expects the client to handle legal compliance (GDPR/CCPA) before sending data to the tracking endpoints.

3. PII Storage

Status: Constraint. Detail: The platform is designed to be privacy-forward.

• IP Addresses: Hashed immediately (ip_hash) or discarded. Never stored in raw form in persistent databases.
• Payloads: GTM payloads are opaque and not inspected/stored by the platform (except for transient processing).

4. Legacy Features

Status: Deprecated / Support Only. Detail:

• fingerprint: An older browser fingerprinting module exists in the codebase but is gated and largely superseded by FPID cookies. New implementations should avoid relying on it.
• FPID2: A legacy cookie format supported for backward compatibility but no longer generated for new sessions.

5. Stripe Webhooks

Status: Implementation Detail. Detail: The stripe-webhook Edge Function handles payment events. While critical for billing status, it does not interact directly with the tracking data plane and is documented separately in the Billing Subsystem docs.