Privacy Policy

Data processing

• CSV parsing and validation run inside the app page.
• The app does not persist CSV files, filenames, rows, identifiers, or error reports.
• For the optional preview, only selected identifier values are sent to the customer's own Atlassian Assets API.
• The app has no external network egress and does not use a third-party analytics service.
• The app cannot create, update, or delete Assets objects.

Product metrics and platform logs

The app emits counter-only Forge custom metrics for page views, demo use, validation outcomes, successful previews, and voluntary pricing intent. Atlassian attaches app, site, environment, and module context. No CSV content, identifier, filename, or email address is included. A site administrator may disable custom metrics access through Atlassian administration.

Atlassian Forge may also produce execution logs that a site administrator can choose to share with the app developer for troubleshooting. The app does not intentionally write CSV rows, filenames, object identifiers, or email addresses to those logs. Log access and retention are controlled by Atlassian.

Retention and deletion

The app maintains no application database or customer-data store, so there is no stored CSV or Assets data for the developer to retain or delete. Atlassian controls retention of Forge platform metrics and execution logs under its applicable terms.

Contact

Start a topic in the JSM Development section of the Atlassian Developer Community and include “Assets Import Preflight” in the title. No developer email address is published or collected by this site.