Privacy Policy

1. Data controller

ConfigUX is operated by ConfigUX ApS, CVR 46791657, Ndr Strandvej 36, 2791 Dragør, Denmark. For privacy questions, email info@configux.com.

2. Data we process

Depending on how you use the site or ConfigUX Cloud, we may process:

• Contact and company details submitted through forms, demo booking or support.
• Information about your product, platform, selected plan or scoped 360 Service project.
• Customer-owned product data, configuration rules, media and files uploaded to a workspace or project form.
• Configuration responses, lead details or other end-user data that a business customer chooses to collect through a published ConfigUX Player.
• Booking information, time zone and meeting details.
• Order, account and billing information after a subscription or service order is activated.
• The page address, UTM campaign parameters and consent state connected to a request you submit.
• Advertising click identifiers from LinkedIn, Google or Meta only after Marketing consent.
• Technical security logs and, after Analytics consent, website and server-confirmed conversion events.
• Chat messages if the ConfigUX assistant is enabled and you choose to use it.

The Model Planner analyses uploaded 3D files in your browser. Files are not intentionally uploaded to ConfigUX unless you separately submit or import them through a clearly labelled action.

3. ConfigUX Account, trials and subscriptions

When you create or use a ConfigUX Account, we may process your email address, name, company, workspace, selected plan, licence or subscription status and the technical information needed to secure and administer the account.

Starting the free access offer shown at the time records its start, any expiry, publication usage and the configurators connected to the workspace. Published Player access is evaluated against the current trial or subscription status. Payment and billing information is processed only when you separately accept a paid transaction through the provider and flow shown at that time.

We use account and trial data to provide the requested service, enforce plan limits, secure the workspace, deliver support and document the commercial status. Optional marketing still requires a separate voluntary choice.

4. Our role for customer and end-user data

ConfigUX is the controller for personal data used to operate our own website, business accounts, billing, sales, security and support.

When a business customer uses ConfigUX to collect or process personal data about its customers, prospects or other end users, the business customer is normally the controller and ConfigUX acts as processor on its documented instructions. This processing is governed by the applicable data processing agreement.

The business customer is responsible for providing its own end users with the required privacy information, establishing a lawful basis and configuring appropriate retention, access and deletion rules for the data it chooses to collect through ConfigUX.

5. Campaign and conversion measurement

Analytics and Marketing technologies are optional. ConfigUX uses Basic Consent Mode: optional tags are held back until the matching category is granted. Analytics consent can enable ConfigUX Insights, Google Analytics 4 and Microsoft Clarity. Marketing consent can enable LinkedIn Insight Tag, Meta Pixel and approved Google advertising tags.

A form or booking creates a conversion event only after the server confirms that the request was saved. Client-side conversion events contain technical fields such as a random event ID, event name, lead type and internal priority points. They do not contain your name, email address, telephone number, message or other form answers. For the first LinkedIn setup, only selected high-intent actions are eligible for the LinkedIn conversion signal.

Your request remains stored in the ConfigUX form or booking system even if optional tracking is rejected, because this is necessary to answer the action you asked us to take. Advertising click identifiers are removed from stored attribution unless Marketing consent is granted.

6. Purposes and legal bases

Processing performed for a business customer’s own end users follows the customer’s documented instructions and the applicable data processing agreement. You can withdraw optional consent at any time through Cookie settings in the footer. Withdrawal does not affect processing that occurred before withdrawal.

7. Service providers and transfers

We use service providers where they are needed to run the website, account, Cloud service or consented measurement. Depending on the feature and consent categories used, these may include:

• Hostinger for website and database hosting.
• Cloud infrastructure, authentication, database and object-storage providers used to operate ConfigUX Account, Cloud and published Players.
• Microsoft 365, Outlook and Teams for business email, calendar and demo scheduling.
• Google Workspace for retained mail data and files during the controlled transition period.
• Google Tag Manager, Google Analytics and Google Ads for consented analytics and campaign measurement.
• LinkedIn for consented LinkedIn campaign measurement and audiences.
• Meta for consented Facebook and Instagram campaign measurement and audiences.
• Microsoft Clarity for consented website usability analytics.
• A payment and billing provider when a paid ConfigUX transaction is activated.
• OpenAI for the optional ConfigUX assistant if it is enabled and used.

The applicable account or purchase flow identifies the provider used for a paid transaction before payment details are submitted. Some providers may process data outside the EU/EEA. Where required, we rely on an adequacy decision, approved standard contractual clauses or another valid transfer mechanism. Contact info@configux.com to request more information about relevant providers or safeguards.

8. Retention

We keep personal data only for as long as needed for the stated purpose:

• Account, workspace, trial and subscription records: for the active relationship and a reasonable period afterwards, subject to deletion, security and legal requirements.
• Personal data processed for a business customer: according to the customer agreement, data processing agreement and the customer’s documented retention instructions.
• Historical release-notification sign-ups: no more than 12 months after the final relevant notification, unless withdrawn earlier.
• Website enquiries and demo requests that do not become active customer records: normally up to 180 days after submission.
• Support and active customer records: for the customer relationship and a reasonable period afterwards.
• Optional ConfigUX analytics events: normally up to 90 days unless a shorter period is configured.
• Consent records: normally up to 180 days.
• Provider cookies and advertising identifiers: according to the durations listed in the Cookie Policy and the provider configuration.
• Accounting and transaction records: for the period required by Danish law.
• Uploaded project files: until the enquiry or project is resolved, then deleted or moved into the agreed customer project storage.

Automated retention checks may apply to website forms and other operational records. We may retain limited records longer where necessary to establish, exercise or defend legal claims.

9. Security

We use role-based access, updates, backups, encrypted connections on the live site and restricted handling of credentials. Do not submit passwords, private API keys or unnecessary sensitive personal data through public forms.

10. Your rights

Subject to applicable law, you may request access, correction, deletion, restriction, data portability or object to certain processing. You may also withdraw consent. Contact us at info@configux.com. You may complain to the Danish Data Protection Agency or your local supervisory authority. Requests about personal data controlled by a ConfigUX business customer should normally be directed to that customer first.

11. Changes

We update this policy when the website, Cloud service, provider setup or legal requirements change. The current version and update date are published on this page.

12. Contact