← COMA

Privacy Policy

COMA — Worklog for Jira · Last updated: September 16, 2026

COMA helps you prepare and post Jira worklogs. This policy covers the Chrome extension, maintained by vshtykhnov.

Data COMA uses

• Jira: your site address, account ID and display name; issue details, statuses, assignment and status history; and worklog dates, durations and descriptions. COMA uses your existing signed-in Jira session. It does not ask for or store your Jira password.
• Google Calendar, if connected: your account identifier and email, calendar names and identifiers, and selected-calendar events, including titles, times and your attendance response. These are used to suggest meeting worklogs and remember your calendar selection. Calendar access is read-only.
• GitHub, if connected: your account identifier and username, pull request identifiers, titles and links, and submitted review details and dates. These are used to suggest code-review worklogs. COMA stores the access token you authorize or enter and, for GitHub App authorization, refresh tokens and expiry information. COMA does not modify your repositories or pull requests.
• Your entries and preferences: worklog drafts, posting results, working hours, task mappings, integration selections and other app settings.

Storage and transfers

Workspace data, settings and GitHub credentials are stored locally in your Chrome profile using extension storage. Temporary authorization and meeting-preparation data use session storage. Google authorization tokens are managed through Chrome's identity API. COMA does not provide cross-device synchronization or application-level encryption of local storage.

COMA requests data directly from your Jira site, Google and GitHub over HTTPS when you use their features. When you post worklogs, their dates, durations and descriptions are sent to your Jira site. Descriptions can include meeting titles or pull request titles and links. Suggestions remain local drafts until you post them. Editing or deleting an existing Jira worklog sends the corresponding update or deletion to Jira.

COMA has no application backend receiving your workspace data, and includes no analytics, advertising or browsing-history tracking. We do not sell your data, use it for advertising, or send it to AI services for model training. Connected providers process requests under their own policies and your organization's settings.

Google API data

COMA's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google data is used only for the meeting-worklog features you choose. The maintainer does not receive or read your calendar data through COMA.

Feedback

Feedback opens an optional external Tally form. Information you submit is shared with Tally and the COMA maintainer to handle your report, improve the app and reply if you provide contact details. COMA does not automatically attach account or workspace data. Only share information needed for your report; avoid passwords, tokens and confidential work data. Tally's handling of its service is described in its Privacy Policy.

Retention and your controls

Local workspace data remains until you clear the extension's storage or uninstall COMA. Disconnecting Jira does not erase saved workspaces. Disconnecting Google or GitHub removes the active local connection, but saved drafts, task mappings and calendar preferences may remain. Disconnecting is not the same as revoking provider authorization: you can revoke COMA in your Google or GitHub account settings, and revoke a personal access token in GitHub.

Clearing local data does not delete worklogs already posted to Jira or feedback submitted through Tally. Manage posted worklogs in Jira or through COMA's worklog controls. Feedback is retained for as long as needed to handle the report and follow-up; you can request access, correction or deletion through the contact below.

Contact and changes

For privacy questions or requests, contact the COMA maintainer through the feedback form and include a way to reply. Changes to this policy will appear on this page with an updated date.