Tag Info

Hot answers tagged

79

Summary Minimising the attack vectors by not registering a domain, not registering hosting, not using a credit card, not openly giving out your IP and email address, not using Google Analytics, and not blabbing about your new project will each reduce the chance of your identity being discovered. How might your identity be discovered? To understand how to ...


14

The Whois privacy is barely a protection - most registrars will surrender your personal details at the first request. Well, perhaps at the second. Anyway, the point is, they are generally unwilling to take risk and get under fire so they won't bother to investigate who is right and who is wrong for a client that perhaps only brings $5/month of revenues. ...


10

It's potentially illegal and also morally wrong. Basically, if you would be unhappy for someone to read your private messages then it's wrong (morally) and I suspect it would be considered criminal under one of these Canadian Laws (technically the crime would be committed at the location of the server):- Section 342 of the Criminal Code of Canada ...


8

Without additional safety, no. Random URLs are crawled all the time. However, this is good when done with a sign-on page to authenticate the user. An intermediate solution is to make sure the status page contains no personal data, only general info. For example, 'PAID BY CC' rather than 'PAID by VISA 1234567891' and 'Shipped' instead of 'Shipped to John ...


7

Your boss is paranoid. Reading emails for the sake of SEO spam control is not something Google is doing. If they were caught doing that the Department of Justice would come down so hard on them they'd be lucky if they survived.


6

1. Serverside - block Search Engines Create a robots.txt file in your root directory and add this text to it: User-agent: * Disallow: / Theoretically, This should block all search engines (the ones that honour robots.txt). 2. Know how Search Engines are crawling your site and control your site's visibility. Since you want it to be extremely private, I ...


5

As long as your privacy policy properly disclose what you track, and you don't misuse the information, there shouldn't be any problem.


5

Yes, there are privacy concerns with using Google Web Fonts. If you have strict privacy concerns you should probably not use the service. Users of Google Web Fonts are bound by Google's generic API terms of service, which includes this clause: By using our APIs, you agree that Google can use submitted information in accordance with our privacy ...


4

The first step to protecting your anonymity on the internet is to decide what level of security you need. Are you concerned with hiding from well funded governments / political parties, or just the average Joe? The Average Joe If it's the latter, entering invalid whois data (don't pay for any of the supposed "privacy guard" services, they're just changing ...


4

Using Google Analytics is not unethical Google Analytics does not track Google accounts. GA uses a special set of cookies _ga, __utma, __utmb, __utmv and __utmz to track user activity. And Google Analytics does not allow individual users to be "traced" any more than they would otherwise without GA present. Perfect privacy on the web is impossible Whether ...


4

There are two commonly-used methods of maintaining privacy in domain registrations: Privacy services offered by the registrar. These services are independent of ICANN but regulated by them through policy. ICANN does require that registrars send private registration data to the shared registry, meaning that ICANN has access to that data, but they only ...


3

The whois protection is good enough as far as I know. Obviously this is true for normal people. If police or similar will require your data, they will take them easily.


3

Use a Hidden Service on the Tor-network with a .onion-domain. Unless you give out personal details yourself, it's impossible to trace back to you.


3

No, Adsense does not send the content of every page to Google - that would be pretty inefficient and hog a lot of bandwidth - and in fact is not technically possible with cross-domain restrictions. Instead, the Adsense crawler (different from the normal Googlebot crawler) visits the page separately and decides what the context of the page is. Then when a ...


3

Technically your question is one of international law. But I think that's stretching the technicality well past absurdity for a public forum such as this. My answer is from a more practical "what should the IT folks do until the lawyers and judges figure all this out?" point of view. The answer is do nothing until you see the BIG players responding and ...


3

This is a good question but I would have to agree with Pekka. Perhaps you may not realize the consequences of doing so. For example say you visit one of the many many sites that use jQuery from the Google CDN. If this site just happens to not be coded in manner that makes it gracefully degrade (ie. bad coding standards) then you may be stuck on the home page ...


3

Business registration is not the most economical solution to achieve privacy - see Wikipedia's domain privacy article for the more common means of achieving privacy without providing false information.


3

I can't really answer the question of what information would be missed, though I will say from an analytics standpoint we do tend to care about the browser and OS our users are visiting with (to determine what HTML features we can get away with using). Philosophically I can give you my view on the sitiation-- What CAN be done falls in to two categories: ...


3

The age-old standard for managing robots is /robots.txt. robots.txt asks robots not to crawl or index certain pages on your site. Your specific question seems to relate more to the Robots <META> tag, which belongs in the <head> of your document, and cannot be specified within a <div> tag somewhere in the body of your page. As it is, your ...


3

I would not go with a 404 page. A 404 page is not just page, but also a response. It lets the client know that the page was not found. That it was somehow deleted or the url is wrong. If you are using some sort of session to hide information that is availabe only to logged in users, then you can use your server side scripting language of choice, (asp, ...


3

To be honest, if it says "anonymous" (and that term is up for debate anyway), I'd expect it to be 100% anonymous. No Google Analytics, no Clicktale, no Piwik, no Facebook Beacons nor any other type of data gathering mechanisms. Now, of course, most website visitors wouldn't have a clue what is going on under the hood, therefore I'd expect the site provider ...


3

Don't confuse the words Anonymous and Track-able Any form of communication can be traced and extends further than the use of Google Analytics, you are miss understanding what they refer to 'anonymously'. What they are implying is that the data you input or provide will not be shared to the public nor will they ask for your name. Making a telephone call is ...


3

Google just recently released a video on this exact subject: How does duplicate copy that's legally required (ie Terms & Conditions across multiple offers) affect performance in search? So the answer from the horses mouth is I wouldn't stress about that.


3

A hosted WordPress.com blog would already seem to offer all the privacy settings you would need. Not only can this block the content from search engines, but can also be set to "invite only": Source: Site Visibility - Privacy Settings


2

One main thing is going to be disable or limit access logging. You would have to configure your Web server not to log any user's IP addresses. Also ensure access is not logged elsewhere in the system or the data center, no external applicances like reverse proxies are active, and so on. Also as @JonahBron points out, don't use sessions. Best don't serve ...


2

You could try http://www.whoisguard.com/ -- they say they offer whois privacy protection for 'existing domains' (i.e. without having to transfer them to a different registrar), which sounds like what you're after. If it were me, though, I'd just transfer the domain to someone who offers whois protection for free as part of the service (like namecheap), or ...


2

From this cross-post: To change or remove this notice you need to amend the following Template files: create.html.tmpl located in \template\en\default\account\ request-new.txt.tmpl located in \template\en\default\account\email\


2

The whole point of DNS is to make this information to other computers, so I can't think of anything that you wouldn't want to make public. You can see what can already be found out about your domain using this tool.


2

Depending on where you live there may be local privacy laws which say what you can and can't collect. However it's always best to tell people what you're going to do. The usage information you collect depends on what your aims for the site are. You should collect information which tells you how you're achieving that aim. So for example, if you want people ...


2

"Bad" is a somewhat subjective and relative term. But if you want to adhere to best practices regarding respecting user privacy, then, in addition to KoKo's answer, you can simply track the data for the minimum amount of time needed to do what you need to do, and then discard or anonymize it afterwards. This is what Google and most other major online ...



Only top voted, non community-wiki answers of a minimum length are eligible