Privacy Policy
Last updated: August 10, 2026
The short version: ForkScape is local-first by architecture, so the strongest privacy statement we can make is structural — your work never reaches us, because there is nothing of ours for it to reach.
The desktop app
Canvases, chats, files, settings, and your AI-provider API keys are stored on your machine. The app has no telemetry, no analytics, and no account system. License keys validate offline — no activation server, no phone-home. When you use an AI feature, your prompt goes directly from your machine to the provider you configured (or stays entirely local with Ollama/llama.cpp); we are not in that path and cannot see it. What each provider does with your data is governed by that provider's own privacy policy.
The browser playground
try.forkscape.com stores your canvases in your own browser's local storage. Its free model routes through our proxy, which forwards your messages to the upstream model host and keeps no message content — only daily usage counters keyed by a one-way hash of your IP address, which expire within 48 hours. Free model hosts may process forwarded text under their own terms; don't paste confidential material into a free demo.
What we do collect
Three narrow things, all standard:
· Purchases — checkout is run by Paddle (merchant of record), which
collects your email and billing details under
Paddle's privacy policy. We receive your email and
what you bought, and use it for exactly one thing: sending your license key and
the receipts/renewal notices that go with it.
· Email — if you write to support@forkscape.com we keep the thread to help you.
· Website — forkscape.com is static pages served via Cloudflare, which
provides us aggregate traffic numbers; we run no ad trackers and no fingerprinting.
Your rights
Email support@forkscape.com to access or delete what little we hold about you (your purchase email and support threads). App data is yours to delete locally — it was never ours.
Material changes will be noted here with a new date.