Effective date: August 3, 2026
The short version: ConfigLens runs entirely on Atlassian's Forge platform, inside your Atlassian cloud environment. Everything it reads and everything it stores stays with Atlassian — the app makes no network calls to Macon Apps or to any other external service. We operate no servers for ConfigLens, so there is no place your data could reach us. The app never asks for, collects, or stores an API token, password, or any other credential.
1. Who We Are
ConfigLens is a Jira Cloud app operated by Macon Apps, a trade name of Investor Direction LLC, an Ohio (USA) entity. Contact: [email protected] or 937-217-7327.
2. What ConfigLens Accesses
ConfigLens reads your Jira site's configuration: workflows, custom field definitions, field configurations, screens and screen schemes, permission schemes, notification schemes, and issue type schemes. To show who made a change, it also reads Jira's built-in audit log records. All reads use the app permissions a site admin approves at install — Atlassian's Forge platform enforces that boundary.
ConfigLens does not read the content of your issues, comments, attachments, or user directories, and it writes nothing to your Jira configuration — it is a read-only observer.
3. What ConfigLens Stores, and Where
To detect and display changes, ConfigLens keeps the following in Forge storage — Atlassian-hosted storage that lives inside Atlassian's cloud, alongside your Jira data:
- Configuration snapshots: the current shape of each tracked configuration object, used to compute the next diff.
- Change events: the history you see in the timeline — timestamps, object names, before/after diffs, and plain-language summaries.
- Actor names: where Jira's audit log identifies the admin who made a change, that display name is stored on the change event. This is the only personal data ConfigLens holds, and it never leaves Atlassian's platform.
Because storage is provided by Atlassian's Forge platform, it inherits Atlassian's hosting, security, and data-residency arrangements for your site. Macon Apps has no independent copy and no way to access your site's data outside the app itself.
4. No API Tokens, Ever
ConfigLens authenticates through Forge's built-in app identity, granted once at install by your site admin. It has no setup screen requesting an email-plus-token, no credential field of any kind, and it does not collect, transmit, or store Atlassian user API tokens — in line with Atlassian Marketplace security requirements. If any screen ever appears to ask you for a credential, it is not ours: stop and contact us.
5. Payments
ConfigLens is sold through the Atlassian Marketplace. Billing, invoicing, and payment details are handled entirely by Atlassian on your existing Atlassian bill — Macon Apps never sees your payment information. Atlassian shares standard sales reporting with us (site-level license status), not personal payment data.
6. Cookies, Analytics & Tracking
ConfigLens sets no cookies of its own, embeds no analytics, and does no tracking of any kind. The app's user interface is served by Atlassian inside Jira, and the app makes no network egress to any non-Atlassian destination.
7. Data Retention & Deletion
- While installed: snapshots and change history are retained so the timeline and compliance exports keep working.
- On uninstall: the app's Forge storage is removed under Atlassian's platform rules for uninstalled apps. Nothing persists with Macon Apps, because nothing was ever sent to Macon Apps.
- Earlier deletion: to clear history while keeping the app installed, contact us at [email protected] and we'll walk you through it or ship it as a supported action.
- CSV exports are generated on demand and saved to your own device; you control those copies.
8. Third Parties We Rely On
- Atlassian — hosts Jira, the Forge platform the app runs on, the app's storage, and Marketplace billing (Atlassian privacy policy).
That's the whole list. ConfigLens uses no other processor, host, or service.
9. Your Rights
The only personal data ConfigLens holds is admin display names on change events, stored inside your own Atlassian environment and visible only to your site's admins. Requests about your Atlassian account and its data are handled by Atlassian; for anything about ConfigLens's stored history (access, correction, deletion under GDPR, UK GDPR, CCPA, or similar), email [email protected] and we'll honor them.
10. Changes to This Policy
If a future feature changes what ConfigLens stores or where — for example, optional notifications that require external delivery — we'll update this page, adjust the effective date above, and describe the change in the app's Marketplace listing before it ships. Material changes will be called out in the app itself.
11. Contact
Questions about this policy or your data: [email protected] · 937-217-7327 · or via the support portal.