Privacy Policy & Cookies

Last updated:

1. Data Controller

OutaClip (https://outaclip.com) is operated by the following data controller, a sole proprietorship registered in France:

Benoit Sartre
Sole proprietorship (micro-entreprise)
SIRET: 91538512400010
66 Avenue des Champs-Elysees
75008 Paris
France

Contact for privacy requests: support@outaclip.com

2. Data We Collect

OutaClip collects only the data needed to provide the service:

  • Account: e-mail address, optional display name, language and e-mail notification preferences. The password is stored only as a salted scrypt hash, never in clear text.
  • Files uploaded by users: videos, images (carousel slides, logo, photos, screenshots) and documents added to a conversation with the assistant.
  • Content created with OutaClip: edited shorts, generated videos, carousels, voice-over audio, captions, scripts, plans and the messages exchanged with the assistant.
  • Payment data: payments are processed by Stripe. OutaClip never receives or stores card numbers; it keeps the Stripe customer and subscription identifiers, the plan, the credit purchases and the status of the subscription.
  • Technical logs: date and time of requests, the functions used, error reports, usage counters and the cost of AI operations per account. The IP address is used for security and rate limiting and is stored only in hashed form.
  • Cookies that are strictly necessary to the service (section 9).
  • Visitors without an account who try the editor: the files they upload, attached to a temporary session cookie.
  • Publicly available information about social media videos (title, creator, public counters), used by the discovery features.

3. YouTube data

OutaClip does not use Google Sign-In and asks for access to no Google account: not Gmail, not Google Drive, not contacts, not a YouTube account. The optional “My results” feature works without any Google authorisation: the user pastes the public link of their YouTube channel (or the link of one of its videos), and OutaClip reads, with its own YouTube API Services key, only what anyone can see on youtube.com.

  • No OAuth scope is requested; no Google token is received or stored.

What is read:

  • the channel’s identifier, name, @handle and picture;
  • the channel’s last 50 public uploads (only Shorts are kept) and, for each, its identifier, title, publication date, thumbnails, duration, player dimensions and its view, like and comment counts;
  • nothing else: private and unlisted videos are neither read nor followed.

Why: only to show the user, on their private “My results” page, how each of their public videos compares with the median of their channel 24 hours, 72 hours and 7 days after publication, to recognise which published video matches a short made with OutaClip, and to tell them which of their formats work best.

Where it is stored: in OutaClip’s database, on its server hosted by Hetzner Online GmbH in the European Union. The channel’s attachment to the account, the readings at 24 hours, 72 hours and 7 days and their links to the user’s shorts are visible only in the user’s workspace.

How long: for as long as the channel stays set in OutaClip; the list and the counters are refreshed one to several times a day during that time. When the user removes their channel (Settings, Connections, “Remove my channel and delete my data”), OutaClip deletes the channel’s attachment to their account, its readings and their links to their shorts. The same happens when the account is deleted. The public information of the videos may stay in OutaClip’s watch of public content, like that of any public video.

Reading only: OutaClip has no access to the user’s YouTube account and cannot publish, change or delete anything on it.

This data is not sold, is not used for advertising, is not passed to data brokers and is not used to develop or train generalised artificial intelligence or machine learning models. Until 10 October 2026 a channel could be connected through a read-only Google authorisation; that connection has been stopped: the access granted then is revoked at Google and the corresponding tokens are deleted.

The same read-only principle applies to a connected TikTok account: OutaClip reads the user’s own videos and their public counters, stores the access encrypted, and deletes everything on disconnection. That access can also be revoked from the TikTok settings.

4. How Data Is Used

Data is used only to provide and improve the features the user asks for:

  • create and secure the account;
  • process the files submitted and produce the content requested;
  • manage subscriptions, credits and invoices;
  • send service e-mails (address verification, password reset, “your video is ready”; this last notification can be turned off);
  • prevent abuse and fraud;
  • fix errors and keep the service reliable;
  • comply with legal obligations.

OutaClip sells no personal data, shows no advertising and builds no advertising profile. OutaClip trains no artificial intelligence model on users’ files or on the data read through YouTube API Services.

5. Who Data Is Shared With

Data is shared only with the service providers needed to run OutaClip, each for a single purpose:

  • Hetzner Online GmbH (Germany): hosting of the application and of its database.
  • Cloudflare: storage of uploaded and generated files (Cloudflare R2) and protection against bots at sign-up (Turnstile).
  • Stripe: payments, subscriptions and invoices.
  • Resend: delivery of service e-mails.
  • Google (Gemini API): analysis of the files and text a user submits, and generation of scripts, plans and images. A file sent for analysis is deleted from Google’s file service once it has been read.
  • ElevenLabs: generation of the voice-over audio from the text of the script.
  • An AI video generation provider: generation of video clips from the images and instructions the user provides.
  • Google (YouTube API Services): reading the public information of the channel set by the user, as described in section 3.

These providers process data only as needed to provide their service to OutaClip. Captions are transcribed on OutaClip’s own server, without any third party. Some providers may process data outside the European Union; where required, appropriate legal safeguards are used for these transfers.

6. How Long Data Is Kept

  • Uploaded files and the videos or carousels made from them: 24 hours for visitors without an account (removed by a daily clean-up), 7 days on the Free plan, 30 days on the Creator plan; they are then deleted from storage.
  • Brand kit (logo, photos, colours, signature): until the user removes them or the account is deleted.
  • Account data and the content of conversations: until the account is deleted.
  • YouTube data of “My results” (the channel set, readings, links): until the channel is removed or the account is deleted (section 3).
  • Invoices and payment records: for the period required by tax and accounting law (ten years in France).
  • Technical logs: for a limited period, for security and troubleshooting.

7. Deleting Data and Revoking Access

To have an account and all the data attached to it deleted, the user writes to the contact address in section 1 from the e-mail address of the account. The request is carried out within 30 days at most: the files are removed from storage and the account, its content and its connected accounts are erased. Only the invoices that the law requires to be kept remain.

The YouTube channel set can be removed at any time in Settings, Connections: its readings and their links to the shorts are deleted.

OutaClip holds no access to a Google account: there is nothing to revoke at Google. An access granted before 10 October 2026 can be checked here: Google Account, third-party access (https://myaccount.google.com/permissions)

8. Security

All exchanges with OutaClip are encrypted in transit (HTTPS/TLS). Passwords are kept only as salted hashes, session tokens in hashed form, and the access tokens of a connected account (TikTok) are encrypted at rest.

Files are kept in a private storage space and are served only through short-lived signed links. Access to the production systems is restricted to the operator.

No internet service can guarantee absolute security.

9. Cookies

OutaClip uses only cookies that are strictly necessary to the service. It uses no advertising cookie and no audience-measurement cookie.

  • outaclip_session: keeps the user signed in (30 days at most).
  • outaclip_guest_edit: the temporary session of a visitor who tries the editor without an account.
  • outaclip_anon_id: an anonymous counter for the free search allowance, linked to no identity.
  • outaclip_locale: the language chosen.

On the sign-up page, Cloudflare Turnstile may store what it needs to tell people from bots; on the payment page, Stripe uses its own cookies.

The browser’s local storage keeps unsent drafts and files being added, on the user’s own device.

Strictly necessary cookies do not require consent. If non-essential cookies were introduced later, consent would be requested first.

10. Users’ Rights (GDPR)

Under the GDPR, users have the right to:

  • access their personal data;
  • have inaccurate data rectified;
  • have their data erased;
  • have its processing restricted;
  • receive their data in a portable format;
  • to object to certain processing and to withdraw consent at any time (for example by removing their channel).

Legal bases: performance of the contract (providing the service), consent (adding their YouTube channel, connecting a TikTok account), legitimate interest (security and abuse prevention) and legal obligation (invoices).

Requests are sent to the address below and answered within one month: support@outaclip.com

Users may also lodge a complaint with the French data protection authority, the CNIL (www.cnil.fr).

11. YouTube API Services

OutaClip receives no Google user data through an OAuth authorisation. Should such an authorisation be offered again, OutaClip’s use of information received from Google APIs, and its transfer to any other app, would adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google API Services User Data Policy

The “My results” feature uses YouTube API Services. By setting their channel, the user also agrees to the YouTube Terms of Service; the Google Privacy Policy applies to the data held by Google. YouTube Terms of Service · Google Privacy Policy

12. Changes

This policy is updated when the service, its providers or the law change.

The current version remains available on this page, with its date.

13. Contact

For any question or request about privacy: support@outaclip.com