FerrLens-specific privacy addendum. The canonical FerrLabs privacy policy covers shared account data and infrastructure.
Anonymous tool use
You can run any FerrLens tool without an account. Anonymous use sets no cookie. When a tool needs a server-side lookup, your input (a domain, a URL, a header, a token to decode, etc.) is POSTed to api.ferrlens.com, processed for that one request, and the result is returned to you. For anonymous users these inputs and results are not retained after the request completes.
To keep the free tier fair, the API applies a per-IP rate limit. Your IP address is used transiently for that counter and is not stored alongside your tool inputs.
Data stored for signed-in accounts
- Account — name, email, organization membership and roles, managed by the shared FerrLabs identity provider.
- Tool history — if you are signed in, the tools you run and their results may be saved to your history so you can find them again. You can delete individual entries or clear your history at any time.
- API tokens — tokens you create for the FerrLens API, and the request counts used for quota and rate limiting.
Retention
- Anonymous tool inputs and results — not retained beyond the request.
- Tool history (signed-in) — until you delete it or close your account.
- API request counters — for the current quota period.
Subprocessors and rights
Same subprocessors as the rest of FerrLabs: subprocessors. GDPR rights and how to exercise them: canonical privacy policy.
French version: Confidentialité.