Privacy Policy
Motion Studios is committed to absolute data privacy and transparency. This policy outlines how Automation Studio handles your information, integrates with Google and YouTube APIs, and keeps your production data localized on your PC.
1. Introduction
Motion Studios ("we", "our", or "us") operates the Automation Studio desktop software for Microsoft Windows and related web services at motionstudios.cc. We believe creator independence begins with privacy. Unlike cloud video editors that require you to upload your raw footage and media assets to external servers, Automation Studio is engineered primarily as a local desktop workstation.
By downloading, installing, accessing, or using Automation Studio, you acknowledge that you have read and understood this Privacy Policy.
2. Data We Collect
We practice aggressive data minimization. We only collect the minimal information necessary to authenticate your software license, enable direct YouTube uploads, and process recurring subscription billing:
Your email address, hashed password, and license key managed securely via Supabase Auth. Used strictly to verify your software seat.
OAuth 2.0 access and refresh tokens acquired when you authorize video uploads via the YouTube Data API v3. Stored locally on your machine.
Processed exclusively through Flutterwave. We do not store, process, or have access to your credit or debit card numbers.
3. Google & YouTube API Services
"By using Automation Studio, you agree to be bound by the YouTube Terms of Service. We use YouTube API Services to upload videos. You can revoke our access to your YouTube data at any time via the Google Security Settings page."
How We Access and Use YouTube Data:
- Scoped Permissions: Automation Studio requests only the
youtube.uploadscope to upload your completed videos, assign video titles, descriptions, tags, and set synthetic media disclosure flags. - No Data Harvesting: We do not read, aggregate, analyze, sell, or share your private channel statistics, viewer watch times, or subscriber data.
- Local Token Storage & Encryption: Your YouTube OAuth tokens are encrypted locally on your Windows machine using the Windows Data Protection API (DPAPI). We do not store your active tokens on our servers.
- Google Limited Use Compliance: Automation Studio's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
4. AI Processing & Google Gemini API
Automation Studio utilizes Google Gemini Pro API models to assist creators with scriptwriting, scene breakdown, and metadata optimization.
We interact with Google Gemini exclusively through commercial API endpoints. Under the Google Cloud Enterprise terms, prompts, scripts, and media processed through the Gemini API are not used to train or fine-tune Google AI models. Your intellectual property and creative story concepts remain strictly yours.
5. Local Storage & Processing Architecture
Automation Studio runs FFmpeg natively on your Windows device. Unlike web-based video creators that transmit your clips to cloud rendering farms:
- Your raw b-roll, voiceover audio, and final MP4 files remain on your local hard drive (
%APPDATA%/AutomationStudio/projects). - Video rendering is accelerated locally by your NVIDIA, AMD, or Intel GPU.
- Motion Studios maintains zero copies of your rendered video files on our infrastructure.
6. Data Deletion & User Rights (NDPA / GDPR)
Under the Nigeria Data Protection Act (NDPA) and General Data Protection Regulation (GDPR), you possess full control over your personal data:
7. Security Safeguards
We implement industry-standard cryptographic practices. All communications between the desktop client, Flutterwave, Supabase, and Google APIs are secured with TLS 1.3 encryption. Your local machine security remains protected as we sign our Windows executables to prevent binary tampering.
8. Contact & Inquiries
If you have questions regarding this Privacy Policy, your rights under data protection laws, or wish to request data deletion, please contact our privacy compliance team: