MegaphoneBack to Megaphone

Legal · Last updated

Who handles your data.

Megaphone runs on a small number of outside services. Here is every one that touches your data, what it does with it, and what it keeps.

01

What this page is

A sub-processor is a company we pay to handle your data on our behalf so that Megaphone can work. Each one below gets only what it needs for the job named next to it, under its own contract with us.

This list is part of our Terms and Privacy Policy.

02

The list

Google CloudGoogle LLC
PurposeHosting. Runs the web app and the processing jobs, the server that holds the database and job queues, task scheduling and secret storage.
ReceivesEverything the service stores or processes: account and workspace records, schedules, and your media while a job works on it.
LocationUnited States (us-central1)
Cloudflare R2Cloudflare, Inc.
PurposeObject storage for uploaded videos, rendered shorts, thumbnails and stored transcripts.
ReceivesMedia files and transcript files.
LocationPlaced automatically by Cloudflare
Terms
  • Source uploads are kept in a private bucket with public access turned off, and are reached only through short-lived signed links.
AssemblyAIAssemblyAI, Inc.
PurposeSpeech-to-text. Turns the audio of a long-form upload into a timed transcript.
ReceivesThe audio track of each video you submit for a clip run.
LocationUnited States
Terms
  • We are on a paid plan with model-improvement data sharing turned off, so your audio and transcripts are not used to train AssemblyAI's models.
  • Once our copy of a transcript is stored, we ask AssemblyAI to delete theirs, which also deletes the uploaded audio.
  • AssemblyAI keeps the transcript ID and audio duration after deletion, for billing. Its terms also allow it to keep de-identified data.
Google Gemini APIGoogle LLC
PurposeFinds clip candidates in a transcript and drafts caption text and post copy.
ReceivesTranscript text and the text of your drafts. No audio or video is sent.
LocationUnited States
Terms
  • We use Gemini as a paid service, under which Google does not use prompts or responses to improve its products.
  • Google keeps prompts and responses for up to 55 days, only to detect abuse of its usage policies.
03

Where your posts go

When you publish or schedule a short, we send it, with its caption, to the accounts you connected: YouTube, TikTok, Instagram, Facebook or X. Those platforms are not our sub-processors. They receive the post because you told us to send it there, and what happens to it after that is governed by their terms and privacy policies, not ours.

Nothing is posted unless you schedule or publish it.

04

What we run ourselves

Sign-in and the connections to your social accounts, including the access tokens those connections hold, are handled by our own services, not by a third party. They run on the Google Cloud hosting listed above.

05

Changes to this list

We update this page before a new sub-processor starts receiving your data, or when an existing one changes what it receives or how it handles it. The date at the top changes whenever the list does. If you object to a change, email us; you can also stop using the affected feature, or close your workspace.

06

Contact

Questions about any of these services, or about where your data goes: support@videoeditoraifree.com.