Privacy policy

Last updated:

This page explains which personal data we process when you visit showbits.de and showbits.ai and when you use the ShowBits app (app.showbits.ai), for what purpose and on which legal basis. How the app handles data from Google accounts is described in the section “Google user data”. Content that your company processes in the app is also covered by the data processing agreement. Anyone who books the Hobby plan as a consumer concludes no such agreement; we are then also the controller for this content within the meaning of the GDPR (see “The ShowBits app”).

1. Controller

The controller responsible for data processing on this website is HBC Hohn Business Consulting UG (haftungsbeschränkt), Lerchenstraße 7, 14089 Berlin, Germany.

Email: hello@showbits.ai · Phone: +49 15678 412954

ShowBits is a product of HBC Hohn Business Consulting UG (haftungsbeschränkt). For privacy questions, contact us at the email address above.

2. Hosting and server log files

This website is hosted by Vercel Inc. (USA, delivered via a global server network), with whom we have concluded a data processing agreement under Art. 28 GDPR.

Where personal data is transferred to the USA in this context, this takes place on the basis of the provider’s certification under the EU-US Data Privacy Framework (Art. 45 GDPR) or the European Commission’s standard contractual clauses (Art. 46 GDPR).

Each visit involves technically necessary data: IP address, date and time, page requested, referrer URL, browser and operating system. We process this data to deliver the website, keep it stable and secure, and defend against attacks.

The legal basis is our legitimate interest in secure and reliable operation (Art. 6(1)(f) GDPR). Log data is deleted once it is no longer needed for these purposes, unless a security incident requires longer retention for investigation.

On the pricing page of showbits.ai, we preselect the currency (EUR in Europe, USD elsewhere). For this, our server reads the country that Vercel derives from your IP address and sends only the currency back to your browser. The country is not stored and no cookie is set. The legal basis is our legitimate interest in showing prices in a suitable currency (Art. 6(1)(f) GDPR).

In addition, we use Vercel Speed Insights to measure how fast the website loads for visitors. This processes technical measurements such as loading times, the page visited, device type and browser. No cookies are set and visitors are not recognised. The legal basis is our legitimate interest in a fast and functional website (Art. 6(1)(f) GDPR).

We also use Vercel Web Analytics to understand which pages are visited and where visitors come from. It records the page visited, referrer, country, device type, operating system and browser. Vercel sets no cookies for this; visitors are only distinguished by a daily changing, non-reversible hash and are not recognised across days or websites. We remove URL parameters before sending, except campaign parameters (utm). The legal basis is our legitimate interest in improving our offering (Art. 6(1)(f) GDPR).

3. Encryption

For security reasons, this website uses TLS encryption. You can recognise an encrypted connection by “https://” in your browser’s address bar.

4. Fonts

The fonts used on this website are loaded from our own server. No connection is made to Google or any other font provider when you visit the site.

5. Cookies and consent

We use technically necessary cookies to store your language and your cookie settings. The legal basis is § 25(2) no. 2 TDDDG (German Telecommunications Digital Services Data Protection Act) in conjunction with Art. 6(1)(f) GDPR.

We only set statistics cookies if you have consented via our cookie banner (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). You can withdraw your consent at any time with effect for the future, via the cookie settings in the footer or directly here.

NamePurposeDuration
NEXT_LOCALENecessaryRemembers your languageUntil the browser is closed
showbits_consentNecessaryStores your cookie choice12 months
_gaStatisticsDistinguishes visitors (Google Analytics)24 months
_ga_<ID>StatisticsKeeps the session state (Google Analytics)24 months
_clckStatisticsDistinguishes visitors (Microsoft Clarity)12 months
_clskStatisticsGroups page views into one session (Microsoft Clarity)1 day

6. Google Analytics and Microsoft Clarity

With your consent, we use Google Analytics 4, a web analytics service provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland (“Google”). Google Analytics helps us understand which content is read and how visitors use the website, so we can improve it.

We process usage data (pages visited, time on page, clicks), device and browser information, a pseudonymous identifier and an approximate location derived from your IP address. According to Google, Google Analytics 4 does not store IP addresses. We have disabled Google Signals and use for personalised advertising.

We have concluded a data processing agreement with Google. Data may be transferred to Google LLC in the USA. Google LLC is certified under the EU-US Data Privacy Framework, which is covered by an adequacy decision of the European Commission (Art. 45 GDPR).

The legal basis is your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). Analytics data is deleted automatically after 14 months. Without your consent, Google Analytics is not loaded.

With your consent, we also use Microsoft Clarity, an analytics service provided by Microsoft Ireland Operations Limited, One Microsoft Place, South County Business Park, Leopardstown, Dublin 18, Ireland (“Microsoft”). Clarity shows us in heatmaps and session recordings how visitors use the website, for example where they click, how far they scroll and where they get stuck.

We process mouse movements, clicks, scrolling, the pages visited, device and browser information, a pseudonymous identifier and an approximate location that Microsoft derives from your IP address. Form field input is not recorded. Clarity sets the cookies _clck and _clsk on our domain; Microsoft may additionally set cookies on its own domains (such as MUID and CLID).

The data is stored in the Microsoft Azure cloud. Data may be transferred to Microsoft Corporation in the USA. Microsoft Corporation is certified under the EU-US Data Privacy Framework, which is covered by an adequacy decision of the European Commission (Art. 45 GDPR).

The legal basis is your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). Clarity deletes session recordings after 30 days; recordings marked as favourites and a random sample are kept for up to nine months. Without your consent, Clarity is not loaded.

7. Demo requests, document requests and contact

If you request a demo or security documents or email us, we process the information you provide, such as your name, work email, company, team size, interest and message.

We use this data only to handle your request and contact you. The legal basis is taking steps prior to entering into a contract (Art. 6(1)(b) GDPR) and our legitimate interest in answering enquiries (Art. 6(1)(f) GDPR).

We forward your request as an email to our mailbox. For sending we use Resend, Inc. (USA, sending via the EU region), with whom we have concluded a data processing agreement.

Where personal data is transferred to the USA in this context, this takes place on the basis of the provider’s certification under the EU-US Data Privacy Framework (Art. 45 GDPR) or the European Commission’s standard contractual clauses (Art. 46 GDPR).

We delete the data once your request has been fully handled, unless statutory retention obligations, for example under commercial and tax law, apply.

8. Applications

If you apply to us, we process your application documents and the information in your email to decide on your application. The legal basis is the initiation of an employment relationship (Art. 6(1)(b) GDPR in conjunction with § 26 BDSG).

If you are not hired, we delete your documents six months after the end of the process. If you would like to be considered for future positions for longer, we ask for your consent beforehand.

9. The ShowBits app

This section describes the processing in the ShowBits app (app.showbits.ai) that applies to every user. The following sections describe the services that can be connected to the app. For content that your company processes in ShowBits, such as episodes, transcripts, clips and quote cards, the data processing agreement (DPA) with your company also applies. If you book the Hobby plan as a consumer, there is no DPA: we then also process your content as the controller, to perform the contract with you (Art. 6(1)(b) GDPR), and information about other people in your episodes, such as guests, on the basis of our legitimate interest in providing the service you booked (Art. 6(1)(f) GDPR). Where this policy refers to your company, it then means you.

The app only sets technically necessary cookies: the session cookies for sign-in, short-lived encrypted cookies while you sign in with Google or connect a service, and, after you delete your account, a cookie with which only that browser can fetch your confirmation of erasure for 30 minutes. It uses no analytics or advertising cookies.

Account and sign-in

What data
Your name, your email address and your language. If you sign in with a code by email: the code. At sign-up: the company name, the name of the first workspace, the chosen plan, your confirmation that you are acting as a business, and the versions of the terms and DPA you accepted, with the time. Your memberships in organisations and workspaces with your role; if an admin invites you, they enter your email address and role (ShowBits does not send an invitation email). Billing details that owners and organisation admins enter (company, address, email address for invoices, VAT ID). If you sign in with Google, see “Google user data”. On Hobby you name your podcast instead of a company; whether you act as a business is up to you to state, and without this statement you book as a consumer and accept only the terms. The record then names the plan and that you booked as a consumer. If you later declare that you book as a business, for example to switch from Hobby to Creator or Business, we store this declaration with the accepted versions in the same way.
Purpose
Signing you in, providing your account, assigning you to organisations and workspaces with the rights of your role, the trial period, invoicing and proof that the contract was concluded.
How it is stored
In the database at Supabase (Ireland region, EU). The sign-in code has six digits, is valid for 10 minutes and is sent by Resend (EU) from login@showbits.ai. Your session is kept in cookies that scripts in the browser cannot read. We count attempts to sign in or request a code for ten minutes per email address and per IP address, to slow down guessing codes and passwords; for this we store only hashes (SHA-256) of the email address and the IP address, not the addresses themselves.
Who it is shared with
With our subprocessors, to the extent necessary for the service (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe). When you request a sign-in code or sign in with a password, your browser first loads the Turnstile check by Cloudflare, Inc. (USA): it establishes that a person is signing in, usually without you having to do anything, and receives what your browser sends for this, including your IP address. Supabase Auth checks the result before a code is sent or a password is checked. The legal basis is our legitimate interest in protecting accounts and our email sending from abuse (Art. 6(1)(f) GDPR). Where data reaches the USA in the process, this is based on Cloudflare's certification under the EU-U.S. Data Privacy Framework (Art. 45 GDPR) or on the European Commission's standard contractual clauses (Art. 46 GDPR).
How long it is kept
Profile and sign-in until your account is deleted. Memberships until your account, the workspace or the organisation is deleted. Billing details until the organisation is deleted. The record of the accepted terms and DPA is kept as proof of the contract until 3 years after the organisation ends, also after your account is deleted (see “Deleting your account”). After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest). For consumers, the record covers only the terms, without a DPA.
How it is deleted
You can delete your account yourself in the app under “Your account” → “Delete account” (see “Deleting your account”), or write to us at hello@showbits.ai and we will delete it. Signing out ends the session on this device.

Billing and payment

What data
For every organisation that books a plan or a credit pack: a customer account with our payment provider Stripe with the company name from the billing details (otherwise the organisation's), the email address for invoices (otherwise yours), the address and, where applicable, the VAT ID. When booking in Stripe Checkout, you enter your billing address and payment method at Stripe; we do not receive card details or other payment details. From Stripe we take the IDs of the customer account and the subscription, the plan, billing interval, currency and status of the subscription, the end of the trial and of the current period, a cancellation date, whether a payment method is on file, the country for VAT and the VAT ID with the result of its check. If you book Hobby as a consumer, the customer account at Stripe bears your name, Checkout asks for no VAT ID, and Stripe stores with the booking your express request that we start before the withdrawal period ends. If you withdraw, or an annually billed Hobby ends early, we refund through Stripe with a credit note.
Purpose
To bill plans and credit packs, to calculate VAT correctly (for businesses in the EU outside Germany with the reverse charge) and to show in ShowBits what is booked. The legal bases are the contract (Art. 6(1)(b) GDPR) and our obligations under tax and commercial law (Art. 6(1)(c) GDPR).
How it is stored
At Stripe (EU) and mirrored in our database at Supabase (Ireland region, EU). Stripe sends invoices and receipts by email and keeps them in the customer portal, which owners and organisation admins can open from ShowBits.
Who it is shared with
With Stripe as our payment provider; Stripe calculates VAT and checks VAT IDs with the competent authority, in the EU through the VAT Information Exchange System (VIES). Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
The data in ShowBits until the organisation is deleted. Invoices and receipts remain at Stripe for the statutory retention period.
How it is deleted
With the organisation (see “Deleting your account”) or after the contract ends in accordance with our terms; invoices and receipts only once the statutory retention period has passed.

Cancelling and withdrawing without signing in

What data
What you enter on the pages “Cancel contracts here” and “Withdraw from a contract”: your name, the email address of your ShowBits account, optionally the contract or workspace and, for a cancellation, its kind (ordinary or for good cause), the reason and a desired end date. In addition, when your notice came in, and the outcome: the organisation concerned, when the contract ends and any refund. For a withdrawal, also a six-digit code that we send you, and when you confirmed it.
Purpose
To receive and carry out your cancellation or withdrawal and to confirm its receipt to you, which we are required to do by law (§ 312k and § 356a BGB; Art. 6(1)(b) and (c) GDPR). The code ensures that only you can withdraw from your contract. We keep the record to be able to defend legal claims (Art. 6(1)(f) GDPR).
How it is stored
In the database at Supabase (Ireland region, EU). We send the confirmation and the code by email through Resend (EU) to the address given. As with signing in, we count attempts for ten minutes per email address and per IP address, using hashes instead of the addresses.
Who it is shared with
With Stripe, to end the subscription and refund where applicable (see “Billing and payment”). Where a person has to decide, for example on a cancellation for good cause, our support receives a copy of the confirmation. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
The notice with its outcome for 3 years from its receipt, even if your account or the organisation is deleted earlier (Art. 17(3)(e) GDPR). The code is valid for one hour; the count of attempts lapses after ten minutes.
How it is deleted
Automatically after the 3 years.

Episodes, clips and quote cards

What data
Episodes that you upload or import (video and audio); their transcript with speakers and word timings; the highlights and quotes that ShowBits finds; clips with subtitles, thumbnails and covers; quote cards, which can show the name of the person quoted if it is said in the episode; copy and hashtags per channel; approvals with comments, schedules and posts; brand kits with logos, fonts and images; and usage per workspace (minutes processed, AI usage). Animated quote cards: a video of up to 60 seconds in which the words appear as they are spoken, with the episode's sound at that point.
Purpose
Providing the service: transcribing episodes, finding highlights and quotes, producing clips and quote cards, approval, scheduling and publishing.
How it is stored
Uploaded episodes, previews, clips, thumbnails and quote cards are stored at OVHcloud Object Storage in Frankfurt (Germany), encrypted by the provider. The app delivers them only to members of the workspace, through signed links valid for one hour; there are no public links. A background process on our servers in Germany produces the clips and quote cards. Transcripts, copy, approvals and the other data are stored in the database at Supabase (Ireland region, EU), logos, fonts and images of brand kits also in Supabase's file storage. Files imported from Google Drive, OneDrive, SharePoint, Dropbox, Box or the storage of your MAM or DAM are not copied (see those sections). ShowBits fetches episodes from published podcasts from their feed (see “Episodes from published podcasts”).
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription; Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Approved posts go to the platforms you have connected (see the sections on TikTok, Instagram and Facebook). If your workspace has connected the storage of its MAM or DAM, approved clips are also delivered there (see that section). If your workspace has connected a WordPress website, approved clips and quote cards go there when they are sent from ShowBits or picked in WordPress (see that section). If your workspace has connected an automation tool such as n8n, Zapier or Make, the tool receives the clips and episodes it asks for and passes them on as your workflows define (see that section). Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models. Animated quote cards go, like quote cards, to the platforms and systems your workspace has connected, as video with the episode's sound.
How long it is kept
Until the episode, the clip or the workspace is deleted or the contract ends. The original of an uploaded episode is deleted from storage automatically after 30 days; after that, its clips can no longer be re-cut. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest). We also delete the copy of the sound of an episode from a published podcast after 30 days.
How it is deleted
All members of a workspace can delete episodes and clips; ShowBits then deletes the files from storage within minutes. Admins can delete a workspace including all its content themselves, except the last workspace of an organisation. An owner who deletes their account can delete the whole organisation with it, including all workspaces and content (see “Deleting your account”). Further deletion on request to hello@showbits.ai.

Support requests

What data
Topic, subject and message; your name and email address; the workspace, organisation and plan; and automatically the page of the app you came from, your browser, the app version and your language.
Purpose
Answering your request.
How it is stored
In the database at Supabase (Ireland region, EU). We receive each request by email through Resend (EU); replies go to your email address. You see your own requests and their status in the app.
Who it is shared with
Only with our subprocessors, as far as needed to provide the service (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Until you delete your account, the organisation is deleted or the contract ends; then in accordance with our terms.
How it is deleted
With your account (see “Deleting your account”) or on request to hello@showbits.ai. The emails through which your requests reach us are deleted on request.

Audit log

What data
Who did what and when in the organisation, with the person's name: sign-ins, roles and invitations, connected services and AI keys, security settings, workspaces, uploads and deletions, approvals (through an automation also with the name the tool reports for the person who clicked), scheduling and posts, deliveries and exports of clips, embargo changes and changes to the billing details. Also imports from published podcasts with the feed, the episode and the declaration of holding the rights, and cancellations and withdrawals without signing in with their outcome, without names.
Purpose
Traceability and security for your organisation.
How it is stored
In the database at Supabase (Ireland region, EU). Entries cannot be changed or deleted; only when a person deletes their account do we remove from the entries what names them. Workspace admins see the log of their workspace, organisation admins that of the whole organisation.
Who it is shared with
Only with our subprocessors, as far as needed to provide the service (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Until the organisation is deleted. If a person deletes their account, the entries stay, but without their name and email address.
How it is deleted
With the organisation, on request to hello@showbits.ai or after the end of the contract in accordance with our terms.

Deleting your account

What data
If you signed in more than 10 minutes ago, you confirm it's you before the deletion: with a code from your authenticator app if you have set up a second factor, otherwise with a code by email. After the deletion: a confirmation of erasure with a reference number, the time, your email address and an overview of what was deleted (with the names of the organisations and workspaces) and what stays, without names of other people. If you signed up in the last 60 days: a pseudonymised key of your email address with the date until which this address gets no new trial. A sign-up without a trial, such as on Hobby, creates no such key.
Purpose
Deleting your account at your request (Art. 17 GDPR) and confirming the deletion to you. The key prevents the same address from getting a free trial again and again by deleting the account and signing up anew; the legal basis is our legitimate interest in this (Art. 6(1)(f) GDPR).
How it is stored
In the database at Supabase (Ireland region, EU). You can fetch the confirmation only in the browser you deleted the account with, as a page and as a PDF: that browser gets a random token in a cookie, and we store only its hash. We do not send the confirmation by email. The key is a hash (SHA-256) of your address in lower case, without a +suffix and, for Gmail, without dots; we do not store the address itself for this.
Who it is shared with
If an organisation deleted with your account has a subscription, we end it at Stripe and delete the customer data there. We revoke connections to YouTube, LinkedIn, X and Dropbox at the provider, YouTube not while the same Google account is connected in a workspace that stays. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
The confirmation 30 minutes; if you choose “Done” before that, we delete it at once. We keep no copy and cannot issue it a second time. The key until 60 days after you signed up. The record of the accepted terms and DPA (name of the organisation, your email address, your confirmation that you are acting as a business, versions and time) until 3 years after the organisation ends, without a link to your account, for the defence of legal claims (Art. 17(3)(e) GDPR). Invoices and payment records stay with our payment provider Stripe for the statutory retention period (Art. 17(3)(b) GDPR). Backups are overwritten within 90 days; our service providers (hosting, email delivery) delete their logs on their own schedules. For consumers, the record covers only the terms, without a DPA, and names the plan. Cancellations and withdrawals you declared without signing in remain for 3 years from their receipt (see “Cancelling and withdrawing without signing in”).
How it is deleted
Under “Your account” → “Delete account”; the dialog shows beforehand what will be deleted and what stays. Deleted are your sign-in with password, Google link, second factor, sessions and API tokens, your profile, your memberships and your support requests, as well as the organisations you own, with all their workspaces, content, files, connections, billing details and audit log. If other people work in one of them, you first transfer it to one of them or explicitly delete it for everyone. Only we delete organisations with an Enterprise or OnPremise contract; write to us at hello@showbits.ai. While an invoice is open, the account cannot be deleted. In other organisations, what you contributed stays there, without a link to your account; audit log entries lose what names you (name, email address), and the delivery records of Telegram notifications in organisations you belonged to until then lose your name. If your address is in another organisation's billing details, it stays there until its admins change it. What you published or handed over (posts on platforms, files in WordPress or in the storage of a MAM or DAM) stays there. We delete the confirmation, the key and the record automatically once their period ends.

10. Google user data

The ShowBits app (app.showbits.ai) can be connected to Google services. For each type of Google user data, this section describes which data ShowBits receives, what it is used for, how it is stored, who it is shared with, how long it is kept and how it is deleted.

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

Sign in with Google

Permission (scope): openid, email, profile

What data
Your name, your email address and your Google account ID.
Purpose
Sign-in, your account, assignment to workspaces and the log of sign-ins (audit log).
How it is stored
At Supabase in the EU.
Who it is shared with
Only with our subprocessors, as far as needed to provide the service (see “Sharing”).
How long it is kept
Until your account is deleted; audit entries in other organisations then lose your name and email address. If only an organisation is deleted, we delete its audit log; your profile (name, email address, language) and your sign-in account with your Google account ID are kept, because you can belong to several organisations, and so are audit entries in other organisations you have worked in.
How it is deleted
You can delete your account yourself in the app under “Your account” → “Delete account” (see “Deleting your account” in the app section), or write to us at hello@showbits.ai and we will delete it; with the account we also delete the link to your Google account. You can revoke ShowBits' access to your Google account at any time at myaccount.google.com/permissions.

Google Drive

Permission (scope): drive.readonly

ShowBits only accesses Google Drive if an admin of a workspace connects Drive. Admins can also watch a folder, so that new files in it are imported automatically.

What data
When browsing: folders as well as video and audio files from “My Drive” and “Shared with me”, with name, size, modification date and duration. When importing: the content of the selected file and its Drive ID and name. Also the email address of the connected Google account, which is shown in the app. If an admin chooses an import folder, ShowBits stores its Drive ID and name. If an admin watches a folder: its Drive ID and name, and for each file in it the Drive ID, name, size and modification date.
Purpose
Importing and transcribing episodes from Google Drive, by hand or automatically from a watched folder. Based on the transcript, ShowBits finds highlights and quotes with AI and, on request, creates AI suggestions: copy, headlines, translations and highlights.
How it is stored
The file list shown while browsing is not stored. On import, ShowBits stores the file's Drive ID and name with the episode. A background process at Fly.io (Frankfurt region) reads the file directly from Drive using range requests and extracts the audio track in memory only; it is not stored. The transcript and the highlight scores are stored in the database at Supabase (Ireland region, EU). The original file is neither copied nor stored. OAuth tokens are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU). They are only decrypted for calls to Google, on our servers in Dublin and Frankfurt. Access tokens expire after about an hour; ShowBits renews them with the stored refresh token. For a watch folder, the same background process lists the folder every two minutes and keeps the list of files it has seen (Drive ID, name, size, modification date and status) in the database at Supabase (Ireland region, EU); a new video or audio file is imported as soon as its size and modification date have not changed for ten minutes. Files that were already in the folder are not imported automatically, nor are files in subfolders. ShowBits does not modify, delete or share any files in your Drive.
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription. We have opted out of Deepgram's use of data for model improvement: Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Beyond that, only with our subprocessors, as far as needed to provide the service (see “Sharing”).
How long it is kept
OAuth tokens until the connection is disconnected, the workspace is deleted or the contract ends. Drive ID, name, transcript and highlight scores until the episode or the workspace is deleted or the contract ends. The account's email address and the import folder stay stored after disconnecting, until the workspace is deleted or the contract ends. A watch folder and its file list until an admin stops watching, the connection is disconnected or connected to another account, or the workspace is deleted; a file leaves the list when it leaves the folder. After the end of the contract, they are deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the stored tokens immediately. Admins can delete a workspace including all its content and tokens themselves, except the last workspace of an organisation. All members of a workspace can delete individual episodes; this also deletes the Drive ID, name, transcript, highlight scores and the clips and copy of the episode. If you revoke access at myaccount.google.com/permissions, the tokens become unusable immediately. Stopping a watch folder in the app deletes it and its file list.

YouTube

Permission (scope): youtube.force-ssl

Admins of a workspace can connect a YouTube channel so that approved clips are published there as a Short or a video. ShowBits publishes animated quote cards there as Shorts.

ShowBits uses YouTube API Services. By using the YouTube features of ShowBits, you agree to the YouTube Terms of Service. Processing by Google is governed by the Google Privacy Policy.

What data
When you connect: the channel's ID and name and the access and refresh tokens. After the upload: the video's ID and its processing status at YouTube. ShowBits does not read, change or delete other videos, playlists, comments or analytics.
Purpose
Publishing clips that people approved in ShowBits on your YouTube channel at the scheduled time, with the title, description, visibility and the information on children and altered content that your team chose. Deleting a video that ShowBits uploaded when an admin or duty editor asks for it. Checking every 30 days that the uploaded videos still exist.
How it is stored
Access and refresh tokens are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU). ShowBits also stores the channel's ID and name there, and with each scheduled post the video ID, the link and the time and result of the upload (success or error message).
Who it is shared with
YouTube (Google) receives what you publish there: the video, the title and description, and the visibility and the information on children and altered content. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Tokens until an admin disconnects the channel, the workspace is deleted or the contract ends. ShowBits deletes the IDs of uploaded videos when its access ends. Link and upload result until the clip or the workspace is deleted or the contract ends. After the end of the contract, the data is deleted according to our Terms (30 days after the contract ends, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app revokes ShowBits' access at Google and deletes the tokens, as does deleting the workspace. This ends the whole grant of that Google account, so a Google Drive connection with the same account has to be connected again. You can also revoke access at any time at security.google.com/settings/security/permissions. Videos already uploaded stay on YouTube until you delete them, there or through ShowBits.

Sharing

ShowBits does not use Google user data for advertising and does not sell it. We only share it with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models.

Deletion and revocation

“Disconnect” in the app deletes the stored tokens. You can revoke access at any time at myaccount.google.com/permissions. Admins can delete workspaces including all their content and tokens themselves, except the last workspace of an organisation. An owner can delete an entire organisation, with all workspaces and content, tokens and the organisation's audit log, together with their account in the app, except under an Enterprise or OnPremise contract; otherwise we delete it on request or after the end of the contract in accordance with our terms. You can delete your account yourself under “Your account” → “Delete account”, or request the deletion by email to hello@showbits.ai.

11. Dropbox

The ShowBits app (app.showbits.ai) can be connected to Dropbox to import episodes from Dropbox. ShowBits only accesses Dropbox if an admin of a workspace connects Dropbox. The connection runs through Dropbox's sign-in page, where you can see which permissions ShowBits receives and can decline them. ShowBits never receives your Dropbox password. After that, the members of the workspace can browse and import files through this connection. Admins can also watch a folder, so that new files in it are imported automatically.

ShowBits only requests read access: basic account information, file and folder metadata, and file content. We only use data that ShowBits receives from Dropbox for the purposes described below. We do not sell it and do not use it for advertising.

Your use of Dropbox is governed by Dropbox's Privacy Policy.

Importing episodes from Dropbox

Permission (scope): account_info.read, files.metadata.read, files.content.read

What data
When browsing and searching: folders as well as video and audio files, with name, size and modification date. When importing: the content of the selected file and its Dropbox ID and name. Also the email address of the connected Dropbox account (or its display name if Dropbox provides no email address), which is shown in the app. If an admin chooses an import folder, ShowBits stores its Dropbox ID and name. If an admin watches a folder: its Dropbox ID and name, and for each file in it the Dropbox ID, name, size and modification date.
Purpose
Importing and transcribing episodes from Dropbox, by hand or automatically from a watched folder. Based on the transcript, ShowBits finds highlights and quotes with AI and, on request, creates AI suggestions: copy, headlines, translations and highlights.
How it is stored
The file list shown while browsing is not stored. On import, ShowBits stores the file's Dropbox ID and name with the episode. A background process at Fly.io (Frankfurt region) reads the file directly from Dropbox using range requests, through a temporary link that Dropbox issues for four hours. It extracts the audio track in memory only; it is not stored. The transcript and the highlight scores are stored in the database at Supabase (Ireland region, EU). The original file is neither copied nor stored. OAuth tokens are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU), and are only decrypted for calls to Dropbox on our servers. Access tokens expire after about four hours; ShowBits renews them with the stored refresh token. For a watch folder, the same background process lists the folder every two minutes and keeps the list of files it has seen (Dropbox ID, name, size, modification date and status) in the database at Supabase (Ireland region, EU); a new video or audio file is imported as soon as its size and modification date have not changed for ten minutes. Files that were already in the folder are not imported automatically, nor are files in subfolders. ShowBits does not modify, delete or share any files in your Dropbox.
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription. We have opted out of Deepgram's use of data for model improvement: Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models.
How long it is kept
OAuth tokens until the connection is disconnected, the workspace is deleted or the contract ends. Dropbox ID, name, transcript and highlight scores until the episode or the workspace is deleted or the contract ends. The account's email address or name and the import folder stay stored after disconnecting, until the workspace is deleted or the contract ends. A watch folder and its file list until an admin stops watching, the connection is disconnected or connected to another account, or the workspace is deleted; a file leaves the list when it leaves the folder. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app revokes ShowBits' access at Dropbox and deletes the stored tokens immediately. You can also remove access yourself in your Dropbox account under Settings → Connected apps; the tokens then become unusable immediately. Admins can delete a workspace including all its content and tokens themselves, except the last workspace of an organisation. All members of a workspace can delete individual episodes; this also deletes the Dropbox ID, name, transcript, highlight scores and the clips and copy of the episode. Stopping a watch folder in the app deletes it and its file list. Further deletion on request to hello@showbits.ai.

12. Box

The ShowBits app (app.showbits.ai) can be connected to Box to import episodes from Box. ShowBits only accesses Box if an admin of a workspace connects Box. The connection runs through Box's sign-in page, where you can see which permissions ShowBits receives and can decline them. ShowBits never receives your Box password. For enterprise accounts, your company's Box admin may have to allow ShowBits once. After that, the members of the workspace can browse and import files through this connection. Admins can also watch a folder, so that new files in it are imported automatically.

ShowBits only requests read access to the account's files and folders. We only use data that ShowBits receives from Box for the purposes described below. We do not sell it and do not use it for advertising.

Your use of Box is governed by Box's Privacy Notice.

Importing episodes from Box

Permission (scope): root_readonly

What data
When browsing and searching: folders as well as video and audio files under “All Files”, including items shared with the account, with name, size and modification date. When importing: the content of the selected file and its Box ID and name. Also the login email address of the connected Box account, which is shown in the app. If an admin chooses an import folder, ShowBits stores its Box ID and name. If an admin watches a folder: its Box ID and name, and for each file in it the Box ID, name, size and modification date.
Purpose
Importing and transcribing episodes from Box, by hand or automatically from a watched folder. Based on the transcript, ShowBits finds highlights and quotes with AI and, on request, creates AI suggestions: copy, headlines, translations and highlights.
How it is stored
The file list shown while browsing is not stored. On import, ShowBits stores the file's Box ID and name with the episode. A background process at Fly.io (Frankfurt region) reads the file directly from Box using range requests and extracts the audio track in memory only; it is not stored. The transcript and the highlight scores are stored in the database at Supabase (Ireland region, EU). The original file is neither copied nor stored. OAuth tokens are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU), and are only decrypted for calls to Box on our servers. Access tokens expire after about an hour; ShowBits renews them with the stored refresh token, which Box replaces with a new one each time. For a watch folder, the same background process lists the folder every two minutes and keeps the list of files it has seen (Box ID, name, size, modification date and status) in the database at Supabase (Ireland region, EU); a new video or audio file is imported as soon as its size and modification date have not changed for ten minutes. Files that were already in the folder are not imported automatically, nor are files in subfolders. ShowBits does not modify, delete or share any files in your Box account.
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription. We have opted out of Deepgram's use of data for model improvement: Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models.
How long it is kept
OAuth tokens until the connection is disconnected, the workspace is deleted or the contract ends. Box ID, name, transcript and highlight scores until the episode or the workspace is deleted or the contract ends. The account's email address and the import folder stay stored after disconnecting, until the workspace is deleted or the contract ends. A watch folder and its file list until an admin stops watching, the connection is disconnected or connected to another account, or the workspace is deleted; a file leaves the list when it leaves the folder. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the stored tokens immediately. You can also remove ShowBits' access in the security settings of your Box account; the tokens then become unusable. Admins can delete a workspace including all its content and tokens themselves, except the last workspace of an organisation. All members of a workspace can delete individual episodes; this also deletes the Box ID, name, transcript, highlight scores and the clips and copy of the episode. Stopping a watch folder in the app deletes it and its file list. Further deletion on request to hello@showbits.ai.

13. Microsoft OneDrive and SharePoint

The ShowBits app (app.showbits.ai) can be connected to Microsoft OneDrive and SharePoint to import episodes from there. ShowBits only accesses OneDrive and SharePoint if an admin of a workspace connects them. The connection runs through Microsoft's sign-in page, for work and school accounts as well as personal Microsoft accounts. There you can see which permissions ShowBits receives and can decline them. ShowBits never receives your Microsoft password. In many organisations, an administrator has to approve ShowBits once for the whole organisation; ShowBits offers a link for your IT to do so. After that, the members of the workspace can browse and import files through this connection. Admins can also watch a folder, so that new files in it are imported automatically.

ShowBits only requests read access: to the files the connecting person can open (their own OneDrive, files shared with them and SharePoint libraries, including the files of Teams), to their SharePoint sites, and to basic profile information (name, email address and account ID). ShowBits does not modify or delete anything in OneDrive or SharePoint. We only use data that ShowBits receives from Microsoft for the purposes described below. We do not sell it and do not use it for advertising.

Your use of OneDrive and SharePoint is governed by the Microsoft Privacy Statement.

Importing episodes from OneDrive and SharePoint

Permission (scope): Files.Read.All, Sites.Read.All, User.Read, openid, profile, email, offline_access

What data
When browsing and searching: folders as well as video and audio files in your own OneDrive, including shared folders that you added to “My files”, and for work and school accounts the SharePoint sites with their document libraries, with name, size, modification date and duration. When importing: the content of the selected file and its ID and name. Also the email address of the connected Microsoft account (if there is none, its sign-in name or display name), which is shown in the app, and the account's ID. If an admin chooses an import folder, ShowBits stores its ID and name. If an admin watches a folder: its ID and name, and for each file in it the ID, name, size and modification date.
Purpose
Importing and transcribing episodes from OneDrive and SharePoint, by hand or automatically from a watched folder. Based on the transcript, ShowBits finds highlights and quotes with AI and, on request, creates AI suggestions: copy, headlines, translations and highlights.
How it is stored
The file list shown while browsing is not stored. On import, ShowBits stores the file's ID and name with the episode. A background process on our servers in Germany reads the file directly from OneDrive or SharePoint using range requests, through a short-lived download link that Microsoft issues for the file, and extracts the audio track in memory only; it is not stored. The transcript and the highlight scores are stored in the database at Supabase (Ireland region, EU). The original file is neither copied nor stored. The OAuth tokens and the account's ID are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU), and are only decrypted for calls to Microsoft on our servers. Access tokens expire after about an hour; ShowBits renews them with the stored refresh token, which Microsoft replaces with a new one each time. For a watch folder, the background process lists the folder every two minutes and keeps the list of files it has seen (ID, name, size, modification date and status) in the database at Supabase (Ireland region, EU); a new video or audio file is imported as soon as its size and modification date have not changed for ten minutes. Files that were already in the folder are not imported automatically, nor are files in subfolders. ShowBits does not modify, delete or share any files in OneDrive or SharePoint.
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription. We have opted out of Deepgram's use of data for model improvement: Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models.
How long it is kept
OAuth tokens until the connection is disconnected, the workspace is deleted or the contract ends. File ID, name, transcript and highlight scores until the episode or the workspace is deleted or the contract ends. The account's email address or name and the import folder stay stored after disconnecting, until the workspace is deleted or the contract ends. A watch folder and its file list until an admin stops watching, the connection is disconnected or connected to another account, or the workspace is deleted; a file leaves the list when it leaves the folder. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the stored tokens immediately. Microsoft offers no way to revoke the access of a single app (only all sessions of a person), so ShowBits cannot withdraw it at Microsoft; you can remove ShowBits yourself at myapps.microsoft.com (work or school account) or account.live.com/consent/Manage (personal account), and your IT can withdraw the organisation's approval in the Microsoft Entra admin center under Enterprise applications. Admins can delete a workspace including all its content and tokens themselves, except the last workspace of an organisation. All members of a workspace can delete individual episodes; this also deletes the file ID, name, transcript, highlight scores and the clips and copy of the episode. Stopping a watch folder in the app deletes it and its file list. Further deletion on request to hello@showbits.ai.

14. MAM and DAM storage (S3-compatible)

On the Enterprise and OnPremise plans, a workspace can connect the S3-compatible storage of its media asset management (MAM) or digital asset management (DAM) system: to import episodes from there, to watch folders and to deliver approved clips into a folder there. Only admins of the workspace connect the storage, in the app and not through the API: they enter the storage's address (endpoint), region and bucket and an access key with its secret. The storage belongs to your company or to the provider your company has chosen; ShowBits does not add a provider of its own for it. ShowBits connects only to the address entered, in the cloud only to public addresses over https. After that, the members of the workspace can browse and import files.

For importing, ShowBits needs read access to the bucket, and write access only in the delivery folder. We only use data from this storage for the purposes described below. We do not sell it and do not use it for advertising.

Importing episodes and watching folders

Permission (scope): s3:ListBucket, s3:GetObject

What data
When connecting: endpoint, region, bucket, and the access key with its secret. When browsing and searching: folders as well as video and audio files, with name, size and modification date. When importing: the content of the selected file and its object key and name. If an admin chooses an import folder, ShowBits stores its key and name. If an admin watches a folder: its key and name, and for each file in it the key, name, size and modification date.
Purpose
Importing and transcribing episodes from your MAM or DAM, by hand or automatically from a watched folder (hot folder). Based on the transcript, ShowBits finds highlights and quotes with AI and, on request, creates AI suggestions: copy, headlines, translations and highlights.
How it is stored
Before saving, ShowBits checks the access with a single listing request. Endpoint, region, bucket, access key and secret are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU); the secret is never shown again. The app shows the connection as “bucket · host”. The file list shown while browsing is not stored. On import, ShowBits stores the file's object key and name with the episode. A background process on our servers in Germany reads the file directly from your storage using range requests, through a signed link valid for twelve hours, and extracts the audio track in memory only; it is not stored. The transcript and the highlight scores are stored in the database at Supabase (Ireland region, EU). The original file is neither copied nor stored. For a watch folder, the background process lists the folder every two minutes and keeps the list of files it has seen (key, name, size, modification date and status) in the database at Supabase (Ireland region, EU); a new video or audio file is imported as soon as its size and modification date have not changed for ten minutes. Files that were already in the folder are not imported automatically, nor are files in subfolders.
Who it is shared with
The audio track is sent to Deepgram (EU endpoint) for transcription. We have opted out of Deepgram's use of data for model improvement: Deepgram keeps audio and transcript only for the duration of the request and does not use them for training. For the AI analysis (highlights and quotes), the transcript is sent to the AI provider whose key your organisation has added; AI suggestions for copy, headlines and translations are only created when you request them, with excerpts of the transcript. Your company's contract with that provider applies. Without such a key, ShowBits uses its own accounts at Anthropic, OpenAI and Typesafe.ai, our subprocessors: they process the transcript and the excerpts on our behalf, under data processing agreements, through EU endpoints and with zero data retention, so they do not keep the content after answering and do not use it for training. Beyond that, only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service. Customer data is not used to train AI models.
How long it is kept
Access data until an admin disconnects the storage, the workspace is deleted or the contract ends. Object key, name, transcript and highlight scores until the episode or the workspace is deleted or the contract ends. The connection's name (“bucket · host”) and the import folder stay stored after disconnecting, until the workspace is deleted or the contract ends. A watch folder and its file list until an admin stops watching, the storage is disconnected or connected with another bucket or host, or the workspace is deleted; a file leaves the list when it leaves the folder. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the access data immediately and ends the watch folders and the delivery folder. You can also deactivate the access key in your storage at any time. Admins can delete a workspace including all its content and access data themselves, except the last workspace of an organisation. All members of a workspace can delete individual episodes; this also deletes the object key, name, transcript, highlight scores and the clips and copy of the episode. Stopping a watch folder in the app deletes it and its file list. Further deletion on request to hello@showbits.ai.

Delivering approved clips

Permission (scope): s3:PutObject (delivery folder only)

What data
For each clip and version, ShowBits writes into the delivery folder: the video, the subtitles (WebVTT), the thumbnails or the images of a quote card, and a file clip.json with the workspace, the show, the episode (title, language, embargo, source file) and the clip (kind, title, format, in and out points, duration, text, headline, hashtags, the quote with the name of the person quoted, copy per channel, time of approval), plus the list of files. Clips and images can show and quote people from the episode. In ShowBits: the delivery folder (key and name), whether approved clips are delivered automatically, who changed this and when, and for each clip a delivery record (version, status, attempts, error, location, who requested the delivery, times). If a quote card is animated, its videos with the sound from the episode are included.
Purpose
Handing approved clips with their metadata to your MAM or DAM, so that your team can use them there, for example before airtime.
How it is stored
The background process on our servers in Germany copies the files from our media storage at OVHcloud (Frankfurt) into a folder of their own for each clip and version in your delivery folder, and writes clip.json last. A delivery starts when a clip receives its final approval and automatic delivery is switched on, again when a clip that was already delivered gets a new video or new images, or when a member with write access delivers a clip by hand. Clips are delivered even before the episode's embargo ends; clip.json names the embargo. Publishing on social media still requires approval and the schedule in ShowBits. Delivery settings and delivery records are stored in the database at Supabase (Ireland region, EU). Changes to the delivery settings, deliveries by hand, deliveries and failed deliveries are recorded in the audit log; deliveries and failed deliveries can also trigger your workspace's webhooks.
Who it is shared with
The files go only to the storage your workspace connected. Beyond that, only to our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service.
How long it is kept
Files in your storage belong to your company: ShowBits does not delete them, not even when the clip is deleted or sent back. The delivery settings until the storage is disconnected or connected with another bucket or host, or the workspace is deleted. Delivery records until the clip or the workspace is deleted or the contract ends. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
You delete delivered files in your storage. Admins can switch off automatic delivery; “Disconnect” in the app deletes the access data and the delivery settings. Delivery records are deleted with the clip or the workspace. Further deletion on request to hello@showbits.ai.

15. Episodes from published podcasts

On every plan, a member of a workspace with write access can import episodes directly from a published podcast: found by searching Apple Podcasts and Podcast Index or through a link to Apple Podcasts or to the RSS feed. Before each import, the person declares that the podcast is theirs or that they have its owners' permission to edit it and publish excerpts from it. Anyone who believes their rights are infringed finds our procedure under Report an infringement.

Search, import and origin

What data
What you type into the search or paste as a link; the podcast's feed as it is publicly available (title, description, author, image and episodes); for an imported episode, the address of its audio file, the audio file itself, a hash of the bytes fetched and, where the feed has one, its transcript with timings. In the audit log: who imported which episode from which feed and when, declaring that they hold the rights.
Purpose
To find the podcast, import the episode and process it like an uploaded episode (transcript, quotes, quote cards). The hash shows which version of the file was processed, because some hosts insert different ads with every download. The audit log entry shows who declared the rights, in case a rights holder gets in touch.
How it is stored
The search queries Apple (iTunes Search API) and Podcast Index from our server; they receive only the search term (Apple also the country of the directory, derived from your language), nothing about you. Our server fetches the feed, the audio file and the transcript with the user agent ShowBits-bot/1.0 from the addresses the feed gives; the podcast's host sees our server's address, not yours. ShowBits keeps a copy of the sound (Opus, without picture) in OVHcloud Object Storage in Frankfurt (Germany) only where it is needed: for episodes whose feed has no transcript, and for animated quote cards. If the feed has a transcript, ShowBits takes it instead of transcribing the episode. Everything else is stored in the database at Supabase (Ireland region, EU).
Who it is shared with
Deepgram (EU endpoint) transcribes the episode if the feed has no transcript. If it has one, Deepgram hears only the passages around the quotes of animated quote cards, to find the words in the sound. Beyond that, as for uploaded episodes (see “Episodes, clips and quote cards”).
How long it is kept
The copy of the sound for 30 days, after which it is deleted automatically. The transcript, quotes and quote cards, the episode's address, its feed and the hash until the episode, the workspace or the organisation is deleted or the contract ends. The audit log entry like the audit log (see “Audit log”).
How it is deleted
Members of the workspace delete episodes themselves (see “Episodes, clips and quote cards”). ShowBits does not change or delete the podcast itself or its feed.

16. WordPress (ShowBits plugin)

On every plan, a workspace can connect WordPress websites through the ShowBits plugin, to bring approved clips and quote cards into the website's media library. Only admins of the workspace and owners and admins of the organisation connect a website, in the app and not through the API: they create a site key for the website's address, shown once and valid for 24 hours, which a WordPress user who may manage the website's settings enters in the plugin; or they approve the connection on a consent page in ShowBits. The plugin then receives a key of its own that only opens its own functions, not the REST API. The website belongs to your company or to the hosting provider your company has chosen; ShowBits does not add a provider of its own for it and connects only to the website's own address, in the cloud only to public addresses over https.

In your WordPress, the plugin stores its connection with the key and the secret encrypted, its settings and a list of imports with the WordPress account that started each. Uninstalling the plugin disconnects the website, as far as ShowBits can be reached, and deletes this data; imported files stay in the media library. We only use data from this connection for the purposes described below. We do not sell it and do not use it for advertising.

Connecting a website

What data
From the plugin: the website's address and name, the address at which the plugin receives files (push address) and the plugin's version. In ShowBits: for each site key, its hash and last four characters, the website's host (on the consent page also its name), who created it and when, the number of tries and when it was used or withdrawn; for each connected website, its address, name and push address, the plugin's version, who connected it and when, and when the plugin last called; the website's own key only as a hash, and the secret that signs messages to the website. In the audit log: site keys created by hand, and websites connected and disconnected.
Purpose
Connecting your WordPress websites securely and showing your team which websites are connected.
How it is stored
In the database at Supabase (Ireland region, EU). Site keys and the website's own key are stored only as hashes; a site key is shown once. The secret is encrypted with AES-256-GCM. When connecting, ShowBits sends a single request to the push address, and the website proves with its answer that it is the website that asked. Members of the workspace see which websites are connected; keys, secret and push address stay hidden from them. Connecting and disconnecting can also trigger your workspace's webhooks.
Who it is shared with
Only with our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service.
How long it is kept
A connected website until it is disconnected, in ShowBits or in the plugin, the workspace is deleted or the contract ends. Site keys until the workspace is deleted; expired keys are removed earlier, when the workspace creates a new key. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
Admins of the workspace and owners and admins of the organisation can disconnect a website in ShowBits, and the plugin can disconnect it too. Disconnecting deletes the website's key, its secret and its transfers in ShowBits immediately. Open site keys can be withdrawn before they are used. Admins can delete a workspace including all its content and connections themselves, except the last workspace of an organisation. Further deletion on request to hello@showbits.ai.

Clips and quote cards in the media library

What data
The approved clips and quote cards of the workspace whose episode is no longer under embargo, as the plugin lists them in WordPress: title, text, hashtags, duration, format, time of approval, the quote with the name of the person quoted, episode (title and language) and show, and a small preview image. For each clip or quote card brought into WordPress: the video with its thumbnail, or the image of the quote card in the chosen format, with this information. Clips and images can show and quote people from the episode. In ShowBits, for each transfer: website, clip, format, who sent it or whether the website asked for it, attempts, status and errors, and the plugin's report with the address of the file in the media library or the reason the import failed. In the audit log: clips sent from ShowBits, and every file the website fetched. If a quote card is animated, its videos with the sound from the episode are included.
Purpose
Bringing approved clips and quote cards into your website's media library, picked in WordPress or sent from ShowBits.
How it is stored
Anyone who may upload media in your WordPress sees the list in the plugin; their browser loads the preview images from our media storage at OVHcloud (Frankfurt), through links valid for one hour. Nothing leaves ShowBits without approval or before the episode's embargo ends; clips under embargo do not appear in the plugin at all. A background process on our servers in Germany announces each transfer at the push address with a signed message and a ticket; the ticket opens only the files of that clip, until the website reports back. The website then loads the files from our media storage at OVHcloud (Frankfurt), through links valid for ten minutes. Transfers are stored in the database at Supabase (Ireland region, EU); clips sent from ShowBits can also trigger your workspace's webhooks.
Who it is shared with
The files and their information go only to the website your workspace connected. Beyond that, only to our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service.
How long it is kept
Files in your media library belong to your company. Like every file there, they can be reached publicly, and they stay as they are when the clip is changed, withdrawn or deleted in ShowBits; ShowBits does not delete them. Transfers for 30 days, or until the website is disconnected or the clip or the workspace is deleted. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
You delete imported files in WordPress. Transfers are deleted after 30 days, or with the website's connection, the clip or the workspace. Further deletion on request to hello@showbits.ai.

17. Automations (n8n, Zapier, Make)

On every plan, a workspace can connect automation tools such as n8n, Zapier or Make, for example to approve clips from a chat such as Slack or Microsoft Teams, to notify the team or to start a workflow when an embargo ends. Only admins of the workspace and owners and admins of the organisation create such a connection, in the app and not through the API. The connection receives a key of its own, shown once, which only opens the automation functions, not the REST API: reading clips and episodes, giving or sending back an approval step, and webhooks for clips and episodes. Your company chooses the tool and uses it with its own account or installation, as it does the services its workflows pass data on to; ShowBits does not add a provider of its own for them. In the cloud, ShowBits sends webhooks only to public addresses over https.

We only use data from these connections for the purposes described below. We do not sell it and do not use it for advertising.

Connections and webhooks

What data
For each connection: its name, the tool (n8n, Zapier, Make or another), whether it may see clips and episodes under embargo, the person responsible for it (who created it or took it over), who created it and when, the last four characters of the key and when the tool last called; the key itself only as a hash. Requests are counted per connection and minute. For each webhook of a connection: the address in the tool, the events, a description, who created it and when, its status and the secret that signs the messages; for each message: the event, its content (only IDs and fields such as status and times, never names, titles, texts or comments), the attempts and the last answer. In the audit log: connections created, taken over and revoked, and webhooks created and deleted.
Purpose
Connecting your automation tools securely, limiting what they can do and how often, and showing admins which connections exist and who is responsible for them.
How it is stored
In the database at Supabase (Ireland region, EU). The key is shown once and stored only as a hash; the secret is encrypted with AES-256-GCM. Only admins of the workspace and owners and admins of the organisation see the connections. The tool's requests go to the automation functions of the app at app.showbits.ai. A background process on our servers in Germany sends the webhooks as signed messages to the address in the tool and repeats failed messages for about a day.
Who it is shared with
The messages go only to the addresses registered for your connections. Beyond that, only to our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service.
How long it is kept
A connection with its webhooks until it is revoked, the workspace is deleted or the contract ends. Request counters until the connection's next request; messages for 30 days. Audit log entries as described in the app section. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
Admins of the workspace and owners and admins of the organisation can revoke a connection in ShowBits: its key stops working at once, and the connection is deleted with its webhooks and their messages. A single webhook can also be deleted, in ShowBits or by the tool. Admins can delete a workspace including all its content and connections themselves, except the last workspace of an organisation. Further deletion on request to hello@showbits.ai.

Clips, episodes and approvals

What data
What the tool reads through the connection: clips with title, text, hashtags, translations of the text, format, times, status and approval step, the quote with the name of the person quoted, the episode (title and language) and links to the video, the subtitles (WebVTT) and the images; episodes with title, language, length, show, embargo, time of the analysis and the number of clips per status; both with a link into ShowBits. Clips and images can show and quote people from the episode. For approvals and send-backs through the connection: the step, an optional comment and the name the tool reports for the person who clicked, for example a display name in Slack; this person may have no ShowBits account. For animated quote cards, also links to their videos.
Purpose
Running your company's workflows, for example showing clips for approval in a chat, recording the decision in ShowBits or notifying your team.
How it is stored
The links to the files are signed and valid for one hour; whoever opens them loads the files from our media storage at OVHcloud (Frankfurt). Clips and episodes under embargo reach a connection only if this was allowed when it was created; otherwise they stay hidden from it until the embargo ends. An approval through a connection is given in the name of the person responsible for it; the audit log keeps the connection and the reported name as the tool sent it. ShowBits cannot check that name. Approvals are stored in the database at Supabase (Ireland region, EU) and can trigger your workspace's webhooks.
Who it is shared with
Your tool receives what it reads and passes it on wherever your workflows send it, for example to Slack, Microsoft Teams, email or your website. ShowBits itself passes the data only to our subprocessors (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe), as far as needed to provide the service.
How long it is kept
The step and the comment with the clip's approvals, until the clip or the workspace is deleted; the reported name in the audit log, until the organisation is deleted, also after the connection is revoked. Copies in your tool and in the services it passes data on to are subject to their rules and your settings there. After the end of the contract, the data is deleted in accordance with our terms (30 days after the end of the contract, backups after 90 days at the latest).
How it is deleted
You delete copies in your tool and in the services it passes data on to there. Approvals are deleted with the clip or the workspace; entries in the audit log cannot be changed or deleted, except when a person deletes their account (see the app section), and are deleted with the organisation, on request to hello@showbits.ai or after the end of the contract in accordance with our terms.

18. Approval notifications via Telegram

In the ShowBits app, a workspace can connect its own Telegram bot and register a Telegram group for approval notifications. For each approval step (submitted, forwarded, approved, sent back), ShowBits sends one sentence to this group with the title of the clip, the title of the episode and the step, linked to the clip in the app. Names, comments, post texts and dates are not sent. Link previews are switched off, so Telegram does not open the link itself.

In the registered group, the bot also answers commands: /status with the number of clips waiting at each approval stage, /approvals with a link to the approvals list and /help with the list of commands. When a group is registered and in a test message, ShowBits sends the name of the workspace. ShowBits only processes commands addressed to the bot and changes to the bot's group membership; it does not store other messages from the group.

The bot belongs to your company. Your company's relationship with Telegram applies to the use of Telegram.

Once the clip, the episode, the workspace or the organisation is deleted, the link no longer works. Messages already delivered remain with Telegram; ShowBits does not delete them.

We store the bot token per workspace, encrypted, in the database at Supabase (Ireland region, EU), together with the bot's username, the language of the notifications and the ID and name of the registered group. They are deleted when the bot is disconnected in the app or the workspace is deleted. For each notification we keep a delivery record with the step, the delivery status and, from the approval history, the name of the person and their comment; name and comment are not sent to Telegram. Delivery records are deleted with the clip or the workspace; if a person deletes their account, we remove their name from the records of the organisations they belonged to until then.

19. Posting to TikTok

In the ShowBits app, an administrator of a workspace can connect a TikTok account so that approved clips are published on that TikTok channel. The connection runs through TikTok's own sign-in page. There you see which permissions ShowBits receives and can decline them. ShowBits never receives your TikTok password. ShowBits also publishes animated quote cards there as videos.

TikTok is currently reviewing this feature. Until the review is complete, TikTok publishes posts from ShowBits only privately (“Only me”).

We use data that ShowBits receives from TikTok only to prepare and publish your posts. We do not sell it, do not use it for advertising and do not train AI models with it.

Your use of TikTok, and anything that happens to a video on TikTok after it is published, is governed by TikTok's Terms of Service and Privacy Policy.

Connecting a TikTok account and posting

Permission (scope): user.info.basic, video.publish

What data
When you connect: your TikTok account's identifier for ShowBits (Open ID), the display name, the permissions granted, and access and refresh tokens. When a person prepares a post, and again right before sending, ShowBits asks TikTok for the account's current settings: username, display name, profile picture, the visibility options allowed, whether comments, duets and stitches are switched off, and the maximum video length. After publishing, ShowBits receives the post's ID and builds the link to the video from it. ShowBits does not read videos, followers, view counts, comments or messages from your account.
Purpose
Showing the connected account in the app, preparing posts as TikTok requires and publishing approved clips on your channel at the scheduled time. A person prepares every post: they see the account, choose the visibility, decide whether comments, duets and stitches are allowed, label paid partnerships or own-brand content and can edit the caption. Right before sending, ShowBits checks again that the clip is approved, the embargo has ended and the same account is connected. ShowBits does not change or delete videos on TikTok.
How it is stored
Tokens and the Open ID are stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU). They are decrypted only for calls to TikTok, on our servers in Dublin and Frankfurt. Access tokens expire after 24 hours; ShowBits renews them with the refresh token, which is valid for one year. Also at Supabase, ShowBits stores the account's display name and, with each scheduled post, the post settings including the account's Open ID, who saved them and when, TikTok's publishing ID, the link to the video, and the status and failure reason of the delivery. Preparing a post is recorded in the audit log with the clip title and the chosen visibility. The other account settings ShowBits asks for are not stored; your browser loads the profile picture directly from TikTok.
Who it is shared with
TikTok receives the approved clip as a video file, the caption, the chosen visibility, the settings for comments, duets and stitches, the paid partnership or own-brand label and, if chosen, the cover frame. A background process at Fly.io (Frankfurt region) uploads the video file to TikTok. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Tokens and the Open ID until the connection is removed, the workspace is deleted or the contract ends. The account's display name until the workspace is deleted; it stays stored after disconnecting. Post settings, publishing ID, link and delivery status until the clip or the workspace is deleted or the contract ends. Audit entries until the organisation is deleted. After the contract ends, the data is deleted according to our Terms (30 days after the contract ends, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the tokens immediately, as does deleting the workspace. You can also revoke ShowBits' access at any time in your TikTok account settings under the permissions for apps and services; the tokens then stop working. Videos already published stay on TikTok until you delete them there.

20. Posting to Instagram and Facebook

In the ShowBits app, an administrator of a workspace can connect an Instagram account (business or creator account) and a Facebook page so that approved clips and quote cards are published there. The connection runs through the sign-in pages of Instagram and Facebook. There you see which permissions ShowBits receives and can decline them. ShowBits never receives your password.

Meta is currently reviewing ShowBits (App Review). Until the review is complete, only Instagram and Facebook accounts that have a role in ShowBits' Meta app can be connected.

Scheduled posts go out automatically at their scheduled time, with the text and hashtags set in ShowBits for the channel. Right before sending, ShowBits checks again that the clip is approved and the embargo has ended. A post that is more than six hours late no longer goes out by itself.

We use data that ShowBits receives from Instagram and Facebook only to connect your accounts and publish your posts. We do not sell it, do not use it for advertising and do not train AI models with it.

Your use of Instagram and Facebook, and anything that happens to a video there after it is published, is governed by the Instagram Terms of Use, the Facebook Terms of Service and the Meta Privacy Policy.

Instagram

Permission (scope): instagram_business_basic, instagram_business_content_publish

What data
When you connect: your Instagram account's IDs, the username, the permissions granted and an access token. After publishing: the post's ID at Instagram and the link to the post. ShowBits does not read posts, followers, insights, comments or messages from your account.
Purpose
Showing the connected account in the app (“connected as @…”) and publishing approved clips at the scheduled time as a Reel that also appears in the feed, with the chosen cover frame if set, and approved quote cards as an image in 4:5 format. ShowBits deletes posts on Instagram only if an admin has allowed it, and only posts that ShowBits published itself (see “Deleting published posts”). Otherwise, to take a post down, you delete it on Instagram and confirm that in ShowBits. ShowBits publishes animated quote cards as reels.
How it is stored
The access token is stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU). It is decrypted only for calls to Instagram, on our servers in Dublin and Frankfurt. It is valid for 60 days; ShowBits renews it before it expires. Also at Supabase, ShowBits stores the account's username and IDs, so that deletion requests from Meta can be matched, and with each scheduled post the ID at Instagram, the link, and the status and failure reason of the delivery.
Who it is shared with
Instagram receives the text with the hashtags and, if set, the chosen cover frame. Instagram fetches the video file or the image itself from our media storage through a signed address that is valid for six hours at most. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Token and IDs until the connection is removed, the workspace is deleted, Meta sends us a deletion request or the contract ends. The username until the workspace is deleted or a deletion request from Meta arrives; it stays stored after disconnecting. A post's ID, link and delivery status until the clip or the workspace is deleted or the contract ends. Audit entries until the organisation is deleted. After the contract ends, the data is deleted according to our Terms (30 days after the contract ends, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the token, the IDs and any permission to delete posts immediately, as does deleting the workspace. You can also remove ShowBits' access in the Instagram settings under “Apps and websites” and request deletion of your data there (see “Deletion through Meta”). Posts already published stay on Instagram until you delete them there or through ShowBits.

Facebook pages

Permission (scope): pages_show_list, pages_read_engagement, pages_manage_posts

What data
When you connect: your Facebook user ID for ShowBits, the permissions granted and the list of pages you give ShowBits access to, with ID, name, page token and your roles on the page. Of these, only the one page you choose is stored. After publishing: the ID of the video or photo at Facebook and its link. ShowBits does not read posts, followers, insights, comments or messages of your page.
Purpose
Showing the connected page in the app and publishing approved clips on the page at the scheduled time: vertical clips of 3 to 90 seconds as a Reel, all others as a video, and approved quote cards as a photo. When an admin or duty editor takes a post down in ShowBits that ShowBits published itself, ShowBits deletes it on the page (see “Deleting published posts”). ShowBits does not change or delete any other posts on your page. ShowBits publishes animated quote cards as reels.
How it is stored
The page token is stored per workspace, encrypted with AES-256-GCM, in the database at Supabase (Ireland region, EU) and decrypted only for calls to Facebook, on our servers in Dublin and Frankfurt. It does not expire. Your user token is not stored: while you choose the page, it is kept encrypted in a cookie in your browser for up to ten minutes. Also at Supabase, ShowBits stores the page's name, your Facebook user ID, so that deletion requests from Meta can be matched, and with each scheduled post the video's ID, the link, and the status and failure reason of the delivery.
Who it is shared with
Facebook receives the text with the hashtags. Facebook fetches the video file or the image itself from our media storage through a signed address that is valid for six hours at most. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
Page token and user ID until the connection is removed, the workspace is deleted, Meta sends us a deletion request or the contract ends. The page's name until the workspace is deleted or a deletion request from Meta arrives; it stays stored after disconnecting. A post's ID, link and delivery status until the clip or the workspace is deleted or the contract ends. Audit entries until the organisation is deleted. After the contract ends, the data is deleted according to our Terms (30 days after the contract ends, backups after 90 days at the latest).
How it is deleted
“Disconnect” in the app deletes the page token and the user ID immediately, as does deleting the workspace. You can also remove ShowBits in the Facebook settings under “Business integrations” and request deletion of your data there (see “Deletion through Meta”). Posts already published stay on Facebook until you delete them there or through ShowBits.

Deleting published posts

Permission (scope): instagram_basic, instagram_manage_contents, pages_show_list, pages_read_engagement

What data
When ShowBits publishes a post on Instagram or Facebook, it records the workspace, the channel, the ID of the account or page, the ID of the post and the time of publication, secured with a cryptographic checksum (HMAC). When a post is to be deleted, ShowBits also records who asked for it and when, and when it was deleted. For Instagram, an admin first has to allow deletion through Facebook Login, because apps cannot delete posts through Instagram's own sign-in. ShowBits then receives a Facebook user token, your Facebook user ID for ShowBits and the Facebook pages you selected with the Instagram accounts linked to them. Of these, ShowBits stores only the connected Instagram account (IDs and username), the user token, your Facebook user ID, the expiry date, and who allowed it and when.
Purpose
Deleting posts that ShowBits published itself, at the request of an admin or a duty editor of the workspace. Before deleting, ShowBits checks with Instagram or Facebook that the post belongs to the account or page in the record. ShowBits deletes no other posts, and at most 5 per hour and 20 per day per workspace.
How it is stored
At Supabase (Ireland region, EU). The user token is sealed so that only our background process can decrypt it (X25519 and AES-256-GCM); neither the app nor the database can read it. It is valid for about 60 days; after that, an admin has to renew the permission. Entries in the record of published posts cannot be changed.
Who it is shared with
Instagram and Facebook receive a query about the owner of the post and the request to delete it. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How long it is kept
The permission until it expires or is withdrawn, Instagram is disconnected or another account is connected, Meta sends us a deletion request, or the workspace is deleted. The record of published posts until the workspace is deleted, also after disconnecting and after a deletion request through Meta. After the contract ends, the data is deleted according to our Terms (30 days after the contract ends, backups after 90 days at the latest).
How it is deleted
“Withdraw permission” in the app deletes the permission immediately, as does disconnecting Instagram. You can also remove ShowBits in the Facebook settings under “Business integrations”. The record of published posts is deleted with the workspace.

Deletion through Meta

When you remove ShowBits in the Instagram or Facebook settings, or request deletion of your data there, Meta informs us. ShowBits then deletes the tokens, account and page names and IDs of every connection you made, as well as any permission to delete Instagram posts, and disconnects them. The record of published posts (see “Deleting published posts”) contains no names and stays until the workspace is deleted. A request through Facebook covers your Facebook and Instagram connections, a request through Instagram your Instagram connections. For deletion requests, Meta gives you a confirmation code and a link to a page that shows the status of the deletion. You can also request deletion by email to hello@showbits.ai.

21. Posting to LinkedIn

In the ShowBits app, an administrator of a workspace can connect a LinkedIn profile or a LinkedIn company page so that approved clips and quote cards are published there. The connection runs through LinkedIn's own sign-in page, which names ShowBits as the app (for company pages: ShowBits Pages). ShowBits never receives your LinkedIn password. Company pages can be connected only once LinkedIn has approved ShowBits for them.

Your use of LinkedIn, and anything that happens to a post on LinkedIn after it is published, is governed by LinkedIn's User Agreement and Privacy Policy.

Connecting LinkedIn and posting

Permission (scope): openid, profile, w_member_social (profiles); w_organization_social, r_organization_admin (company pages)

What data
When you connect a profile: your LinkedIn member ID and name. When you connect a company page: the pages on which you are an administrator or content administrator, with their names; ShowBits keeps the page you choose. In both cases the tokens of the connection. After publishing: the IDs (URNs) of the published posts. ShowBits does not read page analytics, followers, messages or members' data.
Purpose
Publishing posts that people approved in ShowBits at the scheduled time: a clip as a video or a quote card as an image, with the text the editors wrote. Unless switched off in the settings, ShowBits adds a first comment with the link to the full episode and a second comment the next morning. Deleting a post that ShowBits published, when an admin or duty editor asks for it. Emailing the admins a week before a connection ends. ShowBits publishes animated quote cards as videos.
How it is stored
The tokens are stored encrypted (AES-256-GCM), together with the IDs (URNs) and name of the connected profile or page and the IDs of the published posts. ShowBits stores no content from LinkedIn. A connection to a profile ends after 60 days; an admin then connects it again.
Who it is shared with
LinkedIn (Microsoft) receives what you publish there: the video or image, the text of the post and the comments. The reminder email goes out through Resend. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How it is deleted
“Disconnect” in the app revokes ShowBits' access at LinkedIn and deletes the token. Posts and comments already published stay on LinkedIn until you delete them, there or through ShowBits.

22. Posting to X

In the ShowBits app, an administrator of a workspace can connect an X account so that approved clips and quote cards are published there. The connection runs through X's own sign-in page, which names ShowBits as the app. Before connecting, ShowBits states what it will do with the account. ShowBits never receives your X password.

X (X Corp.) is not our subprocessor but a recipient that you connect yourself. Your use of X, and anything that happens to a post on X after it is published, is governed by X's Terms of Service and Privacy Policy.

Connecting an X account and posting

Permission (scope): tweet.read, tweet.write, users.read, media.write, offline.access

What data
When you connect: the tokens of the connection and your X account's ID and @-name. After publishing: the IDs of the published posts.
Purpose
Publishing posts that people approved in ShowBits at the scheduled time: a clip as a video or a quote card as an image, with the text the editors wrote. Deleting a post that ShowBits published, on request. ShowBits does not reply, quote, like, repost, follow or send messages, posts no links and no mentions, and does not read timelines, followers or analytics. ShowBits publishes animated quote cards as videos.
How it is stored
The tokens are stored encrypted (AES-256-GCM); the account's ID and @-name and the IDs of published posts are stored with them.
Who it is shared with
X receives what you publish there: the video or image and the text of the post. Beyond that, only to our subprocessors as far as the service requires (Vercel, Supabase, Fly.io, OVHcloud, Deepgram, Anthropic, OpenAI, Typesafe.ai, Resend, Stripe).
How it is deleted
“Disconnect” in the app revokes ShowBits' access at X and deletes the tokens. Posts already published stay on X until you delete them, there or through ShowBits.

23. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You can withdraw any consent at any time with effect for the future (Art. 7(3)).

Right to object: where we process data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation (Art. 21 GDPR).

To exercise your rights, write to hello@showbits.ai. You can also lodge a complaint with a data protection supervisory authority. The authority responsible for us is the Berliner Beauftragte für Datenschutz und Informationsfreiheit (Berlin Commissioner for Data Protection and Freedom of Information).

24. Further information

We do not use automated decision-making, including profiling. You are not obliged to provide data, but we cannot handle a request without the information in the required fields.

We update this privacy policy when our website or the legal situation changes. The version published here applies.