Last updated: May 1, 2026

Privacy Policy

This Privacy Policy explains which personal data may be processed when you use OpenMediaTools. The website is designed to process most files locally in your browser whenever possible. Some optional features, such as Google sign-in, feedback submission, analytics, advertising, AI tools, and social media helpers, involve third-party services or server-side infrastructure as described below.

1. Controller and scope

This Privacy Policy applies to the use of the OpenMediaTools website and its related static pages, Cloudflare Processing System endpoints, optional Google account login, optional feedback submission, optional telemetry, advertising components, and optional AI or social-media-related helper features.

The controller for data processing on this website within the meaning of the General Data Protection Regulation (GDPR) is OpenMediaTools. For privacy-related inquiries, you can reach us by email at [email protected].

2. Core product principle: local browser processing

OpenMediaTools is built to process standard video, audio, image, and PDF tasks locally in your browser whenever technically possible. In those local workflows, your uploaded files are not intentionally sent to OpenMediaTools servers.

Files and settings may be stored in your browser through IndexedDB, localStorage, or sessionStorage so that tools, chats, previews, settings, and gallery items can work properly and be reopened later on your device.

  • Local settings such as language, theme, tool preferences, file naming preferences, and UI state.
  • Locally stored chats, gallery entries, temporary imports, and cached processing results.
  • A language preference cookie so the website can reopen in the preferred language.

3. Account login with Google

If you choose to sign in with Google, OpenMediaTools processes the data required to create and maintain your account and session. This currently includes the Google subject identifier, email address, email verification status, display name, given name, family name, locale, profile image URL, session identifiers, session timestamps, and basic abuse-prevention metadata such as user agent data.

Google sign-in is optional. The legal basis is your request to use the login function and account session, as well as our legitimate interest in securing the authentication flow and preventing abuse.

4. Optional telemetry and feedback

The website contains optional product telemetry and feedback handling. These features are used to understand tool usage, model activity, common errors, and direct feedback submitted by users. Telemetry is sent to infrastructure controlled by the operator of the website.

Telemetry is designed to avoid uploading your normal local media files. However, normalized error messages, hashed client identifiers, tool identifiers, model identifiers, and feedback text that you intentionally submit may be transmitted for analytics or support purposes.

5. Advertising and cookies

The website loads Google AdSense. Depending on Google configuration, visitor region, and consent setup, Google may use cookies, local storage, identifiers, contextual data, or other technologies for ad delivery, frequency capping, fraud prevention, aggregated reporting, and possibly personalized advertising.

Where consent is legally required for advertising-related storage or access technologies, the operator of this website must ensure that a compliant consent solution is implemented and configured correctly.

6. AI tools, social media helpers, and external requests

Some optional features do not work purely locally. This includes certain AI image or video tools, social media helper features, remote asset downloads, oEmbed lookups, and other provider-backed functions. When you use those features, your prompts, selected URLs, or uploaded files may be sent to external services that are necessary to generate the requested result.

Examples include Cloudflare, Google, Hugging Face Spaces or Gradio-based endpoints, and social media helper endpoints. Only use those optional features if you want the relevant data to be processed for that purpose.

If you buy credits, the payment is processed through Stripe Checkout and related Stripe payment, billing, fraud-prevention, and webhook infrastructure. OpenMediaTools does not store full card numbers; however, Stripe and the operator may process transaction metadata such as the purchased package, amount, currency, payment status, checkout session identifiers, and the account that receives the credits.

7. Processors and recipients

  • Cloudflare for static hosting, content delivery, DNS, security, analytics, and Processing execution.
  • Google for optional account login and Google AdSense advertising.
  • Third-party AI or media providers that are triggered only when you actively use optional provider-backed features.
  • Stripe for checkout, payment processing, payment confirmation webhooks, and related billing or fraud-prevention functions when you buy credits.

8. Log data, security, and retention

Like most web services, infrastructure providers may process technical request data such as IP address, timestamps, request metadata, status codes, and device or browser information in logs or analytics systems. This data is used for delivery, security, abuse prevention, troubleshooting, and service stability.

Account records and session data are retained only as long as needed for the account function, security, and legal obligations. Local browser data stays on your device until you remove it, clear browser storage, or use the website’s own deletion features.

9. International data transfers

Because the website uses providers such as Cloudflare, Google, and optional AI endpoints, personal data may be processed outside your country, including in countries that may not provide the same level of protection as your home jurisdiction. Where applicable, transfers should rely on appropriate legal safeguards provided by the relevant service provider.

10. Your rights

Depending on the law that applies to you, you may have rights of access, rectification, erasure, restriction, objection, portability, and withdrawal of consent. You may also have the right to complain to a competent supervisory authority.

Because many standard OpenMediaTools workflows are purely local, the operator may not be able to identify or recover files that never left your device. Rights requests related to account data, telemetry, feedback, or server-side logs must be directed to the operator using the contact details provided in this policy.

11. Changes to this Privacy Policy

This Privacy Policy may be updated to reflect legal, technical, or product changes. The latest version will be published on this page with the updated date.