Privacy policy
Last updated: October 3, 2026
In short: the app runs entirely on Atlassian Forge. SagoSoft runs no servers or databases for it and does not use analytics or tracking. The app stores its settings in your site's Forge storage (webhook links encrypted) and sends issue updates only to the Google Chat spaces that your administrators or users choose. We never sell personal data.
1. Who we are
- Responsible party
- Luis Ángel Sánchez Gómez, an individual entrepreneur (persona física) doing business as SagoSoft
- Address
- Calle Cuenca del Conchos 6831, Fraccionamiento Antiguo Lienzo Charro, C.P. 31375, Chihuahua, Chihuahua, Mexico
- support@sagosoft.com
- Website
- sagosoft.com
This policy covers the Jira Cloud app “Sago Alerts for Jira and Google Chat™” (the “App”), this website, support by email, and the data we receive from Atlassian as a Marketplace partner. It is also our privacy notice (aviso de privacidad) under Mexico's Federal Law on the Protection of Personal Data Held by Private Parties (LFPDPPP).
2. Our role
- Data inside your Jira site (issues, comments, people's names and account IDs) belongs to your organization, which is the controller. When the App processes it, it does so on your organization's behalf and following its configuration, so we act as a processor (encargado). The processing takes place on Atlassian's infrastructure; we don't receive a copy.
- Support emails, Marketplace licensing data and this website's server logs: we are the controller (responsable).
3. Data the App processes
3.1 Stored in Forge storage (Atlassian)
| Data | Details |
|---|---|
| Space settings (set by Jira administrators) | Name, projects, JQL filter, events, status filter, style, threads, language, daily summary hour, time zone, days and date of the last summary. A JQL filter may mention people if an administrator writes it that way. |
| Webhook links | Google Chat webhook URLs of each space, stored as encrypted secrets and never shown in full again. |
| Personal subscriptions | The user's Atlassian account ID, chosen reasons, options (ignore own changes, style, threads, language), on/off and the date of the last change; plus the user's own webhook link, stored as an encrypted secret. |
| Site address | Your Jira site URL, cached for one day to build links. |
3.2 Read from Jira when an update happens (not stored)
Issue key and ID, summary, status, assignee, reporter, priority, issue type and project; the fields that changed with their old and new values; the comment text and whether it is restricted; account IDs and display names of the people involved (who made the change, assignee, mentioned people); for personal subscriptions, the account IDs of watchers and the result of Jira's permission check. This data is used in memory during the few seconds the App needs to build the message, and then discarded.
3.3 Sent to Google Chat
Only to the spaces configured by your administrators (or by each user for personal notifications), the App sends a message that may contain: issue key and summary, project name, status, assignee, priority, the changed fields and their new values (up to four fields, 300 characters each; this can include the description, labels or custom fields), the comment text (up to 600 characters; never for restricted comments), display names of the people involved, and a link to the issue that contains your Jira site address. The daily summary contains the space name, the keys, summaries and statuses of up to 10 issues, counts by status of up to 50 issues, and a link to the Jira search that includes the space's projects and JQL filter. Once delivered, these messages are part of your Google Workspace and are governed by your agreement with Google.
3.4 What we don't collect
No analytics, cookies, advertising identifiers or tracking in the App or on this website. The App doesn't store email addresses, passwords or payment data; payments are processed by Atlassian. We don't ask for sensitive personal data. Please avoid putting sensitive data in issues that you send to Google Chat.
4. Data we control
- Marketplace licensing data. Atlassian shares with us the information a partner needs to manage licenses, such as the site URL, organization name, license tier and dates, country, and the names and email addresses of the technical and billing contacts. We use it to manage licenses, keep accounting and tax records and send essential service or security notices. We don't send marketing.
- Support emails. Your name, email address and whatever you include in your message, used only to answer you.
- Website logs. This site has no cookies or analytics. Our web server keeps standard access logs (IP address, date and time, page requested, browser user agent, referring page) for security and operation.
5. Purposes and legal bases
| Purpose | GDPR legal basis |
|---|---|
| Running the App's features (notifications, personal notifications, daily summary) | Processing on your organization's behalf (art. 28 GDPR); the legal basis is your organization's, typically the performance of its contracts or its legitimate interest in internal communication. |
| Checking permissions as the user before each personal notification | Part of the service the user requests; the user authorizes it in Atlassian's consent screen when saving the personal page. |
| Managing licenses and accounting records | Performance of a contract (art. 6(1)(b)) and legal obligations (art. 6(1)(c)). |
| Answering support requests | Performance of a contract (art. 6(1)(b)) or legitimate interest in answering you (art. 6(1)(f)). |
| Security of the App and this website, including server logs | Legitimate interest (art. 6(1)(f)). |
LFPDPPP. All of the purposes above are primary purposes, necessary for the service. We have no secondary purposes: we don't use personal data for marketing, advertising or profiling.
6. Where data is stored and international transfers
- App data stays in Forge storage on Atlassian's cloud infrastructure, encrypted at rest by Atlassian. If your organization has pinned your Jira site to a data residency location, the App's data is stored in that location. If not, Atlassian decides where it is hosted and may move it between its locations: the United States, the European Union (Frankfurt and Dublin), Germany, the United Kingdom, Switzerland, Canada, Australia, Singapore, Japan, South Korea and India. See Atlassian's Forge data residency page.
- Messages go over HTTPS to
chat.googleapis.comand are stored by Google according to your Google Workspace settings and region. - Support and privacy emails are stored by our email provider, Zoho Corporation, in its United States data centre, and handled by us from Mexico.
- Licensing data is provided by Atlassian through its partner tools; we access it from Mexico.
- This website runs on a server of Contabo GmbH in Germany.
We don't receive the data of your Jira site, so the App does not transfer it to us. Information you send us yourself by email is collected directly by us in Mexico; we don't rely on Standard Contractual Clauses for it.
7. Sub-processors and recipients
| Who | Role | Data |
|---|---|---|
| Atlassian (Atlassian Pty Ltd and affiliates) | Sub-processor: hosts and runs the App on Forge (compute, storage, logs); sells and bills licenses through the Marketplace. | All App data in section 3; licensing data. Privacy policy · DPA |
| Google (Google LLC and affiliates) | Recipient chosen by you: Google Chat receives the messages sent to the spaces you configure, under your own Google Workspace agreement. | Message content (section 3.3). Privacy policy · Data processing terms |
| Zoho Corporation (email, United States) | Our email provider for support@sagosoft.com. | Support and privacy emails. |
| Contabo GmbH (web hosting, Germany) | Hosts this website. | Web server logs. |
We don't sell, rent or share personal data for advertising. We would disclose data to authorities only when legally required.
8. Retention
| Data | How long |
|---|---|
| Space settings and webhook link | Until an administrator deletes the space (possible at any time, also when the license is not active) or the App is uninstalled. |
| Personal subscription and webhook link | Until the user turns it off (possible at any time, also when the license is not active), the Atlassian account is closed or deleted (checked weekly, see section 9) or the App is uninstalled. |
| Issue data read during an update | Not stored: only in memory for the few seconds needed to send the message. |
| App error logs on Atlassian | Technical data only (event type, issue key, HTTP status, short error message), no issue content and no webhook links. Atlassian makes them available to us for a limited time (currently up to 30 days); site administrators can stop sharing them with us in Atlassian Admin. |
| After uninstalling | Atlassian keeps the App's Forge storage for up to 28 days and then permanently deletes it. Reinstalling doesn't restore it, and we don't offer restoring it. If the Jira site itself is deleted, its App data is deleted with it. |
| Deleted data in Atlassian's systems | When the App deletes data, Atlassian may keep soft-deleted copies and backups until the end of its own retention period, under Atlassian's policies. |
| Messages in Google Chat | Under your Google Workspace retention settings. The App can't edit or delete posted messages. |
| Licensing data | While the license is active and afterwards as long as tax and accounting law requires (in Mexico, generally 5 years). |
| Support emails | As long as needed to handle your request and any follow-up, and longer only if needed for a legal claim or obligation. |
| Website server logs | For the period set by our server's log rotation, and only as long as needed for security and operation. |
9. Personal data reporting to Atlassian
Every week the App reports to Atlassian's personal data reporting API the account IDs that have a personal subscription, as Atlassian requires from apps that store account IDs. When Atlassian answers that an account has been closed, the App deletes that person's subscription and webhook link.
10. Security
Webhook links are encrypted secrets, the App can only connect to chat.googleapis.com, administrator actions are checked on the server and personal notifications are sent only after Jira confirms the person can see the issue. More in the security overview.
11. Your rights
Under the GDPR you have the rights of access, rectification, erasure, restriction, portability and objection, and to withdraw consent at any time. Under the LFPDPPP you have the ARCO rights (access, rectification, cancellation and opposition), and you can revoke your consent and limit the use or disclosure of your data.
- Data in your Jira site and the App's settings are controlled by your organization: contact your Jira administrator first. Any user can delete their own personal subscription at any time with Turn off, and administrators can delete any space, also when the license is not active. The personal subscription of someone who can no longer sign in is deleted when their Atlassian account is closed or deleted (weekly check) or when the App is uninstalled. We don't have access to this data, but we will answer your organization's questions to help it handle requests.
- Data we control: email support@sagosoft.com with the subject “Privacy request” and include your name, an email address to answer you, a clear description of the data and the right you want to exercise and, for corrections, the correct data. For requests under the LFPDPPP, also include a document proving your identity (or your representative's authority); for other requests we will only ask for additional information if we have reasonable doubts about your identity.
We answer within 20 business days and, if the request is granted, carry it out within the following 15 business days, as the LFPDPPP provides; for GDPR requests, within one month at the latest. Requests are free.
If you're not satisfied you can complain to the data protection authority of your country (in the EU, see the list of authorities; in Mexico, the Secretaría Anticorrupción y Buen Gobierno; in Brazil, where you also have the rights of article 18 of the LGPD, the ANPD).
12. Other information
- Automated decisions: the App decides who gets a message from the rules you configure; it makes no decisions with legal or similarly significant effects and does no profiling.
- Children: the App and this website are for businesses and not directed to children.
- Changes: we publish any change on this page with a new date. For significant changes we will also give notice in the Marketplace listing or the App's release notes.
- Languages: this policy is also available in Spanish and Portuguese. For Mexican data subjects the Spanish version is the privacy notice under the LFPDPPP.
13. Contact
Luis Ángel Sánchez Gómez (SagoSoft) · Calle Cuenca del Conchos 6831, Fraccionamiento Antiguo Lienzo Charro, C.P. 31375, Chihuahua, Chihuahua, Mexico · support@sagosoft.com