Privacy policy

Last updated: 26 October 2026

Alioramus is a Chrome extension that shows the analytics and advertising tags (pixels) a web page sends, decodes them into readable events and checks them for mistakes. This policy explains what the extension and this website (alioramus.com) do with data.

In short: the extension has no server and sends nothing it reads anywhere. The optional setup agent, which is off until you turn it on, sends data only to the services you connect yourself (Anthropic with your own API key, and Google or Meta after you sign in), and only to do what you ask. Google user data is used only to provide the agent's features, never for advertising, never sold and never used to train AI models.

Who we are

Alioramus is operated by Eyal Moyal ("we"). For anything about privacy, email support@alioramus.com.

The extension: what it processes

Alioramus has permission to read the websites you visit, because a pixel helper has to see a page's tag traffic. It only looks at that traffic:

Every page you open (on by default, like other pixel helpers). The extension reads the network requests of your tabs that match known tag endpoints (for example Google Analytics, Google Tag Manager, Meta Pixel, TikTok Pixel), so the toolbar icon can show how many tags a page sent and the side panel can show them. Everything else is ignored. You can turn this off in the side panel's settings; then only the tab shown in an open side panel is read.
DevTools panel. While DevTools is open on a tab with the Alioramus tab selected, it reads the same kind of requests for that tab, with full request and response detail.
Page calls. A small script on each page notes the tag calls made by the page's own scripts (such as dataLayer.push, fbq or gtag) and passes them to the extension, which uses them the same way (or drops them at once when scanning is off and no panel shows that tab). The page itself keeps only its most recent calls, until you leave it.
Site read. Once per site, the extension reads that site's public files (such as robots.txt, the sitemap and its own scripts), without cookies, to describe the site's setup in the Site tab.

These requests can contain identifiers set by the tag vendors (client ids, click ids, hashed emails) and the contents of e-commerce events (products, order values). Alioramus shows them to you because that is what a tag debugger is for. It does not read page content, form fields, passwords or cookie values beyond what the tag requests themselves carry.

Where the data stays

On your device. Alioramus has no server. The extension never transmits anything it reads. Processing happens in the extension. What it saw on each tab is kept in the browser's session storage so it survives Chrome pausing the extension; it is deleted when you close the tab or quit the browser. Recordings you make in the DevTools panel are saved in the browser's local IndexedDB for the extension so that you can reopen them. You can delete any recording, and uninstalling the extension removes all of it.

Exports are yours. "Export…" writes a file to your Downloads folder when you ask for it. Identifiers are pseudonymised by default in that file; you can turn redaction off. Nothing is uploaded.

What Alioramus does not do

No analytics, telemetry, crash reporting or usage tracking of its own.
No account and no cloud sync.
No remote code: every line of code ships in the extension package.
No selling or renting of data, no advertising, and no use of data for anything other than showing you your tags and, if you use it, running the setup agent for you.
No use of data to determine creditworthiness or for lending purposes.

Permissions

Read and change data on all websites (<all_urls>), webRequest, scripting: to see the tag requests a page sends and the tag calls its scripts make, on whatever site you open. Alioramus does not modify pages or requests.
sidePanel: the Alioramus side panel.
storage, unlimitedStorage: your preferences and local recordings.
identity (setup agent only): to let you sign in to Google through Chrome when you press Connect Google.

The setup agent (optional)

Everything above stays in your browser. The Agent tab of the side panel is an AI agent that sets up and verifies tracking for you. It does nothing until you accept an in-product notice and add your own Anthropic API key. When you use it:

Sent to Anthropic (Claude API), only for the conversation you start: your messages and summaries of what Alioramus records on the site tab the conversation works on: page URLs, the detected site profile (tools, container and pixel ids, consent state), decoded tracking events, Alioramus findings, the configuration of the Tag Manager containers, Analytics properties and Ads accounts you ask it to work on, and the text of ad-platform pages the agent reads for you. Requests go directly from your browser to Anthropic with your key; Alioramus runs no server. Anthropic processes them under your agreement with Anthropic.
Sent to Google, only after you connect your Google account: Tag Manager, Google Analytics Admin and Google Ads API calls that read or change the containers, properties and accounts you manage, each change shown to you and approved first. See Google user data.
Sent to Meta, only after you connect your Meta account: Marketing API calls that read or create the pixels and conversions you choose. See Meta user data.
Ad-platform tabs (Meta, TikTok and others): the agent can operate pages in your own logged-in browser after a per-platform notice you accept. Those platforms' terms restrict automated access; your account carries that risk. Anything permanent (creating a pixel, accepting terms, generating tokens, sharing access) needs your explicit approval.
Redacted before anything reaches Anthropic: every result the agent's tools return passes through one redaction step in the extension. Request and response headers and cookies are dropped. Identifier fields (analytics client ids, click ids such as gclid or fbclid, email and phone fields) are replaced with stable anon_… tokens. Email addresses, phone numbers, card numbers, access tokens and API keys found in page text or URLs are removed. Account ids (pixel, GA4, GTM ids) stay readable because the agent needs them.
Never sent: cookies, passwords, form inputs typed by visitors, your API key or sign-in tokens inside any message, or data from other tabs. The agent refuses to type passwords, tokens, card numbers or real-looking personal data, and hands sign-in, verification-code, CAPTCHA, billing and security screens to you.
Test submissions: when the agent fills a form on your site to verify tracking, it uses a synthetic identity (an example.com address, a fictional 555-01xx number, the name "Alioramus Test").
Stored locally only: your API key and settings (chrome.storage.local), the agent's conversation log (IndexedDB, last 30 runs), and an append-only activity log of every change the agent made, with your approval and the outcome (IndexedDB, kept 90 days by default; 30 days or 1 year in Agent → Settings).
Your controls: Agent → Settings exports conversations and the activity log as JSON, and "Delete all agent data" removes conversations, the activity log, your API key, agent settings and platform consents from this browser. A "never allow the agent on these domains" list stops the agent from acting on the sites you name.

Builds of the agent can also ask for the debugger, tabs and webNavigation permissions. The agent attaches Chrome's debugger only to the ad-platform tab it is working in, only for a step that ordinary clicks cannot do, and detaches on Stop or after a minute of inactivity; Chrome shows "Alioramus started debugging this browser" while it does. Response bodies it reads this way are capped, redacted and used for that step only, never stored. Screenshots are off by default and, when on, stay in your browser and are never sent to the model.

Google user data

When you press Connect Google in Agent → Settings, Google asks you to allow Alioramus these permissions:

Permission (scope)	What Alioramus does with it
`tagmanager.readonly`	Lists your Tag Manager accounts and containers and reads their tags, triggers and variables, so the agent can see what is already installed and reuse it.
`tagmanager.edit.containers`	Creates and edits tags, triggers and variables in a workspace of the container you chose, for the tracking you approved.
`tagmanager.edit.containerversions`	Creates a container version from that workspace so it can be tested as a draft and rolled back.
`tagmanager.publish`	Publishes that version, only after it passed the tests and you approved publishing.
`analytics.edit`	Reads your Google Analytics 4 properties and data streams, and creates the key events and settings in the property you chose.
`adwords`	Reads your Google Ads accounts and conversion actions, and creates or reuses conversion actions in the account you chose.

How it is used: only to carry out the setup and verification you ask for in the agent, inside the scope you approved (site, account, container, publish or draft-only). Every change is shown to you before it is made.
Where it goes: Google API responses stay in your browser. The parts the agent needs to plan its next step (names, ids and settings of containers, tags, triggers, properties and conversion actions) are sent to Anthropic's API with your own key, as described above, after redaction. Nothing goes to us; we run no server.
Storage: the Google access token is kept in the browser's session storage and expires after about an hour; it is deleted when you quit the browser or press Disconnect. Alioramus never sees your Google password.
Sharing: Google user data is not sold, not used for advertising, not shared with anyone except as needed to provide the feature you asked for (the Anthropic API call above), to comply with law, or with your explicit consent.
AI training: Alioramus does not use Google user data to develop, improve or train generalised AI or machine-learning models.
Revoking access: press Disconnect in Agent → Settings, and remove Alioramus at myaccount.google.com/permissions.

Limited Use. Alioramus's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Meta user data

When you press Connect Meta, Meta's own login window asks you to allow ads_management and ads_read. Alioramus uses them only to list your ad accounts and pixels, to read or create the pixel and conversions you choose, and to send test events to that pixel under the test code you give it, so they show only in Events Manager's Test events tab; a test event carries the synthetic test identity described above (hashed), never a real person's data. The access token is kept in your browser (chrome.storage.local) until you press Disconnect or remove the extension; it is never sent to us or included in messages to Anthropic. You can also remove Alioramus in your Facebook settings under Business Integrations. See how to delete your data.

This website

alioramus.com sets no cookies and runs no advertising tags. It counts visits with Vercel Web Analytics, served from this site: for each page view it records the time, the page (with filtered query parameters), the referring site, the approximate location (country, region and city), and the browser, operating system and device type. It uses no cookies and does not tie page views to a person or an IP address; visitors are told apart within a day by a hash of the request that is discarded after 24 hours, so we see totals, not people. Fonts and images are served from this site. The hosting provider, Vercel Inc., processes standard request logs (such as IP address, user agent and the page requested) to deliver the site and protect it from abuse. If you email us, we use your message and address only to answer you.

Your choices and rights

Because the extension keeps its data on your device, you control it directly: delete recordings in the extension, use "Delete all agent data" in Agent → Settings, or uninstall the extension to remove everything it stored. We do not hold copies. Depending on where you live (for example under the GDPR or the CCPA) you may have rights to access, correct, delete or object to processing of personal data; email us and we will answer within 30 days. You can also complain to your local data protection authority.

Children

Alioramus is a professional tool and is not directed at children under 16. We do not knowingly process their personal data.

Changes and contact

Changes to this policy appear on this page with a new date. If a change affects how Google or Meta user data is used, we will ask for your consent in the extension before it applies. Questions: support@alioramus.com.