Privacy policy

Last updated 6 November 2026

Who we are

Clearlane is the brand under which Maxime Ragionieri EI, a sole proprietorship registered in France, publishes its apps (details in the legal notice). Contact: [email protected].

Data processed by our apps

For the content of your Atlassian site and the data our apps keep there, your organisation is the controller, and Atlassian hosts it under its own customer agreement and data processing terms. We do not access this data: questions about it go first to your site administrator, and we will help them.

Clearlane apps run on Atlassian Forge. They read the Jira or Confluence content needed to show their result, with the permissions of the signed-in user (unless stated otherwise below), inside your Atlassian site. We do not copy, store or receive this content, and our apps send no data to any server of ours or of a third party.

What each app keeps, inside Atlassian: Clearlane Fresh remembers which pages someone confirmed as still accurate (page ID, date and Atlassian account ID) and the space’s chosen time window. This is kept in Atlassian’s Forge storage for your site, never on our servers, and Atlassian deletes it after the app is uninstalled according to its retention rules. So that no one uses up Confluence’s request limits, which every customer of the app shares, Fresh also keeps usage counters there: requests per minute and per hour for each person, under a salted one-way key with no account ID (kept at most 2 hours), the same for the whole site, the number of pages a space had at its last view (kept 7 days) and, for at most 15 minutes, whether a person administers a space (under the same salted key).

Clearlane Controlled Documents keeps the records a controlled document needs: Atlassian account IDs, the names shown at signing, revisions, content fingerprints, signatures, read confirmations and the audit trail. Signing passwords are kept only as a salted hash, never in clear text. All of this stays in Atlassian’s Forge storage for your site, never on our servers. It also adds edit restrictions to pages under review. Reminders are page comments that mention the person so that Confluence notifies them: at most one a day per person, grouping everything they have to do, with a link to their list of documents to handle.

Clearlane Answers keeps questions and answers as ordinary Confluence pages and comments, created with the permissions of the person asking or answering. It adds a small record to each question page (status, number of answers, and the Atlassian account IDs of the person who asked and of the person who accepted an answer; votes and “helpful” marks are kept as one-way keys, not account IDs) and keeps each space’s topics and experts (Atlassian account IDs) in Atlassian’s Forge storage for your site. Experts are mentioned on new questions so that Confluence notifies them.

Clearlane Budget reads the work items and worklogs of the projects a budget covers with the app’s own access, so that a budget shows the same figures to everyone allowed to see it. Only Jira administrators and the budget managers they name can create budgets, and only for projects they can browse. It keeps budgets, rates, expenses, settings and computed figures, including the Atlassian account IDs and names of people who logged time, in Atlassian’s Forge storage for your site, never on our servers.

Clearlane CAPA keeps CAPA records (problem, containment, root cause, action plan, effectiveness check), the audit trail, settings, Atlassian account IDs and the names shown at signing in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. With the permissions of the person who asks, it creates the work items of new CAPAs and of their actions and links them; it stores searchable CAPA fields as a work item property, and sends each owner at most one reminder e-mail a day through Jira’s own notifications.

Clearlane Read & Understood keeps read requests, confirmations for each page version, quiz answers, the audit trail, settings, Atlassian account IDs and the names shown at confirmation in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. Readers are told with a page comment that mentions them so that Confluence notifies them: at most one a day per person, on their most urgent page, with a link to their reading list.

Clearlane CRA keeps vulnerability and incident cases (facts, qualification, the fields prepared for ENISA and the submissions recorded, fix, users informed, advisory revisions), the audit trail, products, versions, SBOM component lists, settings, Atlassian account IDs and the names shown at signing in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. With the permissions of the person who asks, it creates the work items of new cases and attaches the CSAF and PDF files to them; it stores searchable CRA fields as a work item property and has Jira send each case owner one reminder e-mail a day. It sends nothing to ENISA or to anyone else.

Clearlane Tests keeps test cases (steps, test data, expected results and their versions), campaigns, runs and results, comments, links to requirements and bugs, the history, settings, Atlassian account IDs and the names shown at signing in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. With the permissions of the person who asks, it creates bugs as Jira work items and attaches evidence files to the work item they choose; it stores searchable coverage fields as a work item property on the requirements, and sends each tester at most one reminder e-mail a day through Jira’s own notifications, only about campaigns that person can see.

Clearlane Breach & Incident Reporting keeps incident records (facts, qualification, the notification texts prepared and the submissions recorded, closure), the breach register, the audit trail, settings, Atlassian account IDs and the names shown at signing in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. With the permissions of the person who asks, it creates the work items of new incidents and attaches their PDF evidence files; it stores searchable incident fields as a work item property, and sends each owner at most one reminder e-mail a day through Jira’s own notifications. As Atlassian’s privacy rules require, the account IDs it keeps are reported to Atlassian every week, and erased when an account is closed. Nothing is sent to any authority.

Clearlane Created vs Resolved, Clearlane Throughput, Cumulative Flow – Clearlane, Sprint Burndown – Clearlane and Velocity – Clearlane, dashboard gadgets for Jira, read Jira with the permissions of the person viewing the dashboard. Their settings are kept by Jira with the gadget. To spare Jira, Created vs Resolved and Throughput keep for at most 10 minutes, in Atlassian’s Forge storage for your site, the counts they have just shown to a person and the project or filter name, under a salted one-way key. Cumulative Flow keeps for at most one hour, in Atlassian’s Forge storage for your site, the counts of work items per status that it has just shown to a person, under a salted one-way key. Sprint Burndown and Velocity keep in the same way, for at most one hour, the sprint data they have just read for a person: the project or filter name, sprint names and dates, work item IDs, statuses and story points. So that no one uses up Jira’s request limits, which every customer of the app shares, these five gadgets also count, under the same kind of salted key, the requests each person and the whole site make in the hour, kept at most 2 hours. No account ID, and no work item summary or description, is kept. Nothing is sent to our servers or to anyone else.

Clearlane Risk Register keeps risks (their description, the fields of their template such as causes and consequences, inherent and residual ratings, owner, linked actions, reviews and decisions), their history, each project’s settings (including the names of its risk managers), Atlassian account IDs and the names shown at signing in Atlassian’s Forge storage for your site, never on our servers. Signing passwords are kept only as a salted hash. With the permissions of the person who asks, it creates work items (the risk’s own and those of its actions) and links work items to the risk. With the app’s own access, it writes its searchable risk fields as a property of the risk’s work item and has Jira send each owner at most one reminder e-mail a day.

To spare Jira’s request limits, Clearlane Pulse keeps for at most 24 hours, in Atlassian’s Forge storage for your site, what it has just read: the project’s statuses (IDs, categories and names), your team’s usual pace (durations in days and status IDs), the status history of work items in progress and finished (work item IDs, dates and status IDs), usage counters and recent failures. The usual pace is shared by the people looking at the same project; a status history is given to a person only for the work items their own Jira search has just returned. Keys are salted one-way fingerprints: no account ID, no person’s name, no summary and no work item content is kept. According to Atlassian, expired entries are erased within 48 hours. Nothing is sent to our servers or to anyone else.

WIP Aging – Clearlane and Cycle Time – Clearlane, dashboard gadgets for Jira, read Jira with the permissions of the person viewing the dashboard; their settings are kept by Jira with the gadget. To spare Jira, they keep for less than 24 hours, in Atlassian’s Forge storage for your site, what they have just read for a person (work item IDs and keys, dates, and the IDs, categories and names of statuses) and, for each project or filter, the status history of finished work items (dates and status IDs), given to a person only for the work items their own Jira search has just returned; usage counters are kept two hours. Keys are salted one-way fingerprints: no account ID, no person’s name, no summary and no work item content is kept. Nothing is sent to our servers or to anyone else.

Clearlane Delivery brings together, in one app, the code of Clearlane Gantt, Pulse, Forecast, Budget and the seven dashboard gadgets. Each part keeps, in Atlassian’s Forge storage for your site and under its own prefix, exactly what the matching single app keeps (described on this page): Plan and Forecast only usage counters, Work in progress and the gadgets short-lived caches without account IDs, Budget its budgets, rates, expenses, figures and the account IDs and names they contain. Plan writes Start date, Due date and “blocks” links only when a person asks, with that person’s permissions. Delivery itself keeps which parts a Jira administrator turned on, and hourly usage counters that share Jira’s request limits between parts and people, under salted one-way marks with no account ID (kept at most 2 hours).

Clearlane Automation Steps & Cost, a page for Jira administrators, reads the automation rules file you drop or paste in your browser only: the file itself is never sent to us or kept. To estimate how often each rule runs, the searches taken from your rules, the list of projects and their permissions are read from your Jira with the permissions of the person using the app, and only numbers come back. It keeps in Atlassian’s Forge storage for your site your plan (products, plans, numbers of users and steps used elsewhere) and the totals of the last 12 analyses (date, numbers of steps and of rules), with no account ID and nothing from your rules. It changes nothing in Jira.

Clearlane Planning Poker keeps in Atlassian’s Forge storage for your site its estimation sessions (name, cards, work item ids and keys, an optional vote-by date), the anonymous votes (a card and the time it was played, under an id that the voter’s browser makes from a random number and the session, never an Atlassian account id), the rounds and reveals, and the cards and target field last used in each project. They are deleted 45 days after the session’s last change. Work items are read, and agreed estimates written, with the permissions of the person using the app. No name, email address or account id is kept.

Clearlane CRA, CAPA, Tests, Budget, Forecast, Controlled Documents and Read & Understood add a Rovo agent. If your site has Rovo and someone asks the agent a question, Rovo, Atlassian’s AI, reads the app’s results through read-only actions and only receives what that person is allowed to see in the app. That processing is done by Atlassian, under its own terms for Rovo. Our apps call no AI model of their own and send nothing to any AI service outside Atlassian.

Every app that keeps Atlassian account IDs (Clearlane Fresh, Controlled Documents, Answers, Budget, CAPA, Read & Understood, CRA, Tests, Breach & Incident Reporting, Risk Register and Delivery) reports them to Atlassian every week, as Atlassian’s privacy rules require, and erases them when an account is closed. When an app is uninstalled, Atlassian deletes its data after its retention period.

To decide when to invite someone to leave a review, each app keeps in that person’s browser a small counter of how many times it was opened and whether the invitation was used or dismissed. It holds no personal data, stays in the browser and is never sent to us or anyone else.

Billing

Apps are sold through the Atlassian Marketplace. Atlassian handles payment and invoicing under its own privacy policy. We receive the licence information Atlassian shares with Marketplace partners, such as the customer’s organisation name, licence tier and technical and billing contact details, and use it only to manage licences and answer support requests. Legal basis: the contract with your organisation and our legitimate interest in managing licences. We keep it while the licence runs, then only as long as accounting rules require.

Support emails

When you write to us, we keep your message and address for as long as needed to handle your request, and at most three years after our last exchange. Support requests are handled in our help centre on Atlassian (clearlane.atlassian.net), so Atlassian processes them on our behalf under its own privacy policy. Legal basis: answering your request, as part of the contract with your organisation or in our legitimate interest.

Business contacts

When we write to someone about our apps, we use a work email address that has been made public (company website, press release, public register), or the company’s general address or contact form. In France and the United States, we may also use a work email address deduced from the format the company already publishes (for example [email protected]): we try only one address and delete it if it does not exist. We may also write to you on LinkedIn from our founder’s account. Names and job titles come from the same public sources or from public LinkedIn profiles. Each first email links to this section. We record where we found each address: reply to any of our messages to learn it, to object (reply “no”) or to have your details deleted. We keep a succinct record (name, job title, company, address and where it came from, date, reply) for three years after your last reply, or after our first message if you never replied. Legal basis: our legitimate interest in presenting a work tool to the people in charge of the area it covers. Our email and files are hosted by Apple (iCloud) and backed up privately with Atlassian (Bitbucket), and we prepare our messages with an AI assistant (Claude, by Anthropic); see “Service providers and transfers” below. Reply “no” to any message and we will not write to you again: we delete your details from our files and keep only a note of this refusal (name, company, date) for three years, so that it is respected; older copies in our private backup are not used and are deleted when it is renewed, within twelve months.

Product updates (“Keep me posted”)

If you ask on our website to be kept posted about an app, we keep your email address, the app and the language of the page, and the proof of your consent: the date, the form and your click on the confirmation link we email you. We use them only to send you short emails about that app: news when it gets something new, and one message two weeks after you sign up to ask how it is working for you. Nothing is collected inside our apps: their “Keep me posted” link only opens this website. These emails carry no open or click tracking. Legal basis: your consent, which you can withdraw at any time with the unsubscribe link in every email or by writing to us. Our email provider, Brevo, a company based in France, keeps these data for us in the European Union under its data processing agreement. We keep them until you unsubscribe; after that we keep only your address on a do-not-email list, so that we never write to you again.

This website

This site uses no cookies, no analytics and no tracking. Our host, Cloudflare, processes technical data such as IP addresses to deliver the site and protect it from attacks. Legal basis: our legitimate interest in delivering and securing the site; Cloudflare keeps these logs under its own policy.

Our LinkedIn page

LinkedIn shows us anonymous statistics about visits to our page. LinkedIn and we are jointly responsible for these statistics under the terms LinkedIn publishes for page administrators; LinkedIn’s privacy policy applies. Legal basis: our legitimate interest in knowing how our page is used.

Our Marketplace listings

When you visit the page of one of our apps on the Atlassian Marketplace, Atlassian may load Google Analytics with our measurement ID, depending on the cookie choices you make on the Marketplace. We see aggregated statistics only, such as how many people viewed each listing, where they came from, their country and their type of device. Links from this site to the Marketplace carry campaign tags that name the page of this site they come from, never the visitor. We receive no name or e-mail address, and none of the data our apps keep. Google processes these statistics for us under its data processing terms; data sharing with Google for other purposes is turned off. Google may process this data in the United States under the EU–US Data Privacy Framework. Event-level data is kept for two months; aggregated reports may be kept longer. Legal basis: your consent, given on the Marketplace, which you can withdraw at any time in its cookie settings (see also Atlassian’s privacy policy).

Service providers and transfers

Atlassian (help centre and private backup of our files), Cloudflare (website hosting), Brevo (product update emails, in the European Union) and Google Ireland Limited (statistics of our Marketplace listings) process data on our behalf. Apple (our email and files) and Anthropic (Claude, the AI assistant we use to read and prepare messages) work under their own terms and privacy policies, with no data processing agreement with us; Anthropic Ireland, Limited is a separate controller of what we enter into Claude. We never upload attachments to Claude, and we have switched off the setting that lets Anthropic use our conversations to train its models (its privacy policy still allows this for conversations flagged for safety review or sent to it as feedback). These providers may process data outside the European Union, in particular in the United States. For those acting on our behalf, these transfers rely on the EU–US Data Privacy Framework, another adequacy decision or the European Commission’s standard contractual clauses; you can ask us for a copy of these clauses. Apple and Anthropic describe their own transfers in their privacy policies.

Your rights

Under the GDPR you can ask to access, correct or delete your personal data, to restrict its use or to receive a copy, and you can object to its use, by writing to [email protected]. You can also complain to the French data protection authority, the CNIL (cnil.fr).