Pixel Studio Product Addendum
Effective Date: 01 May 2026
Version: 1.0.0
This Pixel Studio Product Addendum (“Addendum”) applies to your use of Pixel Studio, a desktop software product provided by PXL READY (FZE).
This Addendum supplements the PXL READY Terms of Service and Privacy Policy. If there is a conflict between this Addendum and the general Terms of Service, this Addendum applies only to your use of Pixel Studio.
1. Pixel Studio
Pixel Studio is a desktop application designed to help creators manage content production workflows, including ideation, scripting, voiceover, media generation, editing, thumbnails, metadata, scheduling, and publishing workflows.
Pixel Studio may include local software, AI agents, automation tools, integrations, connectors, installation helpers, project files, logs, and workflow data.
2. Local-First Storage
Pixel Studio is designed as a local-first desktop application.
By default, Pixel Studio stores project files, drafts, scripts, logs, renders, thumbnails, captions, workflow state, settings, provider configuration, and related data on your device or in a folder you choose.
PXL READY does not access, upload, sync, or review your local Pixel Studio project data by default.
Pixel Studio may send or receive data only when you choose to connect third-party services, use online providers, enable an online feature, request support, approve sharing, or perform an action that requires an internet connection.
3. API Keys and Connected Accounts
Pixel Studio may allow you to connect your own accounts, API keys, tokens, credentials, or subscriptions for third-party services.
These may include AI providers, voice providers, image and video generation providers, stock media providers, music providers, YouTube, cloud storage, or other platforms.
You are responsible for:
- keeping your own API keys and account credentials secure;
- reviewing provider pricing and usage limits;
- managing your provider subscriptions and billing;
- complying with each provider’s terms, rules, and policies;
- removing or rotating keys if you believe they were exposed.
Pixel Studio may help store credentials locally, but you remain responsible for your connected accounts.
4. Third-Party Services
Pixel Studio may integrate with third-party services that are not owned or controlled by PXL READY.
Third-party services may change, fail, limit access, charge fees, suspend accounts, modify APIs, or return incorrect results.
PXL READY is not responsible for third-party service availability, pricing, billing, moderation decisions, account restrictions, API changes, or platform enforcement actions.
Your use of third-party services is governed by their own terms and privacy policies.
5. AI Agents and Generated Output
Pixel Studio may use AI agents or automation to help generate ideas, scripts, voiceovers, visuals, edits, captions, thumbnails, metadata, schedules, and other content.
AI-generated output may be inaccurate, incomplete, offensive, infringing, unsafe, misleading, or unsuitable for publishing.
You are responsible for reviewing and approving all outputs before use, upload, sale, publication, distribution, or monetization.
Pixel Studio does not guarantee that AI-generated content is correct, original, non-infringing, platform-safe, advertiser-safe, or legally compliant.
6. Publishing Responsibility
If you use Pixel Studio to prepare, schedule, or upload content to platforms such as YouTube, TikTok, Instagram, or other services, you are responsible for the final content and its publication.
You are responsible for:
- factual claims;
- copyright and licensing;
- music, voice, image, video, and stock asset rights;
- trademarks, logos, and branding;
- platform policies;
- advertising and monetization rules;
- age ratings, disclosures, and content restrictions;
- permissions for likeness, voice, and personal data.
Pixel Studio may assist with workflow, but you remain the publisher of your content.
7. Approvals and Risky Actions
Pixel Studio may include approval steps before certain actions, such as publishing, spending provider credits, installing tools, deleting files, changing schedules, connecting accounts, or modifying important project data.
Approval systems are safety features, but they may not catch every issue.
You are responsible for reviewing actions before approving them.
8. Budgets and Usage Caps
Pixel Studio may include budget caps, usage limits, warnings, or provider-level cost controls.
These features are intended to reduce accidental usage or overspending, but they are not a guarantee that charges will not occur.
Third-party providers may calculate usage, billing, limits, and refunds according to their own systems and policies.
You are responsible for monitoring your third-party account usage and billing.
9. Local Tools, Installs, and Dependencies
Pixel Studio may help install, configure, launch, or connect local tools, command-line utilities, AI models, media processors, dependencies, plugins, or development tools.
You are responsible for approving installations and ensuring your device meets the requirements.
Local tools may fail, conflict with existing software, require updates, use storage, use CPU/GPU resources, or affect system performance.
PXL READY is not responsible for damage caused by unsupported devices, incompatible systems, third-party installers, modified environments, or user-approved local commands.
10. Files, Backups, and Data Loss
Because Pixel Studio is local-first, your project data may live primarily on your own device.
You are responsible for keeping backups of important projects, exports, keys, settings, and production files.
PXL READY is not responsible for data loss caused by device failure, deletion, corruption, operating system issues, storage problems, third-party sync tools, user actions, or unsupported modifications.
11. Diagnostics, Logs, and Support
Pixel Studio may create local logs, error reports, workflow history, or diagnostic files to help the app function and help you troubleshoot issues.
These logs are stored locally by default unless you choose to share them with PXL READY, request support, enable a support upload feature, or approve a sharing action.
Before sharing logs or files with support, you should review them and remove any sensitive information you do not want to share.
12. No Hidden Cloud Sync
Pixel Studio is designed not to secretly upload your local project files, API keys, logs, drafts, renders, or generated media to PXL READY by default.
If future versions include optional cloud sync, remote processing, account backup, team collaboration, telemetry, or hosted agent features, those features should be disclosed in the app and may require additional consent, settings, or terms.
13. Early Access and Experimental Features
Pixel Studio may include beta, experimental, preview, or early access features.
These features may be incomplete, unstable, inaccurate, unavailable, or changed without notice.
You should not rely on beta or experimental features for critical production workflows without reviewing the output and keeping backups.
14. Acceptable Use
You may not use Pixel Studio to create, automate, upload, or distribute content that violates applicable law, third-party rights, platform rules, or the PXL READY Terms of Service.
You may not use Pixel Studio to abuse third-party services, bypass provider limits, scrape services without permission, distribute malware, misrepresent identity, infringe rights, or automate prohibited platform behavior.
15. License and Restrictions
Pixel Studio is licensed, not sold.
You may use Pixel Studio only in accordance with the PXL READY Terms of Service, this Addendum, and any license terms shown at purchase or inside the app.
You may not resell, redistribute, sublicense, reverse engineer, bypass technical protections, or use Pixel Studio in a way that violates the Terms of Service unless permitted by applicable law.
16. Changes to Pixel Studio
PXL READY may update, modify, suspend, remove, or discontinue Pixel Studio features, integrations, agents, models, tools, or workflows.
Some features may depend on third-party providers and may stop working if those providers change their services, pricing, APIs, policies, or availability.
17. Acceptance Receipt
Pixel Studio may save a local record showing that you accepted the applicable Terms of Service, Privacy Policy, and this Addendum.
This receipt may include the accepted policy versions, date and time, app version, device identifier hash, user account email if provided, and a receipt identifier.
If Pixel Studio is later connected to an online PXL READY account, or license system, PXL READY may store acceptance metadata such as accepted version, acceptance date, and receipt ID.
18. Contact
Questions about Pixel Studio or this Addendum may be sent to:
PXL READY (FZE)
support@pxlready.com
Trade No: 3173
B16, Block B, SRTIP
Sharjah, United Arab Emirates