Privacy policy

In effect since November 3, 2026

Dailies Studio records your video calls in Chrome and turns them into shorts. This page says what personal data the service processes, why, for how long, and who has access to it.

Who processes your data

Dailies Studio is published by Berenger.dev SRL, a private limited company under Belgian law, whose registered office is at rue Sainte Anne Termes 8, 6813 Chiny, Belgium, registered with the Crossroads Bank for Enterprises under number 0787.693.448.

For any question about your data, or to exercise your rights: [email protected].

We hold two distinct roles, and the difference matters:

• Controller for what makes the service run: your account, your subscription, billing, security and this site.
• Processor for your recordings, their transcripts and what is made from them, and for any personal data your brand’s files may hold. You are their controller: you decide what is recorded, kept and published, and we act only on your instructions, as article 28 GDPR requires.

This site

This site is a static page. As long as you open neither its support desk nor its page for booking a call, described below, it sets no cookie and writes one thing only to your device: the rank, among the people this site shows, of the one its front page just showed you, so that it shows you the next one the time after. That rank is no identifier: every visitor who was just shown the same person holds the same one. Outside that booking page, its fonts, pictures and scripts are served by our host, which keeps a technical log of requests (IP address, date, page requested) to keep the service secure.

We measure its audience with PostHog, hosted in the European Union: pages viewed, the site you came from, your clicks, and a recording of how your visit unfolds (scrolling, pointer movements) on this public page. No cookie is set and no identifier is kept on your device: each page loaded counts as a new visit, with nothing to recognise you from one page or one day to the next. These measurements pass through the address f.getswimlane.com, which PostHog runs for us. If your browser sends “Do Not Track”, nothing is counted or recorded.

The support button, at the foot of the page, loads nothing until you click it. It then opens a messaging desk provided by Heedback: from that moment, Heedback receives your IP address and the messages you write, sets a session cookie and, if you start a conversation, keeps an identifier in your browser’s storage to find it again on your next visit.

The page for booking a call lets you book a first call with our team, in a calendar provided by Calendly (Calendly, LLC). As soon as you open that page, your browser loads Calendly’s calendar from its servers: Calendly then receives your IP address, and may set cookies of its own. What you enter in the calendar (the slot you pick, your name, your email address and whatever its booking asks you for) is collected by Calendly on our behalf, and is used to set up that call and then to hold it: for nothing else. Our audience measurement notes that the page was opened, never who booked.

The price shown on the Pricing page is read from our server when the page loads: that request carries nothing but what any page load carries.

The people shown on this site do not exist: their pictures were generated by an artificial intelligence model.

The data we process

Your account

• your email address, verified by a code sent at sign-up, then by a code at each sign-in;
• your password, kept in a hashed form we cannot read back;
• your settings (caption template, webcam background, blurring of guests);
• the language the web app shows and your browser’s time zone, to write to you in your language and date our emails on your own time;
• your email choices (the one about ready shorts, the tips and offers, your planning’s reminder, the weekly summary) and the journal of the emails we sent you, reduced to their name and date, so we never write the same thing twice nor too often;
• the length and the date of each call you had processed, and the history of the credits your account received when the service was taken by the hour;
• if you subscribe: where your subscription stands (running, date of renewal or of its end) and the identifier Stripe keeps it under; your payment method stays with Stripe;
• your devices’ sign-in tokens, which expire after 30 days.

To keep you signed in, the web app keeps your session’s token and your email address in your browser’s storage, with the language you picked, and hands them to the Dailies Studio extension installed in the same browser, which records under your account. This storage is needed for the service and serves nothing else; the token is erased from it when you sign out.

How you use the service

To know what helps and what gets in the way, we note what you do with the service: an account created, a call recorded, processed or failed, a short played, planned or published, a setting changed, a subscription, files of your brand sent, an email we send you or you turn off, the screens of the web app and of the extension you open. These notes are tied to your account, by its number and by your email address, so that we know whose they are; never to your name. They hold nothing of your calls: no title, no transcript, no guest’s name, nor what you search for in your shorts; and nothing of your brand’s files, not even their names.

On the web app (dashboard.dailies-studio.com), we also record how your sessions unfold (clicks, scrolling, the layout of the screen) to see where the interface stops you. Every text, field, picture, video and sound is masked there in your browser, before anything is sent, and the page’s address is reduced to the kind of page it names: a recording shows blocks and clicks, nothing of what your calls hold. These recordings are tied to your account the same way. Nothing is written to your device for this; these measurements pass through the address f.getswimlane.com, which PostHog runs for us.

Our emails

We write to you about your account and your recordings: your codes, a welcome when your address is verified, the shorts of a call you have not opened yet, a planned short that could not be published, a call that waits for a subscription and the reminders before its deletion, the start of your subscription, in the afternoon, a reminder when nothing is planned for the next day and some shorts are waiting for a date, and, on Monday morning, a summary of your week when it counted a call or a publication: how many calls you recorded and how long they ran, your shorts, those we published, what your planning holds for the week ahead and, if you allowed us to read them, what LinkedIn and Instagram count of your publications. These emails are part of the service. You can turn off the one about ready shorts, the planning reminder and the weekly summary, with the link each carries or from the extension’s Config page.

Now and then, we also send you tips to make the most of the service and a presentation of our offer (the subscription): one a day at most, chosen from what you did with the service, a subscription never taken, a test drive never taken or shorts never planned for instance. The sign-up form says so and lets you refuse them at once; you can then stop them whenever you like, with the link each one carries or from the Config page. An account created without the form having said so gets none unless it turns them on there.

All are written in the web app’s language. None holds an invisible picture that would tell us whether you opened it: their links open the web app and name the email they come from, which is enough to know which ones help you.

Support

The web app carries no support desk: to write to us from it, use the address [email protected].

Our team may also create a WhatsApp group with you, from its own phone, if you give it your number: you ask your questions there, and we paste into it ourselves, by hand, messages Dailies Studio prepares for you: every Monday, your week’s statistics (the views of your posts, the number of shorts published, the title of the most viewed one and the network that carries you most), with slides that present them, and word of the shorts we send you to approve, then of those still waiting. We keep the group’s invite link and those messages until your account is deleted. No application reads or writes in that group on our behalf; WhatsApp (WhatsApp Ireland Limited) processes your messages and your number there under its own terms.

Your recordings

When you start a recording, the extension captures the call tab’s sound, your microphone and your webcam; it does not record the tab’s picture. It also records the video the call receives from each of the other participants: the same pictures the tab shows, read from the call page as they arrive, so that they stay usable when the call platform shrinks them beside a shared screen or moves them to another window. To do so, it runs a script in the call tab while the recording lasts, and only then; that script reads the participants’ video and nothing else of the page: none of its text, no name, nor whom it shows speaking. If you turn on automatic recording and give the extension access to the sites of your calls (Google Meet, Microsoft Teams, Zoom), that script is in their pages for as long as they are open: it looks there for someone joining you in a call, to record it without a click on Google Meet, where it then also records the sound the page plays of the participants in place of the tab’s, or to remind you to click elsewhere. It reads no text of those pages and never changes anything in them; turning the option off takes that access away. The extension keeps what it records in memory while it sends it to our servers, in segments, and writes none of it to your disk.

If you film with your phone, the web app’s camera page, open on that phone, also records its camera and its microphone during the calls the extension records and during your test drives, and sends those recordings straight to our servers, in segments, writing none of it to the phone. To help you place it, what it films shows on your computer over a direct connection between the two devices; if that connection cannot open, the phone sends our servers a small picture every two seconds, for as long as your computer shows it, and we keep only the latest, for a few seconds. The phone is paired with your account by a QR code the extension shows, valid for five minutes; it receives a token that only films: it opens neither your shorts, nor your planning, nor your account, and you remove it from the extension or from the phone; changing your password removes it too. The phone’s microphone also hears what your computer’s speakers play, so your guests’ voices: on our servers, we place the phone’s sound against the call’s and lower it while a guest alone speaks, comparing it with the call’s sound and your microphone, with no third-party service; this computation recognises nobody’s voice. For an account that disguises its guests’ voices, the shorts take the voice of your microphone, from which the browser takes the guests’ out.

During a spoken test drive, which we open account by account, Léa, Dailies Studio’s interviewer, asks you her questions aloud. Léa is an AI, OpenAI’s voice model: our servers send it your microphone’s sound as it comes and ask it to listen and answer you; its voice comes back through our servers to your browser, which plays it. So that she speaks to you of your trade, we give her your first name and, once our team has written it, the analysis of your profile drawn from your recordings (what you do, your clients, your subjects), never our team’s own notes. We keep with the test drive the text of her questions and when she asked them, so that her voice, which your microphone hears through your speakers, is never taken for yours in your shorts; her voice is not recorded and shows in no short. OpenAI does not use these exchanges to train its models and keeps a copy for 30 days at most, to detect abuse. If Léa cannot be reached, your questions are shown on screen.

From these recordings, we make for you:

• the call’s transcript, track by track;
• the call’s name and its summary, written in the app’s language and naming nobody;
• the passages proposed as shorts, with their title, keywords, captions and cover picture;
• a quality check of each short before it is offered to you: its sound is transcribed a second time and set against its text, to catch a sentence cut short, then Claude, Anthropic’s model, reads that text and tells our team whether the passage stands on its own and whether it is technically clean. We keep its opinion of each short; it decides nothing more than offering it to you at once or leaving it to our team;
• the retouch you ask for on a short: Claude reads your request beside the short’s text and, when it comes down to simple gestures (a word written otherwise in the captions, a sentence kept or cut, a title, a graphic, the music), our tool makes them as our team would, and the short comes back to you after the quality check; otherwise our team makes the retouch. What the tool changed is kept with the short, for our team;
• the video files of the shorts you have published.

The video file of a short is made on servers we rent from Google Cloud, in Paris, from the media we prepared, in two cases: shortly before the planned moment of a short you plan, where it is what gets published (“Your social networks”), and when you export it, where the export is open to your account. Once made, that file is also what a short’s page plays, for as long as the short is not changed. Until then, a short’s page composes it in your browser from those media, which your browser keeps on your device for a few hours so that it opens again without downloading them anew; they are erased from it when you sign out. For a short that is published or exported, that file is then made a second time, in the Netherlands, your webcam’s picture first redrawn by an artificial intelligence model we run ourselves on a graphics processor we rent from Google Cloud (FlashVSR+): it adds to your face the detail the webcam did not catch, eyelashes, hair, the grain of the skin, without identifying anyone; that second file takes the first one’s place. It never redraws a guest’s picture, and no picture is sent to a third-party AI service. The versions of the extension before 0.29.0 still make that file in your browser when you export it: the software that draws it, Remotion, then reports it to its publisher, Remotion AG (Zurich, Switzerland), which checks that way that its licence is complied with, and which receives your IP address, as any server your browser reaches does, and the extension’s identifier. That report holds nothing of your calls, your shorts or your account.

Your brand’s files

With the subscription, you can send us files of your brand: your logo, your colours, your fonts, your brand guidelines. They are sent straight from your browser to our storage, and stay there until you remove them.

At each sending, Claude, Anthropic’s model, reads them through Cloudflare’s gateway (the pictures, the PDFs and the texts among them, a font or a design application’s file by its name alone) and proposes our team three templates in your brand’s colours and fonts, which our team adjusts before giving you yours; we keep what it read of your brand (its colours, its fonts, its tone) and its proposals until the next reading. At each sending too, our team receives by email a link to those files, valid for 30 days: it downloads them to make your brand’s template. That email holds your name, your account number, your email address and the files’ names, not the files themselves. Your sending also shows in its internal tool until it marks your brand as integrated, which it tells you by email, with a word of its own if it writes one. We keep the date of each sending and of its integration, and who of our team did it.

Put in them only what describes your brand. If those files hold personal data, someone’s photo or name for instance, you are responsible for it as for your recordings.

Your social networks

From the web app’s Config page, you can connect your LinkedIn profile, so that we publish there the shorts you plan. LinkedIn then asks you, on its own page, to let us know your name and your profile picture, and publish on your behalf. If you agree, we keep the identifier LinkedIn gives us for your profile, your name as it appears there, a copy of your profile picture, which we show you in the preview of your posts, the permissions you granted and the token that lets us act on your behalf, encrypted in our database; LinkedIn sets its lifetime at two months. We ask for neither your LinkedIn email address nor your connections, and we do not read your posts.

When you plan a short and tick LinkedIn, we publish it for you at the planned moment: we then send LinkedIn the short’s video and the text of the post (the one we write for LinkedIn from what the short says, or the one you put in its place, which may be empty), which become a public post of your profile, subject to LinkedIn’s terms. We publish nothing you have not planned. Of each publication we keep its identifier at LinkedIn, to give you its link and never to make it twice. If you allow it on LinkedIn’s page, we also read regularly, over the six months that follow, what LinkedIn counts of those publications (impressions, people reached, reactions, comments, reshares, plays of the video), which we keep with them: numbers, never the name of who saw them. These numbers serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below). You disconnect your profile whenever you want, from the same page: we then erase that data and ask LinkedIn to invalidate the token. You can also withdraw the permission from your LinkedIn account’s settings.

You can also connect your Instagram account there, if it is a professional one (Creator or Business); no Facebook Page is needed. Instagram then asks you, on its own page, to let us know your username, publish for you and read the statistics of your posts. If you agree, we keep the two identifiers Instagram gives us for your account, your username, a copy of your profile picture, which we show you in the preview of your posts, the permissions you granted and the token that lets us act on your behalf, encrypted in our database; Instagram sets its lifetime at sixty days, and we renew it for as long as your account stays connected, so that you do not have to connect it again. We read neither your messages, nor your comments, nor your followers, nor your other posts.

When you plan a short and tick Instagram, we publish it for you at the planned moment, as a reel of your account: we then give Instagram the text of that reel (the one we write for Instagram from what the short says, or the one you put in its place, which may be empty) and a link, valid for one hour, through which it reads the short’s video from our storage; the reel becomes a public post of your account, subject to Instagram’s terms. Of each reel we keep its identifier and its address at Instagram, and the identifiers of the account it was published for, to give you its link, never to publish it twice and to find it again should you one day ask Instagram for your data to be deleted; we read regularly, over the six months that follow, what Instagram counts of it (views, accounts reached, likes, comments, shares, saves, watch time): numbers, never the name of who saw it, which serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below). You disconnect your account whenever you want, from the same page: we then erase the connection and its token. Instagram gives us no way to invalidate that token on its side: it is no longer used nor renewed, and ends by itself after its sixty days; to invalidate it at once, remove “Dailies Studio” from your Instagram account’s settings (“Apps and websites”). If you withdraw the permission there, Instagram tells us and we erase the connection; if you ask there for your data to be deleted, we also erase what Instagram had told us of your reels (their identifier, their address, their statistics and the account they were published for), whether your account is still connected or not, and the page Instagram sends you to confirms it.

You can also connect your Threads profile there. Threads then asks you, on its own page, to let us know your profile, publish for you and read the statistics of your posts. If you agree, we keep the identifier Threads gives us for your profile, your username, a copy of your profile picture, which we show you in the preview of your posts, the permissions asked for and the token that lets us act on your behalf, encrypted in our database; Threads sets its lifetime at sixty days, and we renew it for as long as your profile stays connected, so that you do not have to connect it again. We read neither your replies, nor your mentions, nor your followers, nor your other posts.

When you plan a short and tick Threads, we publish it for you at the planned moment, as a video post of your profile: we then give Threads the text of that post (the one we write for Threads from what the short says, or the one you put in its place, which may be empty) and a link, valid for one hour, through which it reads the short’s video from our storage; it becomes a public post of your profile, subject to Threads’ terms. Of each post we keep its identifier and its address at Threads, and the identifier of the profile it was published for, to give you its link, never to publish it twice and to find it again should you one day ask Threads for your data to be deleted; we read regularly, over the six months that follow, what Threads counts of it (views, likes, replies, reposts, quotes, shares): numbers, never the name of who saw it, which serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below). You disconnect your profile whenever you want, from the same page: we then erase the connection and its token. Threads gives us no way to invalidate that token on its side: it is no longer used nor renewed, and ends by itself after its sixty days; to invalidate it at once, remove “Dailies Studio” from your Threads account’s settings (“Website permissions”). If you withdraw the permission there, Threads tells us and we erase the connection; if you ask there for your data to be deleted, we also erase what Threads had told us of your posts (their identifier, their address, their statistics and the profile they were published for), whether your profile is still connected or not, and the page Threads sends you to confirms it.

You can also connect a Facebook Page you run there; Facebook lets no app publish on a personal profile. Facebook then asks you, on its own page and under your Facebook account, to let us know the Pages you run, including those you run through a business portfolio, publish on those Pages and read the statistics of their posts. If you agree, we read the list of those Pages, to let you choose the one to publish on when you run several, and we keep, for the Page you chose only: its identifier, its name, a copy of its picture, which we show you in the preview of your posts, the permissions asked for, the identifier Facebook gives us for you, without your name, and the token that lets us act as that Page, encrypted in our database, on which Facebook sets no lifetime. Your own Facebook token is not kept: it only serves to read your Pages, for a few minutes at most, the time of that choice. We read neither your profile, nor your friends, nor your messages, nor the Page’s other posts.

When you plan a short and tick Facebook, we publish it on that Page at the planned moment, as a reel: we then send Facebook the short’s video file and the text of that reel (the one we write for Facebook from what the short says, or the one you put in its place, which may be empty); it becomes a public post of the Page, subject to Facebook’s terms. Of each reel we keep its identifier and its address at Facebook, and the identifiers of the Page and of you, to give you its link, never to publish it twice and to find it again should you one day ask Facebook for your data to be deleted; we read regularly, over the six months that follow, what Facebook counts of it (plays, people reached, reactions, comments, shares, time played): numbers, never the name of who saw it, which serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below). You disconnect the Page whenever you want, from the same page: we then erase the connection and its token. We do not end that token at Facebook, which would withdraw your permission for all your Pages: to end it, remove “Dailies Studio” from the settings of your Facebook account (“Business integrations”). If you withdraw the permission there, Facebook tells us and we erase the connection; if you ask there for your data to be deleted, we also erase what Facebook had told us of your reels (their identifier, their address, their statistics, the Page and the account they were published for), whether the Page is still connected or not, and the page Facebook sends you to confirms it.

You can lastly connect your YouTube channel there. Dailies Studio uses YouTube API Services for this: by connecting your channel, you agree to the YouTube Terms of Service, and Google handles your data under its Privacy Policy. Google then asks you, on its own page and under your Google account, to let us upload videos to your channel, view your channel and view its YouTube Analytics reports; you may leave those reports out there, in which case we read fewer figures. If you accept, we read the name and the picture of the channel you picked there and we keep: its identifier, its name, a copy of its picture, which we show you in the preview of your posts, the permissions granted and the token that lets us act for that channel, encrypted in our database. Google sets no end to that token: we check with it, every fifteen days, that your permission still stands, and read the channel’s name and picture again then. We read neither the name nor the address of your Google account, nor your subscriptions, your playlists, your comments or the channel’s other videos, and we change and delete nothing on YouTube.

When you plan a short and tick YouTube, we upload it to that channel at the planned moment; YouTube shows it as a Short. We then send YouTube the short’s video file, its title (the short’s, or the one you write in its place), its description (the one we write for YouTube from what the short says, or the one you put in its place, which may be empty) and the visibility you choose: public, which is where it starts, unlisted or private. The video is declared to YouTube as not made for kids. It becomes a video of your channel, subject to YouTube’s terms. We keep each video’s identifier and address at YouTube, with the channel’s identifier, to give you its link and never publish it twice; we regularly read, over the six months that follow, what YouTube counts of it (views, likes, comments and, from the channel’s YouTube Analytics reports if you allowed us to, shares, watch time and subscribers gained): numbers, never the name of those who saw it, which serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below).

You disconnect the channel whenever you want, from the same page: we ask Google at once to withdraw our permission, and we delete the connection, its token and what YouTube had told us of your videos (their identifier, their address, their statistics). Your videos themselves stay on YouTube, where only you can delete them. You can also withdraw that permission from your Google account’s security settings: we find out at the next check, fifteen days later at most, and then delete the same data. If you delete a video on YouTube, we delete what we kept of it as soon as we find out.

You can also connect your TikTok account there. TikTok then asks you, on its own page and under your TikTok account, to let us read your name and your profile picture, post videos to your profile and read your public videos; you may leave that last permission out there, in which case we read no figures. If you agree, we keep: the identifier TikTok gives us for you, your display name, a copy of your profile picture, which we show you in the preview of your posts, the permissions granted and the token that lets us act for this account, encrypted in our database. TikTok gives that token a year; we renew it with TikTok before it ends. We read neither your followers, nor your messages, nor what you watch, nor your private videos, and we neither change nor delete anything on TikTok.

When you tick TikTok for a short you plan, we first ask TikTok, each time, what your account allows: your name and your username, who may view a video, whether comments, Duets and Stitches are open on it, and how long a video may be. We show it to you and keep none of it. You then choose, for that video, who can view it, what you allow on it and, if it promotes your own business or a third party, its disclosure as commercial content; nothing is chosen for you, and a short is never posted to TikTok without those choices. At the planned moment, we send TikTok the short’s video file, its caption (the one we write for TikTok from what the short says, or the one you put in its place, which may be empty) and those choices; it becomes a video of your profile, subject to TikTok’s terms. We keep each public video’s identifier and address at TikTok, to give you its link and never publish it twice; we regularly read, over the six months that follow, what TikTok counts of it (views, likes, comments, shares): numbers, never the name of those who saw it, which serve your account alone: to show them to you, in Dailies Studio and in the summary of your week, and what we learn from them for your shorts (below). You disconnect the account whenever you want, from the same page: we ask TikTok at once to withdraw our permission, and we delete the connection and its token. You may also withdraw it in the TikTok app, from its security settings (“Manage app permissions”): the connection then reads as expired here as soon as we find out.

What your figures teach us. Your posts’ figures also serve you alone in two ways. The posts we write for your shorts follow what worked best for you. And our team estimates each of your shorts’ viral potential (low, medium, high or excellent), which helps it prepare them, once one of your networks has five posts two days old: we compare the short’s title, the openings of its posts and its topics with the titles and openings of your most and least viewed posts, with Jev, a TypeSafe model run by Cloudflare, which keeps nothing it reads. Only your own figures and texts serve your shorts, never another account’s.

What our team knows of you. To know you better and prepare your shorts better, our team keeps a description of you written by Claude, Anthropic’s model, from the transcripts of your recordings and the titles of your shorts: your trade and your offer, the clients you address, the subjects you talk about and the way you speak, with the notes the team adds to it. It is rewritten as you record, names none of your guests, says nothing of your emotions, your health or your private life, is shown to our team alone, and goes with your account. You may ask for it, or ask us to delete it, at any time.

The notice declaration

Before each recording, you declare that you informed the participants; if you turn on automatic recording, you declare it once, for every call recorded that way. We keep that declaration, with its date, as proof of what you declared.

Your guests

Your guests appear in your recordings without being our users. You are responsible for informing them, and for obtaining their agreement before publishing anything that shows, voices or quotes them. A guest who wants to access their data, or have it corrected or erased, asks the person who recorded the call, whom we help to answer.

What we do not do

• Your recordings and your brand’s files are never used to train or improve any model, ours or a provider’s.
• We create no voiceprint and do no face recognition, and we keep no name for your guests: in a transcript, their words are only marked as a guest’s.
• We infer no emotion from a voice or a face.
• The cut-out of your webcam, which replaces or blurs your background, is computed by a model we run ourselves, on our servers or on the graphics processors we rent from Google Cloud in Belgium and the Netherlands: it separates a person from their surroundings without identifying anyone, and no picture is sent to a third-party AI service.
• The cover of a short shows the frame of your webcam where you are best photographed: facing the camera, eyes open, mouth at rest. It is chosen by models we run ourselves on our servers, which read nothing else of your face, identify no one and keep nothing of what they read. The picture behind you on that cover is generated by Cloudflare (Workers AI) from a few words describing what the short is about, never from a picture of you.
• To show a guest in a short, the same models look whether the video the call received from them shows a face, and where, to frame it: they identify no one, and we keep nothing of it but that point. No provider sees those pictures for this.
• We sell no data and use none for advertising.

Why, and on what basis

Who has access

From its internal tool, open to its members alone, our team sees the list of accounts with, for each, where its subscription stands, how many calls and shorts it has, the date of its last call and the networks it connected. It controls each short before it is offered to you: it watches it, may correct its text, captions, cut, music and posts, and sets the style of your shorts (template, background, motion design, music, thumbnails, guests, publishing rhythm). For that it reaches your calls’ transcripts and your shorts’ media, and nothing else of your calls. It approves them on your behalf only from your own account, opened as described below. To know what happened to a short, it also reads its history, which we keep for each one: every change made to it, with what it was before, who made it (you, a member of our team or our tool) and when, and what each processing cost for it. That history is read by our team alone and goes with the short.

To help you, a member of our team may also open your account and act in it on your behalf, as you would: watch your shorts, approve or plan them, change your settings or your subscription. They do so from its internal tool, after writing down why they open it and typing a code sent to their own email address, never to yours, for 30 minutes at most, after which the session closes by itself. What asks you for your password, such as deleting your account, asks them for it too, and they never choose your password. Every opening (who, when, why and for how long) and every change made during it are kept in a log that only our team reads, and a change made to a short shows in its history as made by our team on your behalf. You are not told of it by email. That log is kept after your account is deleted, without your address, as a record of what our team did.

Your data is processed by our team, as far as running the service requires, and by the following providers, bound by a contract that forbids them to reuse it for their own purposes:

Where a provider processes data outside the European Union, the transfer is covered by the European Commission’s standard contractual clauses.

Remotion AG, the publisher of the software that draws the video file of your shorts, is not one of our providers: it receives on its own account the report described above (“Your recordings”), in Switzerland, a country whose level of data protection the European Commission recognises.

LinkedIn (LinkedIn Ireland Unlimited Company) is not one of our providers either: when you connect your profile, you are the one who lets it hand us the data described above (“Your social networks”), and it handles your visit to its page under its own privacy policy. When we publish a short at your request, LinkedIn receives it as a post of your profile, which it handles on its own account.

The same goes for Instagram (Meta Platforms Ireland Limited): when you connect your account, you are the one who lets it hand us the data described above (“Your social networks”), and it handles your visit to its page under its own privacy policy. When we publish a short at your request, Instagram reads its video from our storage and receives it as a reel of your account, which it handles on its own account. Threads, which Meta Platforms Ireland Limited also runs, works the same way: you are the one who lets it hand us that data, and it reads the video of a short you publish there, which it receives as a post of your profile and handles on its own account. The same goes for Facebook, which Meta Platforms Ireland Limited also runs: you are the one who lets it hand us that data, and it receives from us the video file of a short you publish there, as a reel of your Page, which it handles on its own account.

YouTube (Google Ireland Limited) is not one of our providers either: when you connect your channel, you are the one who lets Google hand us the data described above (“Your social networks”), and it handles your visit to its page under its own privacy policy. When we publish a short at your request, YouTube receives its video file, its title and its description from us, as a video of your channel, which it handles on its own account.

TikTok (TikTok Technology Limited, in Ireland, for the European Economic Area, the United Kingdom and Switzerland) is not one of our providers either: when you connect your account, you are the one who allows it to pass us the data described above (“Your social networks”), and it handles your visit to its page under its own privacy policy. When we publish a short at your request, TikTok receives its video file, its caption and your choices for that video from us, as a video of your profile, which it handles on its own account.

How long

To have a recording or your account deleted, write to us at the address above. Deleting a recording erases its files, its transcript and its shorts from our servers; deleting the account erases all your recordings and your brand’s files.

Your rights

You can access your data, have it corrected or erased, ask for its portability, restrict its processing or object to it. Write to us at [email protected]: we answer within one month.

If our answer does not satisfy you, you can lodge a complaint with the Belgian Data Protection Authority (dataprotectionauthority.be), which we answer to, or with the authority of your country, in France the CNIL (cnil.fr).

Security

Exchanges with our servers are encrypted. A password is not enough to open your account: each sign-in also asks for a code sent to your email address. Wrong tries at a password or a code are counted so they can be limited, per account and per place they come from, as digests that hold neither your email address nor your IP address in clear, for a day at most. Recordings, like your brand’s files, are sent straight from your browser to our storage, through addresses that only work for a limited time. The text of your calls, your guests’ names and the titles of your recordings are never written to our technical logs.

Changes

We update this page when the service changes. The date at the top of the page is that of the version in effect; an important change is announced to you by email before it applies.