Privacy: Jira Projects.
Policy for the internal application Aura | Projetos: Acompanhamento, which connects execution in Jira to client follow-up in Jira Service Management.
This is an English translation provided for convenience. The Portuguese version is the official text and prevails in case of any discrepancy.
-
Application and controller
This policy describes the processing of data by the internal application Aura | Projetos: Acompanhamento, identified in Forge as 3471bcf5-06bb-4dec-a7ce-76f041aff5ac, in Aura Tech’s Jira environment. It covers the integration between internal AUP projects and AURA follow-up requests.
The party responsible for operating the application is WEAURA TECH LTDA., CNPJ 66.871.366/0001-44. For privacy matters, use privacidade@weaura.tech. For application support, use contato@weaura.tech.
This policy is limited to that application. It does not change the policies of other Aura applications or of clients. Responsibilities over data provided by clients also follow the contractual relationship and the instructions applicable to the provision of the service.
Browsing this public page is covered by the privacy policy of the institutional website, including the contact form and cookie preferences.
-
Data processed and purposes
The application queries existing information in Jira, Jira Service Management and Assets to verify permissions, identify the correct recipient and maintain a single follow-up for each project or delivery.
- Identity and authorization: Atlassian identifiers of operators, requesters, authors and participants; names and access status queried in Jira. They are used to identify who requests an action, verify authorization and confirm the permitted audience.
- Service context: references to Client, Contract, Account, JSM Organization, project, ticket, request type and links between tickets. They are used to check that the context is consistent and to route information to the correct follow-up.
- Authorized communication: titles, texts expressly intended for the client, results and evidence selected to create and update the follow-up in the portal.
- Progress and acceptance: public replies from the client, acceptance records, justifications and progress milestones. They are used to bring relevant information into the internal work and to record the authorized progress.
- Technical records: identifiers of commands and events, dates, hashes, links, execution states, receipts and error codes. They are used for reconciliation, duplicate prevention, controlled recovery and traceability.
Free text may contain personal data entered by users. Do not include passwords, tokens, personal documents or unnecessary sensitive data in titles, evidence and updates. The application does not need that information to work.
This application does not integrate with Tempo, does not read or copy time entries and does not create contractual balances or credits. It does not use advertising, marketing tracking or its own artificial intelligence features.
-
Source, storage and processing
The information comes from the Atlassian systems used by Aura and from the explicit actions of authorized users. The application’s processing and technical storage take place on the Atlassian Forge platform.
The KVS technical storage keeps commands, identifiers of people, texts included in commands or effects, links between items and technical receipts. Part of the information is also recorded in the Jira/JSM tickets and comments themselves. Technical error records use reduced projections of phase, operation and code, instead of copying the full content of the ticket.
The version described declares no external network destinations and does not send this data to a backend of its own outside the Atlassian platform. This configuration does not mean that Atlassian services are hosted exclusively in Brazil. Infrastructure conditions, subprocessors and any international processing follow the applicable Atlassian instruments.
-
Access and communication
Use of the application depends on an active identity, access to the application, an authorized group and native Jira permissions. The Client, Contract, Organization and recipient checks must pass before anything is published.
Public texts are those expressly intended for the client, in addition to the milestones provided for by the workflow. Internal technical discussions and attachments are not copied indiscriminately. Information published in JSM becomes visible to the audience permitted by the rules of the ticket and the portal, which may include the requester, participants and the corresponding organization.
Eligible public replies from the client may be reflected as internal information in the execution item. Automated validations check context, authorization and workflow state; they do not replace the client’s acceptance or authorize the disclosure of another client’s data.
Enabling features depends on the application’s operating configuration. Permissions declared in the manifest do not, by themselves, authorize the team to publish any content.
-
Retention and deletion
Technical records serve operation, reconciliation and traceability. The current version does not implement a fixed expiration period or an automatic deletion routine for KVS records. They may remain for more than 24 hours. Closing or deleting a ticket does not prove that the corresponding technical records were deleted.
The need for retention or deletion must be assessed administratively, considering the purpose, the applicable obligations and the integrity of reconciliation. A removal must also consider the source records in Jira/JSM and Atlassian’s storage and recovery conditions.
-
Privacy requests
Through privacidade@weaura.tech, the data subject may request information about the processing, confirmation of and access to their data, correction, information about sharing and, where applicable, anonymization, blocking, deletion, portability or objection. Review and handling will observe the applicable legal requirements and time limits, including possible retention duties.
When a request involves information under a client’s responsibility, Aura will coordinate the handling with the applicable controller. Identity confirmation may be required to avoid providing data to another person. Use of the application does not constitute generic consent for other purposes.
-
Updates and references
Material changes to purpose, data categories, recipients or retention require this policy to be updated. The published date and version identify the applicable document.
- Brazilian General Data Protection Law (Law No. 13,709/2018): information on processing and data subject rights (in Portuguese).
- Atlassian privacy policy.
- Security and responsibility on the Forge platform.