Who we are
Jaylert Chat and Jaylert Test ("the apps") are developed by Jaylert, Hungary ("we"). Contact: [email protected].
Jaylert Chat: data the app processes
Jaylert Chat runs on Atlassian Forge. Personal messages (below) also use the Jaylert relay service. When an issue event matches a rule, it reads the issue data needed for the notification and sends it to the Google Chat webhook set by your Jira administrator:
- issue key, summary and issue type;
- the fields selected in the rule (status, assignee, priority, reporter, due date, labels, components, fix versions);
- the display name of the person who made the change;
- optionally, the first 300 characters of the description or of a new comment. Comments with restricted visibility and internal notes are never sent.
Apart from personal messages, we, the developer, have no access to this data and do not store it on our own systems.
Data Jaylert Chat stores
In Atlassian's Forge storage, within your Atlassian site:
- notification rules;
- Google Chat webhook URLs, encrypted;
- a delivery log (time, issue key, event type, rule name, result), kept for 30 days. It contains no issue content and no personal names;
- for daily digest rules only: a queue with the issue key, summary, type and the change of each matching update. People are stored only as Atlassian account IDs; their names are looked up from Jira when the digest is sent. The queue is deleted when the digest is sent and expires after 7 days at the latest.
Function logs (errors, issue keys, rule names) are kept by Atlassian under its platform retention rules.
Personal messages and the Jaylert for Jira Google Chat app
When your Jira administrator turns on personal messages and you connect your Google Chat account (in Jira: Settings (⚙) → General settings → Apps → Jaylert Chat), Jaylert sends you direct messages in Google Chat through the Jaylert relay service, run by us on Cloudflare with data stored in the European Union.
What the relay stores: the Atlassian site ID, your Atlassian account ID, your Google Chat user ID and the ID of your direct-message space with the app, the site address, and the time you connected. While you connect, a one-time code is stored only as a hash for up to 10 minutes; wrong code attempts are counted per Google user for an hour. We do not store your name, email address or any issue content.
What passes through: the message about the issue (the same fields as a Jaylert Chat card: issue key, summary, type, the change, who made it, status, assignee, priority and, for comments without restricted visibility, the first 300 characters of the comment). It is forwarded to Google Chat and not stored or logged by us.
Google user data: from Google Chat, the app receives your Google user ID, the direct-message space ID and the messages you send to the Jaylert app, which are used only to read a connect code or a command such as "disconnect". It does not read other Google Chat messages and does not access other Google data. We use this data only to deliver your Jira notifications, never for advertising, and do not share or sell it.
In your Atlassian site (Forge storage): the on/off switch, and for each person who connects, their message choices and connection dates, keyed by Atlassian account ID.
Deletion: the connection is deleted when you disconnect in Jira, send "disconnect" to the app or remove the app in Google Chat; when Google reports that your direct message no longer exists; when Jaylert Chat is uninstalled from the site; and when Atlassian reports that your account was closed (checked weekly).
Contact form and support email
When you write to us through the contact form or by email, we receive your name, email address, optional Jira site address and your message. We use them only to answer you, keep them in our support mailbox, and delete them within 24 months of the last message. The form is delivered through Cloudflare, which hosts this website.
Jaylert Test
Jaylert Test is in development and not yet available. This section describes how it will handle data. Jaylert Test runs on Atlassian Forge. It stores the test cases, folders, test cycles and results that your users create, the Jira issue keys they link, and the Atlassian account IDs of people who ran tests, in Atlassian's Forge database for your site. It reads Jira issues, runs JQL and creates bug issues only as the signed-in user. The CI upload token is stored only as a hash.
AI drafts send the summary and description of the chosen Jira issue to Atlassian-hosted models (Forge LLMs); nothing is sent to other AI providers or to us. The proposed drafts are kept in Forge storage for up to one day, so the person who asked can review them. Jaylert Test sends no data outside Atlassian. Data stays until your users delete it or the app is uninstalled.
Jaylert Test waitlist
If you join the list at jaylert.com/test, we receive your email address and, if you choose to tell us, your team size and current test tool. We use them only to email you once when Jaylert Test is available, keep them in our support mailbox, and delete them after that email or when you ask. Reply "remove" to any of our emails to leave the list.
Third parties
- Atlassian hosts and runs the app on Forge.
- Google receives the notifications in the Google Chat spaces you choose, under your own agreement with Google.
- Cloudflare hosts this website, counts visits with Cloudflare Web Analytics (which sets no cookies), delivers contact form messages to our mailbox and runs the Jaylert relay for personal messages (data stored in the EU).
- Google also receives personal messages in your direct message with the Jaylert app in Google Chat.
The app uses no other sub-processors. This website sets no analytics or advertising cookies and serves its fonts itself.
Retention and deletion
Rules stay until your administrator deletes them or uninstalls the app. The delivery log expires after 30 days, the digest queue after 7 days at the latest. Personal message connections stay until deleted as described above. Messages already posted to Google Chat are managed in Google Chat. In Jaylert Test, test cases, cycles and results stay until your users delete them or the app is uninstalled; proposed AI drafts that were not saved expire after one day.
Your rights
Under the GDPR you can ask for access to, correction of or deletion of personal data. Apart from personal message connections, the app keeps no personal data outside your Atlassian site, so your Jira administrator can handle most requests. To delete your personal message connection yourself, disconnect in Jira or send "disconnect" to the Jaylert app. For any privacy question, write to [email protected].
We publish changes to this policy on this page and update the date above.