Blank check terms, Runtime kill switch - twin EULA problems

[Craig Newman]

I have a subscription to a certain backup program. If I let that lapse, we part company and I lose the comfort of ongoing backups. That is all; I get that.

Is there any other company that places its users in such a peculiar position? Is there some large marketplace of users for which these issues are in fact non-issues?

And is the silence of the mothership due to frantic internal discussion about what they are doing and how to answer? Kevin?

I am keeping a disk image of the last Community version in a safe place. 

Craig

> On Dec 30, 2025, at 3:58 PM, Curry Kenworthy via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Blank check terms, Runtime kill switch - twin EULA problems
> 
> I meant to add - that WE have successfully raised the topic;
> thanks all. That helps LiveCode evaluate kill switch plans.
> 
> And EXACTLY! to Neville Smythe:
> 
> > It could well be a kill switch for the company,
> > I can’t think why any developer would want to use LiveCode
> > for standalones with such a time bomb in place.
> 
> But 1 more heads up on the twin EULA problem -
> Blank check terms.
> 
> Yes, it can affect you.
> Not only commercial users.
> Anyone.
> 
> Meet the LiveCode Create EULA -
> https://livecode.com/eula
> 
> Yes, twin clauses - 8.2 Kill switch, 8.1 Blank check.
> They enforce Runtime payments, but both are extreme.
> 
> Blank check = legal/financial minefield;
> One wrong move can be disaster.
> 
> An evaluation said "you should NOT accept this as-is."
> 
> Quickest example - paying 5% royalty, vs user/month seats;
> Big difference! Big enough to bankrupt or derail operations.
> 
> Or free users vs paid. Same thing. Or double the seats.
> Blank check turns Fine print ambiguities into High risk.
> 
> Got your attention now?
> 
> "8.1 ... If the audit reveals under-licensing, you agree
> to promptly purchase additional licenses to cover the shortfall
> and reimburse LiveCode for the cost of the audit"
> 
> Don't tune out on 'audit' - it's just 'LiveCode's audit team.'
> Not independent. All subjective. No protections. No real argument.
> 
> Just as kill switch does not require an official audit -
> You already agreed in full. No dispute resolution. They alone decide.
> 
> No wrong move - perfect use - still can be disaster.
> Blank check! You pay whatever they say.
> And you pay them to say it.
> 
> Whoever runs and staffs LiveCode now, and later.
> No assurances/answers can remove that risk - EULA prevails.
> Interpretation could change.
> Fine print ambiguities in sections 3-6.
> 
> EULA ambiguities should be corrected, written crystal clear -
> but Blank check is still never safe.
> 
> This will hold LiveCode Create back -
> at least with those who notice things.
> 
> For me, Blank check/audit and Runtime kill switch will not fly.
> Too risky, ethically and physically impossible.
> 
> Window is closing to fix LiveCode pricing/terms issues.
> People have been retooling elsewhere; no choice.
> Easy to fix if LiveCode chooses.
> 
> Happy Holy-days of Christ's Mass!
> 
> Best wishes,
> 
> Curry Kenworthy
> 
> "Dominate documents with WordLib and LC"
> https://livecodeaddons.com/wordlib.html
> 
> (Still recuperating from illness - more news soon.)
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode