Privacy Policy

Last updated 5 November 2026 · Applies to every Timbre and Co. console

Timbre and Co. collects only what it needs to run its jobs, keeps it on servers in Sydney, encrypts it, and never sells it. This policy follows the Australian Privacy Principles.

1. What we collect

WhatFor exampleWhy
Account detailsName, email, role, password (stored only as a one-way hash) To sign you in and show who did what
Sign-in recordsTime, IP address, browser and device type To protect accounts and spot misuse
WorkProjects, tasks, comments, schedules, shoot locations, files and footage To run the jobs
Clients and contactsNames, businesses, emails, phone numbers, deals and quotes To manage client relationships
EmailsMessages to and from our business mailboxes, linked to the jobs and people they concernTo keep each job's work in one place
Device settingsLight or dark theme, a remembered device, notification permission To make the consoles work on your device

2. How we use it

To deliver our work, contact people about their jobs, keep the consoles secure and meet our legal obligations. We do not sell it, and we do not use it for advertising.

3. AI processing

The consoles send the text of comments, emails and job details to Anthropic's Claude AI to suggest tasks, update dates and keep short job notes. Anthropic processes it under its commercial terms, and does not use it to train its models. People can see, change or undo what the AI does.

4. Google Calendar

Each person can choose to connect their own Google Calendar to the consoles (Calendar → Calendars). Nothing is read from Google until they do, and they can disconnect at any time.

What Google data we access

  • The email address of the Google account they connect, to show which account is connected.
  • The list of their calendars (names and colours), so they can choose which ones to show (calendar.calendarlist.readonly).
  • The events on the calendars they choose: title, time, place, description, organiser, guests and their answers, and any Google Meet link (calendar.events).
  • Busy times only (never event details) for the guests they invite, when they plan a meeting (calendar.freebusy).

We do not create aggregated or anonymised data from Google user data.

How we use it

  • To show their Google Calendar events on their console calendar, and keep the two in step both ways (events made, changed or deleted on either side).
  • To create meetings they ask for, invite the guests they choose (Google sends the invitations) and add a Google Meet link.
  • To answer invitations they receive (yes, no or maybe), and show which of their guests are free when they plan a meeting.

We use Google user data only to provide these features to that person. We never use it for advertising, profiling, credit or lending decisions, or anything else.

Who it is shared with

  • Only the person who connected the calendar sees its events in the consoles.
  • Guests they invite receive the invitation from Google, as with any Google Calendar invitation.
  • Service providers that run the consoles for us, only to provide these features: BinaryLane hosts our servers in Sydney; Anthropic's Claude AI processes the events needed to answer a question only when the person asks Hazel, our assistant, about their own schedule, for that answer only, under terms that forbid training on it.

We do not sell Google user data or transfer it to anyone else, including advertisers or data brokers, except where the law requires it.

How we protect it

All connections use HTTPS. Google's access keys are kept in an encrypted vault on our servers in Sydney and are never shown to anyone. The copied events are visible only to their owner. People at Timbre and Co. do not read them, except with that person's permission, to investigate a security problem, or where the law requires it, and access to our systems is logged.

How long we keep it, and deleting it

We keep a copy of the events only while the calendar is connected, refreshed every few minutes. Disconnecting (Calendar → Calendars) revokes our access with Google and deletes the copied events and the access keys from the consoles straight away. Removing our access from your Google Account at myaccount.google.com/permissions stops all access too. Copies already in our encrypted backups are removed as those backups expire: within 30 days on our own servers, and within 6 months in our off-site disaster-recovery backup, which is never read except to restore the system after a failure. You can also ask us at contact@timbreandco.com to delete everything sooner.

AI and Google's Limited Use rules

We do not use Google user data to develop, improve or train AI or machine-learning models, and we do not send it to any AI service that would use it to train its models.

Timbre and Co.'s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

5. Who can see it

  • Inside Timbre and Co. Staff and contractors see only what their role needs. An email is visible only to the people on it, and each person's calendar is theirs alone.
  • Partners such as Fairy Tale Proposals see only the jobs they work on with us. A producer can preview a partner's console as its members see it, view only, and each preview is logged.
  • Clients see only their own jobs, files, quotes and messages.
  • Service providers that run the consoles for us: BinaryLane (our servers, in Sydney), our email providers, Anthropic (AI), Canva (documents), Google (fonts, and Google Calendar for people who connect it), Squarespace (our logo) and Open-Meteo (weather for shoot locations). Browsers' own services deliver push notifications.
  • Others only when the law requires it.

Some of these providers store or process data outside Australia. We choose providers with appropriate safeguards.

6. How we protect it

  • Encrypted in transit: every connection to the consoles uses HTTPS.
  • Encrypted at rest: our data and files sit in an AES-256 encrypted vault on the server, and every nightly backup is separately encrypted with AES-256.
  • Passwords are stored only as one-way hashes. Connected mailbox passwords are encrypted.
  • A new device or network needs a code sent by email.
  • Access is limited by role, and sign-ins are logged.
  • The server's security is checked automatically every day.

7. How long we keep it

We keep job records for as long as we need them for the work and for legal and tax records (usually 7 years), then delete or anonymise them. Backups are kept for 30 days. Sign-in records are kept for 12 months.

8. Cookies

The consoles use only the cookies they need to work: one to keep you signed in, and small ones that remember your settings and the page you were on. There are no advertising or tracking cookies.

9. Your rights

You can ask to see or correct the personal information we hold about you, or ask us to delete it where we do not need to keep it. Email contact@timbreandco.com, or write to us at 34 Immarna Avenue, Lilli Pilli NSW 2229, Australia, and we will reply within 30 days.

10. Complaints

Email contact@timbreandco.com first. If you are not satisfied with our answer, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.

11. Changes

We will post any change here and tell account holders the next time they sign in.