Legal
MediaUse Privacy Policy
Effective Date: April 9, 2026
At MediaUse, your data belongs to you. This policy is designed around local-first execution, minimal collection, and clear data-controller boundaries under modern privacy frameworks.
1. The Local-First Principle
- MediaUse is designed as a local-first application and is built around data sovereignty.
- No cloud storage by default: we do not host or store the website/media content processed in your local workflows.
- No telemetry by default: Core does not report your command history, visited sites, or media content as part of default operation.
2. Information We Do Not Collect
- We generally do not collect runtime PII from your local CLI/browser tasks.
- We do not collect your authentication credentials (cookies, session tokens, or local login state).
- We do not receive your local browsing task content, media payloads, or local agent prompts/outputs by default.
3. Information Collected in Limited Circumstances
- License verification: licensed Core builds may send minimal metadata to validate license status or entitlement.
- Plugin downloads: commands like mediause add may generate delivery logs such as requested plugin id, timestamp, and IP/network metadata.
- Official website/repository visits may be subject to standard platform analytics under those platform notices.
4. Third-Party Websites and Services
- MediaUse interacts with third-party websites only as directed by you.
- In local-first mode, data flows between third-party websites and your local machine, not through a hosted MediaUse proxy.
- Third-party website policies govern how they handle interactions appearing from your browser/session.
5. Data Security
- Because data remains primarily local, security depends on your device and environment.
- Use disk encryption, protect tokens and API keys, and install plugins only from trusted sources.
6. Children's Privacy
- MediaUse is not intended for children under 13 and does not knowingly collect children's personal information through default local operation.
7. CCPA/CPRA and GDPR Positioning
- Under CCPA/CPRA and GDPR frameworks, MediaUse is generally positioned as local infrastructure software, not a hosted processor of your workflow content.
- In normal local-first usage, MediaUse generally does not sell or share personal data from your local tasks.
- You are the primary controller/operator for data you choose to process through your own workflows and accounts.
8. Changes to This Policy
- We may update this Privacy Policy and publish updates through official channels with a revised effective date.
9. Contact Us
- If you have questions, contact us through your official MediaUse support email or project issue channel.
10. Supplemental Compliance Allocation
- You are responsible for legal basis, third-party terms compliance, and regional privacy obligations tied to your workflows.
- If you operate as the controller/operator, you are responsible for handling data subject rights requests.
Acknowledgment
By installing, executing, or using MediaUse, you acknowledge that you have read and understood this Privacy Policy, and that you are responsible for the legal compliance of the workflows you operate.