Privacy Policy – PLEASE UPDATE

Who we are

Our website address is: http://impacts.org.

What personal data we collect and why we collect it

While you visit our site, we’ll track:

  • Form Fields Data: Forms Fields data includes the available field types when creating a form. We’ll use this to, for example, collect information like Name, Email and other available fields.
  • Location, IP address and browser type: we’ll use this for purposes like geolocation and reducing fraudulent activities.

We’ll also use cookies to keep track of form elements while you’re browsing our site.

When you fill out a form, we’ll ask you to provide information which may include your name, address, email, phone number, credit card/payment details and optional account information like username and password and any other form fields available in the form. We’ll use this information for purposes, such as, to:

  • Send you information about your account and order
  • Respond to your requests, including transaction details and complaints
  • Set up your account for our site
  • Comply with any legal obligations we have, such as calculating taxes
  • Or any other service the built form was created to comply with and it’s necessary information

If you create an account, we will store your name, address, email and phone number, which will be used to populate the form fields for future submissions.

We generally store information about you for as long as we need the information for the purposes for which we collect and use it, and we are not legally required to continue to keep it. This includes your name, address, email, phone number.

Members of our team have access to the information you provide us. For example, both Administrators and Editors can access:

  • Form submission information and other details related to it
  • Customer information like your name, email and address information.

Our team members have access to this information to help fulfil entries and support you.

Comments

If visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymised string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service Privacy Policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.

Contacting us

If you choose to contact us we will store information relating to your query. If you have questions about how we use your data or to request that we remove your data from our records, please contact:

Burkhard Horn
Mobility & Transport – Strategy & Planning

c/o Eckwerk Entwicklungs GmbH
Holzmarktstr
19-23 10243 Berlin
Germany

Email: impacts@burkhardhorn.de
Tel: 49017640489690

Cookies

If you leave a comment on our site you may opt in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.

If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.

When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.

If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.

Google Analytics

We use Google Analytics to measure user-interactions on our website.
Full documentation can be found on the Google Analytics Developer Guide.

Cookie NameDefault Expiration
Time
Description
__utma 2 years from set/update Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmt 10 minutes Used to throttle request rate.
__utmb 30 mins from set/update Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics.
__utmc End of browser session Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit.
__utmz 6 months from set/update
Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics.
__utmv
2 years from set/update
Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics.

Embedded content from other websites

Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.

Who we share your data with

We do not sell your information or provide it to third-parties, however we do use some tracking on our website so we can measure how users are interacting with our website, such as Google Analytics.

We use plugins that use the Stackpath Content Delivery Network (CDN). Stackpath may store web log information of site visitors, including IPs, UA, referrer, Location and ISP info of site visitors for 7 days. Files and images served by the CDN may be stored and served from countries other than your own. Stackpath’s privacy policy can be found here.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.

For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.

All information (data) is retained in the local database indefinitely, unless otherwise deleted.

Events

When you create an event you consent to being contacted by us with regards to it. You will be required to provide contact details to submit an event. We are not responsible for third party events in any way.

We reserve the right to remove or unpublish events at any time and without notice

Event, Venue, and Organizer Information

If you create, submit, import, save, or publish Event, Venue, or Organizer information, such information is retained in the local database:

  1. Venue information: name, address, city, country, province, postal code, phone, website, geographical coordinates (latitude and longitude)
  2. Organizer information: name, phone, website, email
  3. Event information: website, cost, description, date, time, image

Importing Events, Venues, and Organisers:

  1. All data present within a CSV or ICS file and external URLs (for events, venues, organisers, and tickets)
  2. Import origin data (URL from where events are being imported—such as Eventbrite, MeetUp, other compatible URL sources, and more, which can include similar or same data as listed above)
  3. Eventbrite Ticket information: name, description, cost, type, quantity

Please note that to create new events through the Community Events submission form, a user must hold a website account on this domain. This information is retained in the local database. It is also possible to create events anonymously, if the site owner has this option enabled.

When purchasing Eventbrite Tickets, attendee, purchaser, and order information are stored and managed by Eventbrite.

We make use of certain API keys, in order to provide specific features.

These API keys may include the following third party services: Google Maps, Facebook, Meetup, PayPal, and Eventbrite (API key, auth URL and Client Secret).

What rights you have over your data

If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.

Where we send your data

Visitor comments may be checked through an automated spam detection service.

Your contact information

Your contact information may be stored for the purposes of creating an account, if you have contacted us, or submitted an event.

Additional information

How we protect your data

What data breach procedures we have in place

What third parties we receive data from

What automated decision making and/or profiling we do with user data

Industry regulatory disclosure requirements