Legal
Terms, privacy, and cookies for Meta VisBreeze generators — plain language, no legal-entity claims, nothing hidden.
1. What Meta VisBreeze is
Meta VisBreeze is a set of AI tools that generate metadata (title, description, keywords, and other platform-specific fields) for content you upload: images, video, and audio. As of this writing, that's four tools:
- Free Image — free, runs on a third-party AI service (Puter.com), no account with us required.
- Pro Image, Pro Video, Pro Audio — paid, run on a prepaid-credit system (Credits VB), shared across all three Pro tools and any future VisBreeze products.
2. How the Free tier works
The Free tool sends your file and prompt directly from your browser to Puter.com — a third-party service with its own terms of service and privacy policy (review them separately at puter.com). Our server never sees or processes the file. Sign-in (if you use a Puter account) is entirely on Puter's side too — we don't check or store any of that.
3. How the Pro tier and Credits VB work
Credits VB is a prepaid virtual currency shared across all Pro tools, current and future. Credits are charged at a fixed rate per successful generation, shown to you before you click "Generate" — if a generation fails (AI-service error, network failure, etc.), the charged credits are refunded to your balance automatically and instantly, as part of the same request (this is a separate mechanism from a monetary refund on a purchase — see section 7).
Pro access is granted via an access token, sent to your email after a purchase in the credits shop. The token is the key to your balance — you're responsible for keeping it safe (see also the "Purchases & Refunds" tab).
4. Acceptable and prohibited use
You may use the service for any lawful purpose related to generating metadata for your own content, or content you have the right to process.
You may not:
- use the service for content that's unlawful in your jurisdiction (including, without limitation: content that infringes someone else's copyright without permission, material involving minors in any context, or material that incites hatred or violence);
- attempt to circumvent the service's technical limits (request limits, file limits, the credit system) through automated or other means outside normal interface use;
- share your access token with third parties for the purpose of reselling access.
We reserve the right to suspend a token if we find confirmed abuse, without refunding unused credits.
5. Responsibility for content
You're fully responsible for the files you upload and for how you use the generated metadata (including publishing it on third-party platforms — compliance with any specific stock/video/audio platform's own rules is on you). AI-generated text can be inaccurate — review the result before publishing.
6. File limits and responsibility for your own device
Numbers like the maximum file count per batch or maximum file size (see each generator's page) are a technical ceiling we allow on our side, not a guarantee that your device can handle a batch that size. How many files you can actually upload and process at once depends on your computer and browser's capabilities, which we don't control and can't check in advance.
We recommend starting with smaller batches and increasing them gradually, only once you've confirmed the previous batch processed without issues on your device.
We're not liable for data loss or incomplete results caused by your device running out of resources (memory, browser performance) while processing a batch — including a frozen or crashed browser tab. Credits already charged for files processed before such a failure aren't refunded, in credits or money.
7. Refunds
There are two independent mechanisms — this is just a summary so the two don't get confused:
- Automatic credit refund to your balance on a failed generation (see section 3) — happens instantly, no support request needed, covers only technical failures of the generation itself.
- A monetary refund on the purchase itself — a separate, narrower policy that applies only in specific cases. Full text: "Purchases & Refunds" tab.
"I didn't like the result" is not grounds for either kind of refund — credits are charged for AI processing actually performed, not for a specific outcome.
8. Disclaimer of warranties and limitation of liability
The service is provided "as is," without warranties of uninterrupted operation, error-free performance, or fitness for a particular purpose. We make reasonable efforts to keep it running, but don't guarantee availability at any given moment.
We're not liable for indirect damages, lost profits, or other losses arising from using (or being unable to use) the service, except where such a limitation is expressly prohibited by applicable law.
9. Changes to these terms
We may update these terms as the service evolves. The current version is always available on this page.
10. Support and questions
Questions about these terms, technical issues, or how the service works — reach us through the in-app feedback form (available to Pro users and to Free users signed in via Puter).
1. What data we actually see
This depends on which tool you use:
- Free Image — we never see your file at all. It goes straight from your browser to Puter.com (a third-party AI service) without our server being involved. Puter has its own privacy policy — review it at puter.com.
- Pro Image — the file (as base64) is sent to our server and immediately relayed to the AI provider (Google Gemini API) through our proxy key — the server holds it only in memory for the duration of the request, never writing it to disk or a database.
- Pro Video / Pro Audio — the file is uploaded to our server as a normal HTTP upload, so it briefly exists as a temporary file on the server's disk (the standard way file uploads work) — this is needed to check duration/audio presence before sending it to the Google Gemini Files API. The file isn't intentionally saved and never ends up in a database; the temporary file is deleted automatically once the request finishes. On Google's side the file has to be stored for the length of the job (that's how their Files API works for video and audio) — we delete it there ourselves the moment the generation finishes, successfully or not. If you close the tab in between — after the upload but before the generation runs — that file is picked up by an automatic cleanup within a few hours. Either way it does not sit there until Google's own 48-hour expiry.
Generated text (title/description/keywords, etc.) is always returned to your browser. Whether it's also kept on our server — see section 3.
2. What we store when you pay (Pro)
When you buy credits, our server receives from our payment processor: your email, the payment amount and currency, the transaction ID, and creates an access token for you. We never receive or store your card number, name, or address — that stays with the payment processor.
We also store: your credit balance, the IP address of the token's most recent use, the date of last use, and a history of credit charge/refund transactions (each entry includes the IP address of that specific transaction).
3. What's stored based on your choices (Pro)
- Generation history (title/description/keywords/filename/platform/model for each generation) — off by default, you turn it on yourself in settings. You can delete individual entries, a batch, or your entire history at any time.
- Custom platforms, CSV presets, synced settings (keyword rules, output language, audio author fields, etc.) — created and edited by you; stored so they're available from any device with your token.
- Your current model/platform choice and title/description/keywords limits stay in your browser (localStorage) only — never sent to our server.
4. Retention
Right now there's no automatic deletion or expiry of data — it's kept until you (for records you can delete yourself) or we, at your request, remove it. Deleting your account entirely (email, token, full history) is done by contacting support — there's no self-service "delete my account" button in the interface yet.
5. Cookies and similar technology
For ordinary visitors and generator users, we don't set any cookies at all. Everything stored in your browser is localStorage: your own access token and your own interface settings. None of it is ever sent to our server automatically — only when a specific action you take (like requesting a generation) explicitly uses it. Full details — see the "Cookie Policy" tab.
(Cookies are only actually used inside our internal admin panel, which isn't meant for site visitors.)
6. Who we share data with
- Puter.com — for the Free tool only, directly from your browser; we're not part of that exchange.
- Google Gemini API — for Pro generation (your file/prompt, for the duration of processing).
- Google Analytics 4 — standard site-visit analytics.
- Cloudflare Turnstile — bot-detection (CAPTCHA) on the "resend my access token" form; Cloudflare sees your IP address at the moment you complete the check.
- Payhip — the payment processor, sees your purchase data directly (we don't pass them anything beyond what you enter on their own payment page).
We don't sell or otherwise share your data with anyone outside this list.
7. The feedback form
If you contact us through the built-in feedback form, we receive your message text, any optional screenshots (up to 5 files), and some technical device information (browser, language, screen size, timezone) — without your IP address. Files are validated by their actual content (not by filename or claimed type) and stored under a randomized name.
8. Your rights
You can, at any time: view and delete your own generation history, custom platforms, and CSV presets right in the interface; request full account deletion (email, token, all data) through the feedback form — we'll act on that request.
9. Changes to this policy
We may update this policy as the service evolves. The current version is always on this page.
1. The short answer
If you're an ordinary visitor or a user of any of our AI generators — we don't set you a single cookie. Everything we use is your browser's localStorage instead (a similar technology, with one important difference: it isn't sent to a server on its own, only when our own code explicitly reads and sends it).
2. What's stored in localStorage, and why
| What's stored | Why |
|---|---|
| Your access token (Pro) | So you don't have to re-enter it on every visit |
| Interface settings for each generator (keyword rules, limits, output language, etc.) | So you don't have to reconfigure them on every visit |
| Saved profiles (e.g. podcast "Show Profiles") | Same thing — purely for your own convenience |
None of this is used to track you across other sites, isn't shared with ad networks, and isn't read by anyone except your own browser and — when you trigger an action yourself (like starting a generation) — our server, which needs your token at that moment to charge the right balance.
You can clear this data any time through your browser's settings (this will usually also clear your saved access token — for that case, the token was emailed to you at purchase, so you can always re-enter it).
3. Google Analytics 4
The site uses Google Analytics 4 — standard visit analytics (which pages get viewed, where visitors came from, and so on). GA4 may set its own identifiers in your browser as part of its own technology — it's a third-party Google service with its own policy. We don't link that data to your identity (email/token) — it's separate, unconnected information.
4. Cloudflare Turnstile
The "resend my access token" form uses a free bot-detection check (CAPTCHA) from Cloudflare — it sees your IP address at the moment you complete the check, only on that page.
5. Everything else
The credits shop and the AI provider for the Free tier (Puter.com) are separate sites with their own cookie practices — this policy doesn't cover them.
1. What you're buying
By making a purchase in this store, you're buying prepaid credits (Credits VB) — a single virtual currency that works across every VisBreeze product (metadata generators for image, video, and audio, and any other VisBreeze services launched in the future).
2. Digital product, instant delivery
Credits are an intangible digital product. Access is granted almost instantly: within a few minutes of payment, an email with your access token and an activation link is sent to the address you provided.
3. Waiver of the 14-day right of withdrawal
EU consumer protection law grants a 14-day right to withdraw from a purchase, but this right does not apply to digital content once the buyer has given explicit consent to immediate access. By agreeing to these terms at checkout, you confirm that you knowingly request immediate access and thereby lose the right to withdraw on this basis, where that right would otherwise apply by law.
4. Refunds for "I didn't like the result"
Credits are charged for AI processing actually performed. The quality and style of the output depend on the AI model selected and the settings you provided — this is not a technical defect and is not grounds for a refund. We guarantee that the service works, not the outcome of any specific generation.
5. When a refund is possible
We will issue a refund only in these cases:
- payment went through but credits were not added, and the issue could not be resolved by manually crediting your account (always contact us first — in most cases we simply add the missing credits, no refund needed);
- you were charged twice for the same purchase.
Credits never expire. If the service is temporarily unavailable — for maintenance, an update, or any other reason — that is not grounds for a refund: once the service is back up, you can use your already-purchased credits at any time, whether that's tomorrow or next month. We apologize for any inconvenience caused by downtime, but no refund is issued in this case.
6. Access token security
Your access token is the key to your balance. You are responsible for keeping it safe. We do not refund or compensate credits spent by a third party who gained access to your token.
7. Support
If you run into a genuine technical problem with payment or crediting — contact us, and we'll sort it out.