Privacy Policy
This policy explains how Andino Apps ("Andino Apps", "we", "us") handles personal information through our apps for Atlassian cloud products (the "Apps") and through andinoapps.com (the "Site"). In short: our Apps run on Atlassian's platform, we don't receive or keep copies of your Jira content, and we never sell or rent personal information.
1. Who we are and how to reach us
Andino Apps is a sole proprietorship based in Toronto, Ontario, Canada. We have designated a Privacy Officer who is accountable for our compliance with this policy and applicable privacy laws, including Canada's Personal Information Protection and Electronic Documents Act (PIPEDA). Contact the Privacy Officer at privacy@andinoapps.com.
2. Our role
- Inside your Atlassian site, your organization decides how the Apps are configured and which data they send where. For that data, your organization is the controller (or the organization accountable under PIPEDA), and we act as a service provider (processor) on its behalf.
- For the Site, support requests and our business records, Andino Apps is the controller.
3. ChatBridge for Jira & Google Chat
ChatBridge runs on Atlassian Forge. Its code and storage are hosted by Atlassian, not on servers we operate.
3.1 Data stored by the app
| Data | Purpose | Kept for |
|---|---|---|
| Rules: name, JQL filter, selected events, on/off state, created and updated dates | Decide which updates to post | Until an administrator deletes the rule or the app is uninstalled |
| Google Chat webhook URLs, stored encrypted as secrets | Deliver messages to the chosen spaces | Same as the rule |
| Event fingerprints: issue ID, event type, and the new status ID, assignee account ID or comment ID | Avoid posting the same change twice | 30 seconds, then deleted automatically |
Rules may contain personal information if an administrator types it in, for example a person's name in a JQL filter. We recommend not doing so.
3.2 Data processed but not stored
When a selected event happens on an issue that matches a rule, the app reads the issue key, summary, project, issue type, status, priority, assignee display name, the display name of the person who made the change, and, for comment events, the comment text. It builds a message containing these fields (comments are cut to 300 characters) and a link to the issue. Comments restricted to a role or group are never posted with their text, only a note that a restricted comment was added; if the app can't confirm a comment's visibility, it also withholds the text. Jira Service Management internal notes are posted with an "Internal note" label. The data is held in memory only for as long as it takes to send the message.
3.3 Data sent to Google
Messages are sent only to the Google Chat webhooks your administrators configure, at chat.googleapis.com. The app is technically prevented from sending data to any other external address. Once delivered, the messages are governed by your organization's agreement with Google and can be read by the members of that Chat space. Google receives this data on your organization's instructions, not as our sub-processor.
3.4 Operational logs
Forge makes app logs available to us, the developer, for troubleshooting. Our logs record issue keys, event types, rule names, delivery status codes, error messages returned by Jira or Google (which can quote a JQL filter), and webhook addresses with the key and token removed. They don't record issue summaries or comment text. Atlassian keeps these logs for a limited period under its own retention policies, and we only access them to investigate problems.
3.5 Where the data is
App storage and logs are hosted by Atlassian on its cloud infrastructure, which may be in the United States, the European Union or other regions, depending on Atlassian's hosting and any data residency settings available for your site. We access logs from Canada. The European Commission recognizes Canada as providing an adequate level of protection for personal information handled by organizations subject to PIPEDA.
3.6 What we don't do
- We don't copy your Jira data to our own systems.
- We don't use your data to train AI models, for advertising, or for profiling.
- We don't sell, rent or trade personal information.
- We don't make automated decisions about people.
4. The Site and support
- No tracking. The Site uses no cookies, analytics, advertising, social media plugins or third-party fonts.
- Server logs. Our hosting provider (see section 6) automatically processes technical data such as IP address, browser type, requested pages and timestamps to deliver the Site and protect it from abuse. These logs are kept for a short period under the provider's policies.
- Email. If you email us, we use your name, email address and message to answer you and to keep records of support and business correspondence. We keep support emails for up to 3 years after the last message, unless the law requires us to keep them longer.
5. Why we are allowed to process data (EU/UK)
Where the EU or UK GDPR applies, we rely on: performance of a contract (providing the Apps and support), our legitimate interests (keeping the Apps and Site secure and working, which we have balanced against your rights), and legal obligations (for example, tax and accounting records). For data inside your Atlassian site, we process data only on your organization's documented instructions, given through how it configures the App.
6. Service providers (sub-processors)
| Provider | Purpose | Location |
|---|---|---|
| Atlassian | Hosts and runs the Apps (Forge), their storage and logs; Marketplace billing | See section 3.5 |
| Netlify | Hosts the Site | United States and global edge network |
| Google (Google Workspace) | Our business email and support inbox | United States and other regions |
We'll update this list before adding a provider that processes customer data.
7. Retention and deletion
- Rules and webhooks are kept until an administrator deletes them. When the app is uninstalled, Atlassian deletes its storage under its Forge data deletion policies.
- Event fingerprints expire after 30 seconds.
- To ask us to help delete data sooner, email privacy@andinoapps.com from an address linked to your Atlassian site.
8. Security and incidents
Webhook URLs are encrypted and never shown again after saving. Only Jira administrators can view or change rules, and the app checks this on every request. The app requests only the Atlassian permissions it needs. If we become aware of a breach of security safeguards involving personal information that poses a real risk of significant harm, we'll notify the affected organizations without undue delay, report it to the Office of the Privacy Commissioner of Canada as PIPEDA requires, and keep a record of it.
9. Your rights
Depending on where you live, you may have the right to access, correct or delete your personal information, to withdraw consent, to object to or restrict processing, and to data portability. For data inside your Atlassian site, contact your organization's administrator first, since your organization controls it; we'll help them respond. For anything else, email privacy@andinoapps.com. We reply within 30 days and may need to verify your identity.
If you're not satisfied, you can complain to the Office of the Privacy Commissioner of Canada, to Quebec's Commission d'accès à l'information, or to your local data protection authority in the EU or UK.
10. Children
The Apps and Site are intended for businesses and are not directed at children under 16.
11. Changes
We'll post any change here with a new version number and date. If a change affects what data the Apps handle, we'll announce it in the app's release notes before it takes effect.