Privacy Policy

OMTME (https://omtme.com/) ("we", "us", or "our") is an AI creative production suite. This Privacy Policy explains how we collect, use, disclose, store, and protect information when you use our planning, media creation, transcription, editing, workflow, publishing, scheduling, and analytics features.

Account and profile data

We collect your email address, name, avatar, authentication identifiers, language, theme, plan, notification preferences, and other settings you provide.

Creative projects and User Content

We process prompts, Storylines, characters, episodes, scripts, storyboards, workflow configurations, templates, captions, timeline edits, thumbnails, publishing copy, and other project data you create.

Uploads and generated media

Depending on the tool you use, we may process uploaded or generated images, product or character references, video, audio, music, voice assets, PDFs, watermarks, subtitle files, and render outputs, together with technical metadata needed to operate the project.

AI and workflow activity

We collect selected models and providers, generation settings, prompts and responses, workflow nodes, execution status, errors, timestamps, usage counts, transcription runs, and other records needed to run jobs, troubleshoot failures, and enforce plan limits.

Connected platform data

When you connect a supported social account, we receive approved OAuth tokens or access tokens, platform and account identifiers, basic profile or channel data, content metadata, and available performance metrics. The exact data depends on the platform and permissions you approve.

Billing and support data

Stripe processes payment-card details. We store billing identifiers, plan and cycle, subscription status, invoices or payment events, and failure or grace-period information. We also process messages and attachments you send to support.

Device and service data

We may collect IP address, browser and device information, request logs, security events, cookie or session identifiers, and feature interaction data needed to secure and operate the Service.

• Provide and synchronize creative projects across the Product
• Run AI generation, transcription, rendering, workflow, and export jobs you request
• Store project state, recover jobs, diagnose errors, and provide support
• Connect supported social accounts, retrieve approved analytics, and publish or schedule content on your instructions
• Manage authentication, preferences, notifications, plans, subscriptions, invoices, and usage limits
• Protect accounts, prevent abuse, rate-limit requests, and investigate security incidents
• Understand aggregate Product usage and improve reliability, usability, and feature design
• Comply with legal obligations and enforce our Terms

We use technical and organizational safeguards designed to protect data, including:

• AES-256-GCM encryption for stored API credentials and sensitive connection tokens
• Database Row Level Security and authenticated authorization checks
• TLS for data transmitted between your browser, OMTME, and supported providers
• Secure session management, server-side input validation, and request rate limiting
• Payment webhook verification and protected background-job endpoints
• Operational logging, access controls, and separation of server-only secrets

No system is completely secure. Keep your password and connected-provider credentials confidential and contact us if you suspect unauthorized access.

We disclose information to providers only for a business purpose described in this Policy or when you direct an integration:

• Supabase — authentication, PostgreSQL database, and object storage
• Stripe — checkout, payment processing, invoices, and subscription management
• AI and media providers — selected text, image, video, audio, transcription, or rendering services, including providers you connect through API Profiles
• Vercel — hosting, server functions, and scheduled operations
• Upstash — Redis-based rate limiting and service protection
• Social platforms — supported publishing and analytics destinations you connect, which may include YouTube, TikTok, Instagram, and Facebook

AI prompts, media, or source material are sent only to the provider required for the operation you request. Third parties process data under their own terms and privacy policies. We do not sell personal data or use it for third-party targeted advertising.

OMTME's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

API keys, service-account credentials, OAuth refresh tokens, and supported platform access tokens are encrypted before storage. They are decrypted on the server only when needed to perform an authorized request. You can remove API Profiles or disconnect social accounts from the Product; you may also need to revoke access directly with the provider.

We use essential cookies and similar browser storage for authentication, security, language, theme, consent state, and core preferences. We do not use third-party advertising cookies. If optional analytics or similar technology is introduced, we will provide any notice or choice required by law.

We retain account and project data while your account is active and as needed to provide the Service. Retention depends on the type of data and why we hold it:

• Project records, Storylines, workflows, captions, templates, and saved media remain until you remove them, close the account, or an applicable Product lifecycle deletes them
• Temporary workflow uploads may be cleaned after the related workflow is deleted or after a period of inactivity; current cleanup jobs generally target eligible inactive files after five days
• Execution, security, and diagnostic records may be retained for reliability, abuse prevention, dispute resolution, and plan enforcement
• Billing, invoice, and payment-event records may be retained as required for tax, accounting, fraud prevention, and legal compliance
• Backups and third-party provider copies may persist for a limited period under their retention schedules

When you request account deletion, we will delete or de-identify data that we are not required to retain, subject to technical backup cycles, legal obligations, and unresolved security or payment matters.

Depending on your jurisdiction, you may have the right to:

• Access the personal data we hold about you
• Request correction of inaccurate data
• Request deletion of your data
• Object to or restrict the processing of your data
• Request a portable copy of your data
• Withdraw consent for optional data processing

To exercise any of these rights, please contact us at the email below.

The Service is not intended for users under 16 years of age. We do not knowingly collect personal data from children. If we become aware that we have collected data from a child, we will take steps to delete it promptly.

AI models process prompts and source material to produce text, images, video, audio, captions, recommendations, or analysis. OMTME also uses automation to run scheduled workflows, render projects, send enabled notifications, reconcile subscriptions, enforce usage limits, and manage failed-payment grace periods.

These systems support creative and operational tasks; they are not intended to make legal or similarly significant decisions about you. You can review AI output, disable schedules, disconnect integrations, change notification preferences, and manage billing from the Product.

OMTME and its service providers may process information in countries other than your own. Where required, we use appropriate safeguards for international transfers. Data protection laws in those locations may differ from the laws where you live.

We may update this Privacy Policy from time to time. We will notify you of significant changes by posting a notice on the Service or sending an email. Your continued use of the Service after changes constitutes acceptance of the updated policy.

If you have any questions about this Privacy Policy or our data practices, please contact us at [email protected].