Privacy Policy
Last updated: June 10, 2026
Who we are
LitPost ("we", "us") is a content creation assistant for solopreneurs and creators, available at https://litpost.app. This policy explains what data we collect, why we collect it, and the choices you have. For any privacy question, contact us at support@litpost.app.
Data we collect
Account data. Your email address and a hashed password, managed through our authentication provider (Supabase).
Profile data. Information you provide about your tone of voice, expertise, and content preferences, used to personalize generated drafts.
Content data. Posts, drafts, and ideas you write or generate in LitPost, and the publication history of posts you publish through connected social accounts.
Connected account data. When you connect a social account (X, LinkedIn), we store the OAuth tokens needed to publish on your behalf, plus basic profile metadata (username, avatar). Tokens are stored server-side only and are never exposed to your browser.
Context source data. If you choose to connect optional context sources, we ingest activity summaries to ground content suggestions in your real work: GitHub (commits, merged pull requests, releases), Plausible (website traffic statistics), newsletter platforms such as Beehiiv and Kit (subscriber counts and issue statistics), and Stripe (see the dedicated section below). Every context source is opt-in and can be disconnected at any time.
Stripe data
If you install the LitPost app from the Stripe App Marketplace, LitPost receives read-only access to limited billing data on your Stripe account: charges, subscriptions, customer references, and your account's business name.
We use this data for one purpose: detecting business milestones (for example, a first paying customer or monthly recurring revenue growth) so the app can suggest social media content based on your real performance. We never receive or store full card numbers, and we cannot create, modify, or refund anything on your Stripe account.
Uninstalling the LitPost app from your Stripe dashboard, or disconnecting Stripe inside LitPost, revokes our access. You can also request deletion of previously ingested Stripe-derived data by contacting support.
How we use your data
We use the data described above to:
- generate draft posts and content suggestions grounded in your real activity;
- publish and schedule posts to the social accounts you connect, on your instruction;
- operate, secure, and improve the service;
- process your subscription payments;
- respond to your support requests.
We do not sell your personal data, and we do not use it for advertising.
Service providers
We share data only with the providers required to run LitPost: Supabase (database and authentication), Vercel (hosting), Stripe (payment processing for LitPost subscriptions), and AI model providers that process your content solely to generate drafts and suggestions for you. Each provider receives only the data needed for its function.
Storage and security
Your data is stored in our Supabase database, encrypted at rest and in transit. Third-party OAuth tokens (social accounts, context sources) are handled exclusively by our backend and never sent to your browser. Access to production data is restricted to what is necessary to operate the service.
Data retention and deletion
We keep your data for as long as your account is active. When you disconnect a context source, we stop ingesting new data from it. When you delete your account, or request deletion at support@litpost.app, we delete your personal data, content, and ingested context data, except where we are legally required to retain records (for example, invoices).
Your rights
Depending on where you live (including under the GDPR), you may have the right to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise any of these rights, email support@litpost.app and we will respond within 30 days.
Cookies and local storage
LitPost uses browser local storage to keep you signed in. We do not use third-party advertising cookies or cross-site tracking.
Changes to this policy
If we make material changes to this policy, we will update the date at the top of this page and notify you by email or in the app before the changes take effect.
