Trust at Guenov Labs

ClientLens turns a Jira project into a plain-language status page that an agency can share with a non-technical client via a secure link, without giving the client a Jira account.

What it accesses. With your authorization, ClientLens reads the Jira issue data (summaries, statuses, and related fields) from the projects, boards, or filters you select. It reads this using your own Jira permissions — it can't see anything you can't already see. It does not write to Jira.

What it stores, and where. ClientLens stores the published page "snapshot" (a project name, a status, a plain-language summary, plain-language descriptions of selected work items, and your branding) and a per-page access token, both on Atlassian's Forge infrastructure. Access tokens are held in Atlassian's encrypted secret storage.

External sharing — by your choice. ClientLens's purpose is to display the information you publish on a page reachable via a secret link, to the recipients you choose, without an Atlassian login. You control what is published and who receives the link. Only the content you publish is shown; your Jira instance itself is never exposed. Each page's link can be revoked or replaced independently at any time.

AI summaries stay on-platform. The plain-language summary is drafted using Atlassian-hosted AI (Atlassian's Forge LLM capability). Your data is not sent to any external AI provider.

Data retention & deletion

Each published page's content and access token are stored only while you keep the page. You control removal directly:

• Revoke deletes a page's access token, so its link stops working immediately. The page's content remains stored so you can restore access with a new link, without rebuilding the page.
• Delete permanently erases a page's stored content and its access token. Its link no longer resolves, and the content is gone.

Revoking or deleting one page never affects any other page.

When ClientLens is uninstalled from your site, a pre-uninstall process runs before the uninstall completes and deletes all ClientLens data stored for your site — every page's content, index entry, and access token. This runs before Atlassian's own uninstall and retention process begins, so no ClientLens data remains in app storage afterward.

Compliance & badges

• ClientLens runs on Atlassian's infrastructure with data stored on-platform.
• ClientLens serves its external client page via a Forge web trigger, so it isn't eligible for the "Runs on Atlassian" badge. This is inherent to the external-sharing feature and does not change where your data is stored — it remains on Atlassian's infrastructure.
• We follow Atlassian's mandatory cloud app security requirements and complete the Marketplace Privacy & Security disclosures for every app.