Privacy for analytics, client reporting and feedback

Cloudflare Web Analytics provides an independent aggregate view of eligible public pages. Its manual beacon loads only on blursor.ai, never on private monitoring or API routes, and is suppressed when this browser is excluded. To avoid exposing details that cannot be reduced before Cloudflare’s script runs, BLURSOR does not load that beacon when the current address contains a query string or fragment, or when the referring address contains more than a safe origin or recognized BLURSOR path. Cloudflare processes the eligible page address and ordinary request, browser, device, and approximate network-location metadata used for its aggregate reports. Cloudflare says it retains unsampled beacon data for seven days, then aggregates it to around 10% for longer-term storage; dashboard queries can be dynamically sampled, and Web Analytics data is accessible for the previous six months. Its bot filtering, coverage limits, and sampling mean these figures are a comparison, not a census of every visitor.

Google Analytics 4 loads only after you select “Allow analytics.” BLURSOR sends one explicit view for the known canonical page, using its static title and a bounded page group. External referrers are reduced to their origin; recognized BLURSOR referrers retain only their canonical path. Of the query parameters, only short values for utm_source, utm_medium, utm_campaign, and utm_content are accepted. Audit measurement records bounded lifecycle labels such as single or comparison mode, form or shared-link entry, completion or partial outcome, and a broad technical error category. Selected audit links and links to Beamtrace, Alex’s website, and Alex’s LinkedIn profile are counted by category.

BLURSOR does not send the page you audit, a comparison URL, a feedback comment, an email address, a token, a credential, a fragment, or a feedback submission ID to either analytics report. Google Signals, advertising features, automatic page views, and enhanced-measurement history tracking are disabled. GA4 event data is retained for 14 months. Returning-user reporting is limited to browsers that consent and keep Google’s identifiers.

The analytics choice is stored in this browser for 180 days. If browser storage is unavailable, the choice lasts only for the current document. Use Analytics preferences in the footer to allow, decline, or withdraw Google measurement. Withdrawal stops future Google events and removes the Google Analytics cookies this implementation can access. The same choice is propagated to other open BLURSOR tabs. Selecting Exclude this browser from measurement suppresses both providers on subsequent eligible loads; BLURSOR does not infer internal traffic from an IP address, location, or VPN.

For a private client workspace, BLURSOR can collect Google Search Console reports for the website property the client authorizes. A BLURSOR operator connects a Google account with read-only access. We use the account’s verified email address and Google account ID to confirm which account was connected.

Reports contain dates, clicks, impressions, reporting filters, and the underlying API responses used to check the figures. Reports may separate brand searches from selected service searches. They do not identify individual website visitors. We use this information to report search performance and compare completed reporting periods.

Cloudflare hosts the private workspace and stores its reports. Only authorized workspace members and BLURSOR operators can access those reports through the app. Reporting credentials are stored in server secrets; an encrypted backup may be kept on the operator’s computer. We do not sell Search Console data or use it for advertising. Search Console reports are kept separate from the dashboard’s automated AI tests.

Reporting history is kept until it is removed from the workspace. To request deletion or disconnection, email contact@blursor.ai. Removing the reporting account’s property access, or revoking the app’s access in Google, prevents future collection. It does not automatically delete previously saved reports; those can be removed separately on request.

Choosing a rating opens an optional comment field. Pressing “Send feedback” sends one email to Alex through Resend, containing your rating, any comment, the tested page address (and comparison page if used), the audit times, and the feedback submission time. We remove URL query strings, fragments, and embedded credentials. We do not request your email address. Closing the card without submitting sends nothing. Avoid putting private information in a comment.

Feedback stays in Alex’s email inbox and may be processed by Resend and Gmail under their retention practices. You can request deletion at contact@blursor.ai; include the approximate date and wording so we can find it.

We store a cooldown date in this browser so the card does not automatically appear again for 30 days after being shown, or 180 days after you send feedback. Clearing browser storage resets this preference. Closing the Leave feedback button hides both the button and automatic card until you refresh the page; this dismissal is not saved. If storage is unavailable, the card only opens when you ask. A random submission ID is used internally to prevent duplicate emails when retrying. Spam limits use keyed hashes of the requesting IP address; those records expire after 48 hours. Feedback does not subscribe you to emails.

When you submit the contact form, your name, email, message, and any website or topic you provide are sent to HubSpot, where Alex manages inquiries. The form does not load HubSpot’s tracking script or send your message to analytics. You can request deletion by emailing contact@blursor.ai.

We use this information to confirm that you asked for the reports, check the selected page once a week, send one result each week, highlight meaningful changes, prevent duplicate or abusive requests, and maintain reliable delivery. A report may also include one relevant new BLURSOR research link.

Cloudflare provides the site, Workers, D1 database, Queue, Turnstile spam protection, and Browser Rendering used by the monitoring system. Requests may also appear in Cloudflare logs and short-lived edge or render caches. The client sign-in at /access keeps a count of attempts for each IP address in Cloudflare’s edge cache, so it can limit them to ten an hour; each count expires within the hour, and BLURSOR does not keep the token you enter.

Google provides Google Analytics 4 after consent. Its measurement is used for aggregate acquisition, page, audit, and consenting-browser retention reports, not advertising.

Resend sends confirmation, management, and weekly emails. Resend may retain transactional delivery metadata under its own retention practices, including after we delete the corresponding BLURSOR subscription record.

An unconfirmed request expires after 24 hours. While monitoring is active, we keep the email address, selected URL, current comparison baseline, delivery records, and the newest eight weekly summaries needed to produce and support the reports.

If delivery is paused after a hard bounce, complaint, or provider suppression, the paused BLURSOR record is removed after seven days. Abuse-prevention records expire after 48 hours, and Resend webhook replay records expire after seven days.

Every weekly report includes an unsubscribe link. Unsubscribing deletes the subscription and its dependent audit and delivery records from our D1 database. You can also replace the monitored page after confirming the change; the previous comparison baseline is then cleared.