Privacy

PrivacyPolicy

What Azelify collects, why it collects it, who else touches it, and how to export or delete it.

Last updated October 20, 2026

In short

We collect the account details you give us, the projects and media you create, and the accounts you choose to connect. We never see your card number. We send your prompts and media to the AI and research services listed on the Subprocessors page. When our users research other creators, we fetch those creators' public posts and keep them for a short time. We do not sell personal data. You can export your data or delete your account from your Account page, without asking us.

1.Who operates Azelify

Azelify is an AI video editor run by one person as a sole proprietorship in Seattle, Washington, United States. No company has been formed. If one is, this policy will be updated to name it as the controller.

For everything below, "we" means the operator of Azelify and "you" means the person or company using it. Under the GDPR and UK GDPR, we are the controller for account and billing data and for the research data described in section 4, and your processor for the content you create and the accounts you connect.

Questions about this policy, or any request under it, go to [email protected].

2.What we collect

The main kinds of data we store about you:

Account details — your name, email address, profile picture, and optionally a phone number, address, and timezone, plus when you last signed in. If you use a password, we store only a scrypt hash of it, never the password. If you sign in with Google, there is no password and your email comes from Google.
Sign-in sessions — the IP address and browser user agent of each session.
Billing records — your plan, its status, trial history, and Stripe identifiers. Invoices are held by Stripe. Not your card number; see section 5.
What you create — projects, timelines, uploaded, imported, and generated media, voiceovers, scripts, captions, transcripts, brand kits, fonts, and chats with the assistants, including notes the assistants keep about your business.
Connected accounts — when you connect TikTok, Instagram, YouTube, X, or Reddit, we store the access tokens that platform issues (encrypted), the account handle, the posts we publish, and the metrics and comments we read from the account.
Research — searches, web pages, and public posts Azelify retrieves when you or its assistants research a topic, a niche, or an account, and what it learns from them.
Scheduled research — some research runs on a schedule rather than when you click: trend sweeps across niches, and regular refreshes of your connected accounts' metrics and comments and of the accounts in your profiles.
Usage and cost records — which features you ran, when, what each cost in AI spend, and errors the product hit, including crash reports with recent log lines.
Support messages — anything you send us by email or through the contact form.

3.Web media you ask us to find

When you ask an assistant to look for images or videos, we search the web for real files using Wikimedia Commons, Openverse, general web search, and Brave Search when enabled, and show you the results to review before anything is fetched. Search results can include a page title, URL, preview, dimensions, licence label when known, and information about the creator or source. When you approve one or more results, we fetch the file and store it as media in your account, along with its source page URL, file URL, provider, creator and licence label when available, the time it was imported, and a record of your approval. Unapproved search results are deleted after 24 hours.

We use that media to build your project and may send the relevant file or derived frames to the AI providers needed for your request, as described in the AI providers section below. Imported media follows the same account-content retention and deletion rules as uploaded project media below. We do not routinely review imported files for copyright before they are added; we may investigate a report and remove access under our Copyright policy.

4.People who are not Azelify users

Azelify also holds some data about people who never signed up: creators whose public posts are fetched when an Azelify user asks to research an account, a hashtag, or a niche, and people who comment on posts from accounts our users have connected, whose comments Azelify reads and sorts with AI.

Instagram posts and profiles are fetched through Meta's Instagram Graph API, YouTube posts through YouTube's API, and ads through Meta's Ad Library. We rely on legitimate interests: showing our users what works in their niche and helping them answer their audience.

You can object at any time. When you do, we delete the posts, cards, and comments we hold under your handle and stop fetching it in the future. How long we keep each kind of data otherwise:

Fetched posts and profiles — captions, handles, transcripts, and media links — are deleted 30 days after they are fetched.
A shared Discover card keeps only the post's link, its niche, tags we derived, and public counts such as views and likes. It is deleted 90 days after research last saw the post.
Comments are deleted 90 days after the last activity on them.
What Azelify learns from a post, such as that it opens with a question and cuts every two seconds, is kept with no handle, caption, or link. It has no time limit, because it no longer identifies anyone.

If you are one of these people and want us to stop, send the platform and your handle to [email protected].

5.What we do not collect

Stated explicitly, because a generic privacy policy usually implies the opposite:

Card numbers. Payments go directly to Stripe, which returns an identifier. Your full card details never reach our servers.
Advertising pixels or third-party analytics. There is no Google Analytics and no advertising pixel. One exception to know about: when you play an embedded post, the platform that hosts it (Instagram, TikTok, or YouTube) loads its own player in your browser, and that player may set its own cookies.
Nothing we could sell. We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under US state privacy laws.

6.Why we process it, and on what basis

If you are covered by the GDPR or UK GDPR, these are the legal bases we rely on:

To perform our contract with you: running the editor, editing and rendering your videos, publishing to the accounts you connected, and billing you for it.
Our legitimate interests — keeping the service secure, preventing abuse, debugging failures, metering AI spend so a runaway job cannot bill you for it, and researching public posts to show you what works in your niche, including the research that runs on a schedule.
Your consent — connecting a social account. You can withdraw it at any time by disconnecting; what was already gathered is kept for the periods in section 11.
Legal obligations — retaining tax and payment records for the period the law requires.

7.How AI providers process your content

Generating a script, a voiceover, an image, or a video means sending the relevant part of your content — your prompt, your brief, your brand kit, and where needed your media — to an AI model provider. Most text requests go to OpenRouter first, which forwards each request to the model host it selects. The Subprocessors page lists every provider and what it receives.

We do not use your content to train general-purpose models. We cannot promise the same for every provider: the model hosts OpenRouter forwards to each have their own terms, and Pollinations is a free image service we have no contract with.

Some of what Azelify learns is yours alone and some is shared. Your taste models are built from your own content and choices and are deleted with your account. Patterns learned from public posts, with no handle, caption, or link attached, are used for every account.

Model output is probabilistic. Review anything before you publish it; see the AI output section of the Terms.

See every AI provider and what it receives

9.YouTube

Azelify uses YouTube API Services. When you connect a YouTube channel, we use them to upload the videos you choose to publish, with the title, description and visibility you set, and to read the channel's details and the metrics and comments of the videos we published for you. When our users research other creators, we read public YouTube posts through the same services.

For a connected channel we store the access token YouTube issues (encrypted), the channel's name and id, the videos we uploaded, and the metrics and comments we read. We share it only with the services that run Azelify, listed on the Subprocessors page. What YouTube and Google collect themselves is governed by the Google Privacy Policy.

You can disconnect YouTube in Azelify at any time, which revokes and deletes the token. You can also revoke Azelify's access from Google's security settings page. Questions about these practices go to the contact in the first section of this policy.

10.Where your data goes

Azelify is operated from the United States, and most of the services we use process data there. Not all of them do: the model hosts OpenRouter forwards requests to can be in other countries. If you use Azelify from the EEA, the UK, or Switzerland, your data leaves your country. Where a service's data-processing terms include Standard Contractual Clauses, the transfer relies on them.

11.How long we keep it, and what deletion actually does

Deleting your account from the Account page signs you out everywhere, deletes your sign-in credentials, cancels your subscription, and clears your name, email address, phone number, and address. A cleanup job then erases your connected-account tokens, the research run for you, and the taste models built from your content.

The rest of your account data is deleted 30 days after you delete the account. Orders and invoices are kept for the period tax law requires.

Disconnecting an account erases its token straight away and asks the platform to revoke it; a record that the connection existed, with its handle, stays until you delete your account. Our own log and trace stores keep operational logs for a few days, and any backups held by our hosting provider expire on that provider's schedule.

How long each kind of data is kept:

Data	Kept for	Counted from
Posts and profiles fetched for research: captions, handles, transcripts, and media links	30 days	When it was fetched
Shared Discover cards: post link, niche, derived tags, and public counts	90 days	When research last saw the post
Creative patterns learned from posts, with no handle, caption, or link	No fixed limit	Not deleted on a schedule
Research notes about someone else's public post	90 days	When the note is archived
Research notes about your own accounts	30 days	When the note is archived
Comments other people left on your posts	90 days	The last activity on the comment
A deleted account's remaining data	30 days	When you delete your account
Background jobs	30 days	When the job finishes
Spend, usage, and learning receipts	180 days	When the record was written
Rebuildable caches, including transcripts of media you upload	90 days	When it was created
Usage counters and technical logs in our database	90 days	When it was recorded
Our operations record of what our systems did for your account: model calls, file analysis, and background work	14 days	When it was recorded
What you create: projects, media, chats, and brand kits	No fixed limit	Kept until you delete it or your account
Orders and invoices, kept for tax law	7 years	When you delete your account

12.Your rights, and how to actually use them

Export and deletion are self-serve on your Account page, so you do not have to email anyone for them:

Access — know what we hold about you. This page is the summary; the export is the specifics.
Portability — download your account data as a JSON file from your Account page. The file lists your media but does not contain the media files.
Correction — edit your name and contact details in your profile. Your email address cannot be changed there; ask us.
Erasure — delete your account from your Account page. Section 11 describes what that does.
Objection and restriction — ask us to stop or limit processing that relies on legitimate interests.
Complaint — if you are in the EEA or UK you may complain to your supervisory authority; if you are in California, Colorado, Connecticut, Virginia, or another state with a privacy statute, you have the equivalent rights there and we will not discriminate against you for using them.

Export or delete from your account

For anything you cannot do yourself, write to [email protected].

13.Security

No system is perfectly secure, and any policy that claims otherwise is telling you something false. What we do:

Traffic between your browser and Azelify, and between Azelify and its vendors, is encrypted with TLS.
Connected-account tokens are encrypted and are left out of your data export, because an export is a plaintext file and a token in one is a credential leak.
Sessions are httpOnly cookies that scripts on the page cannot read and that browsers do not send with most requests from other sites. Access to production data is limited to what running the service needs.
If a breach affects your personal data, we will notify you and the relevant regulator within the deadlines the law sets.

14.Children

Azelify is a business tool and is not directed at children. You must be at least 16 to use it, or older if your country sets a higher age for consent to data processing. We do not knowingly collect data from children; if you believe a child has created an account, tell us and we will delete it.

15.Changes to this policy

When we change this policy we update the date at the top. If a change materially affects how we use data you have already given us, we will tell you by email or in-product notice before it takes effect, not after.

Anything unclear here is our fault, not yours — ask at [email protected].