Legal · Last updated 30 October 2026

Privacy Policy

A bridge carries your integration’s calls to Microsoft Graph or HubSpot and back. The content of those calls — messages, events, contacts, CRM records — passes through and is never stored or logged. This policy explains what we do keep.

1. Who we are

Avakode Bridges (EWS Bridge at ewsbridge.com, Legacy Bridge at legacybridge.dev, the console at bridges.avakode.com) is a service of Tigran Avakov, a self-employed individual, Mirzo-Ulugbek 45A, 100007 Tashkent, Uzbekistan. In this policy “we” and “Avakode” mean that entity.

2. What this policy covers, and our role

Personal data we handle when you visit this website, create a bridge and use the console, when your integration calls a hosted bridge, when a self-hosted server checks its licence, when you buy a plan and when you contact support. For the content your integration sends through a hosted bridge, you (or your organisation) are the controller and we act as your processor, only to perform the calls you send. A self-hosted bridge runs entirely on your server; we receive only its licence check (section 5).

3. What passes through and is never stored

  • Request and response bodies. Each call is translated in memory, performed with your tenant’s or portal’s credentials and answered. Message bodies, subjects, addresses, attachments, events, contacts and CRM properties are not written to any database, file, log or report.
  • Coverage events hold metadata only: the operation name, whether it translated, a short reason or error code, the names of schema fields that could not be returned, the number of upstream calls, the latency and a request id. They feed your usage figures and gap report.
  • Free tools. Files uploaded to the EWS log analyzer and the HubSpot scanner are read in memory and discarded with the response. The upload itself, its file names and the paths and addresses in it are never kept; the HubSpot scanner adds one run to a daily tally (section 4).

4. What we store

  • Your bridge: the email address you signed in with, your licence key and plan, and the name you give a portal. The licence key is stored encrypted (AES-256-GCM).
  • Upstream access: for EWS, the id of your Microsoft 365 tenant confirmed by your administrator’s sign-in, and a default mailbox address if one is set; for HubSpot, the access token you save and your portal id. The token is stored encrypted and never shown again.
  • Bridge keys and console sessions: stored only as SHA-256 hashes; a key is shown to you once.
  • Identifiers the translation needs, in a cache: short-lived Microsoft Graph tokens; for HubSpot, your portal id, the mapping between legacy and current list ids, engagement types and paging positions (a day) and the names and types of your portal’s properties (10 minutes); for EWS, mailbox ids (a day) and the mapping between older Exchange item ids and Graph ids (30 days), stored under hashed keys; and, for EWS synchronisation, the ids of items in a synchronised folder with Microsoft’s change link, encrypted, for 30 days after the last use.
  • Agency sign-in: your email address and one-time sign-in links, stored as hashes and valid for a short time.
  • Backups: a daily copy of the database, deleted after 90 days.
  • A daily tally of HubSpot scanner runs: per day, how many scans ran, how many of them found a legacy call, the sum of the shares of those calls the bridge translates, and how many found a call to HubSpot’s Pipelines API v1. Counters only: no IP address, no time of day, no file, path, address or token, nothing that identifies you. We keep it to see how many scans reach a report and what share of the legacy calls they find is covered by the bridge, and to plan what the bridge should cover next.

5. Licence checks

A hosted bridge checks your licence with api.avakode.com when you sign in and once a day. A self-hosted server sends its licence key, the product name and its own address to api.avakode.com when it starts and once a day. Nothing your integration sends is part of these checks.

6. Purchase data

Payments are processed by Paddle, our Merchant of Record, under the Paddle Buyer Terms; Paddle handles your payment details as its privacy policy describes. We receive your name, email, billing country and the transaction record. We never receive card numbers.

7. Support and technical data

If you write to us, we keep the message, your email address and anything you choose to attach; we never ask for your mail or CRM data. Our hosting provider processes connection data (IP address, user agent, requested path, time) to deliver and protect the service. We keep no request logs; counters of failed key attempts are kept per IP address for a minute.

8. Why we handle it

To perform the contract with you (the bridge, the console, licences, support), on the basis of legitimate interest (keeping the service secure and working), and to meet legal obligations (tax and accounting records).

9. Who else handles it

Cloudflare hosts the service, its database, storage and email sending. Microsoft and HubSpot receive the calls your integration sends through the bridge, for your tenant or portal only. Paddle handles payments. We do not sell personal data. Apart from Paddle’s checkout on the pricing pages, the only services these websites load from others are Fathom Analytics and, once we advertise on LinkedIn, the LinkedIn Insight Tag, and only on the pages named in section 12; their fonts come from our own servers. LinkedIn is the one advertising service that receives anything from these websites, as section 12 describes.

10. International transfers

Our providers operate globally, so data may be processed outside your country. Transfers from the EEA and the UK rely on Standard Contractual Clauses or the UK Addendum.

11. How long we keep it

  • Your bridge — its settings and tokens, bridge keys, usage figures, console sessions, EWS synchronisation state, coverage events and the cache entries kept under its id: while your plan is active. When the licence ends, the bridge is suspended; once our licence server has refused its licence for twelve months — counted from the first daily check that finds it suspended for its licence, with a last licence check just before — it is deleted automatically. Earlier on request.
  • Cache entries not kept under your bridge’s id (Microsoft Graph tokens, mailbox and item id mappings): they expire within 30 days. EWS synchronisation state: 30 days after its last use. Database backups: 90 days.
  • An agency account (its sign-in email) stays until you ask us to delete it.
  • The scanner tally (counters per day, no personal data): while the service runs.
  • Purchase and tax records: 7 years, as required by law. Support correspondence: 3 years.

12. Cookies, visit statistics and advertising measurement

Where. Only on the public pages of the two product websites, and on no other page. ewsbridge.com and legacybridge.dev measure these pages:

  • ewsbridge.com: the home page (/), the product pages (/coverage, /security), the pricing page (/pricing), the documentation (/docs), the free EWS log analyzer (/analyzer), its sample report (/analyzer/sample), the legal pages (/terms, /privacy, /refund) and the page you are taken to after a payment (/thanks).
  • legacybridge.dev: the home page (/), the product pages (/coverage, /security, /pipelines-v1), the pricing page (/pricing), the documentation (/docs), the free Legacy API scanner (/scanner), its sample report (/scanner/sample), the legal pages (/terms, /privacy, /refund) and the page you are taken to after a payment (/thanks).

Nothing from the console, from your bridge or from the report an uploaded file returns goes to Fathom or LinkedIn: neither runs there, nor on the checkout hub at bridges.avakode.com or on a self-hosted server. Signing in to the console happens on bridges.avakode.com, which keeps you signed in with one session cookie and runs none of the tags below.

Visit statistics. We count visits with Fathom Analytics (Conva Ventures Inc., Canada) on those pages, on the basis of our interest in knowing which pages are read. It works without cookies and does not identify you: it records the page, the site you came from, the campaign tags of the link, your browser, device type and country, and the events named below, and we see only totals. It does not wait for your choice in the cookie banner, but it respects an objection: once you choose Reject (in the banner or in Cookie settings), it stops counting further events of your visit and is not loaded on the next pages.

Advertising measurement. When we advertise on LinkedIn, those pages load the LinkedIn Insight Tag. It tells LinkedIn that a visitor who may have seen our ad came to the site, opened a sample report, opened the checkout or completed a payment. The payment is reported at the moment Paddle’s checkout confirms it, not when the thank-you page is opened, so opening that page again counts no payment. LinkedIn receives the page address, the referring page, your IP address, browser details and the time, and sets its cookies on our domain: li_fat_id (30 days, links the visit to an ad click), li_giant (7 days) and ln_or (1 day). LinkedIn uses this data under its own privacy policy and keeps it for up to 180 days; it does not tell us who you are, and we see its aggregate reports. In the UK, the EU and the other places where the law asks for consent first, the tag loads only after you choose Accept all, and that consent is the basis; elsewhere it loads by default, on our interest in measuring our advertising, and Reject turns it off. We tell where you are from your browser’s time zone, and when it does not say, we ask first. LinkedIn Ireland Unlimited Company receives the data of visitors in the EU, the EEA and Switzerland and LinkedIn Corporation (United States) that of everyone else; LinkedIn states that it transfers data under the EU-US Data Privacy Framework and Standard Contractual Clauses. Fathom is based in Canada, which the European Commission recognises as providing adequate protection for commercial organisations.

Where you came from. With the same consent (implied or given), the forge_attr cookie remembers for 30 days after your last visit how you first and last reached the site: the campaign tags in the link (utm_source, utm_medium, utm_campaign, utm_content, utm_term), the referring website, the first page you opened, the date, and the click identifier LinkedIn, Google or Meta added to the link. It holds no name, email address or anything you typed. When you open the checkout, your first visit (the campaign tags, the click identifier, the first page and its date) is passed to Paddle with the order, so that we know which campaigns bring customers; it is not used for anything else. Reject deletes the cookie.

Your choice. The forge_consent cookie keeps your choice for 182 days. Change your mind at any time with Cookie settings in the footer of those pages.

13. Your rights

You may ask us for a copy of your data, to correct or delete it, to restrict processing, or for it in a portable format. Write to support@avakode.com and we will answer within 30 days. If you are in the EEA or the UK you may also complain to your supervisory authority.

14. Changes

If we make a material change we will announce it here and, for customers, by email at least 30 days before it takes effect.

15. Contact

Email support@avakode.com, or write to Tigran Avakov, a self-employed individual, Mirzo-Ulugbek 45A, 100007 Tashkent, Uzbekistan.