FerrLens-specific privacy addendum. The canonical FerrLabs privacy policy covers shared account data and infrastructure.
<h2>Anonymous tool use</h2>
<p>
You can run any FerrLens tool without an account. Anonymous use sets
<strong>no cookie</strong>. When a tool needs a server-side lookup, your input (a domain, a
URL, a header, a token to decode, etc.) is POSTed to <code>api.ferrlens.com</code>,
processed for that one request, and the result is returned to you. For anonymous users these
inputs and results are <strong>not retained</strong> after the request completes.
</p>
<p>
To keep the free tier fair, the API applies a <strong>per-IP rate limit</strong>. Your IP
address is used transiently for that counter and is not stored alongside your tool inputs.
</p>
<h2>Data stored for signed-in accounts</h2>
<ul>
<li>
<strong>Account</strong> — name, email, organization membership and roles, managed by the
shared FerrLabs identity provider.
</li>
<li>
<strong>Tool history</strong> — 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.
</li>
<li>
<strong>API tokens</strong> — tokens you create for the FerrLens API, and the request
counts used for quota and rate limiting.
</li>
</ul>
<h2>Retention</h2>
<ul>
<li>Anonymous tool inputs and results — not retained beyond the request.</li>
<li>Tool history (signed-in) — until you delete it or close your account.</li>
<li>API request counters — for the current quota period.</li>
</ul>
<h2>Subprocessors and rights</h2>
<p>
Same subprocessors as the rest of FerrLabs:
<a href="https://ferrlabs.com/subprocessors">subprocessors</a>. GDPR rights and how to
exercise them: <a href="https://ferrlabs.com/privacy">canonical privacy policy</a>.
</p>