Your privacy,
taken seriously.
Uploads stay in your browser
Screenshots used in the editor are processed client-side and are not stored on our servers after your session ends.
We collect the minimum needed
Account, billing, and operational data are collected only to run the service and support customers.
No data sales
We do not sell personal data or share it with advertisers for tracking or targeting.
Payments stay with Stripe
Mockly never sees or stores your full card details. Stripe handles payment processing and subscription state.
You control your data
You can request access, correction, export, or deletion of your personal data at any time.
Analytics are lightweight
We use product analytics to understand usage trends, not to build cross-site behavior profiles.
01
Overview
Mockly ("we", "us", "our") operates mockly.video and the Mockly video mockup editor (the "Service"). This Privacy Policy explains what data we collect, why we collect it, how we use it, and what rights you have over your information.
By using Mockly, you agree to the practices described here. If you do not agree with this policy, do not use the Service.
Regional privacy rights
If you are located in the EEA, UK, or California, you may have additional rights under GDPR, UK GDPR, or CCPA-style laws. We aim to apply privacy-first handling for all users, not just users in those regions.
02
Information We Collect
Information you provide directly
- Account information. When you create an account through Clerk, we collect your email address and, if available, your name or OAuth profile details.
- Payment information. Paid subscriptions are processed by Stripe. We receive subscription status, billing metadata, and a Stripe customer identifier, but not your full card number.
- Uploaded images. Images you use inside the editor are handled in-browser for rendering and export. We do not persist those files on Mockly servers as part of normal product use.
- Support communications. If you email us, we keep the correspondence needed to resolve your question or issue.
Information collected automatically
- Usage data. We collect product activity such as page visits, export counts, and feature usage to understand how the service performs.
- Device information.Browser type, operating system, viewport size, and language preferences help us debug issues and optimize the interface.
- IP address. Request-level IP data may be used for rate limiting, security review, and high-level geographic analytics. We do not keep it longer than operationally necessary.
- Cookies and local storage.We use a small number of browser storage mechanisms to keep you signed in and preserve product preferences.
03
How We Use Your Data
We use collected information to:
- Provide, maintain, and improve the Mockly service.
- Create and manage accounts and authenticate users.
- Process billing and subscription events through Stripe.
- Send transactional messages such as login, receipts, or account updates.
- Detect abuse, enforce our terms, and protect the service.
- Respond to support messages and product questions.
- Analyze aggregate product behavior to prioritize improvements.
- Send product updates only when you have opted in, with unsubscribe controls.
What we do not do
We do not sell personal data, allow ad networks to profile users, or use your information for cross-site advertising.
04
Third-Party Services
We use a small number of service providers that help us run Mockly.
- Clerk. Authentication and user account management. Learn more at clerk.com/privacy.
- Stripe. Payment processing, billing, and subscription lifecycle events. Learn more at stripe.com/privacy.
- Vercel. Hosting and edge delivery infrastructure. Learn more at vercel.com/legal/privacy-policy.
- Analytics. We may use privacy-conscious analytics tooling to understand aggregate product usage without building ad-targeting profiles.
We do not use ad pixels or third-party advertising trackers.
06
Data Storage & Security
Account and subscription records are stored through our vendors using industry-standard safeguards. Payment data is handled by Stripe in line with PCI-compliant practices.
Uploaded images are not stored as a normal part of the editor workflow. Rendering happens on the client side using browser APIs, and image data is discarded when your session ends.
We retain account data while your account remains active, then delete or anonymize it within a reasonable period after account closure unless we need to retain specific records for legal, tax, or fraud-prevention reasons.
Security measures
We use HTTPS in transit, access controls for internal tooling, and secure vendor infrastructure to reduce the risk of unauthorized access.
07
Your Rights
Depending on your location, you may have rights to access, correct, export, restrict, or delete personal data we hold about you.
- Request a copy of your personal data.
- Correct inaccurate or incomplete account details.
- Delete your account and associated personal information.
- Receive exported data in a portable format where applicable.
- Opt out of non-essential marketing messages.
- Object to or restrict certain processing in specific jurisdictions.
How to exercise your rights
Email privacy@mockly.video and we will respond within a reasonable timeframe, typically within 30 days.
08
Children's Privacy
Mockly is not directed to children under 13, or under 16 where a higher age threshold applies. We do not knowingly collect personal data from children. If you believe a child has provided personal data, contact us and we will investigate and delete the information where appropriate.
09
Changes to This Policy
We may update this Privacy Policy as the product, our vendors, or legal obligations change. When updates are material, we will revise the date at the top of this page and may provide additional notice through the product or by email.
10
Contact Us
For questions, requests, or concerns about privacy, contact the Mockly privacy team.
Mockly Privacy Team
Email privacy@mockly.video
Website mockly.video
Response time within 5 business days