Quercus Origin
Data sharing agreement
This agreement sets out how Oak & Origin handles the data a distillery puts into Quercus Origin: the distillery owns its data, and Oak & Origin holds and uses it only to run the service for that distillery.
1. Parties, term and meanings
Parties. This agreement is between Daniel's Whisky Holdings Pty Ltd, ABN 68 642 008 053, of 2-4 Bowral Lane, Welby NSW 2575, trading as Oak & Origin ("Oak & Origin"), and the business that holds a Quercus Origin account ("the Distillery").
Term. It applies from the day the Distillery first uses Quercus Origin, or from 20 November 2026 if the Distillery was already using it, and runs for as long as the Distillery uses Quercus Origin. Clauses 8 and 9 continue after it ends.
Meanings.
- Quercus Origin, or the Service, is the distillery management software Oak & Origin provides at the Distillery's own address under quercus.au, and the support that goes with it. On screen the software is named Quercus.
- Distillery Data is everything the Distillery or its users enter, import or connect into the Service: customers and contacts, orders and invoices, products, batches, stock, still house and bond store records, casks, tasks and files.
- Personal Information is any part of Distillery Data that identifies a person, such as a customer contact, a trade buyer, a cask owner or a member of staff.
- Service Provider is an outside company Oak & Origin uses to run the Service, listed in the Schedule.
- Oak & Origin's other businesses are its online store, its agency work and anything else it does apart from Quercus Origin.
How this fits with the Terms of use. The Terms of use govern the Service generally. Where the two differ about Distillery Data, this agreement applies. The Privacy policy describes how personal information is handled.
2. Ownership and use
2.1 The Distillery owns the Distillery Data. Nothing in this agreement gives Oak & Origin any ownership of it.
2.2 Oak & Origin may use Distillery Data only to:
- provide the Service to the Distillery;
- send the emails and pass on the records the Distillery asks the Service to send;
- answer a support request from the Distillery;
- find and fix faults, and keep the Service secure and running;
- meet a legal obligation.
2.3 Oak & Origin will not:
- sell Distillery Data, or give it to anyone for marketing;
- use Distillery Data in, or share it with, Oak & Origin's other businesses, including to buy, sell, price or promote spirits;
- contact the Distillery's customers, trade buyers or cask owners for its own purposes;
- use Distillery Data for the benefit of another distillery, or combine it with another distillery's data;
- use Distillery Data to train an artificial intelligence model, or allow a Service Provider to;
- publish figures drawn from Distillery Data, even with names removed, unless the Distillery agrees in writing.
2.4 Oak & Origin may keep and use counts that identify no person and no distillery, such as the number of orders the Service handles, to run and improve the Service.
2.5 If the Distillery also deals with Oak & Origin's other businesses, for example by selling through its store, that dealing is separate. Nothing Oak & Origin learns from Distillery Data will be used in it.
3. Access, security and location
3.1 Support access. Only people Oak & Origin has authorised to support Quercus Origin may sign in to the Distillery's site, and only to answer a request from the Distillery, to fix a fault, or to keep the Service running. Each such sign-in is recorded on the Distillery's activity feed, where the Distillery's administrators can see it. A person who gives support may also work in Oak & Origin's other businesses. They may use what they see only to give that support, and never in those other businesses.
3.2 Security. Oak & Origin will keep in place at least these measures:
- the Distillery's records are separated from every other distillery's by row-level security in the database;
- each user has a role that limits what they can see and change;
- connections to the Service are encrypted;
- the keys the Service holds for the Distillery's connected systems are stored encrypted;
- passwords are held in hashed form by the sign-in provider and cannot be read by Oak & Origin;
- the database is backed up daily and each backup is kept for seven days.
3.3 Location. The application and its database are hosted in Sydney, Australia. Distillery Data leaves Australia only through the Service Providers and connected systems marked as overseas in the Schedule.
3.4 People. Anyone working for Oak & Origin who can reach Distillery Data is bound to keep it confidential.
4. Service providers and connected systems
4.1 Service Providers. Oak & Origin uses the Service Providers in the Schedule to run the Service. Each receives only what it needs for its job. Oak & Origin stays responsible to the Distillery for what they do with Distillery Data.
4.2 Changes. Oak & Origin will tell the Distillery at least 30 days before adding or replacing a Service Provider that will hold Distillery Data, unless the change is needed urgently for security. If the Distillery objects, it may end its use of the Service and take its data under clause 8.
4.3 Systems the Distillery connects. The Distillery may connect its own accounting system, web shop, till or payment account. When it does:
- the Distillery is instructing Oak & Origin to pass the relevant records to and from that system;
- that system belongs to the Distillery, and what happens to data inside it is between the Distillery and that provider;
- the Distillery may disconnect it at any time. Records already passed across stay in that system.
5. Features that use an AI model
5.1 Three features use an artificial intelligence model: the report assistant, Reach and Studio. Nothing is sent to the model unless a user uses one of them. The report assistant is part of the Service; Reach and Studio are off unless they are switched on for the Distillery. Oak & Origin will switch any of the three off for the Distillery on request.
5.2 When a user uses one of them, this is what is sent to the model provider named in the Schedule:
| Feature | What is sent |
|---|---|
| Report assistant | The question typed. When asked to explain a report: its title, its filters and up to its first 150 rows, which can include customer and contact names and phone numbers where the report lists them |
| Reach (campaigns) | The campaign's name, goal and audience notes; the product's name, description, sizes, prices and strength; the brand's voice and rules; monthly web shop sales totals for the last twelve months; and the advertising text being written or checked. No customer details |
| Studio (playbooks) | The playbook's name, description and anchor date, and the list of tools the business uses. No customer details |
5.3 What the model returns is shown to the user or saved for the user to check. The model is given no means of changing Distillery Data itself.
5.4 Oak & Origin uses the model provider on terms that do not allow what is sent to be used to train its models, and will not move to terms that allow it without the Distillery's written agreement.
5.5 If the Distillery connects its own AI assistant account to the Service through the Quercus Origin connector, that account is a connected system under clause 4.3.
6. If there is a data breach
6.1 If Oak & Origin learns that Distillery Data has been lost, or seen or taken by someone who should not have it, Oak & Origin will tell the Distillery without delay and within 72 hours of learning of it.
6.2 Oak & Origin will say what it knows at that point: what happened, which records are affected, what it has done, and what the Distillery should do. It will add to that as it learns more.
6.3 Oak & Origin will act promptly to contain the breach and stop it happening again.
6.4 The Distillery decides whether and how to tell its own customers and any regulator. Oak & Origin will give the help the Distillery reasonably needs to do so.
7. What the Distillery is responsible for
7.1 Its own customers. The Distillery decides what Personal Information it keeps about its customers, trade buyers and cask owners, and is responsible for having the right to keep it and to put it into the Service.
7.2 Its own privacy obligations. The Distillery is responsible for its own privacy policy and for answering requests from the people whose information it holds. Oak & Origin will help with a request within 14 days of being asked.
7.3 Its users. The Distillery's administrator issues and removes logins and sets each person's role. The Distillery is responsible for what its users do, and for telling Oak & Origin promptly if it thinks a login has been misused.
7.4 Its connected systems. The Distillery is responsible for the accounts it connects and for who can use them.
8. Export, return and deletion
8.1 Export. The Distillery may ask for a full export of its Distillery Data at any time. Oak & Origin will provide it within 30 days as CSV files, one for each kind of record.
8.2 Leaving. When the Distillery stops using the Service, Oak & Origin will provide a final export if asked, and will delete the Distillery Data from the live Service within 30 days of the Distillery's written request.
8.3 Backups. Deleted data remains in backups until they expire, which is seven days after deletion. Oak & Origin will not restore it except to recover the Service.
8.4 What may be kept. Oak & Origin may keep its own records of the account, such as invoices for the Service and correspondence, and anything the law requires it to keep.
9. General
9.1 Confidentiality. Each party will keep the other's confidential information confidential, and use it only for this agreement. For Oak & Origin that includes all Distillery Data.
9.2 Required by law. If the law requires Oak & Origin to disclose Distillery Data, Oak & Origin will tell the Distillery first where it is allowed to.
9.3 Changes. Oak & Origin may update this agreement by giving the Distillery at least 30 days' notice by email. If the Distillery does not accept the change, it may stop using the Service and take its data under clause 8. Any other change must be agreed in writing by both parties.
9.4 Liability.
(a) Rights that cannot be excluded. Nothing in this agreement excludes or limits any guarantee, right or remedy under the Australian Consumer Law, or under any other law, that cannot lawfully be excluded or limited. Where the law allows Oak & Origin to limit its liability for failing to meet such a guarantee, that liability is limited, at Oak & Origin's choice, to supplying the Service again or paying the cost of having it supplied again.
(b) Losses neither party is liable for. Subject to (a), neither party is liable to the other for loss of profit, revenue, business, goodwill or anticipated savings, or for any indirect or consequential loss, whether or not it could have been foreseen.
(c) General limit. Subject to (a), Oak & Origin's total liability to the Distillery for all claims arising in any 12-month period, whether in contract, negligence or otherwise, is limited to the fees the Distillery paid for the Service in the 12 months before the first event giving rise to a claim.
(d) Higher limit for the Distillery's data. For claims arising from Oak & Origin's breach of clause 2 (ownership and use), clause 3 (access, security and location) or clause 6 (data breach), the limit in (c) is three times those fees.
(e) Where the limits do not apply. The limits in (c) and (d) do not apply to loss caused by a party's fraud or deliberate wrongdoing.
(f) What Oak & Origin is not responsible for. Oak & Origin is not liable for loss to the extent it is caused by the Distillery or its users, by the misuse of a login the Distillery issued (unless Oak & Origin's own breach allowed it), by a system the Distillery connected under clause 4.3, or by an event beyond Oak & Origin's reasonable control. An event beyond Oak & Origin's control does not release it from clause 6.
(g) The Distillery's own records and returns. The Service records what the Distillery enters, and some figures, such as volumes in wood, are estimates and are labelled as estimates. The Distillery remains responsible for the accuracy of what it enters and for its own tax, excise and regulatory records and returns. Oak & Origin is not liable for a figure the Distillery relied on without checking it against its own measurements.
(h) Claims by other people. The Distillery will meet any claim made against Oak & Origin by a third party that arises from Personal Information the Distillery had no right to put into the Service, or from the Distillery's breach of clause 7. Oak & Origin will meet any claim made against the Distillery by a third party that arises from Oak & Origin's breach of clause 2 or clause 3, up to the limit in (d).
(i) Reducing loss. Each party must take reasonable steps to reduce any loss it suffers.
9.5 Governing law. The law of New South Wales applies.
9.6 Questions and notices. Notices to Oak & Origin go to developer@johnjarvis.com.au, or by post to its address in clause 1. Notices to the Distillery go to the email address in its distillery profile.
9.7 Acceptance. The Distillery accepts this agreement by using the Service. Oak & Origin will provide a signed copy on request.
Schedule: Service Providers
As at 20 November 2026.
Used for every distillery
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Fly.io | Runs the application | Everything passing through the Service | Sydney, Australia |
| Supabase | Holds the database and sign-in details | All Distillery Data | Sydney, Australia |
| Resend | Sends email | Each email, its recipients and its delivery status | Overseas (Japan and the United States) |
| OpenStreetMap (Nominatim) | Finds map coordinates for an address | A customer's street address, with no name attached | Overseas |
| Cloudflare | Holds the address records (DNS) for quercus.au | No Distillery Data. Traffic does not pass through it; it sees only which Quercus Origin address a device looks up | Worldwide |
Used only when the Distillery uses an AI feature
| Provider | What it does | What it receives | Where |
|---|---|---|---|
| Anthropic | The model behind the report assistant, Reach and Studio | What clause 5.2 lists for each feature | United States |
Systems the Distillery may connect (clause 4.3)
| System | What passes between it and the Service |
|---|---|
| Xero or MYOB | Invoices and the customer's name, email and ABN go to it; whether an invoice is paid comes back |
| Shopify | Trade customers and trade orders go to it; its products, stock and orders come back |
| WooCommerce | Its orders come into the Service |
| Square | Its sales come into the Service |
| Stripe | The invoice number and amount go to it; the payer enters card details on Stripe's own page |
| The Distillery's own AI assistant account, through the Quercus Origin connector | Tasks, and the customer, order and activity details linked to them, go to it when a user asks; it can add and update tasks |