Privacy Policy

Who we are

Omniscape is operated by Omniscape LLC. When this page says “we”, “us” or “Omniscape”, that is the company it means.

It covers the marketing site at omniscape.io, the self-serve product at app.omniscape.io, and the branded studio portals we run for customers on their own subdomains of omniscape.io.

Questions, requests, or corrections: info@omniscape.io. A person reads that address.

The short version

• Nothing that records you loads before you opt in. That is true on the marketing page and in the signup flow and studio, and each of those asks separately — a yes on the marketing page does not turn on recording inside the product. If your browser sends Global Privacy Control, wherever we would ask about recording we record a no for you and never ask. Session recording never runs on a customer’s branded portal at all.
• We only measure visitors in the United States. If you are anywhere else, none of it runs for you — not Vercel Web Analytics, not Speed Insights, not Microsoft Clarity. You are not asked to consent, because there is nothing to consent to. If we cannot tell where you are, we treat that as “not the United States” and measure nothing.
• Separately from that opt-in, and within the United States only, every page our application renders — including the branded customer portals — carries Vercel’s own cookieless page-view and performance measurement, which the banner does not switch off. The analytics section below is exact about where each thing runs.
• We do not sell your data, and we do not run advertising trackers or ad-network pixels anywhere on our sites.
• If you make an account, we store the things needed to run it: your email, a hashed password, what you made, and what you uploaded to make it.
• Making a video means sending your prompt and your images to the AI providers listed below. That is not optional — it is how a render happens.
• You can ask us to delete the personal information held with your account by emailing info@omniscape.io. We do it by hand, and some records survive it — the retention section below says which, and why.

Analytics and consent

There are two different things here, with two different rules. One can record a session and only runs if you say yes. The other cannot record a session and runs everywhere our application does. This section says exactly which is which and where each one is. Before either of them, there is a rule that applies to both.

First: measurement runs only in the United States

Microsoft Clarity — opt-in only, US only, and only in two places

Microsoft Clarity measures how a page is used: clicks, scrolls, mouse movement, and session replays of the page you were on. It is opt-in only and, like everything else on this page, United States only. The only places it can run are:

• The marketing page at omniscape.io. Clarity records that page as it is shown to you.
• The signup flow and the studio at app.omniscape.io, which asks its own separate question — see below. Because that is a recording of a session inside a product you are logged into, we mask what we can: page text and anything you type are masked before they leave your browser, which covers your quotes and captions, file names, workspace names, and the email address you type into signup. Images on screen are not masked, including your own photos and your renders. Clarity’s replay refetches images by their address, so masking text does not reach them. Masking images is a setting on Clarity’s own dashboard rather than something our code can do; we may turn it on, and we will say so here when we do. A replay also shows, unmasked, the pages and addresses you visited, the shape and layout of the screen, where you clicked, how far you scrolled, your browser and device, and approximate location from your IP address. This one also sits behind a switch that is off today — while it is off, no Clarity script loads there at all, opted in or not.

The app host asks its own question

Saying yes on the marketing page does not switch on recording inside the product, and we do not carry your answer across. They are not the same thing: the marketing page measures an anonymous visitor reading a public page, while the app host records a session inside a product you are logged into, with your own photos and your own work on the screen. Agreeing to the first is not agreeing to the second, so the app host asks you again, in its own banner, in its own words.

Neither answer carries across, a no included. Your browser keeps the storage for omniscape.io and for the app host separate, so neither can read the answer you gave the other. So a no on the marketing page does not answer the product’s question, and the product asks you itself, in its own banner, while its recording switch is on. If you want one answer that holds everywhere without being asked, turn on Global Privacy Control in your browser: wherever a surface asks about Clarity recording (for visitors in the United States, and on the app host only while its recording switch is on), it reads the signal, records you as opted out, and Clarity never loads. The signal does not switch off Vercel’s own page-view and performance measurement for United States visitors, described below.

How either opt-in works

• Nothing loads before you opt in. Until you press Opt in on the banner there is no Clarity script on the page and no Clarity cookie in your browser.
• If your browser sends Global Privacy Control (or the older Do Not Track signal), then wherever a banner would ask you, you are recorded as opted out of Clarity automatically and the banner is never shown.
• Your two answers are stored separately, in your own browser. The marketing page owns om-consent-measurement; the app host owns om-consent-measurement-app, and that is the only one of the two that can switch on recording inside the product. Neither ever overwrites the other. Both are local storage on your device rather than records on our servers, so neither follows you to another browser or device, and clearing your site data clears both and puts the questions back.
• Withdrawing is as easy as giving. The marketing page carries a persistent ( Analytics choices ) control in the footer of omniscape.io, which reopens its banner so you can change your answer. It is one click, with no account and no email required. Opting out stops Clarity in the page you are on. The product asks nothing while its recording switch is off, so it has no such control today; it gets its own when the switch is on.
• When you opt in, we tell Clarity that advertising storage is denied and only analytics storage is allowed. We never consent to ad storage on your behalf.
• Opting out does not by itself erase replays Microsoft already holds. Email info@omniscape.io and we will submit a deletion request to Microsoft for them.

Never on a customer portal, and never on our control plane

Clarity does not run on the branded studio portals we operate for customers on their own subdomains of omniscape.io, and it does not run on the internal portal we administer the business from. We do not session-record a paying customer’s workspace. There is no consent banner on those hosts because there is nothing there to consent to.

Vercel’s hosting measurements

What we collect

If you never make an account

Reading the marketing page requires nothing from you. Your IP address and browser user-agent reach our servers with the request, as they do with any website; they are used to serve the page and to rate-limit abusive traffic, and our hosting provider logs them. If you email us, we have your email and whatever you wrote in it.

One exception worth naming: if you start a signup, we record that attempt even when it does not become an account — the IP address, the browser user-agent, the domain part of the email (never the full address), and why the attempt was rejected. That record exists to catch bots and abuse.

If you make an account

• Your email address and your name. Creating an account yourself asks for your full name when you accept our terms, and we keep it with the record of that acceptance; an account someone else sets up for you carries the name they gave us, if any. We never invent a display name out of your email address.
• Your password, hashed with bcrypt. We store the hash, never the password itself, and we cannot read or recover it.
• Your workspace — the account, its plan tier, and which users belong to it.
• The IP address you signed up from, and whether you agreed to marketing email. We also record which version of our terms you accepted, when, and the full name you accepted them under; the version is stored as a fingerprint of the exact document text.
• Your confirmation that you are 13 or older. Creating an account requires confirming it, and we keep that confirmation alongside the record of the agreement you accepted, so we can show what you were asked and when you answered. We do not ask for your date of birth or your actual age.
• What you make and what you make it from — the photos, video clips, quotes, captions and prompts you upload or type, the rendered videos themselves, and a record of each render (when it ran, whether it succeeded, what it cost us to produce).
• Email delivery state — whether we sent you a verification, reset, or notification email, and whether you have unsubscribed.
• Billing identifiers, if you subscribe. See the payments section below.

We do not ask for, and have no field for, your date of birth, government ID, precise location, or biometric data.

Your uploads, prompts, and renders

Making a video means handing your material to the service that renders it. When you run a render, the images, video clips and text involved are sent to the relevant AI or rendering provider named in the table below, and the finished file comes back to us. We store the result in our own storage so that your library does not depend on a vendor’s temporary links.

We do not use your uploads or your renders to train our own models — we do not train models. What the individual providers do with material sent to them is governed by their own terms; we have not negotiated a separate no-training commitment with each of them, and we would rather tell you that than imply otherwise.

Some renders can be published to a public share link. Anything you deliberately share that way is, by design, viewable by anyone holding the link.

Who else touches your data

These are the outside services the product actually uses, and what each is used for.

This is our current list of sub-processors — the outside services that process personal information or customer data on our behalf — and it is current as of the Last updated date at the top of this page. We will update this list when we materially change the providers that process personal information or customer data on our behalf.

We do not sell personal information, and we do not share it with advertising networks or data brokers.

Cookies and local storage

We set no advertising cookies ourselves, and nothing is set for measurement unless you opt in. If you opt in to Microsoft Clarity, Microsoft sets the cookies listed below on its own terms, and Microsoft says some of them are also used across its own sites. Here is every item we or a provider put in your browser, what it is for, and how long it lasts.

Three categories are used below. Strictly necessary means the Service cannot do what you asked without it: signing you in, the passcode door, and the record of your consent answer. It is set whatever you choose. Preference means it remembers a choice you made about how the product looks or behaves (your theme, a list layout, what you used last, which notices you have seen). It is never used to measure you and never shared with anyone else: the theme cookies are sent only to our own servers, so the page is drawn in your theme. Clearing it only resets that choice. Measurement means it exists to tell us how the product is used: it is set only after you opt in, and it stops when you opt out.

Three things that are not in the table, and why:

• Vercel Web Analytics and Speed Insights set nothing. Vercel documents both as cookieless; they store no identifier in your browser, which is why they have no row above.
• Cloudflare Turnstile, the bot check on login and signup, is embedded from Cloudflare and processes signals Cloudflare lists as your IP address, TLS fingerprint, user-agent and our site key. We do not enable Turnstile’s pre-clearance mode, which is the mode Cloudflare documents as setting a cf_clearance cookie, so we do not list a Turnstile cookie here. Anything Cloudflare sets on its own challenge domain is under Cloudflare’s terms, not ours.
• Stripe. Checkout happens on Stripe’s own pages, not ours, so Stripe’s cookies are set there under Stripe’s terms. We load no Stripe script on our pages.

Blocking or clearing the sign-in items will log you out and, on the hosts that have one, put the passcode door back in front of you. Clearing a record of your consent answer brings that surface’s banner back. Clearing a preference item only resets that choice; you stay logged in. Nothing above is used to build a profile of you or shared with an advertising network.

Payments

Subscriptions are handled by Stripe. Card numbers are entered on Stripe’s own hosted surfaces and are never sent to or stored by Omniscape. What we keep on our side is the identifiers and subscription state Stripe gives us back — your customer and subscription IDs, your plan, and whether it is active — which is what lets the product know which features you have.

How we protect it

Concretely, and only what we can point at:

• Everything is served over HTTPS.
• Passwords are stored as bcrypt hashes, never in readable form.
• Session cookies are HTTP-only and host-scoped, so a session cannot be read by page scripts or reused across customer portals.
• Keeping accounts separate is a design rule we enforce in our own code. Customer records carry the account they belong to, and our server routes are written to scope every read and write to the account making the request, checking who you are and what you are allowed to touch. There is no browser-side database access at all — the browser can only reach our own server routes, and our database credentials never leave the server. We describe that as the control we operate, not as a guarantee no mistake is possible.
• Requests are rate-limited to blunt brute-force and abuse, and signups run through a bot check.
• The database rejects anonymous access outright. Row-level security is on, and the only role with a policy is our server’s own — there is no public credential that can read anything. To be exact about what that does and does not do: it shuts out anyone without our server’s credential, and it is not what separates one customer account from another. That separation is done by our server code, as described above.
• Our database and file storage are operated by Supabase and our hosting by Vercel, both of which state that they encrypt stored data at rest as part of their platforms. That is their commitment about their infrastructure, not encryption we perform ourselves on top of it.

No system is perfectly secure, and we are not going to pretend otherwise. If you believe you have found a security problem, please write to info@omniscape.io and we will take it seriously.

Staff access to accounts

We would rather you hear this from us than discover it. A small number of Omniscape administrators can sign into a customer account — to provide support, investigate a failed render, fix a billing problem, or check on an account we have suspended, which stays reachable to staff precisely so a suspension can be undone.

Being accurate about the controls on that, because the details matter more than the reassurance:

• You are not automatically notified. On our branded client portals the screen carries a banner while the session is a staff session, but that banner is on the staff member’s screen, not a message sent to you. The self-serve app at app.omniscape.io does not show that banner at all.
• Access is meant to be logged, and the log is not yet guaranteed. Every such sign-in writes to an internal audit trail, but that write is deliberately allowed to fail without blocking the access, and the audit table is not yet in place on every environment. So access can happen without a row being recorded. We are not going to claim a complete trail we cannot yet prove.
• If you want to know whether anyone has opened your account, ask us at info@omniscape.io and we will tell you what we hold.

How long we keep things

We do not delete account data or customer content on a fixed automatic schedule. We generally keep your account information, uploads, renders and workspace records for as long as the account exists, so your library is there when you come back.

Here is the schedule we work to. Treat these as our retention targets rather than guaranteed expiry dates: most deletion today is still carried out by hand rather than by an automatic timer, so the moment a record actually leaves our live systems can run a little longer than the window below.

• Customer content — your uploads, renders and workspace records — is kept for as long as the account is active.
• Paid accounts: after termination we keep customer data available for export and then delete it about 30 days later, matching the export period in the Subscription Agreement.
• Trial and free content: deleted about 14 days after the trial or free period ends, as set out in the Trial Terms.
• Security and abuse-prevention logs — including the anti-abuse signup record described above — are kept for about 12 months.
• Billing, tax and contract-acceptance records are kept for about 7 years to meet accounting and legal obligations.
• Backups are kept only for our infrastructure providers’ documented backup lifecycle; we do not set a separate window of our own for them.
• Legal hold: anything under a legal hold is kept until the matter it relates to is resolved, even if a window above would otherwise have passed.

You can ask us to delete personal information associated with your account by emailing info@omniscape.io. There is no self-service delete control today: we verify the request and carry it out by hand.

Deletion does not necessarily reach everything. We may keep information we need for security and abuse prevention — including the anti-abuse signup record described above — and for billing, tax, accounting, contract enforcement, legal claims, or other legal obligations, along with a limited record that the account or the request existed. Removing data from our live systems also does not immediately remove copies held in our infrastructure providers’ backups, or information a payment, email, analytics, AI or rendering provider keeps independently under its own terms — Stripe’s payment records being the clearest example. We do not currently promise a specific period after which those backup copies expire.

If you sign a contract with us

Business customers accept our agreements electronically. When you sign, we record the name and email you typed, the time, your IP address and browser user-agent, and a copy of the exact document you agreed to. That record exists so both sides can prove later what was agreed, and it is kept for as long as the agreement matters.

Your choices

• Analytics: opt in or out at any time on the marketing page, with the ( Analytics choices ) control in the footer of omniscape.io. The product asks nothing while its recording switch is off; when it is on, it asks separately, keeps a separate answer and has its own control. Withdrawing takes exactly as many clicks as agreeing did, and we do not ask you for anything in return.
• Email: transactional email (verification, password resets, billing) is part of running your account. Anything else carries an unsubscribe link, and it works without logging in.
• See or correct your data: most of it is visible in the product. For anything that is not, email us and we will get it for you.
• Delete your account: email info@omniscape.io from the address on the account. There is no self-serve delete button; we do it by hand, and we will confirm when it is done. We remove your workspace, its users, and its content and stored files — not the records described under How long we keep things, which is where the exceptions are set out.

Your privacy rights, and how to use them

Omniscape complies with the privacy laws that apply to how we process personal information. Depending on where you live and subject to those laws, you may have the right to request access to or a copy of your personal information, correction, deletion, or portability; to object to or restrict certain processing; to opt out of sale, sharing for cross-context behavioural advertising, targeted advertising, or certain profiling; and to appeal if we turn a request down. Omniscape does not sell personal information and does not use it for targeted advertising.

If you are in the United Kingdom or the European Union, your rights come from the UK or EU GDPR and are set out specifically — along with our lawful basis for each thing we do, and the deadline that applies to you — under If you are in the UK or the EU.

To make a request, email info@omniscape.io with the subject Privacy Request and tell us which right you want to use. We may ask for information reasonably necessary to verify your identity, your account, or your authority to act for someone else; we use that information only to handle the request.

We will acknowledge a request within 10 business days and respond within 45 calendar days — sooner where the law requires it. If the law allows an extension we will tell you why and give you the new date. If we deny a request we will explain why and how to appeal by replying to that decision. We will not treat you differently for exercising a privacy right.

If a business customer put your information into Omniscape, that customer usually decides what happens to it — contact them first. We will help them as our agreement with them and the law require.

If you are in the UK or the EU

This section is for people covered by the UK GDPR or the EU GDPR. Everything above still applies; this adds the things those laws specifically require us to tell you.

Who is responsible for your information

For the marketing site, the self-serve product at app.omniscape.io, and your own account with us, the controller is:

Omniscape LLC, a Delaware limited liability company
8 The Green #26398, Dover, DE 19901, United States
info@omniscape.io

There is a second case. When a business customer uses Omniscape to handle information about other people — a creator, an employee, someone whose photograph was uploaded — that customer decides why and how it is used, so that customer is the controller and we are its processor. If your information reached us that way, ask them first; see If you are a business customer.

We have not appointed a UK or EU representative under Article 27. We are telling you that rather than leaving you to look for one. Write to the address above and a person will answer.

Why we are allowed to use it (lawful basis)

We do not make decisions about you by automated means that produce legal effects or similarly significant effects on you. Automatic limits in the product — a render allowance, a rate limit, a bot check — restrict what the product will do at that moment; they do not profile you, and suspending an account is a decision a person makes.

Your rights

Subject to the conditions the GDPR sets on each one, you can ask us to:

• Access — confirm whether we hold personal data about you and give you a copy of it.
• Rectify — correct it if it is wrong, or complete it if it is missing something.
• Erase — delete it. The limits on this are real and are set out under How long we keep things: records we must keep for tax, billing, security or a legal claim survive a deletion request, and we will tell you which ones did.
• Restrict — keep it but stop using it, for example while you are disputing whether it is accurate.
• Port — receive the data you gave us in a structured, commonly used, machine-readable format, or have us send it to someone else where that is technically feasible.
• Object — to any processing we base on legitimate interests, including Vercel’s measurement, and to direct marketing at any time, which is absolute and needs no reason.
• Withdraw consent — at any time, for anything we do on the basis of consent. Withdrawing is as easy as giving: the analytics banner is one click either way from the same control, and marketing email has a one-click unsubscribe that works signed out. Withdrawing does not make what we did before it unlawful, and it will never cost you access to a feature you paid for.
• Complain to a supervisory authority. You can do this without asking us first, though we would rather you gave us the chance to fix it. In the UK that is the Information Commissioner’s Office (ico.org.uk). In the EU it is the authority for the country you live or work in, or where you think the problem happened; the list is at edpb.europa.eu.

To use any of these, email info@omniscape.io with the subject Privacy Request. We may ask for enough information to be sure it is really you, and we use what you send only to handle the request. There is no fee, unless a request is manifestly unfounded or excessive — in which case we will say so and explain why before charging anything or refusing.

Sending your information out of the UK and the EEA

We are based in the United States and so is our infrastructure, so using Omniscape from the UK or the EU means your personal data is transferred to, and processed in, the United States and potentially other countries outside the UK and the EEA. The providers that receive it are the ones listed under Who else touches your data.

Where a provider is outside the UK or the EEA and is not covered by an adequacy decision, we rely on the European Commission’s Standard Contractual Clauses — with the UK International Data Transfer Addendum for UK transfers — as incorporated into that provider’s own data processing terms. Several of the providers above publish exactly those terms and apply them to every customer by default.

How long we keep it

The windows are set out in full under How long we keep things, and we are not going to restate them differently here. Two points that matter for this section specifically: those windows are operational targets rather than automatic timers, because most deletion today is done by hand; and for anything without a stated window — backups being the clearest case — the period is not yet fixed, and we would rather write that than publish a number nothing enforces.

Where information is processed

Omniscape is based in the United States. We use service providers to host, operate, render, analyse and support the Service. Our AWS and Remotion rendering defaults to the AWS us-east-1 region unless its deployment configuration specifies another region.

We do not currently offer a data-residency commitment or guarantee that customer data will stay in a particular country or region. We have not made a public commitment as to a fixed processing region for our database, application functions, logs, backups, analytics or other providers.

If your organisation requires a particular storage location or an international-transfer mechanism, contact info@omniscape.io before submitting personal information or customer data; we will make such a commitment only in a written agreement signed by Omniscape.

If you are in the UK or the EU, the transfer mechanisms we rely on — and what we have not yet documented — are set out under If you are in the UK or the EU.

If you are a business customer

When a business customer puts personal data into Omniscape and decides why and how it is used, that customer is the controller (or business) and Omniscape acts as its processor (or service provider). That distinction decides who answers a request from a creator, an employee or a contract signer whose data was uploaded by a customer.

A data processing agreement is available on request — email info@omniscape.io and we will send you the current version. The sub-processors that would handle your data, and what each one is used for, are published above under Who else touches your data; that is the standing sub-processor list for this Service, and we keep it current.

Security incidents

If we confirm a security incident involving personal information, we will investigate, take reasonable steps to contain and fix it, and notify affected customers, individuals, regulators or others where the law requires it.

Where we act as a processor for a business customer, we will tell that customer without undue delay after confirming a breach affecting its data, and give it the information we reasonably have so it can meet its own obligations. Notices to individuals are made without unreasonable delay and within any deadline the law sets, allowing for law-enforcement restrictions and the time it takes to work out who is affected.

We deliberately do not promise a fixed number of hours here. A timeline we cannot currently staff would be worth less to you than the commitment above.

How this relates to your agreement

This Privacy Policy is a notice describing what we do with information. It does not create a separate choice of law or a separate place to bring a dispute, and it does not change an agreement you have already accepted with us. Governing law, arbitration and venue are set by the applicable Terms of Service, Subscription Agreement or other written agreement — subject to any rights that cannot lawfully be waived.

Minimum age

You must be at least 13 years old to use Omniscape. The Service is not directed to children under 13, and we do not knowingly collect personal information from anyone under 13.

Creating an account also means accepting an agreement and making promises about your rights to the images and words you upload. If you are under 18, a parent, guardian or the business you work for must accept that agreement and hold the account with you.

A business customer may upload content showing a minor only if it has every right, notice and consent the law requires. If you believe someone under 13 has created an account or sent us personal information, email info@omniscape.io. We will look into it and take appropriate steps, which may include suspending the account and deleting information where we are required to.

Changes to this policy

When this policy changes we update the Last updated date at the top. For a change that meaningfully affects what we collect or who we share it with, we may give additional notice — by email or in the product — where the law requires it or the change warrants it. We have not built an automatic notification for policy changes, so we are not going to promise one here.

Contact

Omniscape LLC
info@omniscape.io