Privacy Policy
Effective date: November 17, 2026 · Last updated: November 17, 2026
OpenLenz is operated solely by Daft Planet Media LLC, a Florida limited liability company and the data controller responsible for the information described below. This policy covers our websites, the OpenLenz application, and the publishing surfaces described under “When your content becomes public”.
What we collect
Account. From Google sign-in: your name, email address, and profile photo.
OpenLenz. The same Google sign-in gives you a reader account on OpenLenz, and signing in there asks for nothing from YouTube. What we keep for it: the publications you follow, the comments and chat posts you make, the days you were active on the network (which is what a daily goal, a streak, and your place on the network map are made of), and, if you turn notifications on, the browser or device push subscription used to deliver them. Turning notifications off deletes that subscription.
YouTube. From the OAuth flow you complete on the Channels page: per-channel metadata (channel ID, title, handle), an encrypted refresh token, and, where you grant the analytics scope, view, watch-time, and subscriber statistics for your own channel. The section “Google user data & Limited Use” below lists exactly what we read, store and share.
Billing. From Stripe: customer and subscription identifiers, plan, and payment status. We never see or store your card number. On the $1 SEO plan the card goes on file with Stripe before a channel is connected, and we use the subscription status to decide what your account may run.
Uploaded media. The video files you upload or share from your Google Drive, photos you add for thumbnails, and, for script packs, clips you upload with the rights record you give us (rights type, licence or permission, credit line) and any proof of permission you attach (pasted text, an image, or a PDF).
Transcripts and pipeline output. Transcripts of your own videos and uploads (made on our own server, by Gemini, or from your own captions through the YouTube API), transcripts of a podcast's public audio when you give us its feed for a script pack, and everything the SI produces: SEO copy, thumbnails, clips, captions, scripts, blog drafts, social posts, story videos, and audit logs. Edits and render settings you create in the editors are stored too, as are notes you paste into a script pack and the permission requests you draft there.
Analytics. Your own channel's YouTube statistics where you grant that scope, and how you use our site (see cookies below).
Copyright records. If we receive a copyright notice about something on your account, we keep the notice, what we did about it, and any counter-notice.
Your own API keys. If you connect keys for Gemini, ElevenLabs, fal.ai, or Sonauto, we store them encrypted at rest and use them only to perform work you request on your own provider accounts.
Usage and marketing attribution. Standard server logs (IP address, user agent, pages requested), and, when you first arrive, the campaign tag, advertising click identifier, or referring website that brought you, which we keep against your account so we can tell which marketing works. See the cookie table below.
Cookies and similar technologies
We set the following. “Essential” cookies are required for sign-in and for the service to function; the rest are used for measurement and advertising.
| Cookie | Type | Purpose | Kept for |
|---|---|---|---|
| next-auth.session-token | Essential | Keeps you signed in | Session / 30 days |
| mka_signup_host | Essential | Remembers which brand you signed in from so sign-in completes on the right site | 10 minutes |
| mka_ref | Essential | Credits a referral when you arrive from someone's share link | 30 minutes |
| mka_trial_cohort, mka_search_cohort | Essential | Records which signup offer you arrived through | 30 minutes |
| mka_offer | Essential | Records that you arrived through the $1 SEO plan's page, so your account is set up on that plan rather than the free tier | 7 days |
| mk_hero_intent | Essential | Holds the link to your own video that you pasted on the homepage, or that you chose Upload video, while you sign in and subscribe, so it is back in the box afterwards | 30 minutes |
| mka_hs_try | Essential | Stops the sign-in handoff between our sites from retrying in a loop | 90 seconds |
| mka_channel | Essential | Remembers which of your channels the dashboard is showing | 1 year |
| mka_acting | Essential | Remembers which channel a staff login is working on | 1 year |
| mka_impersonator | Essential | Set only while our support staff view your account to help you, and ends the support session | Up to 2 hours |
| mka_blog_profile | Essential | Shows your name and picture on a publication with its own web address, without a sign-in token | 30 days |
| olz_uid | Essential | A random id so a like or a report on OpenLenz counts once | 1 year |
| olz_seen | Essential | Remembers which OpenLenz articles you have already been shown, so the feed shows new ones | 2 weeks |
| olz_theme | Essential | Remembers light or dark mode on OpenLenz | 1 year |
| mka_attr, mka_attr_relay | Analytics | Records which campaign, link, or referring site brought you to us, so we can tell which marketing works | 90 days |
| _ga, _ga_* | Analytics | Google Analytics: aggregate usage measurement | Up to 2 years |
| mka_fbc, mka_fbc_relay, _fbp | Advertising | Meta advertising click and browser identifiers, used to measure whether an ad led to a signup | 90 days |
| mka_lp_v | Analytics | Keeps you on one version of a landing page during an A/B test | 30 days |
| olz_vid | Analytics | A random id that lets us count how many people visited rather than how many pages were opened. It says nothing about who you are and is never shared. Only set if you accepted the cookie banner | 180 days |
| olz_consent | Essential | Remembers whether you accepted or declined the counting cookie, so we stop asking | 1 year |
You can clear or block cookies in your browser. Blocking essential cookies will prevent sign-in from working.
Advertising and measurement
We advertise our own service and we measure whether those adverts work. To do that we send Meta a one-way SHA-256 hash of your email address, together with your IP address, browser user agent, and Meta's own click and browser identifiers, when you create an account, and again when you start a paid subscription (with the amount paid, never your card details). Meta uses this to match your signup or purchase to an advert you may have clicked. We also run Google Analytics and TinyVisits for aggregate website measurement.
We do not sell your personal information, and we do not share the content of your videos, your transcripts, your generated assets, or any data we receive from Google APIs with advertising networks. The sharing described in this section is limited to the signup and website-measurement signals named above.
To opt out, email daniel@blokstreams.com and we will exclude your account from advertising measurement.
Google user data & Limited Use
OpenLenz's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Signing in with Google grants us only your basic profile (name, email, photo). YouTube access is a separate, later step that only a creator connecting a channel takes; an OpenLenz reader account never requests it.
What we access. Through the YouTube Data API, with the access you grant, we read your own channels (ID, title, handle, thumbnail), the list of your uploads, your own videos' details (title, description, tags, duration, privacy status, view counts) and, for your own videos, their caption tracks. With the YouTube Analytics scope we read your own channel's views, watch time and subscriber statistics. We write only to your own channel, at your direction: uploading the videos, Shorts and long cuts you publish with us, and updating your own videos' titles, descriptions, tags, chapters, thumbnails and captions. For a script pack about a video you choose that is not yours, we read only its public details (title, description, tags, chapter times, view count, channel name) with one request; never its captions or transcript, and we never download it.
What we store. Your channel details, the details of your own videos we work on, your own captions turned into a transcript, your analytics (up to 90 days), and, for a script pack about another channel's video, its title, channel name and view count. The rules below say how long.
What we share. Only with the providers that do the work for you: Google Cloud stores it, and Google Gemini reads your own captions, titles and descriptions to write your SEO, thumbnails, clips and scripts. We do not use Google user data for advertising, we do not sell it, and we do not transfer it to anyone else except as required by law. Humans do not read your Google user data except where necessary for security, to comply with the law, or with your explicit consent.
OpenLenz uses the YouTube API Services. By using OpenLenz you agree to be bound by the YouTube Terms of Service. Information collected by Google in connection with your use of these services is handled under the Google Privacy Policy.
You can revoke OpenLenz's access to your YouTube account at any time through the Google security settings page, or by disconnecting the channel from the Channels page in your dashboard, which revokes our access at Google straight away.
How long we keep YouTube data. Information we get from the YouTube API Services (such as video titles, channel names and thumbnails, view counts, the public details of a script pack's source video, and analytics) is refreshed at least every 30 days, and anything we could not refresh in that time is deleted. We keep at most 90 days of your channel analytics, and we re-fetch that whole period from YouTube at least every 30 days. When you disconnect a channel, or revoke our access, we delete the YouTube data we stored for that channel, including its analytics, statistics and transcripts, within 7 days. The videos, thumbnails, clips and SEO text we made for you stay in your account until you delete them.
Instagram messages and Meta Platform Data
OpenLenz can answer direct messages sent to an Instagram professional account that its owner has connected to our automatic replies. Today that is only our own business's accounts. When you send such an account a message, Meta passes it to us through the Instagram API, and we receive and store: your Instagram-scoped user ID, your username and display name, the text and time of your message, and the reply we sent. From the connected account itself we hold its Instagram account ID, its username, and an access token, encrypted at rest.
We use this data only to choose and send the automatic reply, to avoid answering the same person twice, and to show the conversation to the account owner's staff so they can follow up personally. We do not use it for advertising, we do not sell it, and we do not share it with anyone except our hosting provider (Google Cloud) and where the law requires. We handle data received from Meta in line with the Meta Platform Terms.
We keep these messages while the Instagram account stays connected. Disconnecting it deletes its access token, reply templates and message log immediately, and the account owner can also remove our access at any time in Instagram under Settings → Apps and websites. If you messaged one of these accounts and want your data deleted, see our data deletion instructions.
When your content becomes public
Some features publish on your behalf. Each is off unless you turn it on, or is an explicit action you take:
- Updating your YouTube video's title, description, tags, chapters, thumbnail, and captions.
- Publishing clips to YouTube, or to TikTok, Instagram, X, Facebook, or Pinterest through our distribution provider (Post for Me).
- An automatically written blog derived from your videos, published on a public website that may carry third-party advertising.
- A public podcast RSS feed, and episodes sent to Buzzsprout.
- A continuous public video stream assembled from your videos.
- Posts, replies, images and videos you share in OpenLenz Chat, shown publicly with the name and picture of the publication or account you post as.
Subscribing to a publication on OpenLenz. Following a publication shares nothing with its owner beyond a count. If you choose “share my email” when subscribing (or on your Subscriptions page), your email address and name are made available to that publication's owner for their own mailing list, and, if they connected one, sent to their email-list tool. You can withdraw this at any time from your Subscriptions page, which stops future sharing; the owner is responsible for removing you from lists they already exported.
Anything published this way is public and may be copied, cached, or indexed by others. Turning a feature off stops future publishing; it does not retract what was already published elsewhere.
Who we share it with
We use the following providers (subprocessors) to deliver the features you use. Where you connect your own key for one of them, that provider receives your content under your own account and terms. We do not use any service to download videos from YouTube.
- Google (Sign-In, YouTube Data API, YouTube Analytics API), authentication, reading your own channel and videos, publishing to your own channel at your direction, and showing your own channel's analytics.
- Google Drive API, reading the video files you share from your Google Drive with a link, only when you give us that link or folder.
- Google Cloud Platform, hosting, database, file storage, and render servers.
- Google Gemini and Vertex AI, transcription, SEO copy, thumbnail generation, clip selection, editing decisions, script packs, and blog drafting.
- Stripe, payments, subscriptions, and partner payouts.
- OpenAI, word-timed transcription of clips and text generation in parts of the editing and assistant features.
- ElevenLabs, narration and music generation.
- fal.ai, SI video generation.
- Sonauto, SI music generation.
- Hetzner, servers in Germany that hold a copy of the videos in your 24/7 live stream and push it to your restream targets, only while a stream is running.
- Post for Me, publishing clips to TikTok, Instagram, X, Facebook, or Pinterest when you choose to.
- Buzzsprout, podcast episode publishing, if you enable it.
- Google Workspace (Gmail) and Resend, sending account, video and support emails.
- Calendly, booking a call with us, if you choose to book one.
- Pexels, stock footage search for b-roll (receives search words only, never your files or personal data).
- Meta (Facebook/Instagram), advertising measurement (see the advertising section).
- Google Analytics, website usage measurement.
- TinyVisits, lightweight website visit measurement.
We may also disclose information where required by law, to enforce our terms, or as part of a merger or acquisition.
Agency and partner access
If your account was created for you by an agency or partner reselling this service, staff at that organisation can see your account, connected channels, jobs, and generated assets in order to manage them on your behalf. They are bound by their agreement with us.
People we contact
Separately from our customers, we maintain a business-contact list used to send introductory emails about our services, for example publicly listed business email addresses and professional-licence records. We hold the name, business contact details, and public professional information of those contacts, and we rely on our legitimate interest in direct business-to-business marketing.
Every such email includes an unsubscribe link. To be removed and have your details deleted, use that link or email daniel@blokstreams.com. We do not sell this list.
If you are a customer, we email you about your account and your videos: sign-in, billing, a video finishing, a job that needs your attention. We also send occasional offers about our own plans, for example when a video finishes or when we run a promotion. Every offer email carries an unsubscribe link that stops offers only; account and video notifications continue, because you need them to use the service. We do not share your address with anyone for their marketing.
Storage, security, and how long we keep things
Account, channel, and job records are held in Postgres on Google Cloud. Generated assets, thumbnails, clips, transcripts, rendered videos, are held in a private Google Cloud Storage bucket and served through short-lived signed links. OAuth refresh tokens and any API keys you supply are encrypted at rest with AES-256-GCM before being written to the database.
We keep your account data and generated assets for as long as your account is open. We do not currently apply an automatic expiry to stored assets, so assume anything generated for you remains stored until you delete it or close your account. You can delete individual jobs and clips from the dashboard at any time.
- Account (name, email, photo, settings): while your account is open, to run the service and contact you about it.
- Billing (Stripe identifiers, plan, payment status): while your account is open, then as long as tax and accounting law requires.
- Uploaded media (your videos, Drive files, photos, script pack clips and permission proof): until you delete them or close your account, to make and publish your work. The rights record for a third-party clip is kept with the project while it exists, and with any copyright notice about it.
- Studio recordings (podcasts recorded in the browser): the pieces each device uploads are deleted once a take is put together. A take you keep for later, or leave unreviewed, is deleted after 30 days unless you send it to editing; a discarded take is deleted at once, and a practice run records nothing. Takes sent to editing follow your edit. Messages in the studio chat are never recorded or streamed; they are kept while the room is in use (private ones only for the two people in them) and deleted 30 days after the room was last used.
- Transcripts and generated work: until you delete them or close your account, so you can reuse and republish them. A transcript made from your own YouTube captions is YouTube data and follows the 30-day and 7-day rules above.
- Analytics: your own YouTube analytics, up to 90 days, refreshed at least every 30 days; site usage as listed in the cookie table.
- Copyright records: for as long as needed to apply the repeat-infringer policy and to answer legal claims.
When you close your account, account data and pipeline outputs are removed within 30 days. Billing records are retained for as long as tax and accounting law requires. Disconnecting a YouTube channel revokes our access straight away, and the YouTube data we stored for it is deleted within 7 days (see “Google user data & Limited Use” above).
International transfers
We operate from the United States and our providers are largely US-based, so if you are outside the United States your information will be transferred there. Where we transfer personal data out of the UK or European Economic Area we rely on the European Commission's Standard Contractual Clauses, or an adequacy decision where one applies.
Your rights
Wherever you live, you can ask us to give you a copy of your data, correct it, delete it, or stop using it for marketing. If you are in the UK or European Economic Area you also have the right to object to or restrict processing, the right to data portability, and the right to complain to your local supervisory authority. If you are in California you have the right to know what we collect, to delete it, to correct it, and not to be discriminated against for exercising those rights, and, as stated above, we do not sell personal information.
Our legal bases are: performing our contract with you (running the service you signed up for), your consent (optional publishing features and any advertising cookies where consent is required), legitimate interests (security, debugging, measuring our own marketing, business-to-business outreach), and legal obligation (tax and accounting records).
To exercise any of these, email daniel@blokstreams.com. We respond within 30 days.
Children
The service is not intended for anyone under 16, and we do not knowingly collect their information. If you believe a child has given us personal data, contact us and we will delete it.
Changes
We update this policy as the service changes. The date at the top reflects the current version, and we will tell you by email before a change that materially reduces your rights takes effect.
Contact
Privacy questions, data requests, and deletion requests: daniel@blokstreams.com.
Daft Planet Media LLC, Florida, United States.