Quercus Origin
Privacy policy
Quercus Origin is distillery management software provided by Daniel's Whisky Holdings Pty Ltd (ABN 68 642 008 053), trading as Oak & Origin, of 2-4 Bowral Lane, Welby NSW 2575. This policy says what personal information Quercus Origin holds, why, who else handles it, and how to see or correct it. In it, "we" means Oak & Origin, and "Quercus Origin" means the software, which is named Quercus on screen. It covers Quercus Origin only, not the Oak & Origin online store.
1. Who this covers
Quercus Origin holds personal information about three groups of people.
- People who use Quercus Origin. Staff of a distillery who sign in, and the distillery's trade buyers and cask owners where the distillery gives them a login.
- People a distillery keeps records of. The distillery's customers and their contacts, which the distillery enters or imports. For these records the distillery decides what is kept and why; we hold them on the distillery's behalf.
- Visitors to quercus.au. Anyone who reads the public site or sends an expression of interest.
If you are a customer of a distillery and want to know what it holds about you, ask the distillery first. We will help the distillery answer.
2. What we collect
| Whose | What | Where it comes from |
|---|---|---|
| People who sign in | Name, email address, role, when they last signed in, and a record of the changes they make (the activity feed) | The distillery's administrator, and use of the service |
| A distillery's customers and their contacts | Business name, ABN, addresses, contact names, job titles, email addresses, phone numbers, notes of visits and calls, orders and invoices | Entered or imported by the distillery |
| Trade buyers and cask owners given a login | Name, email address, what they order, the casks they own and their statements | The distillery, and their own use of the portal |
| Buyers in a connected web shop or till | Name and order details as the shop or till supplies them | Shopify, WooCommerce or Square, when the distillery connects one |
| People who are emailed through Quercus Origin | Email address, the subject, and whether the message was delivered | Sending an invoice, a reminder or a welcome link |
| Visitors who send an expression of interest | Business name, contact name, email address, phone number and what they tell us | The form on quercus.au |
Quercus Origin does not ask for or store payment card numbers. Card payments are taken on Stripe's own page.
When something goes wrong on a page, Quercus Origin keeps an error report: the page address, the time, who was signed in and the technical detail. It is used only to fix the fault.
3. How we use it
We use personal information only to run Quercus Origin for the distillery it belongs to:
- to sign people in and show each person what their role allows;
- to keep the distillery's customers, orders, stock, casks and records;
- to send the invoices, reminders and welcome links the distillery asks it to send;
- to pass invoices, orders and payments to the outside systems the distillery has connected;
- to answer a support request and to fix a fault;
- to reply to an expression of interest.
What we do not do:
- We do not sell personal information or pass it to advertisers.
- We do not use it in the Oak & Origin online store, the agency or any other part of our business, or share it with them.
- We do not contact a distillery's customers for our own purposes.
- We do not use one distillery's records for another distillery, or combine them.
- We do not read a distillery's records except to fix a problem the distillery has reported or to keep the service running. Each time our support signs in to a distillery's site, the sign-in is recorded on that distillery's activity feed.
4. Who it is shared with
Quercus Origin runs on a small number of outside services. Each receives only what it needs for its job.
Always in use
| Service | 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 stored records | Sydney, Australia |
| Resend | Sends email | The email, its recipients and its delivery status | Outside Australia (Japan and the United States) |
| OpenStreetMap (Nominatim) | Finds map coordinates for an address | A customer's street address, with no name attached | Outside Australia |
| Cloudflare | Holds the address records (DNS) for quercus.au | No stored records. Traffic does not pass through it; it sees only which Quercus Origin address a device looks up | Worldwide |
Only when the distillery uses or connects it
| Service | What it does | What passes between it and Quercus Origin | Where |
|---|---|---|---|
| Anthropic | Powers the report assistant, Reach and Studio | What the next table lists for each feature goes to it | United States |
| Xero or MYOB | The distillery's accounting system | Invoices and the customer's name, email and ABN go to it; whether an invoice is paid comes back | As the distillery's own account is set up |
| Shopify | The distillery's web shop | Trade customers and trade orders go to it; its products, stock and orders come back | As the distillery's own account is set up |
| WooCommerce | The distillery's web shop | Its orders come into Quercus Origin | As the distillery's own account is set up |
| Square | The distillery's till | Its sales come into Quercus Origin | As the distillery's own account is set up |
| Stripe | Card payments on invoices | The invoice number and amount go to it; the payer enters card details on Stripe's own page | Australia and overseas |
What the AI features send
| Feature | What is sent to the model provider |
|---|---|
| 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 |
What is sent is not used to train the provider's models. A distillery that connects its own AI assistant account through the Quercus Origin connector is sending tasks, and the customer and order details linked to them, to that account.
The accounting system, web shop, till and payment account belong to the distillery. What happens to information once it is in them is governed by the distillery's agreement with that provider.
We may also disclose information where the law requires it.
Information that leaves Australia. Email, address look-ups and the AI features are handled by providers outside Australia, as the tables show. We send them only what the job needs. The email and AI providers are used on terms that require them to protect what they receive; the address look-up receives an address with no name attached. Nothing is sent to the model provider unless someone at the distillery uses an AI feature. The report assistant is part of every site; Reach and Studio are off unless switched on. We will switch any of them off for a distillery on request.
5. Where it is kept and how it is protected
The application and its database are hosted in Sydney, Australia. Information leaves Australia only through the services marked in section 4.
- Separation. Each distillery's records are separated from every other distillery's by row-level security in the database, so a person signed in to one distillery cannot read another's.
- Roles. Each person has a role that limits what they can see and change.
- Encryption. Connections to Quercus Origin are encrypted. The keys it holds for a distillery's connected systems are stored encrypted.
- Passwords. Passwords are held by the sign-in provider in hashed form. We cannot read them.
- Backups. The database is backed up daily and each backup is kept for seven days.
- Support access. Only the people who support Quercus Origin can sign in to a distillery's site, and each sign-in is recorded on that distillery's activity feed. A person who gives support may also work in other parts of Oak & Origin, and may use what they see only to give that support.
No system is perfectly secure. If a distillery's records are lost, or seen or taken by someone who should not have them, we will tell that distillery within 72 hours of learning of it, and will tell the regulator where the law requires it.
6. How long we keep it
We keep a distillery's records, including error reports and the record of emails sent, for as long as the distillery uses Quercus Origin. Nothing is deleted automatically.
- A distillery can delete its own customers, contacts and orders at any time.
- A distillery can ask for an export of everything, and for deletion when it leaves.
- After deletion, copies remain in backups until those backups expire, which is seven days.
- Expressions of interest are kept until the conversation ends or the person asks for them to be removed.
Orders keep a copy of the customer's name as it was when the order was made, so that past invoices stay accurate after a customer record is deleted.
7. Cookies
Quercus Origin uses four cookies, all its own. It uses no advertising or analytics trackers.
| Cookie | Where | What it does |
|---|---|---|
| Sign-in | A distillery's site | Keeps you signed in |
| Preferences | A distillery's site | Remembers the quick actions you chose to show at the top of each page |
| Tour | A distillery's site | Shows the welcome tour once, on first sign-in |
| Arrival | quercus.au | Remembers the first page you opened, the date, the site that linked you and any campaign tag, so an expression of interest shows where it came from |
8. Your rights, complaints and contact
You can ask to see the personal information Quercus Origin holds about you, and to have it corrected.
- If a distillery holds it (you are its customer, trade buyer or cask owner): ask the distillery. It controls those records and we will help it respond.
- If we hold it directly (you sign in, or you sent an expression of interest): email developer@johnjarvis.com.au.
To complain about how your information has been handled, email the same address. We will reply within 30 days. If you are not satisfied, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
This policy may change as the service does. The date below moves when it changes, and distilleries are told of any change that affects how their records are handled.