Legal
Effective 2026-10-10 · Version 1.0
Acliptic ("Acliptic," "we," "us," or "our") is operated by Abdul Rehman, an individual sole proprietor based in the United Arab Emirates. Acliptic is not currently operated through a separately registered corporate entity. If that changes, this Privacy Policy will be updated to name the new operating entity and we will post a successor notice — that change will not reduce the rights described here.
This Privacy Policy applies to acliptic.pro and the Acliptic application (together, the "Service"), and to everyone who uses it, anywhere in the world. Section 15 adds a few notices specific to where you're located.
Account information. Your name and email address. If you sign up with a password instead of a third-party login, we store a securely hashed password — never your password in plain text.
Platform connection data. When you connect a platform, we receive and store an OAuth access/refresh token and basic profile information for that platform, so the Service can act on that connection on your behalf. The exact scopes we request, and no more:
youtube.upload and youtube.readonly, used to publish clips to your own channel and to confirm the upload. We store your channel name and channel ID. Signing in with Google itself (separately) only requests your basic profile and email — connecting YouTube for uploads is a distinct, later step you take from Settings. See Section 6 for the full YouTube-specific disclosure.Stream and video content. The video/audio of the livestream or file you ask us to process (obtained via each platform's own streaming/VOD interface — e.g. Twitch's M3U8 stream manifest or Kick's HLS stream), plus the clips, transcripts, captions, and AI-generated titles/descriptions our pipeline produces from it.
Billing information. If you subscribe to a paid plan, Stripe collects your payment card details directly — we never receive or store your raw card number. We store only your billing identifiers and plan/usage information (such as how much processing time you've used).
Usage data. How many streams you have active and how many seconds of video have been processed on your account, used to enforce your plan's limits.
We do not use your content or your connected-platform data to serve you advertising, and we do not sell your personal information.
Auto Upload is off by default and entirely optional. If you leave it off, your clips are generated and kept in your clip library for you to review and upload manually, platform by platform, whenever you choose. If you turn it on for a stream, each clip generated from that stream is published automatically to the platform(s) you selected, using the title, description, and caption style our AI produced — see Section 17 for what that means in practice today. You can turn Auto Upload off at any time — for a single stream before launching it, as your saved default in presets, or by disconnecting the destination platform entirely from Settings → Integrations.
Acliptic's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements, and to the Google Privacy Policy.
The YouTube channel data and upload access we receive through your Google connection are:
Acliptic does not download, cache, or store video content from YouTube. YouTube is used only as a place Acliptic can publish a clip to, at your direction — never as a source Acliptic pulls video from.
Revoking access. You can disconnect YouTube at any time from Settings → Integrations, which immediately revokes the token at Google (we call Google's own revoke endpoint) as well as deleting our stored copy of it. You can also revoke access directly, at any time, from Google's Third-party access page.
Deletion timelines. When you disconnect YouTube or ask us to delete your account, we delete the Authorized Data we received through this connection within 7 days. If you instead revoke access from Google's own settings page, we delete it within 30 days of learning about that revocation (Google requires us to periodically check). Email support@acliptic.pro to request this at any time — see Section 13.
Where you connect Instagram, we use the Instagram API with Instagram Login solely to publish clips as Reels to your own account and show you basic performance insights for content published through us. This is subject to Meta's Platform Terms and Developer Policies. We don't use your Instagram data for advertising and don't sell it.
Disconnecting Instagram from Settings removes our stored copy of your token. Acliptic does not currently have a way to revoke the token at Meta's end programmatically — to fully revoke access, follow these steps on Instagram's own account-access settings.
Where you connect Twitch or Kick, we use basic account/channel identification to monitor the channel or stream you specify, through each platform's own public streaming interfaces. Your use of Twitch and Kick through Acliptic is additionally governed by their own terms of service.
Our infrastructure is located in more than one country:
Acliptic is operated from the United Arab Emirates. By using the Service, you understand your information may be transferred to and processed in countries other than your own, which may have different data protection laws than where you live.
Intermediate pipeline files — the raw downloaded audio/video segment, and intermediate rendered versions of a clip — are deleted as soon as that clip's processing finishes. We retain the final generated clip, its transcript, and its metadata for as long as your account exists, so you can view, manage, or manually upload it later. Account information is retained until you ask us to delete it (Section 13). We retain billing records for as long as required by applicable tax and accounting law. Platform connection tokens follow the deletion timelines in Sections 6–8 above.
Data in transit to and from Acliptic is encrypted via HTTPS. Passwords are stored hashed, not in plain text. Platform access/refresh tokens are stored in our database and protected by our database provider's standard at-rest encryption; they are not separately encrypted field-by-field by Acliptic today. Access to production data is limited to what's needed to operate and support the Service. No method of storage or transmission is 100% secure, and we don't claim certifications or guarantees we don't hold.
Regardless of where you're located, we extend these same access, correction, deletion, and portability rights to everyone who uses the Service.
United Arab Emirates. We aim to handle your data consistently with the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021), to the extent it applies to this Service. We do not have, and do not claim to have, a Data Protection Officer or a registration with any data protection regulator.
European Economic Area / United Kingdom. If you're in the EEA or UK: Abdul Rehman is the party responsible for your data (contact in Section 20). Our legal bases for processing are your consent (for connecting platforms and enabling Auto Upload), performance of our contract with you (to provide the Service you've signed up for), and our legitimate interests (such as security and fraud prevention). Processing happens in the countries listed in Section 10 — we rely on each provider's own data protection safeguards rather than maintaining a separate EU/UK representative. You have the rights described in Section 13, plus the right to lodge a complaint with your local data protection supervisory authority. Clip-worthiness scoring is automated but only affects which moments we suggest as clips — it has no legal or similarly significant effect on you, and doesn't make any decision about you as a person.
United States. We do not sell or share your personal information for cross-context behavioral advertising. We don't currently have a dedicated process for state-specific privacy requests beyond the contact method in Section 20 — email us and we'll handle it manually.
The Service is intended for users 18 and older. We do not knowingly collect personal information from anyone under 18, and we don't verify age beyond asking you to confirm it when you sign up. If you believe someone under 18 has given us personal information, contact us and we'll delete it.
Acliptic's AI analyzes your stream's transcript to find clip-worthy moments, and generates a title, description, and caption style for each clip. Today, that AI-generated text is used as-is — there is not yet an in-app step where you review or edit a clip's title or description before it's used, whether you publish manually or through Auto Upload. If exact control over a video's title or description matters to you, download the clip from your library and upload it to the platform yourself outside Acliptic, where you can set it directly. We're aware this is a gap and expect to add an editing step in a future update.
We do not use your content to train AI models for any purpose beyond generating your own clips, and we do not share your content with our AI sub-processors for any other purpose.
Connecting a platform through Acliptic doesn't replace that platform's own policies, which still apply to you directly:
We may update this Privacy Policy. If we make a material change — especially one that changes how we use Google user data — we'll update the date and version at the top and, where required, ask you to re-consent before the change applies to you.
Version history: v1.0 — 2026-10-10 — initial published version.
Questions about this Privacy Policy, or requests under Section 13, can be sent to support@acliptic.pro.