1. Who we are
heyEO provides AI-search visibility, technical SEO, audience-fit analysis and outcome monitoring for small teams. For the personal data described here, heyEO is the controller. Contact us at support@heyeo.io.
2. Information we collect
Account and workspace information
Your name, email address, authentication identifiers, workspace membership and role, invitations, preferences, and account activity. When you sign in with Google, GitHub, LinkedIn or X, we receive your basic profile (name, username and profile picture) and, where the provider shares it, your email address. We do not receive your password or post on your behalf.
Project, scan and recommendation information
Websites and URLs you submit, declared audiences and competitors, monitored prompts, publicly accessible page content and technical metadata collected during crawls, scan results, recommendations, changes you record, and before/after observations.
Google data you choose to connect
If a workspace owner connects Google, heyEO requests read-only access to Google Search Console and Google Analytics. We access the selected properties and import daily aggregate clicks, impressions, click-through rate, average position, sessions, engaged sessions, key events, AI-referral sessions, and up to 25 top pages or landing pages. We do not import or retain Search Console queries, countries or devices, raw Analytics events, client IDs, or user-level Google Analytics data.
AI assistants you choose to connect
heyEO can be connected to AI assistants and coding tools that support the Model Context Protocol, such as Claude, ChatGPT and Cursor. When you connect one, you sign in to heyEO and grant that assistant access to act as you. We record the grant, the assistant's client identifier, short-lived access and refresh tokens, and a log of the heyEO tools the assistant calls and when. The assistant can only reach the workspaces and projects your account can already see, and it can only start a credit-spending scan after showing you the price.
Project, scan and recommendation information that a tool returns is sent to the assistant you connected and becomes subject to that provider's privacy policy. heyEO does not receive or store your conversations with the assistant and does not control how the provider uses what it receives.
Billing and communications
Subscription and credit-pack status, transaction identifiers, invoices and entitlement records. Payment-card details are collected by Stripe and are not stored by heyEO. We also process email delivery status and your digest preferences.
Usage, device and support information
IP address, browser and device information, security and diagnostic logs, service usage, support correspondence, and first-party activation milestones such as completing onboarding or a first scan. With your consent, the website uses Google Analytics to understand visits, page usage and which channels bring new customers (see Cookies and similar technologies). heyEO does not use Google user data for advertising.
3. How and why we use information
- Provide accounts, workspaces, scans, reports, schedules, recommendations, billing, collaboration and support.
- Import and display the Google outcome reporting you explicitly connect.
- Answer requests from AI assistants you explicitly connect, and record what they do in your account.
- Secure the service, prevent abuse, troubleshoot failures and maintain audit records.
- Send invitations, requested digests and operational, billing or security notices.
- Measure and improve reliability, usability and the effectiveness of user-facing features.
- Meet legal, accounting and regulatory obligations and enforce our terms.
Under UK data-protection law, we rely on performance of our contract where processing is necessary to provide heyEO; our legitimate interests in securing, operating and improving the service where those interests are not overridden by your rights; consent where required, including when you connect optional Google services or an AI assistant; and legal obligation where applicable.
4. Google API data and Limited Use
heyEO uses information received from Google APIs only to provide the visible Search Console and Google Analytics connection, property-selection, aggregate reporting and outcome-comparison features that you request. Access is read-only. Google refresh tokens are encrypted in a restricted secrets vault and are not exposed to browser clients or ordinary database roles.
We do not sell Google user data, use it for advertising, use it to determine creditworthiness, or transfer it to data brokers. Humans do not read Google user data except when you ask for support involving specific data, when necessary for security or legal compliance, or when data has been aggregated for internal operations.
heyEO's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5. When we share information
We share information only as needed with service providers acting for us: Supabase for authentication and database hosting; Cloudflare for application hosting, security, delivery and encrypted storage of AI-assistant connection grants; OpenRouter and selected model providers for AI analysis; Stripe for payments and billing; Resend for transactional email; and Google for authentication, connected reporting APIs and, with your consent, site analytics. Workspace information is also visible to authorised members of that workspace according to their role.
When you connect an AI assistant, the provider of that assistant (for example Anthropic, OpenAI or Cursor) receives the information its tools request on your behalf. That provider acts for you, not for heyEO, and is not our service provider.
We may disclose information when required by law, to protect rights or security, or in connection with a merger, financing, acquisition or sale, subject to appropriate safeguards and notice where required. We do not sell personal information.
6. International transfers
Some providers process information outside the United Kingdom. Where required, we use recognised safeguards such as UK adequacy regulations, the UK International Data Transfer Agreement or the UK Addendum to approved standard contractual clauses. Contact us for more information about safeguards relevant to your data.
7. Retention
- Google project-level daily aggregates are retained for up to 13 months; page-level Google rows for up to 90 days.
- Google OAuth state is short-lived. Refresh tokens are kept until you disconnect Google, close the relevant account, or the token is revoked or no longer needed.
- AI-assistant connection grants and tokens are kept until they expire, you disconnect the assistant, or the grant is revoked. Logs of the tools an assistant called are kept with your account's other activity records.
- Account, workspace, project, scan and recommendation records are kept while your account is active and afterwards only as reasonably necessary to provide exports, resolve disputes, enforce agreements, maintain security and meet legal obligations.
- Billing and transaction records may be retained for the period required by tax, accounting and anti-fraud law.
- Security, diagnostic and email-delivery records are retained for a limited period appropriate to their purpose.
8. Security
We use access controls, encryption in transit, restricted server credentials, row-level workspace isolation, signed payment webhooks, and limited-access secrets storage. No online service can guarantee absolute security, so please use a strong account and notify us if you suspect unauthorised access.
9. Your choices and rights
You can change or withdraw your analytics cookie choice at any time from Cookie settings in the site footer. You can disconnect Google from workspace settings, change digest preferences, and revoke Google access from your Google Account. You can disconnect an AI assistant from within that assistant, or ask us to revoke its access. Depending on applicable law, you may request access, correction, deletion, restriction, objection, or portability of personal data, or withdraw consent without affecting earlier lawful processing.
You have the right to object to processing based on our legitimate interests. Email support@heyeo.io to exercise a right or request account or connected-data deletion. We may need to verify your identity. You may also complain to the UK Information Commissioner's Office or your local data-protection authority.
11. Children
heyEO is a business service and is not directed to children. You must be at least 18 years old to create or administer a workspace.
12. Changes
We may update this policy as heyEO or applicable law changes. We will update the date above and provide additional notice when a change materially affects how we use personal data. See also our Terms of Service.