Source: https://www.aufundab.eu/en/datenschutz
Timestamp: 2019-06-27 12:06:57
Document Index: 27613373

Matched Legal Cases: ['Art. 6', 'Art. 6', 'Art. 6', 'Art. 6', 'Art. 6', 'Art. 6', 'Art. 28', 'Art. 6', 'Art. 6']

Link to the imprint: https://www.aufundab.eu/impressum
In conclusion, our online offering requires us to be able to keep track of whether users who are interested in affiliate links and / or the offers available to us, then take advantage of the offers on the affiliate links or our online platform. For this, the affiliate links and our offers are supplemented by certain values, which can be part of the link or otherwise, eg in a cookie. The values include in particular the source website (referrer), time, an online identifier of the operator of the website on which the affiliate link was located, an online identifier of the respective offer, an online identifier of the user, as well as tracking specific values such as ad ID, affiliate ID and categorization.
For more information about Affilinet's data usage and opt-out options, please see the company's privacy policy: https://www.affili.net/de/footeritem/datenschutz.
OUTTRA Partner Program
Integration of services and contents of OUTTRA
On the basis of our legitimate interests (ie interest in the economic operation of our online offer within the meaning of Art. 6 (1) lit. DSGVO), we are participants of the 81 MEDIA GmbH partner program. For the function of calling up the goods availability we use the component OUTTRA of the 81 MEDIA GmbH, Ziegelbrennerstr. 5, 73074 Stuttgart. To display this function, a query of the visitor's IP address by the component is required. The component initially uses the IP address solely to send the browser or visitor appropriate information. The IP address is thus required for the representation of this function.
With a click on an offer, a forwarding to the respective shop takes place. Here, the IP address is stored. After 24 hours, this IP address will be anonymized.
To display the product availability of the product selected by the visitor via the "Local Offers" function, GEO coordination or a zip code entered by the visitor is transmitted to the server of OUTTRA and processed.
For the function "notification", the visitor enters his e-mail address in the system, which is processed by OUTTRA. This function works according to the double opt-in procedure. A deregistration is possible at any time via any of the notification e-mails. The e-mail address will be deleted.
Mountain Friends Partner Program
Based on our legitimate interests (ie interest in the economic operation of our online offer within the meaning of Art. 6 (1) lit. DSGVO), we are participants in the partner program of Bergfreunde, Bahnhofstr. 26, 72138 Kirchentellinsfurt, Germany, which was designed to provide a medium for websites by means of which the placement of advertisements and links to Bergfreunde advertising reimbursement can be earned (so-called affiliate system). Bergfreunde uses cookies in order to understand the origin of the contract. Among other things can Mountain friends recognize that you have clicked on the partner link on this website and subsequently concluded a contract with or about Mountain friends have made.
Further information on the use of data by Bergfreunde and contradictory options can be found in the privacy statement of the company: https://www.bergfreunde.de/datenschutz/.
Comments, contributions, surveys
When contacting us (eg by contact form, e-mail, telephone or via social media), the information provided by the user to process the contact request and its processing acc. Art. 6 para. 1 lit. b. (in the context of contractual / pre-contractual relationships), Art. 6 para. 1 lit. f. (other requests) DSGVO processed. User information can be stored in a Customer Relationship Management System ("CRM System") or comparable request organization.
CRM system from Zoho
We use the CRM system of the supplier Zoho Corporation Pvt. Ltd, 4141 Hacienda Drive Pleasanton, California 94588, USA, in order to be able to process requests from users more quickly and efficiently (legitimate interest in accordance with Art. 6 (1) lit. DSGVO).
Zoho is certified under the Privacy Shield Agreement, providing an additional guarantee to comply with European data protection law when processing data in the US (https://www.privacyshield.gov/participant?id=a2zt0000000TOJbAAO&status=Active).
Zoho uses users' data only for the technical processing of inquiries and does not pass them on to third parties. To use Zoho at least the specification of a correct e-mail address is necessary. A pseudonymous use is possible. During the processing of service requests it may be necessary to collect further data (name, address).
If users disagree with data collection and data storage in Zoho's external system, we will provide them with alternative ways to submit service requests by e-mail, telephone, fax or post.
Further information is available to users in Zoho's privacy policy: https://www.zoho.com/privacy.html
Credentials: To subscribe to the newsletter, it is sufficient to provide your e-mail address. Optionally, we ask you to give a name, for the purpose of personal address in the newsletter.
The dispatch of the newsletter takes place by means of the dispatch service provider "Zoho", contact address and data protection regulations of the service provider above under "Zoho-CRM". The shipping service provider is based on our legitimate interests gem. Art. 6 para. 1 lit. f. DSGVO and a contract processing agreement acc. Art. 28 (3) sentence 1 DSGVO.
New Relic - Server Monitoring and Error Tracking
For these purposes, we use the service New Relic, Inc. Attn: Legal Department 188 Spear Street, Suite 1200 San Francisco, CA 94105, USA. New Relic is certified under the Privacy Shield Agreement, providing a guarantee to comply with European data protection law (https://www.privacyshield.gov/participant?id=a2zt0000000TNPiAAO&status=Active).
New Relic processes aggregated performance data, ie performance, utilization and comparable technical values, which provide information about the stability and any conspicuous features of our online offering. In the case of errors and conspicuousness, individual requests of the users of our online offer are pseudonyms to identify and correct problem sources. In this case, pseudonym means in particular that the IP addresses of the users are stored shortened by the last two digits (so-called IP masking). The aggregated data is deleted after three months and the pseudonymized data after seven days.
For more information about the processing of personal information by New Relic, please refer to the privacy policy of the service: https://newrelic.com/termsandconditions/privacy.
We use Google's online AdWords marketing tool "AdWords" to place ads on the Google advertising network (eg, in search results, in videos, on websites, etc.) to show them to users who have a suspected interest in the ads. This allows us to better target advertisements for and within our online offering so that we only present ads to users that potentially match their interests. For example, if a user sees ads for products he's been looking for on other online offerings, that's called remarketing. For these purposes, upon access to our and other websites where the Google Advertising Network is active, Google will immediately execute a code from Google and become so-called (re) marketing tags (invisible graphics or code, also as " Web beacons ") incorporated into the website. With their help, the user's device stores an individual cookie, ie a small file (instead of cookies, comparable technologies can also be used). In this file is noted which web pages the user visited, for what content he is interested and what offers the user has clicked, as well as technical information about the browser and operating system, referring web pages, visit time and other information on the use of the online offer.
The data of the users are pseudonym processed in the context of the Google advertising network. For example, Google does not store and process users' names or e-mail addresses, but processes the relevant data in a cookie-related manner within pseudonymous user profiles. That is, from the perspective of Google, the ads are not managed and displayed to a specifically identified person, but to the cookie owner, regardless of who that cookie owner is. This does not apply if a user has expressly allowed Google to process the data without this pseudonymization. The information collected about users is transmitted to Google and stored on Google's servers in the United States.
The data of the users are pseudonym processed in the context of the Google advertising network. For example, Google does not store and process users' names or e-mail addresses, but processes the relevant data in a cookie-related manner within pseudonymous user profiles. That is, from the perspective of Google, the ads are not managed and displayed to a specifically identified person, but to the cookie owner, regardless of who that cookie owner is. This does not apply if a user has expressly allowed Google to process the data without this pseudonymization. The information collected about users through Google Marketing Services is transmitted to Google and stored on Google's servers in the United States.
We use the "Scalable Central Measurement Method" (SZM) of INFOnline GmbH (INFOnline GmbH, Brühler Str. 9, D-53119 Bonn.) For the determination of statistical parameters for determining the copy probability of texts. Anonymous measurements are taken. Alternatively, traffic metering uses a session cookie or a signature created from various automatically transmitted information from your browser to recognize computer systems. IP addresses are only processed in anonymous form. The procedure was developed in compliance with data protection. The only goal of the procedure is to determine the copying probability of individual texts. At no time individual users are identified. Your identity always remains protected. You will not receive advertising through the system.
Here user data and metadata of the users are processed, whereby the IP addresses are shortened and the measurement procedures are pseudonymous. The shortened IP address is stored for a maximum of 60 days. The usage data in connection with a pseudonymous assignment value ("identifier") are stored for a maximum of 6 months.
Users are also provided with an opt-out in order to object to the above mentioned purposes: https://optout.ioam.de, Further information can be found in the INFOnline privacy policy https://www.infonline.de/datenschutz/benutzer.
We point out that data of the users outside the area of the European Union can be processed. This can result in risks for the users, because for example the enforcement of the rights of the users could be made more difficult. As for US providers certified under the Privacy Shield, we point out that they are committed to upholding the EU's privacy standards.
- Google (Google LLC, 1600 Amphitheater Parkway, Mountain View, CA 94043, USA) - Privacy Policy: https://policies.google.com/privacy, Opt-out: https://adssettings.google.com/authenticated, Privacy Shield: https://www.privacyshield.gov/participant?id=a2zt000000001L5AAI&status=Active.
- Twitter (Twitter Inc., 1355 Market Street, Suite 900, San Francisco, CA 94103, United States) - Privacy Policy: https://twitter.com/de/privacy, Opt-out: https://twitter.com/personalization, Privacy Shield: https://www.privacyshield.gov/participant?id=a2zt0000000TORzAAO&status=Active.
We may embed the videos of the Vimeo platform of Vimeo Inc., Attention: Legal Department, 555 West 18th Street New York, New York 10011, USA. Data protection: https://vimeo.com/privacy, We point out that Vimeo can use Google Analytics and refer to the Privacy Policy (https://www.google.com/policies/privacy) as well as opt-out options for Google Analytics (http://tools.google.com/dlpage/gaoptout?hl=de) or Google's data-use settings for marketing purposes (https://adssettings.google.com/.).
We include the maps of the service "OpenStreetMap" (https://www.openstreetmap.de), which are offered by the OpenStreetMap Foundation (OSMF) based on the Open Data Commons Open Database License (ODbL). Data protection: https://wiki.openstreetmap.org/wiki/Privacy_Policy.
The data can be processed in the USA. Further information can be found in the privacy policy of OpenStreetMap: https://wiki.openstreetmap.org/wiki/Privacy_Policy.
This site uses the services of Outdooractive via an API. Provider is the Outdooractive GmbH, Missener Str. 18, 87509 Immenstadt im Allgäu, Germany.
To use the functions of Outdooractive, it may be necessary to save your IP address and usage data. The provider of this page has no influence on this data transfer.
The use of Outdooractive is in the interest of an attractive presentation of our online offers and an easy findability of the places, tours and POIs that we provide on the website. This constitutes a legitimate interest within the meaning of Art. 6 para. 1 lit. f DSGVO.
For further information on the handling of user data by Outdooractive see the privacy statement of Outdooractive: https://www.outdooractive.com/de/datenschutz.html
This site uses the services of Strava, Inc. through an API Provider is Strava, Inc, 500 3rd Street, Suite 110 San Francisco, CA 94107, United States.
To use the functions of Strava, it may be necessary to save your IP address and usage data. The provider of this page has no influence on this data transfer.
The use of Strava is in the interest of an appealing presentation of our online offers and an easy findability of the places, tours and POIs that we provide on the website. This constitutes a legitimate interest within the meaning of Art. 6 para. 1 lit. f DSGVO.
For more information on the handling of user data by Strava, see Strava's privacy policy: https://www.strava.com/legal/privacy.
We organize raffles. Of course, we have to collect certain data required for the raffle. We store the necessary contact data and shipping address for the implementation. In the event that we pass on this data to external third parties (eg publisher, dealer or manufacturer of the product advertised in the raffle) so that they can, for example, send the winnings, we ask in advance by email or another suitable contact for the consent whether we be allowed to pass on the data.
The storage of the data with us only covers the minimum data required for the raffle: name, e-mail address and possibly postal address. We pass these beyond what is necessary to convey the profits, not further.
This feature only records the activities of a site's registered users, and the retention period of activity data will depend on the site's plan and activity type.
Data Used: User_mail_address, user_role, user_login_name, user_display_name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com web site. connected site ID of the site on which the activity takes place, the site's Jetpack version, and the time stamp of the activity. Some activities may include the actor's IP address (login attempts, for example) and user agent.
Activity Tracked: Login attempts / actions, post and page update and publish actions, comment / pingback submission and management actions, plugin and theme management actions, widget updates, user management actions, and the modification of various site settings and options. Retention duration of activity data depends on the site's plan and activity type. See the complete list of currently-recorded activities (along with retention information).
Data Synced (?): Successful and failed login attempts, which will include the actor's IP address and user agent.
Data Used: The following information (obtained from the visitor's browser) is collected and sent to Automattic's Demand Partners: IP address, geographical data (derived from the IP address), user agent, operating system, device type, unique user ID (randomly generated identifier) , current URL, and IAB (Interactive Advertising Bureau) interest category. Log data (IP address, geographical data, user agent, operating system, device type) is stored for 30 days. The unique user ID is stored in cookies and remains for 1 year.
Activity Tracked: Ad impressions, video-related events (ie pause, mute, 100% plays, etc.) or errors, and ad click events. Various cookies are used for the following purposes: delivering targeted advertisements to specific visitors, storing user identifiers, and collecting anonymous ad platform stats.
Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, URL, timestamp of event, browser language, country code.
Data Used: WordPress.com user ID / username, the local site-specific user ID (if the user is signed in to the site) on which the like occurred), and a true / false data point. If you perform a like action from one of our mobile apps, some additional information is used to track the activity: IP address, user agent, time stamp of event, blog id, browser language, country code, and device info.
Data Used: If Akismet is enabled on the site, the contact form submission data - IP address, user agent, name, email address, website, and message - is submitted to the Akismet service (ie owned by Automattic) for the sole purpose of spam checking. The actual submission data is stored in the database of the site on which it is submitted and is emailed directly to the owner of the form (ie the site author who published the page on which the contact form resides). This email will include the submitter's IP address, timestamp, name, email address, website, and message.
Data Synced (?): Post and post meta data associated with a user's contact form submission. If Akismet is enabled on the site, the IP address and user agent are originally submitted with the comment are synced, as well as they are stored in post meta.
Data Used: Please refer to the appropriate Google Analytics documentation for the specific type of data it collects. For sites running WooCommerce (ie owned by AutomatticThe following information: order number, product id and name, product category, total cost, and quantity of items purchased. Google Analytics does offer IP anonymization, which can be enabled by the site owner.
Activity Tracked: This feature sends page view events (and potentially video play events) about Google Analytics for consumption. For sites running WooCommerce-powered stores, there are also some additional events: shopping cart additions and removals, product listing views and clicks, product detail views, and purchases. Tracking for each specific WooCommerce event needs to be enabled by the site owner.
Data Used: This feature wants to send a hash to the user's email address (if logged in to the site or WordPress.com - or if they have submitted a comment on the site using their email address that is attached to an active Gravatar profile) Gravatar service (ie owned by Automattic) in order to retrieve their profile image.
Data Used: In order to record page views via WordPress.com Stats IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, (which must be in), with additional loads, the following information is used: visiting URL, URL, timestamp of event, browser language, country code.
Activity Tracked: Page views will be tracked with each additional load (ie when you scroll down to the bottom of the page and a new set of posts automatically). If the site owner has enabled Google Analytics Google Analytics account with each additional load.
Data Used: Commenter's name, email address, and website URL (if provided via the comment form), timestamp, and IP address. Additionally, a jetpack.wordpress.com IFrame receives the following data: WordPress.com blog ID attached to the site, commenter's local user ID (if available), commenter's local username (if available), commenter's site URL (if available), MD5 hash of the commenter's email address (if available), and the comment content. If Akismet (ie owned by Automattic) is enabled on the site, the commenter's name, email address, site URL, IP address, and user agent.
Activity Tracked: The comment author's name, email address, and website URL (if provided during the submission submission) are stored in cookies. Learn more about these cookies.
Data Synced (?): All data and metadata (see above) associated with comments. This includes the status of the comment and, if Akismet is enabled on the site, whether or not it is classified as spam by Akismet.
Data Used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser language, country code.
Data Used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, URL, timestamp of event, browser language, country code. Some visitor-related information or activity may be submitted to the site owner via this feature. This may include: email address, wordpress.com username, site URL, email address, comment content, follow actions, etc.
Activity Tracked: Sending notifications (ie when we send a notification to a particular user), opening notifications (ie when a user opens a notification that they receive), performing an action in the notification panel (eg liking a comment or marking a comment as spam) , and clicking on any link from within the notification panel / interface.
Data Used: In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user's IP address, attempting user's email address / username (ie according to the value they were attempting to use during the login process), and all IP related HTTP headers attached to the attempting user.
Activity Tracked: Failed login attempts (these include IP address and user agent). So we set a cookie (jpp_math_pass) for 1 day to remember if / when a user has successfully completed a math captcha to prove that they are a real human. Learn more about this cookie.
Data Used: When sharing content via email (this option is only available if Akismet is active on the site), IP address (for spam checking), user agent (for spam checking), and email body / content. This content wants to be sent to Akismet (ie owned by Automattic) so that a spam check can be performed. Additionally, if reCAPTCHA (by Google) is the owner of the IP address. You can find Google's privacy policy here.
Activity Tracked: The PayPal payer ID, transaction ID, and HTTP referrer are sent to the site owner.
Data Used: To initiate and process subscriptions, the following is used: subscriber's email address and the ID of the post or comment (depending on the specific subscription being processed). Http://ipp.me/1/********************************************************************************************************** access the page (REQUEST_URI and DOCUMENT_URI). This server data is used for the exclusive purpose of monitoring and abuse.
Data Used: For video play tracking via WordPress.com Stats, the following information is used: viewer's IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, URL, timestamp of event, browser language, country code , If Google Analytics is enabled, video play events wants to be there, as well.