Hermes AI Terms

Summary

This summary is a plain-language guide to the main points of this document. It does not form part of the document’s binding terms and does not change their meaning. The numbered clauses govern.

Hermes is the AI assistant in Lucrii. It answers questions about your records, reads files you give it, makes changes you ask for, remembers what you tell it, and offers suggestions.
What you put into Hermes and what it produces belong to you.
Lucrii does not train AI models. Its AI providers do not train on your data.
Hermes runs on Anthropic’s Claude models through Amazon Bedrock in Australia. Cohere’s embedding models, which index your records so Hermes can find them, run through Amazon Bedrock and may be processed in AWS regions outside Australia.
The content of Hermes interactions goes to PostHog, Lucrii’s analytics provider in the United States, to measure and improve Hermes. It is not used to train AI models. Klaviyo, Lucrii’s email provider, does not receive the content of Hermes interactions.
Hermes messages are deleted after 90 days.
You can see and delete what Hermes remembers.
Hermes asks you to confirm before it deletes things or acts on many records at once.
Each plan includes monthly credits for Hermes. Use beyond them is charged, and Hermes stops when overage reaches a spending limit the Owner sets.
An Owner or Administrator can turn Hermes off for the organisation, and Lucrii will not turn it back on.
Hermes can be wrong. Review what it produces before you rely on it, and do not treat it as professional advice.

1.1 These Hermes AI Terms (AI Terms) form part of the Terms of Service (Terms) between Lucrii Pty Ltd (ABN 46 694 710 211, ACN 694 710 211) (Lucrii) and the Customer. These AI Terms adopt the definitions in clause 2.1 of the Terms, including Customer, Customer Data, Owner, Administrator, Service, Hermes, Hermes Content, Credits, Outputs and Sub-processor, and capitalised words that these AI Terms do not define have the meaning the Terms give them.

1.2 The order of precedence in clause 2.3 of the Terms applies. If these AI Terms conflict with the Terms on a matter concerning Hermes, these AI Terms prevail. The Data Processing Addendum (DPA), and the EU Standard Contractual Clauses and UK Addendum it incorporates, prevail over both for the processing of Personal Information in Customer Data.

1.3 These AI Terms are governed by the law of Victoria, Australia, as clause 22.5 of the Terms provides.

2. Definitions

In these AI Terms:

AI Provider means a provider of an AI model that Hermes uses, as named in clause 6.

Input means anything a User or the Customer gives Hermes, including messages, instructions, files and the records Hermes reads to respond.

Memory means a piece of information that Hermes keeps for later conversations, as clause 7 describes.

Industry Figures means the figures described in clause 8.

Scheduled Task means an instruction a User saves for Hermes to carry out on a recurring schedule.

3. What Hermes does

3.1 Hermes is available to Users in Organisations where Hermes is turned on. Hermes can:

(a) answer questions about the Organisation’s records and about how to use Lucrii;

(b) read files a User attaches, including images, PDFs, spreadsheets, Word documents and emails;

(d) keep Memories at user, team and organisation level, as clause 7 describes;

(e) show Industry Figures, as clause 8 describes;

(f) offer suggestions and a briefing, as clause 9 describes; and

(g) carry out Scheduled Tasks, as clause 9 describes.

3.2 While Hermes is turned on, Lucrii also analyses the Organisation’s records in the background to give Hermes context about the business, so that Hermes can find relevant records and answer questions about them.

3.3 Hermes acts with the permissions of the User it is working for. It cannot read or change a record that the User cannot read or change.

3.4 Hermes is designed to treat the content of files, emails and other records as information to work with, and it does not save a Memory from that content.

4. Inputs, Outputs and ownership

4.1 Inputs and Outputs are Customer Data. As between the parties, the Customer owns them, and Lucrii assigns to the Customer any rights Lucrii has in Outputs.

4.2 Lucrii uses Inputs and Outputs only to provide Hermes and the Service to the Customer, to measure and improve the quality of Hermes as clause 6.4 describes, to keep the Service secure, and as the law requires.

4.3 Outputs may be similar to Outputs Hermes produces for others. The Customer’s ownership of its Outputs does not extend to similar content produced for anyone else.

4.4 The Customer must have the rights it needs to give Hermes its Inputs, including any files it attaches.

4.5 Lucrii deletes each Hermes message 90 days after it is sent. A file a User attaches to a message in chat is deleted about a week after it is uploaded, unless it has been attached to a record. The title and summary of each Hermes conversation are kept while the Organisation exists, unless the Customer asks Lucrii to delete them under clause 9.3 of the Terms.

5. No training

5.1 Lucrii does not train or fine-tune any AI model, and does not use Customer Data, Inputs or Outputs to do so.

5.2 Lucrii’s AI Providers do not use Customer Data, Inputs or Outputs to train or improve their models.

5.3 Industry Figures are statistics calculated from records under clause 8. They do not involve training an AI model.

6. AI providers and where processing happens

6.1 Hermes uses the following AI Providers:

(a) Anthropic’s Claude models, which generate Hermes’ responses; and

(b) Cohere’s Embed models, which index records and Memories so that Hermes can find relevant information.

6.2 Anthropic’s models are served through Amazon Bedrock, part of Amazon Web Services, in Australian regions (Sydney and Melbourne). Cohere’s embedding models are served through Amazon Bedrock’s cross-region inference, and requests to them may be processed in AWS regions outside Australia. Lucrii hosts Customer Data with Amazon Web Services in Sydney.

6.3 Lucrii may change the models Hermes uses. A new AI Provider is a new Sub-processor, and Lucrii will list it on the Sub-processors page with the notice and right to object that clause 7 of the DPA provides.

6.4 Lucrii sends Hermes Content, and excerpts of the records Hermes indexes under clause 3.2, to PostHog, its analytics provider, in the United States, to measure and improve Hermes. Lucrii does not use them to train any AI model. Klaviyo, Lucrii’s email provider, does not receive Hermes Content. The Privacy Policy and the Sub-processors page describe PostHog’s role and the safeguards for the transfer.

7. Memory

7.1 Hermes keeps Memories at three levels:

(a) user Memories, which only the User they belong to can see and change;

(b) team Memories, which the team’s members, Administrators and Owners can see, and which the team’s Team Leader, Administrators and Owners can change; and

7.2 Hermes saves a user Memory when a User tells it something worth keeping in chat, and shows the User that it has done so. Hermes saves a team or organisation Memory only when someone who can change that level approves it. Hermes saves Memories only from what a User types in chat.

7.3 Memories stay within the Organisation. Lucrii does not use one Organisation’s Memories for another Organisation.

7.4 A User can delete a Memory they can change, either from the Memory section of the Hermes settings page or by asking Hermes to forget it. Hermes asks for confirmation before it forgets a team or organisation Memory. A deleted Memory is removed permanently and does not appear in the Organisation’s audit history.

7.5 Hermes keeps its Memories in order on its own, for example by merging duplicates. It deletes a Memory only when a person deletes it, or when a User’s Memories reach their limit and a Memory replaces the least used one.

8. Industry figures

8.1 Industry Figures show an Organisation how its own measures, such as quote acceptance or time to be paid, compare with similar businesses. Lucrii builds them from public data blended with aggregated statistics drawn from the records of Organisations that use Lucrii.

8.2 Lucrii applies disclosure rules, including minimum group sizes and rounding, so that no Industry Figure reveals any one business’s data or any Personal Information. An Organisation sees only the figures for its own peer group, and Lucrii does not keep any Organisation’s own contribution once the figures are calculated.

8.3 An Organisation with Hermes turned off neither contributes to Industry Figures nor receives them. Demo organisations do not contribute.

8.4 The Customer licenses Lucrii to use its records for this purpose under clause 8.2(c) of the Terms.

9. Suggestions, briefings and scheduled tasks

9.1 Hermes may offer Users suggestions, for example an order due to ship today or a customer who usually reorders by now, in a short daily briefing, in prompts elsewhere in the Service and on record pages. Each User can choose how often Hermes offers them, or turn them off. Acting on a suggestion that changes a record goes through clause 10.

9.2 A User may create a Scheduled Task. A Scheduled Task runs as the User who created it, with that User’s permissions at the time of each run. It pauses if that User leaves the Organisation or loses a role it needs. Owners and Administrators can pause or end any Scheduled Task.

9.3 A Scheduled Task cannot confirm an action on anyone’s behalf. Where a step needs confirmation under clause 10, it waits in the inbox of the User who created the Scheduled Task until that User confirms or cancels it.

9.4 A schedule can also create a recurring quote, sales order or purchase order. Scheduled runs do not send documents to anyone. A User decides whether to send each one.

10. Confirmation for risky and bulk actions

10.1 Before Hermes deletes or clears records, forgets a shared Memory, or takes another action Lucrii treats as risky, it shows the User a confirmation describing what will happen. The action runs only if the User confirms.

10.2 Before Hermes changes many records at once, it shows the User a preview of the change. The change runs only if the User confirms it, and a large destructive change requires the User to type the number of records affected.

10.3 Lucrii checks the User’s permissions again when the User confirms. If a record has changed since the confirmation was shown, Lucrii refuses the action and tells the User.

10.4 Hermes acts on behalf of the User it is working for. An action Hermes takes at a User’s request, in a Scheduled Task, or after a User confirms it, is the Customer’s action, and the Customer is responsible for it as if the User had taken it. The User should check each confirmation before confirming it.

11. Credits, overage and spending limits

11.1 Lucrii measures Hermes use in Credits. The Credits a piece of work uses depend on how much text Hermes reads and writes and on the model that runs it. Chat, background analysis of records, briefings, drafts, Scheduled Tasks and questions from MCP Clients use Credits. Help with using Lucrii requested by an MCP Client does not.

11.2 Each Plan includes a monthly allowance of Credits, as shown on the Pricing Page. At the date of these AI Terms:

(a) the Free plan includes 1,000 Credits a month for the Organisation; and

(b) the Early Access plan includes 4,000 Credits a month for each Seat, shared across the Organisation.

Credits not used in a month do not carry over. A sub-organisation uses its parent Organisation’s allowance.

11.3 During a trial, the Organisation receives the Early Access allowance for each Seat and Lucrii never charges for Hermes. Hermes stops when the trial’s Credits are used up.

11.4 On the Free plan without a card, Hermes stops when the month’s Credits are used up and starts again when they refresh. An Owner may add a card to keep using Hermes past the allowance.

11.5 Where a subscription or a card pays, use beyond the included Credits is charged at the overage rate on the Pricing Page, which is A$0.02 per Credit (A$20 per 1,000 Credits) at the date of these AI Terms. Lucrii adds overage to the next invoice.

11.6 The Owner may set a monthly spending limit on overage in the Billing settings. The limit starts at A$100 on the Early Access plan and at A$20 on the Free plan with a card, and a limit of 0 means no limit. When overage reaches the limit, Hermes stops until the Owner raises the limit or the next month begins. Work already running when the limit is reached finishes and is charged, so a month’s overage can pass the limit by the cost of that work. Lucrii emails the Owners as overage approaches and reaches the limit.

11.7 Hermes also stops while a subscription payment is past due.

11.8 A change to the included Credits, to the overage rate or to the way Credits are measured that would increase what the Customer pays for the same use is a price change under clause 6 of the Terms, and Lucrii will give at least 30 days’ notice of it.

12. Turning Hermes off and role permissions

12.1 Hermes is on when an Organisation is created. An Owner or Administrator can turn Hermes off with the Hermes AI switch on the General page of the Organisation’s settings.

12.2 While Hermes is turned off for an Organisation, Hermes stops processing and learning from that Organisation’s data, and the Organisation does not contribute to or receive Industry Figures.

12.3 Lucrii will not turn Hermes back on for an Organisation where an Owner or Administrator turned it off. Only an Owner or Administrator can turn it back on.

12.4 Turning Hermes off does not delete the Organisation’s Memories or conversations. A User can delete Memories under clause 7.4, Hermes messages are deleted under clause 4.5, and an Owner may ask Lucrii in writing at support@lucrii.io to delete the rest of its Hermes data, which Lucrii will do within 30 days after receiving the request.

12.5 Owners and Administrators can choose which roles may use certain Hermes features. Owners always hold every Hermes permission.

13. Reviewing outputs

13.1 Hermes uses AI, and Outputs may be inaccurate, incomplete, out of date or unsuitable for the Customer’s purpose. Lucrii does not warrant that Outputs are accurate, complete or free from bias, except as the Australian Consumer Law requires.

13.2 The Customer must review Outputs before relying on them, before sending them to anyone, and before confirming a change Hermes proposes. The Customer is responsible for its use of Outputs, including any document it sends that Hermes drafted.

13.3 Hermes does not give financial, legal, tax, accounting or other professional advice, and is not a substitute for it. Outputs are not financial product advice within the meaning of the Corporations Act 2001 (Cth). The Customer must not rely on Hermes for advice of that kind.

13.4 The Customer must not use Hermes alone to make a decision that has a legal or similarly significant effect on an individual, such as a decision about employment, credit or access to services. Where the Customer uses Hermes in making decisions about individuals, the Customer decides, and is responsible for any disclosure the law requires of it, including under the Australian Privacy Principles.

13.5 Clause 19 of the Terms governs Lucrii’s liability for Hermes and Outputs, and nothing in these AI Terms extends it. Non-Excludable Rights apply.

14. Prohibited AI uses

14.1 The Acceptable Use Policy, including clause 9 of it, applies to Hermes. In addition, the Customer must not, and must ensure its Users do not:

(a) try to make Hermes ignore its rules or permissions, including by placing instructions in files, records or messages;

(b) try to obtain another Organisation’s data, or to work out any business’s data from Industry Figures;

(d) try to avoid Credits, spending limits or the confirmations in clause 10.

15. Changes to these AI Terms

15.1 Lucrii may change these AI Terms under clause 21 of the Terms, by giving at least 30 days’ notice by email to the Owners.

15.2 If a change is materially adverse to the Customer, an Owner may cancel the subscription or end the agreement before the change takes effect, as clause 21.3 of the Terms provides.

15.3 These AI Terms show the date they were last updated.