Terms of Service

Plain terms for a gateway: the bridge accepts calls to an API that is being retired and performs them through the API that replaces it. These terms cover the Avakode Bridges family: EWS Bridge (ewsbridge.com) and Legacy Bridge for HubSpot APIs (legacybridge.dev), their websites, the hosted bridges, the console at bridges.avakode.com and the self-hosted licence.

1. Who you are contracting with

Individual Entrepreneur Darya Avakova, Tax ID 534556558, Parkent street 9, apt. 78, Mirzo Ulugbek district, Tashkent, Republic of Uzbekistan — trading as Avakode. By creating a bridge or buying a plan you accept these terms. Plans are sold by Paddle.com, our online reseller and Merchant of Record; the Paddle Buyer Terms apply to the purchase itself.

2. What the service does

EWS Bridge accepts Exchange Web Services (SOAP) calls and performs them through Microsoft Graph with an app-only token of your Microsoft 365 tenant, after your administrator has granted consent. Legacy Bridge accepts HubSpot legacy v1–v3 calls and performs them through HubSpot’s date-based API with an access token of your portal. The console issues bridge keys and shows usage and a gap report. The self-hosted licence runs the same software on your own server.

3. What it is, and what it is not

Not every operation of the old APIs translates. The coverage tables at EWS Bridge coverage and Legacy Bridge coverage list what translates, what only partly and what does not; a call that does not translate gets a clear protocol error and a line in your gap report, never a silent empty success. We do not promise parity with the retired API, and we do not control Microsoft’s or HubSpot’s APIs, limits or deadlines. Avakode Bridges is not affiliated with or endorsed by Microsoft or HubSpot; their names are used only to say which APIs the bridges speak.

4. Your tenant, your portal, your keys

You decide what the bridge may do: the permissions your Microsoft 365 administrator consents to, and the scopes of the HubSpot token you save. The bridge acts only on calls authenticated with your bridge keys. Keep the keys secret; you can revoke and reissue them in the console at any time. You remain responsible for your integration, for the data it sends and for complying with Microsoft’s and HubSpot’s terms.

5. Plans, billing and cancellation

Hosted plans are billed monthly and the self-hosted licence yearly, through Paddle. A plan renews automatically at the end of each period until you cancel. You can cancel at any time — from the link in your Paddle receipt or by writing to us — and the cancellation takes effect at the end of the period you have paid for: the bridge keeps working until then and is not renewed. Going over a plan’s monthly request volume never blocks your traffic; we get in touch instead. If we change prices, the new price applies from your next period, never mid-period, and we tell you at least 30 days before.

When a plan ends or its licence lapses, the hosted bridge stops answering calls for that tenant; the console stays readable so you can see your reports. Twelve months after our licence server has started refusing the licence, the hosted bridge and what it keeps are deleted (Privacy Policy, section 11). A self-hosted server stops bridging after a 14-day grace period.

6. Refunds

The first payment of a monthly plan is refundable for 14 days, the self-hosted licence for 14 days from purchase; for a renewal you did not want we request a refund if you ask within 7 days and the bridge was not used since. Refunds are issued through Paddle, our Merchant of Record. The details are in our Refund Policy.

7. Acceptable use

Do not use the bridges to access tenants, mailboxes or portals you are not authorised to use, to process data you have no right to process, to attack or overload the service or the upstream APIs, or to resell bridge keys. An Agency plan is meant for managing your clients’ portals. We may suspend a tenant that is used in breach of these terms, and tell you why.

8. Availability and support

We aim to keep the hosted bridges available and to answer support within two business days, but we do not offer a contractual uptime commitment at this stage. The bridges depend on Microsoft Graph and on HubSpot’s API: their outages and limits are outside our control, and the bridge passes their throttling on to your client as the old API would.

9. Liability

To the extent the law allows, our total liability for any claim connected to the bridges is limited to what you paid us in the twelve months before the claim. We are not liable for lost profits, lost data, regulatory penalties or business interruption. Nothing here limits liability that cannot be limited by law.

10. Changes to these terms

We may update these terms. Material changes are announced here and, for customers, by email at least 30 days before they take effect.

11. Governing law

These terms are governed by the laws of the Republic of Uzbekistan, without regard to its conflict-of-law principles. Disputes go to the competent courts of Tashkent, Republic of Uzbekistan. Mandatory consumer protections in your country of residence continue to apply.

12. Contact

Email support@avakode.com.