Vendors
OurSubprocessors
Every third-party service that touches Azelify customer data, what it is for, and what it actually receives.
Last updated September 12, 2026
In short
Running Azelify means sending parts of your data to other companies — to host it, to bill you, to generate your ads, and to publish them. This is the complete list. It is kept in step with the credentials the backend actually holds, so a new integration means a new row here.
1.Infrastructure and operations
The vendors that keep the service running. Every one of them processes data in the United States.
| Vendor | What it does | What it receives |
|---|---|---|
| Railway | Application hosting and the primary database | Everything stored in the product: account records, projects, timelines, billing state, and operational logs |
| Cloudflare R2 | Object storage for media and archives | Uploaded and generated video, images, audio, and archived research payloads |
| Google (Sign in with Google) | Sign-in, for accounts that use “Sign in with Google” | Your email address, name, and profile picture, and the fact that you signed in. Only if you choose Google; an email-and-password account sends Google nothing. |
| Stripe | Payments, subscriptions, and invoicing | Your email, billing address, card details entered directly on Stripe, and your subscription history |
| Amazon Web Services (SES) | Transactional email delivery | Your email address and the contents of the notifications we send you |
2.AI model providers
These receive the content needed to generate what you asked for. We contract on terms that do not permit training on our API traffic, and none of them is given your account identity beyond what a request requires.
| Vendor | What it does | What it receives |
|---|---|---|
| Anthropic | Scripts, captions, planning, and the in-product assistant | Your prompts, briefs, brand kit text, and the script or caption context for the request |
| OpenAI | Text generation, embeddings, and image generation | Your prompts, briefs, brand kit text, and the script or caption context for the request |
| OpenRouter | Routing to additional text models when a primary provider is unavailable | Your prompts, briefs, brand kit text, and the script or caption context for the request |
| ElevenLabs | Voiceover synthesis | Voiceover script text, and a voice sample where you supplied one |
| fal.ai | Image and video generation and editing | Image and video prompts, plus source frames where the request edits existing media |
| Runway | Video generation | Image and video prompts, plus source frames where the request edits existing media |
3.Research and web data
These run only when you ask Azelify to find evidence, study a topic, or learn from a public account. They receive the query, not your account content.
| Vendor | What it does | What it receives |
|---|---|---|
| Brave Search | Web search for evidence and topic research | The search query or page URL for the request |
| Exa | Web search for evidence and topic research | The search query or page URL for the request |
| Tavily | Web search for evidence and topic research | The search query or page URL for the request |
| Firecrawl | Retrieving and parsing the pages a search returned | The search query or page URL for the request |
| Parallel | Retrieving and parsing the pages a search returned | The search query or page URL for the request |
| ScrapeCreators | Retrieving public posts from a creator account you named | The public account handle you asked us to study |
4.Stock media libraries
Queried when you search for stock footage, imagery, or animation inside the editor. They see the search term and nothing else.
| Vendor | What it does | What it receives |
|---|---|---|
| Pexels | Stock imagery, video, and animation search | The search query or page URL for the request |
| Pixabay | Stock imagery, video, and animation search | The search query or page URL for the request |
| Giphy | Stock imagery, video, and animation search | The search query or page URL for the request |
5.Publishing destinations
These receive data only for accounts you have explicitly connected, and only what is needed to read or publish on your instruction. Disconnecting an account revokes and deletes the stored token.
They are not our subprocessors in the usual sense — they are your accounts, on their platforms, under their terms. They are listed because data does leave Azelify to reach them.
| Vendor | What it does | What it receives |
|---|---|---|
| TikTok | Publishing your approved posts, and reading the account's own history when you ask it to | The video, image, caption, and scheduling metadata you approved, plus the access token that platform issued you |
| Instagram (Meta) | Publishing your approved posts, and reading the account's own history when you ask it to | The video, image, caption, and scheduling metadata you approved, plus the access token that platform issued you |
| YouTube (Google) | Publishing your approved posts, and reading the account's own history when you ask it to | The video, image, caption, and scheduling metadata you approved, plus the access token that platform issued you |
| X (Twitter) | Publishing your approved posts, and reading the account's own history when you ask it to | The video, image, caption, and scheduling metadata you approved, plus the access token that platform issued you |
| Publishing your approved posts, and reading the account's own history when you ask it to | The video, image, caption, and scheduling metadata you approved, plus the access token that platform issued you |
6.Changes to this list
When we add a vendor that processes customer data, this page changes and the date at the top moves. If a change materially affects how your data is handled, we will tell you rather than leaving you to notice.
To ask about a vendor, or to object to one, write to [email protected].