VET Creator

Privacy policy

Effective 11 October 2026. Last updated 11 October 2026. This policy describes how the service works today. We will email account owners a summary of what changed by 10 November 2026.

1. Who we are

VET Creator is an online tool that helps Australian RTOs and VET trainers write training and assessment material. It is run by Jason Clifford, trading as VET Creator, a sole trader in Hobart, Tasmania. ABN 62 917 834 243.

In this policy, “we” and “us” mean VET Creator. “You” means a person with an account, or the organisation they work for.

2. The privacy law we follow

We believe we are a small business that the Privacy Act 1988 does not currently cover. We still follow the Australian Privacy Principles and the Notifiable Data Breaches scheme, as a promise to you. That promise is part of our terms of service, so your organisation can hold us to it, and you can complain to us as section 14 says. We are not yet on the Office of the Australian Information Commissioner’s (OAIC) opt-in register, so the OAIC may not be able to look into a complaint about us.

Working with Tasmanian government. If we work under contract for a Tasmanian Government department or other Tasmanian public body, we also follow the Personal Information Protection Act 2004 (Tas) for the information that contract covers. Under that Act we send information outside Tasmania only to the providers listed in section 9, and we take reasonable steps to make sure their terms protect it. Staff of that body can also complain to the Ombudsman Tasmania (ombudsman.tas.gov.au).

3. Information about your students

We hold none. VET Creator has no class lists, no student names or IDs, no dates of birth, no USIs and no results. It builds the training and assessment material. Your students’ records and results stay in your own student management system.

The documents you print have blank lines for a student’s name, signature and outcome. Those are filled in by hand, or in your own learning management system. Either way the results stay with you, not with us.

Some of what you type or upload is sent to AI services to write and check your material. So please do not type a student’s name or details into any box, and do not upload photos of students or files that identify them.

When you upload your own assessments or learner guides, you must tick a box to confirm they hold no student work and no student names. Please upload blank templates only. If we find student information, we will delete it and tell your organisation.

4. What we hold

We hold information about the staff who use VET Creator(trainers, managers, admin staff and validators) and the material your organisation builds or gives us. We never hold information about your students.

  • · Your account — your name, email address and login, and when you last signed in. Your password is stored hashed, so we cannot read it.
  • · Your email settings — which emails you want, and a private link that lets you unsubscribe.
  • · Your organisation — its name and RTO code, and if you add them, a logo, a postal address and the licence holder’s name.
  • · Your team — each person’s role: owner, compliance manager, team lead, trainer, admin staff or validator.
  • · Invitations — when someone invites a colleague, we store that colleague’s email address and role, and use it to send the invitation.
  • · Validators — a validator is given access to a unit for a validation. That access then ends.
  • · Signed compliance records, such as Standard 1.3 tool reviews and 1.5 validation records. When a staff member signs one, we copy their name (or their email address, if they have not set a name), their role and the time onto the record, and keep the signed file. These stay on the record even if that person later deletes their login, because the record shows who signed it.
  • · An activity log — who did what, and when. Managers in your organisation can see it. It also holds notes from the automatic checks after each build, which only we see (see section 6).
  • · AI usage — for each AI request, the organisation, the user, the AI model, the amount used and the cost. We use this to run the AI budget on your licence.
  • · Your work — the units, courses, assessments and packs you build, the worked examples of workplace documents you save, and the photos, logos, files and YouTube links you add.
  • · Assessments you upload so the course teaches what they ask. We read the files and then delete them straight away. We keep the full text and a short AI summary with that unit, because later builds use them. They stay until someone in your organisation presses Remove on that unit.
  • · Materials checks. If you upload learner guides or assessments for a materials check (gap report), we delete the files once they are read. We keep the findings, short quotes from your documents, and the file names and sizes.
  • · Billing — your plan or unit purchases, your Stripe customer and subscription numbers, and any refunds. At checkout Stripe collects your card, your billing address and, if you give it, your ABN. Card details go to Stripe; we never see or keep them. If you ask to pay by invoice, we keep the legal name, ABN, purchase order number, accounts-payable email address and the name of the person who asked.
  • · A free-trial record — the RTO code and email domain used for each free trial, so the same organisation cannot take a second one.
  • · Technical logs — our hosting provider’s logs can include IP addresses.

5. How we collect it, and why

From you when you sign up and use the tool; from documents you upload; from a colleague when they invite you; from Stripe when you pay; from the automatic checks after a build; and in logs when you use the site. We use it to:

  • · give you an account and let you sign in;
  • · let your team work together with the right access;
  • · build your material, and make later builds match any assessments you uploaded;
  • · check and repair each course automatically after a build (this uses your organisation’s AI budget);
  • · keep the compliance records you ask us to keep;
  • · run the AI budget and billing;
  • · stop the same organisation taking more than one free trial;
  • · improve how the tool builds units, using only notes about gaps against public unit text (see section 6);
  • · send the emails the service needs;
  • · give support you ask for, fix faults and restore from backups;
  • · keep the service secure.

We do not sell your information, we do not use it for advertising, and we do not use your material to train AI.

You cannot use VET Creator without giving a name and email address, because we need to know who has access to your organisation’s material and who signed its records. You can browse the website, demos and pricing without giving us anything.

6. Your material stays yours

We never share your organisation’s material with another organisation or show it to one. That covers the units, courses and assessments you build, your edits, and any documents you upload, such as your own assessments. We pass it only to the service providers in section 9, to run the tool for you, or where the law requires us to.

One thing we do learn from. After each build the tool checks the course against the unit of competency. A unit of competency is public text from training.gov.au. Where the check finds the course missed part of the unit, we keep a note of what was missed. We see these notes on our admin page, and we use them to make later builds better for every customer who builds a unit from the same training package. The notes are about gaps against the public unit. We do not pass on your documents or your edits with them.

Checks against your own uploaded assessments are never used for anyone else. Their results are shown only to your organisation. On our admin page we see only a count of them.

7. Where it lives

In a database hosted in Sydney, Australia, and the application that reads it runs in Sydney too. Each organisation’s records are kept apart at the database level, so one customer cannot see another customer’s records through the app.

We also keep an encrypted daily copy of the database on our office computer in Hobart, Tasmania, for 30 days.

8. Who at VET Creator can see your information

VET Creator is run by one person, Jason Clifford. No staff or contractors have access to your information.

He can see your organisation’s information, including your material and uploaded assessments, when he needs to: to give support you ask for, to fix a fault, to restore from a backup, or to keep the service secure. He does not look at your work for any other reason.

  • · He has a read-only admin page. It shows each organisation’s name, RTO code, plan, unit counts, the owner’s name and email, and when people last signed in. It also shows the notes about gaps against public unit text (section 6), and only a count of checks against your own assessments.
  • · The admin page needs a two-factor sign-in, and every visit to it is logged.
  • · For fixes and restores he can also reach the database and the backups directly.

When we use AI tools to help with support, fixes or restores, your information may pass through Anthropic, under the same terms as in section 9.

If we ever take on staff or contractors, they will be bound by the same rules and we will update this policy first.

9. Who else handles it, and where they are

Only the services that make the tool work. Each gets only what it needs.

  • · Supabase — database, file storage and logins. It also sends invitation and password-reset emails. Data stored in Sydney; the company is in the United States.
  • · Vercel — hosting. Runs in Sydney; the company is in the United States. Its logs include IP addresses.
  • · Stripe — payments. It gets your card details, billing address, ABN if you give it, your organisation’s name and the owner’s email. United States and Ireland.
  • · Anthropic (Claude) — writes and checks your content, and writes the descriptions for pictures. It is sent the unit text, the instructions you type, the content you are working on, and the text of any document you upload: your own assessments, or files for a materials check. United States.
  • · OpenAI — draws the course pictures. It is sent a short picture description written from the course page, such as a title, labels and a scene. The picture comes back and is stored in Sydney. United States.
  • · Resend — sends trial emails, alerts when a unit you use changes, and invitations to people who already have an account. It is sent the staff email address and the email. United States.
  • · training.gov.au (the national register) — to fetch a unit and check it is current. Only the unit code is sent. Australia.
  • · Pexels (Canada) and Wikimedia Commons (United States) — photo searches from the course editor. Only search terms built from the unit.
  • · YouTube (Google) — if you paste a YouTube link into a course, the video plays from youtube-nocookie.com. United States.
  • · GitHub — holds our code and runs our nightly backup job. The job briefly handles a copy of the database before it is encrypted. United States.
  • · Amazon Web Services — stores our encrypted off-site backups in Sydney.
  • · Cloudflare and Forward Email — pass on email sent to our contact addresses. United States.
  • · Google (Gmail) — the mailbox where that email is kept. United States.
  • · healthchecks.io — told only whether a backup worked. No personal information.

So some information goes to companies in the United States, Ireland and Canada. Information that can identify a person goes to: Stripe (billing name, email, billing address and ABN); Vercel (IP addresses in its logs); Supabase and Resend (staff email addresses, to send emails); Anthropic (anything typed into a box or contained in an uploaded document, and what we look at when we use AI tools for support or fixes); and GitHub (briefly, during the backup). That is why we ask you not to type or upload anyone’s personal details beyond what is needed. We choose providers whose business terms limit how they can use it, and we stay responsible for how they handle it.

We will email account owners at least 30 days before we add a provider that will receive your material or your staff’s details.

10. AI and your content

  • · We do not use your material to train AI, and we choose AI services whose terms say they do not train on it.
  • · We use Anthropic’s and OpenAI’s paid business services. Under their current published terms, neither uses what we send to train its AI by default.
  • · Both keep requests for a limited time to check for misuse (OpenAI says up to 30 days). They may keep them longer if a request is flagged or the law requires it. We do not have a special zero-retention arrangement with either.
  • · We check these providers’ terms from time to time. If we learn that either has changed them in a way that weakens this, we will tell you.
  • · Every AI picture is captioned “AI-generated illustration made for this course.”
  • · AI can be wrong. Check all material before it is used with learners.

11. How we keep it safe

  • · Data is encrypted in transit, and encrypted at rest by our database and storage providers.
  • · Each organisation’s records are kept apart at the database level. Each person sees only what their role allows. Validator access ends when the validation ends.
  • · Passwords are stored hashed. Our admin page needs a two-factor sign-in.
  • · Our off-site database backup in Sydney is encrypted before it is uploaded, and the key to read it is never uploaded with it. Uploaded files in that backup are encrypted at rest by Amazon Web Services.
  • · The daily copy on our office computer is encrypted with the same key as the off-site backup.
  • · We are a one-person business. We do not hold ISO 27001 or similar certification. Our database, hosting and backup providers (Supabase, Vercel and Amazon Web Services) publish their own security reports. Ask us and we will do our best to answer your security questionnaire.

12. How long we keep it

While you are a customer, we keep your information. When a paid plan ends, your account is read-only for 90 days (30 days after a free trial): everything opens and exports, and nothing new is built. After that we keep it, out of reach, so it can come back if you subscribe again. We delete it 24 months after the licence ends, and we email the owner at least 60 days before we delete anything. The owner can delete the organisation sooner. Units you bought one at a time stay readable until the owner deletes the organisation.

Exporting everything. While your licence is live, and through the whole read-only window, an owner can download everything from the Licence page. The download holds every unit’s full pack, a history of edits, and your compliance records, including the names of the staff who signed them.

Deleting your organisation. An owner can delete the organisation from the Licence page. That removes its units, packs, uploaded text and files from live storage straight away. It cannot be undone, so export anything you want to keep first.

Deleting your login. Logins are not removed with the organisation, because the same person can belong to another one. You can delete your own login on the Account page, or ask us to. An owner must first hand ownership to someone else or delete the organisation. When you delete your login, it is closed and your profile becomes “Deleted user”. The units you made pass to your organisation’s owner. Your name stays on compliance records you signed, because they are your organisation’s record of who signed. An owner can remove a staff member from the team at any time.

Removing an uploaded assessment. If you press Remove on an uploaded assessment, its text and summary are gone from the live service straight away. Course pages already written from it stay until you change them. Short notes our checks made from it, and the file names, stay in your activity log. Copies stay in backups until they expire.

What stays after a deletion. Our payment records and invoices stay in Stripe, because tax law requires us to keep business records. The RTO code and email domain used for a free trial are kept, so the same organisation cannot take a second trial.

Copies stay in our backups until they expire:

  • · our database provider’s own backups: 7 days;
  • · daily encrypted database copies, off-site in Sydney: 30 days;
  • · monthly encrypted database copies, off-site in Sydney: 12 months;
  • · encrypted daily copies on our office computer: 30 days;
  • · older versions of uploaded files that were replaced: 90 days.

Copies of uploaded files and pictures in the off-site backup are not removed automatically. Ask us and we will remove them, usually within 10 business days. Backups are not searched or used for anything except restoring the service after a fault. If you ask, we will confirm in writing when your data has been deleted, and say which backup copies remain and when they expire.

Your record-keeping obligations are yours, not ours. An RTO must keep assessment records for its own retention period, and deleting your organisation here does not satisfy that. Export before you delete.

13. If something goes wrong

If we become aware of unauthorised access to, or loss of, your information, we will tell your organisation’s owner within 72 hours of finding out: what happened, what was affected and what we have done. We will not wait to be asked. We will work with you while you deal with it, including giving you what you need for your own reports. If a breach is likely to cause serious harm, we will also tell the people affected and the OAIC, following the Notifiable Data Breaches scheme.

14. Seeing, fixing or complaining about your information

  • · You can ask what we hold about you, and ask us to correct it. It is free. You can fix most details yourself on the Account page.
  • · For anything else, contact our privacy contact, Jason Clifford, at hello@vetcreator.com.au.
  • · We may ask you to confirm who you are before we share anything.
  • · We reply within 30 days. If we cannot give you something or change it, we will tell you why in writing, and how to complain.
  • · To complain, write to us first. We will look into it and reply in writing within 30 days.
  • · If you are not happy with our answer, your organisation can take it up under our terms of service. Once we are on the OAIC’s opt-in register, you will also be able to complain to the OAIC at oaic.gov.au. Staff of a Tasmanian public body can complain to the Ombudsman Tasmania (see section 2).

15. Email

We send only emails the service needs: invitations (sent through Supabase, or through Resend when the person already has an account), password resets (sent through Supabase), and trial reminders and alerts when a unit you use is superseded (sent through Resend). We do not send billing emails ourselves; any payment emails come from Stripe. We have no marketing list and we never share or sell email addresses. Trial reminders can be turned off from the link in the email, and both trial reminders and unit alerts from the Account page.

16. Cookies

We use only what the site needs to work: cookies that keep you signed in, a cookie that remembers which organisation you are working in, and a setting saved in your browser for how dense the criteria lists look. No analytics, advertising or tracking. Our fonts are served from our own site, so loading a page does not contact Google.

A YouTube video on a course page plays from youtube-nocookie.com, Google’s privacy-enhanced mode, and only signed-in users see it. Google may store its own data in your browser once you press play.

17. Automated decisions

We do not use computer programs to make decisions that significantly affect people. One check is automatic: when someone starts a free trial, the app checks whether their RTO code or work email domain has had a trial before. It also asks for an RTO code if they sign up with a personal email address such as Gmail. If it refuses a trial and you think that is wrong, email us and a person will look at it. The AI writes and checks training material. It does not judge people.

18. Changes to this policy

When we change this policy we update the date at the top. If a change affects how we use your information, we email account owners at least 30 days before it takes effect. Ask us for an earlier version and we will send it.

Questions, or a request to access or correct what we hold: hello@vetcreator.com.au, or write to 1/498 Oceana Drive, Howrah, Tasmania 7018, Australia. Terms of service.