Skip to content
harny
PlatformDevelopersBenchmarks
Get early accessEarly access↗︎
PlatformDevelopersBenchmarks

Harny / Legal

Developer agreement.

Last updated September 12, 2026Vexta Labs Inc.

The terms for developers integrating Harny into their applications.

Website termsPrivacy policyDeveloper agreement
On this page
1. Service Description, Availability, and Security2. Data Processing3. Developer Obligations4. Pricing and Billing5. Data Deletion and End-User Erasure6. Service-Improvement License7. Indemnification8. Limitation of Liability9. Suspension and Termination10. Data Protection Roles11. Governing Law and Dispute Resolution12. General

Questions about these terms?

Contact Harny ↗︎
On this page +
1. Service Description, Availability, and Security2. Data Processing3. Developer Obligations4. Pricing and Billing5. Data Deletion and End-User Erasure6. Service-Improvement License7. Indemnification8. Limitation of Liability9. Suspension and Termination10. Data Protection Roles11. Governing Law and Dispute Resolution12. General

This Developer Agreement ("Agreement") is entered into between Vexta Labs Inc.("Harny," "we," "us") and you, the developer or entity integrating the Harny platform into your application ("Developer," "you"). By creating an application on the Harny platform or accepting this Agreement through the developer console, you agree to be bound by its terms.

1. Service Description, Availability, and Security

1.1 What the platform does

Harny provides an infrastructure service that processes data from your application's end users' connected accounts to derive structured context, enabling AI-powered features within your application, and keeps the Record of what your agent did afterwards so you can watch, debug, and evaluate it. The sources, derivation methods, and output formats available through the platform are as described in this Agreement and may be updated from time to time with notice per Section 12.

1.2 Harny does not act

Harny supplies context and keeps the Record. Harny does not act. Your agent takes the actions. It runs in your systems, under your control, using your own credentials and your own tools. Harny does not send messages, make purchases, move money, write to your end users' connected sources, or take any other step in the world on your behalf or on your end users' behalf. Every source connector Harny offers reads and never writes, and the permissions we ask an end user for are read-only permissions. This applies to source connectors.

1.3 Availability

We work to keep the platform running, and we do not promise that it will be. We make no uptime commitment. The platform is provided as-is. 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 platform down for maintenance, and we may do so without notice where security requires it.

1.4 Security

We take reasonable measures to protect the platform. 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.

2. Data Processing

2.1 Processing

When your end users authorize a data source connection through your application, Harny receives content from that source (such as email messages) and derives structured context from it. In this Agreement, "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.

Purposes. We process this material to provide, personalize, improve, and develop the service; to derive aggregate insights; and to produce contextual recommendations.

Content is processed using third-party large language model providers, under our agreements with those providers, to derive structured facts relevant to your application's use case. 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. Where a piece of content is short enough that the whole of it is the fact, it is stored as it came in rather than summarized; longer content is decomposed into separate facts.

Harny stores structured facts, short summaries, search representations of that material, metadata anchors (message ID, timestamp, sender domain, byte size, category tier), copies of items fetched from a Connected Source, processing logs, and the Record.

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.

The count is sender domain, category, and date. It is held separately from the End User's Context and is never used to answer queries. Senders in sensitive categories — financial, medical, legal, and insurance — are excluded by default.

2.2 Retention

  • 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 are kept indefinitely. No retention period is set.
  • Operational material — execution logs, delivery attempts, and query traces — is swept on shorter schedules.

2.3 Handling of source content

Stored source content is not shared between applications. What another application can receive about a shared end user is an abstracted fact, never stored source content, including content stored as written. Some facts are marked as not shareable between applications. 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.

2.4 Google sources

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 this Agreement entitles you to a Google connection.

3. Developer Obligations

3.1 End-User Disclosure

You must include a clear disclosure in your application's terms of service or privacy policy informing your end users that:

  • Their connected account data is processed by a third-party infrastructure service, which may share context derived from it with other applications that participate in the same platform
  • Structured information is derived and stored, alongside copies of the fetched items, to provide personalized features
  • What that service keeps, and for how long (Section 2.2)
  • They may disconnect their account at any time, and how to request deletion

A clause covering these points is provided in your console on the app settings page after signing in — view it there. Include it, or your own wording covering the same points.

You are responsible for ensuring your disclosure complies with applicable law in the jurisdictions where your users are located.

3.2 End-User Consent

You are responsible for obtaining any necessary consent from your end users for the processing described in this Agreement. Harny relies on your contractual relationship with your end users as the basis for processing their data.

3.3 Lawful Use

You must not use Harny to:

  • Conduct surveillance or monitoring of individuals without their knowledge
  • Intentionally ingest data falling within GDPR Article 9 special categories (health data, religious beliefs, sexual orientation, political opinions, biometric data) except where your end users have provided explicit consent for that specific processing
  • Process data of individuals under 13 years of age, or under the applicable age of digital consent in your end users' jurisdictions
  • Violate the terms of service of any connected data source
  • Transfer or disclose extracted context to advertising networks, data brokers, or any third party for marketing or advertising purposes

3.4 Participation

Context derived through your app may be used to serve the same end user in other applications on the platform. Your app participates by default. What is shared is the abstracted fact only, never stored source content. Some facts are marked as not shareable between applications. An application receives facts only about end users it already has.

4. Pricing and Billing

4.1 One variable

What you pay for is the number of end users on your developer account. Harny is free up to a threshold. Above that threshold, you pay a monthly amount for each end user. The threshold and the price are published on the Harny pricing page, and your current count against the threshold is shown in your console. There is no second variable.

4.2 We can change the pricing

Harny may change its tiers, its thresholds, and how it charges, at any time, on at least 30 days' notice to you. Notice is given 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 platform before the change takes effect and to terminate under Section 9. Continued use after the notice period constitutes acceptance.

4.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.

4.4 Free tier

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

4.5 Taxes and payment

Fees are exclusive of taxes, which you pay in addition where they apply, and are payable in the currency stated on the pricing page. Fees already paid are not refundable except where the law requires it.

5. Data Deletion and End-User Erasure

5.1 Source Disconnection

When you or your end user disconnects a data source through your application, Harny ceases further data retrieval from that source immediately. Extracted data associated with that connection is marked for deletion.

5.2 Erasure Completion

We act on an erasure request without undue delay and complete it within 30 days. Erasure removes the derived context held about that end user, the copies of items fetched from their Connected Sources, the Records attributed to them, and the other material held about them.

Three things are kept:

  • the record we hold for the end user survives in scrubbed form, with name and email removed;
  • a minimal audit record that the erasure happened survives, in a form that does not identify the end user;
  • Records scoped to your app rather than to a person — maintenance jobs — are not attributed to an end user and are removed when the app is deleted rather than by a per-end-user erasure.

Aggregated cohort statistics describing no individual may be retained longer.

5.3 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. It is not a self-serve API, and this Agreement does not offer one.

5.4 End-User Erasure Path

Your end users may request erasure of their data by contacting you. You are responsible for initiating the erasure by disconnecting the user's data source through your integration or by contacting support@harny.ai. Alternatively, end users may contact Harny directly at support@harny.ai with their request, and Harny will execute the deletion within 30 days.

6. Service-Improvement License

You grant Harny a non-exclusive, royalty-free, worldwide license to use content processed through the platform to operate and improve the service, and to produce aggregated cohort statistics describing no individual.

The license over aggregated cohort statistics survives termination of this Agreement.

7. Indemnification

You agree to indemnify, defend, and hold harmless Harny and its officers, directors, and employees from any claims, damages, losses, or expenses (including reasonable legal fees) arising from:

  • Your end users' content processed through the platform
  • Your failure to obtain necessary consent or provide required disclosures to your end users
  • Your violation of applicable law or this Agreement
  • Any misuse of the platform by you or your end users

8. Limitation of Liability

8.1 Cap

Harny's total aggregate liability under this Agreement shall not exceed the fees paid by you to Harny in the twelve (12) months preceding the event giving rise to the claim.

8.1a What Harny Is Not Responsible For

Harny does not act. We do not decide what your agent does, we do not review its decisions before it makes them, and we do not approve or refuse the actions it takes. To the fullest extent permitted by law, we are not liable for: 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; or your failure to obtain consent or make disclosures. Context is retrieved material, not advice and not a warranty of fact.

8.2 Exclusions

In no event shall Harny be liable for indirect, incidental, special, consequential, or punitive damages, or loss of profits, revenue, data, or business opportunity, regardless of the theory of liability.

8.3 Exceptions

The limitations in this section do not apply to liability arising from Harny's gross negligence or willful misconduct, or to the extent prohibited by applicable law.

9. Suspension and Termination

9.1 Suspension

Harny may suspend your access to the Service or disable your API keys with immediate effect if: (a) you breach Section 3 (Developer Obligations) or Section 2 (Data Processing); (b) your usage threatens the stability, security, or availability of the platform; (c) required by law, regulation, or a binding order; or (d) your account enters a billing grace period that expires without resolution. Harny will notify you promptly after suspension and state the grounds. Access will be restored once the grounds are resolved to Harny's reasonable satisfaction. If suspension continues for more than 60 days without resolution, either party may terminate this Agreement under Sections 9.2 or 9.3.

9.2 Termination by Harny

Harny may terminate this Agreement for convenience upon 30 days' written notice to you. In the event of termination for convenience, you may ask us during the notice period for a copy of the context we hold for your app, on the request path in Section 5.3.

9.3 Termination by Developer

You may terminate this Agreement at any time by closing your account; a term you have already paid for runs to its end and the unused part is not refunded. You may also terminate immediately if Harny commits a material breach of this Agreement that remains uncured for 30 days after you provide written notice specifying the breach.

9.4 Effect of Termination

Upon termination, Harny will cease processing your end users' data and delete extracted data in accordance with Section 5.2. Provisions that by their nature should survive termination (including Sections 6, 7, 8, and this Section 9.4) will survive.

10. Data Protection Roles

You are the controller. Harny is your processor. You decide what data reaches us and why. We process it to provide the service to you, on your instructions and on the terms of this Agreement, for the purposes stated in Section 2.1.

Where the law treats Harny as a controller in its own right for some part of this processing, we will act accordingly and will say so. A Data Processing Addendum is available on request.

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. Notifying your end users, and any regulator, is yours to do — you hold the relationship and you are the controller.

11. Governing Law and Dispute Resolution

This Agreement is governed by the laws of the Province of British Columbia, Canada, without regard to conflict of law principles. Any disputes arising from this Agreement shall be resolved in the courts located in British Columbia, Canada.

12. General

12.1 Amendments

Harny may update this Agreement with 30 days' prior written notice. Material changes will be communicated via the email address associated with your developer account. Continued use of the platform after the notice period constitutes acceptance.

12.2 Assignment

You may not assign this Agreement without Harny's prior written consent. Harny may assign this Agreement in connection with a merger, acquisition, or sale of all or substantially all of its assets.

12.3 Entire Agreement

This Agreement constitutes the entire agreement between you and Harny regarding the subject matter hereof, and supersedes all prior agreements and understandings.

harny

Agent harness infrastructure.
Context, connection, continuity.

Show us what you’re building.

Products, partnerships, or the story behind Harny. Talk directly with the team.

support@harny.ai ↗︎
BenchmarksPrivacy policyTerms of serviceDeveloper agreement
© 2026 Harny · Vexta Labs Inc.