Skip to content

Black Friday: −50 % on your first plan payment and +100 % credits on packs through December 7 See the offer →

This Privacy Policy explains how JAN TEAM LLC (“we”) collects, uses and protects personal data when you use WowReveal at https://wowreveal.com, including our API and MCP server. We are the controller of this data.

We collect only what we need to run the Service, we don't sell your personal data, and we don't use your content to train our own AI models.

1. Data we collect

  • Account data: email address, display name, password (stored only as a bcrypt hash), language preference and, if you sign in with Google, your basic Google profile (name, email, avatar).
  • Your content: videos, links, images and audio you upload or submit, scripts, prompts, brand assets (logos, music) and the outputs we generate.
  • Usage and technical data: IP address, browser and device information, request logs, job history and credit transactions, and the days you use the Service.
  • How you found us, recorded when you sign up: the website you came from (its domain only), campaign labels in the link (utm_source, utm_medium, utm_campaign), the first page you opened, and the country of your sign-up IP address — looked up on our own server, without sending your IP address anywhere.
  • Payment data: payments are processed by our payment providers. We receive the payment status, amount, product, currency and a customer reference — never your full card number.
  • Communications: messages you send to support.
  • Requests for done-for-you Reels (no account needed): the name, e-mail address, Telegram or WhatsApp contact, page links and other details you type in the request form, the account you were signed in to, if any, and a one-way fingerprint of your network address (not the address itself) to limit repeated requests. We use them only to answer your request and agree the work, and we send you one confirmation letter. We keep a request while we discuss and do the work; ask us at support@wowreveal.com, and we delete it within 30 days.
  • Connected social accounts (auto-posting): if you connect a Facebook Page, an Instagram professional account or a Threads profile, we receive from Meta, with your permission, the account's name, username and profile picture, the identifiers Meta uses for it (and, for Instagram, the Facebook Page it is linked to), and access keys that let us publish the videos you schedule. We store the access keys encrypted. For each post you schedule we keep the video it belongs to, the title and text, the time you chose, and the result — the link to the published post or the reason Meta gave for refusing it. We do not read your feed, messages, followers or statistics.
  • Connected YouTube channels (auto-posting): if you connect a YouTube channel, we receive from Google, with your permission and through YouTube API Services, the channel's name, handle, profile picture address and ID, the permissions you granted, and access keys (an OAuth refresh token and short-lived access tokens) that let us upload the videos you schedule to that channel. We store the access keys encrypted. For each upload we keep the video it belongs to, the title, description and tags you approved, the privacy setting and the “made for kids” answer you chose, the time you chose, and the result — the link to the published Short or the reason YouTube gave for refusing it. We do not receive your Google account's email address or profile, and we do not read your channel's other videos, comments, subscribers, playlists or statistics.

2. How we use your data

  • to provide the Service — processing your videos, generating scripts, voiceovers, captions, images and videos;
  • to manage your account, credits, subscriptions and payments;
  • to prevent fraud and abuse (for example, limiting signup bonuses per IP address) and to keep the Service secure;
  • to send service emails such as verification, password resets, receipts and important notices;
  • to publish the finished videos you scheduled to the social accounts you connected, at the time you chose, to show you how each publication went, and to email you when one fails or when an account needs to be connected again (you can switch these emails off) — we publish only what you placed or approved yourself;
  • to provide support and improve the Service using aggregated statistics — for example, which channels bring new users and how the product is used;
  • to comply with legal obligations.

Where the GDPR or UK GDPR applies, our legal bases are: performance of our contract with you, our legitimate interests (security, fraud prevention, improving the Service), your consent where we ask for it, and compliance with legal obligations.

3. Service providers (processors)

We share data only with providers that help us run the Service, and only what they need for the task:

  • Hosting and infrastructure: cloud servers, databases, storage and backups.
  • Payments: Whop, Polar, Stripe, Lemon Squeezy and NOWPayments (crypto), depending on the method you choose.
  • AI processing: OpenRouter (language and vision models), Google (Gemini models), ElevenLabs (voice generation) and fal.ai (image and video generation). Content is sent to them only to perform the job you request.
  • Email delivery: our transactional email provider.
  • Sign-in: Google, if you choose Google sign-in.
  • Meta Platforms (Facebook, Instagram, Threads), when you use auto-posting: through Meta's official APIs we send Meta the video and the text you scheduled, so it can publish them to your account. For Threads, and for Instagram when needed, Meta downloads the video from a private link that is valid for about two hours. Meta's own privacy policy applies to what is published on its platforms.
  • Google (YouTube), when you use auto-posting to YouTube: through YouTube API Services we send Google the video and the title, description, tags and privacy setting you scheduled, so it can publish them on your channel, and we ask it for your channel's name, handle, picture and ID and for how the processing of your uploads is going. Google's Privacy Policy applies to what you publish on YouTube.
  • Analytics: Google Analytics, on the public pages and inside the signed-in app (never for administrators), and, depending on where you are, only if you accept the analytics notice; our server also reports events to it (see “Cookies and local storage”). Google acts as our processor for this.

These providers process data under their own terms and privacy policies and, where required, data-processing agreements with us. Some are located outside your country, including in the United States; where required, transfers rely on safeguards such as Standard Contractual Clauses.

4. YouTube API Services and Google data

WowReveal's auto-posting to YouTube uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms); Google's Privacy Policy (https://policies.google.com/privacy) describes how Google handles your data.

When you connect a channel, Google asks you to approve two permissions, and we use each of them only for what is listed here:

  • youtube.upload: lets us upload the videos you schedule to your channel, at the time you chose, with the title, description, tags and settings you approved. We add nothing to your title or description.
  • youtube.readonly: lets us read your channel's name, handle, profile picture address and ID — so that you can see which channel will publish — and check how YouTube is processing the videos we upload for you. We do not read your other videos, comments, subscribers, playlists or statistics.

We use the information we receive from Google only to provide this auto-posting feature: to upload what you schedule, to show you which channel it goes to and how each upload went, and to email you when an upload fails or the channel needs to be connected again (you can switch these emails off in Settings → Preferences). We do not sell it, and we do not use it for advertising or to build advertising audiences. People at JAN TEAM LLC do not read it, except where you ask us to (for example, when you write to support about it), where it is needed for security (for example, to investigate abuse or a bug), where the law requires it, or where it is aggregated and used for internal operations. It is passed on to no one but Google itself — the video and the text you schedule go to YouTube to be published on your channel — and to the service providers listed above, which process it only to run the Service.

WowReveal's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.

Keeping it up to date. For as long as a channel is connected, its name, handle and picture are read from Google again before they are 30 days old. If we cannot read them again — for example because Google does not answer, or because you removed WowReveal in your Google account — then, 30 days after the last time we read them, we let go of everything Google told us about the channel in the same way as when you disconnect it (see below). A connected channel that can be read again later gets its name, handle, picture and ID back; the links to its Shorts do not come back.

Disconnecting and deleting. You can disconnect a channel at any time in Settings → Social accounts. We then, at once: delete its access keys and ask Google to revoke them; cancel what was scheduled for it; replace the channel's name, handle and picture with the label “YouTube channel”; replace the channel's ID with a one-way fingerprint — a code that cannot be turned back into the ID, and that we use only to recognise the same channel if you connect it again, so that WowReveal never uploads the same video to the same channel twice; and delete the links to your published Shorts, the video IDs behind them and YouTube's own words about an upload it refused. What stays is the list of your past uploads without any of that — which video it was, the title, text and settings you chose, the time, and whether it was published or failed — shown under the label “YouTube channel” and kept with the video until you delete the video or your WowReveal account. We can also do all of this for you on request: write to support@wowreveal.com, and we do it as soon as we can and within 7 days of your request. Deleting your WowReveal account deletes everything, the fingerprint and the list of uploads included. Deleting data with us does not delete anything on YouTube: videos already published there stay until you delete them on YouTube.

Revoking access in your Google account. In addition to disconnecting a channel in WowReveal, you can revoke WowReveal's access to your Google account at any time on Google's security settings page, https://myaccount.google.com/permissions. Google does not tell us when you do. The keys we hold stop working, and we find out the next time we use them — when something is published to that channel, or when its name is read again (see above) — and the channel is then shown as needing to be connected again; you can disconnect it as described above. In any case, what Google told us about the channel is let go of 30 days after we last read it, if it could not be refreshed (see above) — that is, within 30 days of your revoking access.

Questions or complaints about how we handle YouTube data: support@wowreveal.com.

5. How long we keep data

  • Finished videos and generated files: 7 to 90 days depending on your plan, then deleted automatically.
  • Temporary processing files (downloads, intermediate renders): deleted after processing, and in any case within the same retention window.
  • Account data: for as long as your account is open. When you delete your account, we delete or anonymise your personal data within 30 days, except where we must keep it.
  • Access keys of connected social accounts: while the account is connected. They are deleted at once when you disconnect the account in Settings → Social accounts, when you remove WowReveal in your Facebook, Instagram or Threads settings, or when Meta sends us a data deletion request for you. The list of your scheduled and past publications is kept with the videos they belong to and is deleted with them or with your WowReveal account. Posts already published on Facebook, Instagram or Threads stay there until you delete them on those platforms.
  • Access keys and data of a connected YouTube channel: the access keys are kept while the channel is connected. They are deleted at once when you disconnect the channel in Settings → Social accounts or delete your WowReveal account, and they stop working when you remove WowReveal at https://myaccount.google.com/permissions. The channel's name, handle, picture and ID are kept while it is connected, and its name, handle and picture are read from Google again before they are 30 days old. When you disconnect the channel — or when 30 days have passed since we last read it and it could not be refreshed — the name, handle and picture are replaced with the label “YouTube channel”, the ID with a one-way fingerprint, and the links to your published Shorts are deleted. The list of your scheduled and past uploads, without those links, stays with the videos it belongs to until you delete them or your WowReveal account. We delete the data we hold about a YouTube channel within 7 days of your request. Videos already published on YouTube stay there until you delete them on YouTube.
  • Billing records: for as long as tax and accounting laws require.
  • Security logs: for a limited period needed to protect the Service.

6. Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, to object to or restrict certain processing, and to withdraw consent. You can update your profile and delete your account in Settings at any time.

You can delete the data about your connected social accounts at any time: the “Data deletion” page (https://wowreveal.com/legal/data-deletion) explains the ways to do it, including a deletion request from your Facebook settings and how to remove our access to a YouTube channel in your Google Account.

To exercise your rights, contact us at support@wowreveal.com. We'll reply within 30 days — and we delete the data we hold about a YouTube channel within 7 days of your request. You also have the right to complain to your local data-protection authority.

7. Cookies and local storage

We use one strictly necessary session cookie to keep you signed in. Your theme and language preferences, and your answer to the cookie notice, are saved in your browser's local storage.

We use Google Analytics, a service of Google, to see how the site is found and used. It runs on the public pages of this site (the ones anyone can open without an account, such as the home page, pricing, templates, tools, documentation, the blog and these legal pages) and inside the signed-in app (Create, Library, Billing, Settings and the like), and it never runs on the sign-in and sign-up pages or in the admin area, and never for administrator accounts. Its address reports are reduced first: for a public page we drop everything in the web address that is not a campaign label or a setting those pages read, and for a page inside the app we report only the kind of page (for example “/app/projects/:id”), never the full address, a link you pasted or the identifier of your project. It sets its own cookies (_ga and similar) and collects which pages and features are used, how the visit was found (the referring site and any campaign labels in the link), scrolling, clicks and similar interactions, simple events about what you do with the product (for example that you opened a lesson, started or finished a video, used a tool, or began a checkout, each with a few fixed labels such as the tool or the plan, never text you typed), approximate location, device and browser. No advertising features are used: we deny ad storage and ad personalization to Google, show no ads and do not build advertising audiences.

Whether we ask first depends on where you are. If you visit from the European Economic Area, the United Kingdom or Switzerland, or if we cannot tell where you are, Analytics starts only after you press Accept in the analytics notice, and not before. Elsewhere it starts with your first page, and no notice is shown. In every case you can turn it off, and on again, at any time with “Analytics settings” at the bottom of the public pages, in the account menu inside the app and under Settings → Preferences; turning it off stops the measurement and removes its cookies from this browser.

If you are signed in, Analytics also receives a user ID made from your account number with a secret key (a keyed hash that cannot be turned back into your account number, e-mail or name) and a few properties of the account: plan, interface language, content language and niche you chose in the introduction, whether you signed up with Google or e-mail, a broad category of where you came from (for example search, social, direct) and a range for how old the account is. This lets the same person be recognised across devices and visits. They are never sent for administrator accounts, nor when analytics is off for you.

Some events are reported by our server, because they happen when no page is open or are too important to depend on a browser: that an account was created (and whether with Google or e-mail) or its e-mail address confirmed; that a payment went through or was refunded (our payment number, amount, currency and the plan or credit pack); and the result of your work — that a video or a Clipper analysis finished or failed (with the tool, a fixed error label, a rough length and the language), and your first finished video. These are sent only when analytics is on for you, and then they carry the Analytics identifiers of your browser, which we keep for up to 30 days to match later events to your visit, and the user ID and properties above; if analytics is off or you have not accepted it, nothing is sent from our server at all. No e-mail, name or anything you typed is sent with them.

We also count page views on our own server, without any cookie and without keeping anything in your browser: a public page that opens tells our server so, and we add one to a daily total — which page it was, the kind of device, the site or campaign the visit came from and the country. Only these totals are kept — no IP address and no record of a single visit is stored. Requests made by robots (search engines and other crawlers) are counted the same way, by the robot's name.

We don't use advertising cookies. Payment forms and pages of our payment providers may set their own cookies under their policies.

8. Security

We protect data with encryption in transit (HTTPS), hashed passwords and API keys, access controls and ownership checks on every file. No system is perfectly secure, so please use a strong, unique password and keep your API keys private.

9. Children

The Service is not intended for anyone under 18, and we don't knowingly collect personal data from children. If you think a child has given us personal data, contact us and we'll delete it.

10. Changes to this policy

We may update this policy. For material changes we'll notify you by email or in the app before they take effect. The date at the top shows the latest version.

11. Contact

JAN TEAM LLC · https://wowreveal.com · support@wowreveal.com

Questions about this document?

Contact JAN TEAM LLC at support@wowreveal.com

This document is available in English and Russian. If the versions differ, the English version prevails.