967 karma · joined January 14, 2012
Example: Parts of our software run on customer servers and as such they are processing data in their control and not ours, hence can for example used to filter out personal data before they are then sent to our servers, without causing any GDPR related triggering of sending personal information to a third party (our company).
as per GDPR 6(1) grounds for processing can be (b) performance of contract, (c) compliance with legal obligations (d) vital interests of data subject - which can all cover logging ip addresses and user agents for network security reasons (for a short amount of time) to protect the user, which log files are often used for. (IANAL)
data leaks of course are always a breach and must be reported. that doesnt mean you get a fine though.
googling gives some results of scientific papers that would say this is the way its done.
I find it interesting that always around the full thousands there are sudden immediate pushbacks, for example when it dipped below 8000 several days ago it was pushed back to 9000. same happened at 10000 back to 12000.
But Storing IP addresses for each access indefinitely (> some days) is the problem.
If you rotate the files into a version where IP addresses are without the last part after a few days, then this is considered pseudonymous data and GDPR has no problem with you keeping this for a long time anymore.
1. concerns of security and quality of service (gathering logs with full ip addresses is allowed for a reasonable time, a few days for example).
2. you don't need to delete the logs if you use them for this specific purpose only.
3. for analytical purpose it is enough to use pseudonomic identifiers, in case of ip address zero out the last part and you are fine.
4. using Piwik or your own cookies? Suddenly its not a third party cookie anymore and you are more free to do things.
The problems for operators begin when they are handing this over to a third party.
Fractional Reserve Banks currency also usually exhibits natural demand on the account of being the currency required to pay taxes and accepted by stores/businesses in that country.
Yes, fractional reserve banking is bad. But at least the central banks have somewhat a clue how to control it and a legal framework to do so. Whereas for bitcoin exchanges, they just make it up along the way.
If you cater to companies, it is easier. You ask for the VAT number and only if the company is from your own country, you add the VAT, otherwise its 0%.
If you cater to individuals, you need to use two different mechanisms to identify where the user is from (IP Address + Geo location and another one) and store this information, then you need to charge the VAT from that country and you need to signup for the EU Mini One Stop Shop (MoSS) with your local tax office, report your european VAT earnings quarterly.
Selling to a customer (business or individual) from outside the EU you can charge 0% VAT, so that is easy as well.
I recommend that you use either Recurly or Quaderno in combination with Stripe, because they generate the invoices for you and handle the VAT calculation perfectly.
I don't know about other countries than Germany (were we are located), but we also have to submit monthly VAT report to our tax office, all in all we pay our tax attorney 400-500 Euros per month, plus another 1000 for the yearly report. Maybe other EU countries allow startups to report quarterly or yearly? Idk.
Think disagreement between miners, changes to algorithms, forks of blockchains. Gold does not have the same risk.
One nitpick: I think the SEC ruled ICOs to be comparable to certificates from what I understood. This is quite different to stocks. I could be wrong.
It feels to me a fallacy to think because you understand the tech, you are magically a good investor in it.
Buffet is historically one of the most successful investors in assets, and that usually didn't require him to "technically" understand every detail of the inner working of the offered product.
We are working on separating the extension that powers our SaaS APM for PHP and the original xhprof callgraph profiler again into two extensions in the near future :-) Then the extension will still be branded, but it has no code related to sending data to our service and just the backwards compatible profiling API.
The approach Basecamp (37signals) has with picking a location, then paying people based on 95% percentile (top 5%) market rate regardless of where they live is just much easier to explain to employees than some arbitrary multiplier thing that just leads to endless discussions.
https://m.signalvnoise.com/how-we-pay-people-at-basecamp-f1d...