Privacy Policy for Eagle View

This Privacy Policy describes how PearlFox ("we", "our", or "us"), a technology company based in India, handles information in connection with the Eagle View desktop application ("Application", "Service").

Eagle View is a productivity widget that connects to your Microsoft Outlook or Google Gmail account to display a real-time summary of emails, calendar meetings, flagged tasks and, where your Microsoft work account allows it, Microsoft Teams chats — all processed locally on your device. You may optionally also connect Jira, Azure DevOps, and/or Slack for the same kind of at-a-glance summary of those accounts; each is entirely opt-in and none is contacted unless you explicitly connect it.

We aim to follow the EU General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), India's Digital Personal Data Protection Act 2023 (DPDP Act), and internationally recognised privacy principles including OECD Privacy Guidelines and ISO/IEC 29101. Compliance work on these is in progress; Eagle View has not yet been independently audited or certified against any of them, and does not currently hold ISO/IEC 27001 or SOC 2 certification.

Eagle View requests the permissions listed below from your connected accounts. Most access is read-only, used to display your mail, calendar, and tasks. A small number of write actions are also available — see below — and every one of them only happens when you directly trigger it (e.g. clicking a button in the app); Eagle View never performs any of them automatically or in the background.

Write actions you can trigger

These actions are available directly from Eagle View's interface. Each one is performed on your connected account only when you click the corresponding button — never automatically, never in the background, and never without you initiating it:

• Mark as read — marks a message as read on your account (Outlook/Gmail)
• Flag / unflag (star) — flags or unflags a message for follow-up (Outlook/Gmail)
• Delete — deletes a specific message from your account (Outlook/Gmail)
• Complete — marks a flagged/to-do item as done (Outlook/Gmail)
• Transition — changes a Jira issue's status (e.g. To Do → In Progress), if you connect Jira
• Update state — changes an Azure DevOps work item's state, if you connect Azure DevOps
• Mark chat as read — marks a Microsoft Teams chat as read on your account. The extra Teams permission this needs is requested only at that moment

Eagle View can read, mark as read, flag and delete mail. It does not send, reply to, forward or draft mail.

Permissions requested from your accounts

These are the exact permissions (OAuth scopes) in the current version of Eagle View. Several are requested only when you use the related feature.

Azure DevOps is connected with your existing Microsoft sign-in.

Jira (optional)

There are two ways to connect. (1) With your Jira site address, your Atlassian email and an API token you create yourself: this goes directly from your computer to Atlassian. (2) With “Sign in with Atlassian” in your web browser. For (2), the one-time code and later the refresh token pass through a PearlFox server function, because Atlassian requires an app secret that cannot be stored safely inside a desktop app. The function only forwards the request to Atlassian and returns the answer. PearlFox does not store these tokens or read your Jira issues. The tokens are kept on your computer in the operating system’s secure storage.

ServiceNow (Incidents), Learn4U and Peakon rows

These look in your mailbox for mails from a sender address that you save in Settings and whose subject matches the pattern for that row. ServiceNow and Learn4U also check that the mail is addressed to you; Peakon does not. For ServiceNow and Learn4U, the body is read only for the newest mail of each incident or training number, and these lists and bodies are kept in memory only. For Peakon, the app stores on your device a web link to the survey mail, the times it found and answered the survey, and whether you dismissed it. The sender address, subject text and similar settings you enter are also stored on your device.

ServiceNow (optional)

If you connect ServiceNow, Eagle View shows your open incidents. There are two ways: by mail (Eagle View reads your own incident notification mails, as described under ServiceNow (Incidents), Learn4U and Peakon rows above) or by signing in to your organisation’s ServiceNow in your web browser. With the browser sign-in, your password is typed only in your browser and is never seen by Eagle View. The long-lived sign-in token is kept in your operating system’s secure storage and the short-lived token in memory only. Signing out in Settings deletes the saved token.

Clipboard

Some Settings boxes have a paste button. Eagle View reads your clipboard only at the moment you press that button, and puts the first line of it into the box you are filling. It does not read the clipboard at any other time, does not write it to the log, and does not send it to PearlFox.

Coming in a future version

Not in the version you can download today. The following are in development. We list them now so that you know what a future update will do before you install it:

• Google Chat (read-only). Shows your recent Google Chat conversations: names of spaces and people, a short preview (up to 80 characters) of the latest message and whether you have read it. It never writes to Google Chat. It adds four read-only Google permissions to the Gmail sign-in: chat.spaces.readonly, chat.messages.readonly, chat.memberships.readonly and chat.users.readstate.readonly. Content is kept in memory only.
• Time Sheet reminder. A reminder day that you choose in Settings, stored in the local settings file. The reminder runs entirely on your device.

We process your data solely to provide the features of Eagle View. The legal bases for processing under GDPR Article 6 are:

We do not use your data for advertising, analytics, profiling, machine learning training, or any purpose beyond delivering the functionality you explicitly requested.

We do not sell your personal data. We do not share your personal data with any third party except as described in Section 5 (Third-Party Services).

The email, calendar, chat and task content that Eagle View handles stays on your local device (licensing details are held on our licensing server, see Section 5). The following files are created on your device during normal operation:

Diagnostic log and Log Viewer

• The log records technical events (for example "refresh finished", "sign-in cancelled", an error code) so problems can be diagnosed. It is written to avoid personal data. Email addresses and full web addresses are removed from every line automatically, and your operating-system user name in file paths is replaced with <user>. The app is not written to log meeting titles, message text, or Jira / Azure DevOps / Slack names and ids. Sign-in tokens are not written to it.
• Eagle View does not upload or email the log. It stays on your device unless you choose to send it. The Log Viewer (Settings, or Debug Logs on the sign-in screen) opens it in your browser and has two buttons, Download as TXT and Download as HTML, so you can save a copy and send it to PearlFox support yourself.
• The Log Viewer page shows your license email address, and the downloaded file's name contains it (or your operating-system user name if there is none), the app version and the date, for example EagleView_Log_v1.1.7_you@example.com_2026-10-12_15-38-27.txt. Check the name before you share it publicly.
• Old lines are removed automatically: entries older than 5 days are deleted each time Eagle View starts and each time the Log Viewer is opened. Factory Reset erases the log and any saved viewer pages.
• Log files written by older builds of Eagle View (before the October 12, 2026 update) may still contain data that newer builds no longer write, until those lines age out after 5 days or you use Factory Reset.

Security Measures

• Version 1.1.8 and later: on macOS, the sign-in tokens for Microsoft (Outlook, Teams and Azure DevOps), Gmail, Jira (when you use “Sign in with Atlassian”) and ServiceNow, and the key that protects the other saved settings, are kept in your Keychain. On Windows they are meant to be kept in Credential Manager (we have not yet been able to test the Windows version on a real PC). A Jira API token and a Slack token are encrypted with AES-256-GCM before being written to disk, and the key is held in the Keychain or Credential Manager. Azure DevOps stores no secret of its own. For ServiceNow, your organisation's ServiceNow address and the Client ID are saved as plain text in the local settings file; they are not secrets. Version 1.1.7 kept the Outlook, Jira, Azure DevOps and Slack tokens in the encrypted settings file. Versions before 1.1.7 kept them in the settings file without encryption. For Jira this is your site address, email and API token; you can revoke the API token at any time in your Atlassian account.
• All API communication uses TLS 1.2 or higher (HTTPS only)
• The Application requests only the permissions listed in Section 2, and requests the Teams permissions only when you use the related feature
• No telemetry, crash reporting, or usage analytics data is transmitted from the Application. The Application does make a few background requests, listed under "Other services" in Section 5; like any web request, they reveal your IP address to those servers

Eagle View integrates with the following third-party platforms at your direction. Your use of these platforms is governed by their respective privacy policies:

Licensing & Payment Services

Other services

These services receive no account, mail, calendar or task data from you. Like any web request, each one can see your IP address.

PearlFox is not responsible for the privacy practices of Microsoft, Google, Atlassian, Slack, or the other services listed above. Eagle View's use of data obtained from these APIs is limited to displaying information within the Application and is not used for any secondary purposes. Jira, Azure DevOps, and Slack are all optional integrations — none of them are contacted unless you explicitly connect them.

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

PearlFox's servers do not receive your email, calendar, chat or task content. They do hold the licensing records described below. Retention periods:

For email, calendar, chat and task content: PearlFox retains no copies on our servers. For licensing records: these are retained on our licensing server for the periods above and deleted upon request, except the event history described above and where the law requires us to keep them.

Depending on your jurisdiction, you have the following rights regarding your personal data. Because Eagle View does not send your email, calendar, chat or task content to our servers, most rights over that content can be exercised directly by you within the Application or your operating system. For the licensing records we hold (Sections 2 and 6), contact us at dev@pearlfox.io.

Rights under GDPR GDPR

Rights under CCPA/CPRA CCPA

Rights under DPDP Act 2023 India

To exercise any right that requires our involvement, contact us at dev@pearlfox.io. We will respond within 30 days (GDPR: 1 month; DPDP: as prescribed by the Board).

Eagle View is a professional productivity tool intended for use by individuals aged 18 years and older. We do not knowingly process personal data of children under the age of 13 (or the applicable age of digital consent in your jurisdiction).

If you believe a child has provided personal information in connection with Eagle View, please contact us at dev@pearlfox.io and we will take appropriate steps to address the matter.

PearlFox is headquartered in India. Eagle View processes your email, calendar, chat and task content locally on your device and does not send it to our servers. The licensing details described in Sections 2 and 5 are stored by our licensing provider, Supabase, in Tokyo, Japan. Our other providers (Razorpay, Resend, Zoho and GitHub) process data in their own locations, which may be in other countries.

When Eagle View connects to Microsoft or Google APIs on your behalf, your data may be processed on servers operated by these providers in various countries. These transfers are governed by Microsoft's and Google's respective data transfer mechanisms (including Standard Contractual Clauses under GDPR).

For enterprise deployments subject to data residency requirements, please ensure your Microsoft or Google tenant is configured with the appropriate regional data boundary settings before deploying Eagle View.

We may update this Privacy Policy from time to time to reflect changes in our practices, legal requirements, or the features of Eagle View. When we make material changes, we will:

• Update the "Effective Date" at the top of this document
• Post the updated Policy at eagleview.pearlfox.io/privacy.html

Your continued use of Eagle View after the effective date of a revised Policy constitutes your acceptance of the changes. If you do not agree with the changes, you should discontinue use of the Application.

Business address: PearlFox, India
Privacy contact: dev@pearlfox.io
Grievance contact (DPDP Act / IT Act): dev@pearlfox.io
EU Representative: To be appointed upon EU market entry
UK Representative: To be appointed upon UK market entry