Help
Understand what moves and why.
Privacy starts with a clear account of the data required for the task.
Minimize the input
Supply only the context necessary for the authorized task. Avoid unrelated personal information, secrets, and credentials.
Inspect recipients
A product workflow may involve infrastructure, a model provider, or a connected tool. Know what each receives and for what purpose before authorizing processing.
Ask about retention
Understand which records persist, for how long, who can access them, and how deletion or a rights request works. A policy draft is not evidence of an implemented process.
Separate optional processing
Advertising, analytics, replay, and other optional tools need their own accurate disclosure and choices. No such SDK is configured in this candidate’s application code.
Current website behavior
The synthetic walkthrough uses page-bundled values and temporary browser-memory state. Page delivery still reaches the hosting edge. Contact intake remains closed until its operational and privacy gates pass.
Before product access
Actual Merism providers, retention, files, account controls, and connected-service behavior require a verified data map and operative disclosures before broader release.