Privacy Policy

1. Who we are

Shurivo is a product brand operated by Sajjad Alizadeh, an independent developer. References to “Shurivo,” “we,” “us,” or “our” in this Policy refer to Sajjad Alizadeh operating the Shurivo brand.

2. Scope

This Policy applies to Shurivo for Jira Service Management (the “App”) and to privacy-related communications sent to Shurivo. The App is built on Atlassian Forge and is intended for use with Jira Service Management.

3. Information the App accesses

To provide request-editing and related controls, the App may access:

• Jira/Jira Service Management request and field values;
• requester identity information such as Atlassian account ID and display name where required for authorization or auditing;
• request participants where the configured editing policy permits requester-or-participant editing;
• project, request type, status, field metadata, and Jira permission information; and
• project-level App configuration.

4. How information is used

The App uses this information only as needed to provide configured request-editing functionality, apply authorization and policy checks, write approved changes to Jira, and create audit information inside Jira.

Audit information stored inside Jira may include the request key, requester/editor identity, timestamp, changed field names, and before/after values.

5. Storage and data location

Request content and request before/after values are not stored in Forge Key-Value Store (KVS). Project-level configuration is stored in Atlassian Forge hosted storage and may include project identifiers, enabled state, editable field IDs, status rules, actor rules, update time, and the identity of the configuration editor.

The App does not use Forge Remote, a Shurivo-operated runtime server, or an external customer-data database. App runtime processing and hosted App configuration remain within Atlassian-provided infrastructure.

6. Logging and analytics

The App does not intentionally log customer request content, Atlassian account IDs, or request before/after values. Operational logs are limited to information needed to operate and troubleshoot the App.

The App does not use third-party analytics or telemetry SDKs for customer Jira/Jira Service Management data.

7. Sharing and third parties

Shurivo does not send App runtime End-User Data to non-Atlassian third-party services. The App has no external runtime backend and no external customer-data database.

If you contact Shurivo by email, normal email metadata and message content may be processed by the email infrastructure used to receive and send that correspondence. This email handling is separate from the App runtime data flow.

8. Retention and deletion

Jira request data and audit information written to Jira are retained according to the customer’s Jira/Atlassian configuration and applicable Atlassian terms. Forge-hosted App configuration follows Atlassian’s Forge hosted-storage lifecycle. Atlassian currently documents a 28-day hosted-storage retention period after App uninstallation, subject to Atlassian’s platform policies and updates.

9. Privacy requests

Customers and users may contact [email protected] about privacy questions or requests. Where a request concerns data controlled by the customer inside Jira, Shurivo may direct the requester to the relevant customer administrator or assist the customer as appropriate.

10. Security

Shurivo uses the security controls provided by Atlassian Forge together with App-level authorization and policy checks. More information is available on the Security page.

11. Certifications

Shurivo does not claim an independent SOC 2, ISO 27001, FedRAMP, or HIPAA certification for this App.

12. Changes to this Policy

We may update this Policy when the App, applicable requirements, or our privacy practices change. The “Last updated” date above identifies the current version.

13. Contact

Privacy inquiries: [email protected]
General inquiries: [email protected]