Privacy Policy

What we collect

• Jira authorization. When you connect Jira, Atlassian gives us OAuth access and refresh tokens. We request scopes to read your Jira work and user profile, to write only the changes you start (see below), to register a webhook for your own assigned items, and offline_access so the connection can refresh.
• Your Atlassian profile. Account id, display name, and email — to identify your account and show who is signed in.
• App-only content you create. Notes, configuration, and files you attach inside Jeedle. This stays in Jeedle; it is never written into Jira.
• Board cache from Jira. Descriptions, comments, and full history are read on demand and not kept as a permanent copy. To keep the board fast, we cache lightweight fields for work items on your Jira site — summary, status, assignee, priority, and assignment history used for columns like Shipped. That cache is keyed by Jira site and may be shared with other Jeedle users on the same site. We only show you items your Jira permissions already allow.
• Optional GitHub connection. If you connect GitHub, we store encrypted GitHub App tokens and basic profile fields (user id, login, name, avatar). Pull requests and commits for a ticket are fetched on demand and not stored as a lasting copy.

Your code stays on your machine

The Code view reads git from a folder you choose in the browser via the File System Access API. Source, commits, and diffs stay on your device— they are never uploaded to Jeedle servers. We may remember only the folder handle you picked (locally). We can't see your code; we only ever act on Jira (and optional GitHub) through the APIs you authorize.

Changes we make in Jira

Jeedle writes to Jira only when you ask, and only these changes:

• moving a work item's status, and setting its assignee;
• posting, editing, or deleting your own comment;
• editing a work item's title or description;
• setting labels, and linking one work item to another;
• logging work;
• creating a new work item;
• attaching a file or image you add to a comment or description. Those become real Jira attachments — anyone who can see the work item can see them. Files on private notes never leave Jeedle.

It never edits Jira on its own.

Attachments

• Private note fileslive in a private storage bucket, readable only by your Jeedle account (max 15 MB; common document and image types).
• Jira attachments are fetched through Jeedle with your OAuth token and streamed to you. Jira still enforces who may see them. We do not keep a lasting copy of those bytes.

The AI Companion

When you ask the Companion a question, or draft a standup or timesheet, we send what that request needs — relevant work item details and related private notes — to a third-party AI provider. Only when you use the Companion; if you never open it, nothing is sent. Conversations are not stored as a lasting record on our servers.

By default that provider is Groq. Under their terms, prompts sent through the API are not used to train their models. We don't use Companion conversations for advertising or our own model training.

How we store and protect it

• Data is stored in managed PostgreSQL (Supabase). Jira and GitHub tokens are encrypted at rest with AES-256-GCM — never plain text, never sent to your browser.
• Your session is an httpOnly, signed cookie that holds a connection id only — not the OAuth tokens.
• Webhook delivery payloads may be queued briefly (on the order of a day after processing) so we can apply board updates reliably.
• Your private notes, config, and uploads are tied to your connection. Board cache and some pipeline state are keyed by Jira site so teammates on the same site can share a consistent board view.

How we use it

Only to run the product: show your Jira work, make the changes you ask for, save notes and config, optional GitHub context, and Companion answers. We do not sell your data or use it for advertising.

Service providers

Atlassian (Jira), optional GitHub, Supabase (database & file storage), Vercel (hosting), and an AI provider (Groq by default). Data is processed by them only to run Jeedle.

Disconnecting & deletion

Disconnect in the app revokes our stored Jira tokens and webhook so we cannot call Jira for you anymore. Your private notes, config, and uploads are kept so you can reconnect later. Board cache for the site is not wiped on disconnect.

To delete your account and associated notes, config, and files, email privacy@jeedle.com. Closed Atlassian accounts may also be erased through Atlassian's personal data reporting process.

Contact

Privacy questions: privacy@jeedle.com.