Privacy notice
Follow-up Steward stores the reminder information needed to bring you back to a Jira issue and records what happened to each scheduled notification. Last updated 14 September 2026.
Who is responsible
Mikhail Eshchenko, operating as Misheno, provides Follow-up Steward. Contact support@misheno.com for privacy requests. Your organization controls its Jira content, user access and instructions to the app. The data processing addendum covers processing on your organization’s behalf.
What the app reads and stores
| Category | Purpose and handling |
|---|---|
| Jira issue data | Reads issue ID, current key and summary, project, status category, assignee and access information to show and send an authorized reminder. It does not copy issue descriptions, comments or attachments. |
| Reminder content | Stores your plain-text note, up to 1,000 characters, selected recipients, owner, schedule, time zone and optional end date. Notes may contain personal or confidential information you enter. |
| Personal controls | Stores snooze dates, opt-out choices, current-assignee bindings and changes needed to apply your preferences. |
| Technical history | Stores scheduled times, processing and acceptance times, recipient outcomes, reasons and audit events. It does not retain a separate copy of each email body or previous note text. |
| Account and policy information | Stores account IDs, ownership and membership references, privacy-reporting dates, project settings and license state needed for authorization and maintenance. |
The app does not need to store recipient email addresses or user API tokens. Issue summaries used in emails are read at sending time rather than archived in reminder history.
Who receives the information
Self-only reminders are private. Team participants and authorized project administrators can see team reminder information only with current issue access. Administrator status alone does not expose private reminders.
Atlassian Forge supplies compute, storage, identity and platform diagnostics. Jira sends the due email to selected eligible internal recipients. The email contains the note and an authenticated link, and Jira adds the issue key and summary. Mailbox providers process the email under the recipient’s arrangements.
Access is checked before Jira submission. Revoking access or deleting a reminder afterward cannot remove an email already accepted by Jira or stored in a mailbox.
Retention and deletion
| Data | Retention and controls |
|---|---|
| Reminder settings and note | Kept while the regular schedule is active or a valid personal return is pending. A completed one-time reminder with a personal return six months away keeps its settings until that return is resolved. |
| Completed or stopped reminder | Kept for 90 days after its schedule has ended and the last valid personal return has been sent, missed or cancelled. A new permitted personal return before deletion restarts that period when it ends. |
| Reminder history and audit events | A rolling 90 days from each event, including while the reminder remains active. Old event history is not kept for the life of a long-running schedule. |
| Inactive subscription | App definitions are cleared after 90 days of confirmed license inactivity. This takes priority over a future personal return. Physical cleanup depends on the platform continuing to run maintenance. |
| Explicit deletion or confirmed issue deletion | Stops new sending work and clears the affected content. Minimal technical records prevent late background work from recreating deleted data. Email already accepted by Jira cannot be recalled. |
| Uninstall and platform copies | Atlassian applies its hosted-storage retention and recovery process. Uninstall is not a promise of immediate removal from platform backups. Reinstallation does not automatically resume old reminders. |
Owners can delete their reminders. Recipients can stop receiving and remove their personal return. These controls remain available when the app license is inactive. Deletion and erasure do not change the Jira issue or recall email.
Logical expiry prevents app access and new sending work before physical cleanup completes. Atlassian’s platform copies follow its hosted-storage lifecycle. The app does not promise a fixed 28-day uninstall deletion period.
Other services and support
Persistent reminder data stays in Forge hosted storage; Security explains the residency scope and email boundary. The app has no configured external analytics or advertising integration.
The Misheno website is hosted by Hetzner. Information you voluntarily send to the Google-hosted support mailbox is separate from app data and is covered by website privacy. Send only the details needed to resolve the issue, with notes, names and issue content removed.
Privacy requests
To erase your own data, open My reminders from Apps in Jira and choose Erase my data. Reminders you own are removed. You are removed from other reminders, together with your personal returns and history entries, and the notes of those reminders are deleted. The page shows when erasure has finished. Email already accepted by Jira cannot be recalled. A Jira administrator can remove all reminder data on the site with Remove all reminder data on the app’s admin page; site and project settings stay.
For other requests, email support@misheno.com with the product name, installation and request, without passwords or tokens. We verify the request before acting.
For Jira source content or emails held by your organization, also contact its administrator. The app cannot erase content held independently in those systems.