Privacy

The library

• No telemetry. WolfXL does not collect usage analytics, crash reports, or feature metrics from your runtime.
• No phone-home DRM. There is no license activation call, heartbeat, or runtime usage tracking. Access is regulated by a private package index credential, not by code that runs inside your workbook pipeline.
• Required dependencies. WolfXL and its required runtime dependencies are served from the authenticated index configured in your package manager.

Website analytics

• Limited, cookieless measurement. The public website uses PostHog to measure page views and clicks on explicitly tagged navigation, licensing, and evaluation actions. It does not set analytics cookies or use local or session storage for analytics identifiers.
• Event data. Analytics events may include the event type, page path, referring page, timestamp, browser and device information, and network metadata processed by PostHog. Query strings and URL fragments are removed before an event is sent. PostHog may receive an IP address while handling the network request; the production PostHog project must discard IP addresses from stored events.
• Capture limits. Website analytics do not create person profiles, identify visitors, record sessions, capture form values or page text, collect application exceptions or performance traces, or enable heatmaps, surveys, feature flags, advertising, or cross-site tracking.
• Browser privacy signals. Analytics remain disabled when the browser sends Do Not Track or Global Privacy Control. PostHog processes events under its privacy terms.

The purchase

• Stripe processes payment. WolfXL does not receive or store your full card number. Stripe handles the transaction under its own terms.
• Purchase records. The WolfXL ledger stores the details needed to fulfill and support the purchase: email, customer legal name, tier, intended use, server-derived seat count, Stripe checkout session identifier, agreement and authority evidence, fulfillment status, acquisition attribution, and timestamps.
• Owner alerts. A purchase alert is sent to the owner so access can be provisioned. This includes the email, customer legal name, tier, intended use, and seat count, not payment card data.
• Acquisition attribution. The browser may keep bounded campaign parameters and the referring hostname in session storage for the current tab so they survive navigation. Checkout and the evaluation request form also ask how you found WolfXL. These values are sent and stored when you submit one of those two forms. WolfXL stores no referring path, query string, or browsing history.

Evaluations and package access

• Evaluation requests. Submitting the evaluation request form stores what you typed: the named evaluator, work email, customer legal name, workbook format, described workflow, required operations, optional success criteria, acceptance of the evaluation terms, the nonproduction attestation, acquisition attribution, and timestamps. A request is a record of interest and a triage status, not access.
• Request alerts. A request alert is sent to the owner so the evaluator and customer identity can be reviewed. It contains the same request fields and no payment data.
• Evaluation records. A 30-day evaluation record stores the named evaluator, email, customer legal name, stated use case, agreement acceptance evidence, start and expiration timestamps, and credential status.
• Credential storage. WolfXL stores a one-way SHA-256 digest of each issued package credential. The plaintext secret is written once to the operator-selected secure delivery file and is not stored in the commerce database.
• Package service records. Package-index and hosting systems may process the credential identifier, requested package path, timestamp, IP address, and routine security logs to deliver packages, investigate compromise, and enforce access.

Data we do not collect

We do not sell buyer or website analytics data, use analytics for advertising, create identified visitor profiles, or record browsing sessions. Website analytics capture no form values or page content, and do not run inside the WolfXL library or package. Fields you submit in the checkout or evaluation request forms are stored only as described above.

Questions

For privacy questions, contact us from your purchase email.