1. Who is responsible for your data?
DFrame is the controller for the personal data described in this policy. You can contact us at info@dframe.nl.
2. Data we may process
Website and contact
When you visit the website or contact us, we may process technical request data, your name, email address, company, Revit version, workflow details you choose to provide and the contents of your message. The public website currently does not use advertising trackers or behavioural marketing analytics.
Beta registration and licensing
To manage controlled beta access and protect licensed use, DFrame may process your name, email address, company, intended workflow, beta group or waiting-list position, licence key, machine fingerprint, activation records, IP address, user agent, Revit version and DFrame version. DFrame Beta requests no payment-card or billing data.
Support and issue reports
Logs, system information, screenshots or project-related attachments are only received when you choose to submit them for support. Please remove confidential project information that is not needed to investigate your request.
Product telemetry
DFrame keeps diagnostic events locally and sends a small, fixed beta usage event to Azure for stability and product analysis. The central event contains a random event identifier, event and module name, DFrame and Revit versions, UTC time, optional duration and outcome. It does not accept a name, email address, machine identifier, document, project, file path or arbitrary properties. When you deliberately submit feedback, the release version, beta phase and released module list may also accompany the report.
3. Why we use personal data
- To process access requests, provide downloads and answer enquiries.
- To create, activate, validate and secure DFrame licences.
- To manage beta groups, capacity and the waiting list.
- To request, receive and follow up on beta feedback.
- To prevent abuse, fraud and unauthorised access.
- To maintain the reliability and security of our services.
- To meet legal, tax and accounting obligations.
Depending on the situation, processing is based on performance of a contract, steps requested before entering a contract, a legal obligation, legitimate interests in operating and protecting DFrame, or your consent where consent is required.
4. Service providers and international processing
DFrame uses carefully selected service providers, including Microsoft Azure for licensing infrastructure and operational monitoring, the email provider for beta communication, and the website hosting provider for delivering this website. No payment processor receives beta registration data because payment is disabled during beta.
Some providers may process data outside the European Economic Area. Where required, appropriate transfer safeguards are used, such as an adequacy decision or approved contractual clauses.
5. Retention
We keep personal data only for as long as necessary for the purpose for which it was collected, to provide and secure an active licence, to handle disputes and support requests, and to meet applicable legal obligations. Waiting-list information is removed when it is no longer needed for beta admission. Security records may be retained for a limited period proportionate to preventing abuse. When data is no longer required, it is deleted or anonymised.
6. Your rights
Subject to the General Data Protection Regulation, you may have the right to access, correct, erase or restrict your personal data, object to certain processing, receive portable data and withdraw consent. You can submit a request through info@dframe.nl. We may need to verify your identity before completing a request.
You may also lodge a complaint with the Dutch Data Protection Authority or the competent supervisory authority in your country.
7. Security and changes
DFrame uses technical and organisational measures designed to protect personal data, including encrypted connections, restricted access, managed secrets and signed licensing data. No system can guarantee absolute security.
This policy may be updated when the product, providers or legal requirements change. Material changes will be identified by a new last-updated date.