Privacy Policy

1. Who we are

Scritt Solutions, a sole proprietorship operated by Ryosuke Kamei and based in Tokorozawa, Saitama, Japan, develops and operates the App. Our detailed address is disclosed without delay on request. Contact us at support@scritt.com.

3. What the App stores

The App writes five kinds of record to Forge app storage, all scoped to your Atlassian site.

• Rule definitions. The rule name, the JQL you entered, the schedule, the action settings, the cooldown, and the Atlassian account ID of the administrator who created the rule. Kept until you delete the rule.
• Execution logs. For each run: a run identifier, the rule identifier and a copy of the rule name, start and finish times, counts of issues processed, and the Atlassian account ID whose permissions the run was checked against. When issues fail or are skipped, the log also records those issue keys with a short reason, up to 50 of each. Kept for 90 days, then deleted by a daily cleanup job.
• Idempotency records. A rule identifier and a time slot, written to stop the same scheduled run from executing twice. Kept for 7 days, then deleted by the same daily job.
• Cooldown records. Issue keys and the time the App last acted on them, so a rule does not act on the same issue again too soon. Entries older than the rule's cooldown window are removed as the rule runs.
• Cleanup results. The time of the last cleanup and how many records it removed. One record, overwritten each day.

4. What the App reads but does not store

To run a rule, the App reads from Jira: the issues your JQL matches, their assignee (account ID and display name), due date, last-updated time, project type, and available status transitions. It uses these in the moment and does not write them to its own storage. Assignee details appear in the comment it posts, in the same way a comment you write yourself would.

5. What the App writes to Jira

Only what your rule specifies: a comment, a priority or label change, or a status transition. The App posts as itself, not as a user, and appears in the issue history under the App's name.

Before acting, the App checks the permissions of the administrator who created the rule. If that person could not perform the action themselves, the App skips the issue.

6. Personal data

The Atlassian account IDs described above are personal data under GDPR and comparable laws. The App stores them to record who created a rule and whose permissions a run was checked against, which is what lets a site administrator audit the App's actions.

Atlassian acts as the data controller for your site's Jira data. We process the data listed above on your behalf as part of providing the App.

To access, correct, or delete this data: delete the rule (removes the rule definition) or wait for the retention period to elapse (removes the logs). To remove everything at once, uninstall the App. Atlassian deletes an app's storage after uninstallation. You can also reach us at support@scritt.com.

7. Jira Service Management

The App does not act on Jira Service Management issues. It detects them at run time and skips them, because comments on a service request can be visible to the customer who raised it. If the App cannot determine a project's type, it skips the issue rather than risk acting on one.

8. Children

The App is not directed at children and we do not knowingly collect data from them.

9. Changes to this policy

We will update this page when the App's data handling changes, and we will change the date at the top. Material changes will also appear in the App's Marketplace release notes.

10. Contact

Questions about this policy or your data: support@scritt.com