Privacy Policy
Effective November 3, 2026
This policy explains what Nukxon, LLC ("Nukxon", "we", "us") collects, why, and what you can do about it. We are the data controller for information about your account, and a data processor for the scene Content you upload.
legal@nukxon.com · Nukxon, LLC, 131 Continental Drive, Suite 305, Newark, DE 19713, USA
1. What we collect
You give us:
- Account details — name, email, password hash, company name if provided.
- Content — the
.nukxonfiles you upload. A.nukxonis a zip archive containing, depending on the kind of project: 3D geometry (Walkable exteriors carry none), the images rendered at each capture point (360° panoramas for interiors, views around an exterior, the frames of an object or of a 4D animation), camera positions and orientations, and any names or labels you gave your cameras, teleports and anchors. It also carries a small block of export metadata: which design software and version you exported from, your render engine, the export timestamp, and a hash of the scene geometry used to detect changes between exports. - Support correspondence — anything you send us.
- Founding-member and waitlist sign-ups — your name, email, and the 3D tool and render engine you use, when you join the founders list or the beta waitlist on nukxon.com. We use them to email you about your spot, the beta and launch offers. Every email has an unsubscribe link.
We collect automatically:
- Usage data — pages viewed, features used, credits used, errors encountered.
- Technical data — IP address, browser and device type, operating system, referring page.
- Cookies — see section 7.
What ends up in a published Project
This matters more than most of this policy, so it is spelled out.
Served in every Project, public or client:
- the images rendered at every capture point
- for interiors, an overhead floor plan generated during processing, including its real-world dimensions in metres
- the names you gave your cameras, teleports and anchors
The 3D geometry differs by link type, and this is the important part:
| Public link | Client link (password) | |
|---|---|---|
| 3D geometry served | a reconstruction built from the capture | your actual model |
| Can your model be obtained from it? | No | Yes, by anyone with the password |
We do this so a public Project cannot be used to extract the model you uploaded — which matters if you work with licensed third-party assets whose terms permit rendering but prohibit redistribution.
Never served, on either link type. The original object names from your model — which often carry client names, project codes or internal shorthand — do not survive our processing. We also strip the export metadata described above. It is retained on our side for support and is not served to viewers.
What you should do about it. Assume the floor plan and every label are visible to anyone who can open the Project. Don't put a client's name in a camera label. Use a public link only for work you are happy to have seen by anyone, and remember that a password on a client link is only as private as the people you give it to.
Our plugins collect nothing
The exporter plugins for Blender, 3ds Max, SketchUp and Unreal Engine send nothing about you or your scene. The only connection any of them makes is the Blender add-on’s update check: once a day, and only while Blender’s Allow Online Access is on, the Blender add-on reads a small file from downloads.nukxon.com to see whether a newer version or a notice is out. Like any web request, it reaches our server with your IP address and the add-on’s version; nothing else is sent. Apart from that, the plugins do not phone home, check licences, send telemetry, or read anything about your machine — no username, no hostname, no hardware identifier, no file paths. They read your scene, render it, and write a .nukxon file to a folder you choose. Nothing leaves your computer until you decide to upload that file.
You can verify this. The Blender extension declares two permissions: files, to write your export, and network, used only for the daily update check described above. It is distributed under GPL-3.0-or-later, so you can read every line of it.
We receive from others:
- Payment status from Dodo Payments: whether a payment succeeded, plan, country and last four digits. We never see or store your full card number.
- Authentication data from our sign-in provider if you use a third-party login.
2. Why we use it, and our legal basis
| Purpose | Legal basis (GDPR) |
|---|---|
| Provide the Service, process your scenes, deliver Projects | Performance of a contract |
| Take payment and prevent fraud | Contract; legitimate interests |
| Support and service notices | Contract; legitimate interests |
| Improve the Service, diagnose failures | Legitimate interests |
| Security, abuse prevention, copyright enforcement | Legitimate interests; legal obligation |
| Founders list and waitlist emails | Consent, withdrawable at any time |
| Marketing emails | Consent, withdrawable at any time |
We do not sell your personal data. We use your Content only to build your projects. We never use it to train AI models or for anyone else.
3. Subprocessors
We use these providers to run the Service. Your data may be processed by them.
| Category of recipient | What it does | Where |
|---|---|---|
| Cloud GPU compute | Processing uploaded scenes into Projects | United States |
| Database hosting | Your account records and Project metadata | United States |
| Object storage and CDN | Storing and delivering your files and Projects | United States / Global |
| Authentication | Sign-in and account security | United States |
| Product analytics | Understanding which features are used | United States |
| Payments — Dodo Payments, our merchant of record | Taking payment, tax, invoicing | United States / Global |
| Business email | Support and service correspondence | Global |
| Email newsletters | The founders list, the beta waitlist and product emails | European Union / Global |
We identify these by category rather than by vendor name, which GDPR Article 13(1)(e) permits ("the recipients or categories of recipients"). Business customers who need the named list for their own compliance records can request our Data Processing Agreement, which identifies every subprocessor individually.
We will give notice before adding a category of subprocessor that materially changes how Content is handled.
4. Sharing
We share personal data only with: the subprocessors above; professional advisers under confidentiality; authorities where legally required; and an acquirer if the business is sold, in which case we will notify you.
Projects you share are shared by you, not by us. A public link is viewable by anyone who has it and is not authenticated — do not put confidential material behind one. A client link is password-protected, but a password is an access control rather than a guarantee: anyone you give it to can pass it on.
5. International transfers
We are US-based, so data is transferred to the United States and other countries. For transfers out of the EEA and UK we rely on Standard Contractual Clauses with our subprocessors, plus supplementary measures where needed.
6. How long we keep it
| Data | Retention |
|---|---|
| Account details | While your account exists, then 90 days |
| Content and Projects | While active. If deactivated for non-payment: 90 days, then permanently deleted |
| Payment records | 7 years (tax and accounting obligations) |
| Server and security logs | 12 months |
| Support correspondence | 3 years |
| Founders list and waitlist | Until you unsubscribe or ask us to delete it |
| Backups | Overwritten on a rolling basis, normally within 35 days |
On a paid plan, you can download the Gaussian splat file for any interior, exterior or object at any time while your account exists, including during the 90-day deactivation window. That file is the reconstructed capture of your space and is yours to keep. The interactive Project is hosted and is not downloadable — if your account is deactivated, Projects stop being viewable even though you keep the splat files. After deletion we cannot recover anything.
7. Cookies
We use:
- Strictly necessary — sign-in and session security. These cannot be switched off.
- Functional — remembering preferences such as viewer quality settings.
- Analytics — understanding which features are used, so we can improve them.
We do not use advertising or cross-site tracking cookies. Where required by law we ask for consent to non-essential cookies before setting them, and you can change your choice at any time.
8. Your rights
Depending where you live you may have the right to:
- access a copy of your personal data
- correct inaccurate data
- delete your data
- restrict or object to certain processing
- portability — receive your data in a machine-readable format
- withdraw consent at any time
- complain to your data protection authority
In practice, most of this is self-service. You can edit your account details, download the Gaussian splat file for any publish, and delete your Content from the product at any time. For anything else email legal@nukxon.com and we will respond within 30 days.
If you are in California, you have rights under the CCPA/CPRA including to know, delete, correct, and to opt out of sale or sharing. We do not sell or share personal information as those terms are defined. We will not discriminate against you for exercising these rights.
9. Security
We use encryption in transit (TLS), access controls, and isolated cloud containers for processing. Uploaded files are validated before processing to reject malformed or hostile input.
No system is perfectly secure. If a breach affects your personal data we will notify you and the relevant authority as required by law.
10. Children
The Service is not for anyone under 18 and we do not knowingly collect data from children. If you believe a child has given us data, email legal@nukxon.com and we will delete it.
11. Changes
We may update this policy. For material changes we will give at least 30 days' notice by email or in the product. The effective date at the top always shows the current version.
