VERI5ME
SERVICE TERMS

Terms & Conditions

Last updated: 11 July 2026. These terms cover Veri5me web, API, admin, provider, billing, and mobile verification workflows.

Important Production Conditions

These platform terms are implemented product copy for operational use and should receive final Australian legal approval before regulated production launch. They do not replace a signed enterprise order form, data processing addendum, partner agreement, or provider-specific terms.

Business Customer Terms

  • Business customers may request checks only for a genuine employment, contractor, onboarding, tenancy, property, compliance, or risk-management purpose that has been disclosed to the candidate.
  • Customers must choose checks that are proportionate to the role or purpose and must not use reports for unrelated decisions, discriminatory screening, or excessive information collection.
  • Adverse, exception, disputed, or unable-to-verify outcomes must be reviewed for relevance before a customer makes a decision about the candidate.
  • Customers are responsible for configuring lawful templates, notices, retention settings, API/webhook access, and internal user permissions.

Candidate Terms

  • Candidates can review the request purpose and check categories before providing consent, submit evidence, track progress, and access reports or shared-report controls where enabled.
  • Candidates must provide accurate information and evidence. Veri5me may pause processing where identity, consent, document quality, fraud, provider, legal-hold, or dispute concerns require review.
  • Candidates can request access, correction, dispute review, or withdrawal through the platform. Withdrawal may be limited after provider processing, report release, legal hold, or regulatory retention has started.
  • Candidate self-checks are candidate-owned workflows. Sharing, refresh, wallet, or retention features are governed by the pricing and controls shown at purchase.

API And Enterprise Terms

  • API clients must use issued credentials, scoped keys, idempotency keys for write operations, allowlisted IPs where configured, and signed webhooks for authorised verification workflows only.
  • Enterprise customers can configure white-label presentation, SSO metadata, HRIS/ATS sync settings, webhook delivery, usage billing, retention policy, and MFA policy from the admin surfaces.
  • Customers must secure webhook receivers, rotate compromised keys promptly, validate Veri5me webhook signatures, and avoid sending unnecessary sensitive data in metadata fields.
  • Usage billing, overage fees, prepaid credits, invoice delivery, and purchase-order requirements are governed by the plan, order form, or admin billing configuration shown in the platform.

Property, Tenancy, And Regulated Checks

  • Property, title, landlord, and tenancy workflows may be used only for legally permitted purposes and may require additional notices, source access approval, and jurisdiction-specific review.
  • Tenant screening must not include consumer credit reports unless separate legal obligations, source permissions, notices, adverse-action workflows, and review controls are implemented.
  • Police/criminal-history, official identity, work-rights, title, watchlist, and other regulated checks require the relevant accredited partner, approved data source, or provider pathway before production activation.
  • Regulated workflows may be disabled, routed to manual fallback, or blocked until provider approval, security review, privacy review, and legal approval are recorded.

Pricing, Payment, Invoices, Credits, And Refunds

  • Quotes show selected items, GST, provider-cost snapshots, Stripe fee estimates, margin snapshots, terms version, expiry, and the payer responsible for the workflow.
  • Payment activates the paid workflow. Stripe Checkout may collect card, Apple Pay, Google Pay, and other wallet methods supported for the customer, device, and Stripe configuration.
  • Invoices, refunds, payment disputes, prepaid credits, and usage-billing records are stored in the billing ledger and may also appear in Stripe records where live Stripe keys are configured.
  • Refunds and cancellations are assessed against workflow state, provider costs already incurred, whether a regulated third-party check has started, customer fault, system fault, duplicate payment, and Australian Consumer Law rights.

Reports, Disputes, And Corrections

  • Reports are factual verification outputs based on selected checks, candidate evidence, provider results, agent review, and QA controls. They are not legal, migration, credit, or employment advice.
  • Candidate disputes or correction requests may pause report release, apply a compliance hold, trigger QA/admin review, and preserve relevant evidence until the request is resolved.
  • Report sharing is controlled by active share tokens, expiry, revocation, and signed download URLs where enabled. Customers must not redistribute reports beyond the disclosed purpose.

Transactional And Marketing Messaging

  • Transactional messages include account security, consent, evidence, workflow, referee, payment, refund, dispute, provider, and report milestones needed to deliver the service.
  • Marketing messages are separate, optional, and preference-based. Users can opt out of marketing without disabling required transactional, security, billing, or workflow notices.

Complaints

Complaints about privacy, billing, candidate treatment, provider outcomes, or report accuracy can be raised through support or the candidate action workflow.

Contact

General support: hello@updates.veri5me.com.au. Privacy and candidate requests: privacy@veri5me.com.au.