WolfSDKWolfXLWolfPPTWolfDocxWolfRender

Last updated: August 2026

Privacy

WolfXL limits data collection across the public website, purchases, evaluations, package access, support, and the library itself. The library has no telemetry or runtime tracking.

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

  • Cookieless page counts. wolfxl.com and wolfsdk.com count page views with Umami, an open-source analytics tool that runs on WolfXL's own server. It sets no cookies and stores nothing in your browser, so it runs without asking. For each page view it receives the public page name (pages outside the published list are reported only as "other"; account, sign-in, administration, and API pages never), the referring site's address without its path, and your screen size and browser language. The Umami server derives the browser family, operating system, device type, and approximate location (country, region, and city) from the request and does not store your IP address. To count visits it computes an identifier from your IP address, browser details, and a value that changes every month, so the same browser is recognised for at most a calendar month and never across sites. Query strings, URL fragments, page titles, page text, form values, and clicks are never sent, and the counts stay on WolfXL's server.
  • Your analytics choice. Beyond those page counts, the website asks before measuring anything in your browser, with equal Accept and Reject buttons, and an Analytics settings control stays available to change the choice later. Rejecting analytics in one tab also stops them in this site's other open tabs. The choice itself is saved in this browser's local storage for this site only; it is not a cookie and is not sent anywhere.
  • Browser events, only after you accept. If you accept, the website uses PostHog to record page views, how long a page stayed open, page-load performance, and clicks on explicitly tagged navigation, licensing, install, and evaluation actions. Each event carries the site name, a public page name (pages outside the published list are reported only as "other"), the referring site's address without its path, short campaign source, medium, and campaign codes (never free text), and the browser and operating system family. Account, sign-in, administration, and API pages are never reported. Query strings, URL fragments, page titles, page text, and form values are never sent.
  • Session-only identifier. After you accept, PostHog keeps a random identifier in this browser tab's session storage so page views in one visit can be counted together. It ends with the tab. All analytics identifiers and tab metadata are deleted when you reject analytics later. Visits are counted as sessions, not people: analytics do not create profiles, identify visitors, link visits across sites, or fingerprint the browser.
  • How events reach PostHog. Events go to this site's own server first, which forwards them to PostHog without your IP address, cookies, or referring headers, and every event asks PostHog not to look up a location. PostHog processes events under its privacy terms.
  • Capture limits. Website analytics do not record or replay sessions, capture form values or page text, collect application exceptions or network traces, or enable heatmaps, surveys, feature flags, or advertising.
  • Browser privacy signals. When the browser sends Do Not Track or Global Privacy Control, neither the page counts nor the opt-in analytics run, and no consent request is shown.
  • Request counts. Separately from browser analytics, the web server records a minimized log line for each request: the time, the site, the public page name or "other", the request method, the response status, the request and response sizes, the duration, and a coarse client class such as "browser" or the crawler the request names itself as. These lines do not include your IP address, the full user agent, query strings, cookies, or other request headers. They are used only for aggregate traffic and crawler counts, the log files are kept for at most 30 days, and the daily aggregates for at most 365 days.
  • Analytics are separate from purchases. Analytics events are not linked to your checkout, evaluation request, or package access. A click on a checkout button is counted as a click, not as a purchase.

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. If you accept analytics and your browser permits it, checkout and evaluation requests may include validated first-touch campaign codes and the external referring hostname. Only after acceptance, these values are kept in this tab's session storage for up to 30 minutes so they survive navigation to an order or evaluation form. Rejecting analytics removes them. These forms also ask how you found WolfXL. Submitted values are stored with the request. 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, deployment environment, current pain, relevant openpyxl API names when provided, developer count, purchase timeline, purchase authority, 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 60-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.

This page is operational copy for the WolfXL commercial site, not legal advice. The applicable accepted agreement, published policy, or package notice controls.