netvibes respects every netvibers' privacy and upholds strict confidentiality. netvibes has gone to great lengths to guard and secure all User's personal information by encrypting them in its database.

To learn more, please visit our privacy policy section at http://www.netvibes.com/static.php?show=privacy

Just a few rules that help maintain good safety and security practices. They apply to every website on internet:

• Never store passwords, credit cards numbers, and any sensitive information on a Webnote, a WebMail or any online disk space. Storing passwords in Webnotes is as secure as writing them on real post-it notes and hiding them under your keyboard. The main problem is people watching over your shoulder or getting access to your account if you forget to disconnect from a secure website at the end of the session.

• Multiply your passwords. Don't use the same password for different website, especially if some of them contain information you care about. Common examples include names, date of birth and country. Be cryptic.

• Disconnect from your account when leaving your computer. This is particularly important when you access a website from a public place or from a computer that is not yours.

netvibes would never be what it stands for without you, the Users. You are also one of the vital pieces of the security architecture of netvibes.

If by any chance, despite all our efforts, you find a problem with netvibes security, please follow these guidelines:

• You should report any security question or problem to security@netvibes.com before disclosing it to the public. You can also use the netvibes feedback form located at the bottom of your netvibes page.

• When you have a security question or problem dealing, once reporting it to netvibes, please wait at least wait 9 days before announcing it to the public. Note: your patience is appreciated while the netvibes Team qualify the problem or question, test it in our lab and work on a solution.

• When reporting a security problem with netvibes, please provide the following details:
  • Platform used
  • Authenticated or not
  • Module source or output if it's module related
  • Is the problem demonstrable or repeatable?
  • How to repeat the problem (step by step, if possible with screen shots of critical section)
  • URL used
  • Even if you cannot reproduce the problem, a screenshot showing the problem
  • If possible, full dump of HTTP traffic (The output of the following Firefox extensions can be really helpful: Web Developper through Information > HTTP Header, Firebug, Live HTTP Header) when you demonstrate this problem.