Privacy Policy

Aificient Studio is made by Concord Software SL, an independent software company at Avenida Cantabria 15, 39012 Santander, Spain. For anything we do process, Concord Software SL is the data controller, and this policy explains what that involves under the EU General Data Protection Regulation (GDPR) and other applicable law.

The short version is that Aificient is built to keep the sensitive parts of your work with you. You can reach us about privacy any time at [email protected].

You can use Aificient Studio on the web, as a desktop app on Windows or macOS, or as an app on iPhone and iPad. Your projects — scripts, scenes, characters, voices, and the images and videos you generate — together with your account details are stored in your Aificient account, in our database, so your work is saved and waiting for you when you come back. That database is hosted within the European Union.

We hold this data to provide the service to you, we treat it as yours, and you can export or delete it at any time, as your rights below explain.

We store your projects to provide Aificient to you, and for nothing else. We do not use your content to train AI models, we do not sell or rent personal data to anyone, and we run no analytics or profiling. The only third-party tags we use are the Google Ads and Meta conversion measurement tags, described in section 11. We keep the personal data we hold to the minimum the service needs.

You can connect TikTok, YouTube and Instagram to publish from Aificient. Each one connects through the platform’s own official sign-in: you log in on the platform’s page, see the permissions we ask for, and approve them. We never see or store your platform password. The platform then gives us access tokens that work only within the permissions you approved.

What each connection lets us do:

• TikTok (Content Posting API, with Login Kit) — read your basic profile (nickname and avatar) and the posting options TikTok allows your account, such as privacy levels, comment, Duet and Stitch settings and maximum video length; and post your videos to your profile with the caption and settings you choose.
• YouTube (YouTube Data API) — see your channel’s ID, name and avatar, so you know which channel is connected; and upload Shorts to it with the title, description, privacy setting, publish time and thumbnail you choose.
• Instagram (Instagram API with Instagram Login, for professional Business or Creator accounts) — read your basic profile (account ID, username and profile picture) and how many posts Instagram still allows you to publish; and publish Reels to your account with the caption and cover you choose.

We use this access only to do what you ask: show which account is connected and the options the platform allows, and publish a video when you click publish or at the time you scheduled. Scheduling runs on our servers, so a scheduled post goes out even with the app closed. A video is sent to the platform only when you publish it or its scheduled time arrives.

We do not read your messages, followers, comments, analytics or any other content on these platforms. We do not sell this data, use it for advertising, or use it to train AI models.

The access and refresh tokens are stored encrypted on our servers, in our EU-hosted database, together with the connected account’s basic profile and the details of posts you schedule or publish through Aificient — caption or title, the settings you chose, the scheduled time and the result the platform returns. Tokens are kept until you disconnect the account or delete your Aificient account, as section 05 explains.

Profile details we receive from a platform are refreshed while you use the connection, and any that have not been refreshed within 30 days are deleted.

We share this data only with the platform itself — the video and post details go to the platform you publish to — and with the hosting providers that run our servers on our instructions. Each platform is a separate controller of what you publish there, under its own policy: TikTok Privacy Policy, Instagram (Meta) Privacy Policy and Google Privacy Policy.

Aificient uses YouTube API Services to upload to YouTube. By connecting a YouTube channel you agree to the YouTube Terms of Service, and Google handles your data under the Google Privacy Policy. You can revoke Aificient’s access at any time in your Google Account security settings.

Aificient’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

You can have your data deleted at any time, in any of these ways:

• Disconnect a social account in Aificient. Disconnecting TikTok, YouTube or Instagram in the app’s settings deletes that account’s access tokens from our servers immediately, so we can no longer publish to it, and posts still scheduled for it will not go out.
• Delete your Aificient account. Deleting your account from the app’s settings deletes your projects, your account details and all connected-account data, including tokens and post history. It is deleted after a 30-day grace period in which you can change your mind; to cut platform access straight away, disconnect your accounts first.
• Email us. Write to [email protected] from the address on your account and tell us what to delete — one connected account or your whole account. We delete the data of your connected TikTok, YouTube and Instagram accounts within 7 days, complete the rest of the request within 30 days, and confirm when it is done.

Deletion covers everything except the limited records the law requires us to keep, such as invoices. Videos you have already published stay on the platform until you delete them there.

You can also revoke Aificient’s access from the platform itself, which stops our tokens working at once:

• YouTube — remove Aificient in your Google Account third-party access settings;
• TikTok — in the TikTok app, open Settings and privacy, then Security, and remove Aificient from your apps and services permissions (the wording varies by app version);
• Instagram — in Instagram, open Settings, then Website permissions, and remove Aificient from Apps and websites.

After revoking access on a platform, disconnect the account in Aificient too, or tell us, and we will delete the tokens we still hold for it.

Video generation can run on your own GPU or, for heavier scenes, on a rented cloud GPU you choose to attach. That compute processes only the content you send to render, for as long as the render takes.

Because a rented GPU may be involved, we will never claim that nothing ever leaves your computer — we will only ever tell you exactly where the work runs. The provider of any GPU you attach processes that content as a service provider, under its own terms.

Aificient does not collect face data. Our apps do not use Face ID, the camera, ARKit or the TrueDepth camera, and we do not detect, measure, map or recognize faces: no face geometry, facial landmarks, face templates or any other biometric identifier is created, stored or shared, and we never try to identify who is in a picture.

You can choose to add a photo that shows a person — for example as a reference when you create a character or the creator of an ad, or as an image to animate. On iPhone and iPad you pick it with the system photo picker, so the app receives only the photos you choose. We use such a photo only to make the content you ask for: it is sent, as an ordinary image, to the AI model that draws your character or scene or generates your video, and the result is a new, AI-made image. We do not use it for anything else — not to identify anyone, not for advertising, and never to train AI models. Only add photos of yourself or of people who have agreed to it.

The photo and the pictures made from it are stored in your Aificient account, in our cloud storage on Amazon Web Services in London, United Kingdom. To generate your content they are processed by the AI model providers we use, acting as our service providers: Google (Gemini), OpenAI and Anthropic, for images and for reading the pictures you add, and BytePlus, ByteDance’s cloud service, for video. To render an ad, BytePlus keeps the AI-made portrait of a character — not your original photo — in a private library of ours, used only for our renders. Each provider processes what we send only to return the result, and may keep it for a limited time under its own terms for business API customers.

You decide how long it is kept. You can delete the photo, the character or the project at any time; deleting a character also deletes its portrait from BytePlus’s library. Deleting your account deletes all of it, as section 05 explains.

If you email us at [email protected] or use a contact form, we receive your email address and whatever you choose to write, and we use it only to answer you and keep a record of the conversation. We rely on our legitimate interest in responding to you, and we keep support correspondence only as long as we need it.

Subscriptions bought on our website or in the desktop app are paid through our payment processor, Stripe. You enter your card details with the processor, not with us; we never see or store your full card number. We receive only the limited billing information we need to provide the service and to meet our tax and accounting obligations, which we keep for as long as the law requires.

Subscriptions bought in the iPhone and iPad app are sold by Apple through your Apple Account. Apple sends us the details of each transaction — which plan, when it started and renews, and its identifiers — so we can give you the plan; we never receive your payment details.

If you ask Apple for a refund of one of those purchases, Apple may ask us about it, and we tell Apple whether the purchase was delivered, whether you could try Aificient for free before paying, and our view on the request, which reflects how much of the purchase you used. Nothing else is sent — never the content you create. We do this, as our Terms of Service set out, to help resolve your request accurately and to prevent refund abuse.

When you download the app or it checks for updates, our hosting and content-delivery providers necessarily process basic request data — such as your IP address and the file requested — to deliver the download and to keep the service secure against abuse.

If the app uses a licence or activation key, we process that key to confirm your access. We rely on legitimate interests, and where relevant on performing our agreement with you, for this.

The site you are reading runs no analytics and builds no profile of you. Our web host may keep short-lived server logs (including IP addresses) to deliver pages and protect the site, which is a standard security measure based on our legitimate interests.

We advertise on Google. To know whether those ads work, we use the Google Ads conversion tag (Google tag, gtag.js) in three places:

• this website;
• two pages of our API (api.aificient.io) that both the web app and the desktop app open in your browser: the sign-in confirmation page shown when you create an account with Google or Apple, and the checkout confirmation page shown after a payment;
• the web app, once, right after you create an account with an email code.

If you visit from the European Economic Area, the United Kingdom or Switzerland, the tag does nothing until you answer the cookie notice shown on your first visit. Elsewhere, where the law does not require asking first, it is enabled unless you opt out from the “Cookies” link in the footer. We tell the two apart from the country of your connection.

If it is enabled, it does the following, so Google can attribute those events to the ad:

• If you arrived from a Google ad, it stores the ad-click identifier in a first-party cookie on aificient.io for up to 90 days.
• When you create an account, it reports to Google that a sign-up happened, with an anonymous account reference.
• If you later start a free trial, it reports that a trial started.
• If you buy a plan, it reports that a purchase happened, the plan price, whether it is your first paid plan with us, and an anonymous transaction reference.

With those events it also sends a hashed version of your email address. The address is scrambled in your browser with SHA-256 before anything leaves the page, so Google receives a code rather than the address, and uses it only to match the sign-up or purchase to your click when the cookie alone cannot, for example on another device.

If you reject, it stores nothing, sends no email hash, and sends Google only a cookieless signal with the click identifier removed. It never sends your name, your address in the clear or what you create, and it is never used to personalise ads. Google processes this data under its own privacy policy.

We also advertise on Facebook and Instagram, and we measure those ads the same way with the Meta Pixel, on the same pages and under the same cookie notice and the same country rule. Until it is enabled it stays completely off: no cookie, no request to Meta.

If it is enabled:

• It records a visit to this site and stores a browser identifier and, if you arrived from a Meta ad, the ad-click identifier, in first-party cookies on aificient.io for up to 90 days.
• When you create an account, it reports to Meta that a sign-up happened; when you start a free trial, that a trial started; and when you buy a plan, that a purchase happened and the plan price.
• Each of those events carries an anonymous reference and a hashed version of your email address, scrambled in your browser with SHA-256 before it is sent, so Meta receives a code rather than the address.

If you reject, it sends nothing at all. It never sends your name, your address in the clear or what you create, and it is never used to personalise ads. Meta processes this data under its own privacy policy.

Your answer to the cookie notice is kept in a cookie on aificient.io for up to 400 days, and you can change it at any time from the “Cookies” link in the footer. The site and the app work the same either way.

Under the GDPR, the limited processing described above rests on one of these grounds:

• Performance of a contract — to provide the app, downloads, and any paid service you ask for, and to publish to the social accounts you connect;
• Legitimate interests — to answer your messages, deliver and secure the service, prevent abuse, and answer Apple’s questions about a refund you request for an App Store purchase, balanced against your rights;
• Consent — for the Google Ads and Meta measurement cookies and the hashed email sent with them, which you give or refuse in the cookie notice and can change at any time from the “Cookies” link in the footer;
• Legal obligation — to keep the billing and tax records we are required to keep.

We do not sell your personal data. We share the little we process only with the service providers that help us run Aificient, acting on our instructions — for example our web host and content-delivery network, our email provider, and our payment processor, Stripe. Apple receives what is described above when you buy in the iPhone and iPad app or ask it for a refund. The AI model providers named in section 07 — Google, OpenAI, Anthropic and BytePlus — process the content you ask them to generate, and ElevenLabs processes the voice recordings you choose to clone. The cloud-GPU provider you choose to attach also processes your render content as described above, and the social platforms you connect receive only what you choose to publish to them.

Aificient’s database is hosted within the European Economic Area. Some service providers may nonetheless process limited data outside it; where that happens, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses. We may also disclose data if the law genuinely requires it.

We keep your projects and account data for as long as your account is active, so your work is there when you return. You can delete individual projects or your whole account at any time, and we will delete the associated data — except for limited records, such as billing, we are required to keep for as long as the law says.

If a deleted account received the free welcome credits, we keep for up to 12 months a one-way code (a hash) of its email, sign-in, device, browser and IP address — not the data itself, and linked to nothing else — only so those credits are given once per person.

If an account without a subscription goes unused for 30 days, we may delete the media we generated in its projects — images, audio and video — to free storage. We email you first, at least 15 days before, and signing in or subscribing before then cancels it. Your scripts, projects, the files you uploaded, your characters, voices and chat history are kept, and an account that paid for a plan in the last 60 days is never affected.

The tokens for a connected social account are kept only until you disconnect it or delete your account, and platform profile details not refreshed within 30 days are deleted; section 05 explains how to delete this data.

Support emails are kept only as long as needed to help you, and security logs for a short period; when we no longer need something, we delete or anonymize it.

We use reasonable technical and organizational measures to protect the data in our care — including encryption in transit and at rest, access controls, and EU-based hosting — and we keep what we hold to a minimum. No system is ever perfectly secure, but we work to keep your projects safe and to limit who can reach them.

We never see or store your social-platform passwords: you sign in on each platform’s own page, and the access tokens it gives us are stored encrypted and used only as section 04 describes.

Wherever the law gives them to you, you have the right to access the personal data we hold about you, to have it corrected or deleted, to restrict or object to its processing, to receive it in a portable form, and to withdraw consent at any time.

To exercise any of these, write to [email protected] and we will respond within the time the law allows. You also have the right to complain to a data-protection authority — in Spain that is the Agencia Española de Protección de Datos (AEPD), or you can contact the authority in your own country.

Aificient Studio is meant for adults and is not directed to children. We do not knowingly collect personal data from anyone under 18 (or under the minimum age in your country). If you believe a child has provided us data, contact us and we will delete it.

We may update this policy as Aificient grows or the law changes. When we do, we will change the “last updated” date below, and for material changes we will try to give clearer notice in the app or by email. Continuing to use Aificient after an update means you have seen the current version.