This Privacy Policy explains how VlogMe, the web service at vlogme.ai, collects, uses and shares personal data, including in Director, the Studios, Aisma, DUB, News Videos, Lab and the API. VlogMe is aimed at users in the United States and is available worldwide. This Policy applies to everyone who uses it, and section 5 explains where we ask before measuring. We have written it to be understandable.
1. Who we are
VlogMe is operated by BEINTOUCH PTE. LTD. ("we", "us"), a company registered in Singapore under UEN 202144978W, with its registered address at 10 Anson Road #20-05, International Plaza, Singapore 079903. We are responsible for the personal data described here. Privacy questions and requests go to privacy@vlogme.ai.
2. What we collect
- Account data: email address, name and profile picture when provided, and the sign-in method you use.
- Your content: photos, video, scripts, prompts, audio and other files you upload or create, including portraits used for avatars and voice samples used for voice cloning.
- Results and projects: generated images, clips, voice tracks and videos, Director plans and the settings that produced them, all saved in Lab.
- Consent records: your confirmation that you have the rights to a face, voice or video, stored with the job or project.
- Share links: the links you create to share a file from Lab, until you revoke them.
- Share pages and reports: a share link opens a page that shows the file with the VlogMe tool and the model maker that made it, and the price of making one like it. It never shows your prompt, the file's name or who you are, and search engines are asked not to list it. Anyone with the link can report the file on that page. A report keeps the reason, the details and the email address the reporter chooses to give, and a keyed code of the reporter's network that changes every day (never the IP address itself).
- Connected channels: if you connect social accounts for publishing, the connection details and what you schedule or publish.
- News Videos data: the topics and sources your monitors follow, and the stories and scripts you work on.
- Payment records: plan, credit purchases and refunds. Card details are handled by Stripe; we never receive full card numbers. If you cancel a plan, you may tell us why: the reason you pick is kept with our product events, and the reason and any note you add go to Stripe and are kept with your payment record there. We never store the note ourselves.
- Affiliate program: if you apply to be a partner, the details of your application (name, email address, channels, audience and country), the payout and tax details needed to pay you, and your referrals and commissions.
- Referral records: if you signed up through a partner's link or code, which partner referred your account and the payments their commission is calculated from. We do not share your content or account details with the partner.
- Visit and purchase attribution: where your first and latest visits to VlogMe came from (campaign tags, the referring site, whether the visit followed an ad click, the public page you landed on and its language), the country your sign-up came from, as estimated by Cloudflare, the call to action you used, and what a purchase was for (the tool, model and price you were shown). If you answer the optional question after a payment, where you first heard about VlogMe.
- API and agent use: for an API key, the name and version an AI agent or MCP client reports when it connects and its User-Agent, kept with the key and the jobs and file imports it starts.
- Email choices and lifecycle email: which optional emails you turned off, and a record of each optional email we queue or send you (which email, the job, price or page it is about, and when it was sent), and a note that a one-time email was queued (sent or cancelled), so it is never queued twice. Not the text of the email and not your address, which we read from your account when we send.
- Conversion tests and abuse checks: which version of a page or price offer you were shown while we test it, and whether first-result credits were granted to your account. To limit abuse of those credits and of the partner program, we keep one-way coded values (keyed hashes) of an account's email address and network (the first three parts of its IP address) and, for partner checks, of the payment card's fingerprint from Stripe; never the details themselves.
- Studio plan trial: if you start the Studio plan trial, a record of your agreement to its renewal terms (the checkout session, the version of the terms you agreed to, your confirmation and the time) and how the trial went, together with the type of the card that paid for it (credit, debit or prepaid) and the country that issued it, as Stripe reports them; never anything that identifies the card. To limit the new-customer offer to one per customer, we keep one-way coded values (keyed hashes) derived from your account and checkout details; never the details themselves. When you open the trial's checkout, even if you do not pay, we keep coded values derived from your account and checkout details with that checkout for 30 days, so that checkouts opened in parallel cannot repeat the offer.
- Technical data: IP address, device and browser information, and logs of requests and errors, used to run and secure the service.
- Messages: what you send to support.
3. How we use it
We do not sell personal data, and we do not use your private uploads, prompts or results to train AI models.
- Provide VlogMe: sign-in, projects, generation, editing, dubbing, publishing and Lab;
- charge and settle credits and payments, and prevent fraud and abuse;
- run the affiliate program: review applications, record referrals, and calculate and pay commissions;
- secure the service, investigate failures and answer support requests;
- review reports about shared files within 48 hours and take down files that break our rules;
- send messages about sign-in, your account and billing;
- send optional emails: "Your video is ready" when a render takes longer than 2 minutes; one promotional reminder of that price to US accounts a day after a price was shown and nothing was bought; and one review request to US customers after their first download. Every one has an unsubscribe link and can be turned off in Account → Email. We do not use tracking pixels or the email service's open and click tracking; links in these emails name the email, so a visit or purchase that follows is counted like other calls to action;
- test how we show prices and offers, and grant and limit test credits;
- count visits to our public pages, to learn which pages help people and improve them;
- comply with legal obligations.
4. Service providers
We share data only with the providers that run VlogMe for us, and each receives only what its task needs:
- Hosting and infrastructure: Cloudflare (delivery, security and backups) and Supabase (accounts, sign-in, database and private file storage).
- Website analytics: Cloudflare Web Analytics and, on vlogme.ai, Ahrefs Web Analytics (Ahrefs Pte. Ltd., Singapore) count visits to public pages (section 5). Ahrefs also uses aggregated, anonymized statistics to improve its own services, such as its traffic estimates, and may publish studies based on them.
- Email: Resend delivers sign-in, confirmation and account emails and the optional emails described in section 3. It receives your address and the email, not your content or files.
- Affiliate payouts: if a partner-program platform (Tolt) is used to pay partners, it receives the partners' commission amounts and payout details, not the details of the customers they referred.
- Sign-in with Google: if you choose Continue with Google, Google shares your name, email address and profile picture with us.
- Payments: Stripe.
- Advertising measurement: Google Ads receives payment conversion data (the time, amount and currency of a payment, an order identifier and any refund correction) and a Google click identifier for visitors whose advertising measurement is on (section 5), not your email address, phone number, prompts, files or generated content. How Google uses information from sites that use its services.
- AI generation: the provider behind the model or tool you choose, such as Google (Gemini), OpenAI, ElevenLabs, fal, Replicate, Atlas Cloud, BytePlus, MiniMax and Magnific. They receive the inputs and instructions for that job; Atlas Cloud receives the inputs and instructions for Seedance and Wan video generation and editing. Earlier jobs sent directly to BytePlus included a pseudonymous account identifier for abuse detection.
- Publishing: Ayrshare, when you connect social accounts and when you publish to them, and the platforms you choose. Ayrshare also receives a pseudonymous identifier of your account, which labels the publishing profile it creates for you.
- News search: NewsAPI receives the topics and search terms you use in News Videos, including those of your monitors, not your account details.
We may also disclose data to authorities where the law requires it, or to a successor if the business is sold.
5. Cookies and analytics
VlogMe uses browser storage for sign-in, drafts, settings, partner referrals and the advertising measurement described below. On two public pages where we test showing the price before sign-in, your browser keeps which version it was shown (a random choice, in localStorage until you clear it), and after sign-in that version is copied to your account. The price is worked out from the length of the file you choose; the file itself is not uploaded before you sign in. If you open VlogMe through a partner link or type a partner code when you sign in, your browser also keeps that code, for at most 30 days and only until you sign in, so that a new account can be recorded as that partner's referral. If you ask for a sign-in link by email, that link also carries the code and a random first-visit identifier, so that the referral and your first visit still count when you open it on another device. We do not load Google advertising pixels or a Google advertising SDK in your browser. Advertising attribution uses a first-party cookie and server-side conversion delivery, as explained below. We count visits to public pages with Cloudflare Web Analytics and, on vlogme.ai, Ahrefs Web Analytics; neither sets cookies. Cloudflare counts page views without building a profile of you. Ahrefs receives the page's address (its path and any UTM campaign tags, never ad click ids, partner codes or other parameters), the address of the page you came from as your browser reports it, the page title, the links you click, the address a form you submit goes to (not what you typed), and your browser, operating system, device type, language and screen size. According to Ahrefs, it uses your IP address only to find your country and city and, together with your browser details, to count unique visitors with a code that changes every 24 hours, and it does not store the IP address. The Ahrefs script runs only on public pages at vlogme.ai: not on the sign-in page or in the app, and not on the development site. How Ahrefs Web Analytics handles data.
VlogMe also records a small set of first-party product events to understand the main funnel: landing, starting a creation, handoff to the app, sign-in outcome, quote and top-up decisions, job outcome, billing, payment and result download. When measurement is allowed, we also record the public page opened, its language, whether it was missing, and the previous public VlogMe page when known. This helps us see which entries lead to actions. The navigation paths do not include URL parameters, fragments, or anything entered into a form. A random identifier in sessionStorage links these steps for one browser tab and expires after 30 minutes of inactivity; after sign-in, it is linked to the account. We keep campaign tags, referring host, page path, the approximate session country code supplied by Cloudflare and compact technical outcomes, but never the text of prompts, form fields, filenames, uploads, generated media, email address or raw provider errors in analytics events. Product analytics events do not store your IP address or city. These events are stored in our Supabase database, and selected events are sent to PostHog for product and error analysis, not to an advertising network. On public pages Ahrefs additionally receives the event names app_entry, create_started and handoff_completed with the page section, app destination, fixed workflow, model or form choice and technical outcome, not user content.
Where advertising measurement is on for your browser (see Advertising measurement below), a first-party attribution record in localStorage also remembers across tabs, for at most 90 days, where your first and latest visits came from: campaign tags, the referring site, whether the visit followed an ad click (never the click identifier), the public page you landed on and its language, and a random identifier. It is not a cookie and is not sent to any advertising network. Where measurement is off, this information stays in the current tab only; turning measurement off or signing out deletes the record. When you create an account, your first and latest visits and the country your sign-up came from, as estimated by Cloudflare, are copied to it; a purchase records them with the call to action you used and what it was for (tool, model and the price you were shown). After a payment we may ask where you first heard about VlogMe; answering is optional. For API keys we keep the name and version an AI agent or MCP client reports when it connects, and its User-Agent (without any email or web address they contain), with the key, the jobs it starts and the files it imports, to learn which tools people use with VlogMe. None of this includes prompts, files, generated content or your email address.
Where we ask first. If you visit from the European Economic Area, the United Kingdom (with Gibraltar, Jersey, Guernsey and the Isle of Man) or Switzerland (we use the country Cloudflare estimates for your connection), we ask before any measurement. Until you choose OK, nothing for measurement is stored in or read from your browser (only your answer is kept), the Ahrefs script does not load, no product analytics events are sent from your browser, so none tied to your browser reach PostHog (events our server records about your account, such as a download or a payment, are still recorded, without your browser's visit), neither the page that brought you nor an ad click is recorded, a partner link is not kept (a code you type yourself at sign-in always is), and the price test described above shows the standard page. If you choose No thanks, it stays that way. Your answer is kept in your browser and in a cookie for 180 days, and you can change it at any time with the “Ad privacy” button in Advertising measurement below or in Account settings. Cloudflare Web Analytics, which stores nothing in your browser and builds no profile of you, counts page views for every visitor. Everyone else, including visitors from a location we cannot recognise, has everything in this section on by default from the first page, sees a one-time notice about it, and can turn advertising measurement off the same way. The records VlogMe needs to run your account, orders, renders, credits and security are kept wherever you are.
Browser signals. We do not change what we collect in response to Do Not Track or Global Privacy Control signals sent by your browser. To turn advertising measurement off, use the setting described below.
Advertising measurement
Where we ask first (see above: the European Economic Area, the United Kingdom with Gibraltar, Jersey, Guernsey and the Isle of Man, and Switzerland), advertising measurement stays off until you choose OK, and it stays off if you choose No thanks. You can change your answer at any time with the “Ad privacy” button at the start of this section or in Account settings; there it covers analytics too. Everyone else, including visitors from a location we cannot recognise, has advertising measurement on by default, sees a one-time notice about it, and can turn it off the same way. Dismissing the one-time notice is remembered in your browser and in a cookie that holds only that fact, for 400 days.
While advertising measurement is on, we keep a Google ad click identifier (gclid, gbraid or wbraid), the landing-page path and limited campaign tags. A first-party HttpOnly cookie contains only a random attribution reference, not the click identifier. After sign-in, that reference may be linked to your account. Our server sends Google Ads each payment you make within 60 days after we record an ad click from you, with its time, amount, currency, an order identifier and the relevant click identifier, including credit packs, a plan's first payment, its renewals, upgrades and plan changes, and the first payment after a Studio plan trial. For an ad click we recorded before November 6, 2026, only your first payment is sent. The $0.99 fee for a Studio plan trial is never sent, and neither are registrations, free tasks or payments we return ourselves. When a payment we sent is refunded or charged back, we also send Google Ads the correction (its time and the corrected amount) while Google still accepts corrections. We do not send your email address, phone number, prompts, uploaded files or generated content to Google Ads, and click identifiers are kept out of Ahrefs and PostHog.
To see your setting, turn measurement off or turn it on again, use the “Ad privacy” button at the start of this section or in Account settings. Turning it off prevents new attribution and makes pending attribution, later renewals included, ineligible for further advertising delivery; it does not undo a conversion already delivered. VlogMe works the same either way. The same setting decides whether the attribution record described in section 5 is kept across tabs.
The attribution cookie expires 30 days after it is set or renewed. Raw click identifiers in the attribution record expire 60 days after we record the ad click (30 days for a click we recorded before November 6, 2026). If an eligible payment occurs during that time, the click identifier in its delivery queue can be retained for up to 30 more days after payment for retries (at most 90 days after we record the click); it is deleted as soon as Google Ads accepts the payment. The preference cookie lasts 180 days. A local opt-out preference remains until you change or clear it, including when the network is unavailable; it contains no click identifier. Payment and conversion delivery evidence is retained for reconciliation without expired raw click identifiers. The rest of an attribution record (the landing page, campaign tags and your setting, without any click identifier) is kept until you delete your account, or without a set limit for a browser that never signed in.
6. Retention
Raw product analytics sessions and events in our database are kept for no more than 90 days and are deleted earlier when the linked account is deleted; the copies of selected events sent to PostHog are kept under PostHog's retention terms and are not deleted with the account. The underlying payment, credit and security records follow the longer periods described below. The attribution record in your browser lasts at most 90 days. What a checkout was for is deleted after 90 days unless it led to a payment, in which case it is kept until you delete your account. The first and latest visits and the sign-up country copied to your account, your answer about where you heard of VlogMe and the agent details kept with API keys, jobs and imported files stay with your account, and with the record of your first purchase, until you delete the account. Records of optional emails are deleted 90 days after they were sent or dropped; the note that a one-time email (the price reminder or the review request) was queued (sent or cancelled) stays with your account until you delete it; your email choices and the test versions you were shown stay with your account until you delete it. The coded values kept against abuse of first-result credits are deleted 400 days after the grant; those kept with referrals follow the referral and commission records below. The coded values kept to limit the new-customer offer to one per customer stay after you delete your account, so that a new account cannot repeat the offer, and are deleted 400 days after the trial. The coded values kept with a trial checkout you opened are deleted 30 days after it was opened, whether or not it was paid, also if you delete your account sooner. The record of your agreement to the trial's renewal terms is kept for at least three years, or for one year after the subscription ends if that is later, also after the account is deleted.
Your content and results stay in Lab until you delete them or delete your account. When you delete a file, it is removed from our storage, together with the working copies that finished jobs made from it (such as the scene cuts of an Aisma source video or a prepared reference photo), and from our file backups, usually within 30 days. A record that the file existed, without its name, and the job that made it, with its settings and prompt, stay with your account until you delete the account. Deletions and their timing are described on Delete your account or data.
A report about a shared file is reviewed within 48 hours by the VlogMe staff member named for it, or their backup. The reporter's email address, details and network code are deleted 90 days after the decision; the rest of the report (the file, the reason and the decision) is deleted with its owner's account. When a file is taken down, its share link stops working and the file cannot be shared again unless an appeal to abuse@vlogme.ai is granted; the owner keeps the file in Lab.
The providers that run a job keep the data they received for it under their own retention terms, and deleting it in VlogMe does not remove their copies. There are three exceptions, where we also delete the provider's copy:
- Dubbing projects: ElevenLabs makes a dubbing project for each dub, with its speech and the speaker voices cloned for it. We delete it when you delete that dub's DUB project, or its dubbed video or the video it was made from in Lab, and we delete all of them when you delete your DUB data or your account, including for a dubbed video that stays in Lab.
- Cloned voices: when you delete a voice you cloned in Audio Studio, or your account, we delete that voice at ElevenLabs.
- Publishing profile: when you delete your account, we disconnect your channels from the publishing profile that Ayrshare created for you and then delete the profile.
Anything these providers may still hold after that, for example in backups or logs, is governed by their own terms, as is the rest of what they received or generated for your jobs, such as the speech ElevenLabs generated for your voice tracks.
We keep the credit, subscription and payment ledgers and the referral, commission and security records as long as accounting, fraud prevention and the law require, even after the account is deleted.
7. Your choices and requests
You can ask us to access, correct, export or delete your personal data. You can delete your DUB or News Videos data or your whole account yourself in Account → Delete data, and single files in Lab; Delete your account or data explains the other services. You can also email privacy@vlogme.ai from the address of your account. We may ask you to confirm that the account is yours. We will not treat you differently for making a request.
8. Security
Files are private by default: they are kept in private storage scoped to your account, and connections are encrypted. Anyone who has a share link you create can open that file until you revoke the link in Lab. Files you publish go to the platforms you choose. The providers that run a job receive that job's files, either uploaded to them or through a link that expires within 24 hours, and keep them under their own terms (section 6); Ayrshare, which publishes for you, receives a link that works for seven days. No system is perfectly secure, but we work to protect your data.
9. Where data is processed
VlogMe is operated from Singapore, and our providers may store and process data in the United States and in other countries where they operate.
10. Children
VlogMe is for adults aged 18 or older. Do not upload material showing or voicing anyone under 18. If you believe a child has given us personal data, contact us and we will delete it.
11. Aisma
Aisma processes the source video you choose, the reference photos you add and your written request to create the edited version, which is saved to Lab. The video and photos are sent only to the providers that analyze the scene and make the edit.
12. DUB
DUB processes the video you upload, its speech and the target language to create a dubbed version with a voice that matches the speaker. The video and audio are sent to ElevenLabs, which makes the dub in a dubbing project and clones each speaker's voice for it. The result is saved to Lab. You can delete DUB projects (the drafts you save in DUB) and dubbed videos on their own; the videos you uploaded, and a dubbed video you used in another project, stay in Lab until you delete them there. Deleting a DUB project, a dubbed video or the video it was made from also deletes that dub's dubbing project at ElevenLabs, with the cloned voices, and deleting your DUB data or your account deletes all of them (section 6).
13. News Videos
News Videos processes your monitors, the news articles they find, the scripts you edit, the presenter portrait and voice you choose and, if you publish, your connected channels. You can delete News Videos projects and files on their own; a News Videos result you used in another project stays in Lab until you delete it there.
14. Changes
We may update this Policy when the service or the law changes. We will tell you about material changes by email or in the product.
This Policy is written in English. If a translation conflicts with the English version, the English version prevails.
15. Contact
Privacy questions and requests: privacy@vlogme.ai. Everything else: support@vlogme.ai.