Privacy Policy

Effective date: October 15, 2026.

Who this policy covers

This policy describes how Four Leafs Technology, LLC ("Certia," "we," "us") handles data through the Certia Atlassian Forge application, installed by an organization ("Customer") on its own Jira and/or Confluence site. Certia is a business-to-business product: it processes Customer's own Jira/Confluence users' data on Customer's behalf, as their data processor — not as a consumer-facing service. If you're an employee whose access was reviewed using Certia, your employer (the Customer) is who controls that data; contact them first for any request about it.

What data Certia collects, and why

When an admin runs an access-review campaign, Certia reads and stores, in Atlassian's own Forge Storage (tied to the application's installation on Customer's site):

• Campaign details — name, scope, due date, and the admin who created it (by name and Atlassian account ID).
• Per reviewed person — name, the Jira/Confluence groups and roles they hold, an inferred last-active date, computed risk flags (e.g. inactive 90+ days, admin-group membership), whether their Jira account is active or deactivated, their direct (non-group) access grants, what else their groups control, what was decided about them in any earlier review cycle, and whether an admin flagged their access as higher-risk for that campaign. This is captured once when the campaign is created, as a point-in-time snapshot.
• Decisions — a reviewer's keep/revoke/escalate decision and a required written note, for every decision made.
• Audit and notification records — a permanent, append-only log of who did what and when (by Atlassian account ID, not name), plus the in-product reminders and escalation notices a user is shown.

Email addresses — read transiently, never stored: when an admin opens the reviewer directory or creates a campaign, Certia calls Jira's API for each person's basic profile, which includes their email address. Certia uses that email address for one narrow purpose — comparing its domain against the organization's majority domain, to compute an "external domain" risk flag — and then discards the address immediately. The email address itself is never written to Certia's storage, never included in the campaign snapshot described below, and never sent to the AI classifier; only the resulting true/false risk flag is retained. Beyond this, we do not collect any data about a person beyond what is already visible to the application through Jira's and Confluence's own user, group, and permission data, under the access scopes Customer's own Jira admin granted when installing the app.

Our website

This section covers visitors to this website (certia.fourleafstechnology.com), not data inside the Certia app. We use Google Analytics 4 to understand how people find and use the site: pages viewed, the site that referred you, approximate location (country and city level), and device and browser type. Google Analytics sets first-party cookies to do this, and Google processes the data on our behalf. The Certia listing on the Atlassian Marketplace may report page views to the same Google Analytics property. None of this is connected to the Certia app or to any data in your Jira or Confluence site. You can block it with your browser's cookie settings or Google's opt-out browser add-on.

Who we share data with

• Atlassian — hosts the application and all of its storage, as the underlying Forge platform. This isn't a choice we make per request; it's inherent to how a Forge app runs.
• AI-assisted pre-classification — runs on Atlassian's Forge LLMs service, which hosts the AI model (Anthropic's Claude) inside Atlassian's own cloud. No data is sent to a separate third-party AI provider. Even so, the classifier only ever receives group names, role names, days since last active, and computed risk-flag labels — a person's name, email, and Atlassian account ID are never included.
• Google — for website visitors only, as the provider of Google Analytics (see "Our website" above). Google never receives data from the Certia app itself.

We do not sell personal data, and we do not share it with anyone else.

Data retention

While your subscription is active, we keep campaign, review, decision, and audit data for the life of the subscription — a completed campaign's record is the point of using Certia. Within 30 days of Customer uninstalling the application, we delete that data. Today this deletion is a manual process we carry out directly against Forge Storage, not yet an automated action triggered by uninstall itself — stated plainly rather than implying more automation than exists.

Your rights

To access, correct, or delete the personal data Certia holds through your organization's use of the app, email [email protected]. We'll verify the request comes from an authorized admin for the relevant site and fulfill it — including deletion — within 30 days. Today we do this manually rather than through Atlassian's own automated data-subject-request tooling (Forge's privacy.reportPersonalData); we intend to adopt that as Certia grows, but a request made today is honored on the same timeline either way. If you're an employee whose access was reviewed using Certia, your employer (the Customer) controls that data — see "Who this policy covers" above; we'll direct individual requests there first.

Security

Every part of the application that returns another person's data checks, on the server, that the calling user actually holds Customer's Jira ADMINISTER permission — this isn't inferred from which screen a request came from. A reviewer can only see and act on their own assigned review items.

Changes to this policy

We'll post updates to this page and revise the effective date above whenever this policy changes. For a material change — one that meaningfully expands what we collect or who we share it with — we'll also flag it, where available, through the billing/order contact Atlassian provides us for an active subscription (a separate channel from the reviewed-subjects' data described above, which deliberately never includes an email address).

Contact us

Questions about this policy: [email protected].

Back to Certia