> Well I thought made clear in my previous post and you basically told me to shut up and stop asking and read the privacy T&C when it comes out?
>
I don't believe I've told anyone to shut up, I'm being patient.
> I want to know how C3 is handling security that will allow you to know what a person is publishing to enforce your license?
>
> For example: If I have a license C3 version and my buddy has a free version and I use my version to upload his capx and export it to a different platform is Scirra going to know of that and will they lock my engine?
>
We've never 'locked people's engines'. And I don't think it's reasonable for us to go into our anti piracy measures with you as part of an effective anti piracy strategy is not outlining what exactly we do to combat it as it's a game of cat and mouse. Our policy internally (and we've debated the ins and outs at length) is that we know some level of piracy will happen, but we will always do our best to ensure it never, ever affects legitimate paying customers. As long as you're a legitimate paying customer you do not need to worry.
> I don't know of any other way you could enforce your license without including code that would allow Scirra to internally shut down a specific engine
>
We've never shut down a legitimate paying customers engine.
> and that raises privacy concerns over who is vieweing and possibly copying our capx projects.
>
It doesn't, as I've explained a few times now we don't have access to your CapX files unless you explicitly decide to upload them as files to our arcade or as forum attachments.
Saying you haven't locked an engine when you have not released C3 which has new security features is not exactly answering the question.
Can you lock a specific engine on C3?
If there is no way for Scirra to view a capx or in some way add a tag to the exported projects we produce I sure don't see how you will enforce your license?
I am interested only because an internet based model of design is going to open up security and privacy issues.