Last updated: 5 September 2026
WolfMarket is a data service, not a consumer product. We collect the minimum needed to run accounts, bill correctly, and keep the service healthy.
| Data | Why | Retention |
|---|---|---|
| Email address, and company name if you provide one | To identify your account and contact you about the service | While your account exists |
| Password, stored only as a salted PBKDF2 hash | Authentication. We never store your password itself and cannot recover it | While your account exists |
| API keys, stored only as a SHA-256 hash plus a short non-secret prefix | To authenticate API requests and show you which key is which | Until revoked; revoked keys are retained as a record |
| Request logs: timestamp, API key id, HTTP method, path, status code, response time | Usage metering for billing, rate limiting, and diagnosing faults | 90 days, then automatically purged |
| Your tracked entities and subscriptions | To deliver the data you asked for and enforce plan limits | While your account exists |
| Email alert preferences and a record of alerts already sent | To send the alerts you opted into, and to avoid sending duplicates | While your account exists |
| Stripe customer and subscription identifiers | To match your account to your billing record | While your account exists |
Request logs record which endpoint was called, not the contents of any response.
We use a single cookie, wolfmarket_portal, which holds your signed-in session for the
customer portal. It is HttpOnly, restricted with SameSite=Strict, and expires
after 14 days of inactivity. It exists solely to keep you signed in — there are no advertising or
tracking cookies, so there is nothing to opt into.
We email you for account and billing matters. Filing alerts and the weekly digest are opt-in only and off by default; you can turn them off at any time in the portal's Account view.
We do not sell personal data. We share it only with the processors needed to run the service:
We may disclose data if required by law.
Account data and request logs are stored on infrastructure operated by Freebranch LLC in the United States.
If you are in a jurisdiction with statutory data rights (for example the UK/EU GDPR or the CCPA), those rights apply and this section is how to exercise them.
Traffic is served over HTTPS. Passwords are hashed with PBKDF2; API keys are stored only as hashes. The API operates against the database under a read-only account with write permissions explicitly denied, apart from the narrow paths needed to record your own subscriptions and usage.
We will note the date at the top of this page when it changes, and email you about material changes.
Questions or requests: [email protected]. See also our Terms of Service.