Privacy policy
Publisher: Mikhail Ozashvili, sole proprietorship registered in the Polish business register (CEIDG) under tax number NIP 5842861679, trading as DobraMara and operating the Stayposted brand ("we", "the publisher"). Privacy contact: privacy@dobramara.com. Effective date: 18 November 2026.
Purpose and information used
Stayposted provides Jira/Jira Service Management notifications in Telegram. It processes issue identifiers, links, summaries, status, priority, type, assignment information, names of relevant users, selected changes and comment content needed for a notification. It also uses Jira account identifiers, Telegram chat/user/topic identifiers, chat titles, subscription preferences and delivery metadata. The administrator provides a Telegram bot token, stored using Forge’s secret-storage API.
We use this information to connect the installation, apply rules and access checks, deliver and update messages, suppress duplicate notifications, investigate delivery failures and process account-data requests. This release does not include advertising, third-party analytics or AI processing of issue content.
Where information goes
Application code and app-managed storage run on Atlassian Forge. Selected notification content and the necessary chat identifiers are sent to the Telegram Bot API at api.telegram.org, using the bot connected by the administrator. Telegram is a separate service with its own terms and privacy practices. The application also sends account IDs and retrieval dates to Atlassian’s personal-data reporting API to process account changes and closures.
Stayposted therefore does not keep all data inside Atlassian. Telegram messages are available to members of the destination chat. Jira access checks do not control Telegram membership. Telegram bot messages are not Telegram Secret Chats.
Storage periods and deletion
TTL values below are configured expiry periods, not promises of physical deletion at an exact instant. Forge removes expired records asynchronously (potentially up to 48 hours later); reads may still return expired records. App code validates expiry for linking codes and uses an explicit logical lease for coordination. Platform copies, queues and logs have separate retention.
| Data in app-managed Forge storage | Implemented retention |
|---|---|
| Pending normalized events, including compacted comment text | Two-hour TTL; normally removed after delivery planning |
| Connect codes and personal linking tokens | Ten-minute TTL; normally removed on use |
| Cached Jira display names | 24-hour TTL |
| Cached Jira administrator check | Ten-minute TTL, used for at most five minutes |
| Deduplication and assignment replay markers | Seven-day TTL |
| Rule preview counters | Three-day TTL |
| Individual delivery-log entries | Seven-day TTL; UI displays the latest 40 from the latest 100 entries |
| Bot configuration, rules, connected destinations, account links and card/message references | Retained while configured; relevant account records can be erased from the personal page or through account-change processing |
| Privacy reporting schedule/action metadata | Reporting schedule follows the API cycle; failed erasure work is retained until processed |
Forge-managed asynchronous queue payloads, platform logs and backups follow Atlassian’s platform retention and are not directly erased by the app’s personal-data button. Only the publisher has access to the app's platform logs. When the app is uninstalled, its app-managed storage is handled under Atlassian's Forge data lifecycle: it is soft-deleted and can be relinked to a new installation only on request within 21 days. We do not promise immediate deletion from every platform copy.
Users can unsubscribe or delete their app-managed account data on Apps → Stayposted. Deletion also cancels the personal link. A successful cancellation or deletion serializes with the final delivery step: a still-running final delivery section prevents that operation from reporting success until the section ends. This orders application requests; a request already issued to Telegram with an unknown outcome can still appear later, including after a crashed invocation. During contention the app asks the user to retry; an unfinished erasure action remains queued for retry. Completed deletion prevents an earlier name/admin lookup from recreating its cache. Messages accepted by Telegram before cancellation cannot be recalled. The app periodically reports stored account information to Atlassian; accounts returned as closed or requiring refresh have their associated app-managed account records erased. A user whose account changed may subscribe again. Pending work, caches and delivery metadata associated with that account are included in cleanup where the app can identify the account.
Messages already sent to Telegram remain there. The app does not recall messages when Jira permissions change, erase forwards/screenshots, or control Telegram’s retention. Contact the relevant chat administrator for message-history management.
Customer controls and requests
The installing organization chooses which projects, events and destinations to connect and should establish the appropriate basis for disclosing data to Telegram. Internal JSM comments, role/group-restricted comments and issues with an issue-security level are excluded from group delivery. Personal delivery checks the recipient’s current Jira access.
Contact privacy@dobramara.com for access, correction, deletion and other privacy requests. We reply within one month of receiving a request; for complex or numerous requests this period may be extended by two further months, and we will tell you why (GDPR Article 12(3)). To protect your data, we may ask you to confirm the request from the email address or Atlassian account it concerns.
Roles. For Jira content and user information that Stayposted processes to deliver notifications, the organization that installs the app is the controller and the publisher processes that data on its behalf. Atlassian provides the Forge platform that hosts the app and its storage under Atlassian's own terms. Telegram is an independent service that the organization chooses as the destination for notifications; data delivered there is handled under Telegram's terms and privacy policy.
International transfers. App code and app-managed storage run on Atlassian Forge, covered by Atlassian's terms for the platform. Notification content is sent to Telegram at the organization's instruction. Telegram states that data of users from the EEA and the UK is stored in data centers in the Netherlands, while Telegram's controller entity is located outside the EEA.
You have the right to lodge a complaint with a data protection supervisory authority. In Poland this is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, ul. Stawki 2, 00-193 Warszawa).
Changes. We publish updates to this notice on this page and change the effective date above.
Stayposted