Skip to content
NewLong jobs: agents that finish whole office jobsRead the changelog →
harny
Developers ▾
DocsQuickstartAPI referenceSecurityStatus
Use cases ▾
Back-office jobsCustomer supportSales and accountsKnowledge basePersonal assistantCoding agents
BenchmarksEnterpriseBlogPricing
Log inGet API key

Harny / Legal

Terms of service

The terms for the Harny website, the API, the console and the connectors.

On this page
The partiesEarly accessAccounts and API keysAcceptable useYour dataFeesAvailability and supportTerminationLiabilityLaw and contact

Questions about these terms?

Contact Harny ↗︎

The parties

1. Definitions

In these Terms:

"Harny", "we", "us" means Vexta Labs Inc., a company incorporated in British Columbia, Canada, of Burnaby, British Columbia.

"Developer", "you" means the person or company that creates an App on the Harny platform, whether or not any fee is payable.

"App" means an application you register with Harny. Each App has its own credentials, its own End Users, and its own settings.

"End User" means an individual who uses your App and whose data reaches Harny through your App. End Users are your users. Your relationship with them is governed by your own terms and privacy policy. How Harny handles their data is also described in Harny's privacy notice and in the End-User Notice.

"Child-Flagged User" means an End User you have marked to us as a child under Section 4.10.

"End-User Notice" means Harny's own short notice to End Users, which we publish and which you show at connect time (Section 4.2).

"Connected Source" means a third-party account — for example an email mailbox or a calendar — that an End User authorises your App to read through Harny.

"Context" means the information Harny derives from Connected Sources and from content your App sends us, together with the material we retain so it can be searched and retrieved. Context is what Harny returns to your App so your agent can answer well.

"Record" means the account Harny keeps of what your agent did — the actions it reported, their outcomes, and the material Harny supplied beforehand. The Record is evidence about your agent's behaviour. It is not an instruction to your agent and it is not Harny acting.

"Run record" means the list of steps your agent took in one run, as your agent's code reports it to us. It is not part of the Record.

"Service" means the Harny platform: the API, the developer console, the SDKs, and the connectors, taken together.

2. What the Service does — and what it does not do

2.1 What we supply

Harny is infrastructure that sits underneath your App. Across a single chain, we help you set the App up, connect Sources, let your End Users authorise those Sources, assemble the right Context for a given moment, and keep the Record of what your agent did afterwards, so you can watch, debug, and evaluate it.

2.2 What Harny does, and what your agent does

Harny supplies Context, carries out the Actions your agent instructs within the End User's permission and the rules you set, and keeps the Record.

Your agent decides. It runs in your systems, under your control, using your own model and your own tools. When your agent decides something, Harny's role is to have supplied Context before it, to carry out an Action only if you enabled it and the End User allowed it, and to record what your agent reported afterwards. Where you enable Actions for your app, Harny also carries out the steps your agent instructs on an End User's Connected Sources — inside what that End User allowed.

Three rules apply, and all three are deliberate:

  1. Reading and acting are separate permissions. Every Source connector reads with read-only permissions the End User granted for reading. Acting on a Source (sending a message, creating an event, writing a page) needs a separate write permission the End User grants, and an Action you enabled for your app. Forwarded email we receive; we send email as an End User only under an enabled Action and a granted write permission.
  2. You decide what your agent may do, and how it asks. For each app you choose the acting policy: which kinds of Actions run without asking, which ask the End User first, and which are never allowed. In test mode, the settings your setup assistant proposed apply until you change them, and changes save at once. When you switch the app to production you confirm them; after that a change needs your confirmation. A kind of action with no setting is not carried out: the agent reads and records only. Your agent's instructions are yours; carrying them out within the permission and the policy is ours.
  3. Every Action is on the record. What was instructed, by which agent, for which End User, under which permission, what happened, and what failed — kept in the action record you and the End User can read, and revocable by the End User at any time, which stops further Actions on that Source immediately.

Early access

2.3 The Service changes

We add, change, and remove capabilities as the platform develops. We give notice of changes that materially reduce what the Service does for you, on the notice terms in Section 12.

12. Changes to these Terms

We may change these Terms on at least 30 days' notice, given by email to your developer account and in the console. Continuing to use the Service after the notice period means you accept the change. If you do not accept a change, terminate under Section 11.2 before it takes effect.

Changes required by law or needed to address a security risk may take effect immediately, and we will tell you as soon as we can.

Accounts and API keys

3. Your account, your Apps, and your keys

3.1 Account

You must give accurate registration details and keep them current. You are responsible for everything done under your account.

3.2 Credentials

Your App authenticates to Harny with credentials you create in the console. You can list, create, and revoke API keys and client ingest keys yourself through the console and the API.

You must keep credentials secret, must not embed a server-side key in client software you distribute, and must revoke a key promptly if you believe it has been exposed. If you think a key has been compromised, tell us at support@harny.ai.

3.3 Access to Google Sources is granted, not automatic

Connections to Gmail, Google Calendar, and Google Drive are not available to every App by default. Access to Google Sources is subject to Google's own verification requirements and limits. Connections to these Sources require approval by Harny, which may be refused.

Nothing in these Terms entitles you to a Google connection. Approval is at our discretion and depends on capacity we do not control.

9. Your obligations to us

You are responsible for:

  • having the right to send us the data you send us;
  • your own disclosures and consents to your End Users (Section 4.2);
  • showing what Section 4.2 asks you to show at connect time, unchanged;
  • obtaining verifiable parental consent for child End Users, and flagging them (Section 4.10);
  • what your agent does with the Context we supply;
  • keeping your credentials secret;
  • the acts of anyone using your account.

Acceptable use

6. Acceptable use

You must not, and must not permit anyone to:

  • use the Service to build or operate a surveillance product;
  • resell standalone access to the Service as if it were your own infrastructure. Building and operating an App on behalf of a client, as an agency or under a white label, is permitted;
  • pass Context or Records to an advertising network, data broker, or any third party for marketing purposes;
  • probe, load-test, or attempt to circumvent quotas, rate limits, or access gates, including the gate in Section 3.3;
  • reverse-engineer the Service except to the extent that restriction is unenforceable where you are;
  • use the Service where doing so is illegal, or in breach of a Connected Source's terms.

We may suspend an App that is doing any of the above. Section 11 governs suspension.

Your data

4. End User data and consent

4.1 Who holds the relationship with the End User

Your End Users are your users, and you hold the relationship with them. You and we are jointly responsible for collecting their data through your App and for processing it to deliver the Service to your App. We are responsible on our own for the purposes we decide alone (Section 13). You are responsible for having the right to send us their data and for telling them, in your own terms or privacy policy, that you do.

4.2 What you must tell your End Users

Before an End User connects a Source, you must disclose to them, in substance:

  • that a third-party infrastructure service processes context from the account they are about to connect;
  • that, with their consent, the service also uses what it learns about their preferences and habits to personalise the other apps they use with the same service;
  • what that service keeps and for how long (Section 4.3 and Section 4.4);
  • that they can disconnect at any time, and how to ask for deletion.

The disclosure clause. A clause covering these points is provided in your console on the App settings page. Include it, or your own wording covering the same points.

Our End-User Notice. At connect time, before the End User authorises a Source, you must also show:

  • the short form of our End-User Notice, with its link, as we supply it;
  • where your App takes part, our question in Section 4.9, unchanged, separate from your own terms, and not pre-selected. You pass the End User's answer to us.

Using the template does not transfer responsibility: making your own disclosure accurate and lawful where your End Users live is yours. Our End-User Notice is ours to keep accurate.

4.3 What Harny stores

Harny stores:

  1. structured facts drawn from the content;
  2. short summaries of what a piece of content meant;
  3. representations of that material used to search it;
  4. metadata anchors — identifiers, timestamps, sender domain, size, category;
  5. copies of items fetched from a Connected Source, kept so we can serve and re-process them without going back to the Source each time;
  6. an audit trail of the processing itself;
  7. the Record of actions your agent reported;
  8. the Run record of your agent's work: when each run started and ended, its outcome and stop reason, step counts and token counts, the model preset used, an optional session reference you choose, and a short summary of each step.

Source copies include the content of the item. An item fetched from a Connected Source is stored as a copy that holds, depending on the Source, either the item's text as received, including its subject line where it has one, or a set of fields extracted from the item.

Short content is stored as written. Where a piece of content is short enough that the whole of it is the fact, we store it as it came in rather than deriving a separate summary from it. Longer content is decomposed into separate facts.

Run records hold summaries, not content. For each run, we store its timing, outcome, stop reason, counts, model preset and the agent instruction version used. For each step, we store the kind of step, the tool name, whether it succeeded, was refused, failed or was cancelled, how long it took, a short summary of its input and output, and a link to the Record entry it produced. Summaries are a few lines long, with credentials and secrets removed. They hold no End User message text, no text of agent answers, no file contents and no bulk tool output; only the length of an answer is kept. Run records are kept apart from Context, are not used to derive Context, and are not shared with other Apps. We also read your Run records to show you where your agent keeps failing and to suggest a change to your agent's instructions; a suggestion is saved as a new version and changes nothing until you or your coding assistant makes it current.

Two boundaries apply to stored source content and do not change:

  • It does not cross the App boundary. Stored source content, including content stored as written, never goes to another App.
  • It is not returned as source content. Source content is not returned as such through the developer interface. Within your own App, the Context we return may quote a short excerpt of the material it was drawn from.

4.4 How long we keep it

Different material is kept for different periods:

  • Items fetched from a Connected Source are kept for a set period, configurable per connection, defaulting to 90 days, after which they are deleted automatically. The period can be shortened, lengthened, or set to no expiry.
  • Derived Context — facts, summaries, and search representations — has no expiry. It exists until it is deleted. No timer and no sweep removes it. It goes when the End User's data is erased, or when a specific item is deleted.
  • Records of agent actions have no time limit. A Record about an End User goes when that End User's data is erased; every Record of your App goes when you ask us to delete the App.
  • Run records are kept for 30 days from the run, then deleted automatically. They are also erased with the End User's data and when the App is deleted.
  • Operational material — execution logs, delivery attempts, and query traces — is swept on shorter schedules.

4.5 Third-party processing

Content is processed by third-party model providers in order to derive Context, under our agreements with those providers.

Where data is processed. We publish where the Service and each of our provider categories process data, and update it when a location changes. Today:

WhatWhere
Application serverUnited States
Main databaseUnited States
Model providers that derive ContextPeople's Republic of China first, United States as the last fallback
Model providers that build search representationsUnited States

The full list, including email delivery, the edge network, the tool-integration platform that carries Actions on your own tools, sign-in and console hosting, is Annex III of the data-sharing agreement.

The regulated route. If your App cannot send End Users' data to China-hosted providers, select the "regulated" model preset. Under it, both your agent's model and our own processing of your App's content use only providers tagged for regulated workloads, hosted in the United States.

Where data is stored. Data is stored in the United States.

4.6 End User rights

Harny supports the following. The honest position on each is stated, because a right described more grandly than it works is worse than one described plainly.

Deletion. An End User's data can be erased. A signed-in user can erase their own data; you can initiate erasure for one of your End Users through the API; and progress can be checked through the erasure-status endpoint. Erasure removes derived Context from the memory stores, the copies fetched from Connected Sources, Records and Run records attributed to that End User, and the other material held about them. We act on an erasure request without undue delay and complete within 30 days.

These are kept:

  • what the law requires us to keep;
  • the record we hold for the End User survives in scrubbed form, with name and email removed, until your App is deleted;
  • a minimal audit record that the erasure happened survives, in a form that does not identify the End User;
  • the record of a request the End User made to us — who asked, what they asked and when we answered — kept to show we handled it, no longer linked to the End User's data;
  • daily usage counts, a day and a number with no content, kept for billing;
  • Records that are scoped to your App rather than to a person — maintenance jobs — are not attributed to an End User and are kept until you ask us to delete the App, rather than removed by a per-End-User erasure;
  • aggregated statistics describing no individual;
  • copies in backups, until the backups are overwritten. They are not used for anything until then.

Export and access. An End User may ask for a copy of the Context we hold about them, and we will provide it in a machine-readable form. This is a request path: you or your End User asks us, and we produce it. You can also export a person's stored data points and memories yourself through the API's export route.

Rectification, restriction, objection. Handled through your App — re-authorising a connection refreshes the data; disconnecting stops further processing — or by contacting us.

We answer End Users directly. For data held in our systems, an End User may come to us instead of you, and we answer them ourselves. That includes objecting to our use of their data to improve the Service, and withdrawing a consent they gave us, by emailing support@harny.ai. We tell you when a request affects your App. You forward to us, without undue delay, requests you receive about data only we hold.

4.7 Deletion when a connection ends

When you or your End User disconnects a Source, we stop retrieving from it and stop acting on it. The copies fetched from it are deleted at once if you ask for that when you disconnect; otherwise they expire on the connection's period in Section 4.4. Derived Context stays until it is erased or the item is deleted (Section 4.4). Disconnecting never changes anything in the Source itself.

4.8 Special categories, children, surveillance

You must not use the Service to:

  • process data about a person without their knowledge, for the purpose of monitoring them;
  • deliberately ingest special-category data — health, religion, sexual orientation, political opinion, biometrics — unless your End User has given explicit consent for exactly that;
  • offer the Service to a child End User — anyone under 13, or under the age of digital consent where they live, whichever is higher — unless you have obtained verifiable parental consent, or the consent the law of the child's location requires, and have flagged that End User to us as a child (Section 4.10). Content about a child that reaches us through an adult End User's own Connected Account, such as a message from a school to a parent, is permitted where the processing serves that adult;
  • ingest data in breach of a Connected Source's own terms.

4.9 Personalisation across Apps

With an End User's consent, we use what we learn about their preferences and habits to personalise the other Apps they use with Harny. We ask the End User for that consent in our own name at connect time, and they may withdraw it at any time.

Your App takes part unless you switch this off, which you may do at any time; switching it off stops such information being drawn from or served to your App. An App receives such information only about End Users it already has, and never stored source content (Section 4.3). An End User's consent, and the information it covers, remain under that End User's control if your App later stops using the Service.

4.10 Children as End Users

Children may be End Users of your App when you have obtained verifiable parental consent, or the consent the law of the child's location requires. For them:

  • You flag them. You mark every child End User to us, through the API, before any of the child's accounts is connected. We do not detect or infer age.
  • You may set a retention limit. If you set how long we keep children's data, we delete each item held about a Child-Flagged User, including their Records, once it is older than that limit. If you set none, we keep a Child-Flagged User's data while the child uses your App, and delete it after 12 months in which the child did not use it. Either way, we delete it within 30 days after a parent asks, you ask, or you remove the child or close the child's account. We keep only daily usage counts, with no content, for billing.
  • We act only as your service provider. For a Child-Flagged User we process data only to provide the Service to your App. None of our own purposes in Section 13 apply to their data, and we produce no statistics from it other than counts.
  • Our written assurances. We give you the written assurances on confidentiality, security, integrity and retention that children's privacy law requires of service providers. They are in the data-sharing agreement.
  • If we learn of an unflagged child, we tell you and treat that End User as flagged from then on. If you do not promptly confirm verifiable parental consent, we delete that End User's data.

5. Consumption-tendency signals

The following disclosure is reproduced word for word:

"Harny counts which senders and categories write to a connected inbox (never the email content) to power personalization; this is stored separately from the user's memory."

To put that in context for a developer reading these Terms: the count is metadata only — sender domain, category, and date. No message body and no subject line is kept. It is held in a separate store from the End User's Context and is never used to answer queries, so it cannot surface as context in an answer. Senders in sensitive categories, such as financial, medical, legal, and insurance, are excluded.

13. Data protection roles

We are responsible for the data we handle, in our own right. Three roles apply:

  1. Together, for the Service. You and we are joint controllers for collecting End Users' data through your App and processing it to deliver the Service to your App. You decide which Sources your End Users may connect, what your agent asks for, your acting policy, retention on each connection and your setting in Section 4.9. We decide how the Service collects, stores, derives, secures and records data. You give your own notice and show ours; we answer End Users directly for data in our systems.
  2. On our own, for our purposes. We are the controller for the purposes we decide alone, each on its own lawful basis: personalisation across Apps under Section 4.9 (the End User's consent); security of the Service, improving it, and aggregated statistics describing no individual (legitimate interests, with safeguards); sender-and-category counts (legitimate interests); billing (these Terms). Our privacy notice describes them.
  3. For you only, for children. For Child-Flagged Users we are your processor and service provider only, and none of our own purposes apply (Section 4.10).

The rights you grant us. You grant us a non-exclusive, royalty-free, worldwide licence to use content processed through the platform to operate and improve the Service, and to produce aggregated cohort statistics describing no individual, in each case except for Child-Flagged Users' content. The licence over aggregated cohort statistics survives termination.

The data-sharing agreement. Our Data Sharing and Joint-Controller Agreement sets out these roles in detail, including the transfer clauses and the terms for Child-Flagged Users. It forms part of these Terms.

Fees

7. Pricing and tiers

7.1 What you pay for

What you pay for is the number of End Users who used your App in the calendar month.

You can create any number of Apps. One App is active and free at a time. In it, the first 500 monthly-active End Users are free, forever. For each monthly-active End User above 500 in an App, you pay $0.30 per month. Your current count is shown in your console.

7.2 We can change the pricing

We may change our tiers, our thresholds, and how we charge, at any time, on at least 30 days' notice to you. We give notice by email to the address on your developer account and in the console.

If you do not accept a change, your remedy is to stop using the Service before the change takes effect, and to terminate under Section 11. Continuing to use the Service after the notice period means you accept the change.

7.3 Paid periods are honoured

A change to pricing does not disturb a period you have already paid for. If you have paid for a term, the terms you paid under run to the end of that term, and the change applies from your next renewal.

7.4 Free tier

The free tier is free. We may change what it includes on the notice in Section 7.2. We do not undertake to keep any particular capability free.

7.5 Taxes and payment

Fees are exclusive of taxes, which you pay in addition where they apply. Fees are payable in the currency stated on the pricing page. Fees already paid are not refundable except where the law requires it. If a payment fails, Section 11.1 governs what happens next.

Availability and support

8. Availability and security

8.1 Availability

We work to keep the Service running, and we do not promise that it will be.

We make no uptime commitment. The Service is provided as it is, in early access. To the extent the law allows, we give no warranty about the Service beyond what these Terms state. There is no service level agreement, no availability target, no credit or refund for downtime, and no committed support response time. We may take the Service down for maintenance, and we may do so without notice where security requires it.

8.2 Security

We take reasonable measures to protect the Service. In particular, the credentials an End User gives us for a Connected Source, and the secrets used to sign webhooks to you, are encrypted at rest.

8.3 Breach notification

If we become aware of a security breach affecting your End Users' data, we will tell you without undue delay, describe what we know, and tell you what we are doing about it.

For a breach in our systems, we make the notifications to regulators that the law requires of us, and we tell affected End Users where the law requires it, through your App or directly where we hold their contact details. We agree the content and timing of any End User notice with you. For a breach in your systems, notifying is yours. For Child-Flagged Users, notifying parents and regulators is yours, with our help.

Termination

11. Suspension and termination

11.1 Suspension

We may suspend your access or disable your credentials immediately if you breach Section 4 or Section 6, if your usage threatens the security or stability of the platform, if the law requires it, or if payment is overdue past any grace period. We will tell you promptly and say why. Access is restored when the cause is resolved.

11.2 You may terminate

You may stop using the Service and close your account at any time. A term you have already paid for runs to its end; we do not refund the unused part.

11.3 We may terminate

We may terminate on 30 days' notice for convenience, or immediately for material breach.

11.4 What happens after

We stop processing your End Users' data and delete derived data on the schedule in Section 4.6, except as Section 4.9 says for facts an End User chose to share. During a notice period you may ask us for a copy of the Context we hold for your App, on the request path in Section 4.6.

Sections 4.6, 9, 10, 13, and this Section survive termination.

Liability

10. Liability

10.1 What we are responsible for

We are responsible for operating the Service — supplying Context and keeping the Record — with reasonable care.

10.2 What we are not responsible for

We do not decide what your agent does, and we do not review its decisions before it makes them. We carry out an Action only within the End User's permission and the rules you set, and we refuse one that falls outside them or that no one can be reached to confirm (Section 2.2). To the fullest extent permitted by law, we are not liable for:

  • an Action your agent instructed and your rules allowed, carried out as instructed;
  • anything your agent does, or fails to do, including where it acted on Context we supplied;
  • a decision you or your End User made in reliance on Context;
  • Context that is incomplete, out of date, or wrong;
  • anything a Connected Source did, or any change a third-party provider made to it;
  • your failure to obtain consent or make disclosures.

Context is retrieved material, not advice and not a warranty of fact.

10.3 Cap

Our total aggregate liability under these Terms is limited to the fees you paid us in the twelve months before the event giving rise to the claim.

10.4 Excluded losses

Neither party is liable for indirect, incidental, special, or consequential loss, or for lost profits, revenue, data, or business opportunity.

10.5 What cannot be excluded

Nothing here excludes liability that cannot be excluded by law, including for fraud, or for death or personal injury caused by negligence. The limits in this Section do not apply to our gross negligence or wilful misconduct.

10.6 Indemnity

You will indemnify us against claims, damages, and reasonable costs arising from your End Users' content, your failure to obtain consent or make the disclosures in Section 4.2, your failure to obtain parental consent for or flag a child End User under Section 4.10, your breach of these Terms, and misuse of the Service by you or anyone using your account.

Law and contact

14. Governing law and disputes

These Terms are governed by the laws of the Province of British Columbia, Canada, and the federal laws of Canada that apply there, without regard to conflict-of-law principles. Any dispute arising from these Terms is resolved in the courts located in British Columbia, Canada.

15. General

Assignment. You may not assign these Terms without our consent. We may assign them in a merger, acquisition, or sale of substantially all our assets.

Entire agreement. These Terms are the whole agreement between us about the Service and replace any earlier agreement, including the Developer Agreement v1.0 dated May 2, 2026.

Severability. If a provision is unenforceable, the rest stands.

No waiver. Not enforcing a provision once does not waive it.

Notices. We write to the email address on your developer account. You write to us at hello@harny.ai for questions about these Terms, and support@harny.ai for security and data requests.

harny

Agent harness infrastructure.

ProductMemory APIMCP serverAgent harnessLong jobsConnected accountsActionsPricingBenchmarksChangelog
DevelopersDocumentationQuickstartAPI referenceAuthenticationErrorsLimitsFAQStatus
For agentsllms.txtFull docs as MarkdownAgent setup promptOpenAPI specMCP manifestAPI catalog
LearnGuidesIndustriesWhat is agent memoryKnowledge updatesAs-of recallMemory for LangChain agents
Free toolsUser cost calculator
CompanyAboutBlogBrandSecurityEnterpriseContactCommunityCookiesPrivacy policyTerms of serviceDeveloper agreement
© 2026 HarnyReport a problem