Written to be read, not skimmed past. These terms apply to licenses bought through the pricing page; pilots run under their own agreement. Payment processing and the sale itself are handled by our merchant of record, whose own terms of sale apply to the transaction.
One purchase licenses one person: that person may install and use the plugin, on any number of machines that person uses, for any internal purpose including commercial work. The license is perpetual for every 1.x release and includes those updates as they ship.
Your scenes, your assets and your projects remain yours. Every dataset the plugin generates from them is yours too: frames, labels, masks, metadata. You may use, sell and redistribute your generated data without asking us, subject only to the rights you hold in the source assets, which are your responsibility to have.
The plugin, its source and the bundled runtime remain ours. Do not redistribute, resell, sublicense or publish the plugin or the bundle, in whole or in part, and do not remove license or attribution notices. Reading the shipped source to understand or debug it is fine.
The software is provided as is. We publish measured failure rates instead of promising there are none, and the quality page is part of the documentation. To the extent the law allows, liability is limited to what you paid for the license. Nothing here limits rights that consumer law does not let us limit.
Broken for you means refunded: if the plugin does not work as documented on a supported setup, write to hello@getnameframe.com, and if we cannot make it work you get the money back in full. Changing your mind is not a refund reason: every kind of output the plugin makes is published for evaluation before purchase. Statutory consumer withdrawal rights, where they apply, are handled at checkout by the merchant of record. If you break these terms and do not fix it after being told, the license ends; your generated data remains yours even then.
The product runs locally and does not send your scenes or datasets anywhere. Anything a support bundle would contain is written down before you send it, and sending one is always a deliberate action. Details are in the privacy notes that ship inside the bundle.
