# Disclaimer ## Privacy by Principle Vector's whole approach both philosophically and technically revolves around privacy, never straying from the path. Privacy is a basic, fundamental human right and should be protected at all costs. It is our goal to continue to improve and optimize our open-source ecosystem to provide the best tools to protect, enhance, and solidify your privacy. *** ## What Vector Does Not Do 1. **Collect your personal data**: no name, email, or phone number required 2. **Store your messages**: end-to-end encrypted, we can't read them even if we wanted to 3. **Require KYC**: no identity verification or ties to other social platforms 4. **Track your metadata**: no logs of who you talk to, when, or how often 5. **Track your location**: not collecting information about your location 6. **Sell your information**: zero data brokering, zero ad targeting 7. **Show you ads**: no ads, no sponsored content, no nonsense 8. **Use centralized servers**: built on Nostr, global decentralized network 9. **Tokenization**: no token/coin or financial ownership model—beware of scams 10. **Answer to Big Tech**: no corporate overlords, no investor pressure to monetize you *** Vector Privacy has no interest in your personal data as much as we have no interest in sharing our passports and IDs with criminals. Privacy is security and we have designed a system that honors and protects that with some of the best technologies that are available, accessible to everyone for free. ***Privacy isn't a feature, it's the foundation.*** *** --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://vector-privacy.gitbook.io/vector-privacy/help-center/disclaimer.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.