MDMSDEALER MANAGEMENT SYSTEM
Legal

Privacy Policy

Last updated: 7 November 2026

This document is provided for information and does not constitute legal advice.

1. About this policy

This Privacy Policy explains how Modern DMS ("MDMS", "we", "us", "our"), based in Queensland, Australia, handles personal information in connection with the Modern Dealer Management System website and software-as-a-service platform (the "Service").

We are bound by the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Where we handle health, tax file number, or other sensitive information on behalf of a customer, we do so only as permitted by law and by our agreement with that customer.

2. Information we collect

  • Account information — name, business name, email, phone, role, and authentication identifiers.
  • Customer Data — records you upload into the Service (customers, equipment, parts, invoices, quotes, work orders, etc.). You control this data; we process it on your behalf.
  • Billing information — ABN, billing address, plan, invoices. Card details are handled by our payment processor and not stored by us.
  • Technical and usage data — IP address, device and browser data, log files, pages visited, feature usage.
  • Diagnostic error logs — automatic technical records of faults you encounter in the Service, scrubbed of contact and financial identifiers before storage. See section 7.
  • Trial usage monitoring — during a free trial only, additional records of pages visited and data exports/downloads, each with IP address and device, used to prevent trial abuse. See section 8.
  • Communications — support tickets, sales enquiries, survey responses.
  • Website chat messages — everything you type into the chat assistant on our website, the page you were on, and a scrambled (hashed) form of your IP address used to limit abuse, plus the name, email and company if you choose to give them.
  • Demo video requests — name, work email, company, role, optional phone and team details, the videos we sent you, and which videos you open, start and finish, kept against your personal link. We also keep a scrambled (hashed) form of your IP address and the time you agreed, as proof of consent.
  • Cookies and similar technologies — see our Cookie Policy.

3. How we collect it

We collect information directly from you when you sign up, use the Service, request our demo videos, or contact us; automatically through your use of the Service; and occasionally from third parties such as identity providers, referrers, or publicly available sources.

4. Why we use it (APP 6)

  • Provide, maintain and improve the Service.
  • Authenticate users and secure accounts.
  • Process billing and manage subscriptions.
  • Provide support and respond to enquiries.
  • Send service notices and, with consent, product updates and marketing.
  • Where you give us a phone number with a demo request, we may call you about that request.
  • Send demo videos you ask for, follow up by email (at most two emails in 14 days), and see which videos are watched so we can answer the right questions.
  • Detect and prevent fraud, misuse and security incidents.
  • Comply with legal obligations and enforce our terms.

5. Disclosure to third parties (APP 6 & APP 8)

We disclose personal information to trusted sub-processors who help us run the Service, including cloud hosting, database, email delivery, analytics and customer-support providers. We require them to handle information consistently with this policy. Our current list is at moderndms.com.au/sub-processors, and a business that needs a Data Processing Agreement can ask for one there.

We use Stripe, Inc. ("Stripe") to process payments and manage subscriptions. When you make a purchase, billing and payment information you provide at checkout is collected and processed by Stripe as an independent data controller in accordance with Stripe's Privacy Policy. We do not store full payment card details.

The database that holds the information you and your business enter into the Service is hosted by Supabase, Inc. in Sydney, Australia (AWS region ap-southeast-2).

Some of these providers operate, or process data, outside Australia (for example in the United States or the European Union). By using the Service you acknowledge that your information may be transferred to and processed in those jurisdictions. We take reasonable steps to ensure overseas recipients handle personal information in a way consistent with the APPs.

Our AI features use Anthropic, PBC and other AI providers named in section 5A. These providers may process information outside Australia, including in the United States, so a dealer using AI features should expect that text sent to the AI may be processed overseas.

We may also disclose information where required or authorised by law, including to law enforcement, regulators, courts or in connection with a sale or restructure of our business.

5A. Artificial intelligence (AI) features

We use AI models in four places. In each, the text sent to the AI provider is processed to produce a reply and is not used by us to train our own models.

MDMS AI (optional add-on inside the Service). When a user asks MDMS AI a question, we send the question and the information needed to answer it, limited to what that user's role is allowed to see, to Anthropic, PBC, whose Claude models write the reply. Before sending, we remove Australian tax file numbers and bank account numbers (BSB and account numbers) by pattern matching, which can miss unusual formats. We do not remove names, email addresses, phone numbers or other business details, so please do not type information into a question that you would not want sent to an AI provider. MDMS AI can look things up. It does not change records on its own: it prepares a change for the user to confirm, and the Service checks the user's role again before saving.

Help assistant and help search. Questions to the help assistant, and the help articles matched to them, may be processed by OpenRouter, a service that routes requests to AI model providers, and by Voyage AI, which matches questions to help articles. Before sending, email addresses, Australian phone numbers and long number strings are replaced with placeholders, and tax file and bank numbers are removed.

Smart import (optional feature inside the Service). When a business uses Smart import to load a spreadsheet or pasted list, we send column names and, for a few values per column, only their shape (for example "AAA-9999" for a part code), never the values themselves, to an AI model through OpenRouter and its model providers to suggest where each column belongs. Email addresses and phone numbers in column names are removed before sending. Where a business has turned on the setting described below, no value shape is sent for columns that appear to hold names, contact, address, bank or identity details. If a user pastes text for the AI to read (parts and machine lists only), that text is sent after email addresses and phone numbers are removed, so please do not paste customer, supplier or staff details; we refuse pasted text for customers and suppliers. The AI only proposes a mapping or rows: nothing is saved until a person reviews the preview and confirms, records are only added (nothing existing is overwritten), and an import can be undone for 7 days, except records changed or used elsewhere since. Provider retention is as described under "Reducing personal information sent to AI providers" below.

Website chat assistant. The chat on our public website is an AI assistant. It points visitors to feature pages, demo booking or the free trial, and can pass a message to our team. Your messages are processed by an AI model through OpenRouter and its model providers, which may keep a copy of requests for a period under their own terms. We store every chat in our database (hosted by Supabase in Sydney), including the page you were on and a hashed form of your IP address. If you give your name and email, we email them and the conversation to our customer support team through Resend so we can reply. Please do not share passwords, payment details or tax file numbers in the chat. Stored chats in our database are deleted after 180 days; copies emailed to our team are kept in our support mailbox until we delete them.

Reducing personal information sent to AI providers. Where a business turns on the matching setting, most of our AI features remove email addresses, phone numbers, street and postal addresses, card numbers, tax file numbers and bank numbers from the text sent to AI providers, and remove fields known to hold contact, address, bank, birth date, pay and location details from lookup results. Staff, leave, pay and commission lookups are not offered to the AI. Two features, card fill and the help-article assistant, use a narrower removal of email addresses, phone numbers, tax file numbers and bank numbers. A second setting replaces customer, contact and staff names in lookup results with stand-ins; the link between a stand-in and the real name is kept on our servers for the conversation and deleted with it. Names a person types, and names inside free-text notes, can still reach the provider, and stand-ins are still personal information. Some of our AI features ask the provider not to keep requests, but we cannot guarantee that they do not; the direct calls to Anthropic have no such arrangement. The business using MDMS is responsible for what its staff type and for telling its own customers and staff about its use of AI.

Overseas processing. These providers (Anthropic, OpenRouter and the model providers it routes to, Voyage AI and Resend) may process information outside Australia, including in the United States and the European Union. We do not promise that AI processing stays in Australia. Section 5 applies.

Accuracy. AI replies can be wrong. Check anything that matters before you act on it. AI features do not provide legal, tax or financial advice.

5B. Implementation portal

When we set up ModernDMS for a business, we may give named people at that business a personal link to a secure setup page. This section covers what that page collects. It is provided by Modern DMS, ABN 32 737 926 202.

What we collect. Your name, work email and role (given to us by your business or by you), the tasks you tick off, the comments you write, the documents you upload, and the name you type if you confirm a project plan. We also record technical details such as when the page was opened and your IP address in scrambled (hashed) form, to keep the page secure. We email a one-time code to your work email to check it is you before you upload, download or confirm anything.

What we do not take through it. Please do not send tax file numbers, bank or card details, identity documents or passwords through the page. You enter those directly into your own ModernDMS, and we will show you how. We cannot promise that the page will detect sensitive information in every file, so please do not rely on it to do so.

Why. We use this information only to set up and support your ModernDMS and to keep a record of what was agreed. We do not use it for marketing.

Where it is stored. Uploaded files and the records above are held in our Supabase database and storage, in Sydney, Australia (section 5). Uploaded files are private and are not publicly accessible. The one-time code email is sent through Resend, which may process it outside Australia (section 5).

How long we keep it. Uploaded files are deleted 90 days after your project closes, or within 7 days if a file is found to contain sensitive information. Records of plan confirmations are kept for longer so that we can show what was confirmed and when.

Your choices. To see or correct what we hold about you, ask us to remove your link, or make a complaint, contact customersupport@moderndms.com.au. Sections 10 and 16 explain how we respond.

5C. Microsoft 365 Outlook mail and calendar

A business can choose to connect ModernDMS to the Microsoft 365 mailboxes and calendars of its own staff. This section covers what that connection does. It is provided by Modern DMS, ABN 32 737 926 202. The business is responsible for the personal information in its staff mailboxes; we handle the limited information below on the business's behalf.

Who decides. Each person connects their own mailbox by signing in to Microsoft and approving ModernDMS. We cannot read any mailbox that has not been connected this way, and we never ask for access to every mailbox in a business. A person can pause or disconnect at any time, and a business administrator can disconnect anyone in their business.

What we keep. We record an email or meeting when it involves an address already in that business's customer, contact or lead records, or when a person chooses to log a message from the Outlook add-in. When a person first connects we look back 90 days for email, and 30 days back and 180 days ahead for meetings. For each item we keep the subject, the sender and recipient addresses (for meetings, the organiser and up to 20 attendee addresses), the date and time, and a link back to the item in Outlook. We do not keep message bodies or attachments. A short text preview is kept only if the business administrator turns previews on, which is off by default, and then only for the number of days the administrator sets (90 unless changed). Drafts, items marked private or personal in Outlook, and items given the "Not for CRM" category are never recorded.

Who can see it. A recorded item appears on the customer, contact or lead it was matched to, so colleagues in the same business with a sales or management role can see it, including the Outlook mailbox owner's name. The business must give its staff written notice before they connect, and the person cannot connect until an administrator has confirmed that notice. The people whose addresses appear in those emails are not told by us, so the business should cover this in its own privacy policy.

Sending and calendar. If a person uses "Send from Outlook", the message is sent from their own mailbox through Microsoft, and appears in their Sent Items. If they add a task to their calendar, an event is created in their own calendar. We only change events that ModernDMS created.

Where it is stored and how it is protected. Records are held in our Supabase database in Sydney, Australia (section 5). The refresh token Microsoft gives us is encrypted before it is stored in a secured vault, is never shown in the app, and is deleted when the person disconnects. Disconnecting does not delete items already recorded, and does not remove ModernDMS from the person's Microsoft account, which they can do in Microsoft. Microsoft processes mail and calendar data under its own terms and privacy statement.

How long we keep it. Recorded items stay on the customer record until the person or an administrator removes them, or the business closes its account (section 9). A removed item is hidden from the CRM and its subject, addresses and link are erased; we keep only a bare marker so that syncing does not add it back. To see, correct or remove what we hold, contact customersupport@moderndms.com.au.

6. Data security

We use industry-standard safeguards including encryption in transit (TLS) and at rest, role-based access controls, audit logging, network segregation, multi-factor authentication for staff, and regular vulnerability scanning. No system is completely secure, and we cannot guarantee absolute security.

7. Diagnostic error logs

When something goes wrong while you are using the Service, we automatically record a technical description of the fault so that we can find and fix it. This is the only purpose for which these records exist.

Identifiers are stripped before the record is stored. Error text is automatically scrubbed — on your device before it is sent to us, and again on our servers before it is written — to remove email addresses, phone numbers, payment card numbers, ABNs, TFNs, street addresses and authentication tokens. These are replaced with placeholders such as [email] and are never stored.

Each record is linked to the user account and business it came from, and keeps technical context such as the screen, the error code and the software build. We need that link to know who is affected and to tell you when a fault is fixed — so these records are treated as personal information under this policy, not as anonymous data.

Because some error messages are written by hand by our software, we cannot promise that an incidental reference to a person is never captured in the text of an error. We do not rely on scrubbing alone: access to these records is restricted to authorised MDMS personnel, and they are never readable from within your account or by any other customer.

We never sell these records and never share them externally. They are not visible to any other customer, are never used for advertising, marketing, profiling, or to train third-party services, and are not sent to any analytics or error-reporting provider. The only parties that hold them are MDMS and the infrastructure providers that host the Service on our behalf (section 5), and the only other circumstance in which we would disclose them is where we are required to by law. They are used solely by MDMS to diagnose faults and improve the Service for the people who use it, and they do not give us a route into your Customer Data.

Diagnostic error records are automatically and permanently deleted 90 days after the error last occurred.

8. Trial usage monitoring

During a free trial, and only during a free trial, we automatically record how the trial account uses the Service — the pages visited, and actions that take data out of the Service such as exports, downloads, generated PDFs, printed labels and opened documents. The purpose is security and the prevention of trial abuse: for example, an account created to systematically copy the Service or to bulk-export data.

Each record includes the IP address and device/browser (user-agent) the action came from, together with the user account and business, the action, and the time. We keep the IP address in full because it is the signal that lets us recognise automated scraping and multiple trial accounts operated from one source.

This monitoring applies only while an account is on a free trial (including an expired trial that has not subscribed). When you subscribe to a paid plan it stops, and we do not apply it to paying customers' everyday use of the Service.

These records are restricted to authorised MDMS personnel and are never readable from within your account or by any other customer. We never sell them, never share them externally, and never use them for advertising, marketing, profiling, or to train third-party services. The only parties that hold them are MDMS and the infrastructure providers that host the Service on our behalf (section 5). Because each record is linked to the user and business it came from, we treat it as personal information under this policy.

Trial usage records are automatically and permanently deleted 90 days after they are created, and are deleted sooner if the trial's data is deleted (section 9).

9. Data retention

We retain Customer Data while your account is active and for a reasonable period afterwards to allow data export and to meet our legal, accounting and tax obligations. After that period we securely delete or de-identify the information unless we are required to retain it by law. Diagnostic error records are deleted on the 90-day cycle described in section 7. Test mode copies follow section 9A.

Demo requests (including video requests): requests that do not become an account are deleted 24 months after the request, together with the watch records for your link. Your link stops working 90 days after it was issued. If you unsubscribe we keep only a scrambled (hashed) form of your email so we do not contact you again.

Free trials that are not converted to a paid subscription: if your trial ends and you do not subscribe, we keep the data from your trial for 60 days after the trial end date, then permanently delete it along with the associated user accounts. We tell you the exact deletion date when your trial ends, and remind you again roughly 14 days and 3 days beforehand. Subscribing at any point before that date keeps your data intact. If you would like a copy of your trial data before it is deleted, contact us at customersupport@moderndms.com.au and we will provide it. This 60-day rule applies only to trials that never became paid subscriptions.

9A. Test mode copies

If you are on a paid plan, your business administrator can turn on Test mode. Test mode creates a separate test copy of your business inside ModernDMS so your team can try features and practise without touching your live records.

What is copied. The copy contains your set-up and master records: for example customers, suppliers, parts, price books, branches and machines, and a test login for each administrator who uses Test mode. It does not contain your invoices, quotes, work orders, payments, accounting records, payroll or employee tax and bank details, files and photos, signatures, or the keys and logins for connected services such as Xero, MYOB, Stripe and Microsoft 365.

Personal details. In the test copy, email addresses, phone numbers, street addresses, ABNs and notes for customers, suppliers and contacts are removed or replaced with made-up values. Business names, machine numbers and part prices are copied as they are.

Why. We create the copy only at your administrator's request, to let you test and train. We do not use it for any other purpose.

Where it is kept. The test copy is stored with the rest of your ModernDMS data in the same region and is protected by the same access controls as your live data.

No real messages or payments. Test mode does not send email, SMS or notifications to anyone, including the administrator. Messages it tries to send are held and listed on screen so your team can see what would have gone out. It does not take or move money and does not write to your accounting software. Documents made in Test mode are marked as test documents.

How long we keep it. A test copy is deleted automatically after 30 days without use, and in any case no later than 90 days after it was created. Your administrator can reset or delete a test copy at any time under Admin, then Test mode. Deletion removes the test records and the test logins. Deleted test copies may remain in our encrypted backups until those backups expire in the ordinary cycle: daily backups are kept for 30 days and monthly backups for 12 months (see section 9).

On-screen guides. Where guides have been switched on for your company, the guide records the step and screen it reached, the software version, and your company and user identifiers, so that we can find and fix problems and improve the service. It does not record anything you type. These records are kept only for that purpose and are deleted with the test copy.

Your live data. Using, resetting or deleting a test copy does not change your live records.

10. Your rights (APPs 12 & 13)

You may request access to, or correction of, personal information we hold about you by contacting customersupport@moderndms.com.au. We will respond within a reasonable time (generally within 30 days) and will not charge for reasonable requests.

11. Direct marketing and the Spam Act

Where we send marketing communications we comply with the Spam Act 2003 (Cth). Every commercial email includes an unsubscribe link, and you can opt out at any time by using it or by contacting us. We stop within five working days, and normally at once. If we ever call you about a demo request we check numbers against the Do Not Call Register first and call only within permitted hours.

12. Notifiable Data Breaches scheme

If we suffer a data breach that is likely to result in serious harm to an individual whose personal information is involved, we will notify the Office of the Australian Information Commissioner (OAIC) and affected individuals as required by Part IIIC of the Privacy Act.

13. Cookies and analytics

We use a small number of essential and analytics cookies. See our Cookie Policy for details. Video watch records are first-party events tied to your personal link; we do not use third-party video trackers or advertising pixels for them.

14. Children

The Service is intended for business users aged 18 and over. We do not knowingly collect personal information from children.

15. Changes to this policy

We may update this policy from time to time. Material changes will be notified through the Service or by email. The "Last updated" date above always reflects the current version.

16. Complaints and contact

If you have a privacy concern, contact us first at customersupport@moderndms.com.au and we will investigate and respond within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au or on 1300 363 992.

Modern DMS
Queensland, Australia
customersupport@moderndms.com.au