Privacy
Last updated 17 August 2026
Mocko keeps the least it can: enough to know it is you, what you have made, and whether you have paid. There is no tracking of any kind, and nothing here is sold or shared for advertising.
What is stored, and why
| What | Why it exists |
|---|---|
| Email address | Identifies your account and is how we would contact you about it. |
| Name and profile picture | Supplied by Google when you sign in, shown back to you in the app. The picture is a link to Google, not a copy. |
| Google account id | The stable identifier that keeps your account yours if you change your email address. |
| Sign-in sessions | A random token per browser or terminal. Browser sessions last a week; a terminal token lasts a year, because a command line cannot easily ask you to sign in again. |
| Your projects | The layout, copy, colours and device choices of any deck you save to your account. |
| Screenshots you upload | The images placed into your artboards, and the finished exports you download. |
| Monthly screenshot count | Enforces the free plan’s allowance. A number per month, not a log of what you made. |
| Plan and Stripe identifiers | Whether you are on Free or Pro, and the customer and subscription ids that let us ask Stripe about your billing. |
That is the whole list. There is no record of which pages you visited, how long you stayed, or what you clicked.
Your card details never reach us
Payment happens on a checkout page hosted by Stripe. Mocko never receives, handles or stores a card number. What we keep is the identifier Stripe gives us for your customer record, so we can tell whether your subscription is active.
No tracking, and two cookies
Mocko runs no analytics, no advertising pixels, no session recording and no third-party scripts. Two cookies exist, and both are strictly functional:
- Your sign-in cookie keeps you signed in for a week. It cannot be read by JavaScript.
- A short-lived sign-in cookie carries the handoff to Google and back. It lasts ten minutes and is deleted as soon as you land.
The editor also keeps your work-in-progress deck, your preferences and your theme in your own browser’s local storage. That never leaves your machine and is not visible to us.
Who else is involved
Three companies, each doing one job:
- Google — sign-in only. Google learns that you signed in to Mocko. Mocko asks only for your email address, name and profile picture, and never for access to your Google account’s contents.
- Stripe — payments and subscription management.
- Cloudflare — hosting, the database and file storage. Your account records and uploaded images live on Cloudflare’s network.
Nobody else receives your data. It is not sold, rented, or shared for advertising, and there is no arrangement under which it could be.
How long it is kept
Account records, projects and uploads stay while your account exists. Sign-in sessions expire on their own — a week for a browser, a year for a terminal — and the short-lived codes used to link a terminal are deleted within minutes.
Deleting a project deletes its images and finished exports along with it. That is immediate and cannot be undone.
Getting your data, or getting rid of it
Delete account at the bottom of your account page erases everything immediately: the account, every saved project, every uploaded image and every finished export. It is not a request queued for someone to action, and it cannot be undone. Drafts held in your own browser are left alone, because those were never ours to delete.
If you have a live subscription, cancel it first — the page will say so. Deleting the account while Stripe is still billing would leave a charge with nothing behind it.
For a copy of what is held, email hello@mocko.pro.
Changes
If what Mocko stores changes, this page changes with it and the date at the top moves. For anything that materially affects data already collected, account holders will be emailed rather than left to notice.
Questions about any of this: hello@mocko.pro. See also the terms of service.