LÉGALES

Confidentiality

Last updated: November 2026

This Privacy Policy explains how Agile4Me processes personal data in connection with the Flow Analytics Pro solution (“FAP” or the “Solution”) and its website flowanalyticspro.com, in accordance with the General Data Protection Regulation (GDPR) and the French Data Protection Act (loi Informatique et Libertés).


1. Who we are

Agile4Me, a French SARL (limited liability company) with a share capital of 1,000 euros, registered with the Nanterre Trade and Companies Register (RCS) under number 813 922 267, whose registered office is at 21 rue des Vergers, 92320 Châtillon, France, represented by its manager (gérant), Couthaïer Farfra.

Contact and data protection requests: contact@agile4me.com


2. Agile4Me’s role

Agile4Me acts in two capacities:

  • Controller, for the data of user accounts, the business relationship, billing, support and the website.
  • Processor, for the data from the customer’s tools (Jira, Azure DevOps, GitHub, GitLab, imported files) processed by the Solution on behalf of the customer. The customer remains responsible for this processing; Agile4Me acts only on its instructions.

For the Solution installed on-premise, the data are hosted and processed on the customer’s infrastructure. Agile4Me has no access to them, unless the customer expressly authorises it for a support operation.


3. Data processed

3.1 Data of the Solution users

  • Jira Cloud add-on: Atlassian account ID, display name, language, and the Jira site and installation identifiers. Jira group membership is read at sign-in to identify Jira administrators.
  • SaaS Solution: last name, first name, business e-mail address, password (hashed), role in the Solution.
  • Preferences: language, display settings.
  • Technical data: connection and technical call logs (date, time, errors, Atlassian account ID).


3.2 Jira Cloud data accessed by the add-on

The Jira Cloud add-on holds the Jira permissions to read data and to act on behalf of a user (READ and ACT_AS_USER). It only reads data: it does not create, modify or delete anything in Jira. Data are imported when a user adds or refreshes a project.

For the imported projects, the add-on accesses and stores on its backend:

  • Project configuration: project keys and names, boards, sprints, versions, components, epics, labels, priorities, resolutions, issue types, workflow statuses, field definitions and time-tracking settings.
  • Issues: the fields returned by Jira, including key, URL, title (summary), description, type, status, priority, resolution, dates, estimates, labels, components, versions, sprints, parent or epic, the blocked flag and custom fields.
  • Issue history: the Jira change log (date, field changed, old value and new value).

These data are used only to calculate and display the metrics and charts requested by the customer. They are not used to monitor or evaluate individuals.


3.3 Data from the customer’s other tools

For GitHub, GitLab and Azure DevOps, the Solution reads project, branch, commit, pipeline, deployment and label data. The data of imported files are those contained in these files.


3.4 Data of customers, prospects and website visitors

  • Business contact details provided through the contact or demo forms, by e-mail or during business exchanges.
  • Billing data and business relationship follow-up data.
  • Cookies required for the website and the Solution to work (see section 11).


4. Purposes and legal bases

  • Providing the Solution, managing accounts and providing support: performance of the contract.
  • Calculating the metrics on behalf of the customer: performance of the contract, on the customer’s instructions.
  • Ensuring the security of the Solution and preventing fraud: legitimate interest.
  • Invoicing and accounting: legal obligation.
  • Answering contact requests and maintaining the business relationship with professionals: legitimate interest.
  • Sending information about FAP to business contacts: legitimate interest, with the right to object at any time.


5. Alice, the AI analysis assistant

Alice writes analyses based on the data of the Solution’s charts. The processing works as follows:

  • Only the data needed to analyse the chart are sent to the large language model (LLM) provider: metric values and trends, workflow step names, sprint names, anonymised ticket identifiers, the user’s language and, if the user enters one, an optional context.
  • Ticket titles and descriptions, and the names and e-mail addresses of people, are not sent to the LLM provider. Users must not enter personal or confidential data in the optional context.
  • The customer chooses the LLM provider and the geographical processing zone (Europe or USA). The customer can disable Alice at any time.
  • No data is used to train models, neither by Agile4Me nor by the LLM providers, under their commercial API terms.
  • The Solution keeps the three most recent analyses for each chart type of a project. Older analyses are deleted automatically.
  • Alice makes no automated decision within the meaning of Article 22 of the GDPR. Its analyses cover teams and processes, not individuals.


6. Hosting

  • Jira Cloud add-on: Google Cloud Platform, europe-west1 region (Belgium). The add-on’s data are stored on this backend operated by Agile4Me, outside Atlassian’s infrastructure.
  • SaaS Solution: Scaleway, in France.
  • On-premise Solution: the customer’s infrastructure.
  • Website flowanalyticspro.com: OVH, in France.

Backups are stored in Europe. The Solution is administered and supported by Agile4Me from France.


7. Recipients and processors

The data are only accessible to authorised Agile4Me staff, within the limits of their duties. Agile4Me uses the following processors:

  • Google Cloud: hosting of the Jira Cloud add-on, in Belgium.
  • Scaleway: hosting of the SaaS Solution, in France.
  • OVH: hosting of the website, in France.
  • LLM provider chosen by the customer (Mistral AI, OpenAI or Google Vertex AI, which also provides Anthropic models): generation of Alice’s analyses, within the limits described in section 5.
  • Stripe: card payments for subscriptions that are not purchased through the Atlassian Marketplace.
  • E-mail delivery provider: service messages of the SaaS Solution.

For the Jira Cloud add-on, Atlassian provides the Jira platform, user authentication and, through the Atlassian Marketplace, the billing of the add-on. Atlassian processes these data under its own privacy policy.

Agile4Me does not sell or rent any personal data. Data may be disclosed to administrative or judicial authorities when required by law.


8. Transfers outside the European Union

The personal data processed by the Solution are hosted in the European Union. Alice does not send the personal data listed in section 5 to the LLM provider, including when the customer chooses the USA zone. Should a transfer of personal data outside the European Union take place, it would be covered by an adequacy decision of the European Commission or by appropriate safeguards, in particular the Commission’s standard contractual clauses (Article 46 of the GDPR).


9. Retention periods

9.1 During the subscription

  • Customer data and metrics: for the whole subscription term.
  • Alice analyses: the three most recent analyses for each chart type of a project.
  • User accounts: for the subscription term.
  • Backups: daily backups, the last 7 being kept, then overwritten.
  • Technical logs: 30 days.


9.2 After uninstallation of the Jira Cloud add-on

When the add-on is uninstalled from a Jira site, the following schedule applies:

  • Day 0: Agile4Me receives the uninstallation event and marks the site’s data for deletion. The add-on stops accessing Jira.
  • Until deletion: the data are kept so that the customer can recover them by reinstalling the add-on. The customer can ask for earlier deletion at contact@agile4me.com.
  • Within 60 days of uninstallation: an automated daily job permanently deletes the site’s data: imported Jira data, projects, programmes, metrics, Alice analyses, user accounts attached only to that site and installation settings.
  • Within 7 further days: the deleted data disappear from the backups, as they are overwritten.
  • Technical logs are deleted 30 days after they were created.

All the data of an uninstalled site are therefore deleted within 67 days of uninstallation. Billing for Marketplace subscriptions is held by Atlassian.


9.3 Other data

  • For the SaaS Solution: customer data, metrics, analyses and accounts are deleted within 60 days after the end of the contract, then disappear from the backups within a further 7 days.
  • Billing data: 10 years, in accordance with the French Commercial Code.
  • Customer data (business relationship): for the duration of the business relationship, then 3 years for marketing purposes.
  • Prospect data: 3 years from the last contact.
  • Requests to exercise rights: 3 years from the request.


10. Security

The security of the infrastructure and of the hosted data is ensured by the Solution’s hosting providers, Google Cloud and Scaleway, which are certified in particular ISO 27001. Agile4Me implements the following measures at the level of the Solution: encryption in transit (TLS), encryption at rest by the hosting provider, password hashing, multi-factor authentication for administration accounts, access limited to authorised persons, secrets stored outside the code, vulnerability scanning and daily backups. People with access to production are bound by a confidentiality obligation.

In the event of a personal data breach, Agile4Me notifies the CNIL within 72 hours when it acts as controller (Article 33 of the GDPR). When it acts as processor, it informs the customer without undue delay so that the customer can meet this deadline.


11. Cookies

The website and the Solution only use cookies required for them to work: session, security and preference cookies. These cookies do not require consent. You can manage them in your browser settings; blocking them may prevent the Solution from working.


12. Your rights

You have the right to access, rectify, erase, restrict and port your data, and to object to their processing, as well as the right to withdraw your consent when the processing is based on it, and to give instructions on what happens to your data after your death.

To exercise these rights, write to contact@agile4me.com. You will receive an answer within one month, which may be extended by two months for complex requests.

For data from the customer’s tools, for which Agile4Me acts as processor, please send your request to your employer or to the customer concerned. Agile4Me will forward any request received to the customer and help it to answer.

You may lodge a complaint with the CNIL (French data protection authority): 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, www.cnil.fr.


13. Changes to this policy

Agile4Me may change this policy, in particular when the Solution or the regulations change. The date of the last update appears at the top of the document. Customers are informed of any substantial change, and a notice is published on flowanalyticspro.com.

This policy is drawn up in French and in English. In the event of any discrepancy, the French version prevails.