Skip to main content

Privacy Policy for Manager's Companion

Privacy Policy for Manager's Companion

Last Updated: 5 July 2026

At Manager's Companion, privacy is a core design principle rather than an afterthought. The extension is built to help Jira Cloud users generate daily management dashboards—including reports, team availability, on-call rosters, daily notes, and incident monitoring—without requiring any external servers or cloud services.

Unlike many browser extensions, Manager's Companion operates entirely within your browser. The developer does not operate a backend service, collect personal information, or receive copies of your data. Everything remains under your control on your own device.

Privacy at a Glance

Manager's Companion follows a simple approach:

  • Everything runs locally in your browser.

  • No developer-operated servers are involved.

  • Your Jira credentials and application data stay on your device.

  • The extension communicates only with your own Atlassian Jira Cloud instance to retrieve the information needed to display your dashboard.

  • No analytics, advertising, tracking, or third-party data sharing is performed.

What Information the Extension Stores

To provide its features, Manager's Companion stores several types of information locally on your device. None of this information is transmitted to the developer.

The extension stores:

  • Jira connection details, including your Jira base URL, account email address, and API token. These are securely stored in Chrome's private extension storage (chrome.storage.local) and are used solely to authenticate requests to your Jira instance.

  • Report configuration, including project selections, JQL queries, KPI targets, and threshold settings. These preferences are stored in browser local storage (localStorage, using dr.* keys) so your reports can be regenerated without repeated setup.

  • Team information, such as team members, leave schedules, holidays, on-call rosters, and related links. This data supports availability planning and reporting features.

  • Daily notes, allowing you to maintain stand-up, handover, or management notes directly within the extension.

  • Incident monitor settings, including JQL filters, SLA thresholds, favorites, and monitoring preferences.

  • Display preferences, such as visible widgets, custom labels, and dashboard personalization options.

  • Usage statistics, including local counts of reports generated, API requests made, notifications shown, and similar metrics. These statistics are displayed only within the extension's Usage tab and are never transmitted outside your device.

All of this information remains stored locally and is accessible only to the extension.

Network Communication

Manager's Companion makes network requests to only one destination: your own Atlassian Jira Cloud site (https://*.atlassian.net).

These requests are made directly from your browser and:

  • authenticate using the Jira API token you provide;

  • retrieve issues, fields, and incident information required to build your dashboard;

  • process all returned data locally within your browser.

The developer never receives copies of your Jira data, credentials, reports, or usage information.

Your interaction with Jira itself is governed by Atlassian's own Privacy Policy.

Browser Permissions

Manager's Companion requests only the permissions necessary to provide its features.

  • Storage is used to save your settings and locally stored data.

  • Notifications allow the extension to display desktop alerts for new incidents or SLA breaches.

  • Context Menus adds a convenient "Getting Started Guide" option when right-clicking the extension icon.

  • Host access to https://*.atlassian.net/* allows the extension to communicate directly with the Jira Cloud REST API without requiring any intermediary servers.

No additional permissions are requested for tracking, advertising, or unrelated purposes.

Data Security

Your information is stored using Chrome's built-in extension storage mechanisms, which are isolated from ordinary websites and inaccessible to web pages.

Because Manager's Companion is entirely serverless, your Jira API token must be stored locally in the extension's private storage. This token is stored unencrypted on your device so the extension can authenticate future requests without repeatedly prompting you.

For this reason, you should install and use the extension only on devices that you own or trust. If necessary, you can revoke your Jira API token at any time through your Atlassian account security settings.

Exporting and Importing Data

Manager's Companion allows you to export your locally stored application data to a JSON file for backup purposes.

Your Jira connection details and credentials are intentionally excluded from exports to help protect your account.

Any exported files are created, stored, and managed entirely by you on your own device. The developer never receives or stores these files.

Data Retention

Your data remains on your device until you choose to remove it.

You can:

  • clear specific application data from within the extension;

  • reset locally stored usage statistics;

  • remove extension data using your browser's storage controls; or

  • uninstall the extension, which removes its stored data.

Since Manager's Companion does not use any servers, the developer does not possess copies of your information and therefore cannot delete data on your behalf.

Third-Party Services

Manager's Companion does not include:

  • analytics platforms;

  • advertising services;

  • tracking technologies;

  • external databases; or

  • third-party data processing services.

The only external system contacted by the extension is your own Atlassian Jira Cloud instance, and only at your request.

Children's Privacy

Manager's Companion is designed as a workplace productivity tool and is not intended for use by children.

Chrome Web Store Compliance

Manager's Companion is designed to comply with the Chrome Web Store's Limited Use requirements.

Specifically, the extension:

  • does not sell user data;

  • does not transfer user data to third parties;

  • does not collect information for advertising purposes;

  • does not use user data for purposes unrelated to the extension's functionality; and

  • accesses only the information required to display your Jira data and provide the features you choose to use.

Changes to This Privacy Policy

This Privacy Policy may be updated from time to time to reflect improvements or regulatory changes. Whenever updates are made, the Last Updated date at the top of this document will be revised, and the latest version will be published in the same location.

Contact

If you have any questions about this Privacy Policy or how Manager's Companion handles your data, please contact:

rajnikantroyy@gmail.com

This version is more narrative and website-friendly while retaining the legal and Chrome Web Store compliance details from the original policy.

https://chromewebstore.google.com/detail/managers-companion/noielgdhlkohbbgghaolikioghpecfag?authuser=0&hl=en

Comments

Popular posts from this blog

Manager's Companion — Zero Cost, Immediate Payback

  The problem it solves Every engineering lead spends time each morning doing the same manual work: chasing Jira for what's open, figuring out who's actually available (leaves, holidays, on-call), checking for new incidents, and then hand-assembling all of it into a status update for their own manager. It's repetitive, error-prone, and it pulls senior people away from actually leading. Manager's Companion turns that 30–45 minute daily scramble into a two-minute, one-click report. What each lead is equipped with Instead of juggling five browser tabs and a spreadsheet, every lead gets one dashboard : Instead of… They now have… Manually querying Jira and copying numbers A live daily report generated in one click Guessing who's off or on-call An accurate, real-time availability & on-call view Finding out about incidents late An automatic incident monitor with instant desktop alerts Screenshotting messy dashboards for email A clean, presentation-ready report they can...

I got tired of spending an hour every morning rebuilding the same Jira report — so I built this.

  Every single day, no matter what was going on, that report had to go out. Hypercare? It still had to go out. Deployment day with a hundred things on fire? Still had to go out. Slammed with back-to-back meetings, or sitting in an airport with a laptop on my knees while travelling? It still had to go out. Because that daily report isn't optional. It's how the team stays aligned, how stakeholders stay informed, and — let's be honest — how you keep a small issue from turning into an escalation. Skip a day and the questions start. Miss a signal and you're explaining it after the fact. So I was spending 45–60 minutes every morning doing the same thing: running the same JQL queries, tallying the same KPIs, checking who's on leave, noting on-call, formatting it into something readable, and pasting it into email. Rinse and repeat. On my best days it was tedious. On my worst days it was the last thing I had capacity for — and those were exactly the days it mattered most. ...