This policy explains what information VDZ collects about you, why, and who sees it. It goes with our Terms of Service.
1The short version
- Your projects stay on your computer. VDZ doesn't upload your projects, drawings, libraries or results to us.
- We collect what we need to run your account and licence: who you are, which organisation you belong to, which computers you use VDZ on, and whether your licence is paid.
- Crash reports and usage statistics are off unless you turn them on in the desktop application.
- We don't sell your information, show advertising, or put analytics or advertising trackers on this website.
- Stripe handles your card. We never see or store your full card number.
2Who we are and what this covers
VDZ is provided by Zero Cross Pty Ltd (we, us). This policy covers the VDZ desktop application, this account website and the licensing service behind them. We handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth).
If you use VDZ through your employer or another organisation, that organisation also decides how your account is used and has its own privacy practices, which this policy doesn't cover.
3What we collect
Your account
- Your name and email address, and whether you've verified the address.
- Your password, if you sign in with one. It's stored only in a scrambled (hashed) form that we can't read.
- When you signed up and last signed in, and for each sign-in the network (IP) address and the browser and operating system it came from.
- What you told us when you signed up: whether VDZ is for you or a team, and roughly how many people.
- Which version of our Terms of Service you agreed to, and when.
Your organisation
- The organisation's name and sign-in link, who belongs to it, each person's role and how they joined.
- Invitations: the email address invited, who invited them and when.
- Single sign-on: the identity provider's settings and the email domain. When you sign in through your organisation, its identity provider tells us your name and email address.
- Directory sync, if your organisation turns it on: the names, email addresses and active status of the people it assigns to VDZ, and the names and members of the groups it sends.
- Who has been given access to the organisation's licence, and who made each change.
Licences and computers
- Your licences: their type, standing, end date and number of seats, and who holds each seat.
- Each computer VDZ is activated on: the computer's name, its operating system, the date it was activated, whose it is, and a fingerprint. The fingerprint is a one-way code (a SHA-256 hash) calculated from the identifier the operating system gives the computer. It lets us count computers against a licence and stop a free trial being repeated on the same computer.
- A record that an email address and a computer have had a free trial.
Payments
When you buy, Stripe collects your payment card details, billing name and address, and any tax ID. We don't receive your full card number. We keep the identifiers that link your account to your Stripe customer and subscription, the state of your subscription, and a log of the payment events Stripe sends us.
Support and administration
- The emails and other messages you send us.
- A log of every change our staff make to an account or licence: who made it, what it was and why.
Technical records
- Request logs kept by our hosting provider, which include network addresses and can include the email address an email was sent to.
- Error reports from the licensing service when something goes wrong. These hold the error and where in our code it happened. We've set them up to leave out who you are, cookies, request headers and contents, and anything after the “?” in a web address.
We collect most of this from you directly, or from the desktop application when you sign in. Some comes from your organisation's admins, its identity provider or its directory, and some from Stripe.
4The desktop application
Your work
Projects, drawings, libraries, imported files and calculation results are stored on your computer, or wherever you save them. VDZ doesn't send them to us.
Licensing
To sign in, the desktop application opens this website in your browser. It then sends the licensing service the computer's name, operating system and fingerprint to activate the computer, and checks in again about once a day while you're online to keep the licence current. A computer set up with an offline licence file doesn't check in.
Crash reports (off unless you agree)
VDZ asks whether you want to send crash reports, and sends none unless you say yes. You can change your answer in Preferences → Privacy; turning them off takes effect at once. Reports go to Sentry and carry:
- what went wrong and where in VDZ's code, VDZ's version, and the kind of operating system
- a random ID for the installation, created only when you agree and deleted when you turn reports off. It isn't linked to your account.
Before a report leaves your computer, VDZ removes file and folder paths, the names of project files, your user name and the computer's name. One kind of report can't be cleaned this way: when VDZ crashes outright, the report includes a copy of part of VDZ's memory at that moment, which can contain data from the project you had open. Leave crash reports off if that isn't acceptable for your work.
Usage statistics (off unless you turn them on)
You can turn on Preferences → Privacy → Send usage statistics to help us see which parts of VDZ are used. Turning it off stops them at once. They go to PostHog and are designed to say what VDZ is used for, not who used it:
- Sent: which commands and features are used; whether opening, saving, importing, exporting and calculating succeeded or failed; sizes and times as ranges (for example “11 to 50 cables” or “1 to 10 minutes”), never exact figures; which settings were changed, never their values; VDZ's version and edition; the operating system and its major version; and the processor type.
- Never sent: your name, email address, account, licence or computer name; project names, paths, contents, library names, results or error messages.
- A random ID for the installation links one installation's events over time. It's separate from the crash report ID and from your account, it's deleted when you turn statistics off, and a new one is made if you turn them on again.
- PostHog receives your network address, as any server does, but is set not to store it, and no location is looked up from it. No profile of you is built.
Where few people use a particular kind of computer, the kind of computer and the timing of events could still narrow down who sent them.
Demo editions
The first time a demo edition starts, it reads the current date from well-known public websites (operated by Microsoft, Cloudflare and Google) so the demo period can't be changed by resetting the computer's clock. Those sites see your network address, as they would if you visited them. The demo keeps a record of its start date on your computer.
6How we use it
- To create and secure your account, and sign you in.
- To issue licences, count seats and computers, and stop free trials being repeated.
- To take payment, send invoices and receipts, and deal with overdue or disputed payments.
- To send you emails about your account: verifying your address, resetting your password, invitations to an organisation, and billing. If we send you news about VDZ, you can unsubscribe at any time.
- To answer your questions and give support.
- To find and fix faults, protect VDZ against misuse, and improve it.
- To meet our legal obligations, such as keeping tax records.
8Information held outside Australia
Our database is in Australia, but some of the companies in the table above handle information in other countries, mainly the United States and the European Union. We choose providers that commit to protecting personal information, and send them only what they need for the job they do for us.
9How long we keep it
- Account, organisation and licence records: while your account is open. When you ask us to close it, we delete or de-identify them, apart from what is listed below.
- Free trial records: we keep the record that an email address and a computer have had a trial, so a trial can't be repeated.
- Billing records and our staff's change log: for as long as tax and other laws require, and as long as we need them to deal with disputes.
- Sign-in sessions: until they expire or you sign out.
- Usage statistics: 90 days, then deleted.
- Error reports and crash reports: for as long as we need them to find and fix the fault they describe.
- Request logs: for a limited time set by our hosting provider, then deleted.
10How we protect it
Connections to this website and the licensing service are encrypted. Passwords, and the codes that keep desktop applications and directories signed in, are stored only in hashed form. Licence keys aren't kept in our database. Only staff who need access have it, and what they change is logged. Sign-in attempts are rate-limited.
No system is perfectly secure. If a data breach is likely to cause you serious harm, we'll tell you and the Office of the Australian Information Commissioner, as the law requires.
11Your choices and rights
- See or correct your information. Your account page shows your licences and computers. For anything else, or to correct something, email us.
- Remove a computer. You can remove your own computers from your account page.
- Close your account. Email us and we'll close it and delete your information, apart from what we need to keep (see How long we keep it).
- Crash reports and usage statistics. Turn them on or off at any time in the desktop application under Preferences → Privacy.
If your account is managed by your organisation, its admins control your membership and access, so you may need to ask them first. If the law where you live gives you further rights over your information, we'll honour them.
To make a request, email admin@zerocross.com.au. We may need to confirm who you are, and we'll answer within 30 days.
12Complaints
If you think we've mishandled your information, email admin@zerocross.com.au and tell us what happened. We'll look into it and reply within 30 days. If you're not satisfied with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
13Changes to this policy
We'll update this policy when what we collect or who we share it with changes, and change the date at the top. If a change matters to you, we'll tell you by email or on your account page before it takes effect.
14Contact us
Zero Cross Pty Ltd
admin@zerocross.com.au