What is IDVector?

IDVector is a service that enables users to establish secure, private, and anonymous Internet connections. IDVector provides secure shared and private paths from an IDVector Client, across untrusted Internet access provider infrastructure, ultimately exiting the IDVector Path in the geographic location of the user’s choosing. IDVector cannot access the content of any traffic that transits these IDVector Paths. Encryption keys for client traffic are not shared with or stored by IDVector infrastructure; we have no way of decrypting the communications of our users. Additionally, we have no way of telling who an IDVector user is communicating with, and because we sell IDVector clients through resellers, we have no way of knowing who owns a IDVector client.

Requests for IDVector Account Information

IDVector responds to valid legal process issued in compliance with U.S. law. Requests for user account information from U.S. law enforcement should be directed to IDVector through proper service of process.

Service of Process 

IDVector accepts service of court orders, search warrants, and subpoenas for information via email from law enforcement and government agencies, provided that such requests are sent from an official government email address. Law enforcement and/or government agencies should submit legal requests directly from their official government email address to: legal@idvector.net.

While electronic service is preferred, process may also be served by registered mail or courier to:

IDVector, Inc.
Attn: Legal
46040 Center Oak Plaza
Ste 165
Sterling, VA 20166

Private Information Requires a Subpoena or Court Order

Non-public information about IDVector users’ accounts will not be released to law enforcement except in response to appropriate legal process such as a subpoena, court order, or other valid legal process.

Contents of Communications Are Not Available

Our response to all legal requests for user content will state that content is both unreadable and not stored on our servers. 

Information Required in Account Information Requests

Law enforcement or government requests for user information must include:

  • Identifying information of the entity being investigated, such as User ID
  • A description of information being sought

The descriptions should be as narrow and specific as possible in order to avoid misinterpretation and/or objections for overly broad requests. IDVector will construe received requests narrowly to maintain users’ privacy and ensure that any information disclosed does not exceed the scope of the request.

IDVector requires law enforcement and/or government agencies to include the following information so that requests for user information may be validated:

  • Requesting law enforcement/government agency
  • Requesting agent name and badge/ID number
  • Valid agency e-mail address and physical return address
  • Phone number of requesting agent, including extension when applicable
  • Response due date
  • A copy of the court order, warrant, or subpoena

Will IDVector Notify Users of Requests for Account Information?

IDVector's policy is to notify users of requests for their account information prior to disclosure including providing user with a copy of the request, unless we are prohibited by law from doing so. As soon as legally permitted to do so, we will notify our users of requests for their information.

What Information Does IDVector Store?

IDVector maintains the following information about user accounts:

  • Date an account was created
  • Type, software version and unique identifier of IDVector client used to connect
  • Identifier used for payment processing (Stripe customer identifier)
  • Limited records of recent account activity (includes only bandwidth metering, session identifiers, and private path ownership)

IDVector maintains the following information about IDVector Paths while they are in use:

  • IP address information of constituent ephemeral cloud instances
  • Path ownership data
  • Internal IDVector Path Identifier

IDVector collects and maintains the following information about a users connection to IDVector servers while their client is running:

  • Unique session ID
  • Client’s Internet routable IP address
  • Approximate geolocation data associated with the client’s IP address

IDVector maintains the following information pertaining to aggregate service usage statistics:

  • Non-user identifiable usage statistics for shared paths and private path creation
  • Non-user identifiable usage statistics for path network load and throughput

Emergency Disclosure Requests

IDVector may provide information to law enforcement in response to a valid emergency disclosure request.
We review emergency disclosure requests on a case-by-case basis and in accordance with applicable law. Good-faith requests in support of exigent circumstances involving serious physical injury to a person, or death, we may provide information to law enforcement to prevent harm, if we have it.

Law enforcement agencies can submit an emergency disclosure request via email: legal@idvctor.net.

Emergency disclosure requests must be on law enforcement letterhead and include all of the following information:

  • Identity of the person who is in danger of death or serious physical injury;
  • The nature of the emergency;
  • IDVector identifying information (user name, email address, or phone number) of the subject account(s) whose information is necessary to prevent the emergency;
  • The specific information requested and why that information is necessary to prevent the emergency;
  • The signature of the submitting law enforcement officer; and
  • Any other relevant details about the circumstances that we should take into account.

Preservation Requests

Upon receipt of a valid preservation request from law enforcement under applicable law, we will temporarily preserve the relevant and available data for 90 days pending service of legal process. We will not disclose preserved records without receipt of valid legal process.

Preservation requests should be on law enforcement letterhead, signed by the requesting official, and include a valid official email address. Preservation requests may be submitted via the aforementioned methods.

Responding to Civil Subpoenas

Account Content

Parties to civil litigation may satisfy party and non-party discovery requirements by seeking the contents of an account directly from the user. IDVector has no way of associating an IDVector ID with an individual unless they used their own name, email address, or phone number as their IDVector identifier.

IDVector does not preserve account content in response to a request from a private party.

Customer Records

IDVector may provide what customer records we have in response to a valid subpoena issued by a federal, Delaware or Virginia court where the requested information is indispensable to the case and not already within a party’s possession. It is IDVector’s policy to give affected account holders prior notice before complying with such subpoenas.

Parties seeking basic subscriber information must specifically identify accounts by IDVector ID.

While electronic service is preferred, process may also be served by registered mail or courier to:

IDVector, Inc.
Attn: Legal
46040 Center Oak Plaza
Ste 165
Sterling, VA 20166

Production of Records and Authentication 

We provide responsive records in electronic format and believe that any records produced in response to a valid law enforcement request are self-authenticating. If you require a declaration, please explicitly note that in your request. We reserve the right to seek reimbursement for the costs of producing records, where appropriate. 

Mutual Legal Assistance Treaties 

It is IDVector’s policy to promptly respond to requests that are issued via the U.S. courts upon proper service of process either by way of a mutual legal assistance treaty or letters rogatory.

Policy Subject to Change

IDVector reserves the right to update, revise, or otherwise change the policies described herein. Changes to policy will be clearly highlighted and communicated to users via both the web site and in system messages via the service.