Skip to main content

Data Flow & Privacy

This page explains, at a high level, how user and quote data flows through the Infowebplus system and where it is stored.

It is intended as a starting point for privacy reviews and compliance documentation.

High-level architecture​

From the architecture documentation, the main components involved in data processing are:

  • Next.js App – Frontend and API routes.
  • Sanity CMS – Content and structured quote data.
  • Redis / Caching layer – Performance caching.
  • HubSpot CRM – Lead and contact management.

See:

Quote calculator data flow​

When a user interacts with the quote calculator:

  1. User provides selections and contact details in the browser.
  2. The browser sends data to the quote API (/api/quote/track and /api/quote/submit).
  3. The server-side logic:
    • Validates the payload.
    • Stores structured quote data and tracking metadata in Sanity.
    • Creates or updates a contact in HubSpot with quote-related custom properties.
  4. A PDF summary can be generated and delivered to the user.

See:

Storage locations​

Based on the documentation:

  • Sanity CMS
    • Quote configuration and content.
    • Quote submissions and tracking metadata.
  • HubSpot
    • Contact records and quote-related custom properties.
  • Redis / Caching
    • Cached responses and content fragments (non-authoritative, time-limited).
note

Cached data is a performance optimization and should be treated as a transient copy of the source-of-truth data in Sanity and HubSpot.

Personally identifiable information (PII)​

PII that may be processed includes (depending on how forms are configured in the main app):

  • Name
  • Email address
  • Company
  • Phone number
  • Country/region

These are primarily stored in:

  • HubSpot contact records.
  • Sanity quote documents (as documented).
TODO

Review the main application repository and HubSpot/Sanity schemas to confirm the exact PII fields collected, their retention policies, and legal bases (e.g., consent, legitimate interest). Update this section accordingly.

Tracking and analytics​

Documentation references:

  • Google Tag Manager for analytics.
  • Additional tracking around quote calculator usage.

See:

TODO

Audit the actual tracking implementations (GTM tags, custom events, cookies) in the main application repo and analytics tools, then document:

  • What events are tracked.
  • What identifiers are used.
  • How consent and opt-out are handled.