Privacy Policy

hey Morse · heymorse.com · last updated 15 November 2026

hey Morse is operated by DIGITAL VIRALIST SRL, Razoare 200A/20, Florești, Cluj, Romania, 407280 (VAT RO37630978), the data controller for the processing described here ("we", "us"). hey Morse has two parts. The hey Morse connector is a remote Model Context Protocol (MCP) server that lets AI assistants such as Claude and ChatGPT read your marketing data live and read-only from Google (Analytics, Search Console, Google Ads, YouTube), Meta (Facebook Pages, Instagram, Meta Ads), LinkedIn (Pages, Ads), TikTok (Ads, organic accounts), Microsoft Advertising and HubSpot. hey Morse reports are client reports you build on heymorse.com, with an AI setup assistant, AI conclusions and an AI summary written by Anthropic's Claude API, which you can share through a private read-only link. This policy explains what data we process when you use either part at heymorse.com.

1. Data we collect

  • Account data. Your email address, used to sign you in with a one-time code and to identify your workspace, and the display name you set, if any, which the members of your workspaces see.
  • Sign-up requests. When you sign up, your email address, name and company. Requests made through earlier versions of the form may also hold a website, a description of your use case and a Facebook profile link. We keep the request's status (pending, approved or declined), its dates, which administrator decided it or which invitation code opened the account, so we can give access and start your trial.
  • Invitation codes. The invitation codes your account was given to share, and whether each has been used. We do not show the people you invite who joined with your code, and they do not see your email address.
  • Connected accounts. When you link a Google, Meta, LinkedIn, TikTok, Microsoft or HubSpot account, we receive OAuth tokens that let us read data from that platform on your behalf, together with the account's email address or member id and the list of properties, sites, pages or ad accounts it can access. Tokens are encrypted at rest. HubSpot access is read-only: we read contacts, their lifecycle stages and deals to count them (and, when you ask, deal names and amounts); contact names and email addresses are never returned.
  • Marketing data. Analytics, search, page, advertising and CRM statistics are retrieved live from the connected platform when you or your AI assistant ask for them. We do not build a copy of your platform data; results are returned to the requesting client and are not retained by us beyond transient processing and operational logs. The exception is the AI text saved with a report, described under Reports below.
  • Workspace and team. The workspace name, the email addresses of its members and who added them, and workspace settings. Members share the workspace's linked platforms and brands.
  • Brands. The brand names, other names and notes you enter, which accounts belong to each brand (account identifiers and names), and the branding you set (logo, colours, website), so questions about a client use only that client's accounts and its reports use its branding. Logos are stored in a public file store so reports can display them; anyone with a logo's web address can open it.
  • Reports. The reports you build for a brand with hey Morse reports, stored until you change or delete them: the report name; its modules (titles, the description you gave the setup assistant, and the query it chose: platform, metric, chart, breakdown and filters); section titles and the notes you write in text boxes; the AI conclusions and the AI summary, with the period they cover; and the private link token while sharing is on. AI conclusions and summaries quote figures from your platforms, so those figures are stored as part of the text. The numbers in charts are not stored: they are fetched from the platforms when the report is viewed and kept in server memory for up to 10 minutes.
  • Shared links. When you share a report, anyone with its private link can open it without signing in. They see the brand's name, logo, colours and website, the report's titles and notes, the AI conclusions and summary, and live figures for any period they choose, until you turn the link off. They do not see which accounts the report reads from.
  • Client registrations. Identifiers of the MCP clients (for example Claude or ChatGPT) that you authorise to access your workspace, and the tokens issued to them.
  • Usage counts. How many requests each workspace makes per day, by tool, platform and account identifier, and how many failed. We use these to run and support the service. They contain no questions, filters or results, and are deleted with the workspace.
  • AI usage. For each workspace and day: how many Claude API calls hey Morse made for module setup and for conclusions and summaries, the model, the token counts and the estimated cost. These records hold no prompt or answer, and are deleted with the workspace.
  • Billing records. Your plan (MCP or Studio, or none after the trial), billing interval, trial end date, whether the plan is complimentary, the Stripe customer and subscription identifiers, the subscription status and renewal date, and which accounts are in use under the plan's account limit. Payment details are entered on Stripe's pages and held by Stripe; we do not receive or store card numbers.
  • Technical data. Standard server logs (IP address, user agent, request path, timestamps, errors) kept by our hosting provider for security and troubleshooting.

Cookies. We set only cookies that are strictly necessary for signing in: morse_session (your signed sign-in session, 30 days), morse_signed_in (a flag with no personal data that lets the website show a Dashboard link, 30 days) and morse_link_return (the page to return to after you link a platform, 15 minutes). The platform review console sets morse_review for platform reviewers only. We use no analytics or advertising cookies and no third-party tracking scripts.

2. How we use data

  • To authenticate you and the clients you authorise.
  • To retrieve the marketing data you request from the platforms you connected, and return it to your client.
  • To build, show and share the reports you create, and to have Anthropic's Claude API set up modules and write the conclusions and summaries you ask for.
  • To review sign-up requests, run your trial and plan, and bill you through Stripe.
  • To operate, secure, debug and improve the service, and to contact you about it.

We do not sell personal data, use it for advertising, or share it with third parties except as described below. Data is processed only as needed to provide the features you use.

2b. Legal bases

Under the GDPR we rely on these legal bases:

  • Contract (Art. 6(1)(b)): to run the service you signed up for, including sign-in, linked platforms, reports, the AI features you ask for, and billing.
  • Legitimate interests (Art. 6(1)(f)): to keep the service secure, prevent abuse, review sign-up requests, and keep usage counts and server logs to support and improve it.
  • Legal obligation (Art. 6(1)(c)): to keep invoices and billing records as accounting and tax law requires.
  • Consent (Art. 6(1)(a)): where we ask for it. You can withdraw consent at any time.

3. Google user data

hey Morse's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We request read-only access to Google Analytics, Search Console and YouTube (channel data and YouTube Analytics). Google Ads offers no read-only permission, so we request its standard access and use it only to read reports; hey Morse never creates or changes anything in your Google Ads accounts. Google data is used only to provide the functionality you request. When you ask for an AI conclusion or summary in a report, the Google figures it covers are sent to Anthropic, our processor, to write that text, which is then stored with the report (see sections 1 and 5). Google data is not used to develop, improve or train generalised AI or machine-learning models, by us or by Anthropic, and no human reads it except with your permission, for security purposes, or as required by law.

4. Meta data

We request access to the Facebook Pages, Instagram professional accounts and ad accounts you have a role on, in order to retrieve their insights on your behalf. Meta data is retrieved on demand and is not stored beyond transient processing, except for the AI conclusions and summaries you ask for in a report, which quote figures and are stored with the report until you change or delete them. It is used only to provide the functionality you request, in accordance with Meta's Platform Terms. You can revoke access at any time from your Facebook settings; see data deletion.

4b. LinkedIn data

We request access to LinkedIn pages you administer and advertising accounts you can use and, if you link your personal profile, to your own posts' statistics and follower numbers, in order to retrieve these statistics on your behalf. LinkedIn data is retrieved on demand and is not stored beyond transient processing, except for the AI conclusions and summaries you ask for in a report, which quote figures and are stored with the report until you change or delete them. It is used only to provide the functionality you request, in accordance with LinkedIn's API terms. You can revoke access at any time from your LinkedIn settings.

5. Sharing and processors

We rely on the following providers to run the service; each processes data only on our instructions:

  • Vercel: application hosting and request logs. The application runs in Vercel's Frankfurt (EU) region.
  • Supabase: database, file storage for brand logos, and authentication (workspace records, encrypted tokens, one-time codes), hosted in the EU.
  • Resend: delivery of sign-in and service emails, and of what you send through the Request a platform and Report an issue forms.
  • Stripe: subscriptions, checkout, invoices and VAT. Stripe receives your workspace's email address and identifier, and collects your billing name, address, VAT number and payment details on its own pages.
  • Anthropic: hey Morse reports use Anthropic's Claude API. When you set up a module, we send the brand name, the list of metrics available for its platforms and your description of the module. When you ask for an AI conclusion, we send the brand name, the module's title and metrics, and its numbers for the period and the previous period, including breakdown labels such as campaign names. When you ask for an AI summary, we send the brand name, the report name, the section titles and notes in the report, and the same information for every module in it. Anthropic does not use this data to train its models.
  • Google, Meta, TikTok, Microsoft, LinkedIn and HubSpot: the platforms whose APIs we call with your authorisation.

Data you request through an AI assistant is sent to that assistant's provider (for example Anthropic for Claude or OpenAI for ChatGPT) under their own terms.

Anthropic, Vercel, Resend and Stripe are US companies, so some data may be processed outside the European Economic Area. These transfers are covered by the European Commission's Standard Contractual Clauses in each provider's data processing terms.

5b. Requests from public authorities

We do not sell personal data and do not give public authorities access to our systems. If a public authority asks us for personal data of our users, including data received from Google, Meta, TikTok, Microsoft, LinkedIn or HubSpot:

  • we check that the request is lawful, has a valid legal basis and is issued by an authority competent to make it, and refuse it if it is not;
  • we challenge requests we consider unlawful, overly broad or disproportionate, using the remedies available to us under the applicable law;
  • if we must comply, we disclose only the minimum data necessary to answer the request;
  • we keep a record of every request, our response, the legal reasoning behind it and the people involved;
  • we inform the affected users unless the law prohibits it.

6. Retention and deletion

Account data and connected-account tokens are kept while your workspace is active. Reports, with their notes, AI conclusions and summaries, are kept until you change or delete them or the workspace is deleted; a shared link stops working as soon as you turn it off. Sign-in codes expire within an hour; access tokens issued to clients expire within an hour and refresh tokens within 30 days. Invoices are kept, by us and by Stripe, for as long as Romanian accounting and tax law requires.You can disconnect a platform by revoking hey Morse in your Google, Facebook, LinkedIn, TikTok, Microsoft or HubSpot account settings, and you can request deletion of your workspace and all associated data by emailing email@heymorse.com. We delete it within 30 days.

7. Security

All traffic is encrypted in transit (HTTPS). OAuth tokens are encrypted at rest with keys held separately from the database. Access to production systems is restricted to the operators of the service.

8. Your rights

Under the GDPR you have the right to access, correct, export or delete your personal data, to object to or restrict its processing, and to withdraw consent at any time. Contact us at email@heymorse.com to exercise these rights. You may also lodge a complaint with the Romanian supervisory authority (ANSPDCP, dataprotection.ro) or the authority in your country of residence.

9. Changes

We may update this policy as the service evolves. The date above indicates the latest revision; material changes will be announced on this page.

10. Contact

DIGITAL VIRALIST SRL, Razoare 200A/20, Florești, Cluj, Romania, 407280. Questions about this policy: email@heymorse.com. See also the terms and conditions.