Privacy Policy

Data controller: NZ Innovations LLC. We are the controller of the personal data described in this policy, which covers the NZCAM website, your account and theNZCAM desktop application. Privacy questions and requests go to [email protected].

1. The core commitment: your media stays on your device

NZCAM's face swap and voice change processing happens 100% locally on your own computer. Your source photos, video files, and voice recordings are never uploaded to our servers, never stored by us, and never used to train any model. The desktop application connects to our servers to register your device, sign you in, keep your session licensed, deliver updates and, to ensure you enjoy the best experience, share the technical and usage information described in section 2.

Optional cloud-powered features. Some NZCAM features are clearly labeled as cloud-powered (for example, live AI effects). These are the one exception to local-only processing: when you choose to turn one on, the video or audio needed for that feature (and, for a cloud voice, the voice sample you choose) is streamed in real time to our AI processing partners for the duration of that session, transformed, and streamed back to you. It is used only to create your live result; we do not store it or use it to train models. When a cloud voice learns your sample, the voice model it makes is delivered to your computer and kept there, and it joins each cloud voice session only for as long as that session runs. Core face swap and voice clone stay 100% local as described above, and you are always told which features are cloud-powered before you enable them.

2. Data we do collect (website and account)

Running the NZCAM website and account system does require some data:

• Account data: your username, email address, and a hashed password (or your Google/GitHub account identifier if you use social login).
• Billing data: handled by our payment processors, Stripe (cards) and, where bank transfer is offered, Flutterwave. Your card details are entered on the processor's own secure payment page; they never pass through or are stored on our systems. We receive your purchase status, the amount and currency charged, the transaction reference and, if you pay by card, a token for the card, but never your full card number, your bank login, or your PIN. If you set up Auto top-up we store that token so we can charge the amount you chose. We are not currently accepting new bank direct debit mandates; for an existing one we store the mandate reference your bank issued, together with the limits you approved (maximum amount per charge, and expiry date) — not your account credentials.
• Device and connection data: to ensure you enjoy the best experience, the desktop app shares technical information about your device and connection with us, such as a device identifier, its hardware and software details, network information and your approximate location. This helps us keep NZCAM running smoothly on your machine, offer the right service for your region, run the app on one machine at a time, support you, and keep your account safe. A device is recorded once and kept even if you uninstall, so a reinstall resumes where it left off.
• Usage data:how the app's features are used, such as how long they run, so your credits and billing stay accurate and we can keep improving NZCAM. On the website we use cookieless, aggregate analytics (see Section 6), with no personal data and no cross-site tracking.
• Diagnostic data:when something goes wrong in the desktop app (an error, a crash, or a camera it cannot use), the app sends us a short report so we can fix it, often before you notice: the app and Windows versions, what went wrong, and the most recent part of the app's own log. Before a report leaves your computer, the app removes your Windows user name, your computer's name, email addresses and sign-in details from it. When you contact support, we may ask your app for its full logs, which it sends once. Reports never contain your photos, videos, voice, or the contents of your files.
• Contact/support data: the name, email address and message you send us via the contact form, together with the IP address it was sent from (kept with the message to filter abuse).

3. How we use this data

To give you the best experience: to operate your account, keep NZCAMfast and reliable on your device and in your region, find and fix problems in the app, keep your credits and billing accurate, process credit and plan payments, run auto top-up if you turn it on, enforce one signed-in device at a time, provide support, protect the app against tampering and redistribution, measure whether our advertising leads to purchases (section 6), and send the transactional emails needed to run your account (sign-in codes, password resets). Any payment receipt you receive comes fromour payment processor, not from us.

4. Why we are allowed to use it (legal bases)

Where the UK/EU GDPR or a similar data-protection law applies to you, we rely on these bases:

• Performance of a contract — creating and running your account, taking payment, delivering credits, licensing your device, and providing support.
• Legitimate interests — delivering a reliable service suited to your device and region, finding and fixing problems in the app, keeping the service secure, preventing fraud, piracy and abuse, enforcing one signed-in device at a time, understanding aggregate website usage, and measuring whether our advertising leads to purchases (the server-side purchase report in section 6). We rely on this only where it does not override your rights, and you can object under section 11.
• Legal obligation — tax, accounting, and responding to lawful requests.
• Consent — where we ask for it, such as enabling a cloud-powered feature or setting up a payment mandate. You can withdraw consent at any time; that stops future processing but does not undo what was lawful beforehand.

5. Face and voice data

This deserves its own section, because NZCAM is a face and voice tool and you should not have to infer the answer.

We do not collect, receive, store or derive biometric identifiers. The face and voice models run on your computer. No faceprint, voiceprint, face embedding or similar template is sent to us or stored by us, and we do not use your face or voice to identify you, to authenticate you, or to build any recognition database. The one labelled exception is a cloud-powered feature you turn on yourself, where the live video or audio it needs passes to our AI processing partners to create your result, as described in section 1.

Because that media stays on your device, it is yours to manage: source photos, recordings and output live in the folders you chose, and deleting them there deletes them. We have no copy to delete.

6. Analytics and advertising measurement

Our website analytics are cookieless and privacy-respecting: a self-hosted instance of Plausible, run by us, with the page-view events relayed through our own domain. They identify nobody, collect no personal data, and run for every visitor.

Advertising measurement, only with your consent.We advertise on TikTok, and where you allow marketing cookies we load the TikTok Pixel to learn whether an ad led to a visit, a signup or a purchase. It sets a cookie, reads TikTok's click identifier from the link you arrived on, and shares your IP address and browser user-agent with TikTok, who may combine that with data they already hold. If you sign up or buy while it is loaded, it also receives a one-way hash of your email address and account id so TikTok can match the conversion to the ad — never the email itself. How consent works depends on where you are: in the EEA, the UK and Switzerland nothing loads until you accept the banner, and declining or ignoring it means the pixel never loads; elsewhere it loads unless you switch it off on our Cookie Policy page, which is also where anyone can withdraw consent.

Separately from the pixel, after a completed purchase we report that purchase to TikTok's server-side Events API: a one-way hash of your email address and account id, the item bought and the amount in US dollars — no cookies, no IP address and no device identifiers. Its only purpose is to let TikTok match a sale to the ad that led to it. This report does not depend on the cookie banner: we make it on legitimate interest (section 4), and you can object to it under section 11. Automatic top-ups are not reported.

7. Data sharing

We share data only with the service providers needed to run the business: Stripe (card payments, and any refund we issue), Flutterwave (bank-transfer payments, where offered) , TikTok (advertising measurement: the pixel where marketing cookies are allowed, and the server-side purchase report described in section 6), Supabase (our database, account authentication and transactional email), FormSubmit (formsubmit.co, which relays a contact-form message to our inbox only when JavaScript is off in your browser or our own endpoint is unavailable), Cloudflare (network security and routing in front of the site, which sees the address of every request), our hosting provider, and, only when you use a cloud-powered AI feature, the real-time AI processing partners that power it (which receive the live video or audio needed to create your result). Each is bound to use the data only to provide its service to us.

We may also disclose data where we are legally required to — to comply with a valid legal process, to enforce our Terms and Acceptable Use Policy, to prevent fraud or abuse, or to protect someone's safety. If our business is ever sold or merged, account data may transfer with it, and this policy continues to apply until you are told otherwise.

We do not sell your personal data. We have never done so, and we never will.

Where marketing cookies are allowed (section 6), the TikTok Pixel shares limited data with TikTok for advertising measurement, which California law classifies as "sharing for cross-context behavioural advertising". Switching it off on the Cookie Policy page stops the pixel entirely. The server-side purchase report in section 6 is separate from the pixel; you can object to it under section 11.

8. Where your data goes (international transfers)

We are based in the United States, and the providers we use operate internationally, so account and billing data may be processed outside your country — including in the European Union and the United States. Where we transfer personal data out of the EEA or the UK we rely on an adequacy decision, or on Standard Contractual Clauses with the recipient, together with contractual confidentiality and security commitments.

You can ask us which providers hold what, and on what basis, using the contact details below.

9. How we protect it

Data is encrypted in transit. Passwords are hashed, never stored in a readable form, and we cannot see them. Locally stored licence and session files on your device are encrypted and bound to that machine, so copying them elsewhere does not carry your account with them. Access to production data is limited to the people who need it. We use a managed database provider with row-level access rules, so one account cannot read another's data.

Cardholders.We undertake to keep the information of everyone who pays on this site secure and not to violate their privacy. Card details are collected only on our payment processor's own page; we never store a full card number, and we use what we do receive (purchase status, amount, reference, and a token) solely to deliver what you bought, to run any Auto top-up you turned on, and to handle refunds and disputes.

No system is perfectly secure, and we will not claim otherwise. Please use a strong, unique password and keep your sign-in code private.

10. Data breaches

If a breach affects your personal data and is likely to result in a risk to your rights, we will notify the regulator required by applicable law within the time it requires, and tell affected users directly, describing what happened, what data was involved, and what to do about it.

11. Your rights

You can access, update, or delete your account data by contacting us. Where a data-protection law applicable to you grants these rights, you possess specific and enforceable rights regarding your personal data. You have the right to request access to the personal data we hold about you and receive it in a commonly used format. You possess the right to request the rectification of any inaccurate, out-of-date, or incomplete data. You may request the erasure of your personal data where it is no longer necessary for the purposes collected or where you have withdrawn your consent. Furthermore, you hold the right to restrict the processing of your data, the right to object to data processing (particularly for direct marketing or where based on legitimate interests), and the right to data portability. You also maintain the right not to be subject to a decision based solely on automated processing, including profiling, which produces legal or similarly significant effects. To exercise any of these rights, please contact us. If you believe your statutory data privacy rights have been violated, you have the right to lodge a formal complaint with your local data protection authority.

12. Data retention

We keep account and billing data for as long as your account is active, plus a reasonable period afterward for legal and accounting purposes — for payment records, that is the period our tax and accounting obligations require. Device records are retained so a returning machine resumes its prior status; other technical and usage information is kept only as long as it is useful for the purposes in section 3. Diagnostic reports are kept for 90 days. Support messages are kept while they are useful for handling your issue and any follow-up. When a retention period ends, we delete the data or irreversibly anonymise it.

Deleting your account removes your profile, credentials and wallet balance. We may retain the minimum needed for a legal obligation, to resolve a dispute, or to keep an abuse or fraud record effective — because an account terminated under section 4 of our Acceptable Use Policy must not be trivially re-created.

13. Automated decisions

We do not make decisions about you by automated means alone that produce legal or similarly significant effects, and we do not profile you for advertising. Automated signals can flag an account for review — for example, suspected payment fraud or licence tampering — but a person reviews the case before an account is terminated, and you can appeal as described in our Acceptable Use Policy.

14. Children

NZCAM is an 18+ product. It is not directed at children, we do not knowingly collect data from anyone under 18, and accounts we find to belong to a minor are closed and their data deleted. If you believe a child has given us personal data, contact us and we will remove it.

15. If you are in the EEA or the UK

The rights in section 11 apply to you under the UK/EU GDPR, on the legal bases set out in section 4, with transfers handled as described in section 8. You may lodge a complaint with your local supervisory authority — in the UK, the Information Commissioner's Office — as well as with us. We would rather hear from you first.

16. If you are in California

You may request the categories and specific pieces of personal information we have collected, the sources, the purpose, and the categories of third parties we disclosed it to; request deletion; request correction; and you will not be treated differently for exercising any of these rights. We do not sell personal information. The categories we collect are listed in section 2.

We share data for cross-context behavioural advertising in two ways, both described in section 6: the TikTok Pixel, only where marketing cookies are allowed, and a server-side report of completed purchases. You can opt out of the pixel at any time with the switch on our Cookie Policy page; it takes effect immediately in that browser. To opt out of the purchase report, contact us (section 18).

17. Changes to this policy

We'll update the "Last updated" date above whenever we make material changes, and for changes that materially affect how we use your data we will give notice as described in our Terms of Service.