Privacy policy

Effective October 16, 2026

This policy explains how PluginCraft enr. ("PluginCraft", "we", "us") handles personal information. It covers the website at plugincraft.ca, the Craftline Hierarchy app for Jira Cloud (the "app"), and the licensing and support we provide around it.

PluginCraft enr. is an enterprise registered in Québec, Canada. We follow Québec's Act respecting the protection of personal information in the private sector and, where it applies, Canada's Personal Information Protection and Electronic Documents Act (PIPEDA).

Who to contact

The owner of PluginCraft enr. is the person in charge of the protection of personal information. For any question, request or complaint about your personal information, write to plugincraft.support@gmail.com.

1. This website

plugincraft.ca is a set of static pages. It sets no cookies, runs no analytics or advertising scripts, and loads nothing from other websites. We don't build visitor profiles.

The site is hosted on Google Cloud Run, in Google's data centres in the United States. Like any web server, it records basic request logs: your IP address, the date and time, the page asked for, and your browser's user agent. Google keeps these logs for us in Google Cloud Logging, which may store them outside Canada. We look at them only to keep the site running and to deal with abuse, and they are deleted automatically after 30 days.

2. The Craftline Hierarchy app

Where your data lives

The app is built on Atlassian Forge and runs entirely on Atlassian's infrastructure. Everything it stores is kept in Atlassian's Forge hosted storage for your Jira site. That storage stays in your site's data residency location and moves with your site if an admin changes that location.

The app declares no outside network access. It cannot send your data to PluginCraft, to an analytics service, or to any other server outside Atlassian, and it doesn't.

What the app stores

• The hierarchies you build: their rows, folders, memos, planning items, rules, views, columns, notes and app field values.
• Change history and write-back runs, so you can see what changed and undo it.
• Settings, permissions, app admins, limits, and the license key for your site, which carries your organization's name.
• Atlassian account ids, to record who owns a hierarchy, who has access and who made a change. The app does not keep people's names or email addresses on its own. It asks Jira for them when it needs to show them. Anything people type into notes, memos or fields is stored as they wrote it.

When you turn on Jira search for a hierarchy, the app also writes small search tokens to the issues as Jira issue properties. Jira keeps those with the issues.

A few display choices, such as text wrapping or the last hierarchy you opened, are kept in your own browser's local storage. They aren't cookies and they aren't sent to us.

How the app reads Jira

The app reads and changes Jira as the person using it, through Atlassian's own APIs. Jira's permissions apply, so nobody sees or changes more through the app than Jira already allows them.

Logs

When something fails, the app writes a log line that Atlassian makes available to us as the developer. These lines hold only ids, counts, statuses and error codes. They never contain issue summaries, field values, query text, names or email addresses. Atlassian keeps app logs under its own retention rules. We read them only to find and fix problems.

The Rovo agent

If you use the Hierarchy helper agent in Rovo, Atlassian's Rovo processes your request on Atlassian's platform under Atlassian's terms. The app gives Rovo only what it needs to answer, as you, and sends nothing outside Atlassian.

Backups and exports

When an admin makes a backup or someone exports to Excel, CSV or JSON, the file is saved wherever that person chooses. We never receive it.

When the app is removed

If you uninstall the app, Atlassian deletes the app's stored data for your site under its Forge data retention rules. We keep no copy.

Atlassian's role

Atlassian runs Jira Cloud and the Forge platform the app runs on. Its handling of your data is covered by Atlassian's privacy policy, not this one.

3. Licenses, support and contact

This is the only personal information PluginCraft itself holds.

• Licenses. When you ask for a trial or buy a license, we record the customer's name, the Jira site id, the license id and dates, and the name and email of the person we deal with. To issue an invoice we also need a billing address and, for a business, its tax numbers.
• Payments. If you pay online, the payment provider handles your payment details. We never see or keep full card numbers.
• Support and email. When you write to us, we keep your message, your email address and anything you choose to include. The app's support bundle holds only counts and ids, and you decide whether to send it.

We use this information to issue and manage licenses, answer you, send invoices, and meet our legal and tax obligations. We'll email license holders about things that matter to their license, such as an important update or a change to these policies. We won't add you to a marketing list unless you ask to be on one.

How long we keep it

• License and invoice records: while the license exists, then for as long as tax law requires us to keep accounting records (generally six years).
• Support emails: up to two years after our last exchange, unless they're tied to an open issue or a license record.
• Website request logs: 30 days.

After that, we delete the information or make it anonymous.

4. Who we share it with

We don't sell, rent or trade personal information. We share it only:

• with service providers who work for us under contract and only for that work: Google (website hosting and our Gmail email), our payment provider and our accountant;
• when the law requires it, for example a valid court order;
• with a buyer, if PluginCraft is ever sold or merged, under the same protections as this policy.

5. Information kept outside Québec

Some of our providers store information outside Québec, including in the United States. The website runs there, and Google may keep its logs and our Gmail email in other countries. Our payment provider may also keep data abroad. Before we use a provider, we check that it protects information adequately and we put that in writing. The law of the place where the information is kept may let authorities there ask for it.

Data stored by the app is not covered by this section. It stays in your Jira site's own location, as explained above.

6. How we protect it

Access to our accounts and records is limited to the people who need it and protected with strong passwords and two-factor authentication. The key that signs license keys is kept offline. The app relies on Atlassian's security for everything it stores.

If a confidentiality incident involving your personal information creates a risk of serious injury, we will tell you and the Commission d'accès à l'information du Québec promptly, as the law requires. We keep a register of every incident.

7. Your rights

You can ask us to:

• tell you what personal information we hold about you and give you a copy, including in a structured, commonly used technology format;
• correct anything that is wrong, incomplete or out of date;
• delete information we no longer need or should not have;
• stop using your information for a purpose you agreed to earlier.

Write to plugincraft.support@gmail.com. We may ask you to confirm who you are. We answer within 30 days, and it's free.

Data you created in the app is in your Jira site, so your site admins can export, change or delete it directly. We can't reach it from outside.

If you aren't satisfied with our answer, you can complain to the Commission d'accès à l'information du Québec or the Office of the Privacy Commissioner of Canada.

8. Children

The app and this website are meant for businesses and are not aimed at children under 14. We don't knowingly collect their information.

9. Changes to this policy

If we change this policy, we'll update the date at the top of this page. If a change is significant, we'll also email license holders before it takes effect.

10. Language

This policy is available in English and French. Both versions have the same value.