Privacy Policy

Last updated 16 November 2026

This Privacy Policy explains how Ultraform Ltd ("Ultraform", "we", "us", "our") collects, uses, stores, and shares personal data when you use Ultramock (the "Service") at ultramock.io and any related websites, applications, or services.

Ultraform Ltd is a company registered in England and Wales (company number 17075381) with its registered office at 71-75 Shelton Street, Covent Garden, London, WC2H 9JQ.

For the purposes of applicable data protection law, including the UK GDPR and EU GDPR, Ultraform Ltd is the data controller of your personal data.

By using the Service, you acknowledge the practices described in this Privacy Policy.

1. Scope

This Privacy Policy applies to personal data we collect when you:

  • visit our website
  • create an account
  • subscribe to a paid plan
  • use the Service
  • upload content or generate outputs
  • contact us
  • interact with billing, support, or security systems

This Privacy Policy does not apply to third-party websites, products, or services that may link to or integrate with the Service.

2. Personal data we collect

2.1 Account data

When you create an account or sign in, we may collect:

  • email address
  • name
  • profile image
  • authentication provider identifiers
  • account preferences
  • account status
  • subscription entitlement data
  • a record of which version of our Terms of Service you accepted, how (when creating your account, at checkout, or on an updated-Terms notice), and when, including the checkout session reference for an acceptance at checkout

Some information may be provided by third-party login providers such as Google or other supported authentication providers.

2.2 Payment and billing data

Payments are processed by third-party providers such as Stripe. We do not receive or store full card numbers.

For subscriptions purchased from 27 August 2026, Link (a Stripe service) acts as the merchant of record and is the seller for the transaction. Link collects your payment details, billing name and address, and any tax identifier you provide, in order to take payment and to account for applicable taxes. Link determines how it uses that transaction data for those purposes, so it acts as an independent controller rather than only on our behalf, and its own privacy policy applies to that processing.

You may be offered the option to create a Link account at checkout. A Link account is provided by Link and governed by its privacy policy, not this one.

We may receive and store:

  • billing name
  • billing email
  • country
  • VAT or tax identifiers where applicable
  • subscription plan
  • renewal dates
  • payment status
  • transaction identifiers
  • invoice metadata
  • Stripe customer and subscription IDs

2.3 Usage, device and analytics data

When you use the Service, we may automatically collect:

  • IP address
  • browser type
  • device type
  • operating system
  • approximate location derived from IP
  • pages visited
  • feature usage
  • timestamps
  • referring URLs
  • performance metrics
  • crash logs
  • diagnostic logs
  • abuse-prevention signals
  • rate-limit data

We may also use privacy-focused analytics and performance tools, including Vercel Analytics or similar providers, to understand product usage, traffic sources, page performance, and technical issues.

Recordings when the editor fails. When an error happens in the editor, we may send our error monitoring provider (Sentry) a recording of the editor from about a minute before the error to the end of that visit: its layout, the text on screen, where you clicked, what you typed into ordinary fields (for example the names of your projects, shots and files, and text you write), and which addresses the page requested. Your email address, name, sign-in codes, passwords and payment details are hidden in these recordings, and so are the images and videos you upload. If you go from the editor to another page in the same visit, that page is recorded with all its text hidden.

We use this information to operate the Service, secure accounts, prevent abuse, troubleshoot issues, and improve the Service.

2.4 Content you upload or create

We may process content you upload, import, edit, or generate through the Service, such as:

  • screenshots
  • images
  • logos
  • designs
  • mockups
  • exported assets
  • project files
  • prompts
  • settings
  • configuration data

We process this content solely to provide and improve the Service, store projects, generate outputs, and support requested features.

Browser capture extension

When you choose to capture a browser tab with the Ultramock browser extension, it processes its visible content as a screenshot or silent video, together with the source page URL, title, dimensions and recording details. The extension saves source metadata only for captures you request; it does not access your browser history or track general browsing. It does not record your microphone or webcam. If an AI agent you have connected to Ultramock asks your editor to capture a website, the extension opens that page in a new tab and captures nothing until you click its icon on that tab.

Cursor, cleanup and scrolling controls process pointer position, clicks and scroll state locally on the selected page. These interactions operate the requested controls and are not retained as a separate activity log or sent to an analytics service. Visible cursor movement and page interactions may appear in the recording you choose to capture.

The optional Device frame setting uses Chrome's debugger permission so captures can be taken at a device's full resolution. It is used only for a capture you start with a Device frame selected, either by you or by an editor capture request you then start by clicking the extension icon. For the duration of that capture it renders the tab at the device's screen size, adds space at the top of the page for a phone's status bar, and takes the framed screenshot. During a framed recording it also watches for the tab moving to a new page, so the device size can be applied to that page too; the addresses of those pages are not stored or sent anywhere. It attaches when the capture starts, removes that space and detaches when it ends. To keep that space correct it runs a small script in the page that reads element layout and colours, so fixed headers can be shifted down and the band above them tinted to match, and it undoes those style changes when the capture ends. It does not read page text, form input, network traffic or storage. The list of devices is downloaded from ultramock.io about once a day; that request contains no capture content or page data.

Capture data is temporarily stored in your browser and transferred locally to the Ultramock editor. Temporary extension copies are removed after acknowledgement or cancellation, or cleaned up after expiry. Imported recordings remain in this browser on this device until removed; clearing browser storage can remove them. Images and project data saved through the editor follow the Service’s storage practices described in this policy.

The extension does not send capture content to advertising or analytics services, sell it, or use it for credit decisions. Capture access is used to provide the capture and import features you request. The extension itself has no remote capture-upload service.

Chrome Web Store Limited Use

Our use of data obtained through the Ultramock browser extension complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. The following restrictions apply to extension data, including after import into the editor, and take precedence over broader uses described elsewhere in this policy.

We use extension data only to provide and support the capture, import and editing features you request. We do not use or transfer it for advertising, unrelated profiling, creditworthiness or lending. Transfers are limited to those necessary for these features, security, legal obligations, or a merger, acquisition or sale of assets, as permitted by the Limited Use policy.

We do not permit staff or service providers to read extension data except with your explicit consent for specific content, when necessary for security or legal compliance, or when aggregated and anonymised for internal operations as permitted by the Limited Use policy.

AI assistants connected through MCP

If you connect an AI assistant (such as Claude, ChatGPT or Codex) to Ultramock through our MCP server, with an API key or by signing in from the assistant, the assistant sends us structured requests to read and edit your projects. We receive those requests, not your conversation with the assistant: what you type to it stays between you and its provider.

To provide and secure this feature we process:

  • a log of each request: the action, whether it worked, how long it took, which assistant made it, and its settings (for example a device, an angle or a project id), with image data and credentials removed and long text shortened
  • a daily count of requests per account, kept for 32 days, to enforce limits and spot faults
  • copies of a project as it was before each of the assistant's edits, so it can undo its own work; up to 20, deleted 6 hours after its last edit
  • while the project is open in your editor: your playhead position and selected shot (so the assistant can tell what "this shot" means), and whether you are editing or have paused its edits; these are kept for seconds to hours and replaced as they change
  • images and videos the assistant uploads for you; files that are not added to a project are deleted after about a day
  • API keys and sign-in tokens, which we store only in hashed form

The results of a request, including images of your project, are returned to the assistant you connected. That provider's own terms and privacy policy apply to what it does with them. You can disconnect an assistant at any time on your account's MCP page, by revoking its API key or disconnecting it under Connected assistants.

2.5 Communications

If you contact us by email, contact form, support channels, or social channels, we may collect:

  • name
  • email address
  • message contents
  • attachments
  • support history
  • related technical details needed to resolve issues

2.6 Public profiles and the template marketplace

Some features publish information about you on purpose. Nothing in this section is public until you take the step described.

Your profile. When you claim a username, your profile page at ultramock.io/@username becomes public. It shows:

  • your username
  • your display name, which starts as the name from your sign-in provider
  • your profile image from your sign-in provider, if it has one
  • the bio and links you add
  • the templates you have published, and the total number of likes they have

You can change your display name, bio and links at any time on your account page. A username is permanent once claimed; to have one removed, contact us. A profile can appear in search engines once it has at least one published template; until then we ask search engines not to index it.

Your member card. Claiming a username also creates a member card at ultramock.io/@username/card, which anyone with the link can open. It shows your username, your display name, the date you joined, your member number (your place in the order people joined Ultramock) and your membership type: Member, Pro member, or Founding member for a lifetime purchase. Its link preview shows the same details apart from your display name. We ask search engines not to index the card page.

Link icons. Each link on a profile is shown with its website's icon, loaded from Google's favicon service. To show it, the visitor's browser sends Google the website's domain name (not the full link) and, as with any request, the visitor's IP address. No referring page is sent.

Publishing a template. When you submit a template to the marketplace, we keep a copy of it and our team reviews it. If it is approved, it is published under your username with its title, description, cover image and the stills you chose, and those images are served from public addresses. Your own screenshots and background images are removed from the copy unless you choose to include them. A template with motion also has a public preview video: its first 30 seconds as you rendered it, with its sound. For any sound you uploaded, we keep what you told us about it (where it is from, or that you replaced or removed it) for our reviewers. The number of likes is public; who liked a template is not. To enforce the Contributor Terms, we compare a submission with templates by other people that you have used, so we can spot one being republished as someone else's.

Selling a paid template. A paid listing shows the support email address you give for buyers, your refund policy, and whether you sell as an individual or a business. Anyone can see these on the listing.

Buying a paid template. Paid templates are sold through the seller's own Polar or Lemon Squeezy checkout. We do not take the payment, and that store's own privacy policy applies to the purchase. To unlock the template you give us the licence key from your receipt. We send it to the store that issued it to confirm it is valid, and check it again when you use the template, so a refunded purchase stops working. We keep the licence key and a record of the purchase. We do not give the seller your name or email address; they see only how many people have unlocked their template.

Reporting a template. When you report a template, we keep the reason you chose, what you wrote and which account sent it, and email them, with your username and email address, to our team. The seller is not told who reported it and does not see the report.

2.7 3D embeds

Publishing an embed. When you publish a shot as a 3D embed, we copy what the embed needs to show it to public addresses on cdn.ultramock.io: the shot's settings, a poster image of it, and the images shown on the device. Anyone with the embed code or those addresses can load them. Your name and email address are not part of an embed. When you update an embed, the files it no longer uses are removed; when you delete it, its files are removed and we ask our content delivery network to drop its copies.

Visitors to a website that shows an embed. Their browser loads the embed from js.ultramock.io, player.ultramock.io and cdn.ultramock.io, which are served through Cloudflare, our content delivery network. As with any web request, that involves the visitor's IP address and browser details. The embed sets no cookies.

When an embed fails to load. To find broken embeds, the embed may send an error report to our error monitoring provider (Sentry): about one failure in four, and at most three from one browser session, counted in that session's storage. A report contains what failed, the embed's identifier, the screen's pixel density and the website's domain name, not the address of the page.

3. How we use personal data

We use personal data for purposes including:

  • creating and managing accounts
  • authenticating users
  • processing subscriptions and payments
  • providing paid and free features
  • storing projects and outputs
  • showing your public profile, member card and published templates, when you choose to
  • checking licence keys for paid templates
  • reviewing marketplace submissions and enforcing the Contributor Terms
  • generating exports and renders
  • customer support
  • sending transactional emails
  • sending occasional emails about Ultramock, which you can unsubscribe from at any time (section 3.1)
  • fraud prevention and abuse detection
  • enforcing limits and Terms of Service
  • analytics and performance monitoring
  • debugging and error resolution
  • improving features and user experience
  • complying with legal obligations
  • responding to lawful requests
  • protecting our rights, users, and systems

3.1 Emails about Ultramock

When you create an account, or join our waitlist, we add your email address to our mailing list, and we may send you occasional emails about Ultramock: for example new features, tips for using it, and offers. Alongside your email address, the list records how you joined (for example signing up, or the waitlist) and whether you are on Pro, so that we can leave out emails that don't apply to you. We send these emails with Plunk, except the occasional personal note from our founder (for example a tip when you haven't made anything yet), which comes from the founder's own address and follows the same setting.

You can unsubscribe at any time: turn off “Emails about Ultramock” in your account settings, use the link in any of these emails, or write to privacy@ultramock.io. Unsubscribing doesn't stop the emails we need to send you about your account, sign-in, payments or projects. If you delete your account, we unsubscribe you. We keep your email address on the list marked as unsubscribed, so that it isn't added back by mistake.

We rely on our legitimate interests (telling people who use Ultramock about it) for these emails, as set out in section 4.

4. Legal bases for processing (UK GDPR / EU GDPR)

Where applicable, we rely on the following legal bases:

Contract

Where processing is necessary to provide the Service, manage subscriptions, authenticate access, process payments, or provide support, including publishing your profile, member card and templates when you ask us to, and checking a licence key you give us.

Legitimate interests

Where necessary for:

  • security
  • fraud prevention
  • abuse detection
  • enforcing usage limits
  • improving the Service
  • internal analytics
  • sending occasional emails about Ultramock to people who have an account or joined our waitlist (section 3.1)
  • system administration
  • defending legal claims

We balance these interests against your rights and freedoms.

Legal obligation

Where required to comply with tax, accounting, consumer protection, fraud prevention, or other legal obligations.

Consent

Where required by law for optional processing activities. You may withdraw consent at any time.

5. How we share personal data

We do not sell personal data.

We may share personal data with trusted service providers that help us operate the Service, including:

  • payment processors
  • hosting providers
  • infrastructure providers
  • database providers
  • authentication providers
  • email delivery providers
  • analytics providers
  • error monitoring providers
  • customer support tools
  • security and fraud prevention tools

Examples may include Stripe, Vercel, Google, Plunk (our mailing list, section 3.1), and other providers we use from time to time.

These providers process data on our behalf under contractual safeguards.

When you unlock a paid template with a licence key, we send that key to the store that issued it (such as Polar or Lemon Squeezy) to check it. Visitors to a public profile load link icons from Google's favicon service, as described in section 2.6.

Link is an exception. Where it acts as the merchant of record for your purchase, it is the seller for that transaction and decides how it processes the resulting payment and tax data. It is an independent controller of that data rather than a provider acting on our behalf.

We may also disclose personal data:

  • where required by law
  • to enforce our rights
  • to prevent fraud or security threats
  • in connection with a merger, acquisition, financing, or sale of assets

6. International transfers

Some service providers may process personal data outside the UK, EEA, or your country of residence.

Where required by law, we use appropriate safeguards such as:

  • Standard Contractual Clauses
  • UK International Data Transfer Addendum
  • adequacy regulations
  • supplementary technical and organisational measures where appropriate

7. Cookies and similar technologies

We use cookies and similar technologies for purposes such as:

  • authentication
  • session management
  • security
  • remembering preferences
  • fraud prevention
  • essential product functionality
  • limited analytics where permitted

Some cookies are strictly necessary and may not require consent under applicable law.

Where consent is legally required for non-essential cookies or similar technologies, we will request it through appropriate consent tools.

You can also manage cookies through your browser settings.

7.1 Product analytics

We run our own product analytics to understand how people find and use Ultramock, for example which pages lead people to the editor, and where they stop. It is first-party: the data stays with us and is never sold, shared with advertisers, or used to track you on other websites.

What we collect:

  • pages you visit on ultramock.io, and the site, page or campaign that brought you
  • which sections of our website pages were on screen, and for how long
  • how far down a page you scrolled
  • clicks on our own links and buttons, questions opened in our FAQs, and whether you played our product video
  • in the editor, what kind of action you take (for example “added media”, “changed the camera”, “animated”, “exported”, “saw the upgrade screen”), never the content of anything you upload or create
  • your country, device type and browser family
  • if you have an account: whether a visit led to signing up or subscribing, which plan, and whether you were on the Free or Pro plan at the time

We do not store your IP address or your full browser identification string for analytics, and we do not record keystrokes, form entries or screen recordings.

What happens depends on where you are:

  • Where the law allows analytics without consent (including the United States): we set a first-party cookie (um_vid) that recognises your browser across visits for up to 12 months. If you have an account, your visits are linked to it. You can turn this off below.
  • The United Kingdom, France, Spain, Italy and the Netherlands: we ask first. Until you accept, we only count visits anonymously: nothing is stored on your device, the counts are never linked to you or your account, the individual events are deleted within 48 hours, and only an anonymous summary of each visit is kept (for example its country, device, pages and the kinds of action taken). You can turn those anonymous counts off too.
  • Everywhere else consent is required (including the rest of the EU and EEA, and Quebec): we ask first, and collect nothing unless you accept.

If your browser sends a Global Privacy Control or Do Not Track signal, we treat it as a refusal and collect nothing. Your choice is remembered with a cookie (um_consent or um_optout) that only records the choice itself; we ask again after 6 months if you refused, and after 12 months if you accepted.

We rely on legitimate interests (improving the Service) for anonymous counts, and on your consent where it is required. Individual analytics events are deleted after 30 days, and anonymous ones within 48 hours. We keep a short summary of each visit (for example the pages and sections seen and the kinds of action taken). If you have an account it is linked to it and deleted with it. Without an account, a summary stops being linked to your browser after 13 months. Summaries of anonymous visits are never linked to anyone. Deleting your account deletes the analytics linked to it.

Loading your settings…

7.2 Command menu searches

The editor’s command menu (Cmd+K, or Ctrl+K) asks signed-in users once whether we may save what they type into it. We only save your searches if you say yes. Guests are never asked and nothing is saved for them.

If you say yes, for each time you use the menu we save:

  • the last thing you typed (up to 200 characters), with email addresses, web addresses, IP addresses, and phone, card and other long numbers replaced before it is stored
  • whether you ran a result, went to a setting, or closed the menu, and which result you picked and its position
  • whether you were editing a device, text or logo shot, the device model in a device shot, and the app version
  • when it happened

We use this only to improve search: to add the commands and words people look for and fix results that rank badly. It is linked to your account, seen only by our team, and never sold or shared. Our legal basis is your consent, and we record your answer with the date.

Saved searches are deleted after 90 days, and when you delete your account. You can turn saving off at any time with the switch below or the menu’s “Stop saving my searches” command; turning it off deletes the searches we saved.

Whether or not you say yes, product analytics (7.1) may count that a menu result was run, which one (for example “camera zoom”), or that a search found nothing, without what you typed.

8. Data retention

We retain personal data only for as long as reasonably necessary for the purposes described in this Privacy Policy, including legal, operational, security, fraud-prevention, accounting, and contractual purposes.

Typical retention periods may include:

  • account data: while your account remains active and for a reasonable period after closure
  • projects: while you have Pro; if your plan ends, for at least 12 months after that, and we email you before they are deleted
  • a free account’s one saved project: for at least 12 months after it was last edited, and we email you before it is deleted
  • public profile and member card: while your account remains active; they are removed when you delete your account
  • 3D embeds: while they are published; they are deleted when you delete your account
  • published templates: while they are published. If you delete your account (or say you won’t keep supporting them when you cancel Pro), they are taken down; Ultramock may then offer them for free under its own name, without your name, or remove them. A paid template someone has bought stays available to its buyers
  • paid template purchases (including licence keys): while your account remains active
  • template reports: until the template is deleted; if you delete your account, the saved reports no longer record who sent them (the email our team received stays in our inbox)
  • mailing list: until you unsubscribe or delete your account; after that, your email address stays on the list marked as unsubscribed so you aren't emailed again
  • billing and tax records: for periods required by law
  • support records: for operational, dispute-resolution, and legal needs
  • usage logs and diagnostics: for security, debugging, abuse prevention, and product improvement needs
  • sign-in activity: 90 days
  • AI assistant (MCP) data: as described in section 2 (undo copies 6 hours, request counts 32 days, unused uploads about a day; request logs as usage logs)
  • product analytics: individual events 30 days (anonymous: 48 hours); per-visit summaries are kept, unlinked from your browser after 13 months and deleted with your account
  • command menu searches (only if you said yes, section 7.2): 90 days, or until you turn saving off or delete your account
  • backups: until overwritten or deleted through normal backup cycles

Where reasonably practicable, we delete, anonymise, or de-identify personal data when no longer needed.

Some data may be retained longer where required by law, to resolve disputes, prevent abuse, enforce agreements, or protect legal rights.

9. Your privacy rights

Depending on your location, you may have rights regarding your personal data.

These may include the right to:

  • access your data
  • correct inaccurate data
  • request deletion
  • restrict processing
  • object to certain processing
  • withdraw consent
  • receive a portable copy of your data
  • complain to a supervisory authority
  • appeal certain privacy decisions where applicable

To exercise a rights request, contact privacy@ultramock.io.

We may need to verify your identity before fulfilling requests.

We will respond in accordance with applicable law.

Where Link is the merchant of record for your purchases, you can also ask Stripe to delete the data held for those transactions. Doing so cancels any subscription sold through Link and deletes the associated payment records, so please make a request to us first if you want to keep your subscription active.

10. US state privacy rights

Residents of certain US states, including California, may have additional privacy rights under applicable law.

These may include rights to:

  • know categories of data collected
  • access specific data
  • correct data
  • delete data
  • opt out of certain sharing or targeted advertising
  • non-discrimination for exercising rights
  • appeal denied requests where applicable

We do not sell or share personal information, as those terms are defined under applicable US privacy laws, and we do not use it for targeted advertising.

We honour Global Privacy Control and Do Not Track signals: when your browser sends either, our product analytics are switched off for you (see section 7.1).

To make a request, contact privacy@ultramock.io.

11. Children

The Service is not intended for children under 16.

We do not knowingly collect personal data from children under 16.

If you believe a child has provided personal data, contact us and we will take appropriate steps.

12. Security

We use reasonable technical, administrative, and organisational safeguards designed to protect personal data.

These may include:

  • encrypted connections (TLS)
  • access controls
  • credential management
  • monitoring and logging
  • least-privilege practices
  • managed hosting safeguards
  • secure payment processing through providers

No system is completely secure, and we cannot guarantee absolute security.

13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time.

If we make material changes, we may notify users through email, in-product notice, or by updating the date at the top of this page.

Your continued use of the Service after changes take effect means you acknowledge the updated Privacy Policy.

14. Contact

For privacy-related questions or requests: privacy@ultramock.io

For legal or general enquiries: legal@ultramock.io

Never miss an update

Get new features, release notes, and the occasional behind-the-scenes from Ultramock, straight to your inbox.