Skip to main content
DISSFAM
PRIVACY / DATA USE

Know what moves before you provide it.

This is a scoped, fact-based data-use notice. It distinguishes the anonymous Assessment from the separate Contact form and existing infrastructure measurement.

NOTICE RECORD

Content owner
Dissfam site operations
Last reviewed
31 July 2026

IDENTITY BOUNDARY

Dissfam is the public and trading name used on this site. The current first-party claim registry does not release a separate incorporated entity or legal data-controller statement. This notice does not invent one. Until that identity and the required retention terms are approved, public Assessment answers are not transmitted or persisted and saved-report controls remain disabled.

01 / FLOW BY SURFACE

Different exchanges, different treatment.

FLOW 01

Anonymous Operating Assessment

Collected
Selected operating pains, numeric ranges, optional confirmed values, priority, currency, current system names, and editable modelling assumptions. No name, email, company name, free text, or file upload.
Purpose
Calculate an immediate on-screen operating summary and first-loop recommendation.
Storage
Browser memory only. No localStorage, cookie, Dissfam API request, model call, lead-system write, or custom analytics event.
Retention
For the current page session only. Reload, Clear assessment, or closing the page removes it.
Sharing
None by Dissfam because the answers never leave the browser.

FLOW 02

Private Opportunity Brief beta — not public

Collected
Production beta accepts only unmistakable synthetic Assessment records and .invalid email addresses supplied through the authenticated release-smoke path. The public visitor flow collects nothing for this surface.
Purpose
Verify report reconciliation, access, edit, export, deliberate share, revocation, code, expiry, logs, rate limiting, and exact deletion before any real-data publication decision.
Storage
Isolated aios_assessment_* MongoDB collections. Synthetic email is encrypted; tokens and codes are stored as keyed hashes; logs exclude answers, report text, and email content.
Retention
Synthetic report data carries a 30-day TTL and is deleted immediately after production smoke testing. One-time codes expire after 10 minutes, initial links after 7 days, and shares after 24 hours.
Sharing
No email is sent and no real identity or Assessment answer is accepted. The existing memorial RSVP sender is not reused.

FLOW 03

Contact form

Collected
Intent, name, work email, company, optional role, timeline, budget, problem summary, and a honeypot field.
Purpose
Validate the request, create a reference, and enable a considered reply.
Storage
The same-origin endpoint can write the validated record to a configured Notion database and can forward it to a configured lead webhook.
Retention
No approved duration or automatic deletion schedule is defined in this repository. Contact the address below for access, correction, or deletion; fulfilment is a manual operational process.
Sharing
Only the configured contact destinations and infrastructure needed to deliver the request. Contact submission is not marketing consent.

FLOW 04

Site delivery and baseline measurement

Collected
Standard hosting request metadata and the existing Vercel Insights site measurement. Custom Demo and Assessment event transport is disabled.
Purpose
Deliver, protect, and observe the public site at an infrastructure level.
Storage
Handled by the hosting/measurement provider under its service configuration. This repository does not set a custom analytics raw-event retention period.
Retention
Provider and account configuration apply; no new custom retention claim is made here.
Sharing
Vercel as the website hosting and baseline measurement provider.
02 / YOUR CONTROLS
  • Ask what commercial Contact record is held under your email address.
  • Request correction or deletion of that Contact record.
  • Withdraw a Contact follow-up request by emailing the address below.
  • Delete an anonymous Assessment immediately with Clear assessment, reload, or tab close.
  • No action is needed for the private report beta because public visitors cannot create a record.
Request access, correction, or deletion
03 / BOUNDARIES
  • There is no public saved, emailed, shareable, or persistent Assessment report. The implemented private beta is synthetic-only and protected by a server-side access key.
  • Report-delivery consent and marketing consent are separate records in the beta contract. Marketing is false unless explicitly selected; neither choice is presented publicly while collection is disabled.
  • Provider infrastructure may process across regions; no data-residency promise is made.
  • The production-frozen /dad family memorial is outside this commercial transformation and is not linked from the commercial site.
NEXT / NO EMAIL

Use the anonymous Assessment without transmitting your answers.

Your ranges, assumptions, and summary stay in browser memory. Clear them whenever you choose.

Assess your businessInspect the controls →