Skip to main content

Legal

Privacy Policy

Version 2.0. Effective 23 October 2026.

Document fingerprint (SHA-256): 0b95d487074317c5ff986cda1d8176e6d0b3398f6bd0c33c76fa2b06ba08b577. Acceptance receipts for this version refer to this fingerprint.

This policy explains what personal information SkillProof handles, why, who can see it, who we share it with, and how you can ask us about it. It covers the SkillProof application and this website.

Who we are and how to contact us

SkillProof is operated by The Trustee for Ryan Kennedy Trust, trading as Loose End Labs, ABN 90 708 352 217. Loose End Labs is a registered business name. It is not a company. This policy applies to the SkillProof application and to the SkillProof website.

Privacy contact: support@skillproof.au. Use this address to ask about your information, ask for access or correction, raise a privacy concern, or tell us about a possible privacy problem. Please do not send passwords or card details by email.

What this policy covers

This policy describes how information about you is handled when you use SkillProof as an apprentice, an experienced worker preparing RPL evidence, a Supervisor, a Builder or another role the service provides. It also covers visitors to this website.

We aim to handle personal information consistently with the Australian Privacy Principles, whether or not the Privacy Act applies to us by law. This policy does not remove any right or protection you have under the SkillProof Terms, the Founders Charter, or any law that applies regardless of our position.

The short version

  • You own your record and we hold it in custody.
  • Supervisors and others can see only what their role and relationship allow. This policy describes what the system currently does.
  • Some of your information is sent to outside providers to run the service. They are listed below.
  • Photos and documents can show other people and sensitive details. Please take care.
  • If you are under 18, please read the section on under-18 apprentices.
  • The application has no delete-your-account button. Submitted records are kept as history. The section on keeping and deleting explains what that means.

This website

This website, www.skillproof.au, explains SkillProof and links to the application. It has no accounts and no forms. It has no analytics, advertising or tracking scripts, loads no content from other sites, and does not set cookies.

If you email us, we receive your email address and what you write. Our website host, Vercel, processes standard request information, such as your network address and browser description, to deliver pages and keep its own logs. We have not confirmed how long it keeps those logs.

When you follow a link to app.skillproof.au to register or sign in, you leave this website. The application collects information as the rest of this policy describes.

What we collect in the application

WhatDetails
AccountEmail, name, password (kept only as a one-way scrambled form), the pathway you chose (apprentice, RPL, supervisor or builder), phone number.
Business detailsA business address, for supervisor and builder accounts.
Training detailsApprenticeship start and end dates. Years of experience for RPL candidates.
ProfileHome address and an emergency contact name and phone number, if you give them.
Work journalDate, times, hours, breaks, work categories, summary, notes, site name, draft status, and optional links to a project, package or stage.
Photos and filesPhotos you attach to entries and files you upload to your profile.
White Card and licenceImages of a White Card and QBCC licence details and document, if you upload them.
Witness recordsA Supervisor’s confirmation or return of an entry, comments, and statements made in a dispute.
Links and invitationsThe email address of a person you invite, your message, link requests and workspace join codes.
BillingWhich plan you hold, amounts, and the identifiers Stripe uses for your customer, subscription and payment. You give Stripe your payment details and billing name and address at checkout.
TechnicalThe browser or device description recorded when you sign in. Network addresses are used to limit repeated requests.
Records we keep about the serviceAudit records of important actions, evidence version records, Supervisor confirmation records, export receipts, and sign-in tokens in scrambled form.

You can use the service without giving every optional item above. Some features need particular information. A Supervisor invitation needs the invitee’s email. We do not ask for date of birth or a parent or guardian’s details, and the application has no step that checks your age.

What we create about you

  • A fingerprint (hash) of each stored photo. It is of the compressed copy that was stored, not the camera original.
  • A digital fingerprint that ties each Supervisor confirmation to the exact version of the entry they saw.
  • Status labels and counts, such as entry and hour counts and a compliance status on a placement certificate.
  • A short summary of a journal entry written by an AI tool, if you ask for it and the feature is available (see AI features).
  • A pre-screen result for a White Card image, if that feature is available (see AI features).

These are not a finding that you are competent or qualified. SkillProof is not intended to turn your activity or hours into a score, rating or ranking of you.

How we collect it

From you when you register, complete your profile, write an entry, upload a photo, invite someone or pay. From other people on the platform when they confirm or return an entry, record a placement, raise or answer a dispute, or accept a link. From your device when you sign in. From Stripe when a payment or subscription event happens. From our own systems, which create the records described above.

Why we use it

To run your account; to keep your record; to let a linked Supervisor witness your work; to produce certificates and exports you ask for; to take payment; to contact you about your account, invitations and notices about your record; to keep the service safe and prevent abuse; to support you and administer disputes and verification; and to meet legal duties.

We do not intend to use your record to build a score or ranking of you. This policy does not describe any use of anonymised data for product improvement. If we later want to do so, we will explain it first.

Photos and workplace evidence

A photo you attach is evidence you chose to attach. It shows what was photographed and when it was captured or uploaded. It does not prove the work was done well, who did it, or that anyone is competent.

Your phone or browser compresses the photo and uploads it to Cloudinary, an image hosting service, using a request our server issues for your account. Our server then fetches the stored file to work out its fingerprint. We do not keep the camera original. The app reads the capture date from the photo to help set the entry date. It does not read or store the location of a photo.

Who can get to a stored photo. The upload does not ask for restricted delivery. This means anyone with the exact web address of a stored file may be able to open it unless Cloudinary settings restrict it. Please do not upload an image you would not want shared if its address were found.

Other people in your photos. Photos and notes may show or name colleagues, supervisors, clients, passers-by and private homes. Do not upload an image showing a person’s face or identity unless there is a good reason and it is appropriate on that site. Take particular care with children. If you think a photo shows you and you want it dealt with, write to the privacy contact. We will respond, but we cannot promise to remove it in every case.

White Card and licence images. If you upload one, it is stored with Cloudinary and its details are stored with your account. Staff with verification duties can view it. Removing a document from your account clears the stored fields in our records. It does not currently remove the file from Cloudinary.

Who can see your information

A Supervisor who confirms an entry is witnessing, in the workplace, what that version of the entry says. The confirmation is tied to the exact version they saw. It is not a trade qualification, an assessment or a finding of competence. A Supervisor is not a licensing body or an RTO.

What a Supervisor writes about an entry becomes part of that entry’s history. You can see it and dispute it under the Terms. We also hold the Supervisor’s own details: their name, role, email, and the time and fact of their decision.

WhoWhat they can see
YouYour own account, entries, evidence, history, exports and certificates.
Your assigned SupervisorEntries you submit to them and the account details their role view includes.
A Builder you are linked toYour journal and progress as the Builder role allows, and the account details their role view includes.
A workspace or labour-hire hostPlacement records that involve you: your name, the host, the site, dates and status.
StaffModerators can read user accounts, journal entries and photos across the platform and can verify White Card and QBCC documents. Administrators have full access. The platform owner can act as an administrator.
Anyone with a verification linkThe limited details described under public verification.
Other workersNothing about you, unless they are bound to the same record.

What a Supervisor’s roster shows. The list of apprentices that a Supervisor’s account fetches is limited to a defined set of fields. Other screens a Supervisor or Builder can reach may show more account details than the roster does.

Notice when someone else looks. The Terms promise that you will be told when your record is materially changed, disclosed or accessed by someone other than you. The application does not currently send an automatic notice when a Supervisor, Builder or staff member opens your record. It does not currently log staff reads of a worker’s journal or photos.

Public verification

A placement certificate can be checked by a person who has its reference and seal. The check shows the worker’s name, the host builder’s name, the site name, start and end dates, status, compliance verdict, the Charter version and the first characters of the seal. Competency matrix and RPL exports can be looked up by reference. The lookup confirms that an export record exists and when it was generated. It does not show the contents. You should know this before you issue a certificate.

Sharing with service providers

ProviderWhat it does
RenderRuns the SkillProof application server.
Database hostStores account, journal, evidence, confirmation, billing identifier and audit records.
CloudinaryStores photos and uploaded images, including White Card and licence images.
StripeTakes payment and manages subscriptions.
SendGridSends service email such as password resets and invitations.
OpenAIProvides the optional AI features described below, when they are available.
BackblazeHolds database backups.
VercelHosts this website.
Support mailbox providerReceives email sent to the support address.

We have not confirmed how long each provider keeps the information it receives.

Where a Builder, labour-hire host or other workspace brings workers into SkillProof, the workspace can see the placement records involving you.

We comply with lawful orders. The application has no process that records lawful orders or sends notice to the people affected. We will tell you in writing, to the extent the law allows, of any disclosure of your record that we ourselves make outside SkillProof to a government body.

If the business is transferred, your records are not business assets and do not pass as assets. The Terms deal with this.

AI features

Two features can send information to OpenAI. They operate only when the service is configured with an OpenAI key.

FeatureWhat is sentWhat comes back
Journal summaryThe entry date, hours, categories, summary text, notes and day counts.A short AI-written summary stored with the entry.
White Card pre-screenThe White Card front image, your registered name and your email.A pre-screen result stored in your account.

AI output is generated text. It is not a Supervisor’s confirmation, a verification or a finding about you. A person decides. Neither feature approves or rejects a person automatically.

We have not confirmed how long OpenAI keeps what we send, or whether it may use it to improve its own models. We do not say that it does not. There is currently no setting to switch these features off for your account, and no screen that tells you before the information is sent.

Overseas handling

Some of our providers are, or may be, outside Australia. Our application server is configured to run in Singapore. For the other providers, we have not confirmed where your information is stored or accessed. Assume any provider listed above may handle your information outside Australia.

Payments

Payments are handled by Stripe. We create a checkout with a price and your user identifier and ask Stripe to collect your billing address. We store your plan, the amount, currency, mode and the Stripe identifiers. We do not store card numbers. See the Billing Policy.

Email, cookies and analytics

We send service email: password resets, supervisor invitations, link-request notices, account recovery steps and notices about your record. We also send alerts to staff when someone submits a White Card, a QBCC document or a link request. These contain names, email addresses and submission details. When you invite someone, their email address is stored and the invitation is sent for you. The service has no marketing or newsletter feature.

On the web application, sign-in is held in secure cookies set by our server that scripts on the page cannot read. On the phone application, sign-in tokens are held in the device’s secure store, and entries and photos created offline are held in a local database on your device until they can be sent. The application and this website have no third-party analytics, advertising or crash-reporting code.

The application server records the browser or device description when you sign in, and uses your network address to limit repeated requests. Some log lines include email addresses. Hosting providers keep their own logs. We have not confirmed how long any of these logs are kept.

Security

We take steps to protect your information. Passwords are stored only in scrambled form with a minimum length. Sign-in sessions are short and renewable. Password reset and recovery links expire. Photo uploads use a request our server issues for your account. Requests to sensitive and public parts of the service are rate limited. Changes to evidence entries and Supervisor confirmations are kept as a linked history in the application so later changes are visible.

We do not say any system is free of risk, that evidence records cannot be altered, that your information is encrypted in any particular way, or that we hold any security certification. We do not currently offer multi-factor sign-in. If something goes wrong with your information, we will assess it and tell you as the law and the Terms require.

Keeping, withdrawing and deleting

ItemWhat happens today
Draft entries never submittedYou can delete them. They are removed.
Entries that have left draftThey become governed evidence. You can withdraw one. A withdrawn entry stays as history, no longer counts as current evidence, and cannot be edited, resubmitted, confirmed or summarised. We do not delete it.
Your accountThere is no screen to deactivate or delete it. Write to the privacy contact. An administrator can deactivate an ordinary account, which stops sign-in and keeps the data.
Account deletionAn administrator can permanently delete an account only if there is no durable history. If there are journal entries, confirmations given, supervisor or builder links, placements, owned workspaces or billing transactions, the system refuses and the account is deactivated instead.
Photos and White Card filesRemoving one from your account does not remove it from Cloudinary.
Sign-in session recordsDeleted automatically about 7 days after they expire.
Stripe event recordsDeleted automatically after 30 days.
BackupsKept for a period configured at 30 days. This policy does not describe their location or protection.
Billing records, audit records, confirmations, evidence versions and sealed recordsKept. A subscription lapse or cancellation does not remove them.

We do not promise to delete every item you ask us to delete. Sealed records stay as read-only history, because they can bind employers, Supervisors, training organisations and others, and because disputes and legal matters can outlast your use of the platform. A legal duty to keep a record can also override a deletion request. We have no published retention schedule yet. We will tell you in plain words what we deleted, what we kept and why.

If you die, your Identity becomes read-only. It is not made public or used commercially. A beneficiary you name, or a legally appointed executor, may ask for access.

Exports

You may export your record. Today there are two exports. A free personal-record PDF is available to every worker, is marked as a personal record, shows up to 500 entries and tells you if it is incomplete. A signed portable bundle covers placement records and is available only on a paid plan for your role. Neither is a full export of all your evidence and history. The Terms explain the Charter right and the current limitation. An export is a picture of your record when it was made, not the record itself.

Under-18 apprentices

Many apprentices are under 18. The application does not currently ask for your age, check it, ask for a parent or guardian’s agreement, or offer different settings for under-18 users. If you are under 18, think carefully before you upload photos, home addresses or other personal details, and consider talking to a parent, guardian, or your employer or training provider first. A parent or guardian can write to the privacy contact on your behalf.

We do not claim the service meets the standard expected of services for children. The OAIC’s Children’s Online Privacy Code is due to be registered by 10 December 2026, and we will review it.

Seeing and correcting your information

You can ask us for the personal information we hold about you and ask us to correct it. Write to the privacy contact. We need to check the request is from you. We will not ask for your password. The application has no tool for these requests, so we handle them by email. We will respond within a reasonable period and, if we refuse, tell you why in writing and how to complain.

Where something in a sealed record is wrong, we do not silently change it. We correct by annotation or by a new record that supersedes it, so the history shows what was said, what was wrong and what replaced it. You can update details outside sealed records, such as your name or phone number, in your profile.

Complaints

If you think we have mishandled your information, write to the privacy contact. We will reply in writing. You can also complain to the Office of the Australian Information Commissioner.

Other people’s information

Workers: you decide what to put in your record. Do not enter another person’s private details without a good reason. Supervisors: confirm only what you personally witnessed. Builders and workspace operators: use what you can see only for the placement, site or supervision it relates to, and do not build a surveillance profile of a worker. Everyone: do not share a verification link or export with a person who has no business seeing it.

Changes to this policy

We will not change this policy silently. Each version has a number, an effective date, a plain summary of what changed and the version it replaces. Earlier versions stay readable. We will tell you before a material change takes effect. Continuing to use the service is not consent to a change.