VeriClass Privacy Policy
10 November 2026
Operated by Vericlass Pty Ltd (ABN 16 701 124 870, ACN 701 124 870).
Who we are
VeriClass is an AI-assisted waste classification platform operated by Vericlass Pty Ltd (ABN 16 701 124 870, ACN 701 124 870) (“we”, “us”). We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). This policy explains what we collect, why, and who processes it on our behalf. For privacy questions, requests or complaints, email contact@vericlass.io.
VeriClass is a business service for adults. It’s not intended for anyone under 18.
Client and User. In this policy, the Client is the company or organisation that holds the VeriClass account and buys credits or plans. A User is a person who uses VeriClass under a Client’s account (staff or contractors), acting for the Client. The Client’s contact person, who deals with us about its account, is the first person from the Client that we invite to use VeriClass. Each Client has one contact person at a time, who must be a named User. To change the contact person, the current contact person, or a director or owner of the Client, must ask us in writing, and we may check the request first. We only add or remove Users when the contact person asks. Any User can start a Volume plan for the Client, but only the contact person can cancel it or close the Client’s account. A User can also ask us to remove their own login, and we may block a login to protect security. “You” means you personally, as a User.
This policy covers personal information about Users, and about other people named in documents Users upload (such as laboratory staff, samplers or site owners). Privacy rights, such as access and correction, belong to each person personally, not to the Client.
What we collect
- Account details: your name and email address, used to create and secure your User login.
- Contact person details: for the Client’s contact person, their full name, role or position, email address and phone number, so we can deal with them about the Client’s account.
- Job content you upload: laboratory certificates of analysis (PDF; text PDFs within the current 10 MB per-file limit; several PDFs from the same lab job may be processed together), optional site photographs, the site address and coordinates (which you type or confirm — any “Fill from report” suggestion is only a suggestion), a material description, your answers to the screening questions, and an optional email address to deliver the finished report to.
- Chat messages: questions you put to the Guidelines assistant, and its responses. The Guidelines assistant is an AI chatbot (Anthropic Claude). Its answers may be wrong and are not a classification or advice. Please don’t enter personal information about other people.
- Payment details: handled by Stripe. We never see or store card numbers; we keep only the Client’s plan, credit balance, payment status, invoice records and Stripe customer ID.
- Reviewer signing details: for the environmental scientists who sign reports, the name, qualifications, title and signature image printed on each report they sign. Signature images are stored securely and applied to a report only when the reviewing scientist personally approves and signs it.
- Account access requests: the name, email address, organisation and intended use you give when you request access from the sign-in page.
- Activity records: an audit trail of actions on the Client’s account, showing which User did what (uploads, acceptance of the Disclaimer and Terms of Use and the confirmation you tick before submitting a report, processing runs, the reviewing scientist’s decisions and any values they correct, report downloads, emails sent), kept for security and traceability.
- Technical data: IP address, browser and device details, and sign-in times, collected by our hosting and authentication providers to deliver and secure the service.
We collect information directly from you, from the Client (when its contact person asks us to add you as a User), from documents you upload (which may contain details of laboratory staff, samplers, site owners or other people), and from Stripe (payment status). We hold it electronically with the service providers listed below.
Please only upload information you’re allowed to share. You may hide (redact) personal details that the classification doesn’t need, but please don’t change or remove any results. Site addresses and coordinates can identify a property owner or occupier, so we protect them as personal information, along with any other people’s details in uploaded documents.
Photos may contain location data (such as GPS coordinates), which we keep as part of the original photo so the report can be verified. Please avoid photographing people or vehicle number plates. Apart from the uses described in this policy (storing them in the Client’s account, having our AI provider describe them, and including them in the Client’s own report where relevant), we will not share, distribute or publish the photos you give us, unless the law requires it.
You can make general enquiries without identifying yourself. We need your name and email to provide an account and signed reports, so we can’t provide those anonymously.
How we use it
Uploaded content is used for producing the classification and report, our records and audit trail, support, checking report authenticity, and improving VeriClass’s accuracy from scientist corrections (with no names, site addresses or photos). Lab report pages are read by our own software where it recognises the laboratory’s layout, by text recognition on our hosting provider’s servers (Render) where a page holds no readable text, and otherwise by an AI model. Site photographs are described by an AI model. The classification itself is deterministic software applying the NSW EPA Waste Classification Guidelines Part 1 (2014) only to the core tests (see our Terms of Use, clause 5): AI only helps read results where our own software and text recognition can’t, and never decides a classification. The result is assembled into a report, with your laboratory certificate attached, stored in the Client’s account, and emailed to you and to any recipient you nominated once it is signed.
Automated decisions. VeriClass’s software reads the results from your certificates (using text recognition and AI where needed) and then applies the NSW EPA Waste Classification Guidelines Part 1 (2014) only to the core tests (see our Terms of Use, clause 5), to propose each waste classification. Decisions made solely by a computer program: none. Decisions where our software does something substantially and directly related to the decision: the proposed waste classification for each sample, and whether an item is held for the scientist’s review. A qualified environmental scientist reviews every proposed classification before a report is issued. While a report is held, the reviewing scientist may see provisional or suggested classes in the reviewer tools; those unsigned suggestions are not an issued report and must not be relied on as one. The Client is not shown a class until the report is signed. The scientist can correct extracted values and re-run the classification, decide items held for review, or refuse to issue the report, but can’t change the classification itself. Corrections are only for values our software misread from the lab report, not changes to the laboratory’s results. The personal information our software uses for this is: the site address and coordinates, the material description, your screening answers, the lab results, and the name of the person who uploaded the report. We don’t use automated decisions to refuse accounts or services.
We use account and activity data to operate and secure the service, provide support, and meet our record-keeping obligations. Access requests are used only to answer them. We do not sell personal information, and we do not use your content for advertising. We don’t allow AI providers to train on your uploads or reports (see Anthropic under “Service providers we rely on”). When our scientist corrects something at sign-off (for example a misread value), we may keep details of the correction (what was read, what it should have been, and the lab and report format), with no names, site addresses or photos, and use them to improve VeriClass’s accuracy.
We send service emails (reports, review notices, invitations, account security). We’ll send marketing only with your consent, and every marketing email has a working unsubscribe link. We act on unsubscribes within 5 business days.
Service providers we rely on
We use a small set of processors, each receiving only what its function needs:
- Anthropic: We use Anthropic’s commercial API to help read lab reports, describe site photos and answer Guidelines assistant questions. Under Anthropic’s published commercial terms, API content is not used for model training by default. VeriClass does not opt in to training or send Client content as model-improvement feedback. No training does not mean no storage: Anthropic may retain inputs and outputs temporarily for safety, security and service operation. Its published standard API retention period is up to 30 days, but different or longer periods may apply under the relevant model or feature terms, an agreement, Usage Policy enforcement or legal requirements. We do not promise zero storage or immediate deletion.
- Mapbox: address search on the new-report form (your address query is sent to Mapbox to return suggestions) and the static site map in reports.
- Supabase: authentication, database and file storage.
- Stripe: payment processing. Card details are entered on Stripe’s own payment page and handled under Stripe’s terms and privacy policy. We meet our own privacy obligations for the information we hold and share with Stripe. Stripe is responsible for the security of its own systems, and, except where the law makes us responsible, we are not responsible for a security breach within Stripe’s systems that we did not cause or contribute to. If we learn of a breach that affects your information, we will respond as described under “Storage, security and retention”.
- Resend: email delivery. Resend receives each recipient’s address and the message: your signed report and its attachment, sent to you and to any recipient you nominate; a notice to the reviewing scientist when a report needs their review (its reference, site address and outcome so far); an invitation when we add you as a User at the request of the Client’s contact person; and the details you give when you request account access from the sign-in page.
- Vercel: hosting and content delivery for the web application. Vercel processes standard request metadata (IP address, user agent) as part of serving and securing the site.
- Render: hosting for the classification engine and its background workers. Uploaded documents are processed here in transit, including text recognition of pages with no readable text. The servers are in Oregon, United States.
- GitHub: source-code hosting for the application. GitHub holds our code and test files made from publicly available documents. It does not receive your lab reports, site data or account data.
We do not sell personal information. Our providers may use data only to provide their services to us, and for limited purposes of their own such as security, fraud prevention and legal compliance, under their published terms.
We may also disclose information where required or authorised by law (for example to the NSW EPA or a court), to our professional advisers, or to a buyer of our business, who must continue to protect it under this policy.
Some of these providers store or process data outside Australia. Where that happens, APP 8 applies and we take reasonable steps to ensure they don’t breach the APPs. We remain accountable under the Privacy Act for how they handle it. Where each provider holds or processes data:
- Resend (email delivery): United States.
- Stripe (payment processing): United States.
- Anthropic (AI extraction where our own software can’t read a page, photo description and the Guidelines assistant): United States.
- Mapbox (address search and site maps): United States.
- Render (classification engine and background workers): Oregon, United States.
- Supabase (authentication, database and file storage): Sydney, Australia.
- Vercel (web hosting and content delivery): delivered through a global network, with server functions in Washington, D.C., United States.
- GitHub (source-code hosting): United States. GitHub does not hold your personal information.
Who can see reports
Every classification is reviewed and signed by a qualified environmental scientist before it is released to the Client. While a report is held, the reviewing scientist may see provisional or suggested classes in the reviewer tools; those unsigned suggestions are not an issued report and must not be relied on as one. The Client is not shown a class until the report is signed. That reviewer can open the reports awaiting their signature, including the underlying laboratory data, because reviewing it is the service the Client is buying. Anyone who reviews reports for VeriClass is bound by confidentiality obligations.
The Client can ask us which Users are on its account and what they have done in it (for example, who uploaded a report). All Users of a Client can see all of that Client’s reports and uploads, including ones other Users uploaded, and the name of the User who uploaded each one (name only, not their email or other contact details). Users of other Clients can’t see them. Reports belong to the Client. VeriClass staff can see reports when they need to for support and billing. Every action VeriClass staff take is recorded in an audit log.
Storage, security and retention
We protect information with technical measures (encryption in transit and at rest, access controls, logging) and organisational measures (limited staff access, confidentiality obligations, a data breach response plan). Access is enforced both in the application and in the database itself. Each report we issue is digitally signed and carries a verification code, and we keep a fingerprint of the issued file so we can confirm whether a copy is genuine. VeriClass is a waste classification service, not a document storage service. Please download and keep your own copies of your reports, lab reports and photos. You already receive each signed report by email. We normally keep signed reports and the lab reports they are based on for 7 years from the date the report is signed. That is our usual practice, not a guarantee. We keep records for these periods:
- Payment, invoice and credit records: kept 7 years (Corporations Act 2001, section 286).
- Signed reports and the lab reports they’re based on: normally kept for 7 years from the date the report is signed.
- Screening answers, site address and material description for signed reports: normally kept with the report for 7 years from the date the report is signed.
- Site photo files: deleted 12 months after the report is signed. Any photo or photo description included in the signed report is kept with the report.
- The scientist’s sign-off checklist: normally kept with the report in our own records for 7 years from the date the report is signed. It isn’t part of the report the Client receives.
- User personal details: deleted or de-identified once the User is removed or the Client’s account is closed and we no longer need them, except where they form part of the records above.
- Audit records (who did what on each signed report): normally kept for 7 years from the date the report is signed.
- Other audit records: purchase records, each acceptance of the Terms of Use and Disclaimer (date, time, User and version), and records of which User uploaded or did what on a report that was never signed: normally kept for 7 years from the date of the action. These audit records don’t include the site address, material description, screening answers or uploaded files. Sign-in logs and chat assistant logs are not audit records (see below). (Purchase records are also payment records, so the 7-year legal requirement above applies to them.)
- Chat assistant logs and our own sign-in logs: kept for 12 months, then deleted.
- Our providers’ technical logs (Vercel, Resend, Supabase, Render), including the technical data described above, are normally kept for between 1 and 30 days depending on the provider: about 1 day for Vercel, about 7 days for Supabase, about 14 days for Render and about 30 days for Resend. Mapbox keeps IP addresses for 30 days.
- Account access requests (from the sign-in page): the details you give when you request account access are deleted 12 months after we reply.
- Lab reports, photos, site address, material description and screening answers for reports that are rejected, closed or never finished (not signed): deleted 12 months after the report is rejected or closed, or 12 months after the last activity on it if it is never finished.
- Investigations and claims: if the NSW EPA asks for a report, or a legal claim is likely, the related records are kept until that matter is finished, even after the periods above.
- If we plan to stop providing VeriClass or close the business, we will endeavour to give the Client at least 60 days’ notice by email to the contact person so you can download or ask us for copies of your reports. After that notice period, we will securely delete the records, except that we keep payment, invoice and credit records for the 7 years the law requires (Corporations Act 2001, section 286).
- If the VeriClass business is sold: your records pass to the new owner, who must keep protecting them under this policy.
You can ask us to delete your User login and personal details at any time. The Client’s contact person can ask us to close the Client’s account and delete its content. Both are subject to the records above. The law requires us to keep payment, invoice and credit records for 7 years. We normally keep the other records for the periods listed so reports can be checked and verified; that is our usual practice, not a guarantee. If we close or sell the business, the notice and transfer rules above apply.
If we suspect a data breach, we’ll contain it and assess it promptly (within 30 days at most). If it’s likely to result in serious harm, we’ll notify affected individuals and the OAIC as soon as practicable, under the Notifiable Data Breaches scheme.
Access, correction and complaints
You may request access to, or correction of, the personal information we hold about you. This right belongs to you personally, as a User, not to the Client. Email contact@vericlass.io. We’ll verify your identity and respond within 30 days. There’s no fee to make a request. If we refuse, we’ll give reasons in writing. A signed report can’t be edited, but where an error is shown we’ll issue a corrected or superseding report, or attach your statement to the record.
To complain about how we’ve handled your personal information, email contact@vericlass.io with the details. We’ll acknowledge it within 5 business days, investigate, and give you a written response within 30 days.
Contact us
Vericlass Pty Ltd (ABN 16 701 124 870, ACN 701 124 870). Email contact@vericlass.io for privacy questions, requests and complaints.
Cookies
We use cookies and local storage to keep you signed in. Our payment provider Stripe sets fraud-prevention cookies on payment pages. Our map provider, Mapbox, is used for Australian address search and for the site map on a report. When you type an address, your browser sends that text, your IP address and basic browser details to Mapbox in the United States, which keeps IP addresses in its logs for 30 days. The site map is created by our servers and saved in the report as a picture. Mapbox does not set cookies on this website. We don’t use advertising or cross-site tracking cookies.
Changes
We will update this policy when our data practices change. Previous versions are available on request. For material changes, we’ll give at least 30 days’ notice by email and on vericlass.io before they take effect.