Privacy Notice
This notice covers this website only — the questions you answer here and the purchase you make here. The Dualsy mobile app has its own privacy notice, which covers what happens on your device after you install it.
Nexa Labs, LLC is the data controller for the information described below. We are contactable at support+dual@lenalabs.ai.
What this site collects
Your answers
Dualsy records with two of your phone's cameras at once, so the questions on this site ask about how you shoot and where you post, and nothing else. We do not ask for your name or anything else that identifies you personally except one thing: the last question asks for your email address, because a subscription has to have somewhere to send the receipt and the link you cancel from. It stays in your browser until you open the checkout. This site never asks your browser for your camera, your microphone, your photo library or your location — the app asks for those on your phone, later, behind prompts you can decline. Each question needs an answer before Continue will move, so if you would rather not answer one, closing the tab is the way out and nothing further is kept. Your answers stay with this website: they are not sent to the app, so the app asks its own questions again when you first open it.
| What | Why |
|---|---|
| Where will you post: TikTok, Instagram, YouTube or Other platforms. You may pick more than one | Shown back to you on the summary at the end of these questions, and it is one of the three figures behind the weekly time estimate printed there. Sent to our analytics so we can see which platforms the people who buy come from. |
| What do you create: Short-form vertical, YouTube creator, Podcast & interview, Vlog / lifestyle or Educational / how-to. You may pick more than one | Groups you with creators who make the same kind of video, so the summary describes your setup back to you in your own words. Nothing about the app changes as a result. |
| What do you create content about: Fitness & Sports, Beauty & Makeup, Art & Design, Food & Drink, Travel, Gaming, Education, Music & Dance, Tech, Fashion, Daily Vlog or Comedy. You may pick more than one | The same: it is how the summary names what you make. Sent to our analytics as a segment. |
| How often do you post: 1–3 a week, 4–6 a week or 7+ a week | Multiplied by your answers about shoot and edit time to produce the rough weekly figure on the summary page. It is arithmetic on three answers you gave, labelled an estimate wherever it is printed, and it is never a forecast. |
| How do you get a second angle today: I shoot the scene twice, I set up a second phone, I flip the camera mid-take, Someone films me or I don't — one angle is what I get | Decides which single sentence the summary leads with. Sent to our analytics so we can tell which problem brings people here. |
| Which shapes do you need out of one shoot: 9:16 vertical, 16:9 horizontal, 1:1 square or 4:3 standard. You may pick more than one | Shown back on the summary as the shapes one take could give you. Sent to our analytics. |
| How long does one shoot take you: 5 minutes, 15 minutes, 30 minutes or 1 hour or more | The second of the three figures behind the weekly time estimate described above. |
| And how long after the shoot: Under 15 minutes, 15 to 60 minutes, 1 to 3 hours or 3 hours or more | The third of those figures. It is the number that makes the estimate worth printing at all. |
| How will you shoot: I'll shoot dual, I'll shoot front + back or I'll use the teleprompter. You may pick more than one | Shown back on the summary, and sent to our analytics as a segment. It is the answer that decides which of the app's features the summary mentions first. |
| What's your main goal: Publish on multiple platforms, Catch trends fast, Make higher quality content or Grow my audience | Decides the one line the confirmation strip shows after it, and the order of the summary. Sent to our analytics. |
| Which iPhone will you shoot on: iPhone 15 or newer, iPhone 12 to 14, iPhone XS, XR or 11, Older than iPhone XS or I'm not sure | Read only to tell you, before you pay, whether your iPhone can record two cameras at once — it is a hardware feature and older models cannot. Sent to our analytics as a band, never a serial number or a device identifier. |
| Your email address | Handed to the checkout when you open it, so the checkout does not ask for it again beside your card details: RevenueCat, which runs our checkout and subscription, records it against your purchase and sends the receipt and the link you cancel from. Until you open the checkout it stays in your browser and we do not receive it; the coded form of it that Meta receives is described below the table. It is never joined to the answers above, and it is not sent to our analytics. |
None of the questions asks for your name, phone number or postal address. Your answers are stored against a random identifier generated in your browser, not against anything that identifies you.
One question does ask for your email address. A subscription has to have somewhere to send the receipt and the link you cancel from, and asking a screen earlier means you type it once rather than beside your card details. We do not receive it until you open the checkout, though Meta's script on this page sends a coded form of it once you go on, as the next paragraph explains. Typing it sends us nothing: if you never reach the checkout we never receive it at all, and clearing your browser data removes it. When you open the checkout it goes to the payment provider so the receipt and the cancellation link can reach you — that happens when the checkout opens, not when the payment completes — and it is not joined to your answers.
Once you go on from that question, your address also goes to Meta, as a hash and never as an address: with each step after it, and with your purchase. Meta's script on this page turns it into a fixed code before it leaves, and only the code is sent. Meta compares that code with the addresses it already holds, which is the whole point of sending it: it is how a purchase here is matched to the account that was shown the advert. Be clear about what that means: a code like this cannot be read backwards, but it is not anonymous either — anyone who already knows your address can produce the same code, which is exactly how the match works. We do not send your answers. If you appear to be in the UK, the EEA or Switzerland, none of this happens unless you agreed to it above.
Your purchase
We are the seller, so the purchase record is ours: your email address, what you bought, what you were charged, and the country the tax was worked out for. We need it to charge you, to send your receipt, to let you cancel, and to keep the accounts the law requires us to keep.
Your card details are not part of that. They are typed into Stripe's own fields, inside Stripe's frame, and are never sent to, seen by, or stored on this website. We receive the last digits and the card type, which is what a receipt shows, and nothing that could be used to charge a card.
Usage
We record which screens you reached and which options you chose, so we can see where people give up and improve the flow. These records carry the same random identifier, never your name or email.
Measurements are recorded as ranges, not exact figures: an analytics record says which band a value fell into, not the value itself.
Approximate location
We work out which country you are in — from your device's time zone and, where our network provider supplies it, the region of your connection — so the options we show you are the ones available where you live. This is a country, never a precise location, and it is not stored.
What is stored in your browser
We store data locally in your browser so you do not lose your place:
- Your answers and your session identifier, so a reload or a phone call does not make you start over. Kept for 7 days.
- After a purchase, the same record is kept for 180 days. It is what lets us rebuild your unlock link if the copy to your clipboard failed. Without it a purchase can be stranded.
-
Advertising cookies (
_fbpand, if you arrived from an advert,_fbc), set by Meta so that a purchase can be matched to the advert it came from. Kept for 90 days. -
Session-recording cookies (
_clck, kept for 1 year, and_clsk, kept for 1 day), set by Microsoft Clarity so that several page views are recognised as one visit rather than several strangers. Microsoft also sets cookies of its own fromclarity.ms— includingMUID, which Microsoft states it uses for advertising as well as analytics. - If you appear to be in the UK, the EEA or Switzerland, we ask you first. Until you agree, none of it runs: no advertising cookie is set, nothing is sent to Meta, nothing is recorded, and none of Microsoft's cookies above are set. If you decline, it stays that way, and the rest of this site works exactly as it did.
Clearing your browser data removes all of these. You can also stop the advertising cookies with any browser setting or extension that blocks third-party trackers; nothing on this site stops working if you do.
Who we share it with
Only the processors below, each for the single purpose listed. We do not sell your data and we do not share it with data brokers. We do tell Meta when a purchase is made, so that we can tell which adverts work — what that consists of is set out in the table.
We also record how this site is used, through Microsoft Clarity: the screens as they appeared to you, where you tapped, how far you scrolled and where the pointer went. It is how we find the question that stops people and the button that does not work on a particular phone. Microsoft receives those recordings and is a controller of them in its own right, which means it may also use them for its own purposes, including advertising. We do not pay it and we cannot delete one recording on its own — see how long it is kept, below.
| Processor | What it receives | Why |
|---|---|---|
| Stripe Stripe, Inc. (US) |
Your card details, entered directly into its own fields, and the country your card is registered in | Takes the payment for us, and works out the tax on it |
| RevenueCat RevenueCat, Inc. (US) |
Your email address, the plan you chose, and your random session identifier. Also the IP address you view the plans from, which it passes back to us for the advertising match below | Runs the subscription for us, emails your receipts and the link you cancel from, and connects the purchase to your app install |
| Amplitude Amplitude, Inc. (US) |
Screen and choice events, with measurements as ranges | Product analytics: where the flow loses people |
| Meta Meta Platforms Ireland Limited (Ireland) |
Which steps of this page you reached, and the amount and currency of a purchase, against the advertising cookies above and your random session identifier. Meta's own automatic collection also reports the text of buttons you tap, which on this page includes the answers you choose. From the step after you enter it, and when you buy, your email address goes to Meta deliberately as well, as a hash, so that Meta can recognise an account that already holds the same address. When you buy, our server also sends the IP address you viewed the plans from, so the purchase can be matched | Measuring which adverts lead to a purchase |
| Microsoft Clarity Microsoft Corporation (US); for visitors in the EEA, Microsoft Ireland Operations Limited |
A recording of your visit — the screens as they appeared to you, which can include the answers showing on them — together with your taps, scrolling and pointer movement, and the cookies above | Seeing where this site gets in your way |
| Supabase Supabase, Inc. (US) |
Your answers, against the random identifier | Holds them until your app collects them, so you are not asked twice |
| Vercel | Standard server logs, including your IP address | Serving this website and protecting it from abuse |
Some of these are outside the country you live in. Where personal data is transferred out of the UK or EEA, it is done under the transfer safeguards the processor maintains, such as Standard Contractual Clauses.
How long it is kept
| What | How long |
|---|---|
| Your answers, waiting for your app | Deleted the moment your app collects them. If it never does, deleted automatically after 90 days. |
| Data stored in your browser | 7 days, or 180 days after a purchase |
| Analytics events | For as long as the analytics account retains them |
| Advertising measurement data | Kept by Meta under its own retention policy |
| Session recordings | 30 days, on Microsoft's schedule; the heat maps and click counts built from them, up to 9 months. Microsoft's tool cannot delete a single recording, so if you ask us to erase one we can only stop recording and delete the whole project, which is what we will do if you ask. |
| Payment and billing records | Kept by us, and by the providers above, for as long as tax and accounting law requires. A refund does not delete them — we still have to be able to show the tax authority what was charged and returned. |
Why we are allowed to use it
- To provide what you bought — performing our contract with you. This covers your answers and your purchase.
- To improve the service — our legitimate interest in understanding where the flow fails. This covers the usage records, which carry no name or contact detail.
- To meet legal obligations — tax and accounting records.
Your rights
Depending on where you live, you can ask us for a copy of your data, to correct it, to delete it, to restrict or object to how we use it, or to receive it in a portable form. You can also withdraw consent where we relied on it.
Email support+dual@lenalabs.ai. If you bought a subscription, write from the address you bought with and we will find it. If you only answered the questions and did not buy, there is no name or email on that record for us to search — and if you never opened the checkout, the address you typed stayed in your browser and never reached us — send us the unlock link or the identifier from your browser, or clear your browser data and it goes on its own.
If you are in the UK or EEA and think we have handled your data badly, you can complain to your national data protection authority.
Children
This site is not intended for anyone under 18 and we do not knowingly collect data from children. If you believe a child has used it, email us and we will delete what we hold.
Changes
If we change this notice we will update the date at the top. The version in force is the one published here when you use the site.
Contact
Nexa Labs, LLC
30 North Gould Street, Ste N, Sheridan, WY 82801, United States
support+dual@lenalabs.ai