1. Using the service
You must provide accurate account information, keep your credentials secure, and use the service only when you have authority to accept these terms. You are responsible for activity performed with your account and API keys.
Legal
Terms and privacy
The rules for using MediaRuntime and a clear description of how we handle information.
Last updated: October 1, 2026
Terms of Service
These terms govern access to and use of the MediaRuntime website, Workspace, API, and related services.
2. Your media and permissions
You retain ownership of media and other content you submit. You grant MediaRuntime the limited permission needed to receive, process, moderate when requested, store temporarily, and deliver that content. You must have all rights and permissions required for the content and requested processing.
3. Acceptable use
Do not use MediaRuntime to break the law, violate another person’s rights, distribute malware, probe or disrupt systems, evade usage limits, expose credentials, or process content you are not authorized to use. Moderation reports assist review but do not replace your own legal or policy decisions.
4. Billing and payments
Paid processing uses wallet credit and the prices shown by MediaRuntime. Estimates may reserve funds before a job begins; final charges are based on measured execution and selected features. Top-ups and stored payment methods are processed through Stripe. You are responsible for applicable taxes and authorized charges.
5. Jobs, outputs, and availability
Media processing is asynchronous. Completion times are not guaranteed, webhooks may be retried, and outputs may be retained for a limited period. You should verify results and copy required outputs before expiration. We may change, suspend, or discontinue features to operate, secure, or improve the service.
6. Suspension and termination
We may restrict or suspend access for security risks, nonpayment, abusive activity, legal requirements, or material violations of these terms. You may stop using the service at any time. Obligations concerning payment, ownership, disclaimers, and liability survive termination where applicable.
7. Service warranty and liability
The service is provided on an as-available basis. To the extent permitted by law, MediaRuntime disclaims implied warranties and is not responsible for indirect, incidental, special, consequential, or lost-profit damages. Nothing here excludes rights or liability that cannot legally be excluded.
8. Changes and contact
We may update these terms as the service changes. Material updates will be identified by a new revision date. Continued use after an update means the revised terms apply. Questions can be sent through the support page.
Privacy Policy
This policy explains what information MediaRuntime handles, why we use it, and the choices available to you.
1. Information we collect
We collect account and profile details, authentication identifiers, workspace membership, API and product usage, device and diagnostic information, billing status and processor references, communications with support, and media or metadata you submit for processing.
2. How we use information
We use information to authenticate users, operate and secure accounts, process media jobs, calculate usage and billing, deliver outputs and webhooks, answer support requests, prevent abuse, diagnose failures, and improve the service.
3. Service providers
MediaRuntime uses service providers to run the platform, including Google Cloud and Firebase for infrastructure and authentication, and Stripe for payment processing. Providers receive only the information needed to perform their services and handle it under their own terms and privacy obligations.
4. Media processing and moderation
Source media, generated outputs, and technical metadata are processed to perform requested jobs. When moderation is enabled, sampled media may be analyzed to produce a report. MediaRuntime does not use customer media to make unrelated advertising profiles.
5. Retention and security
We retain account, billing, and operational information as needed to provide the service, meet legal and accounting requirements, resolve disputes, and prevent abuse. Uploaded media and generated outputs are temporary and subject to our media retention rules. Eligible uploads become candidates for cleanup after five days; eligible job outputs after at least seven days, subject to delivery expiry. Cleanup includes a grace period and safety checks, so deletion may occur later. Deleted data may remain temporarily recoverable through storage recovery mechanisms. We use technical and organizational safeguards, but no system can guarantee absolute security.
Read the media retention rules6. Your choices
You may update profile information in your account and can ask about access, correction, deletion, or other privacy rights through support. Some records may be retained when required for billing, fraud prevention, security, or legal compliance.
7. International processing and changes
Information may be processed where MediaRuntime and its service providers operate. We may update this policy as the product or legal requirements change, and will show the current revision date on this page.
Media retention
MediaRuntime provides temporary storage for processing and delivery. Keep your own copy of any source files and results you need to retain. These rules describe cleanup eligibility, not a guarantee of download availability or deletion at an exact time.
1. Uploaded source files
Eligible temporary uploads to MediaRuntime, including job-specific captions and artwork, become candidates for cleanup five days after the stored object was created. This applies to supported Workspace and API upload locations. Files in your own external storage are not deleted by this cleanup.
2. Job outputs and older jobs
Eligible outputs, bundles, and job-local reports become candidates for cleanup only after all of these deadlines have passed: seven days after the job finishes, seven days after the stored object was created, and any later delivery expiry recorded for the job. This includes eligible older jobs created before cleanup was introduced. Jobs with missing or unclear timing information are preserved rather than deleted on an assumed date.
3. Grace period and safety checks
Cleanup runs periodically. An eligible object is first staged and must pass another safety check at least 24 hours later before deletion. Active or recent jobs, source references, protection flags, storage holds, missing metadata, processing limits, or errors can delay cleanup further. The five-day and seven-day thresholds are not maximum retention periods or exact deletion deadlines.
4. Sandbox and protected assets
Protected sandbox source media is excluded from this cleanup. Generated sandbox job outputs can expire under the output rules. Published site and blog assets, account watermark assets, character packs, sticker releases, models, and other files outside the temporary-media cleanup locations are not selected by this cleanup.
5. Download access and recovery
Download links and access tokens have their own expiry. Follow the expiry returned for your job and copy required results before access expires; storing an output for cleanup purposes does not extend its download link or guarantee seven days of access after completion. Deletion removes the live stored object. Storage recovery, historical versions, or backup mechanisms may retain copies afterward, so cleanup does not promise immediate permanent erasure.
6. Account and operational records
This media cleanup does not delete account information, billing records, job history, or analytics records. Their retention and any access or deletion requests are handled separately under the Privacy Policy. Contact support with retention or deletion questions.
Questions about these terms or privacy?
Contact support