Emma by Localeyes
PrivacyTerms

Privacy policy

Last updated 19 October 2026

Emma is the SEO workspace used by the Localeyes agency team to look after its clients' websites. It is not a public service: accounts are created by an Emma administrator for members of the team. This policy explains what Emma does with information it receives, including from Google.

Information from Google

When a team member connects a Google account to Emma, Emma asks Google for:

  • Your email address (userinfo.email), to show which Google account is connected.
  • Read-only access to Google Search Console (webmasters.readonly), for the properties that account can already see.

Emma uses Search Console data only to report on and improve the search performance of the agency's clients' websites: clicks, impressions, average position and the searches and pages behind them. It reads this data; it never changes anything in Search Console.

How it is used

  • Figures are shown to signed-in team members in Emma's screens, reports and alerts.
  • When a team member asks Emma's assistant a question, the relevant figures are sent to the AI model that writes the answer, through OpenRouter, only to answer that question. Emma does not use Google user data to train or improve AI models.
  • Emma does not sell Google user data, use it for advertising, or share it with anyone other than the service providers below, for running Emma.

Emma's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Where it is kept

Emma runs on Vercel and keeps its data in a Supabase database. Google access tokens are stored encrypted, and only Emma's server uses them. Search Console figures are kept for as long as the client is looked after by the agency, so performance can be compared over time.

Other information

Emma keeps team members' names and email addresses for signing in, a record of the changes made to client websites and who approved them, and the conversations team members have with Emma's assistant.

Removing access and data

  • Disconnect a Google account in Emma under Integrations → Google, or revoke Emma's access at any time at myaccount.google.com/permissions. Emma then stops reading that account's data.
  • To have data Emma holds deleted, email lawrence.timmins@jpress.co.uk. We will delete it within 30 days, unless we need to keep it to meet a legal obligation.

Contact

Questions about this policy or Emma's use of data: lawrence.timmins@jpress.co.uk.