BeemMeUp

Privacy policy

Last updated 9 October 2026

This policy explains what BeemMeUp collects when you use the website, the courses, labs and tools, and the desktop app; why; who handles it for us; and what you can do about it. We don’t sell your data and we don’t use it for advertising.

Who we are

BeemMeUp is the website at beemmeup.io and its desktop app. We decide what is collected and how it is used, as described here.

Pro payments are handled by Link, Stripe’s checkout, which acts as the merchant of record. Payment details you give Link are covered by Stripe’s own privacy policy.

What we collect

Your account: your email address and password, and the name you enter when you sign up. Passwords are stored hashed by our sign-in provider, never in plain text. If you sign in with GitHub, we receive your email address and basic profile details from GitHub instead of a password.

Your profile and settings: the display name, username, bio and profile picture you choose to add, and your app settings.

Your learning: lessons you complete, quiz and challenge results, study sessions and flash-card progress, and the certificates you earn, including the name printed on them.

Your work: the pipelines you save, and the list of files in your media library — file names, sizes and processing status. The files themselves stay on your device (see “Your files” below).

Your activity: a log of things you do in the app, such as starting a module or opening a tool, which feeds your dashboard.

If you subscribe to Pro: your Stripe customer ID and email, and your plan, billing cycle, subscription status and its dates. Card numbers go straight to Link and Stripe; BeemMeUp never sees them.

Where you came from: if you arrive through a link carrying campaign tags (utm_source and the like), we keep the first and the most recent set of tags, the page you landed on and when, and save them with your account when you sign up.

If you connect an AI assistant through our MCP server: the assistant’s registration (with only a one-way hash of the IP address it registered from, never the address itself), the access you grant it, any jobs it runs, and a record of each tool call — which tool, whether it worked and how long it took.

Your files

The video tools process your files on your device: in your browser, or with your own FFmpeg in the desktop app. Your media library is kept in your browser’s storage. None of this uploads your videos to us.

The one file you upload to us is your profile picture. It is stored in Google Cloud Storage and served from a public link, so anyone with that link can see it.

If you open a stream by its URL, our server fetches that stream’s playlist on your behalf so your browser can play it.

Why we use it

To run BeemMeUp for you: to sign you in, keep your progress and saved work in step across devices, show your dashboard, issue your certificates, bill Pro and apply plan limits, and send the emails your account needs — sign-up confirmation and password resets. We only email you about your account.

To keep the service safe, for example by limiting how often requests can be made.

To see which pages are used and where sign-up and checkout lose people, from the analytics described below.

Certificates are meant to be shown: anyone with a certificate’s ID can check it at beemmeup.io/verify, which shows the name on it, the course and the date it was issued.

Who processes it for us

Supabase stores our database and runs sign-in, including the confirmation and password-reset emails.

Vercel hosts the website and provides Web Analytics and Speed Insights. Page addresses sent to analytics are cut to the site and path: anything after “?” or “#” is removed. We also send a few named events, such as viewing the pricing page, a tool or a lesson, and starting checkout. Sign-up and checkout milestones are recorded on our server with your account ID, never your email or name.

Stripe and Link take Pro payments, handle tax and send your receipts.

Google Cloud Storage stores profile pictures.

GitHub signs you in, if you choose to sign in with it.

We don’t use advertising trackers or any other analytics service.

Cookies and browser storage

Sign-in cookies, set by Supabase, keep you signed in.

Two campaign cookies remember the tags of a link you arrived from, as described above. They are set only when such a link is used, and expire after 90 days.

The desktop app’s sign-in screen sets a cookie when you choose to use it offline.

Your browser’s own storage (local storage and IndexedDB) holds your preferences and layout, progress kept on your device, saved Studio recipes, lab state and your media library. It stays in your browser, and clearing this site’s data removes it.

We don’t use advertising cookies.

The desktop app

The desktop app has no analytics or crash reporting of its own. It talks to us for the same things the website does, such as signing in and syncing your progress.

Once automatic updates are switched on, it will check our update feed for a new version when it starts and every 4 hours after that. That check asks only whether a newer version exists; it sends nothing about you or your files.

How long we keep it

We keep your data until you delete it or delete your account, apart from the cases below.

When Pro ends, we hold your cloud files for 30 days so you can download them, as the terms describe.

Campaign cookies expire after 90 days.

Stripe keeps invoices and payment records under its own obligations. When you delete your account, we remove the name, phone number and address from your Stripe customer record but keep the email address, so those records stay tied to the right person.

Your choices

You can edit or remove your profile details at any time from Account.

You can revoke an AI assistant’s access from Account → MCP.

You can delete your account from Account → Security. This cancels any Pro subscription, without a final charge or a refund, and deletes your sign-in, your profile and settings, your billing records with us and where you came from.

Deleting your account doesn’t yet remove everything automatically: your course progress, certificates, saved pipelines, media library list, activity log, MCP records and profile picture file are left behind. Write to hello@beemmeup.io from the email on your account, before or after deleting it, and we will delete those too.

Data kept in your browser is yours to clear from your browser’s settings.

Children

BeemMeUp isn’t aimed at children under 13, and we don’t knowingly collect their data. If you think a child under 13 has an account, write to hello@beemmeup.io and we will delete it.

Changes

If this policy changes, the date at the top of this page changes with it.

Contact

Questions about your data, or a request to delete it: hello@beemmeup.io.

See also: Terms of service · Refund policy · Pricing