PPT Vision Inc. - Privacy Policy

We collect personally identifiable information when you provide it to us, such as when you subscribe to our email newsletter, register for one of our conferences, register to receive information about our products, or view one of our online demonstrations. This information may include name, company, title, address, phone number, fax number, email address, and other facts. This information may be stored in a secure Contact Management System.

When you log in to the partner area of our web site, we may use a "session cookie." This type of cookie helps us to recognize you if you visit multiple pages on our site during the same session, so that we don’t need to ask you for your password on each page. Once you log out or close your browser, this session cookie expires and no longer has any effect. We may also use other, more permanent, cookies to store links of pages you have visited on our web site and other non-personal information.

PPT Vision uses Google AdWords and HubSpot free conversion tracking features to collect web traffic and advertising statistics only. No personal information is collected in this manner.

We may amend this policy at any time by posting a revised version on our web site. The revised version will be effective at the time we post it.

We value your privacy. The information you give us will be used to provide you with the service you requested. It may also be shared with PPT Vision's business partners only to inform you about PPT Vision's full line of products or provide quotation or application engineering services. No information will be sold or given to any other parties.

If, at any time, you do not want to receive further correspondence from us or our business partners, please let us know.

Questions regarding this privacy statement should be sent to the email address below or to our corporate offices at:

PPT Vision Inc.
6301 West Old Shakopee Road
Minneapolis, MN 55438
Telephone: 952-996-9500
Fax: 952-996-9501

Email info@pptvision.com to contact us regarding a privacy issue.
Last update: April 15, 2011