Designating Customers as Authorized Users

 

Effecting starting: 2016-10-24

This is a supplement to the Bricknode Customer Agreement (the “Agreement”) and is include din the Agreement. Any capitalized terms used but not defined below have the meanings in the Agreement. The purpose of this supplement is to allow your customers to be Authorized Users, subject to the terms below.

1.       If you designate any of your customers as Authorized Users, you will be responsible for their use of the Hosted Services as you would be for any other Authorized User. Accordingly, you must enter into valid, binding agreements with your customers that require them to comply with the applicable terms of the Agreement (including this supplement), including any conditions or restrictions with respect to use of, or access to, the Hosted Services.

2.       For the avoidance of doubt, allowing your customers to be Authorized Users does not mean that you may distribute, resell, or OEM any Hosted Services, or make the products available to your customers on a standalone basis. Rather, it means only that your customers may access your instance of the Hosted Services in order to support their use of your own products and services that are unrelated to the Hosted Services (“Your Products”).

3.       Examples include:

3.1.    Your customers accessing your Bricknode Customer Front End to view the financial positions, conduct transactions, place orders for Your Products;

3.2.    Your customers accessing your Bricknode Advisor Front End to view their advisory customers, manage positions, order, communication and communicate with Your Products;

3.3.    As an Authorized User, your customers may interact with the Hosted Service but may not receive any administrator, configuration or similar access to the Product. For example, your customers may place orders for instruments that you have configured in your Bricknode instance, but you may not permit any of your customers to administer objects like instruments, customers or transactions through the back office/administrative front end of the Product.

3.4.    Bricknode will not have any direct or indirect liability or obligation to any of your customers. For the avoidance of doubt, your customers are not parties to, or third party beneficiaries under, the Agreement.

3.5.    You will defend, indemnify and hold harmless Bricknode from and against any loss, cost, liability or damage, including attorneys’ fees, for which Bricknode becomes liable arising from or relating to any claim brought against us by your customers arising out of their use of the Hosted Services through you.

Say hello to our Partners in the Bricknode Marketplace

Tuesday, January 24, 2017

We are excited to tell you that we just added the companies Choose4use and Hectic Code to our Partne…

Introducing the Bricknode FinTech Startup Sponsorship Program

Wednesday, February 1, 2017

We are introducing the Bricknode FinTech Startup Sponsorship Program for FinTech startup companies, …

Fee Manager version 1.1 has arrived

Thursday, March 2, 2017

Bricknode has released a new version of Fee Manager offering you a more dynamic way of applying any …

Bricknode Broker makes financial institutions PSD2 compliant and enables them to offer their API to partners

Tuesday, April 11, 2017

As a securities brokerage firm, you should constantly be looking for ways to improve the value for y…

We are hiring!

 

We currently have these open positions:

Sales (In Swedish)

Support Manager (In Swedish)

Looking for a job?