FerrLens runs entirely on one surface: the site at ferrlens.com, which serves both the marketing pages and the tools.
Anonymous tool use
Running a tool without signing in sets no cookie. Tool inputs you share are encoded in the URL fragment, never uploaded. The only client-side storage is an optional lang-pref entry in localStorage remembering your language choice.
Signed-in sessions
The shared FerrLabs identity provider sets a session cookie when you sign in:
__Secure-fl_session(orfl_sessionin development) — the session JWT, scoped to.ferrlens.com,HttpOnlyandSecure.
It is read server-side by the FerrLabs API to authenticate your tool history and API quota. See the canonical FerrLabs cookie policy for the IdP details.
French version: Cookies.