Security and data handling for Wezy Customer Voting

Wezy is operated by LooksPretty. This page explains how customer voting data is handled in Jira Service Management and how to report a security concern.

Access to your requests

Wezy uses Atlassian authentication and checks Jira Service Management access before allowing voting or showing request information. Customers can vote only on open requests that are enrolled for voting and already accessible to them. Enrolling a request does not share it with additional people.

Project administration, agent views, exports and erasure require the relevant Jira permissions. Access is checked on the server. Voting information and configuration are held separately for each Forge installation.

Where your data is handled

Voting records, configuration and available analytical history are stored in Atlassian Forge SQL. The app runs on Atlassian Forge and does not automatically send voting records to external services.

Persistent Forge SQL storage uses Atlassian's supported data residency controls. Your Atlassian administrator can check the app's actual location and pinning status. Operational logs, temporary execution data and voluntary external support communications have separate scopes. A storage location does not mean that all of these use the same region.

Diagnostic logs may contain technical identifiers, such as a Jira project identifier. Exporting a diagnostic log creates a copy outside Atlassian. Diagnostic logs are separate from the customer voting exports available in the app.

Local diagnostic copies created for production support are deleted within 30 days after the issue is resolved. This retention period applies to those diagnostic copies; Atlassian-managed logs and customer-held exports follow their own retention controls.

Downloads and deletion

Wezy publishes numeric demand metrics to its Jira fields. These fields follow Jira permissions. Authorized users can download the exports available to their edition. Downloaded files remain under the recipient's control and should be protected and deleted when no longer required.

Authorized administrators can request erasure of Wezy request, organization or account data. Erasure restricts affected Wezy views while source records, derived copies and app fields are processed. It may require several maintenance runs. The Jira request itself is not deleted. Retention is explained in the JSM privacy notice.

Security reports and support

Report an app security concern to wesy@wezy.app. Include the affected product version, the approximate time, reproduction steps and redacted evidence. Never send passwords, API tokens or complete customer exports.

Email and Crisp support are external channels for information you choose to submit. The app does not automatically attach voting data or Jira context when opening support. Any investigation requiring additional personal data needs an agreed handling scope before transfer.