PRIVACY & STORAGE
Control consent, masking and recording exclusions.
Control when recording starts, protect private elements and handle withdrawal.
In this guide 12 sections
What stays in a recording
#Eligible visitor activity travels from the browser to the website’s WordPress database; eligible design snapshots stay on that website’s server. Authorised reviewers open that local evidence. Pro licence validation is a separate connection and does not carry replay payloads.
| Content or page | Recording boundary | Owner’s check |
|---|---|---|
| Ordinary page text | Readable by default; it can contain personal information outside form inputs. | Mask or exclude sensitive page regions and inspect a test replay. |
| Entered field values | Protected rather than included as form answers. | Use synthetic values to verify the relevant fields and private regions. |
| Public design assets | Only eligible styles, images, backgrounds, fonts and safe SVG geometry. | Review capture settings; private or unsupported content is not made public. |
| Cart and checkout | Excluded by default; deliberate inclusion requires full page-text masking. | Review the complete flow before enabling any supported inclusion. |
| Account, order-pay and order-confirmation pages | Remain excluded. | Keep exclusions intact. |
| Optional Pro feedback | Requires current visitor consent and an eligible recording. | Recording without asking first does not grant feedback consent. |
Recording settings do not establish legal compliance. The website privacy notice separately describes ClickClue’s own website, licensing and support services.
Understand the defaults
#The small recording loader runs first. Capture loads only after the saved recording mode, visitor privacy choices, sampling and server authorisation permit it. Banner modes wait for visitor permission. Record without asking first uses an explicit owner policy and does not create a positive visitor-consent choice. Form values are always masked. From 1.2.7, non-empty form values use a fixed-length mask so their original length and spaces are not retained; empty values stay empty. Older stored recordings, exports and backups are not rewritten by this change. Ordinary page text stays readable on new installations; enable Mask all page text to hide it too. Existing saved masking choices stay unchanged on upgrade, and private regions remain protected.
Do Not Track and Global Privacy Control stop recording. Signed-in users and administration, login, account, order-pay and order-confirmation paths are excluded. Cart and checkout are also excluded by default, including configured WooCommerce pages, custom slugs and plain permalinks. Browser navigation into an excluded path stops active capture.
Include cart and checkout pages is an advanced opt-in that requires Mask all page text. Test Classic or Blocks checkout with your actual theme and gateway using sample details before enabling it. Account, order-pay and order-confirmation exclusions remain. Personal text shown outside a form is ordinary page text elsewhere too: mask it or exclude its region.
- Capture public design assets saves eligible public images, backgrounds and fonts into shared local snapshots. It starts on for fresh installations and off on upgrades until explicitly enabled. Private regions still take priority. Legacy individual image approvals remain available.
- Safe SVG geometry can remain. SVG scripts and foreign content, canvas, audio, video, embedded frames, hidden inputs and editable regions remain excluded. Separate SVG files require the PHP DOM extension; unsupported files are omitted safely.
- URL query values and fragments are removed, except a verified public WordPress post or page ID used to distinguish plain permalinks. Recorded links and arbitrary asset URLs are stripped.
- Replay reconstructs the page. Dynamic or complex layouts can differ from the original; inspect a sample visit on your actual theme.
Choose how recording starts
#New installations have no recording mode selected and remain paused until the final Save & enable recording action. All three choices have equal standing in setup and remain available in Settings. Existing installations keep their former behavior: the built-in banner remains the banner mode, and a connected external-consent setup remains external. An upgrade never silently chooses recording without asking first.
The existing Pro feedback and order-association integrations still require a visitor-consent recording. Owner-policy capture does not widen those integration permissions.
- Ask with ClickClue’s banner: display the built-in prompt and wait for replay acceptance. A published privacy policy must be selected in WordPress before setup can finish.
- Use my existing consent banner: wait for your connected banner to call the local consent APIs. Installing another banner alone is not an integration. Test acceptance, refusal and withdrawal.
- Record without asking first: start eligible signed-out visits under the owner’s explicitly chosen policy. No permission prompt or positive visitor-consent choice is created. Provide a floating button or your own footer/menu or connected privacy control so visitors can stop and delete the current recording.
- Every mode respects valid refusals, Do Not Track, Global Privacy Control, unresolved deletion requests, signed-in/private-page exclusions, masking, sampling and storage protections.
Public design snapshots
#When Capture public design assets is enabled, eligible public local images, backgrounds and fonts are saved once and shared by recordings that use the same bytes. A later change to a file does not replace an older saved copy. Theme/plugin assets and public WordPress media attachments are eligible; private files and arbitrary remote URLs are not.
To preserve Google Fonts already used by a page, the browser can reread its public font stylesheet from fonts.googleapis.com without cookies or referrer, and the server can copy font binaries from fonts.gstatic.com. Google receives the respective browser/server IP and font request, never recording contents. Original public raster images retain their quality and may retain embedded metadata. Files over 8 MiB, unsupported formats and unsafe SVG content are omitted; a missing asset does not erase the recording.
Turning public design capture off stops new asset copies. Existing copies follow the linked recordings and are removed after their last recording is deleted or expires. Old recordings cannot recover assets that were never captured. Keep Mask all page text enabled when that is your intended policy; typed values and private regions remain protected in either setting.
Styling and older recordings
#Free 1.2.4 checks captured CSS for private text and unsafe URLs before storage. Older recordings are checked when read, including compatible Pro 1.2.4 recording exports; the player also keeps its privacy checks. Supported public layout, font and icon styling can remain.
Stored cleanup of older CSS runs in bounded background batches through WP-Cron and dashboard activity. Keep WordPress cron working and check reported cleanup problems. Backups and files already exported are not rewritten. Review their access and retention separately.
This does not detect every piece of personal information in ordinary page text, images, classes or IDs. Exclude sensitive regions and test your actual pages with sample details. Keep Mask all page text enabled wherever your recording policy requires it.
Organise approved public images
#The older individual-approval image option remains off by default and is separate from Capture public design assets. Explicitly approve individual public static WordPress attachments and organise them into named collections. The catalogue holds up to 256 approvals. Add or move images in groups of up to 16; browse 12 previews per page. Moving between collections does not alter consent. The separately bounded prepared catalogue holds about 46 MiB of encoded image data and URL metadata. Image copies stored with recordings count toward the recording payload budget.
A recording saves only used copies, bounded to 64 images and 2 MiB within its existing payload allowance. Images are prepared locally without metadata; only supported same-origin local URLs are matched. Private and masked regions always take priority. No arbitrary image URL is fetched.
Removing an individual approval or switching the older image-copy option off removes its affected retained copies. Automatic public design snapshots instead remain until their linked recordings are deleted or expire; disabling that option stops new copies. Downloaded exports and backups need separate handling. Updated capture scope requires current authorisation; banner modes can require a renewed choice.
New 1.2.6 recordings can include clicks on eligible public or approved images. This evidence uses a safe structural identity and position; it does not send raw image source or alternative text as click metadata. Private regions and image-source filtering remain in force.
Publish your notice and keep the recording basis clear
#In WordPress Settings → Privacy, select a published page with your operator identity, privacy contact, replay purpose, legal basis, recipients, retention, transfers and visitor rights. Adapt the ClickClue suggested text there. The built-in prompt links to this page and blocks capture if it is missing. Allow replay and No thanks have equal visual prominence.
In banner modes, browser-reported permission includes a reported choice time and notice revision. This is not independent proof that a person made the choice. Older positive signals or relevant notice/retention/masking/edition changes can require a fresh signal; a valid refusal stays refused. Changing the recording mode also invalidates earlier authorisation. Clear page/CDN caches so visitors receive the current loader and revision.
New recordings retain the client-reported recording basis, server acceptance time, matching revision and retention deadline. A browser assertion or signed admission ticket does not prove a human clicked a banner or gave informed consent. Owner-policy capture is distinct from client-reported visitor consent. Increasing retention later does not extend an existing deadline. A changed notice stops uploads under earlier authorisation. Keep appropriate dated notices and any independent CMP records.
Finish your website-specific privacy setup
#This is a configuration guide, not a compliance certificate. Establish your controller/processor roles, applicable national cookie rules, access controls, processor agreements and international-transfer arrangements. Assess whether a DPIA and a DPO are required for your actual processing before collecting real visits.
Document how you receive and answer access, erasure, objection and other rights requests, normally within one month. The current-visit withdrawal token is not an identity search across every visit. Do not collect new identity data just to make anonymous visits identifiable.
Review cleanup, backups, exports and enabled email/AI/agency services separately. Maintain an incident response process, including authority notification within 72 hours when required and notification to affected people when the applicable threshold is met. Keep your local legal review and decisions with the installation record.
Exclude sensitive regions
#Add data-tw-block to a private element or enter its CSS selector in Settings → Recording & privacy. Existing data-private and .rr-block regions are also excluded.
Structural classes and IDs may remain for layout. Exclude elements whose attributes contain personal information. Inspect dynamic content, account widgets and order details in a synthetic recording before real use.
Excluded page paths can use up to 2,000 UTF-8 bytes and additional selectors up to 500 UTF-8 bytes. Longer rules are rejected without changing saved settings. Review the error and shorten the list; ClickClue never silently cuts an exclusion to fit.
Built-in private-page rules match complete path parts: /my-account/ and its child pages stay excluded, while a public article such as /my-accounting-tips/ can record. The same applies to /order-pay/ versus /order-payment-faq/. Other custom page-path exclusions retain their existing substring matching, so review broad custom rules separately.
<div data-tw-block>Private customer information</div>Connect your existing consent banner
#Choose Use my existing consent banner in setup or Settings. This mode waits for your banner to grant replay permission and never assumes that another banner is connected. Wire and test the local APIs below before relying on capture. Call grant only after replay acceptance; call withdraw on refusal or later withdrawal.
This consent-based mode is separate from Record without asking first. Do not simulate visitor acceptance by calling grant for everyone on page load. The without-asking option uses its own explicit owner-policy setting instead.
The tracewell:status and tracewell:recording-started events include the current state in event.detail.status. The tracewell event names remain for compatibility. Read ClickClue.status() when connecting your listener for an initial state. These status events are not upload or server-deletion receipts; keep checking the relevant confirmation.
- Keep your current recording setup paused while connecting and testing the external banner.
- Test accept, decline, later withdrawal, cleared storage and the next page visit. A current notice revision is required by the start endpoint.
- Archive your CMP notice and consent records. Change the clickclue_consent_notice_revision filter value whenever your CMP replay purpose or notice changes, then clear caches.
- Use window.ClickClue.grantConsent() and window.ClickClue.withdrawConsent() for new integrations. Existing integrations remain compatible.
// Call after the visitor grants replay consent.
window.ClickClue?.grantConsent();
// Call when replay consent is withdrawn.
window.ClickClue?.withdrawConsent();
// Optional local status display; not an upload/deletion receipt.
window.addEventListener('tracewell:status', (event) => {
const status = event.detail?.status;
// Update your status display with this state.
});
const initialStatus = window.ClickClue?.status();Stop capture and confirm deletion
#Replay privacy lets the visitor stop and delete the current authorised recording in every mode, including recording without asking first. Capture stops immediately; a separate confirmation reports whether saved data was deleted. A saved refusal or opt-out is not cleared simply by changing modes.
A failed deletion keeps a tab-local retry token when session storage is available. Use Retry deletion; reloading that tab or reconnecting also retries. New capture stays off while deletion is unresolved. A former capture token can request deletion for up to 30 days after expiry, but cannot upload. Older recordings follow retention and administrator deletion.
Choose where Replay privacy appears
#The floating Replay privacy button remains off by default. Setup separately asks where visitors can stop recording: use the floating button, or confirm that you provide your own footer/menu or connected control. Choosing your own control is an owner declaration, not an automatic verification. Existing installations keep their button and recording settings and show a reminder if no placement is declared. This choice does not change the recording mode or hide the initial consent prompt.
To put the controls in your own footer or menu, add a custom link named Replay privacy with the URL #clickclue-privacy. On public pages where ClickClue runs, selecting it opens the controls even with the floating button off. The link does not grant permission. Visitors can stop recording and request deletion there.
A developer can also call window.ClickClue.openPrivacy() after ClickClue has loaded. Existing grantConsent() and withdrawConsent() integrations continue to work. Test while signed out: open your chosen control, stop the test recording and wait for deletion confirmation. This removes the current test recording. Paused recording, excluded pages and signed-in visitors do not load the recorder or its privacy panel.
<a href="#clickclue-privacy">Replay privacy</a>
// For a custom JavaScript control, after ClickClue has loaded:
window.ClickClue?.openPrivacy();