---
language: "en"
---
# Scrum Manager
## Scrum Manager
Make the most out of your Scrum ceremonies
### Topics
*
#### [Daily Scrum](https://help.view26.com/sm/daily-scrum.md)
* [Capture Updates](https://help.view26.com/sm/capture-updates.md)
* [Scrum Task Review](https://help.view26.com/sm/scrum-task-review.md)
* [Summary](https://help.view26.com/sm/summary.md)
* [Settings](https://help.view26.com/sm/settings.md)
*
#### [Sprint Planning Overview](https://help.view26.com/sm/sprint-planning-overview.md)
* [Creating a Planning Session](https://help.view26.com/sm/creating-a-planning-session.md)
* [Estimating an Item in Synchronous Mode](https://help.view26.com/sm/estimating-an-item-in-synchronous-mode.md)
* [Estimating an Item in Asynchronous Mode](https://help.view26.com/sm/estimating-an-item-in-asynchronous-mode.md)
* [Setting the Planning Session Duration](https://help.view26.com/sm/setting-the-planning-session-duration.md)
* [Setting the Estimate](https://help.view26.com/sm/setting-the-estimate.md)
*
#### [FAQs](https://help.view26.com/sm/faqs.md)
* [Setting up Slack Bot for Scrum Manager](https://help.view26.com/sm/setting-up-slack-bot-for-scrum-manager.md)
---
language: "en"
---
# Accessing the App
**Accessing the App:**
1. Install **VIEW26**App
2. Log in to Jira
3. Click on **Scrum Manager** in the navigation-bar to enter the App.
4. The Boards available will be listed here. Select the Board for Scrum Planning
5. Once the Jira Board is chosen, the **Daily Scrum**opens up by default.
---
language: "en"
---
# Capture Updates
1. Click on :arrow_View: and select **Standup Updates**
2. The **Standup Updates**Page opens up where each team member has to update the 3 daily scrum questions
3. **Drag \& Drop**the tasks into the respective sections -
A. What did I do yesterday
B. What will I do today
C. Are there any impediments- Flag impediments ( if any )
4. Click on the **comment icon**corresponding to the tasks added in the update section. Add comments related to the particular task to provide more context for your team. This comment entered, gets updated in the original Jira Issue comment section.
5. Click on the **Add Note** to add additional comments for issues worked outside of the Sprint Goals
6. Click on the timer icon to update Work log corresponding to the tasks added in the update section.
7. Update Work Log information- Time spent, Time Remaining , Date started \& Time and also the Work Description (The work description entered here gets updated in the Work Log details corresponding to an Issue in Jira.
---
language: "en"
---
# Creating a Planning Session
1. Click on **Sprint Planning** on the left pane to go to Sprint Planning Page
2. **Create New session**to start a Creating a Planning Session
3. Enter **Session Name**
4. The session would be in Synchronous Mode by default for real-time estimation, but you can set the **Async Toggle** ON to enable Asynchronous mode
5. Add the names of **Estimators**
6. Add the list of **Watchers** ,who will observe the planning without providing any estimation
Only users who are **Members** can be added as Estimators and Watchers
7. Click **Next** to continue entering the details
8. Select the issues to be added to the Planning Session
9. Once the items have been selected, click **Create Session**.
10. Your first Planning Session is ready! Click **Join** to get started. If you ever want to delete it, just click the **Delete** button.
---
language: "en"
---
# Daily Scrum
Once the Jira Board is chosen, the **Daily Scrum** opens up by default.
In the **Daily Scrum:**
1. Discuss **Scrum cards** by quickly reviewing each team member's progress on their assigned tasks, any obstacles faced, and planned work for the day, ensuring alignment and transparency.
2. Utilize the **Standup Updates** screen to update the status of tasks and note any impediments that need discussion during the Scrum.
3. Refer to the **Summary** screen to view a heatmap and an overview of the sprint's progress, providing a visual representation of the team's overall performance.
---
language: "en"
---
# Estimating an Item in Asynchronous Mode
Welcome to the Asynchronous Planning Session ! This mode allows team members to cast their votes on Jira issues at their convenience, without needing to coordinate a simultaneous meeting. This flexibility ensures that all team members can participate regardless of their schedules.
**Viewing the Planning Backlog and Cards**
1. Once in the session, the Jira issues to be estimated are displayed on the right under the 'Planning Backlog'.
2. Each item appears as a card. Navigate between items by clicking the arrow (**\>**) next to the card.
3. The current session mode (Asynchronous Mode) is prominently displayed at the top of the screen.
**Voting on Jira Issues**
4. Team members can access the Planning Session at any time. The members review the item and cast their votes using the slider to select their estimate. Members who have not yet voted will be listed in the 'Pending' section, while those who have voted will move to the 'Voted' List.
5. The creator/admin can click on 'Reveal' to view the votes at any time during the session.
**Setting Task Estimates**
7. Once all votes are cast for each card, the 'Review Estimate' button appears in place of the 'Finalize Individual Voting' button allowing the session creator to review the votes and set the estimates.
8. If the creator wants to set estimates without waiting for the entire team, they can click the 'Finalise Individual Voting' button at any point to proceed with the estimation process. This will turn the 'Finalise Individual Voting' button into 'Review Estimates' button.
9. On clicking the 'Review Estimate' button, Planning Session now shifts to Synchronous mode, bringing the entire team together to finalize the estimation.
10. The session creator starts the Timer at the beginning of the session and stops it upon completion. Both the elapsed time and the remaining time for the entire session are displayed. The timer can be paused anytime if necessary.
11. The session creator reveals the votes by clicking the 'Reveal' button at the bottom right of the screen.
redo
11. The 'Reveal' Page displays the votes cast by all team members for that particular card.
12. The creator can set the estimate by moving the slider to the desired number or by entering the number in the textbox below and clicking the 'Set Estimate' button. After setting the estimate for a card, the creator proceeds to the next card for discussion. This process continues for all cards in the Planning Session.
13. Once all the estimates are set, they appear next to the items in the 'Planning backlog'. The Planning Session is now complete.
14. The creator now has the option to 'Restart Game' if needed or select 'Back to Gamelist' to return to the list of Planning sessions.
**Additional Tips:**
**Flexible Participation**: Team members can vote at their convenience, making it easier to accommodate different time zones and schedules.
By following these steps, your team can efficiently estimate tasks in a flexible and collaborative environment, ensuring accurate and agreed-upon task estimates for your sprint.
*** ** * ** ***
---
language: "en"
---
# Estimating an Item in Synchronous Mode
Welcome to the Synchronous Planning Session ! In this mode, the team members (estimators) and the session creator come together in real-time to finalize task estimates. This collaborative approach ensures that all votes are cast and discussed during the session, leading to a consensus on task estimates.
**Viewing the Planning Backlog and Cards**
1. Once in the session, the Jira issues to be estimated are displayed on the right under the 'Planning Backlog'.
2. Each item appears as a card. Navigate between items by clicking the arrow (**\>**) next to the card.
3. The current session mode (Synchronous Mode) is prominently displayed at the top of the screen.
**Timer Management :**
4. The session creator starts the Timer at the beginning of the session and stops it upon completion. Both the elapsed time and the remaining time for the entire session are displayed. The timer can be paused anytime if necessary.
**Discussion and Voting**
5. Team members discuss the item displayed on the card.
6. Each card has a countdown timer, set to a predefined duration from the settings page, displaying the remaining time for that card.
7. Member casts their vote for the item using the slider to select their estimate. Members who haven't voted are listed in the 'Pending' section, while those who have voted move to the 'Voted' List.
8. Once all team members have cast their votes, the session creator reveals the votes by clicking the 'Reveal' button at the bottom right of the screen.
**Setting the Estimate**
9. The 'Reveal' Page displays the votes cast by all team members for that particular card.
10. The creator can set the estimate by moving the slider to the desired number or by entering the number in the textbox below and clicking the 'Set Estimate' button. After setting the estimate for a card, the creator proceeds to the next card for discussion. This process continues for all cards in the Planning Session.
11. Once all the estimates are set, they appear next to the items in the 'Planning backlog'. The Planning Session is now complete.
12. The creator now has the option to 'Restart Game' if needed or select 'Back to Gamelist' to return to the list of Planning sessions.
## Additional Tips
* **Adjusting Estimates**: After revealing the votes, discuss any discrepancies and adjust estimates as needed to reach a consensus.
* **Session Flexibility**: Remember that the timer is flexible and can be paused for extended discussions or breaks.
By following these steps, your team can efficiently estimate tasks in a collaborative and structured environment, ensuring accurate and agreed-upon task estimates for your sprint.
---
language: "en"
---
# FAQs
*** ** * ** ***
| Title | Creator | Modified |
|-----------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------|---------------|---|
| [Setting up Slack Bot for Scrum Manager](https://help.view26.com/sm/setting-up-slack-bot-for-scrum-manager.md) | [Ajay](https://view26.atlassian.net/people/557058:fb9585d6-93fa-43f5-998d-a600a9dd2e9f?ref=confluence) | Sept 02, 2022 | |
---
language: "en"
---
# Quick Start for Scrum Manager
Welcome to VIEW26. Let's get you started with using the App!
## 1. Access the App
1. Install VIEW26 Scrum Manager App
2. Log in to Jira
3. Click on **Scrum Manager** in a Agile Board to enter the app
## 2. Configure Settings
The following options exists for configuring the Scrum Manager board Settings
Ability to configure the time duration of the standup
* By member
* By total duration
Ability to configure the card display order
* By alphabetic order
* By number of items at risk
## 3. Capture Standup Updates - Team Members
1. As a team member provide updates for the daily Scrum by clicking on **Capture Updates** option in the App menu
2. Answer the 3 daily scrum questions by using the drag \& drop feature
3. Add comments to provide more context for your team
4. Flag impediments ( if any )
5. Add additional comments for issues worked outside of the Sprint Goals
6. Submit your Update
## 4. Running Daily Standup - Scrum Master
1. As a Scrum Master click on **Scrum Manager** in a Agile Board to start the daily Scrum ritual
2. Adjust the Scrum Settings for duration/card order.
3. Start the timer to get the Scrum started
4. Take notes by pining Tasks or adding comment(s)
5. Add additional comments for issues worked outside of the Sprint Goals
6. Stop the Timer at the end of the Scrum
## 4. Track progress - Scrum Master
1. Stop the Timer to close the meeting
2. View the Summary page to check the Work-Timeline \& Heat-map reports
3. Use the reports to gain a better understanding of work in progress, identify bottlenecks, and monitor Sprint progress.
---
language: "en"
---
# ๐ Release Notes
## 2023-06-r1
### New Feature
[QR-661](https://view26.atlassian.net/browse/QR-661) Work-Timelines support
## 2023-04-r1
### New Feature
[AA-203](https://view26.atlassian.net/browse/AA-203) Support for Kanban Board
#### Improvement
[AA-241](https://view26.atlassian.net/browse/AA-241) Timer experience improvement
---
language: "en"
---
# Retrospective
The **Retrospective** feature helps gather collective retrospective for the Sprint
1. Click on Retrospective on the left pane
2. All the users who join will participate in the session
3. The creator starts the time.
4. Each user can add '**What went well** ' and '**What could be improved**'
5. Keeping the timer in mind, the creator reveals the Retrospective comments once the users have updated them.
6. The team can discuss the inputs provided that is now visible to all.
7. The action items can also be discussed and added to the section on the right
---
language: "en"
---
# Scrum Task Review
The Daily Scrum enables team members to stay informed about each other's progress and challenges, promoting a more efficient and organized scrum call.
1. As soon as you enter app, you are taken to the 'Daily Scrum' page. You can also get here by clicking on 'Daily Scrum' on the left tab.
2. Here each team member has a card displayed during the scrum call. The card provides details on the Tasks assigned to that particular team member. The Standup Updates (entered by the team member in the standup updates section ) on the tasks the team member is working on today, yesterday's tasks, and any blockers are all updated within the tasks.
3. The session creator starts the Timer at the beginning of the session and stops it upon completion. Both the elapsed time and the remaining time for the entire session are displayed. The timer can be paused anytime if necessary.
4. Each card has a countdown timer, set to a predefined duration from the settings page, displaying the remaining time for that card. The card owner provides updates on their work and any impediments within this allotted time.
5. The count of tasks the team member is working on today, on the yesterday's tasks and on any blockers displayed on the top of each card. The additional comments for issues worked outside of the Sprint Goals appear on the card above all tasks.
6. The Notes section on the right can be used to capture any updates that require follow-up for the current sprint. These notes can be assigned to a particular member, and a due date can also be specified. Once a follow-up activity is completed, it can be ticked off to indicate its completion. This ensures that important follow-up actions are tracked, assigned, and completed efficiently.
7. There are two views available for a card:
1. **Standup Updates View**: This view displays all updates entered in the 'Standup Updates' screen.
2. **Current Sprint Task View**: This view shows only the tasks for the current sprint.
You can switch between these views by clicking the icon on the left.
8. After the updates for a particular card have been discussed, the Scrum Master proceeds to the next card for discussion by clicking the arrow (**\>**) next to the card.
9. The followup screen displays all the followups for the sprint. This is usually the first card in the Daily Scrum.
10. Once all cards have been discussed, the daily Scrum concludes with the scrum master stopping the timer or ending the session by clicking the 'End Scrum' button. This action directs the team to the sprint 'Summary' screen.
---
language: "en"
---
# Setting the Estimate
On the Reveal Page, the votes for each card are revealed.
1. The creator can set the Estimate by moving the slider to the desired number or by entering the number in the textbox below and clicking the **Set Estimate** button
2. The creator can click on **Restart Game** to start the game all over again if required or **Create new Game**.
3. Once the estimate is set, it gets updated next to the Item on the right.
---
language: "en"
---
# Setting the Planning Session Duration
1. Click on the โ๏ธ icon next to 'Planning' on the left.
2. You can set the Planning Session duration by individual card or for the entire session.
3. Configure the game admins (only game admins can start, stop, restart the game, and set estimates).
---
language: "en"
---
# Setting up Slack Bot for Scrum Manager
Step-by-step guide on installing and setting up the Scrum bot companion for Jira Scrum manager on slack.
## Instruction
1. Visit and Click the Add to Slack Button.
2. This button should redirect you to the slack oauth page where you can select the slack workspace(top right of page) to install the app onto by clicking allow.
3. Clicking allow will install the app and redirect you to a page with a link to open the slack app,which takes you to the Scrum Bot Homepage (The bot should also message you on slack on installation) where there will be further instructions on it's usage
## Setting up the bot in slack
### Instructions
1. Add the bot to a channel either by choosing a channel from the drop down in the home page .
2. 
Use the command "@scrumbot setup " to initiate the setup for that channel(Note: the reminder will be sent one hour prior to the selected time)
Enter the URL of the global page of the scrum manager app.
Ex - https://\.atlassian.net/plugins/servlet/ac/com.view26.scrum.manager/view26-app\&slack=true
This should set up the bot to send reminders one hour prior to the selected time, to each user in the channel individually.
Use "@scrumbot help" to see the other commands available and what they do.
---
language: "en"
---
# Settings
1. Click on the โ๏ธ icon next to 'Daily Scrum' on the left.
2. You can set the Scrum duration by individual member or for the entire session
3. Additionally, you can configure the card display order either alphabetically by name or by the number of items at risk.
---
language: "en"
---
# Sprint Planning Overview
Planning in Scrum Manager is an interactive estimation app designed to invigorate project planning across all team types --- hybrid, in-person, or remote.
Seamlessly integrated with Atlassian this app transforms traditional task estimation into an engaging, collaborative game. Ideal for any team dynamic, it ensures ease of use and accuracy in generating task estimates, making project planning both fun and efficient.
**Key Features:**
* **Seamless Integration:** Effortlessly import tasks from your Monday workspace into our intuitive planning game.
* **Easy Setup:**Get up and running quickly with straightforward session setups. Assign roles for watchers and estimators and control timer settings for a streamlined experience.
* **Flexible Estimation Approaches:** Choose between synchronous for real-time estimation, or asynchronous estimation to accommodate busy schedules with an option for team members to vote when it suits them.
* **Unbiased Voting System:** Ensure fair inputs with a voting system that reveals estimates only after all participants have contributed.
* **Transparent Tracking:** Monitor who has voted and view their estimates at any time, fostering transparency and accountability within your team.
* **Enhance Team Collaboration:**With Planning in Scrum Manager, you'll not only improve estimation precision but also boost team synergy.
The app's engaging format encourages active participation and collective decision-making, making it ideal for hybrid, remote, or in-person teams.Ready to estimate? Empower your team with Planning in Scrum Manager
**Accessing the App:**
1. Install
**VIEW26**App
1. Log in to Jira
1. Click on
**Charts and Reports** in the navigation-bar to enter the App
---
language: "en"
---
# Summary
The Summary Page provides a comprehensive overview of the sprint's progress and activities. It consists of two main tabs:Timeline and Heatmap
**Timeline**: This new feature provides a graphical visualisation of the Jira issue activity for team members involved in the sprint.
**Heatmap**:
1. A burndown chart is shown for a visual representation of progress
2. A detailed heatmap of the sprint is displayed.
3. Here each colored box in the table below is interactive and can be clicked to view specific sprint updates.
4. It also shows the percentage of time elapsed, work completed, scope changes, blockers, and flagged tasks.
This 'Summary' aids in understanding the overall timeline and identifying any issues that need attention, ensuring an efficient and organized review of the sprint.
---
language: "en"
---
# Attachment Tags for Jira
## Attachment Tags for Jira
Attachment Tags helps organise and categorise attachments in Jira . It helps perform global search on labelled attachments without the need for searching attach...
[Get Started](https://help.view26.com/atfj/quick-start-for-attachment-tags.md)
### Topics
*
#### [๐ Quick Start for Attachment Tags](https://help.view26.com/atfj/quick-start-for-attachment-tags.md)
* [๐ Basics](https://help.view26.com/atfj/basics.md)
---
language: "en"
---
# 1. View all Attachments linked to an Issue
## 1. Access the App
1. Log in to Jira
2. Navigate to the issue with attachments
3. Click on **Manage Labels**on the glance page on the right
## 2. Getting list of Attachments
1. The Attachments Tag glance page opens up
2. All files / documents attached to the particular issue gets listed on this page
---
language: "en"
---
# 2. Add new Labels to attachments
1. Click on **+ Add Label** or anywhere on the grey box for the attachment (Here in this example we create a label for the attachment *Charts And Reports Video.mp4)*
2. Enter the new **Label Name** (*demo-video* in this case)
3. Select the **Colour** for the label
4. Click on **Create**
---
language: "en"
---
# 3. Add existing Labels to attachments
1. Click on **+ Add Label** or anywhere on the grey box for the attachment (Here in this example we create a label for the attachment *Charts And Reports Audio.mp3)*
2. From the list of existing labels select label name to be tagged to this attachment (*voice-over, draft* , *demo-video* are existing labels in this case). You can add multiple labels to a single attachment.
3. Select the **Colour** for the label
4. Click on **Create**
---
language: "en"
---
# 4. View Labels added to attachments within an Issue
The added labels would be listed under each attachment. You can add more than one label to an attachment
In the example below, the labels *voice-over* and *draft* have been added to the attachment *Charts And Reports Audio.mp3.* And the label *demo-video* has been added to the attachment *Charts And Reports Video.mp4*
---
language: "en"
---
# 5.ย Sorting attachments by Uploader or Uploader date
# 5. Sorting attachments by Uploader or Uploader date
It is possible to sort the attachments by uploader or upload date by choosing the appropriate option from the drop-down
---
language: "en"
---
# 6.ย Search attachments
# 6. Search attachments
1. Click on **Attachment Tags** under Apps to Navigate to the Attachment Tags Home Page
Or
2. Click on **Attachment Tags Icon**on the Glance Page within an Issue
3. All the attachments would be listed with the label information
4. The attachments tagged to a particular Label / Labels can be filtered out
---
language: "en"
---
# ๐ Basics
This App helps you tag attachments with labels and categorize and search attachments easily.
Select one of the following topics:
* [1. View all Attachments linked to an Issue](https://help.view26.com/atfj/1-view-all-attachments-linked-to-an-issue.md)
* [2. Add new Labels to attachments](https://help.view26.com/atfj/2-add-new-labels-to-attachments.md)
* [3. Add existing Labels to attachments](https://help.view26.com/atfj/3-add-existing-labels-to-attachments.md)
* [4. View Labels added to attachments within an Issue](https://help.view26.com/atfj/4-view-labels-added-to-attachments-within-an-issue.md)
* [5. Sorting attachments by Uploader or Uploader date](https://help.view26.com/atfj/5-sorting-attachments-by-uploader-or-uploader-date.md)
* [6. Search attachments](https://help.view26.com/atfj/6-managing-attachments.md)
* [7. Editing Labels in Settings Page](https://help.view26.com/atfj/editing-labels-in-settings-page.md)
---
language: "en"
---
# 7. Editing Labels in Settings Page
## 1. Getting to Settings Page
To edit the Labels at any point, get to the Settings Page by either :
1. Clicking on Settings icon :setting:on the right top of the Attachment Tags Home Page or
Or
1. Clicking on Settings Icon
:setting: on the Attachment Tags glance page
## 2. Editing Labels in Settings Page
1. Click on Edit to edit the Label.
2. It is possible to rename the Label or change the colour of the Label
3. A Label that is no longer required can be deleted
4. Can't find a Label you are looking for? Look it up on top right of the Page
---
language: "en"
---
# ๐ Quick Start for Attachment Tags
Welcome to VIEW26. Let's get you started with using the App!
## 1. Access the App
1. Log in to Jira
2. Navigate to the issue with attachments
3. Click on **Manage Labels**on the glance page on the right
## 2. Getting list of Attachments
1. The Attachments Tag glance page opens up
2. All files / documents attached to the particular issue gets listed on this page
## 3. Add new labels to attachments
1. Click on **+ Add Label** or anywhere on the grey box for the attachment (Here in this example we create a label for the attachment *Charts And Reports Video.mp4)*
2. Enter the new **Label Name** (*demo-video* in this case)
3. Select the **Colour** for the label
4. Click on **Create**
## 4. Add existing labels to attachments
1. Click on **+ Add Label** or anywhere on the grey box for the attachment (Here in this example we create a label for the attachment *Charts And Reports Audio.mp3)*
2. From the list of existing labels select label name to be tagged to this attachment (*voice-over, draft* , *demo-video* are existing labels in this case)
3. Click on **Create**
## 5. View Labels added to Attachments
The added labels would be listed under each attachment. You can add more than one label to an attachment
## 6. Sorting attachments by Uploader or Uploader date
It is possible to sort the attachments by uploader or upload date by choosing the appropriate option from the drop-down
## 7. Search attachments
1. Click on **Attachment Tags** under Apps to Navigate to the Attachment Tags Home Page
2. All the attachments would be listed with the label information
3. The attachments tagged to a particular Label / Labels can be filtered out
## 8. Getting to Settings Page
To edit the Labels at any point, get to the Settings Page by either :
1. Clicking on Settings icon :setting:on the right top of the Attachment Tags Home Page or
Or
2. Clicking on Settings Icon :setting: on the Attachment Tags glance page
## 9. Editing Labels in Settings Page
1. Click on Edit to edit the Label.
2. It is possible to rename the Label or change the colour of the Label
3. A Label that is no longer required can be deleted
4. Can't find a Label you are looking for? Look it up on top right of the Page
---
language: "en"
---
# Storyboard AI
## Storyboard AI
Description Convert your frames into a video in few simple steps, using prebuilt templates, audio and captions
### Topics
*
#### [๐ Basics](https://help.view26.com/storyboard-ai/basics.md)
* [Introduction to Storyboard AI](https://help.view26.com/storyboard-ai/introduction-to-storyboard-ai.md)
* [Installation](https://help.view26.com/storyboard-ai/installation.md)
*
#### [Understanding Core Features](https://help.view26.com/storyboard-ai/understanding-core-features.md)
* [Projects and Sharing](https://help.view26.com/storyboard-ai/projects-and-sharing.md)
* [Frame Editor](https://help.view26.com/storyboard-ai/frame-editor.md)
* [Templates](https://help.view26.com/storyboard-ai/templates.md)
* [Audio \& Captions](https://help.view26.com/storyboard-ai/audio-captions.md)
* [Cover Frame](https://help.view26.com/storyboard-ai/cover-frame.md)
* [1 more pages](https://help.view26.com/storyboard-ai/understanding-core-features.md)
---
language: "en"
---
# Audio \& Captions
## Voices
Pick one of our voices for narration. Click โถ next to a voice to hear a short sample first.
* George (Warm Storyteller)
* Sarah (Confident)
* Alice (Clear Educator)
* Liam (Energetic)
* Matilda (Professional)
* Roger (Laid-Back)
### AI-generated scripts
Describe the tone you're going for ("friendly product demo," "fast-paced social ad," etc.) and give a brief description of what each frames are and click Generate Scripts
The AI drafts a narration line for each frame based on your description and the frame names you've set. Edit the drafts inline to polish the scripts if required.
### Captions
Captions are timed word-by-word to the narration, so each highlight lines up perfectly with the spoken audio.
### Caption Styles
| **Style** | **Look** |
|-----------|-----------------------------------------------------------|
| TikTok | Bold uppercase, one word glowing at a time, bottom-center |
| Subtitle | Classic centered subtitles with a soft fade-in |
| Karaoke | Words light up as they're spoken, with a subtle slide-up |
| Minimal | Small text in the lower-left with a thin accent bar |
| None | No captions |
For any style you can tweak the accent color, background opacity, and font size.
---
language: "en"
---
# ๐ Basics
---
language: "en"
---
# Cover Frame
An optional intro card that plays before your first content frame --- useful for title slides on social posts.
* **Title and subtitle** --- centered text.
* **Background** --- solid color or gradient. Follows the template by default.
* **Duration** --- 3 seconds by default, adjustable.
* **Show/hide** --- toggle the cover off without losing your settings.
* **Add Logo**(optional) --- Add a logo which will be visible in the cover frame(centre of cover, above the title and subtitle) and throughout the video(top left/right, bottom left/right)
---
language: "en"
---
# FAQs
## 1. What is Storyboard AI?
Storyboard AI turns your screenshots and screen recordings into short, narrated videos --- right inside Confluence. Drop in your assets, let AI draft the script, pick a voice, and get a polished MP4 with captions.
### 2. Who is it for?
Product managers, technical writers, designers, customer success, and marketing --- anyone producing demo, announcement, onboarding, or walkthrough videos directly from a set of assets. No previous video creation experience required
### 3. Where do I use it?
Inside Confluence Cloud, in any modern desktop browser, simply install the app from Atlassian Marketplace. You don't need to install anything else or manage rendering --- we handle that in the background.
### 4. Are there templates to get me started?
Yes --- three presets so you don't start from a blank canvas:
* Product Walkthrough --- widescreen, karaoke-style captions
* LinkedIn Post --- square, punchy TikTok-style captions
* In-App Docs --- widescreen, clean subtitle captions
You can tweak anything (aspect ratio, voice, caption style, cover frame) from the left panel once you're in the editor.
### 5. What voices and languages can I use?
Six curated voices --- George, Sarah, Alice, Liam, Matilda, and Roger --- covering a range of English accents. Need another language? Reach out and we'll enable it for you.
### 6. Can the AI write my narration?
Yes. Click **Generate scripts** to draft narration for every frame based on your project title and frame content that you describe in the prompt. Generated text is fully editable before rendering.
### 7. What can I upload?
* Images: PNG, JPG, WebP, GIF, SVG
* Videos: MP4, WebM, MOV
* Max size: 200 MB per file
### 8. What export formats are available?
An MP4. You can render up to 2K (2560ร1440 for widescreen and vertical, 2048ร2048 for square).
### 9. Will the captions match the voiceover?
Yes --- captions are timed word-by-word to the narration, so each word lights up exactly when it's spoken.
### 10. If I tweak the script or voice, do I have to re-render the whole video?
You'll have to click **Generate Video** again to get the new output --- but behind the scenes, only the frames you actually changed are regenerated. Everything else reuses what's already there
### 11. Who can see my projects?
Only the project Owner, invited Editors, and invited Viewers. Storyboard AI does not expose projects to other Confluence users by default, even inside the same space.
### 12.What happens if someone on my team leaves Confluence?
Their personal info is automatically cleared from Storyboard AI, in line with Atlassian's privacy requirements. Any projects they owned stay accessible to the other owners.
---
language: "en"
---
# Frame Editor
1. The editor has two main areas:
* **Left sidebar** --- icons for Template, Audio \& Captions and Cover Settings. Click one to open that panel.
* **Main area** --- your frames, shown as cards you can edit directly.
2. Working with a frame
* **Upload media** --- click **Add Frames** upload images or videos as frames. Click an existing thumbnail to see it full-size.
* **Frame name** --- click to edit. Saves as you type.
* **Script** --- write the narration for this frame. Saves as you type.
* **Duration** --- for image frames without narration, set how long the frame stays on screen. For video frames, the clip's own length is used by default.
* **Mute video** --- mute or unmute a video's audio while keeping your narration.
* **Edit / split a video** --- click the scissor icon in video frames to open video edit tool to set the in/out point, or cut one video into several frames. We can then work on the newly created frames
* **Zoom targets** (for image frames) --- draw rectangles on an image to tell the camera where to zoom. Link each zoom to a span of words in your script so the zoom happens exactly when that phrase is spoken.
* **Transition** --- choose how this frame flows into the next (fade, slide, etc.). You can apply your choice to all frames in one click.
* **Reorder** --- drag a frame up or down to change its position.
* **Delete** --- remove the frame.
---
language: "en"
---
# Generating Video
1. Click **Generate Video** in the top right.
2. We prepare your frames and narration (audio is regenerated only for frames you've changed).
3. The video is rendered in the cloud.
4. Progress is shown in the Renders panel --- you can close the editor and come back; the render continues in the background.
5. When done, the Renders panel shows a Download MP4 button.
6. The previous rendered videos can be accessed from the **Generated Videos** section in the dashboard, where videos are grouped by projects
---
language: "en"
---
# Getting Started
After installation, Storyboard AI is available as a **global page** under the **Apps** menu.
1. **Access the App**
* From your Confluence page, click **Apps** in the navigation
* Select **Storyboard AI** from the dropdown menu
2. **Create your first project**
* Click **New project**
* Choose a template, give title and create the project
* Choose **Product Walkthrough** , **LinkedIn Post** , or **In-App Docs** to apply a preset (aspect ratio, default voice, caption style, transitions, and cover background) in one click. You can always switch to **Manual** mode to tweak any setting individually.
3. **Add frames**
* Click **Add Frames** button to select one or multiple frames
* Supported formats: PNG, JPG, WebP, GIF, SVG, MP4, WebM, MOV. Maximum asset size: **200 MB**.
* Drag to reorder the frames
4. **Write narration**
* Enter narration text for the frame. Storyboard AI auto-saves as you type.
* You can also click **Generate scripts** to have an AI draft narration for every frame by giving a brief idea of what the frames are; edit freely before rendering.
5. **Add Zoom Targets**
* Click on **'+'** to select an area of the image uploaded to draw focus to that area
* Drag along the words in the script to focus the selected area when that script is narrated
6. **Edit Template**
* Choose a different template, audio, caption style from the left panel
* Add, remove or edit the cover frames
* Add logo branding
7. **Render and Download** **Video**
* Click **Generate Video**
* Storyboard AI synthesizes voiceover (if narration was written), builds captions from word-level timestamps, and renders the video
* Once generated, preview the video and **download** it
---
language: "en"
---
# Installation
Storyboard AI installs from the Atlassian Marketplace into any Confluence Cloud site. Follow these simple steps to integrate Storyboard AI to your confluence
## Requirements
* A **Confluence Cloud** site
* A user with **"Manage apps"** permission (site administrator)
* A modern browser (latest Chrome, Firefox, Safari, or Edge)
## Installation Steps
1. Visit the **Atlassian Marketplace** and search for **"Storyboard AI"**.
2. Click **Get it now** (or **Try it free** for a trial).
3. Select the Confluence site to install into and confirm.
4. Review and accept the requested permissions:
* Read Confluence space, user, and content summaries
* Access app storage
* Request an app system token for the rendering backend
5. Wait for installation to finish. The app provisions its database schema automatically on first launch --- no manual setup required.
6. Open Confluence and click **Apps โ Storyboard AI** in the global navigation.
---
language: "en"
---
# Introduction to Storyboard AI
**Storyboard AI** turns a series of screenshots, screen recordings, or design assets into a narrated, captioned video --- all from inside Confluence. It is built for product, design, and enablement teams who need to ship short demo, social posts and walkthrough videos quickly, without switching tools.
Choose from existing templates and create videos in a few simple steps
## **Key Features**
* **Frame-based editor** --- Build a video scene by scene. Upload images or video clips, write narration, set durations, and rearrange frames with drag-and-drop.
* **AI narration scripts** --- Generate first-draft narration from a topic or outline; edit inline before rendering.
* **Voiceover** --- Pick from a curated set of voices. Audio is generated with word-level timestamps, so captions stay perfectly in sync.
* **Four caption styles** --- TikTok, Subtitle, Karaoke, and Minimal. Customize accent color, background opacity, and font size.
* **Templates** --- Start from a preset (Product Walkthrough, LinkedIn Post, In-App Docs) or configure every setting manually.
* **Zoom targets** --- Draw focus rectangles on a still image and tie zoom timing to narration words for Ken-Burns style emphasis.
* **Download:** Generate the video and download it in a single click
* **Collaboration** --- Share projects with teammates as Owner, Editor, or Viewer, and handle access requests without leaving the app.
## Who Is It For?
* **Product teams** producing feature announcements and changelog videos
* **Technical writers** adding walkthrough clips to Confluence documentation
* **Design teams** sharing prototypes with voice-over
* **Sales and marketing** creating short LinkedIn or landing-page demos
* **Customer success** packaging how-to clips for onboarding spaces
---
language: "en"
---
# Projects and Sharing
Each project stores:
* A title
* Video dimensions and frame rate (default 30 fps)
* A list of frames in order
* Your style settings (template, captions, colors, transitions, cover)
* Your recent renders(videos generated)
From the dashboard you can:
| Action | What it does |
|-------------|------------------------------------------------|
| New project | Creates a blank project with one starter frame |
| Open | Opens the frame editor |
| Delete | Removes the project and its uploaded media |
| Share | Invite teammates as editors or viewers |
## Sharing a Project
Invite teammates to collaborate on a project:
* Owner --- full control (edit, render, delete, share).
* Editor --- can edit frames and render.
* Viewer --- can watch and download completed renders.
Shared projects appear in a teammate's dashboard automatically. Access requests can be approved or rejected from the owner's notification banner.
---
language: "en"
---
# Templates
Templates set everything at once --- aspect ratio, voice, caption style, transition, and cover color --- so you can start fast.
| Template | Default Aspect ratio | Voice | Captions | Transition | Cover |
|---------------------|----------------------|-------|----------|------------|---------------|
| Product Walkthrough | 16:9 (1080p) | Liam | Karaoke | Fade | Black |
| LinkedIn Post | 1:1 (Square) | Liam | TikTok | Slide-left | LinkedIn blue |
| In-App Docs | 16:9 (1080p) | Sarah | Subtitle | Fade | Light grey |
Prefer to set things yourself? Switch to Manual mode in the Template panel and customize any piece.
**Aspect ratios \& resolutions**
* 16:9 landscape --- 720p, 1080p, 1440p
* 9:16 portrait --- 720p, 1080p, 1440p
* 1:1 square --- 1080, 1440, 2K
* Custom --- any size between 320px and 3840px
---
language: "en"
---
# Understanding Core Features
1. [Projects and Sharing](https://help.view26.com/storyboard-ai/projects-and-sharing.md)
2. [Frame Editor](https://help.view26.com/storyboard-ai/frame-editor.md)
3. [Templates](https://view26.atlassian.net/wiki/pages/resumedraft.action?draftId=3411804161&draftShareId=60a9f74f-f25e-43fe-a5a6-24adbe413573&atlOrigin=eyJpIjoiNjk3OTkyOTkxMjY4NDdhNmJjNzMwZjQyYWVhNzBiNmMiLCJwIjoiYyJ9)
4. [Audio \& Captions](https://help.view26.com/storyboard-ai/audio-captions.md)
5. [Cover Frame](https://help.view26.com/storyboard-ai/cover-frame.md)
6. [Generating Video](https://help.view26.com/storyboard-ai/generating-video.md)
---
language: "en"
---
# Use Cases
## 1. Feature Announcement Video
A product manager captures four screenshots of a new feature, types three sentences of narration per screenshot, picks the **In-App Docs** template, and hits **Generate Video**. Two minutes later they have a subtitled MP4 ready to embed on the release-notes page.
### 2. LinkedIn Teaser
A growth marketer duplicates last week's project, swaps the screenshots, switches the template to **LinkedIn Post** (1:1, TikTok captions, LinkedIn-blue cover), and renders a square MP4 ready for the company page.
### 3. Documentation Walkthrough
A technical writer drops a screen-recording into a single frame, splits it into three frames at key moments, writes narration for each, and ties zoom targets to the phrase "click here" --- producing a polished, narrated walkthrough that replaces a 600-word how-to section.
### 4. Design Review Clip
A designer uploads hi-fi Figma exports frame by frame, picks the **Karaoke** caption style, enables the cover frame for a title, and shares the project with stakeholders as **Viewers** so they can watch without editing the source.
---
language: "en"
---
# Legal Home
## Legal Home
### Topics
*
#### [EULA](https://help.view26.com/legal/eula.md)
* [Cloud General Terms and Conditions](https://help.view26.com/legal/cloud-general-terms-and-conditions.md)
* [Data Center General Terms and Conditions](https://help.view26.com/legal/data-center-general-terms-and-conditions.md)
* [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md)
*
#### [Policies](https://help.view26.com/legal/policies.md)
* [Support Service Level Agreement (SLA)](https://help.view26.com/legal/support-service-level-agreement-sla.md)
* [Security Bug Fixing Policy](https://help.view26.com/legal/security-bug-fixing-policy.md)
* [App Function Description](https://help.view26.com/legal/app-function-description.md)
* [Technical and organizational measures](https://help.view26.com/legal/technical-and-organizational-measures.md)
---
language: "en"
---
# App Function Description
Click the app name to learn more about its key functionality:
* [Charts and Reports for Jira Service Management](https://marketplace.atlassian.com/apps/1217341/charts-and-reports-for-jira-service-management)
* [Page View Analytics for Confluence Cloud](https://marketplace.atlassian.com/apps/1218023/page-view-analytics-for-confluence-cloud)
* [Scrum Standup Manager for Jira](https://marketplace.atlassian.com/apps/1227145/scrum-standup-manager-for-jira)
* [JSON Viewer Macro for Confluence](https://marketplace.atlassian.com/apps/1217397/json-viewer-macro-for-confluence)
* [Community Lens](https://marketplace.atlassian.com/apps/1226382/community-lens)
---
language: "en"
---
# Cloud General Terms and Conditions
These Cloud General Terms and Conditions are accompanied by the [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md).
## 1 Scope of these Cloud General Terms and Conditions
### 1.1 Scope of application
(1) These Cloud General Terms and Conditions ("**Cloud GTC** ") shall apply if you as a customer (hereinafter, "**Customer** ") access one of our (VIEW26 GmbH, Duisburg, Germany) software solutions for the current basic Atlassian Software (e.g. Confluence; Jira) (hereinafter, "**Software** ") available on the Atlassian Marketplace via a telecommunications connection and the data generated by the use of the Software and/or the data required for the use of the Software (hereinafter, "**Application Data**"), including our support services which we provide in connection with the respective Software.
(2) Our Cloud GTC apply exclusively. Conflicting, additional or deviating terms and conditions of the Customer shall not become part of the agreement unless we have expressly agreed that they apply. Our Cloud GTC shall also apply if we provide a service without reservation while being aware of conflicting or deviating conditions of the Customer.
(3) Our Cloud GTC apply only if the Customer is an entrepreneur (ยง 14 German Civil Code, "BGB"), a legal entity under public law or a special fund under public law.
### 1.2 Subject matter of the agreement
(1) The agreement covers:
(a) the Software selected by the Customer in its most current version. Please click [here](https://help-view26.atlassian.net/wiki/pages/resumedraft.action?draftId=391250000) for the function description.
(b) our support services during the agreement's term, including documentation. For the scope of our support services please click [here](https://help.view26.com/legal/support-service-level-agreement-sla.md).
(2) We do not owe any additional Software qualities and/or further services. In particular, the Customer may not deduce such an obligation from other representations of the Software or our services in public statements or in advertising by our sales partners, unless we have expressly confirmed such a quality.
## 2 Special agreements on the use of the Software
### 2.1 Provision of Software; Storage space for Application Data
(1) We keep the Software available for use on a central data processing system or several data processing systems (hereinafter, "**Server**").
(2) We keep storage space available on the server for the Application Data.
(3) The Software and Application Data shall be backed up on the server on a regular basis, at least every calendar day. The Customer is responsible for compliance with commercial and tax record retention periods.
(4) The point of interconnection for the Software and Application Data is the exit router of our data center.
(5) We are not responsible for the quality of the necessary hardware and software on the part of the Customer or for the telecommunications connection between the Customer and our company up to the point of interconnection.
(6) Delays in performance due to force majeure, e.g. strike or lockout in third companies or in our company (in the latter case, however, only if the labour dispute is lawful), official orders, statutory prohibitions, general disruptions of telecommunications or other circumstances beyond the control of the Customer (hereinafter, "**Force Majeure**") or circumstances within the sphere of influence of the Customer, e.g. delay in cooperating, delays by third parties attributable to the Customer, etc., entitle our company to postpone the provision of the services concerned for the duration of the hindrance plus a reasonable start-up period. If said event of force majeure continues for more than three months, both parties shall be released from their obligation to perform. Our further (statutory) claims or rights, in particular arising from delay of acceptance by the Customer, remain unaffected.
(7) Otherwise the provisions of Article 4.2 shall otherwise apply to claims by the Customer for damages or reimbursement of unnecessary expenses in the event that delivery is delayed, or performance is impossible.
### 2.2 Technical availability of the Software; Access to Application Data
(1) We undertake to provide the following availability of the Software and Application Data at the point of interconnection. The parties agree that availability shall mean the Software and Application Data technical usability at the point of interconnection for use by the Customer.
(2) The annual average availability of the Software shall be 99.5%.
(3) The available use (given availability) also includes the periods during which
a) malfunctions occur in or due to the condition of technical infrastructure's parts required for the execution of the Software which are not to be provided by us or our agents;
b) only an insignificant reduction in fitness for contractual use occurs;
c) maintenance work is carried out in accordance with para. 4.
(4) We carry out maintenance work each Friday, 7:00 am Central European Time (CET).
### 2.3 Free test phase; Agreement's term; Termination
(1) The Customer may initially test the Software free of charge for a period of one month ("**Free Trial Period**"). Within the Free Trial Period we provide support services to the best of our ability without being obliged to do so.
(2) The Customer can choose the term of the agreement on the Atlassian Marketplace according to the options available therein. The term is automatically extended by the originally selected term, unless the agreement is terminated by either party at the end of the term.
(3) The right of each party to extraordinary termination for good cause shall remain unaffected.
(4) Termination can be declared by clicking the button "Unsubscribe" within the administration of the basic Software (see Article 1.1 (1)).
(5) After termination of the contractual relationship the Software may no longer be used.
### 2.4 Further development; Updates
(1) We continuously aim to further improve the Software. There is no entitlement to a specific further development. Further development of the Software can lead to an extension and/or modification of the Software with the result that new functionalities are available, existing functionalities in the process and/or the user guidance are optimised, or the data management is adapted to the state of the art.
(2) The Customer may inform itself about innovations and updates via the means available on the Atlassian Marketplace.
(3) If necessary, the Customer administrator of the basic Software can update the Software to the latest version by clicking on "Update" in the administration of the basic Software.
### 2.5 Customer obligations to cooperate
(1) The Customer shall fulfil all obligations required to perform the agreement. It shall in particular
(a) take the necessary precautions to prevent unauthorised use of the application. In particular, it will ensure that no unauthorized third party can access the application by means of suitable protective measures (e.g. password strength, passwords on its computers, burglary protection). The Customer shall inform us immediately if it believes that access data and/or passwords may have become known to unauthorised persons;
(b) create and maintain the access, functional and system requirements agreed in the order as well as other requirements for the use of the application;
(c) ensure that the users authorized to use the application are sufficiently familiar with the operation of the application on the part of the Customer, in particular that the users receive sufficient training;
(d) ensure that (e.g. when transmitting information of third parties to our server) all rights of third parties to material used by the same are observed;
(e) inform its employees about our data processing for optimisation purposes and their right to object at any time in accordance with section 4.5 as soon as it grants them access to the software
(f) if relevant, check data and information about viruses before sending them to our company and use state-of-the-art virus protection programs;
(g) only send encrypted user data;
(h) cause entitled users to comply with the provisions of this Agreement applicable to them.
(2) The Customer is aware of the essential functional features of the Software and was able to test them within the Free Trial Period. The Customer bears the risk that the Software meets its requests and needs.
(3) The Customer shall be solely responsible for setting up a functional hardware and software environment for the Software of sufficient size to take into account the additional load caused by the subject matters covered by the agreement.
(4) The Customer shall bear any disadvantages and additional costs resulting from a breach of these obligations.
### 2.6 Data backup by the Customer; Liability for loss of data
(1) Provided that the Customer is given the technical opportunity to do so via our software, it will regularly back up the data stored on the server by downloading it to its own computer system.
(2) The Customer shall store its data backups in such a way that the backed-up data may be restored at any time.
(3) Our company shall not be liable for the loss of Customer data insofar as the damage is due to the Customer failing to carry out data backups and thereby ensuring that lost data can be restored with reasonable effort, contrary to its obligation under paragraphs 1 and 2. In all other respects, Article 4.2 shall apply.
### 2.7 Rights of Use; Software protection
(1) Unless the Customer is expressly granted rights under this agreement, our company exclusively holds all rights to the Software - in particular copyright, rights to or as part of inventions and technical intellectual property rights. This also applies to processing of the Software by us.
(2) We grant the Customer a simple right, that may not be transferred or sub-licensed, to use the Software in accordance with the provisions of the functional description and (supplementary) of these Cloud GTC. This right of use may at the same time only be exercised simultaneously by the maximum number of users for whom the Customer also owns Atlassian basic Software license (e.g. Confluence, Jira).
(3) The Customer shall not be entitled to transfer access to the Software to third parties.
### 2.8 Warranty
(1) We guarantee that the software has the agreed quality during the license period. It is not afflicted with defects that cancel or reduce the value or suitability for normal use or the use stipulated in the contract. This includes the non-existence of malicious program parts ("viruses").
(2) If the Customer notifies us of a defect, we are obliged, at our discretion, to immediately remedy the defect or to deliver a replacement free of defects.
(3) The Customer shall support us in the error analysis and elimination of defects, in particular by specifically describing any problems that occur, providing us with comprehensive information and granting us the time and opportunity required to remedy the defects reported.
(4) If we perform services in the search for or removal of defects without being obliged to do so, we may demand remuneration in accordance with our usual hourly rates. This applies in particular if a defect cannot be proven, cannot be reproduced or is not attributable to us.
(5) Warranty claims shall become statute-barred within one year of the software being provided by us.
## 3 Special agreements on the provision of support services
We provide Software support services during the term of the agreement in accordance with the following provisions (hereinafter, "**Support and Update Services**").
### 3.1 Scope of Support and Update Services
(1) The Support and Update Services include the handling of errors or other defects of the software that become known regardless of its use by the Customer, unless specified otherwise below.
(2) Our Support and Update Services do not include:
(a) Services for the software if the latter is not used under the conditions of use specified by us;
(b) Application and adaptation of interfaces and APIs;
(c) Handling errors caused by the Customer or by third parties, including the disruption of operations caused by third-party software;
(d) Services for computer programs or parts thereof that are not included in the software;
(e) Services which can be performed at our registered office, but which are performed at another location at the express request of the Customer;
(f) Instructing and training software users; and
(g) Services that become necessary because the Customer does not comply with its obligations to cooperate according to Article 2.5.
(3) We provide our support via a ticketing system (see [view26- Help Center](https://view26.atlassian.net/servicedesk/customer/portal/2) ). We are not required to provide a telephone hotline.
(4) Support for the Customer shall be provided during our working hours Monday-Friday, with the exception of public holidays in Germany, from 9:00 a.m. to 5:00 p.m. Central European Time (CET).
(5) Pending defect claims of the Customer (Article 2.8) are not included in support services and remain unaffected by the same.
### 3.2 Customer cooperation and obligations with regard to Support and Update Services
(1) The Customer shall provide us with the necessary information in the event of a support request and shall cooperate in answering its request, in particular by:
(a) providing the relevant documents, documentation and information required for the provision of services, in particular concerning existing systems, devices, computer programs and computer program parts which are to interact with our Software;
(b) documenting detected defects of services rendered in a reproducible, at any rate comprehensible form and immediately informing us about said defects;
(c) making available at its own expense facilities, infrastructures and personnel suitable for cooperation, insofar as necessary for the provision of services;
(d) performing necessary acts of cooperation in due time.
(2) The Customer shall name at least one contact person. We shall be immediately informed about any changes regarding in the contact person. The contact person shall have experience in handling the Software and must be able to provide information on the installation environment and the Software error reported in the event of queries from us. The Customer shall grant the contact person a corresponding authorisation to represent the Customer, in particular to also receive declarations from us.
(3) Prior to reporting the error, the Customer shall carry out an analysis of the system environment within the scope of its possibilities to ensure that the error is not attributable to system components that are not covered by this Agreement.
(4) As long as the Customer is in default with carrying out the required actions our company will be entitled to suspend performance of those services that without said Customer's actions cannot be performed at all or can only be performed with disproportionate additional expense. Any additional expenditure actually caused shall be reimbursed to our company by the Customer in addition to the agreed remuneration on the basis of our applicable hourly rates. Our further legal rights remain unaffected.
### 3.3 Defects in support services
(1) The support services are subject to the statutory provisions on service contracts (ยงยง 611 ff. BGB).
(2) We shall only be liable for damages due to a defect in our support services within the limits specified in Article 4.2.
## 4 General provisions
The following provisions apply to all of our aforementioned services (software lease and Support and Update Services):
### 4.1 Fee; Payment
(1) The fee for our services depends on the number of users and can be found under the heading "Cloud Pricing" on the Atlassian Marketplace. The prices are net prices, i.e. not including applicable value-added tax.
(2) Billing will be carried out via Atlassian Pty Ltd., which we have authorised to collect our claims in its own name.
### 4.2 Liability
(1) Both parties are liable for damages due to the violation of contractual obligations to the extent that they are at fault.
(2) The amount of liability for simple negligence shall be limited to the damage typically foreseeable for the damaging party at the time of the breach of duty, however, limited to a maximum amount of US-$ 10,000 per damaging event.
(3) Liability for loss of profit is excluded.
(4) We shall not be liable for the loss of data to the extent that the damage is due to the fact that the Customer has failed to carry out regular data backups ensuring that lost data can be restored with reasonable effort.
(5) Non-contractual liability remains unaffected.
### 4.3 Third party rights
(1) If third parties assert claims against the Customer due to infringement of intellectual property rights in connection with the services rendered by us, we shall indemnify the Customer against these claims and shall cover all necessary and reasonable costs of legal action.
(2) If the Customer is sued by third parties, the Customer shall coordinate with us and shall take legal action, in particular acknowledgements and settlements, only with our consent. We shall defend ourselves against claims by third parties at our own expense if they are based on our attributable breach of duty.
(3) If third parties assert claims which prevent the Customer from exercising the rights of use granted to him in this agreement, the Customer shall inform us immediately in text form. At the same time, he authorizes us to conduct legal actions against third parties both in and out of court on our own.
### 4.4 Confidentiality
(1) The parties shall remain silent about all confidential matters, in particular business or trade secrets, which come to their knowledge in the course of the preparation, execution and performance of this contract and shall neither pass them on nor exploit them in any other way.
(2) The obligation of confidentiality does not apply if the information in question is to be disclosed pursuant to a court order, an administrative order or a law. The parties shall inform each other without delay of the disclosure and shall disclose the information in such a way as to preserve confidentiality to the greatest extent possible.
### 4.5 Data protection; Data processing
(1) We comply with the rules of data protection, in particular if we are granted access to the Customer's establishment or its hardware and software. We ensure that our agents also comply with these provisions, in particular we oblige them to maintain data secrecy before commencing their activities. We do not intend to process or use personal data on behalf of the Customer. If the Customer cannot exclude access by us to its personal data, the parties will conclude the following agreement for data processing: [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md) .
(2) In order to continuously improve the software, we collect the following data during the access to the software by the user:
* Usage of individual functions
* Installation environment
* Errors in frontend code
(3) The data is collected and analysed by a processor who is subject to the Data Processing Addendum linked in 4.5 (1). Once analyzation is completed, the data will be deleted. Under no circumstances will the data be passed on to third parties.
(4) Insofar as the Customer collects, processes or uses personal data when using the application, it shall obtain the consent of the respective person affected if not otherwise authorized.
### 4.6 Export and import control
(1) The Customer is aware that the services under this agreement may be subject to export and import restrictions. In particular, there may be licensing obligations, or the use of the Software or associated technologies may be subject to restrictions in certain countries.
(2) The Customer shall comply with the applicable export and import control regulations of the Federal Republic of Germany, the European Union and the United States of America as well as all other relevant regulations.
(3) The performance of the agreement by us is subject to the proviso that there are no obstacles to performance due to national and international export and import law provisions or any other statutory provisions.
### 4.7 Quotation as reference
We are entitled to use the Customer's name including its logo as a reference for advertising purposes. If the Customer does not agree, it can send an e-mail to at any time, together with a request to cease use. We will comply with this request immediately.
### 4.8 Final provisions
(1) The Customer may only transfer rights and obligations arising from or in connection with this agreement to third parties with our prior consent in writing.
(2) Place of performance is our registered office in Duisburg, Germany.
(3) Insofar as the Customer is a merchant within the meaning of the German Commercial Code ("HGB"), a legal entity or special fund under public law, the place of jurisdiction for any disputes arising from the business relationship between our company and the Customer shall be our registered office in Stuttgart, Germany. We shall also be entitled to file suit at the Customer's place of business as well as at any other admissible place of jurisdiction.
(4) The relations between us and the Customer are subject to the law of the Federal Republic of Germany exclusively. The United Nations Convention on Contracts for the International Sale of Goods of 11 April 1980 (CISG) shall not apply.
---
language: "en"
---
# Data Center General Terms and Conditions
## 1 Scope of these Data Center General Terms and Conditions
### 1.1 Scope of application
(1) These Data Center General Terms and Conditions ("**Data Center GTC** ") apply to the lease of software by our company, view26 GmbH, Duisburg, Germany, to you as a customer (hereinafter, "**Customer** "), if you lease one of our Software solutions for the current basic Software of Atlassian (e.g. Confluence, Jira) via the Atlassian Marketplace for download and installation on your own system (hereinafter, "**Software**"), including our support services, which we provide in connection with the respective Software.
(2) Our Data Center GTC apply exclusively. Conflicting, additional or deviating conditions of the Customer from these Data Center GTC shall not become part of the agreement unless we have expressly agreed that they apply. Our Data Center GTC shall also apply if we provide a service without reservation while being aware of conflicting or deviating conditions of the Customer.
(3) Our Data Center GTC shall only apply if the Customer is an entrepreneur (ยง 14 German Civil Code, "BGB"), a legal entity under public law or a special fund under public law.
### 1.2 Subject matter of the agreement
(1) The agreement covers:
(a) the Software selected by the Customer in its most current version at the time of the conclusion of the agreement. Please click [here](https://help-view26.atlassian.net/wiki/pages/resumedraft.action?draftId=391250000)for the function description.
(b) our support services for the period of time selected by the Customer on the Atlassian Marketplace for support and update services including documentation. For the scope of our support services please click [here](https://help.view26.com/legal/support-service-level-agreement-sla.md).
(2) We do not owe any additional Software qualities and/or further services. In particular, the Customer may not derive such an obligation from other representations of the Software or our services in public statements or in advertising by our sales partners, unless we have expressly confirmed such a quality.
(3) The Customer is entitled to download a previous version from the Atlassian Marketplace instead of the most current version. However, we do not guarantee compatibility with other software and the security of such older versions (see [Security Bug Fixing Policy](https://help.view26.com/legal/security-bug-fixing-policy.md)).
(4) The above provisions shall apply mutatis mutandis to updated versions of the Software which we make available to the Customer for download at our free discretion during the term of the agreement.
## 2 Special agreements for the Software lease
### 2.1 Provision of the Software
(1) We provide the Software for download on the Atlassian Marketplace.
(2) The Customer receives the Software as an executable program. The source code of the Software is not part of the agreement.
(3) Delays in performance due to force majeure, e.g. strike or lockout in third companies or in our company (in the latter case, however, only if the labour dispute is lawful), official orders, statutory prohibitions, general disruptions of telecommunications or other circumstances beyond the control of the Customer (hereinafter, "**Force Majeure**") or circumstances within the sphere of influence of the Customer, e.g. delay in cooperating, delays by third parties attributable to the Customer, etc., entitle our company to postpone the provision of the services concerned for the duration of the hindrance plus a reasonable start-up period. If said event of force majeure continues for more than three months, both parties shall be released from their obligation to perform. Our further (statutory) claims or rights, in particular arising from delay of acceptance by the Customer, remain unaffected.
(4) Otherwise the provisions of Article 4.2 shall otherwise apply to claims by the Customer for damages or reimbursement of unnecessary expenses in the event that delivery is delayed, or performance is impossible.
### 2.2 Free test phase; Agreement's term; Termination
(1) The Customer may initially test the Software free of charge for a period of one month ("**Free Trial Period**"). At the Customer's request the Free Trial Period is extended up to a total of six months. Within the Free Trial Period we provide support services to the best of our ability without being obliged to do so.
(2) The lease following the Free Trial Period has a term of up to twenty-four months and ends thereafter without the need for termination.
(3) The right of each party to extraordinary termination for good cause shall remain unaffected.
(4) After termination of the contractual relationship the Software can no longer be used.
### 2.3 Further developments; Updates; End of Life; Compatibility
(1) We aim at continuously further developing the Software. There is no entitlement to a specific further development. The further development of the Software can lead to an extension and/or modification of the Software with the result that new functionalities are available, existing functionalities in the process and/or the user guidance are optimised, or the data management is adapted to the state of the art.
(2) Further developments of the Software will be made available for download as an update or new version on the Atlassian Marketplace.
(3) For a period of two years, we support versions of our Software older than the most current version only by providing security patches for critical security vulnerabilities ("**End of Life**"). We expressly point out that beyond this period of time, neither compatibility with the current basic Software of Atlassian (e.g. Confluence, Jira) nor sufficient security of such previous versions is guaranteed. If we provide updates, they will be compatible with versions of Atlassian's Software (e.g. Confluence; Jira) released within the last two years.
### 2.4 Customer obligations to cooperate
(1) The Customer shall be obliged to keep the Software up to date at all times during the term of the agreement, in particular to install upgrades and new versions of the Software immediately after we have notified the Customer accordingly. To be informed by us about the latest upgrades and versions of the Software, the Customer undertakes to log in to the "Watch" function. Without a corresponding registration, a Customer can always view the latest version of a Software under the history version, which can be found for the relevant product on the Atlassian Marketplace under "Versions \> See all versions". We inform the Customer about critical security updates in any case without the latter having to take any action; the information is sent to the contact data entered by the Customer on [https://my.atlassian.com](https://my.atlassian.com/). We shall only provide our support services if the Software is up to date with the latest version delivered by us.
(2) The Customer is aware of the essential functional features of the Software and was able to test them within the Free Trial Period. The Customer bears the risk that the Software meets its requests and needs.
(3) The Customer shall be solely responsible for setting up a functional hardware and Software environment for the Software of a size that is sufficient to take into account the additional load caused by the subject matters covered by the agreement.
(4) The Customer shall thoroughly test the Software before use to verify any defects and usability in the existing hardware and Software configuration. This also applies to Software which the Customer receives within the scope of warranty and, where applicable, maintenance.
(5) The Customer shall comply with our Company's instructions for the installation and operation of the Software; it shall regularly keep up to date with our company's current instructions on the website accessible via the Internet at [Help Desk](https://view26.atlassian.net/servicedesk/customer/portal/4) and take them into account during operation.
(6) The Customer shall bear any disadvantages and additional costs resulting from a breach of these obligations.
### 2.5 Data backup by the Customer; Liability for loss of data
(1) The Customer shall take appropriate measures for the event that the Software does not work properly in whole or in part (e.g. daily data backup, fault diagnosis, regular checking of data processing results). In particular, the Customer shall carry out a complete backup of all system and application data immediately before each update or installation of a newer version of the Software. The data backups shall be stored in such a way that the backed-up data may be restored at any time.
(2) Our company shall not be liable for the loss of Customer data insofar as the damage is due to the Customer failing to carry out data backups and thereby ensuring that lost data can be restored with reasonable effort, contrary to its obligation under paragraph 1. In all other respects, Article 4.2 shall apply.
### 2.6 Rights of Use; Software protection
(1) Unless the Customer is expressly granted rights under this agreement, our company exclusively holds all rights to the Software (and all copies made by the Customer) - in particular copyright, rights to or in inventions and technical intellectual property rights. This also applies to processing of the Software by our company.
(2) We grant the Customer a simple right, that may not be transferred or sub-licensed, to use the Software in accordance with the provisions of the functional description and (supplementary) of these Data Center GTC. This right of use may at the same time only be exercised by the maximum number of users for whom the Customer also owns an Atlassian basic Software license (e.g. Confluence, Jira).
(3) The Customer shall not be entitled to transfer the Software to third parties. In particular, it shall not sell, transfer, grant, lease or sublicense the Software in any other way, publicly reproduce the Software or make it accessible or install it on the systems of third parties. If the Customer intends to install our Software on the servers of third parties, a separate, individual agreement between the Customer and our company is required.
(4) Reproductions of the Software are only permitted insofar as they are necessary for contractual use. The Customer may make backup copies of the Software in accordance with the rules of technology to the extent necessary. Backup copies on movable data carriers shall be labeled as such and marked with a copyright notice.
(5) The Customer is only entitled to make changes, extensions and other modifications to the Software within the meaning of ยง 69c Nr. 1 and 2 of the German Act on Copyright and Related Rights ("UrhG") to the extent that this is unconditionally permitted under the Act on Copyright and Related Rights. Before the Customer itself rectifies defects or instructs a third party to do so, it shall first allow our company to attempt to rectify the defect. The Customer is not entitled to rights of use and exploitation in such processing beyond the rights of use granted under this agreement.
(6) The Customer shall only be entitled to decompile the Software within the scope of ยง 69e UrhG and only if we have not provided the necessary data and/or information in writing within a reasonable period of time following a corresponding request to do so in order to establish interoperability with other Software.
(7) Any supplement (e.g. patches, bug fixes) or new version of the subject matter of the agreement (e.g. update, new version) provided by our company to the Customer to replace the previously provided Software version when remedying a defect shall also be subject to the provisions of these Data Center GTC.
(8) The Customer shall not change or remove any of our copyright notices, marks and/or control numbers or symbols.
### 2.7 Warranty
(1) We guarantee that the software has the agreed quality during the license period. It is not afflicted with defects that cancel or reduce the value or suitability for normal use or the use stipulated in the contract. This includes the non-existence of malicious program parts ("viruses").
(2) If the Customer notifies us of a defect, we are obliged, at our discretion, to immediately remedy the defect or to deliver a replacement free of defects.
(3) The Customer shall support us in the error analysis and elimination of defects, in particular by specifically describing any problems that occur, providing us with comprehensive information and granting us the time and opportunity required to remedy the defects reported.
(4) The Customer's rights due to defects shall be excluded insofar as the Customer makes or has made changes to the subject matter of the agreement without our consent, unless the Customer proves that the changes do not have any effects on the analysis and elimination of the defects that are unreasonable for us. The Customer's rights due to defects shall remain unaffected if the Customer is entitled to make changes, in particular within the scope of exercising the right to self-cleaning in accordance with ยง 536a para. 2 German Civil Code ("BGB"), and if these changes have been carried out professionally and documented in a comprehensible manner.
(5) If we perform services in the search for or removal of defects without being obliged to do so, we may demand remuneration in accordance with our usual hourly rates. This applies in particular if a defect cannot be proven, cannot be reproduced or is not attributable to us.
(6) Warranty claims shall become statute-barred within one year of the software being provided by us.
## 3 Special agreements on the provision of support services
We provide Software support services during the term of the agreement in accordance with the following provisions (hereinafter, "**Support and Update Services**").
### 3.1 Scope of Support and Update Services
(1) The Support and Update Services also include the handling of errors or other defects that become known in the Software regardless of its use by the Customer, unless specified otherwise below.
(2) Our Support and Update Services do not include:
(a) Services for the Software if the latter is not used under the conditions of use specified by us;
(b) Adaptation of the Software to a changed hardware or software environment, including adjustment to changed operating systems;
(c) Application and adaptation of interfaces and APIs;
(d) Handling of errors caused by the Customer or by third parties, including the disruption of operations caused by third-party software;
(e) Services for the Software if the latter previously has been modified by programming work not carried out by us;
(f) Services for computer programs or parts thereof that are not included in the Software;
(g) Services for the Software when updates or other bug fixes provided by us have not been installed and the reported bug has already been fixed therein, unless the installation is unreasonable for the Customer for reasons beyond its control;
(h) Services which can be performed at our registered office, but which are performed at another location at the express request of the Customer;
(i) Instructing and training Software users; and
(j) Services that become necessary because the Customer does not comply with its obligations to cooperate according to Article 2.4.
(3) We provide our Support and Update Services only for the latest Software version that we have made available on the Atlassian Marketplace.
(4) We provide our support via a ticketing system (see [https://help.view26.com](https://view26.atlassian.net/servicedesk/customer/portal/4)). We are not required to provide a telephone hotline.
(5) Support for the Customer shall be provided during our working hours Monday-Friday, with the exception of public holidays in Baden-Wรผrttemberg, Germany, from 9:00 a.m. to 5:00 p.m. Central European Time (CET).
(6) Pending defect claims of the Customer (Article 2.7) are not included in support services and remain unaffected by the same.
### 3.2 Cooperation and Customer obligations with regard to Support and Update Services
(1) The Customer shall provide us with the necessary information in the event of a support request and shall cooperate in answering its request, in particular by:
(a) providing the relevant documents, documentation and information required for the provision of services, in particular concerning existing systems, devices, computer programs and computer program parts which are to interact with our Software;
(b) providing test plans and test data and, where applicable, create and provide a test environment;
(c) documenting detected defects of services rendered in a reproducible, at any rate comprehensible form and immediately informing our company;
(d) making available at its own expense facilities, infrastructures and personnel suitable for cooperation, insofar as necessary for the provision of services;
(e) performing necessary acts of cooperation in due time.
(2) The Customer shall name at least one contact person. We shall be immediately informed of any changes in the contact person. The contact person shall have experience in handling the Software and must be able to provide information on the installation environment and the Software error reported in the event of queries from our company. The Customer shall grant the contact person a corresponding authorisation to represent the Customer, in particular also to receive declarations from our company.
(3) Prior to reporting the error, the Customer shall carry out an analysis of the system environment within the scope of its possibilities to ensure that the error is not attributable to system components that are not covered by this Agreement.
(4) The Customer shall immediately install updates and carry out other troubleshooting measures provided by us.
(5) The Customer shall thoroughly test the Software before use to verify any defects and usability in the existing hardware and software configuration. This also applies to software which the Customer receives within the scope of warranty.
(6) The Customer guarantees permanent management of the system environment. The Customer will continuously service the system environment (hardware and software), in which the software is running.
(7) As long as the Customer is in default with carrying out the required actions our company will be entitled to suspend performance of those services that without said Customer's actions cannot be performed at all or can only be performed with disproportionate additional expense. Any additional expenditure actually caused shall be reimbursed to our company by the Customer in addition to the agreed remuneration on the basis of our applicable hourly rates. Our further legal rights remain unaffected.
### 3.3 Defects in support services
(1) The support services are subject to the statutory provisions on service contracts (ยงยง 611 ff. BGB).
(2) Our company shall only be liable for damages due to a defect in our support services within the limits specified in Article 4.2.
## 4 General provisions
The following provisions apply to all of our aforementioned services (Software lease as well as Support and Update Services):
### 4.1 Fee; Payment
(1) The fee for our services depends on the number of users and can be found under the heading "Data Center Pricing" on the Atlassian Marketplace. The prices are net prices, i.e. not including applicable value-added tax.
(2) Billing will be carried out via Atlassian Pty Ltd., which we have authorised to collect our claims in its own name.
### 4.2 Liability
(1) Both parties are liable for damages due to the violation of contractual obligations to the extent that they are at fault.
(2) The amount of liability for simple negligence shall be limited to the damage typically foreseeable for the damaging party at the time of the breach of duty, however, limited to a maximum amount of US-$ 10,000 per damaging event.
(3) Liability for loss of profit is excluded.
(4) We shall not be liable for the loss of data to the extent that the damage is due to the fact that the Customer has failed to carry out regular data backups ensuring that lost data can be restored with reasonable effort.
(5) Non-contractual liability remains unaffected.
### 4.3 Third party rights
(1) If third parties assert claims against the Customer due to infringement of intellectual property rights in connection with the services rendered by us, we shall indemnify the Customer against these claims and shall cover all necessary and reasonable costs of legal action.
(2) If the Customer is sued by third parties, the Customer shall coordinate with us and shall take legal action, in particular acknowledgements and settlements, only with our consent. We shall defend ourselves against claims by third parties at our own expense if they are based on our attributable breach of duty.
(3) If third parties assert claims which prevent the Customer from exercising the rights of use granted to him in this agreement, the Customer shall inform us immediately in text form. At the same time, he authorizes us to conduct legal actions against third parties both in and out of court on our own.
### 4.4 Confidentiality
(1) The parties shall remain silent about all confidential matters, in particular business or trade secrets, which come to their knowledge in the course of the preparation, execution and performance of this contract and shall neither pass them on nor exploit them in any other way.
(2) The obligation of confidentiality does not apply if the information in question is to be disclosed pursuant to a court order, an administrative order or a law. The parties shall inform each other without delay of the disclosure and shall disclose the information in such a way as to preserve confidentiality to the greatest extent possible.
### 4.5 Data protection
We comply with the rules of data protection, in particular if we are granted access to the Customer's establishment or its hardware and software. We ensure that our agents also comply with these provisions, in particular we oblige them to maintain data secrecy before commencing their activities. We do not intend to process or use personal data on behalf of the Customer. If the Customer cannot exclude access by us to its personal data, the parties will conclude the following agreement for data processing: [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md) .
### 4.6 Export and import control
(1) The Customer is aware that the services under this agreement may be subject to export and import restrictions. In particular, there may be licensing obligations, or the use of the Software or associated technologies may be subject to restrictions in certain countries.
(2) The Customer shall comply with the applicable export and import control regulations of the Federal Republic of Germany, the European Union and the United States of America as well as all other relevant regulations.
(3) The performance of the agreement by our company is subject to the proviso that there are no obstacles to performance due to national and international export and import law provisions or any other statutory provisions.
### 4.7 Quotation as reference
We are entitled to use the Customer's name including its logo as a reference for advertising purposes. If the Customer does not agree, it can send an e-mail to at any time, together with a request to cease use. We will comply with this request immediately.
### 4.8 Final provisions
(1) The Customer may only transfer rights and obligations arising from or in connection with this agreement to third parties in writing with our prior consent.
(2) Place of performance is our registered office in Duisburg, Germany.
(3) Insofar as the Customer is a merchant within the meaning of the German Commercial Code ("HGB"), a legal entity under public law or special fund under public law, the place of jurisdiction for any disputes arising from the business relationship between our company and the Customer shall be our registered office in Stuttgart, Germany. We shall also be entitled to bring any actions at the Customer's place of business as well as at any other admissible place of jurisdiction.
(4) The relations between our company and the Customer are subject to the law of the Federal Republic of Germany exclusively. The United Nations Convention on Contracts for the International Sale of Goods of 11 April 1980 (CISG) shall not apply.
---
language: "en"
---
# Data Processing Addendum
Agreement on the processing of personal data ordered pursuant to Article 28 paragraph 3 General Data Protection Regulation (hereinafter "GDPR") between the **Customer** **(hereinafter referred to as the "Controller")** and **view26 GmbH, Hansastrasse 1-3,47058 Duisburg, Germany (hereinafter referred to as the "Processor")** -- with **Controller und Processor together referred to as the "Parties"** .
## ยง1 Scope of the Agreement
(1) Within the framework of performance of the Main Agreement (Annex 1), it is necessary for the Processor to deal with personal data for which the Customer is the Controller, as defined by Article 4 paragraph 7 GDPR (hereinafter referred to as " Customer Data "). This Agreement contains the provisions, in particular, the data protection rights and obligations of the Parties, concerning the Processor's handling of Customer Data for performance under the Main Agreement.
The order covers the service described in the Main Agreement.
(2) Without prejudice to (3) below, the Processor shall process the personal data exclusively in a Member State of the European Union or in a state that is a party to the Agreement on the European Economic Area.
(3) If the Processor has the processing of personal data handled in a third country (i.e. outside the European Union or a state that is a party to the Agreement on the European Economic Area), it shall require the Controller's prior written or electronically documented consent and shall only occur to the extent that the special requirements of Article 44 et seq . of the GDPR are met.
## ยง2 Nature, scope and purpose of the order processing
(1) The Processor shall process Customer Data only on behalf of (ยง1 (1) hereof) and upon documented instructions from the Controller as defined by Article 28 paragraph 3(a) GDPR. The respective Main Agreement is the basis of the processing operations to be carried out by the Processor. By installing the respective product, the Processor issues the instructions for data processing. Additional instructions are sent via the communication channel in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3).
(2) The Processor shall exclusively process the Customer Data as described in [Annex 2](https://help.view26.com/legal/data-processing-addendum.md#annex2) hereto, in terms of nature, scope and purpose. The processing of Customer Data by the Processor relates exclusively to the categories of data subjects subsequently described in [Annex 2](https://help.view26.com/legal/data-processing-addendum.md#annex2) hereto. The Processor is prohibited from any Customer Data processing that deviates from or extends beyond this, in particular use of the Customer Data for its own purposes. In view of the nature of the Agreement, the Controller acknowledges that the Processor can neither maintain nor review the table referred to in [Annex 2](https://help.view26.com/legal/data-processing-addendum.md#annex2). The Controller is obliged to notify the Processor of all required changes to the list in [Annex 2](https://help.view26.com/legal/data-processing-addendum.md#annex2) via the specified communication channel ([Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3)). The Controller is also obliged not to provide the Processor any personal data not covered by [Annex 2](https://help.view26.com/legal/data-processing-addendum.md#annex2) until the table has been updated accordingly.
## ยง3 Authority of the Controller
(1) The Processor shall exclusively process the Customer Data in accordance with the provisions contained in this Agreement and other instructions from the Controller.
(2) The Controller shall issue all instructions and orders in writing or documented electronic format.
(3) The Controller is obliged to confidentially treat all knowledge of the Processor's business secrets and data security measures acquired within the framework of the contractual relationship. This obligation shall remain in force even after termination of this Agreement.
(4) Those authorized and entitled by the Controller are specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3). For the issuance of instructions, the communication channel specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3) shall be used.
(5) As a rule, instructions are to be issued by the Controller's authorized representative or substitute. The Controller shall notify the Processor of any change in those authorized to act or their substitutes, naming a representative as soon as possible via the communication channel specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3). Until such notification has been received by the Processor, those specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3) shall continue to be authorized to issue instructions.
(6) The Processor is to notify the Controller of any change in those entitled, their substitutes, or of the permanent prevention of the latter, with a representative named via the communication channel specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3). Until such notification has been received by the Controller, those specified shall continue to be considered as entitled to receive instructions from the Controller.
(7) If the Processor is reasonably of the opinion that an instruction from the Controller infringes this Agreement or the applicable data protection law (see Article 28 paragraph 3 sentence 2 GDPR), it must notify the Controller immediately. After timely prior notification to the Controller of at least a 14-day period, the Processor is to suspend implementation of the instruction pending confirmation or change of instruction by the Controller. If the Controller confirms the instructions with a brief justification in writing, the Processor is obliged to follow them. In this case, the Parties agree that the Controller alone shall be liable for the lawfulness of the processing.
## ยง4 Rights and duties of the Controller
(1) Externally, in particular to third parties and data subjects, the Controller is solely liable for the assessment of the lawfulness of the personal data processing pursuant to Article 6 paragraph 1 GDPR and for the protection of the rights of data subjects pursuant to Articles 12-22 GDPR. Nevertheless, as far as legally permissible, the Processor is obliged to forward all requests by data subjects to the Controller, as far as these are recognizably directed to the Controller. The Processor shall assist the Controller appropriately in answering requests from data subjects (such as rectification, erasure and restriction of processing) and is entitled to charge reasonable compensation for this.
(2) The Controller is the owner of the Customer Data and, in the relationship of the parties to each other, holder of any rights to the Customer Data.
(3) The Controller shall be responsible for providing the Customer Data to the Processor in good time for contractual performance under the Main Agreement. Further, the Controller shall be liable for the quality and lawfulness of collection of the Customer Data. The Controller must notify the Processor immediately and fully if it finds errors or irregularities regarding data protection regulations or its instructions when examining the results contracted.
(4) In the event that a third party or data subject brings a claim directly against the Processor for violations of rights and/or related claims, the Controller undertakes to indemnify the Processor for all damages, costs/fees, including legal or other expenses or losses arising from the claim, to the extent that the Processor has notified the Controller of the assertion of the claim and has given it the opportunity to cooperate with the Processor in defending against the claim.
## ยง5 Rights and duties of the Processor
(1) The Processor is obliged to process personal data exclusively within the framework of the Agreements made pursuant to the instruction of the Controller. This shall not apply if the Processor is obliged to perform other processing under the law of the EU or of Member States to which the Processor is subject (e.g. investigations by state authorities or law enforcement agencies). In this case, the Processor shall notify the Controller of these legal requirements prior to processing, unless the law in question prohibits such notification due to a significant public interest (see Article 28 paragraph 3 (a) GDPR).
(2) The Processor shall not use the Customer Data provided by the Controller for processing for any other purpose, in particular for its own purposes. The Processor shall not make copies or duplicates of the Customer Data without the Controller's prior written consent, to the extent and as long as not required to ensure proper data processing and performance of the services under the Main Agreement (including data backup) or compliance with statutory retention requirements.
(3) The Processor shall not hand Customer Data over to third parties or other recipients without the Controller's prior written consent. Exceptions to this include data transfers to subcontrollers whose assignment the Controller has accepted pursuant to ยง10 (5).
(4) The Processor shall only provide third parties or authorities with information about personal Controller Data from this contractual relationship, to the extent legally permissible, after prior written or electronically documented instructions or approval by the Controller.
(5) If the Controller is obliged to provide information about the Controller Data or the processing thereof to a governmental body, data subject or another person, the Processor is obliged to assist the Controller in the provision of such information, at first request, in particular by immediately providing all information and documents concerning the contractual processing of the Customer Data, including the technical/organisational measures taken by the Processor, the technical procedure in using the Customer Data, the locations where the Customer Data is used and the employees involved in the processing.
(6) The Processor undertakes to:
ยท fulfil the rights of the data subjects under Article 12-22 GDPR,
ยท fulfil the obligation under Article 32-36 GDPR,
ยท prepare directories of processing activities,
ยท the required data protection impact assessments of the Controller,
ยท as well as comply with the Controller's obligations regarding to the security of the processing
The Processor undertakes to cooperate to the extent necessary and adequately assisting the Controller as far as possible (see Article 28 paragraph 3 (e) and (f) GDPR). The respective information required for this shall be forwarded to the Controller entity specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3).
(7) The Processor shall be obliged to rectify, erase or restrict the processing of personal data resulting from this contractual relationship if the Controller so requests by means of a written or electronically documented instruction and this does not conflict with the Processor's legitimate interests, in particular the observance of statutory provisions.
(8) Both Controller and Processor shall agree on making any change in the processing subject matter or procedure. This change shall be recorded in writing or in a documented electronic format.
(9) For these support actions under ยง5, the Processor is entitled to a charge reasonable fee.
(10) The Processor confirms that it has appointed a qualified company Data Protection Officer (hereinafter "DPO"), with specialist knowledge in particular, pursuant to Article 37 et seq. GDPR. The DPO named for the Processor is provided in [Annex 4](https://help.view26.com/legal/data-processing-addendum.md#annex4). If this changes, the system shall be updated immediately and the Controller notified in writing or electronically via the communication channel specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3).
(11) The Processor is entitled to process data outside the office premises (e.g. with the Processor's employees working from home).
## ยง6 Confidentiality obligation and observance of secrecy rules
(1) The Processor confirms that it is familiar with the relevant GDPR data protection regulations, in particular with regard to order processing (Article 28 GDPR).
(2) The Processor undertakes to maintain confidentiality in the orderly processing of the Controller's personal data. This shall continue after the end of the Agreement.
(3) The Processor warrants that it shall familiarize those employed in carrying out the data processing, prior to commencing the activity, with the data protection provisions relevant to them. For the term of their employment and also after termination of employment, these employees have undertaken to maintain the appropriate confidentiality (Articles 28 paragraph 3 (b) and 29 GDPR).
(4) The Processor shall document these obligations. At the Controller's request, the Processor shall prove compliance with this provision by providing the respective undertakings, or by any other appropriate means.
## ยง7 Technical and organisational measures under Article 32 GDPR (Article 28 paragraph 3 (c) GDPR)
(1) The Processor shall take all technical and organisational measures required to maintain the necessary processing levels during the contractual period to ensure that the level of protection of the rights and freedoms of individuals affected by the processing is appropriate for the specific processing agreed. The protection objectives of Article 32 paragraph 1 GDPR, such as confidentiality, integrity and availability of systems and services, as well as resilience in terms of the nature, scope, circumstances and purpose of the processing shall be taken into account in order to minimize risk during the contract period.
(2) The Processor shall undertake a review, assessment and evaluation of the effectiveness of the technical and organisational measures to ensure processing security at a set time, but at least once a year (Article 32 paragraph 1 (d) GDPR). The results concerning contractual data as well as the complete audit report shall be made available to the Controller, upon written request, for a reasonable fee.
(3) The Processor shall notify the Controller if the measures taken by the Processor do not meet the Controller's requirements.
(4) During the contractual relationship, the Processor is entitled to adapt measures to technical and organisational developments, provided that these do not fall below the standards agreed.
## ยง8 Notification obligations of the Processor in case of processing disruptions and breaches in personal data protection
(1) With regard to Customer Data processing, the Processor is obliged to notify the Controller of any disruptions or breaches of data protection regulations or the provisions hereof by the Processor (or those with access to Customer Data employed by the latter).
(2) The Processor is further obliged to notify the Controller immediately of any data breaches or major irregularities in the processing of the Controller's personal data, in particular if there is evidence - for whatever reason - that a third party may have obtained unlawful knowledge of the Customer Data or if the integrity or confidentiality of the Controller's data is endangered in any other.
(3) The notification obligations of (1) and (2) exist in particular with regard to any Controller reporting and notification obligations pursuant to Articles 33 and 34 GDPR.
(4) If necessary, the Processor shall assist the Controller in the fulfilment of its obligations pursuant to Articles 33 and 34 GDPR (see Article 28 paragraph 3 (f) GDPR).
(5) Notifications pursuant to Articles 33 and 34 GDPR may only be made by the Processor to the Controller upon prior written or electronically documented instructions.
(6) For these support actions under ยง8, the Processor is entitled to charge a reasonable fee.
## ยง9 Control rights of the Controller
(1) Before starting processing and regularly thereupon, the Controller is entitled to satisfy itself, in an appropriate way, with the compliance of the technical and organisational measures taken by the Processor and the obligations set out herein, as well as with the relevant legal data protection provisions (see Article 28 paragraph 3 (h) GDPR). If the Controller ascertains errors or irregularities in this or in any other examination of the agreed outcomes, the Processor shall be notified immediately thereof.
(2) To carry out the checks as defined by (1), the Controller is entitled to enter the Processor's business premises where the Customer Data is processed during normal business hours (Monday to Friday, according to Marketplace Listing of the product at [marketplace.atlassian.com](http://marketplace.atlassian.com/)) at its own expense, without disrupting operations, and strictly maintaining the secrecy of the Processor's business- and trade secrets.
(3) The Controller shall notify the Processor in due time (usually at least two weeks in advance) of all circumstances related to carrying out the inspection. As a rule, the Controller may carry out one inspection per calendar year. Notwithstanding this, the Controller's right remains to carry out further checks in the event of special occurrences.
(4) The Processor shall grant the Controller all rights of access, information and inspection required by the Processor to carry out the inspection. In particular, the Processor undertakes to grant the Controller access to the data processing equipment, files and other documents to enable the monitoring and verification of the relevant data processing equipment, files and other documentation related to Customer Data processing. The Processor shall provide the Controller with all information required for the inspection. The Controller hereby takes due consideration of the Processor's operating procedures and legitimate confidentiality interests.
(5) The Processor shall receive a reasonable lump-sum allowance from the Controller for each of its inspections within the scope of these checks.
(6) If the Controller commissions a third party to carry out the inspection, the Controller must oblige the third party, in writing, as the Controller is also obliged to the Processor on the basis of ยง9 hereof. In addition, the Controller must oblige the third party to confidentiality and compliance with rules to protect confidential information, unless the third party is already subject to a professional confidentiality obligation. At the Processor's request, the Controller must immediately provide it with the confidentiality agreements with the third party. The Controller undertakes not to entrust the inspection to any competitor of the Processor.
(7) Upon written request, the Processor shall provide the Controller with the current certifications, if and insofar as such certification exists, and/or test reports, if and insofar as the Controller has commissioned a test report in order to regularly review the effectiveness of the technical and organisational measures.
## ยง10 Subcontracting relationships (Article 28 paragraph 3 (d) GDPR)
(1) The Processor is only permitted to commission subcontractors for the Controller's data processing with the Controller's prior written consent (Article 28 paragraph 2 GDPR). This approval shall be given by the authorized person or representative (see ยง3(5)) in writing or electronically, but not verbally.
(2) The Processor shall only appoint a third country subcontractor if the special requirements of Article 44 et seq . GDPR are met (e.g. adequacy decision of the Commission, standard data protection clauses, approved codes of conduct).
(3) The Processor shall conclude subcontracting agreements in writing. This form requirement (Article 28 paragraph 9 GDPR) is also met if in electronic format.
(4) The Processor shall ensure that subcontractor(s) are obliged in the subcontracting agreement, in writing, to provide a standard that does not fall short of the standard agreed herein. Furthermore, the Processor ensures that the responsibilities between Processor and subcontractor and possibly also between multiple subcontractors are clearly delineated. The Processor shall ensure that the Controller is entitled to carry out an appropriate evaluation and inspection with subcontractors, also on site, if necessary, or have these carried out by third parties commissioned by it, unless proof of GDPR compliance can be provided by certification or approval pursuant to Article 43 GDPR.
(5) The Controller hereby agrees to the substantiation of the subcontracting conditions according to [Annex 5](https://help.view26.com/legal/data-processing-addendum.md#annex5). Alterations to the subcontracting conditions shall be disclosed by the Processor in [Annex 5](https://help.view26.com/legal/data-processing-addendum.md#annex5).
(6) Pursuant to [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3), the Processor shall notify the Controller in a timely manner of any intended change regarding the addition of new or replacement of previous subcontractors. The Controller shall have the opportunity to object to these changes for good cause within 30 days (Article 28 paragraph 2 GDPR). This objection must be in writing and substantiated. Unless approved or objected to within the 30-day period, the relevant subcontractor shall be deemed approved. If the Controller lawfully objects and the Processor cannot comply with the objection, the Processor shall immediately notify the Controller thereof. Within one month of notification by the Processor, the Controller shall be entitled to terminate the Main Agreement in writing.
## ยง11 Data return and deletion (Article 28 paragraph 3 (g) GDPR)
(1) The Processor is prohibited from actively processing Customer Data after termination of this Agreement; further storage of the Customer Data only remains permitted until the Processor has provided this Customer Data to the Controller as intended, or deleted or destroyed it; in this case, the provisions of this Agreement shall continue to apply even after termination of the Agreement, until such time as the Processor no longer has any Customer Data.
(2) The Controller may delete its personal data and/or create a copy until expiration of the contractual relationship. After the end of the Agreement, the Processor shall delete all personal Customer Data unless legal requirements require a longer retention period. The data shall then be deleted, no later than 6 months after the end of the Agreement, earlier upon corresponding instructions.
(3) The Processor is entitled to charge a reasonable fee for cancellation and destruction under ยง11.
## ยง12 Entry into force; contract duration and termination
(1) This Agreement shall enter into force with effect from ___________
(2) The duration of this Agreement corresponds to the duration of the Main Agreement. The regulations on the normal termination of the Main Agreement apply accordingly. Termination of the Main Agreement automatically causes termination of this Agreement. Termination of this Agreement in isolation is excluded.
(3) The right of the Parties to extraordinary termination of this Agreement and of the Main Agreement for good cause remains unaffected.
(4) In the event of termination of this Agreement, the main Agreement may only be continued if the Processor is excluded from processing the Customer Data. In case of doubt, a termination of the Main Agreement also applies as a termination of this Agreement and a termination of this Agreement also applies as a termination of the main Agreement.
## ยง13 Final Provisions
(1) Amendments, additions to and the termination of this Agreement must be in writing or agreed in a documented electronic format. This also applies to a change or cancellation of the written form requirement.
(2) Agreements on technical and organisational measures as well as monitoring and supervision documents (including of subcontractors) must be retained by both Parties for their validity term and for three full calendar years thereafter.
(3) If individual provisions of this Agreement are or become ineffective or contain a gap, the remaining provisions shall remain unaffected. The parties undertake to replace the ineffective provision with a legally permissible provision that comes closest to the purpose of the invalid provision and best meets the requirements of Article 28 GDPR.
(4) In case of contradictions between this Agreement and other agreements between the parties, in particular the Main Agreement, the provisions of this Agreement shall prevail.
|-----------------------|----------|------------------------------------------------------------------------|
| | Customer | view26 GmbH |
| Name (Required): | | |
| Signature (Required): | | |
| Title (Optional): | | |
| Date (Required): | | |
| Contact details: | | +49 (0) 203 346 893 40 [privacy@view26.com](mailto:privacy@view26.com) |
## Annex 1 - Main agreement
Customer Agreement:
## Annex 2 - Purpose, nature of processing and categories of data subjects
The below tables describe the nature of personal data and categories of data subjects of the Controller that can generally be processed as part of the Processor's service list.
In view of the nature of the service, the Controller acknowledges that the Processor can neither review nor maintain the below table. The Controller undertakes to notify the Processor of any changes to the table below (via the communication channel specified in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3)).
General processes
The following processes are available no matter which app or apps you use and regardless of whether you use Cloud or Server apps.
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Process** | **Purposes of processing** | **Categories of processing** | **Categories of personal data** | **Categories of data subjects** |
| Customer support | Help users from the Controller's organisation to resolve usage problems or error situations and thus contribute to the value of the app for the Controller and improvement of the apps and documentation. | In customer support usage problems or error situations are reported by users from the Controller's organisation via the mechanism described in [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3). In the course of the support process reporters might be asked to provide * JIRA support zips including log files logs from the reporters browser console Data is provided through the support tool (Jira Service Management, see [Annex 5](https://help.view26.com/legal/data-processing-addendum.md#annex5)) Reporters can choose to provide their own mechanism of data transfer. The received data is then analysed manually or automatically for causes or indicators of reported usage problems or error situations. | The process is agnostic of any data supplied to it. For reporting a problem or error situations the * reporter's name reporter's email address will be stored. Example categories of personal data are: * project reports including project collaborators Assignees, reporters, participants of issues Field values and changes on fields \& comments made by users of JIRA Cloud The ControlIer must inform the Processor if he processes additional categories of personal data inside Confluence, JIRA or the app. | ยท Users of Confluence (Cloud or Server) ยท Users of JIRA (Cloud or Server) The Controller must inform the Processor if he processes data of additional categories of data subjects inside Confluence, JIRA or the app. |
| Error tracking | For error tracking data is transferred from the end user's browser to an error reporting service, which allows analysis of errors without users having to actively report them. This is used to improve the quality of the apps. | Data describing the error context, like operations invoked, the user interface element clicked, technical context like browser, operating system values are transferred to the error reporting service (Datadog, see [Annex 5](https://www.k15t.com/legal/data-processing-addendum#DataProcessingAddendum-annex5)). Not all apps have implemented this feature yet. | This service transfers a hash of a technical identifier, to be able to spot cases where single users have reoccurring or interconnected errors. This process additionally transfers the following data * URL Browser and Operating System Invoked operations and clicked user interface elements | ยท Users of Confluence (Cloud or Server) ยท Users of JIRA (Cloud or Server) |
| Product analytics | For product usage analytics data is transferred from the end user's browser to an analytics service, which allows to report on the usage of product features. This is used to improve the quality of the apps. | Data describing the invoked functionality of the app is sent to the analytics service. The data is stored by a sub-processor (Datadog, see [Annex 5](https://help.view26.com/legal/data-processing-addendum.md#annex5)). | This service transfers a hash of a technical identifier, to be able to track typical usage patterns of functions inside the apps. | ยท Users of Confluence, that also use an app from the Processor (Cloud) ยท Users of JIRA, that also use an app from the Processor (Cloud) |
| License distribution | The apps are only usable with valid licenses. Licenses; i.e. commercial, evaluation and community or academic licenses; are distributed through the Atlassian Marketplace or [sales@view26.com](mailto:sales@view26.com). | All data attached to a license under [my.atlassian.com](http://my.atlassian.com/) or in a license request to [sales@view26.com](mailto:sales@view26.com) is transferred to the Processor. The Processor will send informational email when evaluating or using a new app via sub-processor The Processor might also send transactional email informing receivers about their licenses via sub-processor | Data for a license includes: * email address name postal address, if provided organisation | ยท technical contacts ยท sales contacts ยท partner contacts |
**Server**
The Processor's Server apps do not process data at the Processor or one of its sub-processors other than other than for the processes described above.
**Cloud**
The following table describes the data processing of all Cloud apps of the Processor.
The General processes that also apply to Cloud apps are described above.
The Processing is hosted on cloud (AWS, see [Annex 5](https://help.view26.com/legal/data-processing-addendum.md#annex5)).
|------------------------------------------------|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **App** | **Purposes of processing** | **Categories of processing** | **Categories of personal data** | **Categories of data subjects** |
| Charts and Reports for Jira Service Management | Create custom reports and charts with JSM project | Extraction of data from the Jira Cloud instance, transforming extracted data to visuals - charts and reports | Reports on the ยท Name (URL) of the Jira Cloud instance ยท Atlassian account ID \& Name | ยท Owners of the Jira Cloud instance, if the URL reveals the person's name. ยท Users of Jira Cloud ยท The Controller must inform the Processor if he processes data of additional categories of data subjects inside, JIRA using custom fields. |
| Page View Analytics for Confluence Cloud | Create Confluence Page View reports and charts with Confluence pageview webhooks | Process web-hook, transform extracted data to visualize - pageview analytics as charts and reports | Reports on the ยท Name (URL) of the Confluence Cloud instance ยท Atlassian account ID | ยท Owners of the Confluence Cloud instance, if the URL reveals the person's name. ยท Users of Confluence Cloud |
| JSON Viewer for Confluence | Publish formatted JSON Data as a Confluence page macro | No storage or transmission of any data on our Servers | None | None. |
| Scrum Stand-up Manager for Jira | Create custom stand-up meeting using Jira Board data | Extraction of data from the Jira Cloud instance, transforming extracted data to visuals - charts and reports | Reports on the ยท Name (URL) of the Jira Cloud instance ยท Atlassian account ID \& Name | ยท Owners of the JiraCloud instance, if the URL reveals the person's name. ยท Users of Jira Cloud |
## Annex 3 - Authorized persons, entitled persons, Communication channel
Authorized persons under this Agreements are the contacts listed at [my.atlassian.com](https://my.atlassian.com/) for the respective product identified by the SEN (Service Entitlement Number).
Instructions are to be transmitted by the following communication channel:
E-Mail to [support@view26.com](mailto:support@view26.com) or request via [support portal](https://view26.atlassian.net/servicedesk/customer/portal/2).
## Annex 4 - Data Protection Officer
The Processor confirms that it has appointed a qualified company Data Protection Officer, with specialist knowledge in particular and capable in the sense of Article 37 et seq. GDPR.
Data Protection Officer:
John Perayil
Data Protection and Organization Advisor
Hansastrasse 1-3,
47058 Duisburg, Germany
E-Mail: [privacy@view26.com](mailto:privacy@view26.com)
Any change in Data Protection Officer shall be communicated to the Controller in writing or electronically (pursuant to [Annex 3](https://help.view26.com/legal/data-processing-addendum.md#annex3)).
## Annex 5 - Sub-processors
The controller approves the following sub-processors to be used for the described purposes by the processor:
* Amazon Web Services, Inc., Seattle, USA: We use AWS to host our Cloud apps. The AWS privacy statement can be found [here](https://aws.amazon.com/privacy/).
* Process Squad GmbH, Essen, Germany: We use Process Squad GmbH's PETE Backend for process mining. The privacy statement from Process Squad GmbH can be found [here](https://process-squad.com/privacy-policy/).
* Actio Tech LLP, Kochi, India: DevOps team for VIEW26 platform support \& Bug-fixes
* Datadog, Inc., NYC, USA: We use Datadog to visualize and analyze how our apps are used. The Datadog privacy statement can be found [here](https://www.datadoghq.com/legal/privacy/).
* Atlassian Corporation Plc, London, UK: We use Jira Service Management from Atlassian for the creation, tracking and administration of support tickets, and Atlassian Confluence Cloud for the internal documentation of customer use cases. The Atlassian privacy statement can be found [here](https://www.atlassian.com/legal/privacy-policy).
* ActiveCampaign, Inc., Chicago, USA: We use ActiveCampaign to send an informational email when you evaluate or buy a new app. The Active Campaign privacy policy can be found [here](https://www.activecampaign.com/privacy-policy/).
---
language: "en"
---
# EULA
---
language: "en"
---
# monday.com Apps Terms and Conditions
These Cloud General Terms and Conditions are accompanied by the [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md).
## 1 Scope of these Cloud General Terms and Conditions
### 1.1 Scope of application
(1) These Cloud General Terms and Conditions ("**Cloud GTC** ") shall apply if you as a customer (hereinafter, "**Customer** ") access one of our (VIEW26 GmbH, Duisburg, Germany) software solutions for the [monday.com](http://monday.com/) Apps (hereinafter, "**Software** ") available on the monday.com Marketplace via a telecommunications connection and the data generated by the use of the Software and/or the data required for the use of the Software (hereinafter, "**Application Data**"), including our support services which we provide in connection with the respective Software.
(2) Our Cloud GTC apply exclusively. Conflicting, additional or deviating terms and conditions of the Customer shall not become part of the agreement unless we have expressly agreed that they apply. Our Cloud GTC shall also apply if we provide a service without reservation while being aware of conflicting or deviating conditions of the Customer.
(3) Our Cloud GTC apply only if the Customer is an entrepreneur (ยง 14 German Civil Code, "BGB"), a legal entity under public law or a special fund under public law.
### 1.2 Subject matter of the agreement
(1) The agreement covers:
(a) the Software selected by the Customer in its most current version.
(b) our support services during the agreement's term, including documentation. For the scope of our support services please click [here](https://help.view26.com/legal/support-service-level-agreement-sla.md).
(2) We do not owe any additional Software qualities and/or further services. In particular, the Customer may not deduce such an obligation from other representations of the Software or our services in public statements or in advertising by our sales partners, unless we have expressly confirmed such a quality.
## 2 Special agreements on the use of the Software
### 2.1 Provision of Software; Storage space for Application Data
(1) We keep the Software available for use on a central data processing system or several data processing systems (hereinafter, "**Server**").
(2) We keep storage space available on the server for the Application Data.
(3) The Software and Application Data shall be backed up on the server on a regular basis, at least every calendar day. The Customer is responsible for compliance with commercial and tax record retention periods.
(4) The point of interconnection for the Software and Application Data is the exit router of our data center.
(5) We are not responsible for the quality of the necessary hardware and software on the part of the Customer or for the telecommunications connection between the Customer and our company up to the point of interconnection.
(6) Delays in performance due to force majeure, e.g. strike or lockout in third companies or in our company (in the latter case, however, only if the labour dispute is lawful), official orders, statutory prohibitions, general disruptions of telecommunications or other circumstances beyond the control of the Customer (hereinafter, "**Force Majeure**") or circumstances within the sphere of influence of the Customer, e.g. delay in cooperating, delays by third parties attributable to the Customer, etc., entitle our company to postpone the provision of the services concerned for the duration of the hindrance plus a reasonable start-up period. If said event of force majeure continues for more than three months, both parties shall be released from their obligation to perform. Our further (statutory) claims or rights, in particular arising from delay of acceptance by the Customer, remain unaffected.
(7) Otherwise the provisions of Article 4.2 shall otherwise apply to claims by the Customer for damages or reimbursement of unnecessary expenses in the event that delivery is delayed, or performance is impossible.
### 2.2 Technical availability of the Software; Access to Application Data
(1) We undertake to provide the following availability of the Software and Application Data at the point of interconnection. The parties agree that availability shall mean the Software and Application Data technical usability at the point of interconnection for use by the Customer.
(2) The annual average availability of the Software shall be 99.5%.
(3) The available use (given availability) also includes the periods during which
a) malfunctions occur in or due to the condition of technical infrastructure's parts required for the execution of the Software which are not to be provided by us or our agents;
b) only an insignificant reduction in fitness for contractual use occurs;
c) maintenance work is carried out in accordance with para. 4.
(4) We carry out maintenance work each Friday, 7:00 am Central European Time (CET).
### 2.3 Free test phase; Agreement's term; Termination
(1) The Customer may initially test the Software free of charge for a period of one month ("**Free Trial Period**"). Within the Free Trial Period we provide support services to the best of our ability without being obliged to do so.
(2) The Customer can choose the term of the agreement on the Atlassian Marketplace according to the options available therein. The term is automatically extended by the originally selected term, unless the agreement is terminated by either party at the end of the term.
(3) The right of each party to extraordinary termination for good cause shall remain unaffected.
(4) Termination can be declared by clicking the button "Unsubscribe" within the administration of the basic Software (see Article 1.1 (1)).
(5) After termination of the contractual relationship the Software may no longer be used.
### 2.4 Further development; Updates
(1) We continuously aim to further improve the Software. There is no entitlement to a specific further development. Further development of the Software can lead to an extension and/or modification of the Software with the result that new functionalities are available, existing functionalities in the process and/or the user guidance are optimised, or the data management is adapted to the state of the art.
(2) The Customer may inform itself about innovations and updates via the means available on the monday.com Marketplace.
(3) If necessary, the Customer administrator of the basic Software can update the Software to the latest version by clicking on "Update" in the administration of the basic Software.
### 2.5 Customer obligations to cooperate
(1) The Customer shall fulfil all obligations required to perform the agreement. It shall in particular
(a) take the necessary precautions to prevent unauthorised use of the application. In particular, it will ensure that no unauthorized third party can access the application by means of suitable protective measures (e.g. password strength, passwords on its computers, burglary protection). The Customer shall inform us immediately if it believes that access data and/or passwords may have become known to unauthorised persons;
(b) create and maintain the access, functional and system requirements agreed in the order as well as other requirements for the use of the application;
(c) ensure that the users authorized to use the application are sufficiently familiar with the operation of the application on the part of the Customer, in particular that the users receive sufficient training;
(d) ensure that (e.g. when transmitting information of third parties to our server) all rights of third parties to material used by the same are observed;
(e) inform its employees about our data processing for optimisation purposes and their right to object at any time in accordance with section 4.5 as soon as it grants them access to the software
(f) if relevant, check data and information about viruses before sending them to our company and use state-of-the-art virus protection programs;
(g) only send encrypted user data;
(h) cause entitled users to comply with the provisions of this Agreement applicable to them.
(2) The Customer is aware of the essential functional features of the Software and was able to test them within the Free Trial Period. The Customer bears the risk that the Software meets its requests and needs.
(3) The Customer shall be solely responsible for setting up a functional hardware and software environment for the Software of sufficient size to take into account the additional load caused by the subject matters covered by the agreement.
(4) The Customer shall bear any disadvantages and additional costs resulting from a breach of these obligations.
### 2.6 Data backup by the Customer; Liability for loss of data
(1) Provided that the Customer is given the technical opportunity to do so via our software, it will regularly back up the data stored on the server by downloading it to its own computer system.
(2) The Customer shall store its data backups in such a way that the backed-up data may be restored at any time.
(3) Our company shall not be liable for the loss of Customer data insofar as the damage is due to the Customer failing to carry out data backups and thereby ensuring that lost data can be restored with reasonable effort, contrary to its obligation under paragraphs 1 and 2. In all other respects, Article 4.2 shall apply.
### 2.7 Rights of Use; Software protection
(1) Unless the Customer is expressly granted rights under this agreement, our company exclusively holds all rights to the Software - in particular copyright, rights to or as part of inventions and technical intellectual property rights. This also applies to processing of the Software by us.
(2) We grant the Customer a simple right, that may not be transferred or sub-licensed, to use the Software in accordance with the provisions of the functional description and (supplementary) of these Cloud GTC. This right of use may at the same time only be exercised simultaneously by the maximum number of users for whom the Customer also owns monday.com basic Software license
(3) The Customer shall not be entitled to transfer access to the Software to third parties.
### 2.8 Warranty
(1) We guarantee that the software has the agreed quality during the license period. It is not afflicted with defects that cancel or reduce the value or suitability for normal use or the use stipulated in the contract. This includes the non-existence of malicious program parts ("viruses").
(2) If the Customer notifies us of a defect, we are obliged, at our discretion, to immediately remedy the defect or to deliver a replacement free of defects.
(3) The Customer shall support us in the error analysis and elimination of defects, in particular by specifically describing any problems that occur, providing us with comprehensive information and granting us the time and opportunity required to remedy the defects reported.
(4) If we perform services in the search for or removal of defects without being obliged to do so, we may demand remuneration in accordance with our usual hourly rates. This applies in particular if a defect cannot be proven, cannot be reproduced or is not attributable to us.
(5) Warranty claims shall become statute-barred within one year of the software being provided by us.
## 3 Special agreements on the provision of support services
We provide Software support services during the term of the agreement in accordance with the following provisions (hereinafter, "**Support and Update Services**").
### 3.1 Scope of Support and Update Services
(1) The Support and Update Services include the handling of errors or other defects of the software that become known regardless of its use by the Customer, unless specified otherwise below.
(2) Our Support and Update Services do not include:
(a) Services for the software if the latter is not used under the conditions of use specified by us;
(b) Application and adaptation of interfaces and APIs;
(c) Handling errors caused by the Customer or by third parties, including the disruption of operations caused by third-party software;
(d) Services for computer programs or parts thereof that are not included in the software;
(e) Services which can be performed at our registered office, but which are performed at another location at the express request of the Customer;
(f) Instructing and training software users; and
(g) Services that become necessary because the Customer does not comply with its obligations to cooperate according to Article 2.5.
(3) We provide our support via a ticketing system (see [view26- Help Center](https://view26.atlassian.net/servicedesk/customer/portal/2) ). We are not required to provide a telephone hotline.
(4) Support for the Customer shall be provided during our working hours Monday-Friday, with the exception of public holidays in Germany, from 9:00 a.m. to 5:00 p.m. Central European Time (CET).
(5) Pending defect claims of the Customer (Article 2.8) are not included in support services and remain unaffected by the same.
### 3.2 Customer cooperation and obligations with regard to Support and Update Services
(1) The Customer shall provide us with the necessary information in the event of a support request and shall cooperate in answering its request, in particular by:
(a) providing the relevant documents, documentation and information required for the provision of services, in particular concerning existing systems, devices, computer programs and computer program parts which are to interact with our Software;
(b) documenting detected defects of services rendered in a reproducible, at any rate comprehensible form and immediately informing us about said defects;
(c) making available at its own expense facilities, infrastructures and personnel suitable for cooperation, insofar as necessary for the provision of services;
(d) performing necessary acts of cooperation in due time.
(2) The Customer shall name at least one contact person. We shall be immediately informed about any changes regarding in the contact person. The contact person shall have experience in handling the Software and must be able to provide information on the installation environment and the Software error reported in the event of queries from us. The Customer shall grant the contact person a corresponding authorisation to represent the Customer, in particular to also receive declarations from us.
(3) Prior to reporting the error, the Customer shall carry out an analysis of the system environment within the scope of its possibilities to ensure that the error is not attributable to system components that are not covered by this Agreement.
(4) As long as the Customer is in default with carrying out the required actions our company will be entitled to suspend performance of those services that without said Customer's actions cannot be performed at all or can only be performed with disproportionate additional expense. Any additional expenditure actually caused shall be reimbursed to our company by the Customer in addition to the agreed remuneration on the basis of our applicable hourly rates. Our further legal rights remain unaffected.
### 3.3 Defects in support services
(1) The support services are subject to the statutory provisions on service contracts (ยงยง 611 ff. BGB).
(2) We shall only be liable for damages due to a defect in our support services within the limits specified in Article 4.2.
## 4 General provisions
The following provisions apply to all of our aforementioned services (software lease and Support and Update Services):
### 4.1 Fee; Payment
(1) The fee for our services depends on the number of users and can be found under the heading "Pricing" on the monday.com Marketplace. The prices are net prices, i.e. not including applicable value-added tax.
(2) Billing will be carried out via monday.com, which we have authorised to collect our claims in its own name.
### 4.2 Liability
(1) Both parties are liable for damages due to the violation of contractual obligations to the extent that they are at fault.
(2) The amount of liability for simple negligence shall be limited to the damage typically foreseeable for the damaging party at the time of the breach of duty, however, limited to a maximum amount of US-$ 10,000 per damaging event.
(3) Liability for loss of profit is excluded.
(4) We shall not be liable for the loss of data to the extent that the damage is due to the fact that the Customer has failed to carry out regular data backups ensuring that lost data can be restored with reasonable effort.
(5) Non-contractual liability remains unaffected.
### 4.3 Third party rights
(1) If third parties assert claims against the Customer due to infringement of intellectual property rights in connection with the services rendered by us, we shall indemnify the Customer against these claims and shall cover all necessary and reasonable costs of legal action.
(2) If the Customer is sued by third parties, the Customer shall coordinate with us and shall take legal action, in particular acknowledgements and settlements, only with our consent. We shall defend ourselves against claims by third parties at our own expense if they are based on our attributable breach of duty.
(3) If third parties assert claims which prevent the Customer from exercising the rights of use granted to him in this agreement, the Customer shall inform us immediately in text form. At the same time, he authorizes us to conduct legal actions against third parties both in and out of court on our own.
### 4.4 Confidentiality
(1) The parties shall remain silent about all confidential matters, in particular business or trade secrets, which come to their knowledge in the course of the preparation, execution and performance of this contract and shall neither pass them on nor exploit them in any other way.
(2) The obligation of confidentiality does not apply if the information in question is to be disclosed pursuant to a court order, an administrative order or a law. The parties shall inform each other without delay of the disclosure and shall disclose the information in such a way as to preserve confidentiality to the greatest extent possible.
### 4.5 Data protection; Data processing
(1) We comply with the rules of data protection, in particular if we are granted access to the Customer's establishment or its hardware and software. We ensure that our agents also comply with these provisions, in particular we oblige them to maintain data secrecy before commencing their activities. We do not intend to process or use personal data on behalf of the Customer. If the Customer cannot exclude access by us to its personal data, the parties will conclude the following agreement for data processing: [Data Processing Addendum](https://help.view26.com/legal/data-processing-addendum.md) .
(2) In order to continuously improve the software, we collect the following data during the access to the software by the user:
* Usage of individual functions
* Installation environment
* Errors in frontend code
(3) The data is collected and analysed by a processor who is subject to the Data Processing Addendum linked in 4.5 (1). Once analyzation is completed, the data will be deleted. Under no circumstances will the data be passed on to third parties.
(4) Insofar as the Customer collects, processes or uses personal data when using the application, it shall obtain the consent of the respective person affected if not otherwise authorized.
### 4.6 Export and import control
(1) The Customer is aware that the services under this agreement may be subject to export and import restrictions. In particular, there may be licensing obligations, or the use of the Software or associated technologies may be subject to restrictions in certain countries.
(2) The Customer shall comply with the applicable export and import control regulations of the Federal Republic of Germany, the European Union and the United States of America as well as all other relevant regulations.
(3) The performance of the agreement by us is subject to the proviso that there are no obstacles to performance due to national and international export and import law provisions or any other statutory provisions.
### 4.7 Quotation as reference
We are entitled to use the Customer's name including its logo as a reference for advertising purposes. If the Customer does not agree, it can send an e-mail to at any time, together with a request to cease use. We will comply with this request immediately.
### 4.8 Final provisions
(1) The Customer may only transfer rights and obligations arising from or in connection with this agreement to third parties with our prior consent in writing.
(2) Place of performance is our registered office in Duisburg, Germany.
(3) Insofar as the Customer is a merchant within the meaning of the German Commercial Code ("HGB"), a legal entity or special fund under public law, the place of jurisdiction for any disputes arising from the business relationship between our company and the Customer shall be our registered office in Stuttgart, Germany. We shall also be entitled to file suit at the Customer's place of business as well as at any other admissible place of jurisdiction.
(4) The relations between us and the Customer are subject to the law of the Federal Republic of Germany exclusively. The United Nations Convention on Contracts for the International Sale of Goods of 11 April 1980 (CISG) shall not apply.
---
language: "en"
---
# Policies
[Next Page](https://help.view26.com/llms-full.txt/1)