Privacy policy

Last updated 22 November 2026

Success Software Solutions Pty Ltd ("SSS", "we") makes the SSS Command Centre and the apps inside it, software that dental practices and dental groups use to run their business. This policy explains what information we handle, why, who we share it with, and the choices you have. We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth). Success Software Solutions Pty Ltd is ABN 85 679 484 961.

Two roles. For the details of the people who sign in to SSS (staff, owners, administrators) we are the one who decides how the information is used. For the records a dental organization keeps in SSS, such as its patients, appointments, notes, emails and calls, we are the organization's service provider: the organization decides what goes in, and we only handle it to run SSS for them.

1. What we collect

  • Your account. Name, email address, password (kept by our sign-in provider only as a one-way hash, never readable by us), job role, the clinics you work at and what you are allowed to do. Your organization may also ask for staff details such as your mobile number, date of birth and AHPRA registration number.
  • Your organization. Its name, clinics, opening hours, team list, plan and billing details, and the agreements and contracts it keeps in SSS (such as a payment plan provider's retailer agreement), which only its owners, admins and the people who manage that app's settings can open.
  • Patient and business records your organization puts in or connects. For example patient names and contact details, appointments, health information, treatment plans and notes, emails to and from the clinic, call recordings and transcripts, photos (including photos of payment receipts), agreements a patient signs (such as a payment plan agreement, with their drawn signature or a scan of the signed paper copy), invoices and timesheets. Some of it is read from the organization's practice management system; some is typed or uploaded by its staff.
  • Use of SSS. Sign-in times, what was opened or changed (our audit log), and basic technical details such as browser type and IP address, so we can keep SSS secure and fix problems.
  • Payments. Subscriptions are paid through Stripe. Card details go straight to Stripe; we never see or store full card numbers.

2. Why we use it

  • To provide SSS: sign you in, show each person only what their role allows, run the apps the organization has chosen, and send the emails, texts and notifications it asks for.
  • To bill the organization for the clinics and apps it uses.
  • To keep SSS secure, investigate faults, prevent misuse and meet our legal duties.
  • To give support when the organization asks (see section 6).
  • To improve SSS, using counts and totals rather than individual patient records.

We do not sell personal information, and we do not use patient information for advertising.

3. Where it is kept and who helps us run SSS

SSS's database and sign-in are hosted in Australia (Sydney). We use these providers to run SSS, and give each only what it needs for its job:

  • Supabase (database, sign-in and file storage, Sydney).
  • Vercel (hosting the SSS web apps).
  • Amazon Web Services (email sending through Amazon SES in Sydney, and the Claude AI models on Amazon Bedrock in Sydney).
  • Anthropic (Claude AI, only for tasks that carry no patient information).
  • Stripe (subscription payments).
  • Mobile Message (an Australian text message service: the text messages a clinic sends to patients through SSS texting. It receives the patient's mobile number and the words of each text to deliver it, and passes replies back).
  • Telnyx (phone lines and calls for the phone features, and, where an organization chooses it, its text messages: it then receives the patient's mobile number and the words and any pictures of each text in the same way. Telnyx may handle this outside Australia).
  • Clinics keep clinical details out of texts. SSS keeps a record that each text was sent or received and whether it was delivered for 3 years, and the words (and any pictures) of texts sent through SSS texting and of patients' replies (including replies to a clinic's GoHighLevel number, which SSS reads from GoHighLevel when they arrive), in Sydney, for 12 months, so the clinic's staff can read and answer them; only staff the organization allows to answer patient texts can see them.

AI and patient information. Any AI work that involves patient names, health information or the content of a clinic's email is built to run only on Claude in Sydney, and to stop rather than use another region. AI suggestions are drafts: a person reviews them before anything is sent or saved to a patient's file.

Some providers may handle limited information, such as account or payment details, outside Australia. If we disclose personal information overseas we take reasonable steps to make sure the provider handles it consistently with the Australian Privacy Principles.

4. Systems your organization connects

An organization (not SSS) chooses which outside systems to connect: for example its practice management system, its email (Google or Microsoft), GoHighLevel, or Xero. Connecting one lets SSS read and, where a feature says so, write the information that feature needs, for that organization only.

Xero. When an organization connects Xero, SSS asks Xero for access to only what the feature needs: for payroll features, the organization's employees, pay items, pay calendars and timesheets, where SSS creates draft timesheets for a person to review in Xero; for supplier bills, its accounts, contacts and bills. The connection's access tokens are kept in a secrets vault, are used only for that organization and can be removed at any time, either in SSS (Settings → Integrations) or in Xero (Settings → Connected apps). We do not use Xero data for anything other than the organization's own use of SSS, and we do not share it with anyone else.

Partners an organization works with (the Lab portal). An organization can invite the dental laboratories it sends work to onto the Lab portal. A lab sees only the jobs that organization sent it: the patient's name and the details of the work (the item, teeth, shade, instructions and dates), the practice's contact details and the messages about each job. A lab never sees a patient's date of birth, contact details, Medicare or health fund numbers or medical history, nor any other part of the organization's records. Each time a lab opens a job it is recorded in the organization's audit log. A lab's own people sign in with their own login; SSS keeps their name, email address and what they write on the portal, and uses it only to run the portal. Files on a job (photos, X-rays, scans) that the organization or the lab adds are kept in private storage in Australia for as long as the organization keeps the case; each download a lab makes is recorded. A lab can also send its invoices to the organization through the portal, and keep its own contact details and price list, which the organization accepts into its records. On its dashboard a lab also sees, for its own work only, how many jobs each organization sent and received back, and the lab fees the organization recorded for those jobs. A lab never sees another lab's prices, nor how the organization compares labs. The organization can stop sharing with a lab at any time.

Contacts checking their details. An organization can ask a contact it works with (a lab, a specialist, a supplier) to check their details on a secure page, opened with a one-time code emailed to them. What they send (their business contact details and their answers to the organization's questions) is kept in that organization's Directory and used only to work with them. If they reply to the request by email instead, the reply is read by Claude in Sydney to pick out the same details, and stays in the clinic's mailbox.

5. How we protect it

  • Information is encrypted when it travels between you and SSS.
  • Every organization's records are separated in the database itself, so one organization cannot see another's.
  • Passwords and the keys that connect outside systems are kept in a secrets vault, never in plain settings, and are never shown on screen after they are saved.
  • What people open or change is recorded in an audit log the organization can see.
  • People only see what their job role allows, and an organization can switch a person's access off or give it an end date.

If a data breach is likely to cause serious harm, we will tell the affected organization promptly so it, and we, can meet the notification duties under the Notifiable Data Breaches scheme.

6. Our staff and your organization's information

By default our staff can see only an organization's settings, its team list and its plan and usage numbers. They cannot see patients, emails, documents, photos, calls or the audit log. An organization's owner can allow wider access for a set time to get help; each page we open during that time is recorded where the organization can see it.

7. How long we keep it

We keep an organization's information while it uses SSS. Some things are deleted on a schedule the organization controls, for example call recordings (90 days unless the organization changes it), photos, and files sent through secure links (a few days after the link expires). Photos of payment receipts are kept as financial records for 7 years, then deleted. When an organization ends its subscription, we delete or return its information on request, except where the law requires us to keep something (for example billing records).

8. Cookies

SSS uses only the cookies needed to keep you signed in and remember simple choices such as which clinic you are working at today. We do not use advertising or tracking cookies.

9. Your rights, and who to ask

You can ask to see or correct the personal information we hold about you, or ask us a question about this policy, by emailing app@successsoftwaresolutions.com.au. We will reply within 30 days.

If you are a patient of a dental practice that uses SSS, your records belong to that practice. Please contact the practice first; it decides what you can see or change, and we will help it do so.

If you are not happy with our answer, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au, 1300 363 992).

10. Changes to this policy

We will update this page when how we handle information changes, and change the "Last updated" date at the top. If a change matters to how an organization's information is used, we will tell its owner.

Questions about this page? Email app@successsoftwaresolutions.com.au.