FAQ regarding our EULA

1. Our legal department would like to make some changes to your EULA. Is that ok?

Within our current price structure, we're unable to make any changes to our Appfire EULA. Taking into consideration our cost-effective pricing model and the costs associated with creating and managing individual agreements with each of our customers, you can begin to understand our position. Maintaining a standard EULA with all of our product customers allows us to focus our resources on meeting our obligations under these agreements. With that in mind, our EULA has been very carefully authored to be fair to both you and us. There may be some issues that are not covered here or on the rest of this page. If so, please feel free to contact us.

2. Your EULA refers to the grant of Publicity Rights. What does that mean? Can we change that?

We list a small number of our customers on our website as examples of organizations using our software. If you do not want us to mention your company name at all, just contact us and we'll add you to our list of companies requesting not to be party to future disclosures or forms of publicity (including our customer lists on our website).

3. Your EULA refers to data that may be collected and stored. Can you provide more details?

The only customer data that we currently maintain within our own internal systems is customer and transaction information (i.e.: purchase history), as well as anything that you may (or may not) elect to share with us via our online knowledge base or support system. Any application level data is stored either within your systems (if you work with Atlassian's "Server" products), within Atlassian's systems (if you work with Atlassian's "Cloud" products) or within your systems, Atlassian’s systems or our systems (if you work with products architected using Atlassian's "Connect" architecture). In the case of products architected using Atlassian's "Connect" architecture, the location of specific application level data storage depends on the product. To better maintain the integrity of privacy protection for Licensee data, we do not specify the location of application level data storage on a product-by-product basis.

4. Your EULA refers to open source libraries. Can you specify which libraries you use?

For Bob Swift Atlassian Add-on brand products:

Information regarding the use of relevant open source libraries is published in the license directory file inside each of our product .jar files. Please refer to each referenced library’s documentation for further details.

For Wittified Atlassian Add-on brand products:

Information regarding the use of relevant open source libraries is published within an "Open Source" link (or equivalent) inside the support bar area of each product, where relevant.

5. Is it ok for our affiliate users to use the add-ons covered by your EULA as well?

Yes, assuming that (a) actively licensed versions of our add-ons are installed within a single Atlassian deployment, and (b) your affiliate users are included within your total count of "Authorized Users" as defined within the section titled "Orders" in our EULA.

If you would like to have our add-ons installed within multiple different Atlassian deployments, then a unique add-on license will be required for each unique Atlassian deployment.