Skip to content
vendarity.
How it worksUse casesPricingInsightsTrustFAQHelpAboutContact
Sign inStart freeStart free

Legal

Privacy Policy

Version 1.10 · Effective 18 November 2026

This policy explains how Oceanx Consulting Pty Ltd (ABN 67 615 055 368), trading as Vendarity (“we”, “us”), handles personal information when you visit vendarity.com, use a Vendarity workspace, or respond to a document request through the supplier portal.

In short

  • Businesses (our customers) use Vendarity to collect and review supplier documents. For those records, the customer decides what is collected and we process it for them.
  • The application runs on a Hostinger VPS in Malaysia (Kuala Lumpur); files are stored in a private Backblaze B2 bucket in US East (us-east-005). This is not Australian-only hosting.
  • We do not sell personal information, show advertising or use advertising trackers.
  • AI-assisted review is each workspace’s choice and can be turned off at any time; a person confirms the details before any document is accepted.
  • A closed workspace stays read-only for 30 days, then is deleted; recovery copies expire within 35 more days.

On this page

  1. Who is responsible for your information
  2. What we collect
  3. How we use information
  4. AI-assisted review
  5. Email and SMS
  6. Who we share information with
  7. Where information is processed
  8. How we protect information
  9. How long we keep information
  10. Your rights and how to use them
  11. Country-specific information
  12. Cookies and browser storage
  13. If something goes wrong
  14. Supplier library
  15. Children
  16. Changes to this policy
  17. Questions and complaints

1. Who is responsible for your information

Customer workspace records. When a business (“the customer”, also called the buyer) uses Vendarity, it decides which suppliers, contacts, documents and decisions to record. For that information the customer is the controller (in the United States, the “business”) and we act as its processor or service provider under our Data Processing Addendum. If you are a supplier contact or an auditor invited by a customer, that customer is responsible for your workspace records, and privacy requests about them go to the customer first. We help the customer answer them.

Our own records. We are the controller for the information we need to run Vendarity as a business: buyer user accounts and sign-in security, the customer relationship and billing records, website traffic, support, and the cross-workspace records that keep a supplier contact’s sign-in identity and SMS opt-out working for every customer that contacts them.

Supplier library. An optional feature lets a supplier company keep its own document library and share chosen versions with buyers. We are the controller of the library records the supplier owns, as the supplier library section describes.

2. What we collect

Buyer users (workspace members)

  • Name, work email, company name, company country, password (stored only as a one-way hash), email verification, authenticator-app enrolment and recovery codes.
  • The page, source and campaign of the link that brought you to sign up (for example a template page, a supplier request or a partner’s page), to set up your workspace and count where sign-ups come from. No cookie or identifier is used to learn it; we count sign-ups and verified emails only as daily totals.
  • If you start a workspace from a supplier request page after entering a code there, the address you proved is used as your verified account address, and we record, for our own analysis only, which workspace’s request led you to sign up. That business is not told.
  • Sign-in sessions with their time, IP address and browser details, which you can review and revoke on the Security page; rate-limit counters for sign-in and signup attempts.
  • For each workspace you belong to, when you last signed in to it and whether you have set up an authenticator, which that workspace’s Owners and Admins can see (never your devices, IP addresses or use of other workspaces).
  • Your workspace role, invitations, notification preferences and the actions you take, which are kept in the workspace’s activity history.
  • If an Owner or Admin invites you, your email address, the role you are invited as and who invited you. We email you the invitation, which names the person who invited you and the workspace; it can be used for seven days.
  • The Terms, Data Processing Addendum and Privacy Policy versions you accepted at signup, and when.

Customer organizations

  • Legal and display name, country, business identifier and any tax identifiers you enter, billing address, timezone, sites, logo, retention choice, plan and billing state, and, for workspaces created before 16 November 2026, an optional answer to “How did you hear about Vendarity?”.
  • If an Owner or Admin shares a status page: the recipients’ email addresses; the email we send each of them with the link, which names the person who shared it and the workspace; the one-time codes we email them and their short sessions; and, for that customer, when each recipient viewed the page or downloaded a document. The customer can erase a recipient’s address at any time; we create no account for recipients.
  • If an Owner or Admin connects Xero, Vendarity asks Xero for read-only access to the organisation’s contacts. When you choose suppliers to import, it reads their name, email address, tax number and contact person, and keeps only the suppliers you confirm. It stores the Xero organisation’s name and encrypted access tokens until you disconnect, which deletes them.
  • If an Owner or Admin tells us why they cancelled a paid plan: the reason, the plan, the month and any comment, with links and email addresses removed, kept without the workspace’s name.
  • If the workspace was created with a partner’s or customer’s referral code: which partner or workspace referred it, and when. The code is recorded once, when the workspace is created.
  • Billing information: the Stripe customer and subscription identifiers, plan, status, invoice references, amounts and currency (and any amount Stripe reports in another currency), tax treatment and totals, tax identifiers you enter and whether they were verified, the billing country and address as Stripe returns them, and whether a payment method exists. We never receive card details.

Partners

  • If you join the partner programme: your name, business, work email and country, the code we give you, the Partner Programme Terms version you agreed to, your tax details (an Australian ABN, or a US W-9 or W-8BEN form), the bank details you give us to pay you, and the commission we calculate and pay you.

Supplier contacts and auditors (on the customer’s behalf)

  • Name, email address and, if the customer records it, a mobile number; timezone; email and SMS permission, pauses and opt-outs with their source and time; and any report that a request email was unexpected.
  • One-time sign-in codes and portal sessions (short-lived), documents and answers you submit, messages and questions, and the activity history of what was requested, submitted, viewed and decided.
  • If a customer shares an evidence pack with you as an auditor: the invitation we email you for them, with the link, which names the person who shared it and the workspace.
  • Where the business uses send-only links, anyone who has a request email can use its link to send files without a code. We keep each file, when it was sent and, if the sender types them, the name and email they give, for the business’s review, marked as sent without a code. Nothing can be read through such a link.
  • If you hand a request to someone else, the address you type receives one email from us with a link that can only send files. The address is kept with the request’s history and erased with your contact record.
  • If you ask to be emailed the result, we send one email to the request’s address when the business decides.
  • If you answer “How easy was that?”: your score and any comment, with links removed. The business sees only its average once five suppliers have answered; Vendarity’s team reads comments to improve the service. They are never published, are not part of the business’s account export, and are erased with your contact record.
  • If you tick “Remember this browser for 30 days” after entering a code, your browser keeps a random secret in a cookie and we keep only a one-way hash of it, linked to your contact record, so links sent to you open in that browser without a new code. It ends after 30 days, when you choose “Forget this browser” or clear your cookies, or when the business removes you as a contact, changes your email address, ends one of your links or closes its workspace.
  • Documents can contain personal information, such as a name or signature on a certificate. Do not upload medical records, government identity documents, payment-card details or employee credentialing records; the service is not designed for them.

Email forwarded to a workspace’s address

  • Anyone who has a workspace’s forwarding address can send email to it. For each email we keep the sender’s address as the email states it (not verified), the subject, when it arrived, the names of its attachments and up to 10 of its PDF, JPEG, PNG or WebP files; we do not keep the email’s text. The sender, subject and file names stay with the workspace’s records until the workspace is deleted.

Website visitors

  • Connection information that Cloudflare and our server need to deliver and protect the site (IP address, browser and request details). Our web server does not keep access logs.
  • The free expiry check at /renewal-preview reads your file only inside your browser. If you choose “Keep this list”, the supplier names and contact details from that file stay in your browser’s local storage for up to 7 days so you can import them after you sign up; they are not sent to Vendarity until you import them, and “Forget the kept list” removes them.

Setup requests and partner pages

  • If you ask us to set Vendarity up for you, we keep your name, work email, company, number of suppliers and how you track documents today, to reply to you. We delete it after 24 months.
  • A partner’s page at vendarity.com/with/ shows the name, text and logo the partner gave us; we store and serve the logo ourselves.

Page views and emails from Vendarity

  • Where Vendarity counts page views, it counts them by day: the page’s address, the website that linked to it and the campaign tag in the link. It sets no cookie and keeps no IP address, browser details or anything else that identifies a visitor.
  • If you ask for the renewal checklist, we email you a link to confirm and send nothing else until you do. Then we send five emails over 14 days. Each has a one-click unsubscribe, and you can erase your address from the unsubscribe page or by writing to us. We delete the address 30 days after the last email, after you unsubscribe, or 30 days after an unconfirmed request.
  • The Owner of a new workspace gets up to four setup tips by email, each once, which they can turn off; Owners and Admins get a weekly summary, which names suppliers and requirements and which each can turn off.

Free certificate check

  • Where Vendarity offers it, anyone can ask us to read one certificate without an account, at vendarity.com/tools/certificate-check or by email. We receive the file, its name and, for an email, the sender’s address. We scan the file for malware and, if it is clean and no longer than four pages, send its page images and text to Google’s Gemini service to read the details it shows. We show the result only to the person who sent it, on their screen or in one email reply, and never publish it.
  • The file, its name, what was read and any sender’s address are deleted within one hour, and at once when the person keeps the certificate in a new workspace or chooses “Delete it now”.
  • To limit the check to three files a day for each network or email address, we keep for 25 hours a code made from that address with a key held only in our servers’ memory, from which the address cannot be recovered; we never store the address itself. We answer an email only when it passes the sender’s domain checks (DMARC), and never automatic replies or mailing lists. We rely on the consent ticked before the upload and our legitimate interest in providing the tool the person asked for.

3. How we use information

  • To provide the service: accounts, access control, document requests, reminders, change requests and messages, file scanning and previews, review, reports, exports and support.
  • To keep it secure: authentication, multi-factor authentication, rate limits, abuse detection, malware scanning and tamper-evident activity records.
  • To prevent misuse of supplier messages: if someone who receives a request email reports it as unexpected, we record the report against that email, pause the sending workspace’s supplier emails and texts and review it. We monitor bounces and spam complaints on each workspace’s supplier emails and may pause them automatically while we review.
  • To run the business: billing, tax and accounting records, and answering questions and complaints.
  • To improve the product: first-party measures of how the service is used, such as workspace milestones (for example, the first accepted document), how many phone photos a sent file was made from, and how long a supplier took from opening a request link to sending. They never include document or contact contents.
  • To meet legal obligations and enforce our Terms.

Where UK data protection law applies to our own records, we rely on: performing our contract with you or your employer; our legitimate interests in running, securing and improving a business service; and legal obligations. We do not send marketing email or SMS. If that changes, we will ask first where the law requires and every message will include an unsubscribe.

We never use customer documents or workspace records to train AI models, and we do not make automated decisions that have legal or similarly significant effects on people. Evidence is accepted or rejected by a person.

4. AI-assisted review

AI-assisted review is optional. A workspace can turn it on when it is set up, where the choice is offered ticked, or an Owner or Admin can turn it on after reading a disclosure; they can turn it off at any time. While it is on, when a document passes its security scan, or when a reviewer asks for suggestions on a document that was not read, we send that document’s page images and text to Google’s Gemini API under Google’s paid-service terms. The answer is a set of suggested fields (such as issuer and expiry date). A person reviews them with the document and confirms or corrects them, and resolves any required field that is missing or uncertain, before the document can be accepted.

We send requests with Google’s stored-interactions setting off and with no search or tools enabled. Google’s terms say that for paid services Google does not use prompts, files or responses to improve its products, and that it logs them for 55 days solely to detect and prevent breaches of its Prohibited Use Policy. Authorized Google staff can review logged data for that purpose, and Google says it is not used to train models other than those used for policy enforcement. Google may store the data transiently or cache it in any country where it has facilities. We cannot delete Google’s copy sooner. See the Gemini API terms and abuse-monitoring policy.

While AI-assisted review is on, a member can also ask a question about the workspace in plain English. We send only the question’s text and today’s date to the same Gemini API, under the same terms; the answer is a search filter, which Vendarity runs itself inside that workspace. No workspace record is sent with a question. Each new question uses one unit of the workspace’s AI allowance; repeating an earlier question reuses its answer.

While AI-assisted review is on, a member can also ask for a short summary of the workspace’s daily brief. We send only today’s date and each of the brief’s counts with its label, such as the number of submissions awaiting review, to the same Gemini API, under the same terms. No supplier name, document, contact or note is sent, and we show the summary only if each sentence matches one of the counts. Each new summary uses one unit of the workspace’s AI allowance.

Suggestions, corrections, questions, summaries and the reviewer’s decisions stay in that workspace. The sample workspace never sends anything to AI.

5. Email and SMS

We send these emails through Resend: account emails (verification, password reset and account notices); team invitations, and the links to status pages and evidence packs that an Owner or Admin shares, to the addresses they enter; the notification emails that workspace members choose to receive; and, for customers, supplier request and reminder emails. For a supplier library, we email its members their sign-in codes and tell the person who set it up whether we approved it. When a team member chooses, we also email a supplier’s main contact that the customer has asked for changes to a document or sent a message about a requirement, with the customer’s reason or message. Customers set the reminder schedule within our limits. We send these supplier emails and texts only on weekdays between 9:00 and 17:00 in the contact’s time zone (or the workspace’s, if the contact has none), and we limit how often each contact is contacted. A supplier contact can pause routine email in the portal; security codes still arrive.

We send SMS reminders through Cellcast only to mobile numbers in countries whose route is switched on; the SMS Messaging Terms list them. A supplier contact receives SMS only after agreeing themselves in the supplier portal or, for a United States or Canadian number, on the page linked from a request email; a business cannot agree for them. We record when and how each agreement was given and, for a US or Canadian number, the exact wording shown. Each business sends a contact at most 1 message a day, on weekdays between 9:00 and 17:00 in the recipient's time zone. Every message ends with a short vendarity.com link whose page opens the requests (the emailed code is still needed) or stops texts; US and Canadian messages come from our own number and also say to reply STOP.

We do not sell, rent or share mobile numbers or SMS opt-in consent with third parties or affiliates for their marketing or promotional purposes. The business that requested your documents can see whether you agreed, and our SMS provider receives the number and message text only to deliver messages. Otherwise we disclose them only where the law requires.

6. Who we share information with

  • Within a workspace: members see what their role allows. Suppliers see only their own requests, the messages shared with them and any evidence a customer chooses to share with them. Named auditors see only the fixed evidence pack shared with them. A customer can keep and export what you submit, and revoking access cannot recall a copy someone has already downloaded.
  • Your own calendar: a member can subscribe their own calendar app to a private link of upcoming renewal dates, or download them as a file. The events include the supplier, requirement, site and workspace names unless that member leaves them out, so their calendar provider (for example Google, Microsoft or Apple) receives those names and keeps them under its own terms. Without names, each event says only that a supplier document renewal is due and why (an expiry or a review date). Turning the link off stops updates at once but cannot remove copies already in that calendar.
  • Stripe and Link: for paid subscriptions they act as merchant of record and decide their own use of transaction data under their own privacy policies. Receipt and invoice emails come from Link.
  • Partners who referred you: if your workspace was created with a partner’s code, that partner may learn that your business signed up and, where it earns a commission, your plan and the invoice amounts its commission is based on. A customer’s referral link shows the business it refers the referring workspace’s name; nothing else is shared either way.
  • Service providers that process data for us under contract, listed with their purpose and location on the Subprocessors page.
  • Our support staff, who see account metadata only (names, counts and dates, not supplier records or files). They can open evidence only while a workspace Owner or Admin has granted time-limited support access (1 to 72 hours), and every view and download is shown in the customer’s activity history.
  • Authorities and advisers, when the law requires it, to protect people or the service, or to our professional advisers under confidentiality.
  • A buyer of our business, if we sell or restructure it, under the same protections.

We do not sell personal information and do not share it for cross-context behavioural advertising.

7. Where information is processed

The application server and database run on a Hostinger VPS in Malaysia (Kuala Lumpur). Evidence files are stored in a private Backblaze B2 bucket in US East (us-east-005). This is not Australian-only hosting. Our confirmation of the data centre with Hostinger is pending; the location stated is measured from the server’s network registration. Web traffic passes through Cloudflare’s global network. Email is handled by Resend in the United States. If a workspace uses AI-assisted review, Google may process each document it reads in any country where it has facilities. Independent backups keep encrypted recovery copies of the database and of stored files in a separate Backblaze B2 account in Backblaze’s US East region (us-east-005), apart from the account that holds the evidence files.

This means personal information from Australia, New Zealand, the United Kingdom and Canada is processed outside those countries. Before sending it, we take the steps those laws require: we use providers bound by written data protection terms, keep their access to what they need, and protect data in transit and at rest as described below. For UK personal information, our Data Processing Addendum includes the UK International Data Transfer Addendum. In Australia we remain accountable under the Australian Privacy Principles for how overseas recipients handle the information we disclose to them.

8. How we protect information

  • HTTPS for all traffic; secure, HttpOnly cookies; a restrictive content security policy; private pages are never cached.
  • Workspace separation enforced by the database itself (row-level security) as well as by the application, with separate least-privilege database roles.
  • Authenticator-app multi-factor authentication required for workspace Owners, Admins and our operators, and for every member of a workspace that requires it, before they reach real data; re-authentication for exports and closure.
  • Uploaded files are held in quarantine, scanned for malware in an isolated sandbox, and only then copied to a separate storage location. Evidence files are encrypted at rest by Backblaze (AES-256) in a private bucket. Downloads are streamed through Vendarity after checking the person’s current access, so revoking access blocks later downloads at once (it cannot recall files already downloaded).
  • Decisions and activity are append-only for the application, and a signed daily digest makes later changes detectable.

No system is perfectly secure. We do not hold SOC 2, ISO 27001 or other certifications. Encryption of the database disk is not yet verified. The Trust page describes current limits.

9. How long we keep information

Evidence in an active workspace

A document that still supports a current requirement is kept. Superseded, rejected or withdrawn documents, and documents of an archived supplier, are erased 5 years later by default; the customer can choose 1, 3, 5 or 7 years. Erasure removes the original file, previews, extracted text and AI suggestions; the review decisions stay in the history. A legal hold pauses erasure. A file that a retained supplier declaration cites is kept until that declaration’s own retention ends; a declaration’s answers stay in the history, as review decisions do.

Files that never became evidence

Unfinished uploads expire after 24 hours, and the quarantine copy of a scanned file is removed after 24 hours. Blocked or failed files are deleted after 7 days. Files from email replies, and from emails forwarded to a workspace’s address, that no one places are deleted after 14 days (dismissed ones at once). Reply text is deleted after 30 days; no text of a forwarded email is kept. The sender, subject and file names of a received email stay with the workspace’s records until the workspace is deleted. Export downloads expire after 7 days. Erasing a contact also withdraws at once every finished account export and every evidence pack that covers that contact’s supplier.

Sign-ups never verified

A sign-up whose email address is never verified is deleted, with its sign-in records, 30 days after it was made.

Closing a workspace

When an Owner closes the workspace, or a Free workspace is closed after 12 months with no sign-in, it becomes read-only for 30 days. A trial or paid plan that ends moves the workspace to the Free plan, and nothing is deleted for not paying: a payment that is never made makes a paid workspace read-only 3 days after the failed payment until it is paid or the subscription ends, when it moves to the Free plan. During a closure’s read-only time Owners and Admins can still export everything, and a returning customer can resume. We email Owners and Admins when it starts, 7 days before deletion and 1 day before deletion. Then we delete the workspace from the live service: its records, original files, previews, extracted text, access grants and history, and the one-time sign-in identities of its suppliers and auditors that no other workspace uses.

Recovery copies of the database expire within 35 days after they are made, so deleted data can remain in recovery copies for up to 65 days after the read-only period begins. If a copy is ever restored, recorded deletions are applied again before anyone regains access, so deleted data does not return.

Partner records

We keep a partner’s details while they take part. After the last commission payment we keep the payment and tax records for five years, as Australian tax law requires, and delete the rest. A partner’s code stays on the workspaces it referred until each is deleted.

What we keep after deletion

  • A closure record without names: the reason, country, dates and payment-provider references, and the deletion records needed to stop restored copies bringing data back.
  • The Stripe customer and subscription references in the closure record. Stripe, as merchant of record, keeps the invoices and tax records for those sales, for as long as the law requires.
  • A keyed one-way code of any mobile number that stopped Vendarity texts, so the stop keeps working for every business (see the SMS Messaging Terms).
  • Your personal sign-in account, so you can join or create another workspace, until you ask us to delete it.
  • Information under a legal hold, and short-lived security logs (application logs are size-limited and rotate).
  • Copies held by providers under their own terms, such as emails Resend sent or received, Google’s 55-day abuse-monitoring log and Cellcast’s message records for text messages sent. We cannot promise immediate deletion from every provider.

10. Your rights and how to use them

Depending on where you live, you can ask to access, correct, delete or receive a copy of your personal information, object to or restrict some uses, withdraw consent, and complain. Many of these work directly in the product:

  • Copy or export: an Owner or Admin can export the workspace’s records and original files from Settings → Data & closure → Export all data, including while the workspace is read-only. The export lists what it leaves out and why, such as each member’s private saved views, Vendarity’s own product analytics, operational queues and secret tokens; attachments of email replies and forwarded emails that no one placed on a requirement are listed without their files.
  • Correct: Owners, Admins and Managers correct supplier and contact details, and Owners and Admins correct company details, in the workspace; earlier values stay in the history. To correct your own sign-in name or email, contact us.
  • Delete: an Owner can close the workspace (deleted after 30 days). Customers can archive suppliers and remove contacts; a removed contact’s name stays in decision history until the workspace or the record is deleted under the schedule above. An Owner or Admin can also erase a supplier contact’s name, email address and phone number, including while the workspace is read-only; the same person’s other contact records in that workspace are erased with it. The contact then appears as “Former contact” with a number wherever Vendarity shows it. Records of what happened, such as messages, reviews, decisions and delivery and consent records, keep their dates and outcomes but no longer show the person’s details; the original text inside those records is kept, never shown, until the workspace is deleted. Names typed into free text, such as a message or a note, are not changed. Evidence packs and account exports that could contain the contact’s details are withdrawn at once; copies already downloaded cannot be recalled. A mobile number that had stopped texts stays on our SMS stop list as a keyed one-way code, so it is never texted again. To delete your own sign-in account, or an individual record sooner, contact us and we will work through it with the customer.
  • Messages: supplier contacts can pause routine email or SMS in the portal, use the link in any SMS to stop texts from every business on Vendarity, or reply STOP to a US or Canadian message.
  • Sessions: review and sign out other sessions on the Security page.

For workspace records, we pass your request to the customer that controls them, or ask you to contact it directly, and help it respond. To make a request to us, email help@vendarity.com. We may need to confirm your identity and authority. We will acknowledge a request within 30 days and answer within the time your law sets, and we will not treat you differently for using your rights.

11. Country-specific information

Australia

We handle personal information in line with the Privacy Act 1988 and the Australian Privacy Principles, including APP 8 on overseas disclosure, and the Notifiable Data Breaches scheme.

New Zealand

We follow the Privacy Act 2020, including the information privacy principles on overseas disclosure (IPP 12) and telling people when their information is collected from someone else (IPP 3A). Customers that add supplier contacts are responsible for telling those contacts; we help by identifying the customer in every request.

United Kingdom

For our own records we are the controller under the UK GDPR and the Data Protection Act 2018. You can complain to us first and we will acknowledge your complaint within 30 days. You can also complain to the ICO. We have not appointed a UK representative.

Canada

We follow PIPEDA and, for people in Quebec, Quebec’s private-sector privacy law. Personal information may be processed outside Canada and Quebec as described above, and may be available to courts and authorities in those countries.

United States

For customer records we act as a service provider (processor) under state privacy laws such as the California Consumer Privacy Act. In the last 12 months we collected the categories described in section 2 (identifiers, account and security information, commercial and billing information, and documents customers ask us to process) for the purposes in section 3. We have not sold or shared personal information for cross-context behavioural advertising, and we do not knowingly collect information from anyone under 16.

12. Cookies and browser storage

We use only cookies that the service needs: sign-in sessions for buyers, suppliers, auditors, status-page recipients and passport recipients, the selected workspace, a supplier’s choice to remember a browser for 30 days, the single-use code that carries a supplier from a request page to a new workspace (at most 15 minutes), the single-use code of a certificate you chose to keep from the free check (at most 55 minutes), and security checks. The application remembers your light or dark theme in browser storage, and the free expiry check keeps a list there for up to 7 days only if you choose “Keep this list”. A partner’s or customer’s referral code travels in the sign-up link. Where a sign-up came from (the Vendarity page you opened it from, and that page’s source or campaign tag) comes from that link or from the page address your browser sends when you open sign-up from a Vendarity page. Neither is kept in a cookie. There are no advertising or third-party analytics cookies, so there is nothing to opt out of. Cloudflare may set a security cookie to protect the site.

13. If something goes wrong

If we become aware of a data breach that is likely to cause serious harm, we will contain it, assess it promptly (within 30 days at most, as the Australian scheme requires), and notify the affected customers, people and regulators as the applicable laws require. For customer records, we tell the customer without undue delay so it can meet its own obligations; the Data Processing Addendum sets out the details.

14. Supplier library

  • What it is: a verified supplier company keeps its own documents in a private library and chooses, version by version, which buyer relationships receive them.
  • What we hold, as controller: the company’s legal name, country and business identifier; the claimant’s name, email, role and statement of authority; members’ verified email addresses and sign-in records; the documents, their versions and details; and which buyers each version is shared with.
  • Verification: a named Vendarity operator checks the company in a public business register and confirms the claimant’s authority before a library is approved. Similar names or email domains never link two companies.
  • Who sees it: the supplier’s members. A buyer sees only the versions shared with it; when a buyer takes a version into review, its copy becomes that buyer’s record, handled as customer workspace records.
  • Revoking: stops a buyer fetching versions it has not taken and stops future versions. It cannot delete a copy a buyer has already taken; that copy follows the buyer’s own retention.
  • Deleting: a supplier can delete its library documents at any time; the files are erased from live storage and recovery copies expire within 35 days.
  • Closing a library: we keep a library’s records while it is open. A library administrator can ask us at help@vendarity.com to close it; within 30 days we delete its documents as above, disconnect its buyers, and remove its members’ names, email addresses and sign-in records and the claimant’s name and role. We keep the company’s name and register identifier with the history of approvals and closure, without those personal details, so the company can claim a library again.
  • Claims we don’t approve: we delete the claim, with the claimant’s name, email address and role, 12 months after the decision.

Supplier passports

  • What it is: where Vendarity offers it, a supplier contact who has proved their address with a one-time code can keep copies of their own documents in a passport (up to 20 documents and 200 MB) and send a link to any address they choose.
  • What we hold, for the supplier: the kept files and their details, the addresses links were sent to, which customers follow a document, and any reports about a link. We email recipients on the supplier’s behalf and remind the supplier once, 30 days before a kept document expires.
  • Who sees it: a recipient opens a link after a code to their own address, unless the supplier chooses a link anyone can open, which ends after 30 days. Every shared document is labelled as not verified by Vendarity. A customer who follows a document receives a copy, and its renewals, in its workspace for review; that copy becomes the customer’s record, handled as customer workspace records.
  • How long: a passport is kept until the supplier closes it. Closing erases its files and the recipients’ addresses; copies a customer already filed stay with that customer. A customer erasing the supplier as a contact ends that customer’s follows.

15. Children

Vendarity is a business service for adults acting for organizations. It is not directed to children, and we do not knowingly collect their information.

16. Changes to this policy

We will publish any change here with a new version number and effective date. For a material change, we will tell workspace Owners by email before it takes effect.

17. Questions and complaints

To contact us or complain, email help@vendarity.com. Please describe the issue and the workspace concerned, but do not attach sensitive documents. If you are not satisfied with our answer, or at any time where your law allows, you can contact a regulator:

  • Australia: Office of the Australian Information Commissioner (OAIC)
  • New Zealand: Office of the Privacy Commissioner
  • United Kingdom: Information Commissioner's Office (ICO)
  • Canada: Office of the Privacy Commissioner of Canada
  • Quebec: Commission d'accès à l'information du Québec
  • California: California Privacy Protection Agency

Contact

Vendarity is operated by Oceanx Consulting Pty Ltd, ABN 67 615 055 368, Australia. To ask a question, exercise a privacy right or make a complaint, email help@vendarity.com. You can also contact your privacy regulator; the Privacy Policy lists them.

Related: Terms of Service · Data Processing Addendum · Subprocessors · SMS Messaging Terms · Partner Programme Terms

vendarity.

Track supplier certificates and insurance (COIs) before they expire.

Vendarity on X

Product

  • How Vendarity works
  • Plans and pricing
  • All use cases
  • Manufacturing
  • Insurance certificates
  • Recruitment agencies
  • Facilities and property
  • Sample certificate review
  • Free renewal preview
  • Free certificate check

Resources

  • Insights and guides
  • Help centre
  • Frequently asked questions
  • Free templates
  • Compare tools
  • Glossary of terms
  • How to check a document

Company

  • About Vendarity
  • Trust and data
  • Accessibility
  • Partner programme
  • Contact us

Legal

  • Privacy Policy
  • Terms of Service
  • Data Processing Addendum
  • Subprocessor list
  • SMS terms
  • Partner terms
Operated by Oceanx Consulting Pty Ltd · ABN 67 615 055 368 · AustraliaFor businesses in the US, Canada, UK, Australia and New Zealand. In English.