Privacy Policy
Effective May 2026 · [email protected]
Azelia ("we", "our") publishes Azelia Clips, a self-hosted, local-first AI toolkit for podcast creators. This policy describes what data the software accesses on your behalf, where that data lives, and your rights. Azelia does not run a backend that collects or stores your personal data.
Local-first by design. The Azelia software runs entirely on your machine. Your episodes, transcripts, clips, settings, API keys, and any YouTube data you authorize stay on your computer in ~/.azelia/data/. Azelia has no central database, no telemetry, and no account system.
1. Data the software accesses on your machine
1.1 Local content
Azelia reads the podcast media files, transcripts, and configuration you point it at. All of this data lives in directories you choose (PODCAST_DIR) and the data directory (~/.azelia/data/). It is never transmitted to Azelia.
1.2 YouTube channel (optional)
If you connect your YouTube channel via OAuth, Azelia accesses the following data through the Google / YouTube API directly from your machine:
- Channel name, channel ID, and subscriber count
- Video list: title, video ID, publish date, duration, thumbnail
- Basic metrics: views, likes, and comments per video
This data is stored in your local SQLite database (~/.azelia/data/youtube_shorts.db) and used only to bias the curation pipeline toward what already works on your channel.
1.3 YouTube Analytics (optional)
With your explicit authorization Azelia additionally reads YouTube Analytics data, locally:
- Audience retention curves per video
- Click-through rate (CTR) and impressions
- Average view duration and retention percentage
- Subscribers gained and lost per video
What Azelia NEVER receives: we do not run servers that collect your audio, video, transcripts, clips, OAuth tokens, channel metrics, API keys, or any other data. There is no signup, no email collection, and no telemetry.
2. How the software uses your data
| Purpose | Data used | Where it runs |
|---|---|---|
| Clip generation pipeline | Local transcripts, media | Your machine |
| AI inference (curation agents) | Transcript snippets | Anthropic API or Claude Code |
| Channel-aware curation | YouTube metrics, analytics | Your machine |
3. Where your data lives
Everything Azelia generates or caches lives under ~/.azelia/data/ on your machine:
- SQLite databases (jobs, YouTube channel cache, Critic feedback)
secrets.env— your Anthropic key and optional Supabase credentials, stored locally- OAuth tokens for YouTube, stored encrypted at rest with a key generated on first run
Generated clips and curation files live next to your source media under PODCAST_DIR, where you can move, copy, or delete them like any other file.
4. Data sharing
Azelia does not sell or share your personal data because Azelia does not receive it in the first place.
When you use the software, your machine connects directly to the third-party providers you configure:
- Anthropic — receives transcript snippets you send for AI inference, governed by Anthropic's privacy policy.
- Google / YouTube — if you connect your channel, your machine queries Google's APIs directly under the OAuth scopes you approve.
- Your own Supabase (optional) — if you choose to host transcripts in a Supabase instance you own, your machine reads from it directly. Azelia has no access to your Supabase.
5. Data retention and disconnection
You can disconnect your YouTube channel at any time from Settings. Disconnecting revokes the OAuth token with Google and deletes the local YouTube data from your machine.
- Local data: under your control — delete
~/.azelia/data/to wipe everything Azelia stores. - YouTube data: deleted from your machine immediately when you disconnect the channel.
- OAuth tokens: revoked at Google and deleted locally on disconnection.
6. Your rights
Because the data stays on your machine, the classic rights below are exercised locally — by accessing, editing, or deleting files. For data held by integrations (Anthropic, Google), exercise your rights with those providers directly. If you contact us under Colombia Law 1581 of 2012, GDPR (EU), or CCPA (California), we can confirm in writing that we do not store the data in question.
| Access | Read everything under ~/.azelia/data/ |
| Rectification | Edit local files or re-import the source |
| Erasure | Delete ~/.azelia/data/ and revoke any OAuth tokens |
| Portability | All data is already in open formats (SQLite, JSON, mp4) on your disk |
| Withdrawal | Revoke YouTube OAuth in Settings or at Google account permissions |
For any questions about your rights email us at [email protected].
7. Google API use
Azelia uses the YouTube Data API and the YouTube Analytics API exclusively to read data from your own channel with your explicit authorization. We do not write, modify, or delete any content on your channel. Azelia's use complies with the Google API Services User Data Policy, including the Limited Use requirements. All YouTube data is processed locally on your machine and is never sent to Azelia or any third party.
8. Minors
Azelia is not intended for users under 16. We do not knowingly enable data collection from minors.
9. Changes to this policy
We will notify material changes via the dashboard banner and at azelia.ai/privacy. Continued use of Azelia after the notification constitutes acceptance.