Privacy Policy

This Website (Freed.wtf)

This marketing site is a simple webapp hosted on an industry-standard platform known as Vercel. Like any web host, Vercel's infrastructure logs standard HTTP request metadata (your IP address, browser user-agent, timestamp, and the URL requested) as part of their CDN operation. This data is governed by Vercel's Privacy Policy.

We do not run any analytics software, advertising pixels, tracking scripts, or session recorders on this site. There is no cookie consent banner because there are no cookies to consent to. If you subscribe to release notifications, your email address is stored via our newsletter provider solely for that purpose and nothing else.

If you accept the download clickwrap, the website stores a small local record in your browser showing which legal bundle version you accepted and when. That record stays in your browser. We do not receive it.

The Freed Application

Freed is local-first software. When you use it:

• Your feed data stays on your device.Posts captured from X, RSS, YouTube, or any other source are written to local storage: IndexedDB in the browser, the filesystem in the desktop app. None of this ever touches our infrastructure, because we have no infrastructure to touch.
• Zero telemetry.There are no analytics calls, no crash reporters phoning home, no feature flags fetched from a remote server, no usage statistics transmitted anywhere. The app runs entirely air-gapped from any backend we operate.
• No account required.Freed does not have a sign-up flow, a user database, or a concept of "your profile" on our servers. There is no profile on our servers. There are no servers.
• Your credentials never leave your device.Freed accesses social platforms through authenticated browser sessions on your device. Session data stays local to your device and is never transmitted to us.

Data Sync: Your Cloud, Your Keys

If you enable cross-device sync, your Freed data is backed up to cloud storage you already own: Google Drive, iCloud, or Dropbox. The data is encrypted with a passphrase only you know before it ever leaves your device. We cannot read it. We cannot be compelled to hand it over, because we do not have it.

The local sync relay (desktop-to-phone) operates on your local network. It does not route through any server we operate.

Legal Consent Records

Freed stores clickwrap acceptance locally on each device or browser where you accept it. The record contains a legal bundle version, a timestamp, and the consent surface that was accepted.

Desktop provider warnings for X, Facebook, Instagram, and LinkedIn are also stored locally on that device. These records are not synced through Automerge and are not transmitted to us.

Open Source Transparency

Every claim in this policy is verifiable by reading the code. Freed is MIT licensed and fully open source. There is no proprietary backend, no closed-source analytics module, no obfuscated telemetry lurking in a build artifact. If you see something in the code that contradicts this policy, open an issue. We will fix it.

Third-Party Services

Freed captures content from third-party platforms (X, YouTube, RSS feeds, etc.) on your behalf, using your own authenticated session. By doing so, you remain subject to those platforms' terms of service and privacy policies. Freed does not aggregate or transmit that content anywhere. It stays local. The act of accessing it is governed by each platform's relationship with you, not with us.

If you use a third-party AI provider, cloud storage provider, or platform login flow, their privacy policies and terms govern that interaction. Freed does not claim otherwise, and it does not act as a proxy that hides those relationships.

Children's Privacy

Freed is not directed at children under 13. We do not knowingly collect any personal information from children. Given our local-first architecture, we are not positioned to collect anyone's personal information, but we state this explicitly for compliance clarity.

Changes to This Policy

If we make a material change to this policy, we'll update the effective date at the top and post a note in the Updates section. You can also see the full change history in the public git repository.