Privacy Policy

Last Updated: March 9, 2026 Effective Date: March 9, 2026

1. Introduction

This Privacy Policy describes how Human Renaissance Corporation (“we,” “us,” or “our”) collects, uses, and shares information in connection with your use of Lens, a Project Portfolio Management application for Jira Cloud available on the Atlassian Marketplace (the “App”), our pre-launch website, and any related services (collectively, the “Service”).

Lens is built on Atlassian Forge and operates entirely within the Atlassian cloud infrastructure. By using the Service, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

2.1 Information Collected Through the App

When you use Lens within Jira Cloud, the App accesses and processes the following data:

Jira Issue Data: Issue keys, summaries, descriptions, status, priority, assignee, sprint, labels, components, fix versions, story points, dates, custom field values, issue links, and issue type. This data is cached locally in Forge SQL (within Atlassian’s infrastructure) to provide fast portfolio views.
User Identity Information: Your Atlassian account ID, display name, email address, and avatar URL, as provided by the Atlassian platform for authentication, permission checking, and display purposes.
App Configuration Data: Lens definitions, hierarchy structures, view configurations, sync agent settings, formatting rules, and permission grants that you create within the App.
Usage Data: Interaction patterns within the App (e.g., which features are used, error events) collected through Atlassian’s standard Forge telemetry.

2.2 Information Collected Through Pre-Launch Website

When you sign up for our beta program or waiting list:

Email Address: The email address you provide when applying for beta access.
Device Information: Standard web analytics data including browser type, operating system, and referral source.
Analytics Data: We use third-party analytics tools to collect anonymized usage data such as page views, feature interactions, and general traffic patterns to improve the Service.

2.3 Information We Do NOT Collect

We do not collect or store passwords or authentication credentials.
We do not transmit Jira data to any servers outside of Atlassian’s cloud infrastructure.
We do not use advertising networks or sell personal data.

3. How We Use Information

We use the information we collect for the following purposes:

To Provide the Service: Rendering portfolio views, executing sync agents, caching Jira issue data for performance, managing hierarchy structures, and providing inline editing capabilities.
To Manage Permissions: Checking Jira project-level and lens-level permissions to ensure users only see data they are authorized to access.
To Communicate With You: Sending beta program updates, launch notifications, and product announcements to email addresses provided during registration.
To Improve the Service: Analyzing usage patterns and error reports (in aggregate, not individually) to improve reliability and features.
To Enforce Our Terms: Detecting and preventing misuse or abuse of the Service.

4. Data Storage and Security

4.1 Forge Infrastructure

Lens is built on Atlassian Forge. All App data — including cached Jira issues, lens configurations, hierarchy structures, and user preferences — is stored in Forge SQL and Forge Key-Value Store (KVS), both hosted entirely within Atlassian’s cloud infrastructure. No App data is transmitted to, processed by, or stored on external servers.

4.2 Data Residency

Because Lens runs on Forge, data residency is governed by Atlassian’s data residency controls. Your data resides in the same region as your Atlassian Cloud instance. We do not independently control data residency — Atlassian does. Please refer to Atlassian’s Data Residency documentation for details.

4.3 Pre-Launch Website Data

Email addresses collected through our pre-launch website are stored in a database hosted by a reputable cloud provider (e.g., Supabase, Vercel) and are used solely for beta program communication. This data is stored separately from App data and is not linked to Jira account information.

4.4 Security Measures

All data in transit is encrypted via TLS.
All Forge SQL and KVS data is encrypted at rest by Atlassian.
The App undergoes Atlassian’s security screening process for Marketplace publication.
We follow the principle of least privilege: the App requests only the Jira API scopes necessary for its functionality.

We do not sell, rent, or trade your personal information.

We may share information in the following limited circumstances:

With Atlassian: As required by the Forge platform. Forge functions execute within Atlassian’s infrastructure, and Atlassian may have access to operational data as part of platform administration.
Service Providers: We may use third-party services (e.g., email delivery for beta communications) that process limited data on our behalf under contractual obligations to protect that data.
Legal Requirements: We may disclose information if required by law, regulation, legal process, or governmental request.
Business Transfers: In the event of a merger, acquisition, or sale of assets, user data may be transferred as part of the transaction, with notice provided.

6. Data Retention

App Data: Lens configurations, cached issues, and hierarchy data are retained as long as the App is installed on your Jira Cloud instance. Uninstalling the App triggers Atlassian’s standard Forge data cleanup process.
Pre-Launch Email Addresses: Retained until the beta program concludes or you request removal, whichever comes first.
Usage Analytics: Aggregated and anonymized data may be retained indefinitely for product improvement purposes.

7. Your Rights

Depending on your jurisdiction, you may have the following rights:

Access: Request a copy of the personal data we hold about you.
Correction: Request correction of inaccurate personal data.
Deletion: Request deletion of your personal data. For App data stored in Forge, this is accomplished by uninstalling the App. For pre-launch email data, email us at the contact below.
Portability: Request a machine-readable export of your data.
Objection: Object to processing of your personal data for certain purposes.
Withdrawal of Consent: Where processing is based on consent, you may withdraw consent at any time.

To exercise any of these rights, contact us at the email address listed in Section 11.

8. International Data Transfers

Lens operates on Atlassian Forge, which may process data in various Atlassian data center regions globally. By using the Service, you consent to the transfer of information to regions outside your country of residence, subject to appropriate safeguards as maintained by Atlassian.

9. Children’s Privacy

The Service is not directed to individuals under 16. We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal data, please contact us.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the new Privacy Policy on this page and updating the “Last Updated” date. For significant changes, we will provide notice through the App or via email.

11. Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights, contact us at:

Human Renaissance Corporation Email: [email protected] Subject Line: Privacy Inquiry — Lens

This Privacy Policy applies to Lens for Jira Cloud. For questions about how Atlassian handles your data as a platform provider, please refer to Atlassian’s Privacy Policy.