Frequently Asked Questions
Q: Who should buy data from Royalty Connection™?
A: This data is useful for negotiating licenses, whether in a university technology transfer setting or an industry setting, as well as for attempting to settle pending litigation or avert potential litigation. The data gives the user a portrait of the licensing landscape in a large number of industries going back to 1990.
Q: What types of license agreements can I expect to find at Royalty Connection™?
A: You can expect to see several different types of license agreements including Arms-length Agreements, Court-Awarded Licenses, Settlement Agreements, and Related-Party Agreements.
Q: Where does the data come from?
A: Our database contains information from public sources, including SEC filings, court records and press releases. The records contain licensing transactions from 1990 to the present.
Q: What will I receive when I purchase data from Royalty Connection™?
A: You will receive a report containing the following information for each record you select for purchase:
- Licensor/Licensee
License Date
Technology Licensed
SIC, NAICS and Industry
Royalty Rate and Base Type
Licensed Patent Numbers
Other Consideration Paid (such as upfront payments, stock or lump sum payments)
Term of License
Exclusivity
Territory Licensed
Sublicensing Rights
Source
Q: Do all the licenses have running royalty rates?
A: Not all the licenses in the database have running royalty rates. Some licenses are structured so that consideration is paid in a lump sum form only.
Q: How frequently are the records updated?
A: New records are added to the database on a continuous basis, so be sure to check back frequently for new licenses in your area of interest.
Q: Can I search using any wildcard characters?
A: Yes. The wildcard character in Royalty Connection is an asterisk (*). To broaden your search through use of the wildcard functionality, replace part of your search term with an asterisk. For example, “*.com” would return all records containing names ending in .com, while “light*” would return all records containing the words “light”, “lightning”, “lightweight”, and “lighting”.
The query language in the Royalty Connection database cannot recognize the following characters: + & - /
Therefore, if you want to search for a company name or technology that contains one of the these characters (for example, “X-Ray Technologies, Inc.”), we suggest you use the wildcard character in your query so that such characters can be omitted (for example, “*Ray Technologies, Inc.”) in order to receive the most relevant results.
Q: What is your return policy?
A: There are no returns allowed of data purchased from Royalty Connection™.
Q: What are the restrictions on use of the data?
A: Please see our Conditions of Use.
Q: Is my personal information safe?
A: Please see our Privacy Policy.
Q: What will appear on my credit card statement?
A: The charge will appear as "Invotex Group - Royalty Connection."
Q: Will I be charged sales tax on my purchase?
A: Users residing in the District of Columbia will be charged 5.75% sales tax.
Q: I have registered with Royalty Connection but have not yet received my registration confirmation email. What should I do?
A: Your registration confirmation email may have gone to your junk or spam folders, so be sure to check there first. If you need additional assistance, please contact Royalty Connection.
Q: What password should I use to open my purchased License Reports?
A: The password to open your purchased License Reports is the same password you use to log on to Royalty Connection.
Q: I have made a purchase on the Royalty Connection site but have not yet received my Purchase Confirmation email. What should I do?
A: Your Purchase Confirmation email may have gone to your junk or spam folder, so be sure to check there first. If you need additional assistance, please contact Royalty Connection.
Q: What does it mean if there is a blank field in my License Report?
A: A blank field in the License Report simply means that the source document used to create the License Report did not address that topic specifically.

