Cookies and Browser Storage
Necessary sign-in storage
Supabase authentication uses cookies to maintain your sign-in session and support email sign-in by code or link (including PKCE verification for links). Cookie names and expiration times depend on the authentication SDK and configuration; [VERIFY PRODUCTION COOKIE INVENTORY AND EXPIRATION TIMES]. Blocking these cookies or opening a sign-in link in a different browser profile may prevent sign-in. Signing out ends the local sign-in session; you can also clear site data in your browser.
Workspace storage
The workspace uses session storage for a tab identifier (infp-run-client) and local storage for run-ownership identifiers (infp-run-owner: followed by a run ID) to coordinate execution across tabs. These identifiers are not your task text. Session storage lasts for the tab session; local storage can persist until removed by the application or cleared in the browser. Historical UI versions may also have saved hint preferences. Clearing site data removes local preferences and identifiers; it does not delete your server account or saved ideas.
Measurement and third parties
The reviewed application code does not install advertising cookies, optional analytics SDKs or session replay. It does record authenticated product events on the server. This does not mean there are no hosting or authentication logs. Payment and subscription-management pages, if enabled, are hosted by Waffo and have their own storage practices. [VERIFY DEPLOYED NETWORK/COOKIE BEHAVIOR BEFORE FINALIZING THIS NOTICE]. Any future optional tracking requires a separate review and any applicable consent controls before activation.
Provider information
Supabase privacy · OpenRouter privacy · Vercel privacy
These links describe supplier policies, not confirmation that our account settings or service are compliant.