LiberationSign in
Draft — pending legal review. This document is a plain-language starting point and is not legal advice.

Privacy Policy

Last updated: June 14, 2026

This policy explains what Liberation Management Platform (“Liberation”) collects, where it's stored, who else touches it, and the control you have over it. We aim to collect only what the product needs to work. We don't sell your data, and we don't run advertising or ad-tracking of any kind.

1. What we collect

Account information

When you sign in with GitHub, Google, or an email magic link, we receive your email address and basic profile details (such as name and avatar) from that provider so we can create your account.

Content you create

Projects, tasks, bugs, ideas, docs, files you upload, comments, and chat messages — the work you and your collaborators put into the app.

GitHub connection (optional)

If you connect GitHub, we request the read:user and repo scopes so the app can read your profile and link pull requests, issues, commits and CI to your tasks. Your GitHub access token is encrypted at rest and is never included in data exports or shown to other users.

Tester signups

When someone signs up through a project's public showcase, their email address is stored (in our playtest_signups records) so the project owner can send playtest keys and updates. It's used only for that purpose.

Operational data

Basic logs and, if enabled, error reports (see “Who else processes your data” below) help us keep the service running and fix bugs.

2. Where your data is stored

Your data lives in our Supabase project — a managed PostgreSQL database for records and Supabase Storage for uploaded files. Access is controlled by row-level security so people only see the projects they're part of. Authentication (your sign-in session) is also handled by Supabase.

3. Who else processes your data (subprocessors)

We rely on a small set of vendors to run Liberation. Each receives only what it needs:

  • Supabase — database, authentication, and file storage (your core data).
  • Stripe — payment processing for paid plans. If you subscribe, Stripe handles your card details; we store only a customer/subscription reference, never your full card number.
  • Resend — transactional email (invite links, playtest keys, @-mention notices, digests) and inbound email replies. Recipient addresses and message contents pass through Resend to be delivered.
  • GitHub — only if you connect it; used for the code-linking features described above.
  • Discord / Slack — only if you configure an outbound webhook. When you do, the relevant update content is sent to the channel you chose.
  • Sentry — error and performance monitoring, if enabled. May receive technical diagnostics (e.g. error messages and stack traces) to help us fix problems.

4. Cookies

Liberation uses only the cookies it needs to function — no advertising, analytics, or third-party tracking cookies:

  • Authentication — session cookies (set by Supabase Auth) that keep you signed in.
  • active_project — remembers which project you last had open so the app loads where you left off.

That's the full list. We don't embed ad networks or cross-site trackers.

5. Your rights — export and deletion

You're in control of your data:

  • Export everything — from Settings → Data, download a single JSON file with the data tied to your account. (Sensitive items like Stripe identifiers and your GitHub token are stripped from the export.)
  • Delete your account — also from Settings → Data, permanently delete your account and the data tied to it. This can't be undone, so export first if you want a copy.

If you ever can't reach these tools, email us (below) and we'll help.

6. Retention

We keep your data while your account is active. When you delete your account, the data tied to it is removed; some records may persist briefly in backups before they age out, and our vendors keep data per their own retention schedules.

7. Children

Liberation isn't directed at children under 13, and we don't knowingly collect their data.

8. Changes to this policy

If we change what we collect or who processes it, we'll update this page and revise the “last updated” date above.

9. Contact

Questions or requests about your data? Email tylerdevlearning@gmail.com or visit Support.