Privacy
Last updated: 1 November 2026
Operated by TECH BUS LLP · BIN 240740023449 · 3 Dzharkentskaya St., Almaty, Kazakhstan
Harry works by reading and writing your team’s working conversation, so it is worth being exact about what that means. This page says what we hold, why we hold it, and how to make us stop.
Who we are
Harry is an AI business assistant operated by the company named at the top of this page, registered in Kazakhstan. For anything on this page, including access and deletion requests, write to privacy@getharry.app.
What we collect
We hold eight kinds of data, and nothing else:
- A copy of your CRM’s data, if you connected one: deals, leads, contacts, funnels, activities and client conversations — and the access key to it, stored encrypted and never shown back.
- A copy of your advertising results, if you connected Meta Ads or Google Ads: the ad accounts you chose, their campaigns and each campaign’s daily figures — and the access token, stored encrypted. The next section says exactly what.
- A copy of your website traffic, if you connected Google Analytics: the properties you chose and their visits by day and source — sessions, users, page views, engagement, key events and revenue — and the access token, stored encrypted. These are totals; nothing in them identifies a single visitor.
- The messages you exchange with Harry — text, voice notes and files you send him, plus his replies.
- Your messenger identity — the account id, display name and language your messenger reports. We key everything internally on our own person id, not on that handle.
- The working record your organisation builds: people and reporting lines.
- Operational logs — timestamps, error traces and job records needed to run and debug the service.
- Product analytics — how visitors reach and use this site and the console, described in the next section.
Advertising accounts
An admin of your organisation can connect Meta Ads (Facebook and Instagram) or Google Ads. For Meta, they sign in with Facebook Login for Business and tick the ad accounts Harry may read; Meta grants read-only access (ads_read) to your business, not to the person clicking.
For Google Ads, they sign in with Google and allow Harry to reach the Google Ads accounts their Google account can see. Each account becomes its own connection, and the admin can remove any of them.
From each account Harry reads its name, currency and time zone, its campaigns with their status, objective and budget, and each campaign’s figures by day: impressions, reach, clicks, spend, conversions and the actions the platform counts. He never creates, changes or pauses a campaign, and reads nothing about the individual people who saw or clicked your ads.
We use these figures for one thing: showing your organisation its own advertising results, next to its sales, in its dashboards, reports and answers. They are never shown to another organisation, sold, or used to advertise anything. Disconnecting an account deletes its figures and its token — see Data deletion.
Google user data
This section covers what Harry receives from Google APIs. An admin of your organisation can connect Google Ads, Google Analytics, or both, by signing in with Google; each is asked for separately, only when that product is connected. From Google Ads Harry reads what the previous section lists. From Google Analytics he reads the properties the Google account can see, each property’s name, currency and time zone, and its traffic by day and source: sessions, users, page views, engagement, key events and revenue.
Harry uses this data for one purpose: showing your organisation its own advertising and website results in its dashboards, scheduled reports and answers to its questions. He only reads. He never creates, changes or deletes anything in Google Ads or Google Analytics.
Google user data reaches the people in your organisation, within their role, and two providers that process it on our behalf and for no purpose of their own: DigitalOcean, which hosts our servers, database, file storage and backups, and Anthropic, whose Claude models write Harry’s answers. Nobody else receives it. We do not sell it, use it for advertising, give it to data brokers, show it to another organisation, or send it to our analytics provider. We would disclose it otherwise only where the law requires.
No person at Harry reads it, except with your organisation’s permission for support, to investigate security problems or abuse, or where the law requires.
Google user data is never used to create, train or improve artificial intelligence or machine-learning models, generalised or foundational, ours or anyone else’s. Anthropic processes it under commercial terms that do not allow training on what it receives.
Harry’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Disconnecting an account or a property deletes everything copied from it and its token, and you can revoke Harry’s access in your Google Account at any time — see Data deletion.
Product analytics
This site and the web console use Amplitude to show us how people find Harry and where they get stuck. It records pages viewed, buttons pressed, the campaign or site that sent you, your device and browser, and a recording of your visit to this site. It sets one cookie on getharry.app to recognise the same browser across visits.
When you sign up, we tell Amplitude about the steps that follow: opening a workspace, connecting a CRM or a messenger, and subscribing. Those events carry an internal number for you and your organisation, never your email or your name. The console is not recorded, and nothing from your CRM or your conversations is sent.
Why we process it
To run the service you asked for: answering questions, keeping the record and sending the reports you set up.
To keep it working and safe: diagnosing failures, preventing abuse, and meeting legal obligations where they apply.
Large language models
Producing a reply means sending the relevant part of the conversation, and the records it touches, to Anthropic, whose Claude models Harry runs on. Anthropic processes it on our behalf under its commercial terms and does not use it to train models.
Voice notes are transcribed by Groq, which receives only the audio. Images and documents you send are read by Claude when a request needs them.
Where it lives
One Postgres database that we operate holds the CRM copy, the working record, the conversation history and the job queue. Files you send are stored in an object store; the database keeps only a reference to them.
Separation between organisations is enforced by row-level security inside Postgres, so an application bug above it cannot expose one organisation to another.
How we protect it
Your data, and above all the keys to the services you connect, is protected in layers:
- Encryption in transit: every connection uses TLS — between your browser or messenger and us, between our services and the database, and to every provider we call.
- Encryption at rest: the database, file storage and backups are encrypted by our hosting provider.
- Access tokens and keys to your connected services are encrypted again by Harry before they are stored, with keys kept outside the database that can be rotated. They are never shown back, even to admins.
- Organisations are separated by row-level security inside Postgres, and the application connects to the database without administrative rights.
- Inside an organisation, each person sees only what their role allows.
- Our operators sign in with one-time codes and reach data only through an audited console.
Who can reach it
Three groups, and no others:
- People in your organisation, scoped by their role — an admin sees the organisation, everyone else sees themselves and the people who report to them.
- Our operators, for support and diagnosis, through an audited console.
- Our providers, strictly as processors: DigitalOcean (hosting), Anthropic (language models), Groq (voice transcription) and Amplitude (product analytics, which never receives your CRM data, your conversations or data from Google).
What we never do
We do not sell your data, we do not use it for advertising, and we do not share one organisation with another.
How long we keep it
For as long as your organisation uses the service, plus a short window afterwards for backups to roll over. Ask us to delete an organisation and we delete it, including its conversation history.
Your choices
You can stop Harry at any time by blocking the bot in your messenger. You can ask for a copy of your organisation’s data, or its deletion, at privacy@getharry.app; the Data deletion page says how to remove a single connected account yourself.
The messenger you reach Harry through is a separate service with its own privacy policy; this page covers what happens on our side of that conversation.
Changes to this page
When this policy changes we update the date at the top. Material changes are announced in the chat, not only here.