The public website
The Unforge website’s authored pages do not set cookies, use local storage, run analytics, or embed advertising trackers. You can read the pages and download the app without creating an account or choosing marketing preferences.
There is no optional analytics or advertising feature to consent to, so the site does not display a cookie-consent banner. A banner would be added alongside appropriate choices before introducing optional technologies that require consent.
Hosting and security cookies
Cloudflare delivers and protects the site. Depending on its active protections and the request, it may issue security cookies, such as cf_clearance after a challenge or __cf_bm for bot protection. This does not mean every visitor receives these cookies.
Cloudflare documents __cf_bm as expiring after 30 minutes of inactivity. Challenge-cookie lifetime depends on the security configuration and the expiry shown in your browser. See Cloudflare’s cookie documentation for purposes and behavior. These hosting protections are distinct from advertising or app telemetry.
Optional contribution checkout
The optional contribution link takes you to a Stripe-hosted page only when you choose it. Unforge does not embed Stripe’s payment form, scripts, or tracking pixels, so simply reading this site does not load them.
On Stripe’s checkout, Stripe may use cookies or similar technologies for payment, security, and its other services. Those technologies are governed by Stripe’s Cookie Policy and the choices available there. A Stripe account or checkout preference does not change your local Unforge app’s storage.
Storage in the local app
The downloaded app’s local interface is separate from unforge.app. It uses browser storage on its local address to keep the interface usable:
- Display preferences: local storage remembers your large-text and technical-detail settings until cleared.
- Pending operations: session storage holds operation identifiers and their request payloads, which can include text you entered, to help avoid duplicate attempts. Completed operations remove their pending entry.
- Agent jobs: session storage remembers a job identifier so the interface can reconnect to a job.
Session storage normally lasts for the browser tab’s session; browser session restoration may retain it longer. These entries stay in the local interface’s storage and are not website tracking identifiers. Separate project files and records are stored in the workspace, as described in the Privacy Policy.
Your controls
Your browser’s privacy settings let you inspect, block, or clear cookies and site data. Blocking a host security cookie may cause repeated challenges or prevent a request from completing. Clearing the local app’s storage resets interface preferences and temporary job references; it does not delete your workspace or backups.
Links to GitHub and other external websites lead to services with their own cookie rules. Nothing is embedded from those sites merely to display a link.
For questions or corrections, use the privacy contact instructions. This policy will be updated if the website or app’s storage behavior changes.