PUBLIC CANCELLATION HELP · NO PAID ACCESS REQUIRED

Cancel renewal yourself—or reach a person if you cannot.

When you can sign in, METRAXIOM provides a direct self-service cancellation control for the Stripe subscription linked to your workspace. Cancellation does not depend on accepting updated terms, starting another subscription, or keeping paid access active. Andre Jason Watts remains the direct fallback contact if the signed-in route is unavailable.

Open cancellation confirmation Fallback cancellation email

NORMAL ROUTE

Use the direct cancellation control when you can sign in.

Open Plan + Billing cancellation for the affected workspace.
Select Cancel subscription.
METRAXIOM displays an explicit Yes, cancel my subscription / No, keep subscription confirmation. Nothing is canceled merely by opening the page.
Choose Yes, cancel my subscription for the direct route. METRAXIOM submits the cancellation to Stripe for the exact linked subscription. You do not need to email support or wait for manual processing.
If you prefer provider-hosted confirmation, choose Review cancellation in Stripe instead. That opens Stripe's focused cancellation flow for the same subscription.
The page reports whether the subscription is already canceled or scheduled to end at the current billing-period boundary. When transactional email is configured and deliverable, METRAXIOM automatically sends a cancellation acknowledgment to the account email.

Cannot sign in or use either self-service route?

Email the address shown here. A proportionate identity or authority check may be required, but you will not be required to accept unrelated new terms or buy or maintain paid access merely to request cancellation.

FALLBACK ONLY

If the signed-in routes fail, send only what is needed to locate and verify the subscription.

Include

The email used for billing.
The customer or organization legal name.
The workspace display name and plan, if known.
An approximate signup or invoice date.
Your relationship to the customer and authority to make the request.

Do not include

Passwords or authentication codes.
Full or partial payment-card details.
API keys, secrets or recovery codes.
Classified, CUI/FCI, export-controlled, health or unnecessary measurement records.

Opening an email application is not delivery confirmation.

A fallback request becomes “cancellation requested” only after METRAXIOM expressly acknowledges receipt or records the verified request. If no acknowledgment arrives, check your sent/outbox status and resend or use the signed-in cancellation control if it becomes available.

STATUS MEANS SOMETHING PRECISE

Requested, scheduled and canceled are different states.

Cancellation requestedA verified fallback request has been expressly acknowledged; provider completion is not yet represented.

Scheduled to cancelThe reconciled Stripe state reports cancellation at the end of the current billing period.

CanceledThe reconciled Stripe subscription state is canceled.

Cancellation stops renewal according to the confirmed timing. It does not automatically refund prior charges, silently delete the account or retained measurement records, or change optional promotional-email preferences. Refunds, deletion and marketing preferences are separate processes.

Account deletion Promotional email preferences Contract withdrawal information

Automatic counts. No individual tracking.

TRACE counts approved public page requests worldwide without an analytics consent banner. No visitor identifiers, fingerprints, individual browsing histories or GPS locations are collected.

Analytics privacy update · October 29, 2026

TRACE automatically measures aggregate requests to approved public METRAXIOM pages worldwide to improve content, navigation and reliability. It runs at the first-party hosting proxy, before the hosting page cache, and works when JavaScript is disabled. No analytics consent banner or country-based opt-in selection is used.

The basic store contains separate hourly totals for approved pages, country and US-state labels, common referral domains, broad device/browser/operating-system families and unverified request categories. It contains no individual request ledger, full IP addresses, raw user agents, full URLs or queries, visitor identifiers, fingerprints, session histories or GPS coordinates. Country labels come from hosting network metadata and can describe a VPN or network exit. Missing geography is recorded as unavailable. No city, address or coordinates are collected. US-state labels come only from the trusted hosting header; other state/region labels remain unavailable. Software names are broad, spoofable claims, with no versions or cross-request fingerprint.

GPC, DNT and an explicit traffic objection stop collection. Earlier “Keep analytics off” choices saved only in browser storage are carried forward as objections when JavaScript runs on a public application page. They are not sent with the initial HTTP request: that request, JavaScript-disabled requests and static-only visits may contribute until an objection cookie or privacy signal is sent. Exclude this browser from traffic measurement without an account or JavaScript. The preference cookie uses the same value for everyone who excludes traffic (1) or explicitly restores basic measurement (0), lasts up to 180 days and does not identify you. Restoring basic measurement preserves the old local choice; it can apply again after the restore preference expires or is cleared. Restoring aggregate measurement does not override privacy signals or grant individual tracking permission. Earlier aggregate counts cannot be linked back to you or selectively removed.

When you choose a dashboard view, a separate functional reporting-preference cookie remembers only the preset or calendar dates for up to 30 days, scoped to /traffic. It is not used by the collection layer and contains no identifier or consent grant. Use Forget saved reporting view, including without JavaScript, to remove it. A failed refresh may display a clearly dated snapshot held briefly in page memory; it is never relabeled as current or replaced with fabricated zero counts.

Individual browser analytics is disabled in this aggregate-only rollout. The former optional browser collector is not loaded, its intake is retired, and no new tab/session events are accepted. Earlier consent records are not rewritten as new permission. Previously collected optional events follow their existing 30-day retention and integrity-checkpoint policy.

Page requests are separate from verified page rendering or unique people. Navigation requests, crawler claims, link previews, other automation and unknown requests remain separate. Estimated visitors and session histories are unavailable. Small labeled groups are combined in public reports. Counts are aggregate observations and do not establish identity, intent or endorsement.

Recognized health checks, HEAD requests, prefetches, server-component fetches and private/API/unapproved paths are excluded. Browser memory/disk cache, back-forward restores, client-only navigation, privacy objections, missing metadata and storage failures leave coverage gaps. Request retries and spoofed software labels can affect totals. The system does not extrapolate missed traffic or import historical Vercel Analytics counts.

Hourly counter buckets are retained for 30 days and pruned hourly in bounded runs; calendar reports exclude older hourly data even if maintenance is delayed. Separate cumulative marginal totals, with no event times or cross-dimension links, remain for the life of the site’s traffic record. Changing a date range, leaving the page or closing a browser does not erase those totals. Earlier uncollected state/software labels remain unavailable, not reconstructed. Vercel delivers the website and Supabase stores TRACE aggregates in the existing United States database. Provider security logs and backups have separate policies. TRACE adds no paid analytics feed or operator-computer dependency.

This October 29, 2026 supplement updates the analytics description in the September 7, 2026 Privacy Notice. It does not amend frozen agreement snapshots or claim that server-side processing is automatically exempt from privacy law. The assessment concerns this limited data flow and its controls; no universal regulatory approval is claimed. Privacy requests: ANDREWATTS23@gmail.com.