Privacy Policy
Last updated October 20, 2026
AmpClip (“we”, “us”) helps musicians plan and publish slideshows and videos for their own music. This policy explains what we collect, why, and the choices you have. It applies to ampclip.io and the AmpClip application.
What we collect
Account data. Your email address, name, and a password hash (or a Google account identifier if you sign in with Google). We use this to sign you in and to run your workspace.
Free resources. If you request a starter pack, we store your email, the resource requested, the source page, delivery status and any separate permission you give for music-promotion tips. Requesting a resource does not create a paid account or subscribe you to marketing. We use short-lived, hashed network identifiers to limit abuse.
Content you create. Artist profiles, tracks and lyrics you add, audience briefs, images you upload, and the slideshows, captions and hashtags generated in your workspace. This is your content; we store it so you can edit, render and publish it.
TikTok data, only when you connect an account. When you connect TikTok through TikTok Login Kit we receive your TikTok open id, username, display name, avatar, and OAuth access and refresh tokens for the scopes you approve. We store tokens encrypted at rest and use them only to publish the slideshows you choose to publish to your own account, and to read the performance of posts published through AmpClip. We never post without an action you took in the app or a schedule you set.
Facebook, Instagram, and YouTube data, only when you connect them. For a Facebook Page, we request permission to list Pages you manage, publish Page Reels, and read Page engagement and insights. For an Instagram professional account, we request basic account access, Reel publishing, and available media insights. For a YouTube channel, we request upload and read access so we can publish Shorts and retrieve video statistics. We store the connected account ID, name, granted scopes, encrypted access and refresh tokens where supplied, post IDs, URLs, and reported metrics. Connecting is optional; you choose the accounts assigned to each format.
Video and audio. When you upload an artist recording and confirm you have the rights to use it, we store it with the slides and render a shared MP4 for selected Reels and Shorts destinations. Each platform receives the video and its tailored caption or title when a scheduled post is published.
Research data. When you run niche research we retrieve public TikTok posts and comments through third-party data providers. We store the results in your workspace. This data is public content and is not linked to any AmpClip account other than yours.
Usage and technical data. Server logs (IP address, user agent, request paths) retained for a short period for security and debugging.
How we use it
To provide the service, to generate content you request using AI models, to publish to your selected platforms on your instruction or schedule, to show platform-reported analytics (YouTube counts are shown per video and excluded from AmpClip’s combined totals and derived metrics), to keep your account secure, and to bill you if you are on a paid plan. We do not sell personal data and we do not use your content to train models.
Third parties we share data with
Cloudflare (hosting, database, file storage, video rendering and Turnstile verification), Resend (delivery of emails you request), PostHog (usage events such as opening examples, copying scripts and requesting or accessing a pack; these events exclude email addresses and download tokens), OpenRouter and the model providers it routes to (text for slides and hooks, image description for matching; only the prompts needed to generate your content are sent), OpenAI as a direct recipient when Decisions ranking or photo verification is enabled (briefs, hook text, collection or source metadata, and inline photo thumbnails used for those checks are sent to OpenAI's Decisions API rather than through OpenRouter; those paths are off by default and only run when we enable them), Tumblr and Pinterest via Apify (public images you choose to import into collections), Monid (public Instagram posts when you link an artist handle), Apple Music and Deezer public search (verifying that songs named on slides exist), TikTok, Meta (Facebook and Instagram), and Google (YouTube) when you connect and publish, and Stripe (payments, if applicable). Each receives only what its function requires.
YouTube API Services
AmpClip uses YouTube API Services when you connect a channel. Google’s handling of information is described in the Google Privacy Policy. You can revoke AmpClip’s access through Google security settings.
Retention
Content stays in your workspace until you delete it or delete your account. Rendered slides are removed when their slideshow is deleted; imported images are removed when their collection is deleted. Connected social tokens are deleted when you disconnect the account or delete your account. Logs are kept for up to 30 days.
YouTube API metric snapshots are kept for up to 30 days. We check connected YouTube authorization daily and refresh or remove account metadata within 30 days. Video identifiers and links that cannot be reverified within 30 days are removed. Disconnecting YouTube in Accounts deletes its stored tokens, channel details, video identifiers, links, and metric snapshots immediately, holds unsent posts, and attempts to revoke the Google grant. If a periodic check detects revoked or expired authorization, the same stored YouTube data is removed. Your uploaded recording, slides, authored copy, and local publishing history remain until you delete them. Removing data from AmpClip does not remove videos from YouTube or withdraw content already sent to YouTube.
Your choices
You can withdraw permission for music-promotion tips or request deletion of your resource-request information by emailing hello@ampclip.io. Download links expire after seven days.
You can edit or delete any content in the app, disconnect social accounts from Accounts (which deletes their stored tokens), and delete your account and all workspace data from Settings or by request. See our data deletion page. You can also revoke AmpClip's access within each platform's account settings.
Security
Data is encrypted in transit. OAuth tokens are encrypted at rest with a key held only by our publishing service. Access to production systems is limited to the people who operate AmpClip.
Children
AmpClip is not directed at children under 13 and we do not knowingly collect their data.
Contact
Questions or requests: hello@ampclip.io.