Privacy Policy
- We collect what Loudcode needs to write your posts, and nothing more. We don't sell your data or use it to train AI.
- Your data is stored in the EU (Supabase, Paris).
- Analytics cookies are only used if you say yes. You can change your mind anytime.
- Download or delete everything yourself in Account settings, anytime.
Who is responsible
The controller of your personal data under the EU General Data Protection Regulation (GDPR) is Naod Tadele, who runs Loudcode as an individual.
For anything about your data, including the requests in section 9, email hello@loudcode.dev.
What we collect and why
For each kind of data: why we use it, and the legal basis under the GDPR (Art. 6(1)).
| Data | Why | Legal basis |
|---|---|---|
| Account: name, email, profile picture, sign-in method (GitHub, Google or email) | To create and run your account | Contract (b) |
| What you write in Loudcode: product details, check-in answers, voice settings, drafts, edits, ideas, posting times | To write and manage your posts | Contract (b) |
| GitHub: repo names, commit messages, pull request titles and descriptions, releases, and a few files that describe your product (like the README) | To notice what you shipped and write about it. Only the repos you choose, read-only | Contract (b) |
| X: your handle, profile, follower count, the posts you publish through Loudcode and their public numbers (views, likes, replies), and access tokens | To post what you approve, show how posts did, and learn your writing style if you ask | Contract (b) |
| Revenue and analytics apps (Stripe, Polar, RevenueCat, PostHog): totals like MRR, subscriber count, visitors and signups, and the read-only key you give us | To spot milestones and write about them | Contract (b) |
| Screenshots of public pages of your website | To add an image to posts about something visible | Contract (b) |
| Billing: plan, subscription status, renewal date and Polar customer ID (not your card details, which only Polar sees) | To give you the plan you paid for | Contract (b); legal obligation (c) for records |
| API keys for the MCP server: name, first characters and a one-way hash (never the key itself) | To let your AI tools use Loudcode | Contract (b) |
| Support and feedback messages, with the page you sent them from | To answer you and fix problems | Contract (b); legitimate interest (f) |
| Contact form: your name, email, topic, message and a hashed IP address | To reply to you, and to limit spam | Pre-contract steps (b); legitimate interest (f) |
| Technical data: IP address, browser, device and request logs | To keep the Service secure and working, and to prevent abuse | Legitimate interest (f) |
| Usage analytics: pages viewed and features used (PostHog) | To understand what works and improve Loudcode | Consent (a), only if you accept analytics cookies |
| Page visit statistics without cookies (Vercel Web Analytics) | To count visits to our website | Legitimate interest (f) |
| Docs feedback ("Was this page helpful?"): the page, your vote, an optional note, and a hashed IP address | To improve the docs and prevent spam | Legitimate interest (f) |
| Emails we send you: a welcome email and messages about your account or billing | To run your account | Contract (b) |
You don't have to give us any of this, but without account data and at least one connected source, Loudcode can't write posts for you.
How AI is used
To write drafts, we send our AI provider (OpenAI or Anthropic) the information a draft needs: for example commit messages, your product description, your voice settings and your connected numbers. Both providers process this data on our behalf under business API terms: they don't use it to train their models, and may keep it for up to 30 days only to detect abuse.
AI only writes suggestions. It doesn't make decisions about you with legal or similarly significant effects (Art. 22 GDPR), and nothing is posted unless you post or queue it.
Who we share it with
We don't sell your data or share it for advertising. We use these service providers to run Loudcode. They process data for us under data processing agreements, and only as we instruct.
| Provider | What for | Where |
|---|---|---|
| Supabase | Database, login and file storage | EU (Paris, France) |
| Vercel | Hosting, request logs and cookieless visit statistics | USA and global edge network |
| OpenAI and Anthropic | Writing drafts and deciding on images | USA |
| PostHog | Product analytics, only with your consent | EU (Frankfurt, Germany) |
| Resend | Sending account emails | USA |
| Google (Gmail) | Delivering support messages to our inbox | USA |
| YouTube (Google) | Playing the video on our homepage, only after you press play | USA |
Other parties you choose to connect receive or provide data at your request:
- Polar sells our paid plans as merchant of record and processes payments as its own controller, under Polar's privacy policy.
- X receives the posts and images you publish through Loudcode.
- GitHub, Google, Stripe, Polar, RevenueCat and PostHog provide data to us when you sign in with them or connect them.
We may also disclose data if the law requires it, or to protect our rights or the safety of others.
Transfers outside the EU
Some providers above are based in the USA. When personal data goes there, it's protected by the EU-US Data Privacy Framework where the provider is certified, or by the European Commission's Standard Contractual Clauses. You can ask us for a copy of the safeguards at hello@loudcode.dev.
Cookies and local storage
We only use what's needed for Loudcode to work, plus analytics if you agree.
| What | Why | Needs consent? |
|---|---|---|
| Login cookies (Supabase) | Keep you signed in | No, strictly necessary |
| Your cookie choice | Remember whether you accepted analytics | No, strictly necessary |
| Preferences in local storage | Remember small choices, like a docs tab or your vote on a docs page | No, needed for features you use |
| PostHog (cookie and local storage) | Product analytics: which pages and features are used | Yes. Only set if you accept |
| YouTube (privacy-enhanced mode) | Plays the homepage video. Nothing loads from YouTube until you press play | Loads only when you choose to play it |
Vercel Web Analytics doesn't use cookies or track you across sites. You can change your analytics choice anytime: .
How long we keep it
- Your account and everything in it: until you delete your account. Deleting it removes your profile, products, drafts, check-ins, connections, keys and screenshots right away.
- Support and contact messages: until resolved, then up to 2 years in case you follow up. Messages from your account are deleted with it.
- Docs feedback: up to 12 months.
- Server logs: a short time, usually no more than 30 days.
- Analytics (PostHog): up to 12 months, then deleted or anonymized.
- Billing records: kept by Polar as long as tax law requires.
- Backups: deleted data can stay in encrypted database backups for up to 7 days before it's overwritten.
Security
Data is encrypted in transit (HTTPS) and at rest. Access tokens and keys for connected apps are kept in tables that only our server can read, never your browser. MCP API keys are stored only as a one-way hash. We ask connected apps for read-only access wherever possible.
Your rights
Under the GDPR, you have the right to:
- Access your data and get a copy of it (Art. 15).
- Correct data that's wrong (Art. 16).
- Delete your data (Art. 17).
- Restrict how we use it (Art. 18).
- Take it with you in a machine-readable format (Art. 20).
- Object to uses based on legitimate interest (Art. 21).
- Withdraw consent anytime, without affecting what happened before (Art. 7(3)).
The quickest way: in Loudcode, open Account settings, where you can edit your details, Download my data as a JSON file, and Delete account. Or email hello@loudcode.dev; we'll reply within one month.
You can also complain to a data protection authority, in particular the one where you live or work. We'd appreciate the chance to fix it first.
Children
Loudcode is for adults (18 and over). We don't knowingly collect data from children. If you think a child has signed up, email hello@loudcode.dev.
Changes to this policy
We'll update this page when our data use changes, and change the date at the top. For significant changes, we'll tell you by email or in the app before they apply.
Contact
Naod Tadele, Loudcode. Email: hello@loudcode.dev.