Chrome may display warnings such as ‘Block content on any page’ and ‘Display notifications’, alongside access to the listed mail websites. A request to read and change site data can feel broad when all you wanted was an email tracking button. It is reasonable to want an explanation before granting that access.
Elite Mail Suite works inside Gmail™, Microsoft Outlook, and Yahoo Mail to add controls that the inbox does not provide on its own. Here is what the browser permissions enable, how Gmail browser tracking differs from cloud workflows, and which settings give you control over your data. This guide covers the browser extension; provider connections, the Gmail add-on, and native apps have their own authorization screens.
Why does an email tracker need access to my inbox website?
The extension needs to interact with the inbox page to add compose controls, insert the tracking resources you choose to send, and show activity beside the relevant message. That interaction requires site access. A permission warning describes the capability being granted; it does not describe every data flow or replace the privacy policy.
Elite’s Chrome extension declares specific Gmail, Outlook, and Yahoo Mail hosts, plus Elite’s website and tracking service. Its content scripts run on the supported mail sites. It does not declare the browser history permission or an all-websites content-script match. The separate content-blocking permission can still produce a broad warning, which is why reading the purpose of each permission matters.
You can inspect the sites allowed for the extension in Chrome’s extension details. Removing access to an inbox can prevent its controls from appearing there. Your installed version and browser determine the exact wording of the permission prompt.
What each browser permission is for
| Permission | What Elite uses it for |
|---|---|
| Mail-site and Elite-site access | Integrates controls with supported inboxes and communicates with the Elite account and tracking services. |
| Local storage | Keeps preferences, account state, and account-scoped Gmail tracking history and associations in the browser. |
| Identity | Opens the browser-supported account connection flow. Separate provider consent screens describe any provider access. |
| Network request rules | Applies tracker protection and self-open protection so the sender’s own image requests do not inflate tracking activity. |
| Push messaging | Receives service updates through Google Firebase Cloud Messaging when push is configured and enabled. |
| Notifications | Displays enabled activity alerts and reminders. |
| Alarms | Schedules periodic activity checks and background work. |
Turning off an alert changes notifications; it does not automatically stop the underlying tracking. Incoming tracker protection and outgoing tracking are separate controls too. Review the privacy controls documentation for the distinction.
What stays in the browser, and what reaches Elite?
For Gmail browser tracking, message subjects, email addresses, mailbox identifiers, reply observations, and the association between a message and its independent tracking ID stay in account-scoped browser local storage, not Chrome Sync. Elite’s tracking service receives opaque random tracking IDs and eligible, freshly authored link destinations. Events are matched back to the Gmail message locally.
Local storage is still data on your device. Someone with access to your browser profile may have access to that local information. Clearing extension storage or reinstalling can remove local associations; local operation also depends on the browser being available.
| Workflow | Data handled by the service |
|---|---|
| Independent email tracking | Tracking identifiers, link destinations where applicable, timestamps, and engagement signals. IP, user-agent, and approximate location depend on available signals and retention settings. |
| Outlook and Yahoo tracking | Their supported cloud tracking associations, unlike Gmail’s browser-local message associations. |
| Fresh cloud messages and campaigns | Recipients, subject, authored message content, attachments, schedule, and delivery state supplied to that workflow. |
| Document, video, and signature requests | The request details and files, recordings, signing material, and related records that participants submit through those workflows. |
| Account and operations | Account and billing identifiers, connection credentials where applicable, security records, and support information needed to operate the service. |
The narrow Google cloud sending connection does not provide Gmail mailbox reading, reply detection, or bounce detection. Optional Contacts and Picker-selected files require their own grants. A local Gmail boundary does not mean that an uploaded document or a message you compose in Elite’s cloud outbox stays only on your computer.
Our privacy policy states that we do not sell personal information or use tracked-message data for third-party advertising. Google Workspace data is excluded from generalized or foundational model training. Those commitments are different from promising that no data ever leaves the browser.
The safeguards behind the permission prompt
Elite’s privacy approach combines data minimization with controls over account access, shared material, and retention. You can examine the security page rather than relying on a badge or a reassuring slogan.
- Gmail browser tracking keeps mailbox context local while using independent tracking identifiers for service events.
- Production connections use encrypted transport. Provider refresh credentials held by the service are encrypted at rest.
- Tenant-scoped APIs and team roles restrict workspace actions to the authenticated account and authorized role.
- Account controls include optional authenticator MFA, device management, and revocable connections.
- Security and administrative actions produce audit history; signing workflows retain completion records and file hashes.
- Tracking permission modes, separate retention settings, and verified privacy requests give teams ways to implement their data-handling decisions.
Private request links need care as well. A document or recording request link can grant access to whoever possesses it; possession alone does not prove identity. Share links only with the intended person, use the available expiry and cancellation controls, and collect only the material required for the task. Revoking access cannot retrieve a copy someone already downloaded.
How long is tracking data kept?
The current privacy policy specifies default retention of 365 days for engagement events and 30 days for network and approximate-location fields. Authorized customers can configure event retention from 1 to 2,555 days and network retention from 0 to 365 days. A shorter network window can remove IP and location details while retaining a higher-level event.
These are tracking retention settings, not a promise that every type of account data expires on that schedule. Content and uploaded files have their own lifecycle. Account, billing, security, and rights-request records can require longer retention, and backups can remain during a recovery window. Review the policy and the applicable workflow before choosing a period for sensitive material.
What changes when I turn tracking off or disconnect?
| Your action | What changes |
|---|---|
| Send a message without tracking | The message is sent without the tracking resources controlled by that compose choice. This does not stop trackers in older messages. |
| Stop tracking an existing message | Prevents future collection for that tracker after the stop succeeds. Existing history is retained until deletion or retention removes it. |
| Delete Gmail tracking history and events | Removes the local association and collected tracking events. Minimal opaque redirects remain so links already delivered can still reach their destinations. |
| Turn off notifications | Stops the selected alerts. Tracking and retained history are separate. |
| Disconnect a provider or revoke a connection | Ends ongoing access through that connection. Previously sent messages, collected records, and downloaded files are not recalled. |
Do not treat disconnecting as a substitute for stopping existing trackers or deleting retained data. If a stop is pending because the browser is offline, wait for the completed state before assuming collection has ended. The first tracked email guide explains the message-level Stop tracking control.
How Elite supports GDPR responsibilities
Elite provides controls for recorded recipient permissions, strict consent enforcement, configurable retention, exports, deletion, and verified privacy requests. Strict consent mode blocks new tracking when the required current permission evidence is unavailable. The disabled mode blocks new trackers for the relevant account or team scope.
For customer-directed tracking, the customer generally determines the purpose and audience as controller, while Elite acts as processor. Elite has its own responsibilities for account administration, security, and billing. The European Data Protection Board’s explanation describes these roles and the need for a binding processing agreement.
Review and execute the Data Processing Addendum where required, check the subprocessors and processing locations, and determine the lawful basis and any applicable electronic-communications consent requirements for your use. Selecting ‘legitimate interests’ in a setting does not by itself establish a lawful basis. The same is true of enabling strict consent: a software setting supports a compliance process rather than completing it.
Website analytics is a separate choice. The policy describes Google Analytics and Microsoft Clarity as disabled until analytics permission is given, and excludes recipient-facing shared documents, signatures, polls, and videos from those tools. You can change that permission through Privacy choices on the privacy policy page.
How do Elite’s safeguards relate to HIPAA?
Access controls, encrypted transport, audit history, data minimization, and retention controls are relevant safeguards when evaluating a workflow that may handle sensitive information. Elite documents these controls so an organization can review how its intended use would work.
HIPAA compliance requires more than those features. HHS explains that certification is not required by the Security Rule; the relevant question is whether the actual policies, procedures, contracts, and technical safeguards meet the applicable requirements.
HHS cloud guidance requires an appropriate Business Associate Agreement when a cloud provider creates, receives, maintains, or transmits electronic protected health information on behalf of a covered entity or business associate. Encryption alone does not remove that requirement.
A practical privacy check for your setup
Review the extension’s site access and use only the inbox connections you need.
Enable MFA where available and review connected devices and team roles.
Choose outgoing tracking and incoming tracker protection separately. Use untracked sending when tracking is inappropriate.
Set retention around a documented need, including a separate decision about network and location fields.
Keep document, video, and signature request links private; close access when the task is finished.
Use the verified privacy-request process for access or deletion requests, and contact Elite before a regulated or sensitive deployment.
You should be able to understand an extension before trusting it with your work. Start with the privacy policy, the security controls, and the permissions shown by your installed version. If something about your intended workflow is unclear, ask us about that specific data flow so you can make an informed decision.
Frequently asked questions
Does Elite upload my Gmail inbox to its servers?
Gmail browser tracking keeps mailbox subjects, addresses, identifiers, and message-to-tracker associations in account-scoped local browser storage. Independent tracking identifiers, eligible fresh link destinations, and resulting service events still reach Elite. Content you deliberately create or upload in cloud workflows is handled separately.
Can I use Elite without tracking every email?
Yes. Use the compose tracking control before sending, and review your account or team policy. Turning tracking off for a new message does not stop existing trackers. Stop an existing tracker separately, and use deletion controls when you also want its history removed.
Does disconnecting delete my data?
No. Disconnecting ends access through that connection; it does not automatically erase retained records or recall sent messages. Stopping tracking, deleting history, deleting account data, and revoking shared links are separate actions with different effects.
Does Elite provide GDPR controls?
Yes. Documented controls include strict recipient permission checks, retention settings, exports, deletion, and verified privacy requests. Review the DPA and subprocessors for your use. Both Elite and the customer retain their applicable responsibilities; enabling a setting does not establish compliance on its own.
Does the absence of HIPAA certification mean a service cannot comply?
No. HHS does not require Security Rule certification. Compliance depends on the actual safeguards, policies, procedures, and agreements for the specific use. This article does not establish a HIPAA compliance claim for Elite. Confirm the supported scope and required BAA before using protected health information.
Sources & further reading
Provider instructions and product details checked on November 12, 2026. Check the linked source for later changes.
- Chrome: permission warning guidelines
- Chrome: permissions and warning text
- Elite: privacy policy and retention
- Elite: documented security controls
- Elite: compliance settings and recipient rights
- Elite: Data Processing Addendum
- EDPB: controller and processor responsibilities
- HHS: Security Rule certification and evaluation
- HHS: HIPAA and cloud computing