Cookie Policy

1. What this policy covers

This policy explains the cookies and browser storage used by Fork.me itself — the site, the dashboard, and the apps we operate. It supplements our Privacy Policy, which governs everything else we do with data.

"Cookies" are small files a site stores in your browser and sends back on every request. Browser storage (localStorage) is similar, except the data stays in your browser and is only read by the page's own code — it is never attached to network requests automatically.

2. The cookie we set

One first-party cookie, strictly necessary for the Service to function:

• fork_token — carries your signed session token so the server knows who you are when your apps load at their own {app-id}.fork.me address. Set with SameSite=Lax, scoped to Fork's own domains, and expires within 24 hours. Without it you would be signed out every time an app opens.

It is a strictly necessary cookie under the ePrivacy Directive and the UK PECR, which means it does not require consent — but you can still refuse it (see Managing cookies & storage), at the cost of not being able to stay signed in.

3. Local storage

The rest of what Fork remembers about your session is kept in localStorage in your browser. It is not transmitted to us as a cookie, and it never leaves your device except when you deliberately make a request that needs it.

• access_token, refresh_token — keep you signed in between visits. Cleared when you sign out.
• fork_consent — records that you accepted the Terms and Privacy Policy, so we stop asking.
• theme, lang — your dark/light preference and interface language.
• selectedModel — the AI model you last chose for building.
• lastTopicId, lastTopicTitle — which chat to reopen when you come back.
• chatWidth, chatCollapsed, chatCollapsedApps, sidebarCollapsed — the layout you left the interface in.

None of these are used to profile you, and none are shared with anyone.

4. What we don't use

• No third-party advertising cookies.
• No third-party analytics cookies.
• No cross-site tracking pixels, and no ad networks.
• No selling or sharing of personal data for advertising purposes.

Because we set no non-essential cookies, Fork shows you a Terms acceptance gate rather than a cookie consent banner. There is no advertising consent to collect.

5. Apps built on Fork

Apps created by users are served from their own {app-id}.fork.me addresses and may set their own storage — a game saving your high score, a tracker keeping a draft. That storage is controlled by the app's author, not by us, and this policy does not cover it. The author is responsible for disclosing what their app stores; see Apps built on Fork in the Privacy Policy.

If an app on Fork is doing something with your data that it should not, report it to abuse@co.fork.me.

6. Managing cookies & storage

Every browser lets you view, block, and delete cookies and site storage — usually under Settings → Privacy. You can block fork_token specifically, or clear all Fork storage at once by clearing site data for fork.me.

Signing out of Fork deletes the cookie and clears the tokens above from localStorage.

7. Changes to this policy

If we ever introduce a cookie that is not strictly necessary, we will update this page and ask for your consent before setting it. Material changes are announced in the product; the "Last updated" date above always reflects the current version.

8. Contact

FORK Apps, Inc.
1111b South Governors Avenue, Suite 84934
Dover, DE 19904, United States

Privacy questions: hi@fork.me