Privacy policy

Your data, without the fine print.

NZ Accredited Employer Inspector reads a small amount of public employer context only when you ask it to run a check. It does not read your LinkedIn or SEEK account identity.

Effective
6 August 2026
Operator
· Auckland, New Zealand

01 · Summary

Plain-language summary

We process

A random installation UUID and the employer identity visible on a supported LinkedIn or SEEK page.

We do not process

Your LinkedIn or SEEK account identity, credentials, messages, applications, contacts, or private profile data.

We use it for

Accreditation lookup, rate limiting, result provenance, and community-confirmed employer associations.

We never use it for

Advertising, behavioural profiling, data brokerage, or selling personal data.

The extension waits for an explicit click on Check NZ accreditation. It does not automatically send a lookup when a supported page loads and does not collect general browsing history.

02 · Data

Data the extension processes

Random installation identifier

On first use, the extension generates a random UUID and stores it in Chrome’s local extension storage. The UUID is sent in the X-Client-ID request header to nzaei.zemo.bio. It is used to apply rate limits and distinguish one installation’s community confirmation from another.

The raw UUID is not derived from a LinkedIn or SEEK account. Before a community confirmation is persisted in the application database, the API stores a SHA-256 hash rather than the raw UUID.

Supported-page employer context

The extension reads only the fields needed to identify the employer shown on the supported page:

  • the employer or company display name;
  • a public company identifier, such as a LinkedIn company slug, SEEK company path, or normalized SEEK advertiser name;
  • the public company URL, when that page provides one;
  • the platform and page type; and
  • an NZBN selected by you when you confirm an employer association.

These fields are sent to https://nzaei.zemo.bio/api only as part of a user-triggered accreditation check or confirmation.

Official accreditation results

When fresh official data is needed, the extension sends the employer-name or NZBN query directly to Immigration New Zealand’s public lookup service. It may then send the returned employer name, trading name, NZBN, accreditation expiry, and response context to nzaei.zemo.bio for validation and display to extension users.

Optional release-notification email

The landing page—not the extension—offers an optional one-message release waitlist. If you submit an email address, it is used only to tell you when the Chrome Web Store version is ready.

03 · Purpose

How the data is used

  • Accreditation lookup: match the employer shown on a supported page with public Immigration New Zealand accreditation records.
  • Rate limiting: reduce automated abuse and keep the public API available.
  • Community confirmation: remember which official NZBN an installation selected for a LinkedIn company or SEEK advertiser and aggregate confirmation counts.
  • Result quality: show where a match came from, when official data was last verified, and whether another confirmation is required.
  • Service operation: diagnose failures using request IDs and operational events that deliberately omit the raw UUID, employer name, company identifier, and public URL.

Data is not used for any purpose unrelated to these user-facing features.

04 · Sharing

Sharing, sale, and advertising

Data sent to nzaei.zemo.bio is processed by the project’s Cloudflare Worker and D1 database. Cloudflare provides the hosting, network security, rate limiting, logging, and database infrastructure needed to operate the service.

When a live lookup is required, the extension sends an employer-name or NZBN query directly to Immigration New Zealand’s public lookup service. The project does not send your installation UUID to Immigration New Zealand.

Community confirmation totals and employer associations may be returned to other extension users. The raw UUID, stored UUID hash, and an individual installation’s identity are not exposed in API responses.

No sale. No ads. No data brokerage.

We do not sell data, share it with advertising networks, or use it for targeted advertising, credit decisions, or unrelated profiling.

05 · Retention

How long data is kept

DataRetention
Local installation UUID

Stored in Chrome local extension storage until the extension is removed, its storage is cleared, or a replacement UUID is generated because the stored value is missing or invalid.

Raw UUID in API requests

Processed during the request for rate limiting and hashing. It is not intentionally written to the application database or application event logs.

Hashed UUID and community confirmation

Retained while the community-association feature operates, until the related data is no longer needed, or until a valid deletion request can be matched to it.

Employer name, company identifier, and public URL

Retained with the platform identity while the lookup and community-association service operates, or removed earlier when no longer needed or following an applicable deletion request.

No-published-match observation

Used for no more than 24 hours. Its stored fields may remain until replaced or cleared, but the API ignores the observation after the 24-hour expiry.

Official employer records

Retained while the service operates and updated or replaced as newer Immigration New Zealand data is accepted. These are public business accreditation records.

Release waitlist email

Retained until the one release notification is sent or you request deletion, then deleted from the active waitlist within 30 days after the notification campaign ends.

Infrastructure providers may temporarily retain network and operational metadata under their security and service-retention settings. Application events are designed not to include the raw UUID or supported-page identity fields listed above.

06 · Security

How data is protected

  • Extension requests to nzaei.zemo.bio and Immigration New Zealand use HTTPS.
  • The API validates request schemas, limits body size, applies rate limits, and disables response caching.
  • The raw installation UUID is hashed before a community confirmation is persisted in D1.
  • The extension, API, database schema, and tests are open source and publicly reviewable.

No internet service can guarantee absolute security. If you believe you have found a security or privacy issue, please contact the project operator.

07 · Your choices

Deletion requests and contact

You can stop future extension processing by removing the extension or clearing its local storage. You may also ask for stored waitlist, platform identity, or community-confirmation data to be deleted.

Email [email protected] with the subject NZ Accredited Employer Inspector privacy request. Include the supported public company URL and approximate check or confirmation date when relevant. Because the service does not collect your account identity, additional context—and in some cases the installation UUID—may be needed to locate an anonymous hashed confirmation. Do not send passwords, cookies, or account credentials.

Requests will be handled as reasonably practicable. If data cannot be linked to you without collecting additional identifying information, the operator will explain that limitation.

Privacy contactZemo AiAuckland, New Zealand
Email a privacy request

08 · Changes

Changes to this policy

This policy will be updated when the extension’s data practices materially change. The effective date at the top of the page identifies the current version. The public repository provides a history of policy changes.

Review the open-source project