Privacy Policy

Your account and how you use Hepherus. Hepherus LLC decides how the information about you and your account is used, and is responsible for it. Where data protection law uses the term, we are the controller of this information.

The content in your workspace. The documents, conversations and other content in your organisation’s workspace — including any information about other people that it contains — belong to your organisation. We process that content on your organisation’s behalf, to provide Hepherus, under our Terms of Service. Where data protection law uses the term, we act as a processor for that content, and your organisation is the controller.

Contact: contact@hepherus.com

Information you give us

• Account details — your name, email address, and password. Your password is stored in a form we cannot read.
• Your country — we ask for it at sign-up because Hepherus is available only to customers in the United States. Paid plans also require a US billing address.
• Profile details — how you’d like to be addressed, your pronouns, your photo, and a job description, if you choose to add them.
• Organisation details — your organisation’s name, logo, website, and the country used for billing.
• Your content — see §3.
• Communications — what you send us when you contact us or reply to our emails.

Information we collect as you use Hepherus

• Activity — when you sign in, when you were last active, and which parts of Hepherus you use. We use this to understand how the product is used and to improve it.
• Usage — which agents and tools you use and how many credits each action consumes. We use this to bill you accurately and to show you your own usage.
• Technical information — the kind of device and browser you use, your IP address, and the cookies needed to keep you signed in. We use only the cookies required for sign-in. We do not use advertising cookies, tracking pixels, or analytics tools.

Information from services you connect

• Google Drive — see §3 and §10.
• GitHub — when you connect it, the repositories you choose to share with the coding agent.
• Payment — when you pay for Hepherus, your payment is processed by Stripe. We receive confirmation of payment and limited billing details; we do not receive or store your full card number.

The coding agent

• Coding is not yet available. The coding agent does not run: it makes no changes to any repository.
• We never copy your repositories to our systems. If you connect GitHub, we store the repositories you choose to share and references to them — not their contents.
• We do not receive or store any Anthropic credentials of yours.
• We are building a model in which coding runs through your own Claude Code. It is not available yet, and we will update this policy before it is.

Your content means what you give Hepherus and what our agents produce for you: documents, messages, conversations with agents, decisions, plans, reviews, and anything else created in a project.

Where it is stored — during our private testing period

• We store your content in our database, including the full text of documents, so that your projects, conversations and history are available to you and can be searched.
• Documents are also stored in a Google Drive account operated by us.
• Documents created by testers will be moved to the tester’s own Drive when Hepherus opens to customers.
• We do not copy your GitHub repositories to our systems. If an agent drafts code for you, that draft is stored as a document in our database, like any other output an agent produces.

Where it will be stored once Hepherus opens to customers — not yet available

This describes the model we are building. It is not how Hepherus works today, and we will update this policy before it takes effect.

• Your documents will live in your own Google Drive, which you connect. Each approved version of a document is saved as its own file in a versions folder in your Drive.
• We will keep only references to those files — not their text. When you search your documents, Hepherus searches your Drive through your connection.
• We will store in our database your conversations with agents, decisions, tasks, reviews, plans and agent memory (the summaries and notes agents keep about your projects), so that your projects and their history are available to you.
• All of these can contain excerpts of, or information from, your documents. An agent may quote a passage it is discussing with you; a review quotes the work it reviews; decisions, plans and tasks describe the documents they concern; and agent memory summarises conversations, including anything quoted in them. These excerpts are stored in our database along with the rest of your project history.

How it is used

Your content is used only to provide Hepherus to you — to let agents read, write and work on it at your request.

The AI providers

To do the work, the contents of what an agent works on are sent to the AI providers that power our agents. See §5.

We use these providers under terms that do not allow them to use your content to train or improve their AI models.

Information about other people

Your content may include information about other people — for example, names in a contract or details in a financial record. You are responsible for having the right to share that information with Hepherus. We process it only to provide Hepherus to your organisation.

Please don’t upload highly sensitive information

Hepherus is not designed to hold Social Security numbers, government ID numbers, bank or card account numbers, passwords, health information, or similar sensitive information. Please remove it from documents and code before sharing them with Hepherus.

Health information

Our health agent advises on health claims made about products — whether a claim is supportable and whether it overstates the evidence. It is not for advice about your own health, and Hepherus is not designed to hold health information about you. Please don’t send it. If you do, the agent will decline, and we will make a best effort to remove the message — but that removal is automatic and is not guaranteed. Messages you send to agents are otherwise stored with your conversation history, as described above.

AI-generated output

Our agents’ output is generated by AI. It can be inaccurate or incomplete — including about people — and legal, financial and health outputs are drafts for review by a qualified professional, not advice (see our Terms of Service). If output contains inaccurate information about you, contact us and we will help correct it. Hepherus does not use your information to make decisions about you that have legal or similarly significant effects on you.

We do not

• sell your content or your personal information;
• use your content for advertising;
• use your content to train AI models, or allow our providers to.

• Your organisation’s owner can see everything in that organisation, including your conversations with agents.
• Other people in your organisation see what their role and the project’s settings allow. A document marked owner only is visible only to the organisation’s owner and administrators.
• Hepherus staff can access your account information where necessary to run, support and secure the service, and to investigate problems you report.
• Hepherus staff do not read the content of your workspace — your documents, including anything from your connected Google Drive, and your conversations, reviews, decisions, plans, tasks and agent memory — unless you ask us to (for example, in a support request), it is needed to investigate security or abuse, or the law requires it. Because excerpts of your documents can appear anywhere in your project history (see §3), this applies to all of it.
• Our team may access information from outside the United States.

We share information only with the companies that help us run Hepherus (“sub-processors”), and only as needed for the purpose listed.

Services you connect — your Google Drive and your GitHub account — are your accounts, governed by your agreements with those companies.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising.

We may also disclose information if the law requires it, to protect the rights and safety of our users or others, or as part of a sale or reorganisation of our business — in which case this policy would continue to apply to your information.

Our providers are based in, or process information in, the United States and other countries, and our team may access information from outside the United States. Where the law requires safeguards for transferring personal information between countries, we rely on appropriate safeguards such as the Standard Contractual Clauses included in our providers’ data processing terms.

• Your account and content — for as long as your account is active. When you ask us to delete your account, we delete your information within a reasonable period, normally within 30 days, except where the law requires us to keep it. We keep 7 days of daily backups; copies of your information in them are removed as those backups are replaced.
• Agent memory (summaries and notes agents keep about your projects) — kept until the project is deleted.
• Connected-account credentials — access is revoked and credentials deleted within 24 hours of disconnecting the service.
• Your connected Google Drive — when you disconnect it, we delete our references to your files and revoke our access within 24 hours. Your documents remain in your own Drive, which you own.
• Activity information — 24 months.
• System logs — 90 days.
• Audit logs of access to our systems — 12 months.
• Billing records — as long as tax and accounting law requires.

• Credentials for services you connect are encrypted, with the encryption keys held separately in a key management service.
• Access to production systems requires multi-factor authentication.
• Organisations are separated at the database level: one organisation cannot read another’s information.

No system is perfectly secure. If a security incident affects your personal information, we will notify you as required by law.

Depending on where you live, you may have the right to:

• access the information we hold about you;
• correct it if it is wrong;
• delete it;
• receive a copy — on request, we will provide your information in a portable format;
• object to or restrict how we use it;
• withdraw consent where we rely on it.

We offer these rights to all users, wherever they live. To exercise any of them, contact contact@hepherus.com. We’ll respond within 30 days.

• Verification. We may need to confirm your identity before acting on a request, usually by confirming control of your account email.
• Authorised agents. Someone you authorise may make a request on your behalf; we may ask for proof of that authority.
• Appeals. If we decline your request, you can ask us to reconsider by replying to our decision. We’ll respond within 45 days.
• No penalty. We won’t treat you differently for exercising your rights.
• Content in your organisation’s workspace. For content your organisation controls (see §1), we may refer your request to your organisation.

You may also have the right to complain to a data protection or consumer protection authority where you live.

Legal bases. Where the law requires a legal basis for processing, we process your information to perform our contract with you (providing Hepherus), for our legitimate interests (improving and securing the service, understanding usage), and to comply with the law.

This section describes how Hepherus handles information received from Google APIs when you connect your Google account.

• What we access: only the files you choose to open with Hepherus, and the files Hepherus creates for you. We cannot see any other files in your Google Drive.
• How we use it: only to provide the features you use in Hepherus — agents reading, creating and updating documents at your request.
• Who we share it with: only the AI providers listed in §5, only as needed to perform the work you request. We do not transfer it to anyone else except as required by law, for security, or as part of a sale or reorganisation of our business with your notice.
• Storage and retention: as described in §3 and §7.
• AI models: we do not use information received from Google APIs to develop, improve or train generalised or non-personalised AI or machine-learning models, and we do not allow our providers to do so.
• Advertising: we do not use information received from Google APIs for advertising.
• Human access: as described in §4 — including the excerpts of Google Drive content stored in our database.
• Revoking access: you can disconnect Google Drive under Connections in your Hepherus settings, or at https://myaccount.google.com/permissions.

Hepherus’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs will also adhere to the Google Workspace API User Data and Developer Policy.

We do not track you across other websites and do not allow third parties to do so on Hepherus, so we do not change our practices in response to “Do Not Track” signals.

We send emails needed to run your account — for example, invitations, security alerts and billing notices. If we send marketing emails, each one will include a way to unsubscribe.

Some US states give residents specific privacy rights. We offer the rights in §9 to all users, we do not sell personal information or share it for targeted advertising, and we do not use sensitive personal information to infer characteristics about you.

Hepherus is not intended for anyone under 18, and we do not knowingly collect information from them.

We’ll update this policy as Hepherus changes. If a change is significant, we’ll tell you before it takes effect. If a change affects how we use information from your Google account, we’ll ask for your consent before applying it. The effective date at the top shows when it was last updated.

Hepherus LLC
850 New Burton Rd., Ste 201
Dover, DE 19904
contact@hepherus.com

See also our Terms of Service.