Can bitcoins be taxed? Let's say I give someone a bitcoin and then they give me a phone. Could the IRS — or a similar organization, if outside the U.S. — say I bougth the phone and take a chunk of the bitcoins? What if they set up an inventory of phones, and gave a phone to whomever gave him a bitcoin? Would the IRS get involved?
The United State doesn't have a national sales or value added tax, so the IRS would only care about the phone sale insofar as it might represent income to the seller. Insofar as it's income to the seller, it doesn't matter whether the transaction is cash, bitcoin or barter, the seller is supposed to account for it in their income taxes. If you are suggesting that bitcoin sales could be hidden, well, folks have been hiding cash transactions since taxes were invented. Worst case, the IRS discovers that the seller's spending is wildly out of line with their stated income and they begin a criminal investigation.
I see that this would put me under heavy US regulation, and I'd like to avoid that, since it would require huge funding to hire lawyers to do something like that. There are many reasons for financial and banking industry regulations; namely, fraud protection, corruption and money laundering preventions, use of crypto to avoid taxes and records, etc. If you're serious about a startup that involves financial transaction, one of the first things you do is find a law firm to advise you on the legal plausibility of an idea. And be prepared to spend thousands and thousands of dollars in legal fees for regulatory approval. Would doing something like this solve my problem? You're really going to trust randos on the web for legal advice?
It is currently legal to barter goods or services in exchange for gold or silver bullion in the United States. Gold and silver do not have to be registered or certificated, although a prudent person would usually seek evidence confirming their authenticity and it would be common practice to keep gold and silver in a repository such as a bank or Fort Knox, and to conduct the transaction via negotiable certificates evidencing ownership of the gold or silver (basically warehouse receipts whose transfer is governed by the Uniform Commercial Code) rather than to physically transfer the gold or silver, in a large dollar value transaction. There are been periods of time in the United States where this was not allowed, unless done by a state government (which has a constitutional right to do so), or by a local government authorized by a state government to do so. But those laws are not currently in force and haven't been for a long time. Transfers conducted with gold or silver bullion in excess of $10,000 per transferee per year, probably have to be reported to the same officials to whom a cash transaction in that amount is reportable on IRS Form 8300, because it is considered a collectible cash substitute, even though it is legal to do so and no tax is specific to barter transactions in gold or silver. IRS Publication 1544 explains the rule.
Let me be sure that I understand the situation. You set up an account with Big Company, which uses BigCo as a trademark. You want email about that account to reach you with a unique address, so you set up 'BigCo@RichDomain.Com" and gave that as your email when setting up tha account. You don't plan to use that address for any purpose but communications from BigCo to you and from you to them. (Of course these aren't the actual names.) Have I understood the situation correctly? It seems that you ar not using 'BigCo" in trade, nor are you likely to be confused with an official representative of BigCo, so you are not infringing their trademark. However, someone using such an email more generally could perhaps be so confuse, so BigCo has a somewhat legitimate concern, as they cannot know the very limited use you plan to make of this address. The only way that the could force you not to use such an email address would be via a court order as part of a suit for trademark infringement, whcih under the circumstances I doubt they would get. However, unless they have some sort of contract with you to the contrary, they can control who registers on their site. and could refuse to register you using an email address that includes their name or alias. Convincing them to accept your registration, even though it does no harm to them, will almost surely be more trouble than it is worth. Give them "BigFirm@RichDomain.Com" or something else that is not their name, but will suggest their name enough that you will know who it is. This will serve your purpose fully, and avoid a long argument with people who are reading from a script (once you get past the automated process, if you can even do that). This is all assuming that I have understood the situation correctly. I am also largely assuming US law, since you didn't mention a jurisdiction. (EDIT: UK law should not be very different on these points.)
You can put conditions on bequests (subject to other laws that might require you to provide for children etc.), however, these must be antecedent to the gift: once a gift is given you can't call it back. Of course, you could set up a trust that owns the bequest with rules for when and how the beneficiaries can utilise them that effectively do what you ask. However, this is a morbid and sick way of trying to control people from beyond the grave. The acceptable way to do this is to come back as a ghost, vampire, zombie etc. instead.
Yes and no. [note, the following is all written about US law. In other jurisdictions laws are, of course, different (though usually not drastically so.)] In the US there are (at least) three different bodies of law that might apply to code: copyright, patents, trade secrets. Copyright covers original expression. Anything you write is automatically, immediately protected under copyright. The copyright applies to the code itself, and anything "derived" from that code. It's up to the courts to decide exactly what "derived" means. One case that's long been viewed as a landmark in this area is Gates Rubber v. Bando Chemicals. The Court of Appeals for the tenth Circuit decision includes a section titled: "The Test for Determining Whether the Copyright of a Computer Program Has Been Infringed." Note that you can register a copyright, and that can be worthwhile, such as helping recover some damages you can't otherwise. Patents are quite different from copyrights. Where a copyright covers expression of an idea, a patent covers a specific invention. Rather than being awarded automatically, a patent has to be applied for, and awarded only after the patent office has determined that there's no relevant prior art to prevent it from being awarded. A patent, however, covers things like somebody else independently discovering/inventing what's covered by the patent. A trade secret could (at least theoretically) apply to some process or procedure embodied in the code. A trade secret mostly applies to a situation where (for example) you're trying to form an alliance with some other company, and in the process tell them things you don't tell the general public. If you've identified the fact that what you're telling them is a trade secret, and they then tell a competitor (or the general public, etc.) or more generally use that information in any way other than the originally intended purpose, it could constitute a trade secret violation. As a side-note: patents and copyright fall under federal law, so they're basically uniform nation-wide. Trade secrets mostly fall under state law, so the exact details vary by state. Absent a reason to believe otherwise, I'd guess your interest here is primarily in copyright infringement. The key here would be showing that one piece of code was derived from the other. That is, it specifically would not apply in a case where there were only a limited number of ways of doing something, so anybody who wanted to do that had to use one of those ways. Since this would not indicate actual derivation, it would not indicate copyright violation.
Do I have to pay taxes if I register the domain but the website income belongs to someone else? No. The person or company who runs, and/or profits from, the business is the entity under obligation to pay all the applicable taxes: Value Added Tax, income tax, corporate tax, and so forth. Unless you charge a significant amount therefor (see the comments), the mere registration of just one domain is unlikely to trigger tax obligations.
Yes, this violates the GDPR if the user is in Europe. Data which is tied to a personal device can be tied to the person who owns it. From "What Is Personal Data" by the UK Information Commissioner's Office (ICO) (emphasis added): Personal data is information that relates to an identified or identifiable individual. What identifies an individual could be as simple as a name or a number or could include other identifiers such as an IP address or a cookie identifier, or other factors. If it is possible to identify an individual directly from the information you are processing, then that information may be personal data. If you cannot directly identify an individual from that information, then you need to consider whether the individual is still identifiable. You should take into account the information you are processing together with all the means reasonably likely to be used by either you or any other person to identify that individual. The bit about "all means reasonably likely" in the last bullet includes the kind of de-anonymisation tactics described in the NYT article. There are 6 lawful bases for data processing in the GDPR, and all processing must fall under at least one of them. (a) Consent: the individual has given clear consent for you to process their personal data for a specific purpose. (b) Contract: the processing is necessary for a contract you have with the individual, or because they have asked you to take specific steps before entering into a contract. (c) Legal obligation: the processing is necessary for you to comply with the law (not including contractual obligations). (d) Vital interests: the processing is necessary to protect someone’s life. (e) Public task: the processing is necessary for you to perform a task in the public interest or for your official functions, and the task or function has a clear basis in law. (f) Legitimate interests: the processing is necessary for your legitimate interests or the legitimate interests of a third party, unless there is a good reason to protect the individual’s personal data which overrides those legitimate interests. (This cannot apply if you are a public authority processing data to perform your official tasks.) Selling data isn't covered by any of the others, so consent must be obtained. Permission must be clear and positive, and you cannot predicate delivery of a service on the processing of data that isn't necessary for that service. So for instance you cannot say "You can use this service as long as we are allowed to collect and sell your data" because selling the data isn't necessary to the provision of the service. From "Consent" by the ICO: Consent requires a positive opt-in. Don’t use pre-ticked boxes or any other method of default consent. Explicit consent requires a very clear and specific statement of consent. Keep your consent requests separate from other terms and conditions. Be specific and ‘granular’ so that you get separate consent for separate things. Vague or blanket consent is not enough. [...] Avoid making consent to processing a precondition of a service. This applies to any processing of data about individuals within the EU, so just being an American company doesn't get you a free pass to ignore the GDPR if your app gets used by Europeans. The "Legitimate interests" basis is more problematic, in that the company collecting the data has to conduct a vague "balancing test" to determine if this basis applies. For direct marketing the ICO has written this, which says that direct marketing may be a legitimate interest, especially if you can show that the user has expressed interest in such adverts. For instance a location service which promises to tell you about nearby special offers would fall into this category. Against this, the impact on the user's privacy has to be considered, and location data is "special category data" because it can reveal medical information (e.g. hospital attendance) or religious affiliation (e.g. which church you go to). So unless the relationship between the recorded location data and the service is very direct its not going to pass the balancing test. The company would also need to distinguish between knowing the current location and keeping a record of historical locations; the two need separate justification. And of course nothing about this covers the sale of the data; this is considering a company which sells advertising space in it's app, not one that sells the data itself.