Privacy policy · Steadfast Gantt Planner

In short

The app runs entirely on Atlassian’s platform (Forge). I don’t run any servers or databases for it, and it sends nothing anywhere outside Atlassian.
It stores your charts, their last 20 versions, and rows you copy (for 24 hours) in your site’s app storage, with the Atlassian account IDs of the people who edit, author or are assigned to them.
It never stores names or email addresses: they’re looked up from Confluence when they’re shown.
Unsaved edits are kept in your own browser until they’re saved.
There are no analytics, no tracking, no cookies and no ads, and I never sell or share your data.

Who this policy covers

This policy covers the Confluence Cloud app Steadfast Gantt Planner (“the app”), offered on the Atlassian Marketplace by Christian Ortiz, an individual publishing as Christian Ortiz Studio (“I”, “me”). It explains how the app handles data on the Confluence sites where it’s installed, and how I handle the information Atlassian and you share with me.

It doesn’t cover Confluence itself, or Atlassian’s own processing of your data, which is governed by Atlassian’s privacy policy.

Questions about this policy: support@christianortiz.studio.

Where the app runs

The app is built on Atlassian Forge, which means its code runs on Atlassian’s infrastructure and its data is kept in Atlassian-hosted app storage that belongs to your Confluence site.

The app declares no external servers and makes no network requests outside your Confluence site. Its screens load nothing from third parties: no scripts, fonts or images from elsewhere.
I have no database or server of my own that holds your data.
Data residency. Forge hosted storage follows your site’s data residency: if your Confluence site is pinned to a location (such as the EU, US, Australia or Germany), the app’s stored data is kept there too, and it moves with your site if the site is migrated. The app keeps all of its data in Forge hosted storage and has no remotes or outbound requests, so it qualifies without any extra setup. Atlassian aims to run the app’s code in the same location but doesn’t guarantee it, so processing in memory may occasionally happen elsewhere within Atlassian’s infrastructure.

What the app reads

The app works only within your Confluence site, and only reads what it needs:

It checks permissions: before saving any change to a chart, it asks Confluence, as you, whether you can edit the page or blog post the chart is on. It doesn’t read the page’s content.
It reads people’s names from Confluence to show assignees and version authors, and searches people on your site when you pick an assignee. The names are shown, not stored.
It reads the license state Atlassian gives it, to decide whether charts can be edited.

The app has no permission to write to your pages, spaces or any other Confluence content.

What the app stores, and for how long

Everything below is kept in your site’s Atlassian-hosted app storage.

Charts: each chart’s title, working calendar (working days, period start day and holidays), lanes (name and colour), the IDs of the page and macro it belongs to, a revision number, counts, the dates it was created and last saved, and the account IDs of the people who created it and last updated it. Kept while the app is installed. Removing the macro or the page doesn’t delete a chart in this version.
Tasks in each chart: name, type (task, milestone or parent), start and end dates, duration, progress, parent, lane, predecessors, order, whether it’s collapsed, status, and the assignee’s account ID. Kept with their chart.
Versions: snapshots of a chart’s tasks, calendar and lanes, with when and why each was saved and the account ID of its author. The last 20 versions per chart are kept; older ones are deleted as new ones are saved.
Copied rows: the rows you copy with Copy rows (including their assignees’ account IDs), the source page ID and chart title, and your account ID. Deleted 24 hours after you copy them, by a daily clean-up.
Tour progress: whether each person has seen the first-run tour, stored with their account ID. Kept while the app is installed, unless the account is closed.
Personal data register: the list of account IDs the app stores and where, so it can report them to Atlassian and erase them when an account is closed (see below).
App bookkeeping: when the daily clean-up and the personal data report last ran.

Data kept in your browser

While you edit, changes that haven’t been saved yet are kept in your browser’s local storage on your device, so a crash, a closed tab or a lost connection doesn’t lose them. They never leave your device except to be saved to the chart, and they’re cleared once they’re saved. If you choose Download unsaved edits (JSON) or export chart JSON, the file is saved to your device and is yours to keep or delete.

Personal data

Atlassian account IDs are personal data. Task names, chart titles and lane names may also contain personal data that your team types into them; the app handles them only as described here.

The app doesn’t store people’s names, email addresses or profile pictures. Only account IDs are kept.

Every day the app checks whether a week has passed since its last report, and if so it sends the account IDs it stores to Atlassian’s personal data reporting service, as Atlassian requires. When Atlassian reports that an account has been closed, the app removes that account ID everywhere it’s stored: from charts, task assignees (the tasks become unassigned), version authors and other people’s copied rows. It also deletes that person’s own copied rows and tour progress.

Logs

Atlassian gives me access to the app’s logs and usage metrics so I can keep it working. The app writes only reference codes, error codes and counts to its logs, for example the reference and code of a failed save, or how many expired copies the daily clean-up removed. It never logs chart content, task names or account IDs.

Who’s responsible for your data

For the content and account IDs the app handles on your Confluence site, your organization is the controller and I’m the processor: the app processes them only to do what your users ask. The data processing agreement sets out the terms and applies automatically.
For the licensing and contact details Atlassian shares with me, and for support emails you send me, I’m the controller.
Under the California Consumer Privacy Act, I’m your organization’s service provider. I don’t sell or share personal information.

What I receive, and what I don’t

I don’t receive your charts or your Confluence content. The app has no way to send them to me.

When your organization installs, evaluates or buys the app, Atlassian shares licensing information with me, which can include your site address, organization name, and the names and email addresses of technical and billing contacts. I use it only to manage licenses, provide support and send notices that matter (such as security notices), and I keep it only as long as I need it for those purposes and for my legal and tax records.

If you email me for support, I keep your message and email address to help you and to improve the app. I’ll delete them on request unless I need to keep them by law.

I don’t sell, rent or share your data with anyone. The only sub-processor is Atlassian, which hosts the app’s code and storage on Forge under the Forge Data Processing Addendum. There are no other third parties. I’d disclose information only if the law required me to.

Security

The app asks Atlassian only for the access it needs: its own storage, permission checks on pages and blog posts, reading and searching people for names, and personal data reporting. It can’t write to Confluence content.
Every change to a chart is checked on the server: the license, your permission to edit the page (asked of Confluence as you), and the data itself, which is validated before anything is written. Charts are tied to the page and macro they belong to, so a chart can only be changed from its own page.
Conflicting saves are detected instead of silently overwriting each other.
Security contact: email support@christianortiz.studio with Security in the subject line. I acknowledge security reports within two business days.
I don’t hold security certifications of my own, such as SOC 2 or ISO 27001. The app’s code and data run on Atlassian’s infrastructure, which Atlassian’s own audits cover.
If I learn of a security incident that affects your data, I’ll tell affected customers without undue delay.

Deleting your data

Copied rows expire after 24 hours, and versions beyond the last 20 are deleted as new ones are saved.
Closed accounts are erased automatically, as described under Personal data.
Uninstall the app to remove all of its data from your site. Atlassian then deletes the app’s storage under its data lifecycle for Forge hosted storage: the data is soft-deleted when the app is uninstalled and kept for 28 days, then permanently deleted. Reinstalling doesn’t bring it back on its own; within the first 21 days it can be reconnected to a reinstalled app only if your organization asks for that. I don’t keep a copy.
Ask me at support@christianortiz.studio with your site address, for example to remove one chart’s data while keeping the app, and I’ll help and confirm what was removed.

Your rights

Depending on where you live, you may have the right to access, correct, delete or move your personal data, or to object to how it’s used. Because the app’s data lives in your organization’s Confluence site, the quickest route is usually through your site admin, but you can always email me and I’ll respond within 30 days.

For content in your Confluence site, your organization decides what’s stored and why; the app processes it only to provide the charts your users build. The data processing agreement applies to that processing.

Children

The app is a business tool and isn’t directed at children.

Changes to this policy

If I change this policy, I’ll update the date at the top of this page. If a change affects how your data is handled in a meaningful way, I’ll also say so in the app’s release notes or Marketplace listing before it takes effect.

Contact

Christian Ortiz, publishing as Christian Ortiz Studio
support@christianortiz.studio