Last updated: 6th October 2026
Zink Creative Pty Ltd ("Zink", "we", "us", "our") operates the Zink platform (the Platform) a tool that helps creatives (including photographers, videographers and creative teams) manage projects, collaborate, and access job opportunities.
This Privacy Notice explains how we collect, use, disclose, and protect your personal information when you:
We use your information to:
When registering or in your account settings, you may choose:
"Would you like to be searchable for Zink jobs?"
By selecting "Yes," you give Zink permission to process your role, location and profile details for job-matching.
You may withdraw consent at any time through your settings or by contacting us. Withdrawing consent does not affect processing completed before your withdrawal.
If you opt in to job-matching:
We will never:
Your data may be processed in countries outside your home region (including Australia, the UK, EU, and others). Where required, appropriate safeguards such as Standard Contractual Clauses (SCCs) are used.
We retain personal information only as long as necessary for the purposes described or as required by law. If you withdraw job-matching consent, we will stop matching you to opportunities and delete or anonymise related data when no longer needed.
Depending on your jurisdiction, you may have the right to:
You retain full ownership and copyright of all creative content you upload or share on the Platform. This includes photos, videos, project files, text, audio, and any other creative material.
Zink will never use your creative content for marketing purposes without your explicit permission. This includes:
If we ever wish to feature your work, we will ask you directly and obtain clear written consent. No consent = no use.
Zink does not use your creative content or personal data to train any internal or third-party artificial intelligence or machine learning models.
This includes all forms of user generated content:
If you choose to connect Zink to a third-party AI assistant such as ChatGPT or Codex, Zink may provide that service with the workspace information needed to complete the requests you make through the connection. Depending on your request and Zink permissions, this may include project, client, crew, schedule, task, invoice, activity, and financial reporting information.
The connection uses your authenticated Zink identity and selected organisation. Zink applies your current role and organisation AI controls to each request. Connected assistants do not receive your Zink password, and they cannot use tools or records that your account is not authorised to access.
The connected service processes information under its own terms, privacy policy, workspace settings, and data controls. You can remove the connection from that service or contact Zink support for help.
If you choose to connect a WhatsApp Business account, Facebook Page, or Instagram Professional account, Zink uses the account and business asset information permitted by Meta to provide the integration features you select. This may include asset identifiers, account names, granted permissions, message content, and message delivery events.
Zink stores access credentials encrypted on the server and does not expose them in the browser. We do not use a connected Instagram account to extract a general follower or following list.
You can disconnect a Meta account from Settings > Integrations. Disconnecting stops new access through that connection. You may also follow our Meta data deletion instructions.
WhatsApp messages are sent only for purposes allowed by Meta and applicable law. Where consent is required, you may withdraw it using the method provided when you opted in or by contacting Zink.
When you connect Gmail, Zink uses your Google account identifier and email address to identify the connection. With your permission, Zink reads message headers, recipients, subjects, message content, thread identifiers, and attachment information to display and search email and link selected conversations to projects. Send permission lets you send an email or reply through Zink. Zink does not request permission to modify or delete your existing Gmail messages.
Google handles sign-in and consent; Zink does not receive your Google password. Gmail access and refresh tokens are encrypted using AES-256-GCM before storage on our server. Tokens are used on the server and are not returned to the browser by the Gmail integration. Requests to Google use HTTPS. Signed, time-limited OAuth state helps protect the connection process from tampering.
Zink checks the signed-in user and organisation before granting access. Personal connections are available to their owner; company connections are shared within the organisation. When you attach a conversation to a project, its visibility setting controls which authorised project users can read that conversation. Attaching a conversation does not grant those users access to your whole inbox.
AI access is off by default for a new Gmail connection. If you enable it and use a connected AI assistant, relevant email content and metadata can be sent to that assistant to fulfil your request, such as finding a conversation or preparing a reply. Review the assistant provider's data controls before enabling access. Sending through the AI workflow requires confirmation of the message and recipients and is restricted to your own connected account.
The Gmail integration retrieves conversations from Google when requested. It stores connection details and project conversation references, including sharing settings, rather than a separate mailbox archive. Content you include in a project, an AI conversation, or a send request may also be retained as part of that feature's records. Disconnecting Gmail removes the stored access and refresh tokens and stops further access through that connection; it does not delete Gmail messages or automatically erase existing connection records, project references, or AI conversation records. You can remove project conversation links, revoke Zink's permission in your Google Account, or contact admin@zink.ltd to request deletion of retained Zink data, subject to applicable retention obligations.
Zink's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Gmail data is used to provide the user-facing integration features described here, not sold, used for advertising, or used to train general-purpose AI models.
For questions about this notice or to exercise your rights:
Check your connection. If this continues, refresh to load the latest version. Save or copy any unsaved work first.