Privacy and Cookie Policy

TODO(Durham): Finalize this policy before Morphly collection goes live. This scaffold documents the intended CYS pilot: consented, first-party analytics and intent measurement only, with no Morphly rewrite of affiliate CTAs.

Current status

This page is a legal-review scaffold. It describes the intended technical design for the Morphly pilot and flags the sections Durham must finalize before production collection is enabled.

What the Morphly pilot may collect

After analytics consent, the intended categories are:

An anonymous first-party Morphly visitor identifier.
On-site behavior events such as page views, clicks, and dwell time.
Allowlisted campaign parameters such as utm_source, utm_medium, utm_campaign, utm_term, and utm_content.
Page paths without query strings.
Coarse device context such as mobile, tablet, or desktop.

TODO(Durham): Finalize the exact category names, retention language, and jurisdiction-specific disclosure text.

First-party measurement only

The intended pilot runs as a client-side snippet on Change Your Strings pages. Morphly's technical documents describe first-party collection on the client site, tenant-scoped site keys, origin allowlists, and no cross-site account data.

TODO(Durham): Convert that technical posture into final legal wording.

Consent and choices

The CYS integration does not inject the Morphly loader until production has a public site key and the visitor has granted analytics consent. Visitors can accept, decline, manage choices, or opt out.

Choosing Opt out stores declined consent, asks Morphly to delete the current profile when its API is available, and clears the local Morphly visitor cookie.

Cookies and local storage

_mly_consent

Stores analytics and personalization choices in localStorage.

Written when the visitor accepts, declines, or saves choices.

_mly_id

Anonymous first-party Morphly visitor identifier used only after analytics consent.

Created by Morphly after the consent-gated loader runs. Opt out clears it.

Processors and subprocessors

Morphly's template describes Morphly as a data processor for client sites, with Cloudflare as infrastructure and Anthropic only as an optional generated-content service. The CYS pilot is measurement only and does not enable generated content.

TODO(Durham): Confirm processor, subprocessor, DPA, and deletion wording before collection goes live.

Affiliate links

Change Your Strings uses Amazon Associates affiliate links. In this pilot, Morphly is not allowed to replace affiliate CTAs or rewrite page content. Affiliate links continue to render through the protected CYS affiliate components.

Deletion requests

TODO(Durham): Finalize deletion request handling. Until that wording is complete, privacy requests can be sent to hello@changeyourstrings.com.