---
language: "en"
---
# Yogi Calculations - Formulas and Variables for Confluence (Cloud)
## Introduction
**Yogi Calculations - Formulas and Variables** is a powerful Confluence Cloud app that enables users to define **formulas and variables directly within Confluence pages** using a simple macro.
With it, you can perform dynamic calculations --- similar to Excel or Google Sheets --- while keeping everything inside your Confluence documentation.
## **Key Features**
* Insert simple macros directly into your Confluence pages.
* Create simple to powerful formulas and expressionswith operations, (**numbers** , **strings** , **booleans** , and even **nested variables** ) β Want to skip to the syntax ? [Calculation syntax](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/calculation-syntax.md)
* Create and save **variables** to reuse them across your entire content.
* Make sure your calculations are understood by hovering on results.
## Next steps
For more information on macro options and variables, see the following pages:
* [Getting Started](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/getting-started.md)
* [Administration](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/administration.md)
* [Best Practices - Use cases](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/best-practices-use-cases.md)
[Features](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/features.md)
* [Release Notes](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/release-notes.md)
## Need any help?
If you have any questions regarding functionalities, bugs, feature requests, or simply would like to chat, please reach out on the support: .
*** ** * ** ***
---
language: "en"
---
# Administration
[Yogi Calculations - Formulas and Variables for Confluence](https://marketplace.atlassian.com/apps/2481366772/yogi-calculations-formulas-and-variables-for-confluence) application, certified [RUNS ON ATLASSIAN](https://marketplace.atlassian.com/collections/runs-on-atlassian).
## Variables configuration
You can configure variables per page, space or instance.
* To configure variables on the **page**, you can add a simple macro and then save it as a variable.
* To configure variables per space, you need to go into **Space Apps** \> **Yogi Calculations** \> Create Space Variable.
* To configure variables for your whole instance, you need to go into Confluence Administration \> Apps \> Yogi Calculations \> Create Global Variable.
## Permissions
Enlarges the table by opening it in a full screen dialogOpen
| **Action** | **Permissions needed** |
|------------------------------------------------|--------------------------------------------------|
| To render the calculation macro | 'View' space permissions 'Edit' page permissions |
| To create and use calculation macro | 'Edit' space permissions |
| To create/update/delete saved space variables | 'Space admin' permissions |
| To create/update/delete saved global variables | 'Global admin' permissions |
## Frequently Asked Questions
### Can I create Excel-like formulas?
* For now, it is not possible to create formulas based on a table cell content (like Excel or Spreadsheets).
* The calculation syntax is limited to numeric, strings, booleans expressions. If you're interested in more, please let us know on the support:
### Is it possible to have two variables with the same name ?
Note that if two variables have the same name, we'll apply the results using the closest variable (current page \> space \> instance).
* If you have defined a `variable_1` `= 50 ` in your page A and if you have defined a `variable_1` `= 100` as a space variable: if you use `variable_1` in page A, we'll use the value `50`. If you use `variable_1` in a new page, we'll use the value `100`, defined at the space level.
### How many levels of variables can I create ?
* Please note that the calculation are processing variables only up to 5 levels deep. If you have a variable, built using another variable, and so on, more than 5 times, the calculation won't be processed.
---
language: "en"
---
# Best Practices - Use cases
The calculation macro is pretty simple, but it can answer a lot your questions. The goal is to help you build data-driven documentation to help you lead your projects to their goal.
## Use Cases
### Project Budget Tracking
* **Scenario:** You're managing a project and need to track expenses against the budget.
* **Calculation Example:**
* `Total Budget = 25,000 `
* `Expenses = 6,400 + 2,750 + 1,980 `
* `Remaining Budget = Total Budget - Expenses `
* **How Yogi Helps:**
* Store `Total Budget` as a variable and update only the expenses. All budget-related pages, dashboards, and reports update instantly.
### Sprint Velocity \& Forecasting
* **Scenario:** Agile teams want to predict completion time based on past performance.
* **Calculation Example:**
* `Average Velocity = (Sprint1 Points + Sprint2 Points + Sprint3 Points) / 3 `
* `Estimated Sprints to Finish = Remaining Points / Average Velocity `
* **How Yogi Helps:**
Use macros to calculate velocity dynamically, embed results in sprint reports, and reuse variables across project dashboards.
### ROI Calculation for a Marketing Campaign
* **Scenario:** Marketing wants to quickly check campaign profitability.
* **Calculation Example:**
* `ROI (%) = ((Revenue - Campaign Cost) / Campaign Cost) * 100 `
* **How Yogi Helps:**
Enter campaign cost and revenue once, and all ROI references in multiple pages update in real time.
### KPI Dashboard for Operations
* **Scenario:** Operations tracks monthly KPIs like defect rate and on-time delivery.
* **Calculation Example:**
* `Defect Rate (%) = (Defects / Total Units) * 100 `
* `On-Time Rate (%) = (On-Time Deliveries / Total Deliveries) * 100 `
| **Metric** | **Target** | **Actual** | **Variance** |
|-------------------------|------------|------------|-------------------|
| Revenue | 1 200 000 | 1 050 000 | = actual - Target |
| Customer Satisfaction | 90% | 87.5% | = actual - Target |
| Bug Resolutime (hrs) | 48 | 52 | = actual - Target |
| Employee Retention Rate | 95% | 94.5% | = actual - Target |
* **How Yogi Helps:**
Use formulas in Confluence tables to display KPIs for each month and automatically roll them up to a yearly summary.
### Resource Utilization in a Team
* **Scenario:** HR or management needs to know workload distribution.
* **Calculation Example:**
* `Utilization (%) = (Hours Worked / Available Hours) * 100 `
* **How Yogi Helps:**
Store `Available Hours` as a variable per role, reuse it across all team reports, and embed results in planning templates.
### Financial Forecasting
* **Scenario:** Finance wants to predict the next quarter's revenue.
* **Calculation Example:**
* `Forecast = Current Quarter Revenue * (1 + Growth Rate) `
* **How Yogi Helps:**
Keep `Growth Rate` as a global variable so adjusting it updates all forecast pages instantly.
## Feel like we're missing some use cases ?
Please feel free to reach out on the support and share your feedback: [support.requirementyogi.com](http://support.requirementyogi.com/).
---
language: "en"
---
# Calculation syntax
Here is the detailed syntax of values that can be used in your calculations and variables.
## Variable expressions
| **Syntax** | **Output** | **Description** | **Examples** |
|-------------------------------------------------------|------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------|
| $variable | any | Fetches a variable. Variable names must contain only letters, numbers, hyphens, and underscores. Variables are searched in the following order: current page -\> current space -\> global scope. | * $customer * $company-name * $Q3_revenue * $totalCost * $SKU123 |
| * $GLOBAL_variable * $SPACE_variable * $PAGE_variable | any | Fetches a variable from a specific scope. Use this when you need to access a variable from a particular scope, overriding the normal scope resolution order. | * $GLOBAL_company-name * $SPACE_project_budget * $PAGE_taxRate |
## String expressions
| **Syntax** | **Output** | **Description** | **Examples** |
|-------------------------------------|------------|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------|
| "text" | string | Defines a string literal. Use backslash to escape quotes within strings. | * "Hello World!" * "Price: $29.99" * "He said \\"Hello\\"" |
| CONCAT(expression, expression, ...) | string | Concatenates multiple expressions into a single string. Non-string values are automatically converted to strings. | * CONCAT("Hello", " World!") * CONCAT("Order #", 1234) * CONCAT("This", "is", "a", "long", "concatenation") * CONCAT("There are ", $days, " remaining days") |
## Numeric expressions
| **Syntax** | **Output** | **Description** | **Examples** |
|----------------------------|------------|------------------------------------------------------------|------------------------------------------------------|
| * integer * decimal number | number | Defines a numeric literal (integer or decimal). | * 42 * 3.14159 * 1000.50 * -25 |
| number + number | number | Adds two numbers. | * 100 + 25 * 15.99 + $price * $subtotal + 5 |
| number - number | number | Subtracts a number from another. | * 1000 - 250 * 365 - $days_used * $total - $discount |
| number \* number | number | Multiplies two numbers. | * 5 \* 10 * 32 \* $unit_price * $hours \* 40 |
| number / number | number | Divides a number by another. | * 100 / 4 * 15 / $num_items * $revenue / 0.8 |
| number % number | number | Returns the remainder of the division between two numbers. | * 10 % 3 * 100 % $count * $minutes % 60 |
## Boolean expressions
| **Syntax** | **Output** | **Description** | **Examples** |
|---------------------------------------------------------|------------|------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
| * false * true | boolean | Defines a boolean literal. | * false * true |
| * NOT boolean * ! boolean | boolean | Applies a logical NOT to a boolean expression. | * NOT false * !true * NOT $is_complete * !$is_delivered |
| * boolean AND boolean * boolean \&\& boolean | boolean | Applies a logical AND between two boolean expressions. | * true AND false * false \&\& true * false AND $is_active * $is_verified AND true |
| * boolean OR boolean * boolean \|\| boolean | boolean | Applies a logical OR between two boolean expressions. | * true OR false * false \|\| true * false OR $is_manager * $is_admin OR true |
| * expression = expression * expression == expression | boolean | Indicates whether two expressions are equal. | * 100 = 100 * 12.5 == "John" * $is_delivered = false * 1000 = $price |
| * expression != expression * expression \<\> expression | boolean | Indicates whether two expressions are different. | * 42 != 43 * 1.66 \<\> "Jane" * $is_verified != false * 36 != $quantity |
| number \> number | boolean | Indicates whether a numeric expression is greater than another. | * 100 \> 50 * 3.14 \> 3 * $temperature \> 32 * 2500 \> $balance |
| number \>= number | boolean | Indicates whether a numeric expression is greater or equal to another. | * 21 \>= 21 * 75.25 \>= 10 * $score \>= 90 * 100 \>= $minimum_threshold |
| number \< number | boolean | Indicates whether a numeric expression is less than another. | * 25 \< 82 * 0.5 \< 1 * $inventory \< 100 * 500 \< $withdrawal_amount |
| number \<= number | boolean | Indicates whether a numeric expression is less or equal to another. | * 300 \<= 200 * 99.99 \<= 100 * $discount \<= 50 * 30 \<= $wait_time |
---
language: "en"
---
# Create and reuse variables
In [Yogi Calculations - Formulas and Variables for Confluence](https://marketplace.atlassian.com/apps/https://marketplace.atlassian.com/apps/2481366772/yogi-calculations-formulas-and-variables-for-confluence), you create variables to:
* Reuse results of previous calculations,
* Create a dynamic ecosystem depending on other variables, or global standards.
## How to create a variable?
There are 2 ways to create variables:
1. From a calculation macro inside the Confluence page, click on 'Save as a variable' and give it a name. You'll be able to reuse that variable in this page only.
2. From the Space Apps, or the Confluence Administration, to create a specific variable that you'll be able to reuse across one space, or many.
The variable name must contain only letters, numbers, hyphens and underscores (ex: `variable_name`).
### What kind of data is supported inside variables?
Variables can store:
* A **literal value** (e.g., `10`, `"Hello"`, `true`)
* Boolean (e.g., `true` or `false)`
* Numbers \& decimals (e.g. `0`,`1`, `3.14` ...)
* Strings (=Text) (e.g., `"John doe"` ...)
* A **formula** (e.g., `A + B * C`)
* A **reference to another variable** using the **$** prefix, like `$myVariable`.
## How to use a variable in a formula?
The syntax to use a variable is to put a `$` in front of its name (e.g. `$price * $quantity`).
If `price` and `quantity` are defined in the right scope, they'll be evaluated.
## What are the different levels of the variables?
It is possible to set up variables across multiple levels so you can share them through all your ecosystem.
### Global variables
Users with global admin permissions can create global variables in the Yogi Calculations administration.
Those variables will be usable across all spaces.
* **To access:**
1. π Access restricted to global administrators.
2. Go to **Confluence settings** in the top menu.
3. Select **Calculation Yogi**.
4. Create or edit your global variables there.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  |  |  |  |  |
### Space variables
Users with space admin permissions can create space variables in the Space Apps \> Yogi Calculations.
These variables will be accessible for a whole space.
* **To access:**
1. π Access restricted to space administrators.
2. Open the target Confluence space.
3. Go to **Space apps** in the left sidebar.
4. Find **Space apps \> Calculation Yogi**.
5. Create or edit your space variables there.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  |  |  |  |  |
### Page variables
* To access them, you simply need to add a basic calculation and save it as a variable.
* The variable is stored directly **within a page**.
* These variables are **isolated**, only available in that page.
Page variables can be created as documented in [Insert the calculation macro](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/insert-the-calculation-macro.md) .
## Frequently Asked Questions:
### **Does Yogi Calculations support nested variables?**
Yes! A variable's value can reference other variables recursively (within a limit of 5).
### **Can I use the same variable name in different scopes?**
Yes, but the closest scope takes priority:
* A page variable with exactly the same name as a global or space variable will override them
* A space variable with exactly the same name as a global variable will override it.
* A global variable will be replaced by a space variable if they have the same name.
If you want to override that scope and look for a specific variable, you can use a syntax like `$GLOBAL_Variablename`. See: [Calculation syntax \| Variable expressions](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/calculation-syntax.md#Variable-expressions) .
---
language: "en"
---
# Features
The main features of Yogi Calculations - Formulas and Variables is to:
* Insert **calculations** in a Confluence page.
* Perform calculations by creating **formulas** with **variables**.
* **Display conditional content** by defining expressions that adapt to your data.
By combining formulas, expressions, and variables, you can make your Confluence pages smarter, more accurate, and easier to maintain.
For instructions, please follow this documentation:
* [Insert the calculation macro](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/insert-the-calculation-macro.md)
* [Create and reuse variables](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/create-and-reuse-variables.md)
* [Calculation syntax](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/calculation-syntax.md)
---
language: "en"
---
# Getting Started
Looking for a quick way to understand how to insert a Yogi Calculation macro ? Here's how to get started with [Yogi Calculations - Formulas and Variables for Confluence.](https://marketplace.atlassian.com/apps/2481366772/yogi-calculations-formulas-and-variables-for-confluence)
## 1. Insert the Yogi Calculation macro
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| First, anywhere in your page, add the macro using `/calculation` or `/variable` or `/yogi`. |  |
| Then, in the popup, you can define your formula or expression by typing its formula. For details, please checkout out [Calculation syntax](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/calculation-syntax.md). Once done, you can validate and your macro will be inserted in the page. |  |
| You can now see the macro with the result of your processed formula / expression. By hovering the macro, you will have access to the formula to gather details. |  |
## Want to use variables ?
If you want to expand your work and take it to another level, the app also lets you to set up variables. Explore the rest of the documentation to learn more: [Features](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/features.md) .
### Share your feedback
Yogi Status \& Dropdown is all new, so please let us know if you'd like to share your feedback and feature suggestions π .
---
language: "en"
---
# Insert the calculation macro
## Insert your first calculation macro
Any user who has edit permissions on the space will be able to add and edit the macro.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| First, anywhere in your page, add the macro using `/calculation` or `/variable` or `/yogi`. |  |
| Then, in the popup, you can define your formula or expression by typing its formula. For details, please checkout out [Calculation syntax](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/calculation-syntax.md). Once done, you can validate and your macro will be inserted in the page. |  |
| You can now see the macro with the result of your processed formula / expression. By hovering the macro, you will have access to the formula to gather details. |  |
## Save a calculation as a variable
To improve consistency between your data, you can also save your previously inserted macro to reuse it later. If you want to see more details about variables, find the documentation: [Variables](https://docs.requirementyogi.com/yogi-calculations-formulas-variables/create-and-reuse-variables.md) .
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Once you've added your calculation in the page, you can activate the `Save as variable` option allowing you to name your variable. *Note that if two variables have the same name, we'll apply the results using the closest variable (current page \> space \> instance).* |   |
| The rendering is the same as a unnamed macro. |  |
| However whenever you insert a new macro, you can reuse the saved calculation as a variable. * The syntax is to prefix its name with a `$`. |  |
| And just like that, you can build dynamic Confluence pages based on calculated data. *Limitations:* *Please note that the calculation are processing variables only up to 5 levels deep. So If you have a variable, built using another variable, and so on, more than 5 times, the calculation won't be processed.* |   |
## Can the macro be exported ?
With Confluence's native feature to export pages to Word or PDF, you can download your pages and Yogi Calculations - Formulas and Variables for Confluence macros will be downloaded as well.
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  |  |
---
language: "en"
---
# Release Notes
## New app on the Atlassian Marketplace π
2025-08-19 Version 2.3.0
We have just released the first version for the [Yogi Calculations - Formulas and Variables for Confluence.](https://marketplace.atlassian.com/apps/2481366772/yogi-calculations-formulas-and-variables-for-confluence)
Please find out how to get started with [our documentation](https://docs.requirementyogi.com/yogi-status-dropdown/getting-started), and don't hesitate to read the [best practices](https://docs.requirementyogi.com/yogi-status-dropdown/best-practices) for use case examples.
We value your feedback, so please reach out to us and let us know if you have any suggestions to improve the app π .
---
language: "en"
---
# RY's guide for Atlassian Partners
## **Welcome Partners π**
This space is for our partners, so they can get **quick and valuable information on our apps**. Our goal is for you to understand our products' strengths and weaknesses, and make sure you are properly trained to sell and teach our apps.
We've kept the steps quite simple, to ensure that our partners can deal with many apps.
## Follow these steps to become a better partner
* [Step 1 -- Learn the list of our apps](https://docs.requirementyogi.com/partners/our-apps.md)
* [Step 2 -- Use our comparative PDF document to match your customer's expectations with our feature list](https://docs.requirementyogi.com/partners/features-document.md)
* [Step 3 -- Learn our features to succeed the deployment of Requirement Yogi for your customers](https://docs.requirementyogi.com/partners/training-and-tutorials.md)
* [Step 4 -- Subscribe to emails as a Partner to stay on top of evolutions](https://www.requirementyogi.com/partners-mailing-list/)
* [Frequently Asked Questions](https://docs.requirementyogi.com/partners/FAQ.md)
## π’ Stay tuned to our news
Wanna be aware of new features, or training? Please head to to register yourself and choose your hosting and interests.
---
language: "en"
---
# Frequently Asked Questions
## Do you have a partner discount program?
* We are not part of Atlassian's partner program that will automatically give you a discount. But, we still give discounts to partners when they contact us via the[support](https://requirementyogi.atlassian.net/servicedesk/customer/portal/1/group/3). Don't worry, the decision making person will answer you directly.
* Why? Because it allows us to connect π . We'd like Partners to give us feedback on our strategic positioning ; Please tell us what are our smooth or friction points, please tell us how we compare with competitors and what arguments finally close sales.
## How can I stay tuned to your news?
* We have a mailing list where we will inform you about all the new features and important changes. Subscribe here:
## What is the best way to contact you?
* For bugs, feature suggestions, billing questions, you can contact us on the [support](https://requirementyogi.atlassian.net/servicedesk/customer/portals). We usually respond quickly and you'll discuss with a person that has quick access to all information to help you the best way possible.
## Do you offer special training for partners?
* We do not, you can find all training available on our [youtube channel](https://www.youtube.com/@requirement-yogi), or in the [documentation](https://docs.requirementyogi.com/). If you need a specific demo, we are always available for a call, you can book it here:
---
language: "en"
---
# Step 2 - Overall features document
This is a short PDF document that lists all Requirement Yogi features, so you can perform a feature comparison with competitors and check it fulfills your customers usecases.
* [Requirement Yogi for Cloud: Overall features](https://docs.requirementyogi.com/partners/ry-cloud-features.md)
In Requirement Yogi Cloud, you can manage requirements in multiple formats, create custom properties, and deal with project tracking. Please find all our features in this doc, as well as the features we do not have, yet.
* [Requirement Yogi for Data Center: Overall features](https://docs.requirementyogi.com/partners/ry-data-center-features.md)
In Requirement Yogi Data Center, manage requirements, track your project, create baselines, and much more. Please find all our features in this doc, as well as the features we do not have, yet.
---
language: "en"
---
# Step 1 - Our apps
|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  **[Requirement Yogi for Confluence](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence)** A comprehensive solution to manage requirements, specifications, and all kinds of data at the intersection between free text and structured databases. The strength of this app is to let users write documents and annotate them to use the data in reports, with various variants, baselines, traceability matrices, links with Jira, etc. This app is available for **Cloud** and**Data Center.** |  **[Requirement Yogi for Jira](https://marketplace.atlassian.com/apps/1214094/requirement-yogi-requirements-management-for-jira)** This is a complementary app to RY for Confluence that allows you to link requirements to Jira issues and tests. You will then be able to extract this data into RTM's and more. In DC, you can also bulk create Jira issues from requirements. This app is available for **Cloud** and **Data Center**. |
|  **[Yogi Status \& Dropdown for Confluence](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview)** Add customizable dropdowns and status fields to your Confluence pages to track progress, priorities, approval statuses and more. This app is available for **Cloud.** |  **[Yogi Calculations - Formulas \& Variables for Confluence](https://marketplace.atlassian.com/apps/2481366772/yogi-calculations-formulas-and-variables-for-confluence?hosting=cloud&tab=overview)** Insert calculations, formulas, and variables in Confluence pages and measure estimates, project progress and more This app is available for **Cloud.** |
|  **[RY Testing \& Compliance](https://marketplace.atlassian.com/apps/1217990/ry-testing-and-compliance)** Write test plans and tests in Confluence, in free text format. This app can be used independently or together with Requirement Yogi. You can create test sessions from your requirements, and quickly access their results from the popup and RTM. This app is only available for **Data Center.** |  **[PSEA Export add-on](https://marketplace.atlassian.com/apps/1215546/psea-export-add-on?hosting=datacenter&tab=overview)** This app is a technical module to export requirements to Excel on Data Center. This app is available for **Data Center**, and you do not need it for Excel exports on Cloud. |
|  **[**ReqIF extension**](https://marketplace.atlassian.com/apps/1222948/reqif-extension-for-requirement-yogi)** Import ReqIF files into Requirement Yogi for Confluence. This is very useful to any users who work with other requirement management tools and want to link their ReqIF requirements to their Confluence Requirements. This is only available for **Server** DEPRECATED . |  **[RY - Comala Integration](https://marketplace.atlassian.com/apps/1228574/requirement-yogi-comala-integration?hosting=datacenter&tab=overview)** Are you familiar with [Comala](https://marketplace.atlassian.com/apps/142/comala-document-management?hosting=cloud&tab=overview)? Well if you use this app for workflows and document reviewal, you might want to use it to approve your requirements as well. This integration allows you to see the Comala workflow on each requirements, in your RTMs. This app is only available for **Data Center.** |
---
language: "en"
---
# Requirement Yogi for Cloud: Overall features
Please note that this document dates from December 2025 and may be outdated.
|-------------------------------------------------|----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
| **Theme** | ****Cloud Features**** | **Reference** | **Fill for your client** |
| **Manage requirements in Documents - Navigate** | β
Easy navigation between requirements | [++In Tables++](https://docs.requirementyogi.com/cloud/writing-requirements) / [++ISO Documents++](https://docs.requirementyogi.com/cloud/linear-documents)++/++ [++Detail \& Treeview++](https://docs.requirementyogi.com/cloud/writing-requirements#Writingrequirements-Whatyourrequirementlookslike) | ... |
| **Manage requirements in Documents - Navigate** | β
Search | [++Search Syntax++](https://docs.requirementyogi.com/cloud/requirements-search) | ... |
| **Manage requirements in Documents - Navigate** | β
Requirement dependencies | [++Tutorial++](https://www.youtube.com/watch?v=891Q3OpCiLA&t=133s) | ... |
| **Custom Properties on requirements** | β
Properties | [++Tutorial++](https://www.youtube.com/watch?v=891Q3OpCiLA) | ... |
| **Custom Properties on requirements** | β
External Properties | [++External properties++](https://docs.requirementyogi.com/cloud/external-properties) | ... |
| **Project Tracking** | β
Link with Jira items | [++Requirement panel in Jira++](https://docs.requirementyogi.com/cloud/requirement-yogi-for-jira) | ... |
| **Project Tracking** | β
Requirement Traceability | [++Traceability Matrix++](https://docs.requirementyogi.com/cloud/traceability-matrix) | ... |
| **Project Tracking** | β
Calculations | [++Calculations++](https://docs.requirementyogi.com/cloud/calculations) | ... |
| **Versioning** | β
Variants \& Branches | [++Variants++](https://docs.requirementyogi.com/cloud/variants) / [++Modification Matrix++](https://docs.requirementyogi.com/cloud/modification-matrix) | ... |
| **Versioning** | β
Baselines | [*What is the difference with Variants?*](https://docs.requirementyogi.com/cloud/difference-variants-and-baselines.md) | ... |
| **Integrations** | β
Export to Excel | [++Exports++](https://docs.requirementyogi.com/cloud/traceability-matrix#Traceabilitymatrix-Exports) / [++RY Report++](https://docs.requirementyogi.com/cloud/report-macro) | ... |
| **Integrations** | β
Import from Word/Excel/PDF | [++Native in Confluence++](https://support.atlassian.com/confluence-cloud/docs/import-content-into-confluence-cloud/)++/++ Copy \& Paste | ... |
| **Integrations** | β
Jira | [++Requirement panel in Jira++](https://docs.requirementyogi.com/cloud/requirement-yogi-for-jira) | ... |
| **Integrations** | β
Rest API | [BETA is released](https://docs.requirementyogi.com/cloud/rest-apis) | ... |
| **Integrations** | β ReqIF | | ... |
| **Testing** | β Native | | ... |
| **Testing** | π‘ Xray | You can already integrate with it, but is a work in progress | ... |
| **Testing** | β
Zephyr Scale | [Zephyr Scale integration](https://docs.requirementyogi.com/cloud/zephyr-scale-for-jira) | |
| **SOC2 / Quality \& Compliance** | β
Validation Rules and Conformity | [++Requirement Types++](https://docs.requirementyogi.com/cloud/requirement-types.md) | ... |
| **SOC2 / Quality \& Compliance** | β
History | [Track history modifications \& restore](https://docs.requirementyogi.com/cloud/changes-history-and-restoration) | ... |
| **SOC2 / Quality \& Compliance** | β Workflows / Approvals / Automations | Maybe... Very long term | ... |
| **SOC2 / Quality \& Compliance** | β
Data Residency | [++CAIQ++](https://docs.requirementyogi.com/legal/caiq-lite-requirement-yogi-cloud) | ... |
|--------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| ****Security \& Privacy**** |||
| **GDPR / Data Privacy** | [++Privacy Policy++](https://docs.requirementyogi.com/legal/privacy-policy) | ... |
| **Cloud fortified \& Bug Bounty Program,** | [++Certification++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=overview#:~:text=Certification-,CLOUD%20FORTIFIED,-This%20app%20offers) | ... |
|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| ****Vendor**** |||
| **Response time/ Availability** | [++24 hour support response time++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=reviews) | ... |
| **Reviews** | [++Marketplace++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=reviews) | ... |
| **Time on the Marketplace** | 10+ years | ... |
| **Newsletter** | [++For users++](https://www.requirementyogi.com/cloud-mailing-list/) / [++For partners++](https://www.requirementyogi.com/partners-mailing-list/) | ... |
|-------------------------------------|---------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| ****Pricing**** ||||
| **Requirement Yogi for Confluence** | **Main app,** can be used as a standalone | [++Paid++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=pricing) ($126 pm / 100 users) | ... |
| **Requirement Yogi for Jira** | Integration. Cannot be used as a standalone | [++Paid++](https://marketplace.atlassian.com/apps/1214094/requirement-yogi-requirements-management-for-jira?hosting=cloud&tab=pricing) ($56 pm / 100 users) | ... |
## π’ Stay tuned to new features
Wanna stay aware of our new features? Please head to to register yourself and choose your hosting and interests.
---
language: "en"
---
# Requirement Yogi for Data Center: Overall features
Please note that this document dates from December 2025 and may be outdated.
|---------------------------------------|----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------|
| **Theme** | ****Data Center Features**** | **Reference** | **Fill for your client** |
| **Manage requirements in Documents** | β
Easy navigation between requirements | [++In tables++](https://docs.requirementyogi.com/data-center/the-requirements-yogi-macro) / [++ISO Documents++](https://docs.requirementyogi.com/data-center/word-import) / [++Popup++](https://docs.requirementyogi.com/data-center/the-requirements-yogi-macro#TheRequirementsYogimacro-WherecanIseerequirements?) | ... |
| **Manage requirements in Documents** | β
Search | [++Search Syntax++](https://docs.requirementyogi.com/data-center/search-syntax) | ... |
| **Manage requirements in Documents** | β
Requirement dependencies | [++Dependencies Matrix / Coverage++](https://docs.requirementyogi.com/data-center/dependencies-dependency-matrix-and-coverage) | ... |
| **Custom Properties on requirements** | β
Properties | [++Tutorial++](https://docs.requirementyogi.com/data-center/properties) | ... |
| **Custom Properties on requirements** | β
External Properties | [++Estimates \& External properties++](https://docs.requirementyogi.com/data-center/estimates-and-external-properties) | ... |
| **Project Tracking** | β
Link with Stories | [++Requirement panel in Jira++](https://docs.requirementyogi.com/data-center/jira-links) | ... |
| **Project Tracking** | β
Requirement Traceability | [++Traceability Matrix++](https://docs.requirementyogi.com/data-center/traceability-matrix) | ... |
| **Project Tracking** | β Calculations | [++Available in Cloud++](https://docs.requirementyogi.com/cloud/calculations) | ... |
| **Versioning** | β
Baselines | [++Baselines \& Diff++](https://docs.requirementyogi.com/data-center/baselines-and-versioning) | ... |
| **Versioning** | π‘ Variants \& Branches | [*What is the difference with baselines?*](https://docs.requirementyogi.com/cloud/difference-variants-and-baselines.md) | ... |
| **Integrations** | β
Export to Excel | [++Export Matrix with PSEA++](https://docs.requirementyogi.com/data-center/psea-export-add-on) / [++RY Report++](https://docs.requirementyogi.com/data-center/ry-reports) | ... |
| **Integrations** | β
Import from Word/Excel/PDF | [++Native in Confluence++](https://docs.requirementyogi.com/data-center/word-import) / [++Excel Import++](https://docs.requirementyogi.com/data-center/excel-import)++/++ [++Import External properties++](https://docs.requirementyogi.com/data-center/excel-loop) | ... |
| **Integrations** | β
Jira | [++RY for Jira++](https://docs.requirementyogi.com/data-center/requirement-yogi-for-jira) + [++Jira Bulk Issue Creation++](https://docs.requirementyogi.com/data-center/jira-issues-bulk-creation-from-requirements) | ... |
| **Integrations** | β
Rest API | [++Developer documentation++](https://developer.requirementyogi.com/) | ... |
| **Integrations** | β ReqIF (Available only on Server) | | ... |
| **Integrations** | β
Comala Documents | [++Document approval and reviews++](https://docs.requirementyogi.com/data-center/comala-integration) | ... |
| **Integrations** | β Scroll Version | Only the latest published version is indexed. | |
| **Testing** | β
Native | For simple tests in Confluence. [++Requires an extra addon.++](https://docs.requirementyogi.com/data-center/ry-testing-and-compliance) | ... |
| **Testing** | β
Xray | [++See examples++](https://docs.requirementyogi.com/data-center/xray-integration-with-requirement-yogi) | ... |
| **Testing** | β
Zephyr | [++See examples++](https://docs.requirementyogi.com/data-center/zephyr-integration-with-requirement-yogi) | ... |
| **Testing** | β
Any other testing app | We have an integration with all common fields of Jira, which makes it easy to integrate with testing apps that use Jira to report test results. | ... |
| **SOC2 / Quality \& Compliance** | β
Validations and Requirement types | [++Requirement types++](https://docs.requirementyogi.com/data-center/requirement-types.md) | ... |
| **SOC2 / Quality \& Compliance** | β
Lock Keys | [++Define authorised key patterns++](https://docs.requirementyogi.com/data-center/key-suggestions#KeySuggestions-Usecases) | |
| **SOC2 / Quality \& Compliance** | β
History | For now, you can see **what** has been modified between baselines. We do not manage the **Who** \& **When** yet. You can still use the native Confluence page history feature. | ... |
| **SOC2 / Quality \& Compliance** | β Workflows / Approvals / Automations | Maybe... Very long term | ... |
|-------------------------|-----------------------------------------------------------------------------|-----|
| ****Security \& Privacy**** |||
| **GDPR / Data Privacy** | [++Privacy Policy++](https://docs.requirementyogi.com/legal/privacy-policy) | ... |
|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| ****Vendor**** |||
| **Response time/ Availability** | 24 hour support response time | ... |
| **Reviews** | [++Marketplace++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=datacenter&tab=reviews) | ... |
| **Time on the Marketplace** | 10+ years | ... |
| **Newsletter** | [++For users++](https://www.requirementyogi.com/data-center-mailing-list/) / [++For partners++](https://www.requirementyogi.com/partners-mailing-list/) | ... |
|-------------------------------------|------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----|
| ****Pricing**** ||||
| **Requirement Yogi for Confluence** | **Main app,** can be used as a standalone | [++Paid++](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=datacenter&tab=pricing) ($7,992 pa / 500 users) | ... |
| **Requirement Yogi for Jira** | Integration. Cannot be used as a standalone | [++Free++](https://marketplace.atlassian.com/apps/1214094/requirement-yogi-requirements-management-for-jira?hosting=datacenter&tab=overview) | ... |
| **RY Testing \& Compliance** | Can be used as a standalone | [++Paid++](https://marketplace.atlassian.com/apps/1217990/ry-testing-and-compliance?hosting=datacenter&tab=pricing) ($1,400 pa / 500 users) | ... |
| **PSEA Export Add-on** | Integration to export your matrices to Excel. Cannot be used as a standalone | [++Free++](https://marketplace.atlassian.com/apps/1215546/psea-export-add-on?hosting=datacenter&tab=overview) | ... |
| **RY Comala Integration** | Integration to work with Comala Documents. Cannot be used as a standalone | [++Free++](https://marketplace.atlassian.com/apps/1228574/requirement-yogi-comala-integration?hosting=datacenter&tab=overview) | ... |
## π’ Stay tuned for our new features
Wanna stay aware of our new releases? Please head to to register yourself and choose your hosting and interests.
---
language: "en"
---
# Step 3 - Training and Tutorials
π Please train your consultants with the following tutorials, so they can better sell and deploy the solution for customers.
Don't have time to go through docs and tutorials? [We can introduce the app to you (personally) in less than 30 minutes with our Open Hours!](https://calendly.com/requirement-yogi/open-hours)
## Requirement Yogi for Cloud
### Tutorial Playlist
[.png?cb=3c85e300ce7d03c31ea8df466b473c01)](https://youtube.com/playlist?list=PLSef8S-KtJMwLDjovOQpNlXv2ijfsmG1R)
### Complete documentation
[](https://docs.requirementyogi.com/cloud/)
## Requirement Yogi for Data Center
### Tutorial playlist
### Complete Documentation
[](https://docs.requirementyogi.com/data-center/)
## π’ Stay tuned
Want to stay aware of our new training? Head to to register yourself and choose your hosting and interests.
---
language: "en"
---
# Trust Center
Welcome to the Requirement Yogi Trust Center!
## Agreements, policies and terms of service
All our terms and policies are grouped in the following page:
[Terms and Policies](https://docs.requirementyogi.com/legal/terms-and-policies.md)
### Security
* [Security Overview](https://docs.requirementyogi.com/legal/security-overview.md)
* [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md)
### Business details
For the identity card of the company, please refer to:
[Requirement Yogi Legal Information](https://docs.requirementyogi.com/legal/requirement-yogi-legal-information.md)
### Getting Support
Our SLA policy is available on this page: [Support times - SLA Statement](https://docs.requirementyogi.com/legal/support-times-sla-statement.md)
[](https://requirementyogi.atlassian.net/servicedesk/customer/portal/1/group/1/create/9)
## Support
The best way to contact us is the [Service Desk portal](https://requirementyogi.atlassian.net/servicedesk/customer/portal/1/group/1/create/9).
---
language: "en"
---
# Acceptable Use Policy
**Last Updated:** February 27, 2026
See also: [Terms of Service](https://docs.requirementyogi.com/legal/terms-of-service.md)
**Acceptable Use Policy**
This Acceptable Use Policy establishes the rules of conduct for any individual accessing the Service. By accessing the Service, you represent that you are at least eighteen years of age and you agree to comply with this Policy.
In this Policy, "**Company** " refers to Requirement Yogi SAS (registered under number 812 048 452 RCS Grasse, headquartered at Les Aqueducs B3, 535 Route des Lucioles, 06560 Valbonne, France), including its affiliates and successors. "**Service**" refers to the suite of software applications provided by the Company. Capitalized terms not otherwise defined in this Policy have the meaning given to them in the Terms of Service.
The Company may update this Acceptable Use Policy from time to time. Your continued use of the Service constitutes your acceptance of the updated document.
## **1. Illegal and harmful activities**
**1.1 Compliance with laws.** You must use the Service strictly in accordance with applicable laws. You must not use the Service to (i) conduct fraudulent activities, (ii) distribute defamatory material, or (iii) promote violence.
**1.2 Harassment and abuse.** You must not use the Service to harass any individual. You must not transmit content that is (i) obscene, (ii) hateful, or (iii) highly offensive.
**1.3 Intellectual property violations.** You must respect the intellectual property rights of others. You must not upload or share content if you lack the necessary rights to do so.
**1.4 Export compliance.** You must not access the Service from a jurisdiction subject to economic sanctions by the European Union or the United States. You represent that you are not listed on any restricted party list maintained by these authorities.
## **2. Security and technical integrity**
**2.1 System security.** You must not compromise the security of the Service. You must refrain from (i) probing the vulnerabilities of the Service, (ii) breaching authentication measures, or (iii) intercepting data not intended for you. However, this section does not prohibit good-faith security testing conducted strictly in accordance with the rules of our official bug bounty program, provided this testing is clearly identified as part of this program.
**2.2 Malicious code.** You must not distribute malicious software through the Service. This prohibition includes (i) viruses, (ii) worms, (iii) trojan horses, (iv) corrupted files, or (v) any other similar software, program, or prompt intended to damage the operation of the Service or another third party.
**2.3 Reverse engineering.** You must not attempt to extract the source code of the Service. You must refrain from (i) reverse engineering the Service, (ii) decompiling the software, or (iii) disassembling the application, except to the extent expressly permitted by mandatory applicable law.
**2.4 Sensitive data.** You must refrain from submitting highly sensitive personal information to the Service. This includes (i) financial account numbers, (ii) payment card industry data subject to PCI-DSS, (iii) protected health information subject to HIPAA or similar applicable health privacy regulations, and (iv) government-issued identification numbers.
**2.5 Account sharing.** You must not share your individual authentication credentials with any other person. You must access the Service using strictly your own designated account.
**2.6 Artificial intelligence.** You must not use the artificial intelligence features of the Service to (i) generate unlawful content, (ii) circumvent copyright protections, (iii) intentionally mislead others regarding the origin of the generated content, or (iv) make automated decisions that produce significant individual, legal, financial, or systemic effects without appropriate human oversight. You acknowledge that outputs generated by AI Features may be (i) inaccurate, (ii) incomplete, (iii) inappropriate, or (iv) similar to outputs generated for other customers.
## **3. Resource usage and abuse**
**3.1 Fair usage.** You must use the Service in a manner that does not unreasonably burden the infrastructure of the Company. You must not engage in (i) unauthorized load testing, (ii) denial-of-service attacks, or (iii) automated scraping of the Service.
**3.2 Circumvention of limits.** You must respect the technical limitations enforced by the Service. You must not bypass mechanisms designed to (i) limit your usage, (ii) restrict your access to specific features, or (iii) enforce billing quotas.
**3.3 Unsolicited communications and impersonation.** You must not use the Service to (i) transmit unsolicited commercial messages, (ii) distribute deceptive content, (iii) conduct phishing or social engineering attacks, or (iv) spoof the identity of the Company or any other individual.
**3.4 Competitive intelligence.** You must not access the Service to (i) build a competitive product, (ii) reverse engineer our feature parity, or (iii) publicly share performance benchmarks without the explicit prior written consent of the Company.
## **4. Third-Party Platforms**
**4.1 Platform compliance.** The Service integrates with various Third-Party Platforms (such as Atlassian). When using the Service within or alongside a Third-Party Platform, you must comply with the terms of service of that specific platform.
**4.2 Disruption of platforms.** You must not use the Service to degrade the performance or stability of any Third-Party Platform.
## **5. Enforcement**
**5.1 Suspension of access.** The Company reserves the right to suspend your access to the Service if you violate this Acceptable Use Policy.
**5.2 Customer responsibility.** The Company may report any violation of this Acceptable Use Policy to the Customer that authorized your access. The Customer retains the ultimate responsibility for your actions under the Terms of Service.
**5.3 Reporting to platforms.** The Company reserves the right to report any severe violation of this Policy to the relevant Third-Party Platform administrators or to law enforcement authorities.
**5.4 Content removal.** The Company acts as a business-to-business service provider and relies on the Customer to manage its users. However, the Company reserves the right to remove or disable access to any content that violates this Policy. The Company will typically coordinate with the Customer to address violations, but may act immediately without prior notice if required by law or to protect the Service.
## **6. Contact Information**
If you have any questions about this Policy, please contact the Company through our support website.
*\[End of Policy\]*
---
language: "en"
---
# Archives
* [Terms of Use (archive)](https://docs.requirementyogi.com/legal/terms-of-use.md)
---
language: "en"
---
# CAIQ Lite βΒ Requirement Yogi Cloud
Our consensus for the Cloud Security Alliance is public to help customers assess our security posture.
We use the Consensus Assessments Initiative Questionnaire Lite (CAIQ-Lite) from the [Cloud Security Alliance](https://cloudsecurityalliance.org/star/caiq-lite/) as a baseline mechanism to express our security posture in real terms and to provide security control transparency.
We've made this publicly available to help customers assess our security posture for their own vendor management initiatives. Please reach out to our security people over at [security@r-yogi.com](mailto:security@r-yogi.com) if you have any queries.
| Section Heading | Control Heading | CAIQ ID | Question Text | Answer | Notes / Comment |
|---------------------------------------------------------------|------------------------------------------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Application \& Interface Security | Application Security | AIS-01.2 | Do you use an automated source code analysis tool to detect security defects in code prior to production? | Yes | We use [dependency-check maven](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/), a Maven plugin which warn about known vulnerabilities in dependencies. We treat those vulnerabilities as top priority. |
| Application \& Interface Security | Application Security | AIS-01.5 | (SaaS only) Do you review your applications for security vulnerabilities and address any issues prior to deployment to production? | Yes | Same as the previous answer. |
| Application \& Interface Security | Customer Access Requirements | AIS-02.1 | Are all identified security, contractual, and regulatory requirements for customer access contractually addressed and remediated prior to granting customers access to data, assets, and information systems? | Yes | We address this in our customer agreement and privacy policy. |
| Application \& Interface Security | Data Integrity | AIS-03.1 | Does your data management policies and procedures require audits to verify data input and output integrity routines? | No | The policies and procedures don't require such audits. However, we regularly perform security audits to check that our software correctly escapes data input and output. |
| Audit Assurance \& Compliance | Independent Audits | AAC-02.1 | Do you allow tenants to view your SOC2/ISO 27001 or similar third-party audit or certification reports? | Yes | We don't have SOC2 or ISO 27001 reports, but we publish our last third-party audit (available on this page: [Security audit (14/07/2022)](https://docs.requirementyogi.com/legal/security-audit-14-07-2022.md)) |
| Audit Assurance \& Compliance | Independent Audits | AAC-02.2 | Do you conduct network penetration tests of your cloud service infrastructure at least annually? | Yes | Same as the previous answer. We perform the test every year, but more than 12 months can happen between two audits, depending on the date of the test. |
| Audit Assurance \& Compliance | Independent Audits | AAC-02.3 | Do you conduct application penetration tests of your cloud infrastructure regularly as prescribed by industry best practices and guidance? | No | "Industry best practices and guidance" is not specific enough to answer this question. |
| Audit Assurance \& Compliance | Information System Regulatory Mapping | AAC-03.1 | Do you have a program in place that includes the ability to monitor changes to the regulatory requirements in relevant jurisdictions, adjust your security program for changes to legal requirements, and ensure compliance with relevant regulatory requirements? | No | |
| Business Continuity Management \& Operational Resilience | Business Continuity Testing | BCR-02.1 | Are business continuity plans subject to testing at planned intervals or upon significant organizational or environmental changes to ensure continuing effectiveness? | No | |
| Business Continuity Management \& Operational Resilience | Policy | BCR-10.1 | Are policies and procedures established and made available for all personnel to adequately support services operations' roles? | Yes | Some policies and procedures are written when necessary. |
| Business Continuity Management \& Operational Resilience | Retention Policy | BCR-11.1 | Do you have technical capabilities to enforce tenant data retention policies? | Yes | |
| Business Continuity Management \& Operational Resilience | Retention Policy | BCR-11.3 | Have you implemented backup or recovery mechanisms to ensure compliance with regulatory, statutory, contractual or business requirements? | Yes | |
| Business Continuity Management \& Operational Resilience | Retention Policy | BCR-11.7 | Do you test your backup or redundancy mechanisms at least annually? | No | |
| Change Control \& Configuration Management | Unauthorized Software Installations | CCC-04.1 | Do you have controls in place to restrict and monitor the installation of unauthorized software onto your systems? | No | "unauthorized" is not specific enough to confirm that we have controls in place (Authorized by whom?). |
| Data Security \& Information Lifecycle Management | E-commerce Transactions | DSI-03.1 | Do you provide standardized (e.g. ISO/IEC) non-proprietary encryption algorithms (3DES, AES, etc.) to tenants in order for them to protect their data if it is required to move through public networks (e.g., the Internet)? | No | We don't have e-commerce transactions. However, all traffic is in HTTPS or SSH when going over the internet. |
| Data Security \& Information Lifecycle Management | E-commerce Transactions | DSI-03.2 | Do you utilize open encryption methodologies any time your infrastructure components need to communicate with each other via public networks (e.g., Internet-based replication of data from one environment to another)? | No | We don't have e-commerce transactions. However, all traffic is in HTTPS or SSH when going over the internet. |
| Data Security \& Information Lifecycle Management | Nonproduction Data | DSI-05.1 | Do you have procedures in place to ensure production data shall not be replicated or used in non-production environments? | Yes | No SSH over the internet is possible for our Cloud instances, so DevOps employees cannot extract data through it. |
| Data Security \& Information Lifecycle Management | Secure Disposal | DSI-07.1 | Do you support the secure deletion (e.g., degaussing/cryptographic wiping) of archived and backed-up data? | No | |
| Data Security \& Information Lifecycle Management | Secure Disposal | DSI-07.2 | Can you provide a published procedure for exiting the service arrangement, including assurance to sanitize all computing resources of tenant data once a customer has exited your environment or has vacated a resource? | No | |
| Datacenter Security | Asset Management | DCS-01.2 | Do you maintain a complete inventory of all of your critical assets located at all sites/ or geographical locations and their assigned ownership? | No | We don't manage a data center. We use cloud services (Amazon AWS and Digital Ocean). |
| Datacenter Security | Controlled Access Points | DCS-02.1 | Are physical security perimeters (e.g., fences, walls, barriers, guards, gates, electronic surveillance, physical authentication mechanisms, reception desks, and security patrols) implemented for all areas housing sensitive data and information systems? | No | We don't manage a data center. We use cloud services (Amazon AWS and Digital Ocean). |
| Datacenter Security | User Access | DCS-09.1 | Do you restrict physical access to information assets and functions by users and support personnel? | No | We don't manage a data center. We use cloud services (Amazon AWS and Digital Ocean). |
| Encryption \& Key Management | Key Generation | EKM-02.1 | Do you have a capability to allow creation of unique encryption keys per tenant? | No | |
| Encryption \& Key Management | Encryption | EKM-03.1 | Do you encrypt tenant data at rest (on disk/storage) within your environment? | Yes | |
| Governance and Risk Management | Baseline Requirements | GRM-01.1 | Do you have documented information security baselines for every component of your infrastructure (e.g., hypervisors, operating systems, routers, DNS servers, etc.)? | No | We don't have hypervisors, DNS servers, etc. since we use cloud services to host customer data (Amazon AWS, Digital Ocean). |
| Governance and Risk Management | Policy | GRM-06.1 | Are your information security policies and procedures made available to all impacted personnel and business partners, authorized by accountable business role/function and supported by the information security management program as per industry best practices (e.g. ISO 27001, SOC 2)? | Yes | |
| Governance and Risk Management | Policy Enforcement | GRM-07.1 | Is a formal disciplinary or sanction policy established for employees who have violated security policies and procedures? | No | |
| Governance and Risk Management | Policy Reviews | GRM-09.1 | Do you notify your tenants when you make material changes to your information security and/or privacy policies? | No | |
| Governance and Risk Management | Policy Reviews | GRM-09.2 | Do you perform, at minimum, annual reviews to your privacy and security policies? | No | |
| Human Resources | Asset Returns | HRS-01.1 | Upon termination of contract or business relationship, are employees and business partners adequately informed of their obligations for returning organizationally-owned assets? | Yes | |
| Human Resources | Background Screening | HRS-02.1 | Pursuant to local laws, regulations, ethics, and contractual constraints, are all employment candidates, contractors, and involved third parties subject to background verification? | No | |
| Human Resources | Employment Agreements | HRS-03.1 | Do your employment agreements incorporate provisions and/or terms in adherence to established information governance and security policies? | Yes | |
| Human Resources | Employment Termination | HRS-04.1 | Are documented policies, procedures, and guidelines in place to govern change in employment and/or termination? | Yes | |
| Human Resources | Training / Awareness | HRS-09.5 | Are personnel trained and provided with awareness programs at least once a year? | Yes | |
| Identity \& Access Management | Audit Tools Access | IAM-01.1 | Do you restrict, log, and monitor access to your information security management systems (e.g., hypervisors, firewalls, vulnerability scanners, network sniffers, APIs, etc.)? | No | We don't manage any internal network, since we use the cloud (Amazon AWS, Digital Ocean). |
| Identity \& Access Management | Audit Tools Access | IAM-01.2 | Do you monitor and log privileged access (e.g., administrator level) to information security management systems? | No | The company is very small (5 persons to date) and few people have administrator access. |
| Identity \& Access Management | User Access Policy | IAM-02.1 | Do you have controls in place ensuring timely removal of systems access that is no longer required for business purposes? | Yes | We have a procedure. |
| Identity \& Access Management | Policies and Procedures | IAM-04.1 | Do you manage and store the identity of all personnel who have access to the IT infrastructure, including their level of access? | No | |
| Identity \& Access Management | Source Code Access Restriction | IAM-06.1 | Are controls in place to prevent unauthorized access to your application, program, or object source code, and assure it is restricted to authorized personnel only? | Yes | |
| Identity \& Access Management | Source Code Access Restriction | IAM-06.2 | Are controls in place to prevent unauthorized access to tenant application, program, or object source code, and assure it is restricted to authorized personnel only? | Yes | |
| Identity \& Access Management | User Access Restriction / Authorization | IAM-08.1 | Do you document how you grant, approve and enforce access restrictions to tenant/customer credentials following the rules of least privilege? | No | |
| Identity \& Access Management | User Access Reviews | IAM-10.1 | Do you require a periodical authorization and validation (e.g. at least annually) of the entitlements for all system users and administrators (exclusive of users maintained by your tenants), based on the rule of least privilege, by business leadership or other accountable business role or function? | No | |
| Identity \& Access Management | User Access Revocation | IAM-11.1 | Is timely deprovisioning, revocation, or modification of user access to the organizations systems, information assets, and data implemented upon any change in status of employees, contractors, customers, business partners, or involved third parties? | Yes | |
| Infrastructure \& Virtualization Security | Audit Logging / Intrusion Detection | IVS-01.1 | Are file integrity (host) and network intrusion detection (IDS) tools implemented to help facilitate timely detection, investigation by root cause analysis, and response to incidents? | No | |
| Infrastructure \& Virtualization Security | Audit Logging / Intrusion Detection | IVS-01.2 | Is physical and logical user access to audit logs restricted to authorized personnel? | No | Since we are a very small company (5 persons to date), the authorized personnel would include the same people who have access to these systems. |
| Infrastructure \& Virtualization Security | Audit Logging / Intrusion Detection | IVS-01.5 | Are audit logs reviewed on a regular basis for security events (e.g., with automated tools)? | No | |
| Infrastructure \& Virtualization Security | Clock Synchronization | IVS-03.1 | Do you use a synchronized time-service protocol (e.g., NTP) to ensure all systems have a common time reference? | Yes | |
| Infrastructure \& Virtualization Security | OS Hardening and Base Controls | IVS-07.1 | Are operating systems hardened to provide only the necessary ports, protocols, and services to meet business needs using technical controls (e.g., antivirus, file integrity monitoring, and logging) as part of their baseline build standard or template? | No | |
| Infrastructure \& Virtualization Security | Production / Non-Production Environments | IVS-08.1 | For your SaaS or PaaS offering, do you provide tenants with separate environments for production and test processes? | No | |
| Infrastructure \& Virtualization Security | Production / Non-Production Environments | IVS-08.3 | Do you logically and physically segregate production and non-production environments? | No | Production and non-production envrionments are managed in separate AWS accounts, which is a logical separation but not a physical separation (same datacenter). |
| Infrastructure \& Virtualization Security | Segmentation | IVS-09.1 | Are system and network environments protected by a firewall or virtual firewall to ensure business and customer security requirements? | Yes | |
| Infrastructure \& Virtualization Security | VMM Security - Hypervisor Hardening | IVS-11.1 | Do you restrict personnel access to all hypervisor management functions or administrative consoles for systems hosting virtualized systems based on the principle of least privilege and supported through technical controls (e.g., two-factor authentication, audit trails, IP address filtering, firewalls and TLS-encapsulated communications to the administrative consoles)? | Yes | We restrict those functions, but only through part of those technical controls such as two-factor authentication. For example, we don't have IP address filtering for the access to the AWS console (AWS doesn't provide this feature, to our knowledge). |
| Infrastructure \& Virtualization Security | Wireless Security | IVS-12.1 | Are policies and procedures established and mechanisms configured and implemented to protect the wireless network environment perimeter and to restrict unauthorized wireless traffic? | No | It is assumed that "wireless" refers to the employee network, and employees can work outside of the office, therefore the answer can't be positive. |
| Infrastructure \& Virtualization Security | Wireless Security | IVS-12.2 | Are policies and procedures established and mechanisms implemented to ensure wireless security settings are enabled with strong encryption for authentication and transmission, replacing vendor default settings (e.g., encryption keys, passwords, SNMP community strings)? | No | It is assumed that "wireless" refers to the employee network, and employees can work outside of the office, therefore the answer can't be positive. |
| Infrastructure \& Virtualization Security | Wireless Security | IVS-12.3 | Are policies and procedures established and mechanisms implemented to protect wireless network environments and detect the presence of unauthorized (rogue) network devices for a timely disconnect from the network? | No | It is assumed that "wireless" refers to the employee network, and employees can work outside of the office, therefore the answer can't be positive. |
| Interoperability \& Portability | APIs | IPY-01.1 | Do you publish a list of all APIs available in the service and indicate which are standard and which are customized? | No | |
| Mobile Security | Approved Applications | MOS-03.1 | Do you have a policy enforcement capability (e.g., XACML) to ensure that only approved applications and those from approved application stores can be loaded onto a mobile device? | No | We don't have mobile devices. |
| Security Incident Management, E-Discovery, \& Cloud Forensics | Incident Management | SEF-02.1 | Do you have a documented security incident response plan? | Yes | See [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md). |
| Security Incident Management, E-Discovery, \& Cloud Forensics | Incident Management | SEF-02.4 | Have you tested your security incident response plans in the last year? | No | |
| Security Incident Management, E-Discovery, \& Cloud Forensics | Incident Reporting | SEF-03.1 | Are workforce personnel and external business relationships adequately informed of their responsibility, and, if required, consent and/or contractually required to report all information security events in a timely manner? | No | |
| Security Incident Management, E-Discovery, \& Cloud Forensics | Incident Reporting | SEF-03.2 | Do you have predefined communication channels for workforce personnel and external business partners to report incidents in a timely manner adhering to applicable legal, statutory, or regulatory compliance obligations? | No | |
| Security Incident Management, E-Discovery, \& Cloud Forensics | Incident Response Legal Preparation | SEF-04.4 | Do you enforce and attest to tenant data separation when producing data in response to legal subpoenas? | No | We haven't had the experience of a legal subpoena, but if it happens, we are able to identify tenants in the database and only extract tenant-related information. |
| Supply Chain Management, Transparency, and Accountability | Incident Reporting | STA-02.1 | Do you make security incident information available to all affected customers and providers periodically through electronic methods (e.g., portals)? | Yes | |
| Supply Chain Management, Transparency, and Accountability | Network / Infrastructure Services | STA-03.1 | Do you collect capacity and use data for all relevant components of your cloud service offering? | No | |
| Supply Chain Management, Transparency, and Accountability | Third Party Agreements | STA-05.4 | Do third-party agreements include provision for the security and protection of information and assets? | Yes | |
| Supply Chain Management, Transparency, and Accountability | Third Party Agreements | STA-05.5 | Do you have the capability to recover data for a specific customer in the case of a failure or data loss? | No | |
| Supply Chain Management, Transparency, and Accountability | Supply Chain Metrics | STA-07.4 | Do you provide tenants with ongoing visibility and reporting of your operational Service Level Agreement (SLA) performance? | No | |
| Supply Chain Management, Transparency, and Accountability | Third Party Audits | STA-09.1 | Do you mandate annual information security reviews and audits of your third party providers to ensure that all agreed upon security requirements are met? | No | |
| Threat and Vulnerability Management | Antivirus / Malicious Software | TVM-01.1 | Do you have anti-malware programs that support or connect to your cloud service offerings installed on all of your IT infrastructure network and systems components? | No | |
| Threat and Vulnerability Management | Vulnerability / Patch Management | TVM-02.5 | Do you have a capability to patch vulnerabilities across all of your computing devices, applications, and systems? | No | |
| Threat and Vulnerability Management | Mobile Code | TVM-03.1 | Is mobile code authorized before its installation and use, and the code configuration checked, to ensure that the authorized mobile code operates according to a clearly defined security policy? | Not Applicable | We don't issue employees mobile phones. |
---
language: "en"
---
# EULA
**Last Updated:** June 15, 2026
These terms apply to all our Data Center and downloadable products. See also:
* [Terms of Service](https://docs.requirementyogi.com/legal/terms-of-service.md) for our Cloud products.
* [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md)
* [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md)
* [Acceptable Use Policy](https://docs.requirementyogi.com/legal/acceptable-use-policy.md)
These terms (the "**Agreement** ") are entered into by (i) Requirement Yogi SASU, a French simplified joint-stock company registered under number 812 048 452 RCS Grasse, headquartered at Les Aqueducs B3, 535 Route des Lucioles, 06560 Valbonne, France (the "**Company** "); and (ii) the entity accepting these terms (the "**Customer** "). The Company and the Customer are each referred to as a "**Party** " and collectively as the "**Parties**".
By (i) checking a box indicating acceptance, (ii) executing an order document that references this Agreement, (iii) installing the Software, (iv) upgrading to a new Feature Release of the Software, or (v) renewing an existing subscription or maintenance period from the current date onward, Customer agrees to be bound by this Agreement. This Agreement supersedes and replaces any prior end-user license agreements regarding the Software. The individual accepting this Agreement represents that they have the authority to bind Customer.
Major Version means a version of the software whose second number is incremented, representing Y in the format "X.Y.Z".
**Business use only.** Customer represents that it is acquiring the Software for its own commercial or industrial purposes. Customer represents that it is not a consumer as this term is generally defined under French and EU regulations.
## **1. The software**
**1.1 Scope of the software.** The Company provides downloadable software applications dedicated to requirement management, along with related plugins, scripts, and ancillary tools (collectively, the "Software").
**1.2 Excluded products.** This Agreement applies exclusively to the Company's downloadable and on-premise software products. It does not apply to any cloud-based or hosted services provided by the Company, which are governed by a separate Terms of Service.
**1.3 Excluded open-source tools.** This Agreement does not apply to any scripts or tools explicitly published and distributed by the Company under an open-source license. Such tools are governed strictly by the terms of their respective open-source licenses.
**1.4 Third-party open-source libraries.** The Software may contain embedded third-party components distributed under open-source licenses. Customer acknowledges that (i) these components are governed by their respective licenses, (ii) they are subject to their own lifecycles, and (iii) the Company's warranties do not extend beyond the scope permitted by such third-party licenses. The Company uses commercially reasonable efforts to avoid incorporating any third-party component governed by a copyleft license (such as the GNU General Public License) that would require the Company to disclose or distribute the proprietary source code of the Software. If such a component is inadvertently included, the Company will promptly replace it with a functionally equivalent component under a permissive license. Customer agrees that this replacement constitutes Customer's sole and exclusive remedy regarding the inadvertent inclusion of such components.
## **2. License grant and restrictions**
**2.1 License grant.** Subject to Customer's continuous compliance with this Agreement and payment of applicable fees, the Company grants Customer a limited, non-exclusive, non-transferable, and worldwide right to install and use the Software during the applicable Subscription Term.
**2.2 License restrictions.** Customer must not, and must not permit any third party to: (i) rent, lease, sell, distribute, or sublicense the Software; (ii) provide access to the Software to anyone other than authorized Users; (iii) charge its own customers a distinct fee for the use of the Software; (iv) use the Software to build a competitive product or for any benchmarking purposes; (v) reverse engineer, decompile, or disassemble the Software except to the extent permitted by applicable law; (vi) bypass or breach any security device or usage limits; or (vii) remove or obscure any proprietary notices in the Software.
**2.3 License verification and enforcement.** The Software contains technical mechanisms designed to verify the legitimacy and validity of the applied license keys. The Company reserves the sole right to determine the validity of a license. If the Company determines that a license is invalid, forged, or misused, the Company may suspend the Software's functionality. In such events, continued use of the Software may require Customer to enter a specific override key provided directly by the Company.
**2.4 Acceptable use policy.** Users accessing the Software or interacting with the Company's support services must comply with the Company's Acceptable Use Policy (the "**AUP**"). Customer is responsible for ensuring its Users adhere to the AUP. The Company reserves the right to suspend support services for any specific User who violates the AUP, notably by engaging in abusive behavior or spamming the support channels.
**2.5 Maximum Subscription Term.** For Software deployed on Atlassian Data Center or Server host products, the Subscription Term ends no later than March 28, 2029. Any portion of a Subscription Term extending beyond March 28, 2029, is void.
## **3. Orders, capacity, and audits**
**3.1 Purchasing channels.** Customer may purchase Orders: (i) directly from the Company, or (ii) through a Reseller. All Orders are governed by this Agreement. If Customer purchases through a Reseller, the billing, payment terms, and refunds are governed entirely by the policies of that Reseller. The Company is not responsible for their billing errors, payment processing, or license provisioning delays.
**3.2 Usage limits.** Customer's access is strictly limited to the capacity limits and user tiers specified in the applicable Order. If Customer's usage exceeds these limits, Customer must purchase an upgraded Order covering the excess usage. Any unauthorized usage beyond the permitted capacity constitutes a material breach of this Agreement.
**3.3 Usage verification.** The Company may request that Customer provides a written certification signed by an authorized representative confirming that Customer's use of the Software complies with the permitted capacity. The Company will make this request no more than once in any 12-month period. If this verification reveals that Customer has exceeded its purchased capacity, Customer will be invoiced for the excess usage at the then-current list price.
## **4. Delivery and customer environment**
**4.1 Electronic delivery.** The Software and associated license keys are delivered electronically. Delivery is deemed complete when the Software or the license key is made available to Customer for download or activation via the applicable purchasing channel.
**4.2 Customer responsibility.** Customer is exclusively responsible for (i) procuring, configuring, and securing the hardware, operating systems, and platforms required to host the Software; (ii) implementing adequate firewall and network security measures; and (iii) maintaining regular backups of all data processed by the Software. The Company bears no liability for any data loss, security breach, or system failure arising from Customer's hosting environment. Customer is responsible for its Users' compliance with this Agreement and the Acceptable Use Policy (AUP). Any breach of this Agreement or the AUP by a User will be deemed a material breach by Customer.
## **5. Maintenance, support, and data privacy**
**5.1 Version support.** The Company provides updates, patches, and security fixes exclusively for the most recent major release of the Software. Customer is responsible for promptly installing updates. The Company will not be liable for any issues or vulnerabilities arising from Customer's use of outdated versions of the Software.
**5.2 Support services.** During the applicable Subscription Term, the Company will use commercially reasonable efforts to provide technical support for the Software. Customer may provide anonymized logs, error reports, and reasonable cooperation to assist the Company in diagnosing issues. However, the Company's ability to resolve support requests is contingent upon Customer providing sufficient information, reproducible instructions and cooperation.
**5.3 Privacy and GDPR roles.** Because the Software is installed within Customer's environment, Customer acts as the sole Data Controller and Data Processor for any business data processed by the Software under the EU General Data Protection Regulation (GDPR). The Company does not host, access, or process such data. Any personal data voluntarily provided by Customer to the Company during support interactions is processed strictly in accordance with the Company's Privacy Policy.
## **6. Warranties and disclaimers**
**6.1 Prior evaluation and updates.** Customer acknowledges that the Platform provides opportunities to evaluate and confirm the capabilities of the Software prior to purchase. Customer represents that it has relied exclusively on its own evaluation to determine whether the Software meets its requirements, and accepts the Software strictly on that basis. Furthermore, Customer acknowledges that the Company may, at its sole discretion, release updates that modify, replace, or deprecate certain features of the Software.
**6.2 Third-party platforms.** The Software is designed to operate within a specific Platform that is controlled by a third party. The Company does not warrant the performance, continued availability, security, or continued compatibility of any Platform. The Company is not liable for any degradation or failure of the Software caused by (i) Customer's failure to maintain a supported version of the Platform, (ii) updates, API changes, deprecations, or bugs issued by the Platform provider, or (iii) outages or end-of-life declarations of the Platform. Incompatibility resulting from Platform changes does not constitute a breach of this Agreement, and the Company is under no obligation to modify the Software to restore such compatibility.
**6.3 Disclaimer.** **To the maximum extent permitted by applicable law, the Software, support, and all ancillary tools are provided "AS IS" and "WITH ALL FAULTS." The Company makes no warranties, whether express, implied, statutory, or otherwise, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. The Company does not warrant that the Software will operate uninterrupted, error-free, or be completely immune to unauthorized access or hacking. The Company is under no obligation to correct any bugs, defects, or errors in the Software.**
## **7. Limitation of liability**
**7.1 Exclusion of indirect damages.** To the maximum extent permitted by applicable law, and in accordance with Article 1231-4 of the French Civil Code, neither Party will be liable to the other for any indirect or unforeseeable damages (*dommages indirects et imprΓ©visibles*) arising out of or relating to this Agreement, including (i) loss of revenue or profits, (ii) loss of business opportunity, (iii) loss of use, (iv) loss of data, (v) corruption of data, (vi) reputational harm, or (vii) the cost of procuring substitute software or services. This applies regardless of whether a Party was advised of the possibility of such damages.
**7.2 Mutual liability cap.** In no event will the total, cumulative liability of either Party arising out of or related to this Agreement exceed an amount equal to six months of the subscription fees paid or payable by Customer under the specific Order giving rise to the claim.
**7.3 Excluded claims.** The limitations of liability set forth in Section 7.2 will not apply to: (i) Customer's obligation to pay all fees due under this Agreement; (ii) damages resulting from a Party's gross negligence, willful misconduct, or fraud (faute dolosive ou faute lourde); or (iii) any liability that cannot be excluded or limited under applicable law.
## **8. Intellectual property**
**8.1 Company ownership.** The Company and its licensors exclusively own all right, title, and interest in and to the Software, ancillary tools, algorithms, interfaces, and documentation, including all associated intellectual property rights. No rights are granted to Customer other than the limited right to use the Software as expressly set forth in this Agreement.
**8.2 Customer ownership.** Customer retains all right, title, and interest in and to all data, information, or material processed by Customer using the Software. The Company claims no ownership rights over Customer's data.
**8.3 Feedback.** If Customer or its Users provide the Company with suggestions, enhancement requests, or comments (collectively, "**Feedback**"), the Company may use, modify, and incorporate such Feedback without restriction or obligation.
## **9. Term and termination**
**9.1 Term of agreement.** This Agreement commences upon acceptance and remains in effect until all applicable Orders have expired or been terminated.
**9.2 Termination for cause.** Either Party may terminate this Agreement if the other Party materially breaches this Agreement and fails to cure the breach within thirty days after receiving written notice. The Company may terminate this Agreement immediately upon notice if Customer violates the Acceptable Use Policy, breaches the license restrictions or fails to pay any amounts due.
**9.3 Effect of termination.** Upon expiration or termination of this Agreement: (i) all rights and licenses granted to Customer will immediately cease; (ii) Customer must immediately stop using the Software and securely destroy all copies of the Software and license keys in its possession; and (iii) upon request, Customer will certify in writing that it has complied with these obligations.
**9.4 Survival.** The following provisions will survive any expiration or termination of this Agreement: Sections 3 (Payment obligations), 6 (Warranties and disclaimers), 7 (Limitation of liability), 8 (Intellectual property), 9.3 (Effect of termination), and any other provisions that by their nature should survive.
## **10. General provisions**
**10.1 Updates to the agreement.** The Company may modify this Agreement from time to time. Unless a modification is required by applicable law to take effect immediately, material changes will become effective upon the first day of Customer's next renewal period.
**10.2 Entire agreement.** This Agreement, including any referenced policies and Orders constitutes the entire agreement between the Parties relating to the Software and supersedes all prior or contemporaneous agreements, whether written or oral, relating to such subject matter. For clarity, this Agreement applies strictly to the on-premise Software and does not supersede or alter any separate terms governing Customer's use of the Company's cloud-hosted services. No terms or conditions stated in a Customer purchase order or other Customer documentation will be incorporated into or form any part of this Agreement, and all such terms are null and void. In the event of any conflict or inconsistency, the following order of precedence will apply: (i) a separate agreement mutually signed by authorized representatives of both Parties (such as a Master Services Agreement), (ii) this Agreement, and (iii) the applicable Order. For clarity, an "Order" refers exclusively to the official ordering document provided by the Company or an authorized Platform.
**10.3 Force majeure.** Neither Party will be liable for any delay or failure to perform its obligations (except for payment obligations) if the delay or failure is due to any event qualifying as force majeure under Article 1218 of the French Civil Code, including (i) natural disasters, (ii) labor disputes, (iii) systemic electrical, telecommunications, or other utility failures, (iv) earthquakes, (v) storms, (vi) blockages, (vii) embargoes, (viii) riots, (ix) acts or orders of government, (x) acts of terrorism, or (xi) war.
**10.4 Export compliance.** The Service is subject to export control and economic sanctions laws of the European Union, the United States, and other applicable jurisdictions. Customer agrees to comply strictly with all such laws. Customer represents that it is not (i) located in, or organized under the laws of, any country or territory subject to a comprehensive US or EU embargo, or (ii) listed on any restricted Party list maintained by the US government, the EU, or any EU Member State. If Customer becomes subject to any such sanctions during the Agreement, such event constitutes a material breach by Customer. The Agreement will terminate immediately without any obligation to refund prepaid fees, and Customer must not permit its Users to access or use the Software in violation of any applicable export embargo, prohibition, or restriction.
**10.5 Governing law and jurisdiction.** This Agreement will be governed by and construed in accordance with the laws of France, without regard to its conflict of laws principles. The United Nations Convention on Contracts for the International Sale of Goods will not apply. Any dispute, claim, or action arising out of or relating to this Agreement will be subject to the exclusive jurisdiction of the Commercial Court (*Tribunal de commerce*) of Paris, France.
**10.6 Independent contractors.** The Parties are independent contractors. Nothing in this Agreement will be construed as creating a joint venture, partnership, employment, or agency relationship between the Company and Customer. Neither Party has any right or authority to assume or create any obligation or responsibility, express or implied, on behalf of or in the name of the other.
**10.7 Assignment.** Neither Party may assign or transfer any of its rights or obligations under this Agreement without the prior written consent of the other Party. However, either Party may assign this Agreement in its entirety (including all Orders), without consent, to an affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets. Notwithstanding the foregoing, Customer may not assign this Agreement to a direct competitor of the Company without the Company's explicit prior written consent. Any purported assignment in violation of this section is void.
**10.8 Waiver.** No failure or delay by either Party in exercising any right under this Agreement will constitute a waiver of that right. Any waiver must be in writing and signed by an authorized representative of the Party granting the waiver.
## **11. Definitions**
**"Atlassian Marketplace"** means the online marketplace operated by Atlassian where the Software may be purchased or accessed.
**"Feature Release"** means a new version of the Software that increments the first (X) or second number (Y) in the standard "X.Y.Z" versioning format, distinguishing it from standard bug fixes or security patches.
**"Order"** means the applicable ordering document, online checkout process, or subscription flow that specifies the Software purchased, the applicable fees, the Subscription Term, and the capacity limits.
**"Platform"** means any third-party software environment (such as Atlassian Confluence or Jira) through which the Software is installed, integrated or deployed.
**"Reseller"** means a third-party entity formally authorized by the Company, or authorized by a Platform, to resell subscriptions to the Software.
**"Software"** means the proprietary downloadable computer programs (logiciels) and ancillary tools developed and owned by the Company.
**"Subscription Term"** means the specific duration of Customer's access to the Software as set forth in the applicable Order.
**"User"** means any individual authorized by Customer to access and use the Software, subject to the user limits defined in the applicable Order.
## **12. Contact Information**
If you have any questions about this Agreement, please contact the Company through our official support website.
*\[End of Agreement\]*
---
language: "en"
---
# Privacy Policy
This is our privacy policy for all our apps and websites, as of June 26th, 2023. By using our products:
* You agree that your information may be used according to the following policy,
* You agree that your information may be used according to the [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md),
* You agree to the [Terms of Use](https://docs.requirementyogi.com/legal/terms-of-use.md) (for cloud products) or to the [End-User License Agreement](https://docs.requirementyogi.com/legal/eula.md) (for downloadable products),
* You agree that Atlassian is not responsible for the privacy, security or integrity of Vendor-Collected End User Data.
Contents:
## What information we collect
We gather information through support cases. We also receive information from Atlassian through licenses ("Atlassian-collected end-user data"), Jira support issues, and from website tracking tools such as Google Analytics, Fullview, or other session-recording tools.
We host data created by users in our Cloud apps.
We don't collect any data when apps are installed by the customers on their own server, with the exception of the "feedback job" in Play SQL Base, explained in the table below.
## How we use information we collect
We use the information to:
* Provide the service,
* Provide support for the software,
* Explain features and develop engagement about the software,
* Design new features,
* We may use information in aggregated form (statistics, etc) for advertising,
* For accounting purpose, concerning billing information,
* For legal reasons, to protect the owner, the company, the software or when required by law.
This includes:
* Customers with a license are added to a mailing list to notify them about features of the product. They can unsubscribe from this mailing list.
## What data is collected?
### Data collected in the products
Atlassian defines:
* Atlassian-collected end-user data (basically, the license details)
* Vendor-collected end-user data, which we've split in 3 categories:
* Data containing PII,
* Other collected data, in normal usage (The free data that users create in the application - We only "collect" this data when you use Cloud products),
* Support Data: Data collected by the application when sending a support request (only for Requirement Yogi).
Atlassian is not responsible for the privacy, security or integrity of Vendor-Collected End User Data.
| Mode | Product | Status | Framework | Atlassian-collected end-user data^(1)^ | Vendor-collected end-user data^(1)^ ||
| Mode | Product | Status | Framework | Atlassian-collected end-user data^(1)^ | Data containing PII^(3)^ | Other collected data, in normal usage |
|-------------|--------------------------------------|--------------|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------|--------------------------|-----------------------------------------------------------------------------------|
| Cloud | Requirement Yogi | Paid | Atlassian Connect and Atlassian Forge, using [Atlassian's official ACSB](https://bitbucket.org/atlassian/atlassian-connect-spring-boot). | The license subscription information | None | Application data^(2)^ (the requirements, page IDs, page titles, Jira issues) |
| Cloud | Requirement Yogi for Jira | Paid | Atlassian Connect and Atlassian Forge, using [Atlassian's official ACSB](https://bitbucket.org/atlassian/atlassian-connect-spring-boot). | The license subscription information | None | Application data^(2)^ (the requirements text, page IDs, page titles, Jira issues) |
| Cloud | Any other Cloud plugin | Free or paid | Any framework | The license subscription information | None | Application data |
| Server / DC | Requirement Yogi | Paid | Atlassian P2 plugins | The license subscription information | None | None |
| Server / DC | Requirement Yogi for Jira | Free | Atlassian P2 plugins | None | None | None |
| Server / DC | RY Testing \& Compliance | Paid | Atlassian P2 plugins | The license subscription information | None | None |
| DC | RY-Comala integration | Paid | Atlassian P2 plugins | The license subscription information | None | None |
| Server / DC | PSEA - Play SQL Export Add-on | Free | Atlassian P2 plugins | None | None | None |
| Server / DC | SEO Manager | Free | Atlassian P2 plugins | None | None | None |
| Server / DC | Play SQL Base | Free | Atlassian P2 plugins | None | None since 3.1.2^(4)^ | None |
| Server / DC | Play SQL Spreadsheets | Free | Atlassian P2 plugins | None | None since 3.1.2^(4)^ | None |
| Server / DC | Play SQL Forms | Free | Atlassian P2 plugins | None | None | None |
| Server / DC | ReqIF extension for Requirement Yogi | Free | Atlassian P2 plugins | None | None | None |
(1) As defined in [Atlassian Marketplace Publisher Agreement, section Β§8.4](https://www.atlassian.com/licensing/marketplace/publisheragreement): Generally the company name, country, address, technical email, licensing email, reseller details, license number, etc.
(2) Free text may contain PII if users have entered any.
(3) PII: Personally identifiable information (user names, email, phone number, etc).
(4) There used to be a feedback job in Play SQL Base and Play SQL Spreadsheets. This feedback job was removed in version 3.1.2 ([see the history of this page](https://requirementyogi.atlassian.net/wiki/spaces/RYC/history/1804763557)).
### What other data is collected?
* We have Google Analytics on some of our websites.
* Google collects data about page views which is returned in a form that is not personally identifiable to us, notably aggregated by location, age, gender or demographic factors.
* We do not engage in remarketing.
* We have NOT enabled Advertising features in Google Analytics.
* We have mailing-lists, managed by MailChimp. Users can opt-in, out-out and manage their subscription by clicking on the link in emails.
* Users can get support through a Jira Cloud website, which is under [Atlassian's privacy policy](https://www.atlassian.com/legal/privacy-policy).
* Users can get support by email, in which case we manage our emails through FastMail.
## How we share information we collect
Requirement Yogi is currently a sole-trader company (company type "[SASU](https://fr.wikipedia.org/wiki/Soci%C3%A9t%C3%A9_par_actions_simplifi%C3%A9e_unipersonnelle)" in France) with:
* The founder, Adrien Ragot,
* If any employee or intern is hired, they sign a contract stating that they are strongly forbidden from leaking any information,
* Temporary contractors, hired for a specific time or project.
There are special situations where external people may have access to the data:
* In the situation where the company or one product is sold to a new owner: We sign a mutual NDA before the negotiation. Upon ownership transfer, the new owner takes responsibility for respecting or updating the current licenses and privacy policy.
* In the situation where someone illegally accesses our systems, we cannot provide control about your data,
* In the situation where we are compelled by law to provide this information, we cannot provide control about your data.
Here is what we allow:
| Information | Founder | Employees under confidentiality agreement | Contractors | Accountant |
|------------------|---------|-------------------------------------------|-------------|------------|
| Billing | Yes | No | No | Yes |
| Application Data | Yes | Yes | Yes | No |
| Web Analytics | Yes | Yes | No | No |
| Support | Yes | Yes | No | No |
## How we host and transfer data internationally
### Security
Please see our [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md).
### How long we keep information
We try to delete data as early as possible, except for backups which we keep a little longer.
| License information | License information is provided to us by Atlassian every time we need it. If Atlassian starts limiting the history, then we will store it for up to 2 years, mainly for accounting purposes. |
| User-created data in our Cloud apps | We delete data from the active databases as soon as the addon is uninstalled. We keep a backup of customer data for up to 2 months. |
|-------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
### Subprocessors, where we keep information, how it is transferred internationally
Our products are generally hosted by Amazon AWS and Digital Ocean, except our website which is managed by OVH, France. The computers we use to create software and access your information are located in France.
| Type | Product | Where it is hosted | Link | Data Processing Addenum | Implementation date |
|--------------------------|------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------|
| Data from Cloud products | Requirement Yogi | Amazon AWS. The data residency zones depend on the customer's selection: * Europe (Ireland) by default, * USA if selected. | |  Part 1.14 of their ToS | Pre-2022 |
| Web | Our website | OVH, France | |  [Part](https://www.ovh.com/fr/support/documents_legaux/Annexe%20Traitement%20de%20donn%C3%A9es%20%C3%A0%20caract%C3%A8re%20personnel.pdf) 2 of their [ToS](https://www.ovh.com/fr/support/contrats/) | Pre-2022 |
| Web | Cloudflare | USA | |  [DPA CloudFlare](https://www.cloudflare.com/cloudflare-customer-dpa/) | 2023 |
| Web | OpenAI | Europe / USA | |  [DPA OpenAI](https://openai.com/policies/data-processing-addendum/) | 2025 |
| Web | Google Analytics 4 | Europe | | Data is stored in Europe | 2023 |
| Web | Google Tag Manager Google Ads | Europe | |  [DPA for GTM and Google Ads](https://support.google.com/tagmanager/answer/7207086?sjid=5419309028302576720-EU) | 2023 |
| Web | Fullview | Europe | | Data is stored in Europe | 2023 |
| Support data | Slack | USA | |  [DPA for Slack](https://slack.com/terms-of-service/data-processing) | |
| Support data | Jira and Confluence | Europe | - | - | - |
| Mailing lists | Hubspot | USA | |  [DPA for HubSpot](https://docs.requirementyogi.com/__attachments/a_649dc19af641f7f1d41eebd9a0215a5b2c1d96e51b8847279eb8e7363cc6e26a/HubSpot_DPA_1Sep2023_SubP_SCC_UK.pdf.md?cb=bf9e2075caa1d16832c8c0874b55c7f2) | 2023 |
| Mailing lists | Mailchimp | Not used anymore since 2023. ||||
| Email | Fastmail | Fastmail, Australia / USA. | |  [Part of their ToS](https://www.fastmail.com/about/dpa.html) | Pre-2022 |
| Administrative documents | Encrypted backups of our administrative documents, invoices, work documents. | SpiderOak, USA | |  [2019-10-24 SpiderOak DPA.pdf](https://docs.requirementyogi.com/__attachments/a_e4b2fd142ff0f8e1432b1f7b0381b8a190caccd264a16e6d05cad86bfa5cecdb/2019-10-24%2520SpiderOak%2520DPA.pdf.md?cb=53a374947df55cef42712ffb96b896e3) | Pre-2022 |
| Desktop | Our computers, our company, etc. | Encrypted laptops, desktops and hard drives, Carried by our employees and consultants. || | Pre-2022 |
### How to access and control your information
You have a right to access the personal information we collect and correct it. Most of the processes are automated:
* Concerning the "feedback job" of Play SQL Spreadsheets, you can disable it in the "Privacy Policy" tab of your add-on,
* Concerning the data that is sent for support cases, you are notified and you can send an email manually to us,
* Concerning the free data that you create in the Cloud apps, you can edit it in the application.
* Concerning backups, our Cloud products contain a "Backup" page which can be used to export your data.
## Architecture and specific information for Requirement Yogi Cloud (Confluence and Jira)
See [Security Overview](https://docs.requirementyogi.com/legal/security-overview.md).
## Contact
If any process is not automated or you do not know how to exercise your rights, you may exercise them by contacting Adrien Ragot at:
| Email | [gdpr@r-yogi.com](mailto:gdpr@r-yogi.com) |
| Mail | Requirement Yogi - Responsable GDPR 535 route des Lucioles Les Aqueducs B3 06560 Sophia Antipolis France |
|-------|----------------------------------------------------------------------------------------------------------|
## How we update this policy
We may update this policy without notice, for the purposes of being more specific, reflecting a new practice or complying to legal requirements.
Change log:
* July 5th, 2025: Added the data residency in USA,
* October 17th, 2023: Added Fullview, Google Tag Manager, Google Analytics 4,
* February 15th, 2022: Added Amazon AWS and Requirement Yogi Cloud, and removed cloud products which have been shut down. Added a specific section for Requirement Yogi Cloud.
* October 2nd, 2019: Added SpiderOak for our backups; Reflected the removal of support-requests-through-the-app features.
* January 29th, 2019: Rewrite, to comply with Atlassian's request for updated policies, to have one policy for all products, to be specific on the location of your data, and to reflect up-to-date information.
* September 11th, 2015: Add sections "What data we have", "Who accesses the data", "How we keep our servers secure", "How you can opt out" - see page history.
* November 11th, 2013: Rewrite, to go from generic statements to specific ones.
* October 2nd, 2013: Original version.
## Application
Our Privacy Policy applies to all of the websites and software offered by us. It excludes services offered by Atlassian or any other provider.
When we receive formal written complaints, we contact the person who made the complaint to follow up. In case of dispute, we seek the best amicable resolution. We may work with appropriate regulatory authorities to resolve complaints. The privacy policy is governed by the laws of France, and, subject to the following sentence, in case of dispute, the parties irrevocably and unconditionally submit to the exclusive jurisdiction of the courts of Lyon, France.
---
language: "en"
---
# Requirement Yogi Legal Information
Here are our administrative details.
## Company details
| Denomination | Requirement Yogi S.A.S.U au capital de 5.000 Euros |
| Address | Requirement Yogi 535 route des Lucioles Les Aqueducs B3 06560 Valbonne |
| French registry | 812 048 452 (RCS Grasse) |
| SIRET / SIREN | 81204845200047 |
| APE Code | 58.29C - "Edition de logiciels applicatifs" |
| GST# (NumΓ©ro de TVA intracommunautaire) | FR68812048452 |
| LEI | 969500ZEKXRI8BDJZ453 |
| C.E.O. (PrΓ©sident-Directeur GΓ©nΓ©ral PDG) | Adrien Ragot |
| Official Activity (French) | La SocieΜteΜ a pour objet : * L'eΜdition de progiciels applicatifs bureautiques (notamment tableur -- NAF 58.29C) en teΜleΜchargement et en ligne ; * Prestation de deΜveloppement et de conseil en informatique, * La creΜation, l'acquisition, la location, la prise en location-geΜrance de tous fonds de commerce, la prise aΜ bail, l'installation, l'exploitation de tous eΜtablissements, fonds de commerce, usines, ateliers, se rapportant aΜ l'une ou l'autre des activiteΜs speΜcifieΜes ci-dessus ; * La prise, l'acquisition, l'exploitation ou la cession de tous proceΜdeΜs, brevets et droits de proprieΜteΜ intellectuelle concernant lesdites activiteΜs ; * La participation directe ou indirecte de la SocieΜteΜ dans toutes opeΜrations financieΜres, immobilieΜres ou mobilieΜres, et toutes entreprises commerciales ou industrielles pouvant se rattacher aΜ l'objet social ou aΜ tout objet similaire ou connexe. * La participation de la SocieΜteΜ par tous moyens aΜ toutes entreprises ou socieΜteΜs creΜeΜes ou aΜ creΜer, pouvant se rattacher aΜ l'objet social notamment par voie de creΜation de socieΜteΜs nouvelles, d'apport, commandite, souscription ou rachat de titres ou droits sociaux, fusion, alliance ou association en participation ou groupement d'inteΜreΜt eΜconomique ou de location-geΜrance. * Toutes opeΜrations quelconques contribuant aΜ la reΜalisation de cet objet. |
| Contact | |
|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
language: "en"
---
# Security audit - Cloud (14/07/2022)
## Report from Arcan Security on July 14th, 2022
The text below is a summary of the security audit performed by Aracan Security. See the full report.
[pentest_report_requirement_yogi_cloud_2022_07_14.pdf](https://docs.requirementyogi.com/__attachments/a_70732a40226f92b251fb2c632bb5b4156bb425df86211e004aa6e2259d4cfa6f/pentest_report_requirement_yogi_cloud_2022_07_14.pdf.md?cb=81562335f8d693301d98984d5ae697fc)
### Introduction
This document reports the security audit results of the Confluence and Jira plugins "Requirement Yogi Cloud" and "Requirement Yogi for Jira Cloud" developed by the company Requirement Yogi.
ArcanSecurity did the audit between the 19th of April 2022 and the 21st of April 2022.
Requirement Yogi provided three accounts: Super Admin, Admin and User.
N.B: the results come from 3 days of audit. Thus, they may be only a subset of what an attacker with no time limit can find.
N.B.2: the results have been updated after a verification audit performed early July.
### Risk analysis summary
The main risks which the auditor was asked to focus on were:
* Data leak of a customer,
* Unauthorized changes or deletion of customer's data - Privilege escalation,
* Availability of the platform.
During the audit, the auditor has determined four scenarios that could impact the company Requirement Yogi:
* A user dumps data linked to another customer or a space he does not have access to,
* A user changes data linked to another customer or a space he does not have access to,
* A user performs a restricted action for which he does not have the granted rights,
* An attacker performs a distributed denial of service on the platform.
### Risk assessment
| Probability of the risk |||
|---|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Impact** || **Description** |
| 4 | **Strong** | The environment or context of the company means that, if nothing is done, such a threat will certainly materialize in the short term. |
| 3 | **Average** | The environment and the context of the company mean that, if nothing is done, such a threat will materialize in the short term. |
| 2 | **Low** | Even in the absence of any security measure, the environment and the context mean that the probability of occurrence of such a threat, in the short or medium term, is low. |
| 1 | **Unlikely** | Regardless of any security measures, the probability of occurrence of such a threat is extremely low and negligible. |
| Impact of the risk |||
|---|-------------|--------------------------------------------------------------------------|
| **Impact** || **Description** |
| 4 | **Strong** | Unsustainable financial, legal, commercial or image impact. |
| 3 | **Average** | Significant financial, legal, commercial or image impact |
| 2 | **Low** | Weak financial, legal, commercial or image impact. |
| 1 | **Minimal** | Financial, legal, commercial or image impact without significant impact. |
#### Summary
| Scenario | Probability | Impact | Risk | Action to lower the risk |
|---------------------------------------------------------------------------------------|-------------|--------|------|-----------------------------------------------------------------------|
| An attacker performs a distributed denial of service on the platform. | 2 | 3 | 6 | Implement a rate-limiting system |
| A user changes data linked to another customer or a space he does not have access to. | 1 | 4 | 4 | Harden the overall system Secure the API Make the API more consistent |
| A user dumps data linked to another customer or a space he does not have access to. | 1 | 3 | 3 | Harden the overall system Secure the API Make the API more consistent |
| A user performs a restricted action for which he does not have the granted rights. | 1 | 3 | 3 | Harden the overall system Secure the API |
### General overview
#### Strength
|-----------------------------------------------|
| Good understanding of the cybersecurity risks |
| Follow the guidelines from Atlassian |
| Secure development |
#### Possible improvements
|-------------------------------------------------------------------|
| Make the API more consistent |
| Integrate all the good practices in the whole stack of the system |
| Address the current flaws |
## Conclusion
During the audit, no critical or high vulnerabilities were found by the auditor.
By focusing on the security picture only, the plugin Requirement Yogi Cloud is at a good level.
An attacker will certainly take a considerable amount of time to find and exploit a potential vulnerability in the API. Thus, an attacker would try gaining access to the system by other meanings, like stealing the AWS credentials, doing a phishing attack on employees or other.
Among that, let's not forget that on a bigger picture, the system needs some work to make the API fully consistent, less verbose, and more robust against denial of service.
By taking all of the steps mentioned in the given roadmap, the probability of an attack could be reduced, and so the risk too.
SAS Arcan Security
SAS ARCANSECURITY au capital de 30 000β¬ - 535 Route des Lucioles, Les Aqueducs B3, 06560 Valbonne, France
TeΜl. +33 4 83 43 25 44 - e-mail: [contact@arcansecurity.com](mailto:contact@arcansecurity.com) -- [www.arcansecurity.com](http://www.arcansecurity.com/)
NΒ°TVA : FR01 828 428 367
---
language: "en"
---
# Security audit - Cloud (19/12/2023)
## Report from NΓ©osoft on December 19th, 2023
The text below is a summary of the security audit performed by NΓ©osoft. See the full report.
[AUDIT R-YOGI PLUGINS - Detailed Report - v1.0.pdf](https://docs.requirementyogi.com/__attachments/a_712480e2e0d2c0c684da6ba47f99ede13b560ebbe3d5e2afe1089e2b905094ff/AUDIT%2520R-YOGI%2520PLUGINS%2520-%2520Detailed%2520Report%2520-%2520v1.0.pdf.md?cb=99a288e3598b5e338186f612f2fa3dcb)
### Introduction
This document reports the security audit results of the Confluence and Jira plugins "Requirement Yogi Cloud" and "Requirement Yogi for Jira Cloud" developed by the company Requirement Yogi.
NΓ©osoft did the audit between for a week in December 2023.
Requirement Yogi provided three accounts: Super Admin, Admin and User.
N.B: *the results come from 4 days of audit. Thus, they may be only a subset of what an attacker with no time limit can find.*
### Risk analysis summary
The main risks which the auditor was asked to focus on were:
* Data injection,
* Security Misconfiguration.
During the audit, the auditor has determined two scenarios that could impact the company Requirement Yogi:
* It is possible to export data in Excel format. However, malicious users (including those with "user" profile) could deliberately enter malicious Excel formulas in these data in order to execute arbitrary code on the workstations of people downloading them. A security warning will probably be displayed when Excel is opened, but most users ignore these warnings.
* The Swagger of the plugin is accessible without authentication at the Swagger URL.
### Risk assessment grades
#### Summary
| Scenario | Likelihood | Impact | Criticality | Action to lower the risk |
|----------------------------|------------|--------|-------------|----------------------------------------------------------------------------------------------------------------------------------------------|
| Excel formula injection | 2 | 2 | 2 | Filter Excel formulas in exported files |
| Access to the swagger file | 1 | 1 | 1 | ++Advised++ : Filter access to the Swagger ++Planned++ : The Swagger file will be accessible to all our client to allow them using our APIs. |
### General overview
#### Strength
β Very limited potential attack surface
β Very few audit findings
β Non-critical audit findings
β Very quick fixes proposed
β JWT session tokens well signed / secured
β Security good practices generally taken into account
#### Possible improvements
β Excel formula injection in exportable data
β Access to Swagger documentation without authentication
## Conclusion
During the audit, no critical or high vulnerabilities were found by the auditor.
By focusing on the security picture only, the plugin Requirement Yogi Cloud is at a good level.
An attacker will certainly take a considerable amount of time to find and exploit a potential vulnerability in the API. Thus, an attacker would try gaining access to the system by other meanings, like stealing the AWS credentials, doing a phishing attack on employees or other.
The global security score assigned to the service is A, meaning that no critical vulnerability has been identified.
Two audit findings have been reported, one of which is more a recommendation for improvement than a real vulnerability.
Malicious users could deliberately enter malicious Excel formulas in exportable data to execute arbitrary code on the workstations of people downloading them. A security warning will probably be displayed when Excel is opened, but most users ignore these warnings.
The main risk would therefore be to use the application as an attack vector to compromise other users' workstations, to steal the data stored on them, or possibly to increase one's privileges on the application.
π
## **Grade : A**
No significant vulnerability or very uncritical vulnerabilities
NEO-SOFT SERVICES
SAS au capital de 832.000β¬ - 41-45 Bd Romain Rolland -- 75014 PARIS
TΓ©l : +33 (0)1 41 10 41 60 - e-mail: -- [http://www.neosoft.fr](http://www.neosoft.fr/)
RCS PARIS 484 348 487
NΒ° TVA : FR23484348487
---
language: "en"
---
# Security audit - Cloud (03/03/2025)
## Report from NΓ©osoft on March 3rd, 2025
The text below is a summary of the security audit performed by NΓ©osoft. See the full report.
[AUDIT R-YOGI PLUGINS 2025 - Executive Report - v2.0.pdf](https://docs.requirementyogi.com/__attachments/a_659bc176037641981744ce0721633c85d59f2f9025b6a51dc4977c7509fb5408/AUDIT%2520R-YOGI%2520PLUGINS%25202025%2520-%2520Executive%2520Report%2520-%2520v2.0.pdf.md?cb=ffb33555951cc9155055e010fab69311)
### Introduction
This document reports the security audit results of the Confluence and Jira plugins "Requirement Yogi Cloud", "Requirement Yogi for Jira Cloud", Requirement Yogi Standalone application and the Keycloak authentication platform developed by the company Requirement Yogi.
NΓ©osoft did the audit between for a week in January 2025.
Requirement Yogi provided three accounts: Super Admin, Admin and User.
N.B: *the results come from 4 days of audit. Thus, they may be only a subset of what an attacker with no time limit can find.*
### Risk analysis summary
The main risks which the auditor was asked to focus on were:
* Data injection,
* Security Misconfiguration.
During the audit, the auditor has determined a unique scenario that could impact the company Requirement Yogi:
* The cookies used by the main application do not have a configured "SameSite" security attribute.
The "SameSite" attribute helps mitigate the risks associated with Cross-Site Request Forgery (CSRF) attacks. In this case, the absence of this protection makes the application more vulnerable to potential CSRF attacks.
Likelihood : 1 (Low)
Potential impact : 1 (Low)
Note : This point cannot be corrected because the OAuth authentication (Keycloak) uses the cookie for authentication across all our websites ([c.f. explaination by the Keycloak team](https://github.com/keycloak/keycloak/issues/19886) ). As this issue is associated with a very low criticality, it was decided to rate it as a false-positive.
### Risk assessment grades
### General overview
#### Strength
β Very limited potential attack surface
β No injections identified (XSS, SQLi, SSTI, ...)
β No access control issues found
β JWT session tokens well signed / secured
β No file upload vulnerabilities found
β Security good practices generally taken into account
β Quick implementation of the identified improvements
#### Possible improvements
β Excel formula injection in exportable data
β Access to Swagger documentation without authentication
## Conclusion
During the audit, no critical or high vulnerabilities were found by the auditor.
By focusing on the security picture only, the plugin Requirement Yogi Cloud is at a good level.
An attacker will certainly take a considerable amount of time to find and exploit a potential vulnerability in the API. Thus, an attacker would try gaining access to the system by other meanings, like stealing the AWS credentials, doing a phishing attack on employees or other.
The global security score assigned to the service is A, meaning that no critical vulnerability has been identified.
For one application, the application's cookies, including session cookies, lack the `SameSite` security attribute, increasing the risk of Cross-Site Request Forgery (CSRF) attacks that could exploit unauthorized requests. But it was decided to rate it as false-positive (see paragraph above).
Positive aspects were also identified, such as the absence of injection possibilities like XSS or SQLi and the absence of reported file upload vulnerabilities. In addition, the service generally adheres to security best practices, including correct input validation, secure coding standards and regular updates.
π
## **Grade : A**
No significant vulnerability or very uncritical vulnerabilities
NEO-SOFT SERVICES
SAS au capital de 832.000β¬ - 41-45 Bd Romain Rolland -- 75014 PARIS
TΓ©l : +33 (0)1 41 10 41 60 - e-mail: -- [http://www.neosoft.fr](http://www.neosoft.fr/)
RCS PARIS 484 348 487
NΒ° TVA : FR23484348487
---
language: "en"
---
# Security audit - Cloud (16/03/2026)
## Report from BugCrowd on March 16rd, 2025
The text below is a summary of the security audit performed by BugCrowd after being retested. See the full report.
Download the PDF of the report:
[Requirement_Yogi_Retest_c_suite_report_16-MAR-2026_v1.0_eb1e438a-2dee-4bc3-a6a0-8290f3f0f1d1.pdf](https://docs.requirementyogi.com/__attachments/a_3ec197641c23e62dc038f11cb25a18d8fc9dcf3c91fa712ed535908b4e658795/Requirement_Yogi_Retest_c_suite_report_16-MAR-2026_v1.0_eb1e438a-2dee-4bc3-a6a0-8290f3f0f1d1.pdf.md?cb=7e29f212832031cada575d4cf4cb2894)
### Introduction
This document reports the security audit results of the Confluence and Jira plugins "Requirement Yogi Cloud", "Requirement Yogi for Jira Cloud", Requirement Yogi Standalone application and the Keycloak authentication platform developed by the company Requirement Yogi.
BugCrowd did the audit from January 28th, 2026, through February 16th, 2026..
### Risk analysis summary
The main risks which the auditor was asked to focus on were:
* Data injection,
* Security Misconfiguration.
During the audit, the auditor has identified 9 vulnerabilities. 1 Critical, 1 Low, and 1 Informational vulnerability were retested and could no longer be reproduced with the reproduction steps. These findings are now remediated.
The remaining vulnerabilities include:
* **0 Critical**
* **0 Severe**
* **0 Moderate**
* **0 Low**
* **5 Informational**
### Risk assessment grades
The following key is used to explain how Bugcrowd rates valid vulnerability submissions and their technical severity. As a trusted advisor Bugcrowd also provides common "next steps" for program owners per severity category.
More detailed information regarding our vulnerability classification can be found at:
## Conclusion
π
## **RISK :** `LOW`
Bugcrowd has rated the risk to the Requirement Yogi's assets as Low
Bugcrowd
921 Front St., San Francisco - 94111, CA, United States of America
e-mail: [support@bugcrowd.com](mailto:support@bugcrowd.com)
CREST approved :
Please note that Atlassian encourages self-managed Penetration Testing by CREST Accredited testing vendors:
---
language: "en"
---
# Security Overview
This document details the technical specifics of our security practices (encryption, backups, hosting, monitoring and access control). If you are looking for high-level commitments and responsibilities, please refer to the [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md).
These practices are accurate on July 5th, 2025.
## Definitions
* **"App"** means the cloud-based software application provided by us, including its user interface, underlying infrastructure, APIs, and associated services, through which Users access and manage requirement-related data and collaborate within integrated platforms such as Confluence.
* **"Data Residency"** means a feature of the App that allows Customers to select the geographic region where their Application Data is hosted and stored. Data Residency applies exclusively to Application Data and does not extend to Support Data, License Data, or Website Analytics.
### Architecure overview
* The app is deployed on Amazon AWS,
* This app is integrated with Atlassian using the [Atlassian Connect Spring Boot](https://bitbucket.org/atlassian/atlassian-connect-spring-boot/src/master/) framework, with a Forge descriptor as required by Atlassian. It means, when the user interacts with Atlassian Confluence and Jira where the app is installed, Atlassian notifies the app of changes, the app downloads the relevant information, extracts the necessary information and stores it in AWS.
* "Data Residency" supports 2 regions:
* Default: The data is stored in Europe,
* US: The data is stored in the USA.
### Security details
* The app is deployed in the AWS Regions:
* `eu-west-1` (**Ireland**) for the default and EU Data Residency,
* `us-east-1` (**USA,** North Virginia) for the US Data Residency,
* The data is stored in AWS RDS and S3, **with encryption enabled**, in the same AWS Region.
* AWS RDS is configured with **automatic backups and 30-day retention period**. The backups are encrypted. There is no granularity: Restoring the data for all customers to a point in time would be easy, while restoring a subset or a single customer would be time-consuming.
* Data in transit is encrypted in HTTPS over the worldwide internet, and TLS between the application servers and the database. The database is on a private subnet with no direct route from the worldwide internet to the database itself.
* The logs are stored in AWS CloudWatch using encryption enabled,
* The change events are stored in AWS CloudTrail in Europe,
* Employees under confidentiality agreement can access the live data in the database, the live servers, and the backups.
### Application Data
The data that the app stores is subject to constant changes depending on features we develop. For the moment, the data is:
* The key, body and other properties of requirements,
* The page IDs, and sometimes the page titles and page body, specifically if there is an error and the support might need to investigate,
* The details of Jira issues when exported by user through a Traceability Matrix,
* Data which the users create in the app, notably reports they create, transformation templates, etc.,
* The userKey associated with changes, which is an anonymized identifier provided to us by Atlassian,
* The clientKey, which is the key of the instance, and its URL,
* License information provided by Atlassian,
* We only retrieve information made accessible to us by Atlassian or edit information that Atlassian allows us to, and we don't recoup this information with other sources.
Since Application Data includes information written by users, it can contain protected information without our knowledge.
## How we update this policy
This information is subject to change in case of architectural change: if we decide to migrate the app to another provider, or if we decide to change databases inside of AWS, or if we decide to add/remove availability zones, or if we decide of another architecture. In any case, we will ensure that the data is encrypted at rest.
We may update this policy without notice, for the purposes of being more specific, reflecting a new practice or complying to legal requirements.
Change log:
* July 5th 2025: Moved a section from the [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md) to create this document.
---
language: "en"
---
# Security Policy
This document describes our security policy. We cannot guarantee that no leak will ever happen, but we do our best to keep your data safe.
## Published annexes
* [Security audit (03/03/2025)](https://docs.requirementyogi.com/legal/security-audit-cloud-03-03-2025.md)
* [Security audit (19/12/2023)](https://docs.requirementyogi.com/legal/security-audit-19-12-2023.md)
* [Security audit (14/07/2022)](https://docs.requirementyogi.com/legal/security-audit-14-07-2022.md)
* [CAIQ Lite -- Requirement Yogi Cloud](https://docs.requirementyogi.com/legal/caiq-lite-requirement-yogi-cloud.md)
## Your data
Please see our [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md) concerning how we manage your data.
## How we develop secure software
* We use code reviews to detect vulnerabilities before merging and delivering to customers,
* We ensure that we check for permissions for any resources we have, and we regularly review those permissions,
* We use Git to manage changes, so that any code that goes to production is easily auditable.
## How we keep our communications secure
We make our best to use state-of-the-art techniques to keep the data safe:
* We use SSH keys to access our servers,
* We use HTTPS and SSL certificates to communicate between us and with you.
* We don't transfer data in clear-text over the network.
## How we keep the data secure
Once again, we make our best to use state-of-the-art techniques to keep the data safe:
* We host our websites on Digital Ocean and OVH,
* We host our Cloud applications and their storage on Amazon AWS (Ireland / North Virginia depending on the selected Data Residency),
* Data is encrypted at rest and in transit in our Amazon AWS installations,
* The hard drives of our personal computers are encrypted (for example with Apple's FileVault 2),
* Our personal backup drives are encrypted (for example with Apple's FileVault 2 / Time Machine / Google Docs backups).
## Where we host your data
Please see the [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md) on where we store data.
## How we handle a vulnerability
Important: If you notice a vulnerability, please submit a report to .
* We will investigate as soon as we can and write an internal report,
* If we confirm the vulnerability, we will notify Atlassian,
* If a breach allowed access or alteration of customer data, we also notify our GDPR authorities within 72hrs (namely [CNIL, for France](https://www.cnil.fr/fr/notifier-une-violation-de-donnees-personnelles)),
* If a breach allowed access or alteration of customer data by an external person, we also notify those customers directly.
* If a breach only allowed users of the same customer to view/edit data they were not permitted to (permission violation), we choose whether we only notify customers through the release notes when delivering the new version, or whether we directly contact customers.
We detect vulnerabilities using:
* Participation to Atlassian's bug bounty program, vulnerabilities reported by Atlassian themselves, and obviously we'll also listen to vulnerabilities reported by external people,
* Regular pentests (Once a year - [Please check out our last security audit - **Cloud** (03/03/2025)](https://docs.requirementyogi.com/legal/security-audit-cloud-03-03-2025.md) ),
* NPM's automatic tool ([**npm audit**](https://docs.npmjs.com/cli/v8/commands/npm-audit)),
* Maven's automatic tool ([**Maven Dependency Check**](https://jeremylong.github.io/DependencyCheck/dependency-check-maven/), which uses the [NIST / OWASP](https://nvd.nist.gov/) database and also detects NPM-related vulnerabilities).
Notes:
* Automatic tools detect suspects in most common industry libraries quite frequently, whether we are affected or not. Therefore, we do not publish a report for each of them, we simply upgrade the library or ensure we are not using the feature of the library which has the vulnerability. Our release process blocks the release of software anyway until the suspect is resolved.
* If a vulnerability looks grave to us (ability to access or alter customer data), we investigate whether it would have allowed access or alteration of customer data, and we apply the process above.
Please send notifications to (In case this portal meets a breach, we are also available by email at [security@r-yogi.com](mailto:security@requirementyogi.com)).
## How we perform audits
Every year, we perform a security audit with an external third-party. We've published the result of the last audit on this page: [Security audit (03/03/2025)](https://docs.requirementyogi.com/legal/security-audit-cloud-03-03-2025.md).
---
language: "en"
---
# Source Code Agreement
Requirement Yogi does not, at this time, allow customers, Atlassian or third-parties to use the source code of our product. This mention is required for the Atlassian Marketplace.
---
language: "en"
---
# Support times - SLA Statement
[](https://requirementyogi.atlassian.net/servicedesk/customer/portal/1/group/1/create/9)
## Support
The best way to contact us is the [Service Desk portal](https://requirementyogi.atlassian.net/servicedesk/customer/portal/1/group/1/create/9).
| Medium | Links |
|-------------------------|-----------------------------------------------------------------------------------------------------------------------------------------|
| Documentation | [https://docs.requirementyogi.com](https://docs.requirementyogi.com/) |
| Technical documentation | [https://developer.requirementyogi.com](https://developer.requirementyogi.com/) |
| Email | [support@requirementyogi.atlassian.net](mailto:support@requirementyogi.atlassian.net) (Not recommended, please create a ticket instead) |
| Issue trackers | [https://requirementyogi.atlassian.net](https://requirementyogi.atlassian.net/) |
## Response times
| **Type** | |
|----------------------|----------------------------------------------------------------------------------------------------|
| 4hrs (1/2 day) | Cloud apps with **Blocking** priority, Data Center apps with **Blocking** and**High priority.** |
| 8hrs (1 working day) | Cloud apps with Priority **High** and **Medium priority,** Data Center apps with **Low priority.** |
| 3 days | Data Center and Cloud apps with Low priority or without priority. |
Our public target is to provide an answer within the above times:
* During working days 10am-6pm European time (8hrs means 1 working day),
* Except on [French bank holidays](https://en.wikipedia.org/wiki/Public_holidays_in_France) and temporary leave.
This SLA is an information of intent, and does not engage Requirement Yogi in any way.
Bugfixes and improvements are explicitly not part of any SLA, as software complexity makes it difficult to estimate the timeframe.
## Data Center escalation process
Data Center customers operate our products in mission critical environments and want to feel confident that if issues arise they can be addressed quickly. We want to reassure them that we'll monitor the response times to their support requests:
| **Step 1** | Create a support request on [https://support.requirementyogi.com](https://playsql.atlassian.net/servicedesk). Don't forget to mention "Data Center" to be in the right queue.  | We actively monitor the response times on this queue. Response times are explicited above. |
| **Step 2** | Please wait. We have received your request and we will answer. | If we do not answer within the due timeframe, proceed to the next section. |
| **Step 3** | Please do not escalate when you are not meeting a blocking issue which have received no answer. In the support request, click "Escalate".  | We will receive an email on our mobile phones, telling us you are expecting an answer for this request. Our target on escalation is to provide an answer within **4hrs during working days**. |
| **Step 4** | Contact the manager using the email address received in the request confirmation. | |
|------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
---
language: "en"
---
# Terms and Policies
We have separated our legal terms in several sections:
| Document | Applies to | **Last updated** |
|----------------------------------------------------------|-------------------|------------------|
| [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md) | All products | 2025-06-03 |
| [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md) | All products | 2025-07-02 |
| [Terms of Service](https://docs.requirementyogi.com/legal/terms-of-service.md) | Cloud products | 2026-02-26 |
| [EULA](https://docs.requirementyogi.com/legal/eula.md) | Download products | 2026-03-01 |
| [Source Code Agreement](https://docs.requirementyogi.com/legal/source-code-agreement.md) | All products | 2024-12-10 |
| [Acceptable Use Policy](https://docs.requirementyogi.com/legal/acceptable-use-policy.md) | Users | 2026-02-26 |
Please refer to each document for more details.
---
language: "en"
---
# Terms of Service
**Last Updated:** February 27, 2026
These terms apply to all our Cloud products. See also:
* [EULA](https://docs.requirementyogi.com/legal/eula.md) for Server and Data Center products
* [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md)
* [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md)
* [Acceptable Use Policy](https://docs.requirementyogi.com/legal/acceptable-use-policy.md)
These Terms of Service (the "**Agreement** ") are entered into by (i) Requirement Yogi SASU, a French simplified joint-stock company registered under number 812 048 452 RCS Grasse, headquartered at Les Aqueducs B3, 535 Route des Lucioles, 06560 Valbonne, France (the "**Company** "); and (ii) the entity accepting these terms (the "**Customer** "). The Company and the Customer are each referred to as a "**Party** " and collectively as the "**Parties**".
By (i) checking a box indicating acceptance, (ii) executing an order document that references this Agreement, or (iii) installing the Service via a Platform, Customer agrees to be bound by this Agreement. The individual accepting this Agreement represents that they have the authority to bind Customer.
**Business use only.** Customer represents that it is acquiring the Service for its own commercial or industrial purposes. Customer represents that it is not a consumer as this term is generally defined under French and EU regulations.
## **1. The service**
**1.1 Scope of the service.** The Company provides a suite of software applications dedicated to requirement management and related productivity tools, accessible via third-party platforms or as a standalone web application (collectively, the **"Service"**). The Service may consist of different modules (such as modules tailored for Jira or Confluence), which may be subscribed separately.
**1.2 Excluded products.** These Terms of Service apply exclusively to the Company's cloud-based and hosted services. They do not apply to any downloadable or on-premise software products provided by the Company (such as Data Center applications), which are governed by a separate End User License Agreement provided with those products.
## **2. Access and use**
**2.1 Provision of the service.** Subject to Customer's continuous compliance with this Agreement and payment of applicable fees, the Company grants Customer a limited, non-exclusive, non-transferable, and worldwide right to access and use the Service during the applicable Subscription Term.
**2.2 Acceptable use policy.** End Users accessing the Service must comply with the Company's Acceptable Use Policy (the **"AUP"**). Customer is responsible for ensuring its Users acknowledge and adhere to the AUP when they are added to the Service or upon account creation.
**2.3 Third-party platforms.** Where the Service is accessed through a third-party platform such as Atlassian (a **"Platform"**), Customer acknowledges that (i) such use is subject to the Platform's separate terms, and (ii) the Platform may enforce quotas or technical limits that affect the Service. The Company is not liable for any actions, limitations, or service interruptions caused by a Platform.
**2.4 Use restrictions.** Customer must not, and must not permit any third party to: (i) rent, lease, sell, distribute, or sublicense the Service; (ii) provide access to the Service to anyone other than authorized Users; (iii) charge its own customers a distinct fee for the use of the Service; (iv) use the Service to build a competitive product or for any benchmarking or competitive intelligence purposes; (v) reverse engineer, decompile, or disassemble the Service except to the extent permitted by applicable law; (vi) bypass or breach any security device or usage limits; (vii) remove or obscure any proprietary notices in the Service; or (viii) access the Service if Customer is a direct competitor of the Company, without the Company's explicit prior written consent.
**2.5 Account registration.** To access the Service, Customer and its Users may be required to create an account with the Company or with a Platform. Customer must provide accurate, current, and complete registration information, and must promptly update this information to ensure the Company can effectively send notices and statements.
**2.6 Authorized Users.** Customer may authorize Users to access the Service in accordance with the applicable Scope of use. Customer represents and warrants that all authorized Users are at least eighteen years old. Customer is strictly responsible for (i) all activities conducted under its Users' accounts, (ii) ensuring each User keeps their login credentials confidential, and (iii) promptly notifying the Company of any unauthorized access to User accounts or the Service.
## **3. Orders, scope of use, and renewals**
**3.1 Placing orders.** Customer may purchase access to specific modules, subscription tiers, or limits at various times (each transaction, an **"Order"** ). Each Order will specify the applicable Subscription Term, pricing, and permitted capacity (the **"Scope of use"**). All Orders are governed by this Agreement.
**3.2 Usage limits.** Customer's access is strictly limited to the Scope of use. If Customer's usage exceeds this capacity, the Company or the Platform may restrict further access until Customer upgrades its Order. If Customer circumvents technical limitations to exceed the Scope of use, Customer is liable for the fees corresponding to the excess usage from the date of the circumvention.
**3.3 Automatic renewal and cancellation.** Unless canceled by Customer prior to the end of the current Subscription Term, each Order will automatically renew for a period equal to its expiring term. Customer may cancel its subscription at any time through the Platform or the Company's billing interface.
## **4. Fees and payment**
**4.1 Subscription mechanisms.** Customer may place Orders through (i) a Platform marketplace (such as Atlassian Marketplace), (ii) an Authorized Reseller, or (iii) directly with the Company.
**4.2 Platform and reseller billing.** If Customer subscribes through a Platform or an Authorized Reseller, the billing, payment terms, and refunds are governed entirely by the terms of service and billing policies of that Platform or Authorized Reseller. The Company is not responsible for their billing errors, payment processing, or license provisioning.
**4.3 Direct billing.** If Customer subscribes directly through the Company, fees are billed and payable in advance. Renewal is contingent upon successful payment. Unless otherwise required by mandatory law, all fees are non-refundable. If Customer's payment method fails, the Company will notify Customer and may suspend access to the Service until payment is successfully processed.
**4.4 Taxes.** All fees are exclusive of any applicable taxes, levies, duties, or tariffs (collectively, "Taxes"). Customer is responsible for paying any applicable Taxes. The entity issuing the final invoice to Customer is responsible for the collection and remittance of applicable Taxes. For Orders placed through a Platform (such as Atlassian Marketplace) or an Authorized Reseller, the tax policies of the entity issuing the final invoice govern the transaction. For Orders placed directly with the Company, the Company's tax policies apply. If Customer is exempt from VAT, a valid intra-community VAT number or applicable exemption certificate must be provided prior to billing; otherwise, standard VAT will be applied to the invoice. If Customer is legally required to withhold any Taxes from its payments, Customer must promptly provide the Company with an official tax receipt to support a tax credit claim.
## **5. Customer data and security**
**5.1 Data ownership and license.** Customer retains all right, title, and interest in and to all data, information, or material that Customer or its authorized Users submit to the Service (**"Customer Data"**). Customer grants the Company a limited, non-exclusive, worldwide license to host, copy, process, and display Customer Data solely to provide, maintain, and support the Service.
**5.2 Privacy and GDPR compliance.** The Company processes personal data in accordance with its Privacy Policy and applicable data protection laws, including the EU General Data Protection Regulation (**"GDPR"** ). Where the Company processes personal data on behalf of Customer as a data processor under the GDPR, the Parties agree to enter into a Data Processing Agreement (**"DPA"**). Upon Customer's request, the Company will provide its standard DPA for execution.
**5.3 Sensitive data restriction.** Customer represents and warrants that it will not upload, process, or submit to the Service any special categories of personal data (as defined in Article 9 of the GDPR, such as health data, biometric data, or revealing racial or ethnic origin), and the Company bears no liability for such data.
**5.4 Security.** The Company implements and maintains physical, technical, and organizational security measures designed to protect Customer Data from unauthorized access, destruction, use, modification, or disclosure. These measures are detailed in the Company's Security Policy, as updated from time to time.
**5.5 Artificial intelligence features.** The Service may include optional artificial intelligence capabilities (the **"AI Features"**). By activating or using the AI Features, Customer authorizes the Company to (i) forward Customer Data to third-party artificial intelligence providers (such as OpenAI or Google) strictly to process Customer's requests, and (ii) use Customer Data to train or fine-tune custom artificial intelligence models exclusively for Customer's own use and workspace. The Company ensures that its agreements with third-party AI providers prohibit them from using Customer Data to train their public or foundational models. Furthermore, the Company will not use Customer Data to train generalized models shared across different customers.
**5.6 Output accuracy.** Customer acknowledges that outputs generated by AI Features may be (i) inaccurate, (ii) incomplete, or (iii) inappropriate. Customer must independently review and validate all outputs before relying on them.
**5.7 Similar outputs.** Customer acknowledges that the AI Features may generate identical or similar outputs for different customers. The Company makes no representations regarding the uniqueness or the ownership of any output by the Customer.
**5.8 Model training.** Customer must not use the outputs generated by the AI Features to (i) develop, (ii) train, or (iii) improve any artificial intelligence or machine learning models.
**5.9 Automated decisions.** Customer must not use the AI Features to make automated decisions that produce significant individual, legal, financial, or systemic effects without appropriate human oversight.
## **6. Customer support and documentation**
**6.1 Documentation.** The Company provides online documentation and guides (the **"Documentation"**) regarding the use of the Service. Customer is expected to consult the Documentation before submitting support requests.
**6.2 Support services.** If Customer cannot resolve an issue using the Documentation, Customer may request assistance through the Company's designated support portal or ticketing system. The Company will use commercially reasonable efforts to provide support. However, Customer acknowledges that response times or target resolutions published by the Company are provided for informational purposes only and do not constitute a legally binding Service Level Agreement (SLA).
**6.3 Service level agreement.** If Customer's Order explicitly includes a premium tier with a Service Level Agreement (an "**SLA**"), Company will provide the Service in accordance with the applicable uptime metrics. The SLA measures only the technical availability of the core Service and explicitly excludes (i) support ticket response times, and (ii) disruptions caused by a Platform. Company will use its internal monitoring logs as the primary tool to measure uptime, but Company will reasonably consider documented contrary evidence provided by Customer. If Company fails to meet the SLA metrics, Customer's sole and exclusive remedy is a pro-rata service credit applied to the next invoice, prorated based on the duration of the downtime. Company will instead issue a cash refund if a credit cannot be applied because (i) Customer does not renew the Order, or (ii) the billing Platform prohibits partial credits. Any such cash refund is calculated strictly based on the net fees actually received by Company, excluding any commissions or taxes retained by a Platform or an Authorized Reseller. To receive a remedy, Customer must submit a written claim to Company within thirty days of the downtime incident, as Company does not issue credits or refunds automatically.
## **7. Intellectual Property**
**7.1 Company ownership.** The Company and its licensors exclusively own all right, title, and interest in and to the Service, the underlying software, algorithms, interfaces, and documentation, including all associated intellectual property rights. No rights are granted to Customer other than the limited right to use the Service as expressly set forth in this Agreement.
**7.2 Customer ownership and license.** Customer retains all right, title, and interest in and to the Customer Data. Customer grants the Company and its subcontractors a worldwide, limited-term, royalty-free license to host, copy, process, transmit, and display Customer Data strictly as necessary for the Company to provide, maintain, and support the Service in accordance with this Agreement and the applicable Data Processing Agreement.
**7.3 Usage Data.** The Company may collect and process technical and behavioral data regarding the use and performance of the Service in an aggregated and anonymized form (**"Usage Data"**). The Company may use Usage Data to analyze trends, operate and improve the Service, and develop new features. The Company owns all right, title, and interest in and to the Usage Data, provided that such data cannot be used to identify Customer or any individual User. Customer may opt out of the collection of Usage Data for product improvement purposes by configuring the applicable settings within the Service or by submitting a written request to the Company.
## **8. Free and evaluation services**
**8.1 Applicability.** The Company may offer certain Services or features free of charge, including trials, evaluations, beta features, or free-tier plans (collectively, **"Free Services"**). Use of Free Services is subject to this Agreement.
**8.2 Permitted use.** Free Services are provided strictly for evaluation, testing, or sandbox purposes. Customer must not use Free Services in a production environment, for commercial operations, or to process live business data. The Company reserves the right to modify the technical limits or eligibility criteria of any Free Service at any time.
**8.3 Anti-circumvention and Company discretion.** Customer must not attempt to circumvent the capacity limits or billing thresholds of Free Services. Prohibited actions include creating multiple Platform instances, accounts, or using alternate email addresses to artificially split user groups. Company may enforce the applicable capacity limits if Company reasonably determines, based on account data, domain names, or usage patterns, that (i) multiple accounts belong to the same entity; or (ii) are being used in a coordinated manner that bypasses licensing requirements.
**8.4 Enforcement.** If the Company determines that Customer is using Free Services in a production environment or circumventing capacity limits, the Company may notify Customer and request that Customer consolidates its usage under a paid Order. If Customer fails to comply within a reasonable timeframe, the Company may suspend the applicable Free Services. The Company also reserves the right to invoice Customer for the standard subscription fees corresponding to the unauthorized production use.
**8.5 "As is" provision.** NOTWITHSTANDING ANYTHING TO THE CONTRARY IN THIS AGREEMENT, ALL FREE SERVICES ARE PROVIDED "AS IS" AND "WITH ALL FAULTS", WITHOUT ANY WARRANTY, SUPPORT OBLIGATION, OR INDEMNITY OF ANY KIND. THE COMPANY'S TOTAL LIABILITY ARISING OUT OF OR RELATED TO CUSTOMER'S USE OF FREE SERVICES WILL NOT EXCEED FIFTY EUROS (β¬50).
## **9. Warranties and disclaimers**
**9.1 Performance warranties.** The Company warrants to Customer that: (i) during the applicable Subscription Term, the Service will operate in substantial conformity with the applicable Documentation; and (ii) the Company will use commercially reasonable efforts designed to ensure that the Service, when and as provided by the Company, is free of any viruses, malware, or similar malicious code. Customer acknowledges that the Company operates a cloud-based service and may update the Service, features, and Documentation, provided such updates do not materially degrade the core functionality of the Service.
**9.2 Performance warranty remedy.** If Company breaches a performance warranty set forth in Section 9.1 and Customer makes a reasonably detailed warranty claim during the applicable Subscription Term, the Company will use commercially reasonable efforts to correct the non-conformity. If the Company determines such remedy to be commerically impracticable within a reasonable time, either Party may terminate the affected Order. The Company will then refund to Customer any pre-paid, unused fees for the terminated portion of the subscription. These procedures represent Customer's sole and exclusive remedy, and the Company's entire liability, for any breach of a performance warranty.
**9.3 Exclusions and third-party integrations.** The warranties in this Section 9 do not apply to the extent the issue or non-conformity is caused by: (i) Customer's unauthorized use, misuse, or modification of the Service; (ii) unsupported releases of the Service; or (iii) third-party products, services, platforms, or infrastructure. The Company does not guarantee the continued availability, performance, or compatibility of any third-party integrations or APIs. This includes integrations or APIs provided by a Platform (such as Atlassian, Google, or others). The Company will not be liable for any disruption caused by changes, deprecations, or outages of such third-party services.
**9.4 Disclaimers.** **Except for the express warranties set forth in this Section 9, the Service, support, and all related services are provided "as is" and "with all faults." To the maximum extent permitted by applicable law, the Company makes no other warranties, whether express, implied, statutory or otherwise, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. The Company does not warrant that Customer's use of the Service will be uninterrupted, completely secure, or error-free. The Company will not be liable for delays, failures, or problems inherent in the use of the internet, third-party cloud infrastructure, Platforms (including Atlassian) and APIs.**
## **10. Limitation of liability**
**10.1 Exclusion of indirect damages.** To the maximum extent permitted by applicable law, and in accordance with Article 1231-4 of the French Civil Code, neither Party will be liable to the other for any indirect or unforeseeable damages (*dommages indirects et imprΓ©visibles*) arising out of or relating to this Agreement, including but not limited to (i) loss of revenue, (ii) loss of business opportunity, (iii) loss of use, (iv) loss of data, (v) corruption of data, or (vi) reputational harm. This applies regardless of whether a Party was advised of the possibility of such damages.
**10.2 Mutual liability cap.** In no event will the total, cumulative liability of either Party arising out of or related to this Agreement exceed the total amounts paid or payable by Customer to the Company during the eighteen (18) month period immediately preceding the event giving rise to such claim.
**10.3 Excluded claims.** The limitations of liability set forth in Section 10.2 will not apply to: (i) Customer's obligation to pay all fees due under this Agreement; (ii) damages resulting from a Party's gross negligence, willful misconduct, or fraud (*faute dolosive ou faute lourde*), as liability for such faults cannot be limited under French law; or (iii) any liability that cannot be excluded or limited under applicable law.
**10.4 Exemption for Third-Party APIs and Infrastructure.** The Company relies on third-party services and APIs, notably Platforms such as Atlassian Cloud products, to deliver the Service. The Company bears no liability whatsoever for any downtime, data loss, degraded performance, or failure of the Service caused by outages, deprecations, rate-limiting, or malfunctions of Atlassian's infrastructure or any other third-party infrastructure beyond the Company's reasonable control.
## **11. Term and termination**
**11.1 Term of agreement.** This Agreement commences on the effective date of the first Order and remains in effect until all applicable Orders have expired or been terminated.
**11.2 Termination for cause.** Either Party may terminate this Agreement (including all Orders) if the other Party materially breaches this Agreement and fails to cure the breach within thirty (30) days after receiving written notice. However, the Company may suspend or terminate this Agreement or any Order immediately upon notice if Customer violates the Acceptable Use Policy, breaches its license restrictions, or fails to pay any amounts due.
**11.3 Effect of termination.** Upon expiration or termination of this Agreement: (i) all rights and licenses granted to Customer will immediately cease; (ii) Customer must immediately stop using the Service and delete any active access credentials, API keys, or integration tokens; and (iii) the Company will delete Customer Data in accordance with its standard data retention policies and applicable law.
**11.4 Financial consequences.** If Customer terminates this Agreement for the Company's uncured material breach, the Company will refund a pro-rata portion of any prepaid fees covering the remainder of the applicable Subscription Term. If the Company terminates this Agreement for Customer's material breach, no fees will be refunded, and any unpaid fees for the remainder of the current Subscription Term will become immediately due and payable.
**11.5 Survival.** The provisions of this Agreement that by their nature should survive termination will survive, including but not limited to Sections 4 (Fees and payment), 5.1 (Data ownership and license), 7 (Intellectual Property), 9.4 (Disclaimers), 10 (Limitation of liability), 11.4 (Financial consequences), 12 (Indemnification), 13 (Confidentiality), and 15 (General provisions). Section 13 (Confidentiality) will survive for a period of three years following termination.
## **12. Indemnification**
**12.1 Indemnification by the Company.** The Company will defend Customer and its officers, directors, and employees against any third-party claim, demand, suit, or proceeding alleging that the use of the Service, standing alone and as permitted under this Agreement, infringes or misappropriates a third party's intellectual property rights (a **"Claim Against Customer"**). The Company will indemnify Customer for any damages, attorney fees, and costs finally awarded against Customer as a result of, or for amounts paid by Customer under a settlement approved by the Company in writing of, a Claim Against Customer. The Company will have no obligation for any claim arising from: (i) Customer Data; (ii) modification of the Service by anyone other than the Company; (iii) combination of the Service with any other hardware, software, or Platforms (including Atlassian Products) not provided by the Company; or (iv) Customer's use of the Service in violation of this Agreement.
**12.2 Indemnification by Customer.** Customer will defend the Company and its officers, directors, and employees against any third-party claim, demand, suit, or proceeding arising out of or relating to: (i) Customer Data (including any assertion that Customer Data infringes or misappropriates a third party's intellectual property rights or violates applicable law); or (ii) Customer's breach of the Acceptable Use Policy or export compliance restrictions under this Agreement (a **"Claim Against Company"**). Customer will indemnify the Company for any damages, attorney fees, and costs finally awarded against the Company, or for amounts paid by the Company under a settlement approved by Customer in writing, as a result of a Claim Against Company.
**12.3 Indemnification procedures.** The obligations above apply only if the indemnified Party: (i) provides prompt written notice of the claim to the indemnifying Party; (ii) grants the indemnifying Party sole control of the defense and settlement of the claim (provided that the indemnifying Party may not settle any claim unless the settlement unconditionally releases the indemnified Party of all liability and does not include any admission of fault); and (iii) providing reasonable cooperation to the indemnifying Party, at the indemnifying Party's expense. The indemnified Party may optionally participate in the defense of the claim with counsel of its own choosing, at its own cost and expense.
**12.4 Mitigation.** If the Service becomes, or Company reasonably believes it is likely to become, the subject of an infringement claim, Company may, at its option and expense: (i) procure for Customer the right to continue using the Service; (ii) modify or replace the Service so it becomes non-infringing; or (iii) terminate this Agreement and refund Customer a pro-rata portion of any prepaid fees covering the remainder of the applicable Subscription Term. This Section 12 states the Company's entire liability and Customer's exclusive remedy regarding any intellectual property infringement claim.
## **13. Confidentiality**
**13.1 Definition.** "Confidential Information" means information disclosed by one Party to the other under or in connection with this Agreement that: (i) is designated by the disclosing Party as proprietary or confidential; or (ii) should reasonably be understood to be proprietary or confidential due to its nature and the circumstances of its disclosure. The Company's Confidential Information includes any source code, non-public pricing, and non-public technical or performance information about the Service. Customer's Confidential Information includes Customer Data.
**13.2 Protection.** The receiving Party will: (i) protect the disclosing Party's Confidential Information using the same degree of care it uses to protect its own confidential information of like kind (but not less than reasonable care); (ii) use it solely to perform its obligations or exercise its rights under this Agreement; and (iii) disclose it only to its employees, contractors, and advisors who have a need to know and are bound by confidentiality obligations at least as protective as those contained in this Section.
**13.3 Exceptions.** Confidential Information does not include information that: (i) is or becomes generally known to the public without breach of any obligation owed to the disclosing Party; (ii) was known to the receiving Party prior to its disclosure without breach of any obligation; (iii) is received from a third Party without restriction; or (iv) was independently developed by the receiving Party.
**13.4 Compelled disclosure.** The receiving Party may disclose Confidential Information to the extent compelled by law, regulation, or court order, provided it gives the disclosing Party prior written notice (to the extent legally permitted) and reasonable assistance, at the disclosing Party's cost, to contest the disclosure.
**13.5 Return and retention.** Upon termination of this Agreement, or upon request, the receiving Party will securely destroy or return all Confidential Information of the disclosing Party. However, the receiving Party may retain copies to the extent required by applicable law or as part of its standard, automated computer backups, provided that such retained information remains strictly subject to these confidentiality obligations until ultimately destroyed.
## **14. Feedback and publicity**
**14.1 Feedback.** If Customer or its Users provide the Company with suggestions, enhancement requests, comments, specific software configurations, or prompts and conversational inputs submitted to AI features (collectively, **"Feedback"**), the Company may use, modify, and incorporate such Feedback without restriction or obligation. Feedback is not considered Customer's Confidential Information.
**14.2 Publicity.** The Company may identify Customer as a User of the Service and may use Customer's name, logo, and the number of licensed Users in its marketing materials, client lists, and public communications. Customer may withdraw this authorization at any time by submitting a written request to the Company.
## **15. General provisions**
**15.1 Updates to the agreement.** The Company may modify this Agreement from time to time. Unless a modification is required by applicable law to take effect immediately, any material changes will become effective upon the first day of Customer's next renewal period. The Company will make reasonable efforts to notify Customer of material updates. If Customer does not agree to the updated terms, Customer's sole remedy is to cancel the subscription before it renews.
**15.2 Entire agreement and order of precedence.** This Agreement, including any referenced policies and Orders, constitutes the entire agreement between the Parties. It supersedes all prior or contemporaneous agreements, representations, or understandings, whether written or oral. No terms or conditions stated in a Customer purchase order or other Customer documentation will be incorporated into or form any part of this Agreement, and all such terms are null and void. In the event of any conflict or inconsistency, the following order of precedence will apply: (i) a separate agreement mutually signed by authorized representatives of both Parties (such as a Master Services Agreement), (ii) this Agreement, and (iii) the applicable Order. For clarity, an "Order" refers exclusively to the official ordering document provided by the Company or an authorized Platform.
**15.3 Force majeure.** Neither Party will be liable for any delay or failure to perform its obligations under this Agreement (except for payment obligations) if the delay or failure is due to any event qualifying as *force majeure* under Article 1218 of the French Civil Code, including (i) natural disasters, (ii) labor disputes, (iii) systemic electrical, telecommunications, or other utility failures, (iv) earthquakes, (v) storms, (vi) blockages, (vii) embargoes, (viii) riots, (ix) acts or orders of government, (x) acts of terrorism, or (xi) war.
**15.4 Export compliance.** The Service is subject to export control and economic sanctions laws of the European Union, the United States, and other applicable jurisdictions. Customer agrees to comply strictly with all such laws. Customer represents that it is not (i) located in, or organized under the laws of, any country or territory subject to a comprehensive US or EU embargo, or (ii) listed on any restricted Party list maintained by the US government, the EU, or any EU Member State. If Customer becomes subject to any such sanctions during the Agreement, such event constitutes a material breach by Customer. The Agreement will terminate immediately without any obligation to refund prepaid fees, and Customer must not permit its Users to access or use the Service in violation of any applicable export embargo, prohibition, or restriction.
**15.5 Governing law and jurisdiction.** This Agreement will be governed by and construed in accordance with the laws of France, without regard to its conflict of laws principles. The United Nations Convention on Contracts for the International Sale of Goods will not apply. Any dispute, claim, or action arising out of or relating to this Agreement will be subject to the exclusive jurisdiction of the Commercial Court (*Tribunal de commerce*) of Paris, France.
**15.6 Independent contractors.** The Parties are independent contractors. Nothing in this Agreement will be construed as creating a joint venture, partnership, employment, or agency relationship between the Company and Customer. Neither Party has any right or authority to assume or create any obligation or responsibility, express or implied, on behalf of or in the name of the other.
**15.7 Assignment.** Neither Party may assign or transfer any of its rights or obligations under this Agreement without the prior written consent of the other Party. However, either Party may assign this Agreement in its entirety (including all Orders), without consent, to an affiliate or in connection with a merger, acquisition, corporate reorganization, or sale of all or substantially all of its assets. Notwithstanding the foregoing, Customer may not assign this Agreement to a direct competitor of the Company without the Company's explicit prior written consent. Any purported assignment in violation of this section is void.
**15.8 Waiver.** No failure or delay by either Party in exercising any right under this Agreement will constitute a waiver of that right. Any waiver must be in writing and signed by an authorized representative of the Party granting the waiver.
## **16. Definitions**
**"Atlassian Marketplace"** means the online marketplace operated by Atlassian (currently located at [https://marketplace.atlassian.com](https://marketplace.atlassian.com/) ) where the Service may be purchased or accessed.
"**Atlassian Product**" refers to the products developed by Atlassian, including "Confluence" and "Jira".
**"Authorized Reseller"** means a third-party entity formally authorized by the Company, or authorized by a Platform, to resell subscriptions to the Service.
**"Customer Data"** means any data, content, materials, or information submitted, uploaded, or configured by Customer or its Users within the Service. For clarity, Customer Data does not include Usage Data or Feedback.
"**Documentation** " refers to the official supporting technical documentation delivered online (currently located at [https://docs.requirementyogi.com](https://docs.requirementyogi.com/) ). It does not include blogs or forums.
**"Hosting Services"** means the cloud computing infrastructure, data storage, bandwidth, and technical support provided by the Company, directly or through its third-party providers, to facilitate access to the Software.
**"Order"** means the applicable ordering document, online checkout process, or subscription flow (whether provided directly by the Company, through the Atlassian Marketplace, or via an Authorized Reseller) that specifies the Service purchased, the applicable fees, the Subscription Term, and the scope of use (e.g., user tier).
**"Platform"** means any third-party ecosystem, marketplace, or software environment (such as Atlassian or Google) through which the Service is accessed or integrated.
**"Service"** means the combined offering of the Software and the Hosting Services made available to Customer under this Agreement.
**"Software"** means the proprietary computer programs (*logiciels* ), algorithms, and intellectual property (*titres de propriΓ©tΓ© intellectuelle* , notably *droits d'auteur*) developed and owned by the Company.
**"Subscription Term"** means the specific duration of Customer's access to the Service as set forth in the applicable Order, including any initial term and subsequent renewal periods.
**"User"** means any individual (natural person) authorized by Customer to access and use the Service under Customer's account, subject to the user limits defined in the applicable Order.
## **17. Contact Information**
If you have any questions about this Agreement, please contact the Company through our support website.
*\[End of Agreement\]*
---
language: "en"
---
# Terms of Use (archive)
## Archived on 26/02/2026
Starting from 27/02/2026, these Terms of Use are replaced by the [Terms of Service](https://docs.requirementyogi.com/legal/terms-of-service.md) .
These terms of use apply to all our cloud products. See also:
* [EULA for server products](https://docs.requirementyogi.com/legal/eula.md)
* [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md)
* [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md)
This Agreement is between you and Requirement Yogi. If you are agreeing to this Agreement not as an individual but on behalf of your company, then "Customer" or "you" means your company, and you are binding your company to this Agreement.
By using or accessing the products, you indicate your assent to be bound by this Agreement.
**1. Scope**
This Agreement governs your use of online services provided by Requirement Yogi.
This Agreement includes and extends the [Privacy Policy](https://docs.requirementyogi.com/legal/privacy-policy.md).
In the case where a product, service, software or the whole company is transferred to a third party (whether it is sold, leased, inherited or given), all your obligations described in this Agreement are extended to the third party, known in this Agreement as "Future Owner".
Requirement Yogi relies on Atlassian's rules and policies about pricing, evaluation periods, agreements.
**2. Products**
This Agreement governs all online services made available by Requirement Yogi, including but not limited to:
* Requirement Yogi (Cloud): A tool to manage requirements in Confluence Cloud,
* Requirement Yogi for Jira (Cloud): A tool to link Jira issues to requirements (cloud version).
**3. Account registration**
You may need to register for an account in order to use the services. Sometimes, the registration is performed on your behalf by other products. These products inform you about this Agreement.
**4. Change**
Requirement Yogi may modify this Agreement from time to time, subject to the terms below. After a change, by your continued use of the service after a period of 1 month, you indicate your assent to be bound by the updated Agreement.
**5. Access**
Subject to the terms and conditions of this Agreement, Requirement Yogi grants you a non-exclusive right to access and use the services during the Duration (as defined below).
**6. Credentials**
You must ensure that all credentials to online services are kept strictly confidential and aren't shared with any unauthorized person. You agree to immediately notify Requirement Yogi of any unauthorized disclosure of information or any unauthorized use of those credentials.
**7. Availability and Quality of Service**
Requirement Yogi does its best to ensure the best quality of service for its customers. This includes the monitoring of services, backups, regular tests, and communication with customers. However, due to the number of parameters and aleas which could alter this services, Requirement Yogi makes no representation about the quality of those services. In particular, when the software uses, requires or depends on third party programs or services, Requirement Yogi or any Future Owner cannot be held liable for any failure or limitation of those services.
In particular, Atlassian, Digital Ocean, Amazon, OVH or an Internet provider or any third party, may suspend, stop delivering or fail at delivering their services, temporarily or permanently, whether it is a consequence or not of a breach or termination of a license, law or agreement by either party. When it causes an impact on Requirement Yogi's service quality, performance or data, Requirement Yogi cannot be held liable of direct or indirect consequences. Requirement Yogi cannot be held liable of direct of indirect consequences when providers, software or hardware fail.
**8. Security**
Requirement Yogi implements security procedures as defined in our [Security Policy](https://docs.requirementyogi.com/legal/security-policy.md). However, you understand that use of the services necessarily involves transmission of your data over networks that are not owned, operated or controlled by us, and we are not responsible for any of your data lost, altered, intercepted or stored across such networks. We cannot guarantee that our security procedures will be error-free, that transmissions of your data will always be secure or that unauthorized third parties will never be able to defeat our security measures or those of our third party service providers.
**9. Duration**
Access to the service is provided from the creation of your account until its suspension or termination, depending on the availability of the service.
**10. Responsibility**
You must ensure that your use of our services and all your data is at all times compliant with our Acceptable Use and all applicable local, state, federal and international laws and regulations. Requirement Yogi assumes no responsibility or liability for your data, and you shall be solely responsible for your data and the consequences of using, disclosing, storing and transmitting your data. You will defend, indemnify and hold harmless Requirement Yogi (or any Future Owner) from and against any loss, cost, liability or damage, including attorney's fees, for which Requirement Yogi (or a Future Owner) becomes liable to, resulting from your negligence of the current Agreement.
**11. Acceptable Use**
The acceptable use of the services is generally defined as the use which does not alter the service for other customers. An infringement of law, a use in a way which wasn't intended by Requirement Yogi, a use in a way which alters other people's privacy are all against the acceptable use policy. You will not submit "Sensitive Data" to the services, as defined as:
* (i) any personally identifiable information (except as necessary for the establishment of your account),
* (ii) any patient, medical or other protected health information,
* (iii) any pornographic material,
* (iii) any other information subject to regulation or protection under specific laws.
**12. Termination**
In case a user uses the software against the Acceptable Use, the agreement may be terminated by Requirement Yogi. There is no liability for any damage resulting of the termination of this Agreement. There is no liability for any direct or indirect damage resulting of the use or incapacity to use the service or products.
The termination of this Agreement implies that you are not allowed to use the products anymore. You will not be entitled to any credit or refund as a result of termination. Requirement Yogi has no obligation to monitor any content uploaded to the services. Nonetheless, if we deem your use is not in agreement with our Acceptable Use, we may remove your data from our services and/or suspend your access to the services. We will generally alert you when we take such action and give you a reasonable opportunity to cure your breach, depending on our evaluation of the situation.
In case of termination of this Agreement, the clauses 10, 12, 14, 18, 19, 20, 21, 22, 23, remains enforceable.
**13. Restrictions**
Except as otherwise expressly permitted in this Agreement, you will not (a) rent, lease, or incorporate any Product into a product or service you provide to a third party, (b) interfere with any license key mechanism or authentication mechanism in the Products or otherwise circumvent mechanisms in the Products intended to limit your use, (c) reverse engineer, disassemble, decompile, or otherwise seek to obtain or derive the source code, underlying ideas, algorithms, file formats or non-public APIs to any Product, except as permitted by law, (d) publicly disseminate information regarding the performance of the Products.
**14. Support, Documentation and Maintenance**
Requirement Yogi provides support, documentation and maintenance for its service during the period for which you have paid the applicable fee. While attempting to deliver the best of its value, Requirement Yogi makes no representation of the schedule, accuracy and fitness of the maintenance, documentation and support for your particular situation. No information given on the websites, documentation or through electronic channels is contractual unless explicitly specified.
**15. Intellectual Property**
Copyright (c) 2012, Requirement Yogi, All rights reserved.
All content created by Requirement Yogi is protected by international copyright, trademark, patent, trade secret and other intellectual property or proprietary rights laws. The use of this content without the authorization of Requirement Yogi is against the Terms of Use.
The user-generated content is owned by the user who created or uploaded the content.
Products are made available on a limited license or access basis, and no ownership right is conveyed to you. You may choose to provide feedback about the product: comments, information, questions, data, ideas, description of processes or any information you provide, including in the course of receiving support and maintenance ("Feedback"). Requirement Yogi and any Future Owner may use, copy, disclose, license, distribute and exploit your Feedback in any manner without any obligation, royalty or restriction based on intellectual property rights or otherwise. Requirement Yogi also needs to measure, analyze and aggregate how users interact with the Products in order to improve them, such as usage patterns and characteristics of the user base. We collect and use analytics data regarding the use of the Products as described in our Privacy Policy. This data may be used by Requirement Yogi in the same way as the Feedback, without any obligation, royalty or restriction.
**16. Trademarks**
Neither the name of Requirement Yogi, or Play SQL, or the names of its contributors, may be used to endorse or promote products derived from this software without specific prior written permission. By accepting this Agreement, you agree that Requirement Yogi is a trademark of Requirement Yogi. You will only use Requirement Yogi's marks in connection with your use of the service and, unless you are otherwise authorized to continue using the marks pursuant to a separate written agreement, you will immediately cease all use of the marks. Marks means the trademarks, trade names, service marks, logos, owned or otherwise used by Requirement Yogi.
**17. Warranty and Disclaimer**
THERE IS NO WARRANTY FOR ANY PRODUCT, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION, RELATED TO YOUR DATA AND SYSTEMS.
As a clarification, you are not responsible for the cost of all necessary servicing, repair or correction, related to our programs and systems.
**18. Limitation of Liability**
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
**19. Interpretation of clauses "17. Warranty and Disclaimer" and "18. Limitation of liability"**
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Products or Services, unless a warranty or assumption of liability accompanies a copy of the Product or Services in return for a fee.
**20. Jurisdiction and General Provisions**
This Agreement is governed by the laws of France, and, subject to the following sentence, the parties irrevocably and unconditionally submit to the exclusive jurisdiction of the courts of Nice, France. Except in circumstances where a party seeks urgent injunctive relief, before commencing any court proceedings, if any dispute arises under this Agreement the parties will negotiate in good faith to resolve the dispute. If there are several possible interpretations for any part of text of the agreement or in case the agreement isn't specific about some situation or may lead to responsibility on the side of Requirement Yogi or its partners, you must request a binding decision from Requirement Yogi. This decision will become part of this agreement. In the event that a clause or part of a clause of the agreement would be considered void or invalid, the other clauses still apply.
Any notice under this Agreement must be given in writing. We may provide notice to you via email or through your account. Our notices to you will be deemed given upon the first business day after we send it. You may provide notice to Requirement Yogi by post to "Requirement Yogi, 535 route des Lucioles, Les Aqueducs B3, 06560 Sophia Antipolis, France". Your notices to us will be deemed given upon our receipt. Neither party shall be liable to the other for any delay or failure to perform any obligation if the delay or failure is due to unforeseen events which are beyond the reasonable control of any party, such as a strike, blockade, war, act of terrorism, riot, natural disaster, death, failure or power or telecommunication services, or refusal of a license by a government agency.
This Agreement may not be modified or amended by you without our written agreement (which may be withheld in our complete discretion without any requirement to provide any explanation).
## Third-Party Copyright and Licenses for Requirement Yogi Cloud
Requirement Yogi Cloud includes the modules developed by third parties.
The list can be found in the 'About Requirement Yogi' page of your Confluence or Jira instance. In the top bar, click on Apps \> About Requirement Yogi.
---
language: "en"
---
# Type: Application Data
| **Data subjects** | Customers and their end-users |
| **Personal data** | User-generated content |
| **Purpose of processing** | Providing the service to customers. |
| **Legal basis for processing** | Not applicable |
| **Retention period** | Between 1 and 2 months after uninstallation. |
| **International transfers** | * Between the Data Residency zones of the customer, * During a support request, to provide support. |
| **Security measures** | * Encryption at rest and in transit, * Access controls, * Automated backups, * Empoyee confidentiality agreement. |
|--------------------------------|-------------------------------------------------------------------------------------------------------------------|
## Contents of Application Data
The data that the app stores is subject to constant changes depending on features we develop. For the moment, the data is:
* The key, body and other properties of requirements,
* The page IDs, and sometimes the page titles and page body, specifically if there is an error and the support might need to investigate,
* The details of Jira issues when exported by user through a Traceability Matrix,
* Data which the users create in the app, notably reports they create, transformation templates, etc.,
* The userKey associated with changes, which is an anonymized identifier provided to us by Atlassian,
* The clientKey, which is the key of the instance, and its URL,
* License information provided by Atlassian,
* We only retrieve information made accessible to us by Atlassian or edit information that Atlassian allows us to, and we don't recoup this information with other sources.
Since Application Data includes information written by users, it can contain protected information without our knowledge.
---
language: "en"
---
# Type: Atlassian-collected end-user data
| **Data subjects** | Customers and their contact details |
| **Personal data** | Company name, contact names and emails |
| **Purpose of processing** | License management |
| **Legal basis for processing** | * Contractual, * For legal reasons (Prove the contractual engagement, etc.). |
| **Retention period** | As long as provided by Atlassian, and 10 years after the last event with the customer. |
| **International transfers** | * Downloaded and hosted in Europe. |
| **Security measures** | * Encryption at rest and in transit, * Access controls, * Empoyee confidentiality agreement. |
|--------------------------------|----------------------------------------------------------------------------------------------|
## Contents of Atlassian-collected end-user data
Atlassian has defined "End-user data" in the Atlassian Developer Terms:
It varies depending on Atlassian. At this date (July 3, 2025), it includes:
* saleDate
* transactionId
* addonLicenseId
* hostLicenseId
* licenseId
* addonName
* addonKey
* licenseType
* hosting
* changeInBillingPeriod
* oldBillingPeriod
* billingPeriod
* changeInTier
* oldTier
* tier
* appEntitlementId
* appEntitlementNumber
* parentProductName
* changeInParentProductEdition
* oldParentProductEdition
* parentProductEdition
* hostEntitlementId
* hostEntitlementNumber
* cloudId
* maintenanceStartDate
* maintenanceEndDate
* saleType
* purchasePrice
* vendorAmount
* partnerDiscountAmount
* paymentStatus
* dunningStatus
* refundReason
* creditNoteReason
* loyaltyDiscountAmount
* loyaltyDiscountReason
* marketplacePromotionDiscountAmount
* marketplacePromotionDiscountCode
* marketplacePromotionDiscountReason
* expertDiscountAmount
* expertDiscountReason
* manualDiscountAmount
* manualDiscountReason
* paymentTerms
* originalTransactionId
* originalTransactionSaleDate
* company
* country
* region
* technicalContactName
* technicalContactEmail
* billingContactName
* billingContactEmail
* partnerType
* partnerName
* partnerContactEmail
* partnerContactName
* lastUpdated
* transactionLineItemId
* appEdition
---
language: "en"
---
# Type: Support Data
| **Data subjects** | Customers and their contact details |
| **Personal data** | Contacts provided by the users, Logs and debug information provided by the users. |
| **Purpose of processing** | Providing the support |
| **Legal basis for processing** | * Contractual, * For legal reasons (Prove the contractual engagement, etc.). |
| **Retention period** | As long as provided by Atlassian, and 10 years after the last event with the customer. |
| **International transfers** | Hosted in Europe. |
| **Security measures** | The data is stored by Atlassian. |
|--------------------------------|----------------------------------------------------------------------------------------|
## Contents of Support Data
The Support Data is any data provided or gathered during support cases:
* Data provided by the user and customer, which can include logs of Confluence, database excerpts, files, configuration files.
* Data collected in production by the support to investigate issues,
* Data collected in license information to check the customers' support coverage.
---
language: "en"
---
# Types of data
---
language: "en"
---
# Yogi Status & Dropdown for Confluence (Cloud)
## Introduction
[**Yogi Status \& Dropdown**](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview) is a user-friendly tool designed to manage dropdown menus directly within your ++Confluence Cloud++ pages. Insert **a simple dropdown macro** directly into your pages, and choose the list with multiple selectable options.
## Key features
* **Easy dropdown insertion:** Add dropdown macros to any page, allowing users to choose from predefined values.
* **Customize your dropdowns:**Create self-made dropdowns based on your needs, with custom values and colors.
* **Reusable dropdowns:** Create space related dropdowns for easy reuse across multiple pages.
* **Centralized Management:** Manage all your dropdowns from a dedicated management page.
* **Flexible Value Selection:** Change dropdown values in both edit and view modes, depending on the users' permissions.
## Need any help?
If you have any questions regarding functionalities, bugs, feature requests, or simply would like to chat, please reach out on the support: .
*** ** * ** ***
[](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview)
---
language: "en"
---
# Administration
[Yogi Status \& Dropdown is a Confluence Cloud](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview) application, certified [RUNS ON ATLASSIAN](https://marketplace.atlassian.com/collections/runs-on-atlassian).
## How to configure my dropdown macros?
In the Space Apps \> Yogi Status \& Dropdown it is possible to administrate your dropdowns.
* Create dropdowns reusable across one space.
* Modify dropdowns.
* Delete dropdowns.
### Permissions
| **Action** | **Permissions needed** |
|-----------------------------------------------------------------------------------|--------------------------------------------------|
| To create saved dropdowns | 'Edit' space permissions |
| To delete and edit saved dropdowns | 'Space admin' permissions |
| To add a dropdowns on pages and change the value of a dropdown (view / edit mode) | 'View' space permissions 'Edit' page permissions |
### Limitations
* Saved dropdowns can only be used per space. At the moment, once you save a dropdown, you cannot reuse it for the whole instance or share it with other spaces.
* If you modify the value of a saved dropdown, the modifications ++will not++ reflect on your Confluence pages. The macros in pages using the saved dropdown will still display old values if you modified them in the configuration, this implies you will have to modify them manually.
---
language: "en"
---
# Best Practices
[The Yogi Status \& Dropdown app](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview) lets you insert any dropdowns in your Confluence pages. With **1 simple macro**, you can enhance your Confluence experience.
## Formats
The drodpown macro is flexible and fully integrated within Confluence. You can add the macro in plain text at the top of your page to see the overall status. Or, you can also add it in tables for individual items, or project summary.
Now, here are a few use-case.
## Use cases
### Workflows / Process tracking
* **Documentation Status** : *Draft* , *Published* , *Needs Update.*
* **Content Owner Review:** *Pending* , *Scheduled* , *Done.*
* **Knowledge Source** : *Internal SME* , *External Consultant* , *Customer Input*.
* **Review Status** : *Not Reviewed* , *In Review* , *Reviewed* , *Approved*.
* **Sign-off Stage** : *Draft* , *Submitted for Sign-off* , *Signed Off.*
* **Release Status** : *Planned* , *In QA* , *Released* , *Deprecated.*
* **Compliance Check** : *Not Started* , *In Progress* , *Compliant* , *Non-compliant.*
### Track p**erformance \& KPIs state**
* **Metric Trend** : *Improving* , *Stable* , *Declining.*
* **Goal Status** : *On Track* , *At Risk* , *Off Track* , *Achieved.*
* **ROI Expectation** : *Low* , *Moderate* , *High.*
### Project Management
* **Project Status** : *Backlog* , *In Progress* , *Done* , *Won't Do*.
* **Requirement Type** : *Feature* , *Software, Hardware, Design.*
* **Deployment Readiness:** *Ready* , *Blocked* , *Pending Testing* , *Deployed*.
* **Testing:** *Passed, Failed, Blocked, Ignored, In Progress*.
* **Risk Level** : *Low* , *Moderate* , *High*.
* **Budget Status** : *On Budget* , *Over Budget* , *Pending Approval*.
* **Stakeholder Visibility** : *Low* , *Medium* , *High Priority.*
## Have any questions or feature suggestions?
Reach out on the support for any suggestions or questions: .
---
language: "en"
---
# Getting Started
Looking for a way to insert dropdown macros in your confluence pages ? Here's how to get started with [Yogi Status \& Dropdown for Confluence](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview).
## 1. Create your dropdown
Before you get started on adding dropdown in pages, you need to create it in the Administration.
1. Go into the space apps and click on the app
2. Click on '+ New dropdown'
3. Give it a name, and / or a description, start adding values and choosing the colors
4. Save your dropdown.
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|  |  |
## 2. Add the dropdown
Once you have created your first dropdown, any user who has edit permissions on the space will be able to add the macro and choose values.
|-----------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Anywhere in your page, add the macro using `/status` or `/dropdown` or `/yogi`. |  |
| Choose a saved dropdown and select the value. You can reuse that dropdown across all pages in your space. |   |
| You can edit the values in the dropdown from edit mode, or view mode. |   |
### Looking for more features?
Yogi Status \& Dropdown is all new, so please let us know if you'd like to share your feedback and feature suggestions π
---
language: "en"
---
# Release Notes
## New app on the Atlassian Marketplace π
2025-08-04 Version 2.3.0
We have just released the first version for the [Yogi Status \& Dropdown macro](https://marketplace.atlassian.com/apps/1238431/yogi-status-dropdown-for-confluence?hosting=cloud&tab=overview).
Please find out how to get started with [our documentation](https://confluence.intranet.requirementyogi.com/wiki/spaces/ysd/pages/2762145795/Getting+Started?atlOrigin=eyJpIjoiYTNmMjM1NDU5YTMyNGVkYzk5OTcwYzM3MzQ5ZDlhNjQiLCJwIjoiYyJ9), and don't hesitate to read the [best practices](https://confluence.intranet.requirementyogi.com/wiki/spaces/ysd/pages/2776498190/Best+Practices?atlOrigin=eyJpIjoiMWYyOTVkODI4MGNmNDQ5ZWJiNzk2ZWM3NTJiZWEyMDEiLCJwIjoiYyJ9) for use case examples.
We value your feedback, so please reach out to us and let us know if you have any suggestions to improve the app π .
---
language: "en"
---
# Requirement Yogi for Cloud Introduction
## **Requirement Yogi** is a tool designed to help teams create and manage requirements easily in **Confluence.**
**Leverage the power of Confluence rich text editor to define, annotate requirements and much more.**
**Confluence** is great for writing requirement documents, and **Requirement Yogi** takes that to another level and here's why:
* You can easily create and annotate your requirements.
* You can navigate through Confluence pages to see where your requirements were defined and/or cited.
* You can build customized visual reports using our [Traceability matrix](https://docs.requirementyogi.com/cloud/traceability-matrix.md).
* You can search for requirements using our advanced [Search syntax](https://docs.requirementyogi.com/cloud/search-syntax.md).
## Key features
### Search screen
Using our [Search syntax](https://docs.requirementyogi.com/cloud/search-syntax.md), you can easily find requirements and have an overview of the requirement's description, dependencies and links to where it was defined and/or cited.
.png?cb=d265fee41bfa56296dad483aa8321c6c)
### Traceability matrix
Traceability matrix is a powerful tool and fully customizable to build visual reports.
Just start from a set of requirements and easily configure columns to display the information you are interested in.
.png?cb=ffddc297aa539c25d0394d8d4a2fd7a5)
### Page transformation
We know it's difficult to work on large documents with countless of requirements, but we have a solution for you.
Using **Requirement Yogi** you can just copy paste your document into a **Confluence** page, configure your columns and let our plugin handle the rest.
### Other key features:
* [External properties and Estimates](https://docs.requirementyogi.com/cloud/external-properties.md),
* [Variants](https://docs.requirementyogi.com/cloud/variants.md),
* [Requirement Types](https://docs.requirementyogi.com/cloud/requirement-types.md),
* [Calculations](https://docs.requirementyogi.com/cloud/calculations.md),
* [Requirements in paragraphs](https://docs.requirementyogi.com/cloud/linear-documents.md).
**Here is more information about the** [**migration to Cloud.**](https://docs.requirementyogi.com/data-center/migrating-to-the-cloud.md)
*** ** * ** ***
[](https://marketplace.atlassian.com/apps/1212523/requirements-yogi?hosting=cloud&tab=overview)
---
language: "en"
---
# 2022
* [October 2022](https://docs.requirementyogi.com/cloud/october-2022.md)
* [July 2022](https://docs.requirementyogi.com/cloud/july-2022.md)
* [June 2022](https://docs.requirementyogi.com/cloud/june-2022.md)
* [May 2022](https://docs.requirementyogi.com/cloud/may-2022.md)
* [April 2022](https://docs.requirementyogi.com/cloud/april-2022.md)
* [March 2022](https://docs.requirementyogi.com/cloud/march-2022.md)
---
language: "en"
---
# 2023
* [December 2023](https://docs.requirementyogi.com/cloud/december-2023.md)
* [October 2023](https://docs.requirementyogi.com/cloud/october-2023.md)
* [July 2023](https://docs.requirementyogi.com/cloud/july-2023.md)
* [June 2023](https://docs.requirementyogi.com/cloud/june-2023.md)
* [May 2023](https://docs.requirementyogi.com/cloud/may-2023.md)
---
language: "en"
---
# 2024
* [December 2024](https://docs.requirementyogi.com/cloud/december-2024.md)
* [November 2024](https://docs.requirementyogi.com/cloud/november-2024.md)
* [October 2024](https://docs.requirementyogi.com/cloud/october-2024.md)
* [August 2024](https://docs.requirementyogi.com/cloud/august-2024.md)
* [July 2024](https://docs.requirementyogi.com/cloud/july-2024.md)
* [June 2024](https://docs.requirementyogi.com/cloud/june-2024.md)
* [May 2024](https://docs.requirementyogi.com/cloud/may-2024.md)
* [April 2024](https://docs.requirementyogi.com/cloud/april-2024.md)
* [January 2024](https://docs.requirementyogi.com/cloud/january-2024.md)
---
language: "en"
---
# 2025
* [December 2025](https://docs.requirementyogi.com/cloud/december-2025.md)
* [October 2025](https://docs.requirementyogi.com/cloud/october-2025.md)
* [September 2025](https://docs.requirementyogi.com/cloud/september-2025.md)
* [August 2025](https://docs.requirementyogi.com/cloud/august-2025.md)
* [July 2025](https://docs.requirementyogi.com/cloud/july-2025.md)
* [June 2025](https://docs.requirementyogi.com/cloud/june-2025.md)
* [May 2025](https://docs.requirementyogi.com/cloud/may-2025.md)
* [April 2025](https://docs.requirementyogi.com/cloud/april-2025.md)
* [March 2025](https://docs.requirementyogi.com/cloud/march-2025.md)
* [February 2025](https://docs.requirementyogi.com/cloud/february-2025.md)
* [January 2025](https://docs.requirementyogi.com/cloud/january-2025.md)
---
language: "en"
---
# Administrator's guide
There isn't much to administrate in Requirement Yogi, but these are the topics to look out for if your users have questions, or do not have admin permissions:
* [Installation Checklist](https://docs.requirementyogi.com/cloud/installation-checklist.md)
* [RY Champions](https://docs.requirementyogi.com/cloud/ry-champions.md)
* [Cleanup Tasks](https://docs.requirementyogi.com/cloud/cleanup-tasks.md)
* [Rename requirements](https://docs.requirementyogi.com/cloud/rename-requirements.md)
* [Key suggestions](https://docs.requirementyogi.com/cloud/key-suggestions.md)
* [Migrating from DC to Cloud](https://docs.requirementyogi.com/cloud/migrating-from-dc-to-cloud.md)
* [Moving Confluence pages or spaces](https://docs.requirementyogi.com/cloud/moving-confluence-pages-or-spaces.md)
* [Data residency](https://docs.requirementyogi.com/cloud/data-residency.md)
* [Limitations](https://docs.requirementyogi.com/cloud/limitations.md)
* [IPs and domains used by Requirement Yogi](https://docs.requirementyogi.com/cloud/ips-and-domains.md)
* [Identity Providers](https://docs.requirementyogi.com/cloud/identity-providers.md)
## Where is the Administration in Requirement Yogi?
### 1. The Champion Center
This is where space administrators can administrate parts of Requirement Yogi. Instance administrator can assign specific users to be RY Champions to allow them to administer all parts of Requirement Yogi for all spaces. See more information here: [RY Champions](https://docs.requirementyogi.com/cloud/ry-champions.md).
### 2. The cog β Requirement Yogi Administration
*The other path to get to this page is: Confluence settings β Atlassian Marketplace β Requirement Yogi.*
These settings are for the whole Confluence Instance.
* Find the **getting started** help.
* **The roadmap** for features in the Cloud
* **Jira integration tab** will help you connect your Confluence and Jira instances: [Guide to install Requirement Yogi for Jira](https://docs.requirementyogi.com/cloud/requirement-yogi-for-jira-installation.md)
* The**Support tab** , this is where you will find your client-key (needed for our devs to look into logs if you report us a bug). You'll also be able to flush the cache there, and activate the end-points for[Migrating from Server to Cloud](https://docs.requirementyogi.com/data-center/migrating-to-the-cloud.md#Before-migrating:~:text=Open%2520the%2520migration%2520endpoint:).
* **Usage tab**, this is pretty useful for system administrators wanting to know how the app is used by its users and how many requirements are in each space. For example, it is not used sys admins may decide to uninstall the app.
* **GDPR/Exports** , this tab is useful is you plan to uninstall the app and remove all of your data from our servers. [Please find our privacy policy for more information.](https://docs.requirementyogi.com/legal/privacy-policy)
* This is also where you'll be able to trigger a full reindex of all pages β Click on the `RESTORE` button.
* **Champions,** this is where instance administrators will be able to assign users to the RY champion group**.**
## π¬ Subscribe to our release notes
The best way to stay updated about our new features is to click on "Watch App" on the product's page!
* [Requirement Yogi for Confluence \| Marketplace](https://marketplace.atlassian.com/apps/1212523/requirement-yogi-requirements-management-for-confluence?hosting=cloud&tab=overview#:~:text=EULA-,Stop%20Watching%20(106),-Cloud%20Migration)
* [Requirement Yogi for Jira \| Marketplace](https://marketplace.atlassian.com/apps/1214094/requirement-yogi-requirements-management-for-jira?hosting=cloud&tab=overview#:~:text=EULA-,Watch%20App%20(57),-Cloud%20Migration)
## π’ Subscribe to our mailing list
Tune your notifications to the information ++you++ care about:
* Release notes and new features
* Pricing and licensing updates
* Security and vulnerability notifications
* New blogs and videos
* Atlassian Community Q\&A
* Community discussions on new features
[](https://www.requirementyogi.com/cloud-mailing-list/)
---
language: "en"
---
# Advanced: Bulk link requirements to Jira issues
If you want to add a list of requirements to your Jira issues, instead of using the simple edit mode, you can use the Advanced mode.
## How to use the bulk link mode
* Enter a list of requirements.
* The data must be CSV formatted as following (we support any delimiter): `REQUIREMENT_KEY,SPACE_KEY,VARIANT_NAME,RELATIONSHIP_NAME`
* Each requirement definition must be separated by a break line.
* Only the column REQUIREMENT_KEY is mandatory, the others can be replaced by empty column. If empty, we'll add the matching requirements from all spaces.
* This list of requirements will replace all the existing requirements linked to this issue. If you want to add links to an issue that already had links, make sure you leave the other ones as well.
[Next Page](https://docs.requirementyogi.com/llms-full.txt/1)