Could Elon Musk dissolve Twitter now that he owns it? I know that generally if you own a company you can just dissolve it, however can Twitter have certain rules set up in their selling contract or perhaps because it's such a large company, can they somehow stop Elon Musk from just dissolving the company if he felt like it?
Elon Musk doesn't own Twitter He is part of a consortium of investors that own it. What he can and can't do with it will be constrained by any agreements that exist between those investors and, as CEO, a duty to all of the shareholders and to the company itself. However, that jus begs the question: can the &quot;owners&quot; of a company dissolve it? Yes. Or, more precisely, the directors acting for the shareholders can cease operating the company, collect all that it is owed, pay all that it owes and distribute wherever is left over to the shareholders. If there won't be anything left over, then the directors have a duty to point an administrator/liquidator to finalise the company. One of these two things is, ultimately, what happens to every company sooner or later.
This is possibly but not necessarily fine. The data controller (the garage) is responsible for safeguarding your personal data. They must take appropriate safety measures, but this depends a lot on their own risk assessment. For example, to protect the data from being used by employees for their personal purposes, the controller might use organizational measures like a policy “you're not allowed to do that.” Many companies allow employees to use their personal devices for work purposes (BYOD). When the data controller allows this and takes appropriate safety measures, everything is perfectly fine. The company still has to make sure that the data is only processed for legal purses and deleted afterwards. Implementing a BYOD policy in a GDPR compliant manner is difficult but not impossible. A data breach has occurred when the security measures were insufficient and your data was deleted or disclosed without authorization. Your scenario would only be a breach if the company did not have a BYOD policy and the salesman used their personal phone, and arguably then only if that device is also breached. However, do not discount the alternatives: they do have a BYOD policy and the salesman is acting within their instructions the salesman was using a company-controlled device, not their personal phone If you have good reason to believe that your data was mishandled (and these alternatives do not apply), then the GDPR offers you the following remedies: You can of course complain to the data controller, especially if they have a dedicated data protection officer. You can lodge a complaint with a supervision authority, which is the ICO in the UK. They expect you to attempt to resolve your issue with the controller first. The ICO can then decide if they want to investigate the issue. You can sue them for compliance and for actual damages suffered (you have none, though). Note that all of these alternatives are more effort than they are likely worth. In particular, the garage can always correct the problem, e.g. by getting your contact info deleted from the personal device or by creating a retroactive BYOD policy.
It's really your client that should be asking these questions. Writing the app is perfectly legal. So you can enter a contract with that client to write the app and deliver it to them, ready to be put on the Google Play store or the App Store (entering a contract needs to be done carefully, obviously). I'd make 100 million percent sure that the contract states clearly that you have zero responsibility if the app is rejected or removed for non-technical reasons, and that the legality of actually selling and running the app is also not your responsibility. The reason is that I very much suspect that running the app might be illegal, and that the chances of getting it permanently on one of the stores are rather slim. And solving those problems is outside of what a software developer can competently do.
a few quick notes that come to mind. As the commenters point out: DSGVO is indeed the German equivalent name to the GDPR (English term) "Imprint" isn't a privacy related topic that much, as such it's not really changed by the upcoming GDPR The GDPR changes many things, but the requirement for up front information isn't one of them - so it would've already been a rule to follow Sometimes the question who is responsible for privacy information might not be that easy to decide when you're on platforms. I take this situation as being pretty clear though. You are basically given a blank slate, you can do with that page whatever you want, and the visitor has no clue whatsoever that it might be hosted by Github. In addition to this, Github would be classified as a data processor (providing the tool) and you as the data controller who is in charge of practically everything except for the provision of the page. I hope this helps. Btw. it's not that hard anymore to write a privacy policy these days.
The warning notice is intended for viewers and participants, not for the court to make its own official record of the proceedings. Presumably, it was this court record that the judge released for educational purposes under his own Order via Twitter. In which case, there has been no contempt of court.
However, this uses the text "rights in an invention"; does that cover copyright? Yes. (Is this the correct law?) It certainly seems to be. Does "Relate … to the employer's business" cover the entirety of software engineering, or just the particular software engineering my employer does? Imagine that you work for a company that writes trading software. In your spare time, you develop a photo editing tool. Do you think a court would find that your project "related to the employer's business"? I do not. Or does my employer own copyright on everything down to the love letters I write? Google does not own everything their employees create; they only claim to. If someone challenged them on it, a court would decide, and probably not in their favor.
This is neither unusual nor illegal, assuming that the buyback price is specified in the agreement. If your friend does not wish to take advantage of the "nice discount" he can decline the deal, and decide for himself whether he wishes to buy shares without restriction, at the market rate. (It would be interesting to know what happens if he sells his shares and then leaves the company. I am fairly sure the agreement will cover this, but requiring an ex-employee to buy shares and then give them to the company could be considered unconscionable. That might be worth asking a lawyer about).
could this mean my employer owns the idea and anything I develop --since I would use the same technology for my idea that I do at work? No, unless by &quot;technology&quot; you mean the employer's materials or resources (see condition 3 of the clause). Your remark that &quot;this is completely and utterly unrelated to [employer's] business model&quot; survives items 1 and 2. Likewise, working on your idea outside hours survives the corresponding part of item 3. Would this also mean that any open-source software I develop outside of work automatically belongs to my employer? No, unless the software you develop is &quot;based on [your] knowledge [etc.] of (COMPANY)&quot;.