Agreeably is operated by Eric John Flockhart, a sole trader in Victoria, Australia, ABN 71 583 301 583. "We" and "us" on this page mean Eric John Flockhart, trading as Agreeably.
This policy explains what personal information Agreeably collects, why, where it is kept, who else handles it, and how long we keep it. We follow the Australian Privacy Principles in the Privacy Act 1988 (Cth). Contact us at hello@agreeably.io with any question or request.
Who this covers
- Website visitors to agreeably.io.
- Customers: the people in a consultancy's Agreeably workspace (owners, delivery leads and viewers).
- People named in our customers' work: client contacts whose emails, names or approvals appear in a workspace, and visitors to a change request shared in the client portal at client.agreeably.io.
For information in a customer's workspace, that customer decides what goes in and why. We handle it on their behalf to provide the service, and we pass requests about it to them.
Website visitors
The website sets no cookies and uses no analytics, advertising or tracking scripts. It is served by Amazon CloudFront, which handles your request (including your IP address) to deliver the page; we do not keep access logs for the website. If you email us, we receive your email address and what you write, and use them only to reply. Email to our addresses is forwarded through Cloudflare.
What we collect from customers
- Account details: your name and email address. Sign-in is handled by Auth0 (Okta). We never see or store your password.
- Workspace content: the workspace name and time zone, projects and clients, agreements you upload or paste, scope, client requests you paste or forward, context notes, the analysis of each request, decisions and their reasons, change requests, approval evidence, and settings such as branding.
- Activity: an audit record of changes (who did what, to which record, and when). It records names of fields and states, not the content you entered.
- Billing: the business name, ABN and billing contact you give at checkout. Card details are collected and held by Stripe; we never see or store your card number.
A forwarded client email can contain the sender's name, email address and message. We store what the forwarded message contains so you can review it; attachments are listed but not analysed. Only mail forwarded by a member of your workspace who can see the project is accepted.
How we use it
- To provide the service: store and show your workspace, analyse requests, and send the alerts and emails you or your workspace set up.
- To bill you through Stripe and keep the records tax law requires.
- To keep the service secure: limit abuse, investigate problems, and keep the audit record.
- To understand how the service is used and improve it. We count, from our own records, which days members use a workspace and when it first reaches steps such as a confirmed scope or a first request. We use no analytics supplier for this, and it never includes what you write or upload.
- To answer your questions and tell you about changes to the service or this policy.
We do not sell personal information, use it for advertising, or send marketing email without your agreement.
Product tips by email
If you choose to receive product tips, at sign-up or in your settings, we may email you occasionally based on where your workspace is: for example when a trial is about to end, or when a confirmed scope has no requests checked against it yet. We send at most one a week, and we record when and where you agreed. Every tip email has an unsubscribe link that works without signing in, and you can turn tips off in your settings at any time. Alerts, billing and account emails are separate and are not affected. These emails come from Eric John Flockhart, ABN 71 583 301 583.
AI analysis
To check a request against your scope, Agreeably sends text to Anthropic's Claude API: agreement text when drafting the scope, and a request's text, its context notes and your confirmed scope when analysing it. Anthropic processes that text outside Australia. We use Anthropic's commercial API, not a consumer chat product. Before anyone can sign up, we will confirm and publish here the retention and training terms that apply to our account.
We never send billing details or client portal visitor details for analysis. The sample project every new workspace receives is built from fixed content without any call to Anthropic. The model cannot send email, change scope, approve work or bill anyone.
The help assistant
When you ask the help assistant in the app a question, we send your question, up to 3 earlier questions and answers from the same chat, and up to 3 of our own help centre articles to Anthropic's Claude API, which turns them into short steps. Anthropic processes that text outside Australia, as it does for AI analysis. The assistant cannot see your workspace, its data or anyone else's, and cannot change anything.
We store each question with who asked it and in which workspace, and what the assistant made of it, for 90 days. We use them to improve the help centre and to keep the service secure: a question that looks like an attempt to misuse the assistant, such as trying to override its instructions, probe our systems or send code meant to exploit them, is flagged and may be reviewed by us. A flagged question is kept until it has been reviewed, then for the same 90 days. Questions are deleted with the workspace. Do not include personal information about anyone else in a question.
Where it is kept and who else handles it
| Supplier | What it does | Where |
|---|---|---|
| Amazon Web Services | Hosts the app, database and files; sends and receives email (Amazon SES); serves the website | Sydney, Australia (the website is served from CloudFront locations worldwide) |
| Anthropic | Analyses agreement and request text, and answers help assistant questions | Outside Australia |
| Auth0 (Okta) | Sign-in | May be outside Australia |
| Stripe | Payments, invoices and billing contact details | May be outside Australia |
| Cloudflare | Our domain's DNS, and forwarding email sent to our addresses | May be outside Australia |
Where a supplier handles personal information outside Australia, we use it only for the purpose above and choose suppliers that protect it. By using the service you consent to this disclosure.
Client portal visitors
If a customer shares a change request with you at client.agreeably.io, we collect your name and
email as you type them; whether you confirmed your email with a code, and when; when you
first and last opened the page; any questions you ask; and, if you are the named approving
contact, whether you approved or rejected it, any note, and when. The customer who shared it
sees these details. We set one cookie, portal_session, which keeps you signed in
to that page for up to 12 hours and is used for nothing else. We do not store your IP address
or browser details, and your details are never sent for AI analysis. An approval is recorded
as evidence for the customer; it is not an electronic signature.
How we measure use of the app
To find what is slow or confusing and fix it, the app tells us which screens are opened, a short fixed list of actions (such as opening Check a request or using a keyboard shortcut), and how quickly each screen loaded and responded. A screen is recorded by its kind, such as "a project's requests", never by which project, request or client it was, and never with anything you typed or uploaded. Each record is tied to your account and workspace, kept for 90 days, and deleted with the workspace. We also time how long our servers take to answer, counted per kind of request. We do this ourselves; no analytics supplier receives it, and no cookie is used for it.
Cookies and browser storage in the app
The app keeps your sign-in session in your browser's local storage so it survives a page reload, and remembers the workspace you last used and display choices such as the theme. It uses no advertising or analytics cookies.
The browser extension
The Agreeably browser extension reads a page only when you choose Send to Agreeably or click its button, and then only the text you have selected. It shows you that text to edit before anything is sent, and sends only what you add, to your workspace. It does not send the page's address or title, read your browsing history, or use analytics. It keeps your sign-in in the browser's memory until the browser closes, and remembers the workspace and project you last used.
How long we keep it
- A workspace's content is kept while the workspace is active, and an owner can delete a project or the whole workspace at any time.
- When a trial ends without a subscription, the workspace becomes read-only and is deleted 30 days later. When a paid subscription is cancelled or unpaid, it is deleted 90 days later. Owners are warned before either happens and can export or subscribe until then.
- Our target is to remove deleted content from our systems within 7 days, and backup copies expire within 35 days.
- Export files are kept for 24 hours.
- Help assistant questions are kept for 90 days, and a flagged question until it has been reviewed and then for 90 days.
- We keep a minimal record that a deletion happened, the audit record, and billing records for as long as the law requires.
Security
Each workspace's data is kept apart from every other's, files are private and downloaded through short-lived links, and access follows each member's role. Email hello@agreeably.io for our security overview, which explains how.
Your choices and rights
You can ask to see or correct the personal information we hold about you, or make a complaint, by emailing hello@agreeably.io. If the information is in a customer's workspace, we will pass your request to that customer, who controls it. We will reply within 30 days. If you are not satisfied with our response, you can complain to the Office of the Australian Information Commissioner at oaic.gov.au.
Changes to this policy
We will update this page when how we handle personal information changes, and change the date at the top. For a significant change we will also tell workspace owners by email.