Privacy Policy

Account data (name, email, password), the content you upload (briefs, media, brand assets, cloned voices and likenesses you provide), the social accounts you connect, and usage data such as pages visited and features used. Payments are handled by our payment processor. We never store full card numbers. SocialFaktory isn't directed to children under 16, and we don't knowingly collect their data.

To run the service: generate your videos, publish to your connected channels, bill your subscription, prevent abuse, and improve the product. We don't sell your personal data. With your consent we also place advertising cookies from Google, Meta, TikTok, Reddit, Pinterest, LinkedIn, Microsoft and OpenAI, which measure which campaigns bring people here; they load only after you accept and never while you decline.

Your briefs and media are processed by AI infrastructure to generate video, voice, and translations. Content you upload is used to produce your output, not to train public models. Cloned voices and likenesses are processed only with your explicit consent and only to generate your content; you can delete them at any time.

You connect each social account yourself, through that platform's own authorisation screen, and we never ask for your platform password. From a connected account we receive an access token, the account's public profile (its name, handle, avatar and identifier), the destinations you can publish to such as pages, boards or channels, and the delivery status and public performance metrics of the posts we published for you. We send the platform only what you asked us to publish: your video or image, its caption, and the publishing options you chose. Platform data serves one purpose, which is to publish and schedule your content and report how it performed. We never use it to train AI models, never sell it, and never transfer it to advertisers, data brokers or any other third party beyond the providers that host and operate SocialFaktory, and an AI client you yourself connected, as section 5 describes. Authorisations are held inside our own infrastructure and are reachable only by the systems that publish for you; they are never shown to you or to anyone else. Disconnecting an account asks the platform to revoke the authorisation, where the platform offers a way to do that, and erases the stored credentials either way. We keep the account name and identifier on the posts already published so your history stays readable, and that record is removed when you close your account. You can also revoke our access from the platform itself at any time, which ends it immediately:

• Google and YouTube
• TikTok
• Pinterest
• Facebook and Instagram
• X
• LinkedIn

You can let a third-party AI client act on your account through our agent endpoint, after signing in and granting it scopes on a consent screen. Within those scopes it can read your brand content, generate video and text on your credits, and publish to the social accounts you connected. We send the client only what its calls return: brand details, channel names and handles, channel limits, quotes, your credit balance, generation status, media links, post status and post metrics. What the client sends us, such as briefs, links and files, is processed like anything you enter yourself, by the AI infrastructure described above, and is never used to train models. Revoking a connection stops its access immediately; its credentials are deleted 30 days after they expire. The client itself may keep its own copy of what it read, under its own privacy policy. You can revoke a connection at any time from Settings, API tokens, and it loses all access immediately.

SocialFaktory uses YouTube API Services. There are two separate Google authorisations and you can grant either, both, or neither. Signing in with Google is optional and only creates or identifies your SocialFaktory account: from it we receive your email address, first and last name, profile picture and Google account identifier, we store those alongside your account so you can sign in again, the sign-in token is encrypted at rest, and none of it is ever used to publish anything. Connecting a YouTube channel is the authorisation that grants publishing access, and we request exactly five permissions: your basic Google profile, your email address, read access to the channels you own, permission to upload videos to that channel on your behalf, and read access to the analytics of videos on it. We use them only to show you which channel is connected, to upload the content you asked us to publish, and to report its performance back to you. We store the authorisation and the channel identifier and title. We don't read, download or retain the videos already on your channel through YouTube API Services; if you separately paste a public video link into SocialFaktory as a creative reference, we download that specific video to work from and keep it until you delete it, which is your own action and not channel access. SocialFaktory's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is never used to train AI models, never sold, and never shared with anyone except the providers that host and operate SocialFaktory, or where you ask us to or the law requires it. You can revoke SocialFaktory's access from your Google Account at any time, which ends our access immediately. Disconnecting the channel in SocialFaktory does the same from our side: we ask Google to revoke the authorisation and we erase the stored tokens, so nothing is left that could reach your channel.

• YouTube Terms of Service
• Google Privacy Policy
• Google API Services User Data Policy
• Revoke SocialFaktory's access in your Google Account

All traffic is encrypted in transit with TLS: between your browser and SocialFaktory, between our own systems, and between SocialFaktory, the AI infrastructure and the platforms we publish to. Credentials that grant access, such as the Google sign-in token and the keys that link your brands to our publishing system, are stored encrypted at rest at the application level, so they stay unreadable even with direct access to the database. Platform authorisations are held in a separate publishing system inside our own infrastructure, reachable only through those encrypted keys; the services that publish for you use them, and they are never displayed to you or to anyone else. Every request is scoped to the authenticated account, so your data is never reachable from another account, and production access is restricted to the few people who operate SocialFaktory. Full card numbers never reach our servers. If an incident ever affects your personal data, we'll notify you and the competent authorities without undue delay, as required by applicable law.

We share data only with service providers needed to operate SocialFaktory (hosting, payment processing, AI processing, email) with the social platforms you explicitly connect when you publish, and with an AI client you yourself connect, as section 5 describes. Providers are bound by contracts limiting use to our instructions. Our infrastructure is hosted in the United States; where your data is transferred internationally, we protect it with the safeguards required by applicable law.

We keep your data while your account is active. When you delete content or close your account, we delete or anonymise associated data within a reasonable period, except where law requires retention. Disconnecting a social account revokes its authorisation and erases the stored credentials straight away; the record that ties it to your published posts is removed when you close your account.

You can access, correct, export, or delete your personal data, and object to or restrict certain processing. Email us and we'll act on the request within the timelines required by applicable law. If you're in the EEA or the UK, you can also lodge a complaint with your local supervisory authority. We don't sell or share your personal data as defined by the California Consumer Privacy Act.

You can disconnect a channel at any time from your brand's Social accounts page. We ask the platform to revoke the authorisation and erase the token, handle and avatar we hold for it; the record linking that channel to posts already published goes when you close your account. Deleting your SocialFaktory account, under Profile then Delete account, removes all your data, including everything obtained from the platforms you connected such as Facebook and Instagram, within 30 days, except records we must keep for legal or billing reasons. You can also request deletion by email at the contact address below, and we confirm within 30 days.

The SocialFaktory browser extension talks only to SocialFaktory's own servers. When you open its popup from the toolbar button, it loads your brands, their channels and, a page at a time, the actors you can pick. When you press a button in its popup, it sends what that action needs: the brand you pick, the address (URL) of the page or link you act on, a draft you paste into it, the text of a post you edit, schedule or keep as a draft with the channel and time you pick, and what you fill in for a video (the product name, the line the actor says and the actor you pick, or the length and the shape you pick), with the request to make it once you accept the price we quote. The right-click item that saves a link to your swipe file keeps that link in your browser and sends nothing. Its other right-click items send only an address, and only once you pick them: recreating an image sends that image's address (URL), and checking a video sends the address of the video's page or of the link you picked. When you ask it to recreate what is on screen, it sends a picture of the visible part of the tab, and nothing else from the page goes with it. An image we fetch from an address you picked is kept in your brand's library, like an image you upload yourself. While a post or a video is being made, the extension checks with our servers how it is going, and stops when it is ready, when it fails, when it needs something from you or when the browser shuts that check down. When you reopen the popup on a video you have not finished, it may send those details again to pick up where it stopped: to register the product, to ask for a price it does not have, or to ask again for one that has gone stale on a run whose answer was lost. A video already being made is only followed, not sent again. Every request to our API carries your sign-in (OAuth) tokens, which show that it is you, and when they have expired the extension renews them and sends the same request again. Depending on the request, it also carries technical identifiers: the kind of video asked for, the ids of what you created, and a random key that stops a retried request from running twice. Signing in, renewing and signing out use our own OAuth endpoints and carry what that exchange needs: the extension's client id, the address your browser returns to, the permissions asked for, a one-time code with its proof, a random value that ties the answer back to the request, and the token to withdraw when you sign out. We handle a page address the way we handle a link you paste into SocialFaktory yourself, and post text the way we handle a post you write there. The extension reads nothing on the pages you visit unless you ask, and runs no scripts on the sites you visit.

You sign in through our own OAuth sign-in. The extension keeps in your browser's extension storage: your sign-in tokens and a random identifier for that sign-in; the brand you last picked, which stays until you pick another; the post or video you have under way, with what you typed and picked for it and what our servers sent back, such as the options written for you, the price quoted and how far it has got, until you finish or discard it, or, for a video, until the popup next sees it finished; and your swipe file, each saved link with the time you saved it and the brand it was saved for. Nothing from your swipe file is sent to us until you act on a saved link.

The extension uses no analytics and no tracking, and we never sell data from it.

The use of information received from the extension will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

• Chrome Web Store Limited Use requirements

The data controller is SAVORA SARL, RCS Vienne 941 129 249, La Tour-du-Pin, France, which operates SocialFaktory.

Privacy questions and requests: [email protected]