Rollei Zeiss Leica Diaprojektor- Service Ankauf Verkauf

Datenschutz EN -privacy-

Privacy police here in English.

Privacy police / Datenschutzerklärung

 
Since you are not logged in we save these settings in a cookie. These settings are therefore only active on this PC. If you are logged in at your any social media services there will be analised the visitors by these extern services- not by us.

ACTIVITY LOG

Data Used: To deliver this functionality and record activities around site management, the following information is captured: user email address, user role, user login, user display name, WordPress.com and local user IDs, the activity to be recorded, the WordPress.com-connected site ID of the site on which the activity takes place, the site’s Jetpack version, and the timestamp of the activity. Some activities may also 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 other 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.

ADS

Data Used: The following information (made available 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 is retained for 1 year.

Activity Tracked: Ad impressions, video-related events (i.e. 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.

Image views are only recorded if the site owner, has explicitly enabled image view stats tracking for this feature via thejetpack_enable_carousel_statsfilter.

Data Used: If image view tracking is enabled, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity Tracked: Image views.

CONTACT FORM

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 (also 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 was submitted and is emailed directly to the owner of the form (i.e. 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 originally submitted with the comment are synced, as well, as they are stored in post meta.

GOOGLE ANALYTICS

Data Used: Please refer to the appropriate Google Analytics documentation for the specific type of data it collects. For sites running WooCommerce (also owned by Automattic) and this feature simultaneously and having all purchase tracking explicitly enabled, purchase events will send Google Analytics the 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) over to Google Analytics for consumption. For sites running WooCommerce-powered stores, some additional events are also sent to Google Analytics: 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.

GOOGLE FONTS

Data Used: We use GOOGOLE FONTS – without accept this you can not use this website. Please refer to the appropriate  https://policies.google.com/privacy?hl   for the specific type of data it collects.

Data protection and data acquisition
What is the importance of using the Google Fonts Web API to protect the data of my users?
The Google Fonts API is designed to restrict the collection, storage and use of end user data. The use of Google Fonts Web API is not authenticated and the Google Fonts API does not set cookies or do not log it. Inquiries to Google Fonts Web API are sent to resource -specific domains such as fonts.googleapis.com or fonts.gstatic.com. Font inquiries are separated from Google.com registration data that are sent to Google.com during the use of other authenticated Google services.
What data receives Google from the visitors of my website when I embed Google Fonts via the Google Fonts Web API?
When end users visit a website on which Google Fonts are embedded, their browser send HTTP inquiries to the Google Fonts Web API. The Google Fonts Web API provides users the Google Fonts-CSS (Cascading Style Sheets) and then the font files specified in the CSS. These HTTP inquiries include (1) the IP address used by the respective user to access the Internet (2) the requested URL on the Google server and (3) The HTTP header that the user -Agent contains that contains the internet browser and the operating system versions of website visitors as well as the reference URL (i.e. the website on which the Google font should be displayed).

For clarification, it should be mentioned that Google does not use the information recorded by Google Fonts for the creation of end user profiles or for targeted advertising.

Why does Google get the IP addresses of visitors to my website when I embed Google Fonts via the Google Fonts Web API?
Google receives the IP address of the website seeker, which is processed to respond to the visitor’s request and for security purposes.

The Internet Protocol needs IP addresses to transmit data via the Internet between a specific client (i.e. browser) and a specific server. For this reason, every client request to any server contains the client’s IP address so that the server can respond to this IP address. Accordingly, the fact that Google’s servers are mandatory for the transfer of fonts is not unique for Google and is in harmony with the functioning of the Internet.

Can I embed Google Fonts into my website without sending end user data to the Google server?
Instead of calling on fonts from Google servers, developers can host web fonts locally on their website by downloading the fonts and uploading them to their server. If a font is loaded by the website of the website operator, Google does not receive any data on the website visits. However, the self -hosted Google Fonts also has some disadvantages (see below).

Further information on Google Fonts’s self -hosting can be found in the short guide thread for self -hosted web fonts.

What are the advantages of embedding Google Fonts into my website via the Google Fonts Web API?
Hosting web fonts on Google’s servers offers several advantages for both developers and end users. With Google Fonts you can give websites and other digital products personality and performance. A lot has happened of its original benefit: we want to make the web faster because your browser can save frequently used fonts on all websites that the API used in the cache. This is no longer the case, but the API continues to offer additional and important optimizations so that websites are invited quickly and the fonts work well.

Using the codes generated by Google Fonts, our servers automatically send the smallest possible file to every user. This is done with the technologies supported by the browser. For example, we use the WOFF 2.0 compression, if available. This can reduce the font size and makes the web faster for all users, especially in areas where bandwidth and connectivity pose problems. The symbols provided by Google Fonts benefit from the same infrastructure.

For sites running WooCommerce (also owned by Automattic) and this feature simultaneously and having all purchase tracking explicitly enabled, purchase events will send Google Analytics the 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.

GOOGLE TAG MANAGER

Data Used: We use the APP Google Tag Manager. Privacy of google you see here:

https://policies.google.com/?hl

GRAVATAR HOVERCARDS

Data Used: This feature will send a hash of the user’s email address (if logged in to the site or WordPress.com — or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile) to the Gravatar service (also owned by Automattic) in order to retrieve their profile image.

INFINITE SCROLL

Data Used: In order to record page views via WordPress.com Stats (which must be enabled for page view tracking here to work) with additional loads, the following information is used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity Tracked: Page views will be tracked with each additional load (i.e. when you scroll down to the bottom of the page and a new set of posts loads automatically). If the site owner has enabled Google Analytics to work with this feature, a page view event will also be sent to the appropriate Google Analytics account with each additional load.

LIKES

This feature is only accessible to users logged in to WordPress.com.

Data Used: In order to process a post like action, the following information is 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.

Activity Tracked: Post likes.

MOBILE THEME

Data Used: A visitor’s preference on viewing the mobile version of a site.

Activity Tracked: A cookie (akm_mobile) is stored for 3.5 days to remember whether or not a visitor of the site wishes to view its mobile version. Learn more about this cookie.

NOTIFICATIONS

This feature is only accessible to registered users of the site who are logged in to WordPress.com.

Data Used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Some visitor-related information or activity may be sent 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 (i.e. when we send a notification to a particular user), opening notifications (i.e. when a user opens a notification that they receive), performing an action from within the notification panel (e.g. liking a comment or marking a comment as spam), and clicking on any link from within the notification panel/interface.

PROTECT

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 (i.e. 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). We also 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’re a real human. Learn more about this cookie.

Data Synced (?): Failed login attempts, which contain the user’s IP address, attempted username or email address, and user agent information.

Data Used: Any of the visitor-chosen search filters and query data in order to process a search request on the WordPress.com servers.

SHARING

Data Used: When sharing content via email (this option is only available if Akismet is active on the site), the following information is used: sharing party’s name and email address (if the user is logged in, this information will be pulled directly from their account), IP address (for spam checking), user agent (for spam checking), and email body/content. This content will be sent to Akismet (also owned by Automattic) so that a spam check can be performed. Additionally, if reCAPTCHA (by Google) is enabled by the site owner, the sharing party’s IP address will be shared with that service. You can find Google’s privacy policy here.

SIMPLE PAYMENTS

This feature is only available by actual payment processing is handled by PayPal.

Data Used: Transaction amount, transaction currency code, product title, product price, product ID, order quantity, PayPal payer ID, and PayPal transaction ID.

Activity Tracked: The PayPal payer ID, transaction ID, and HTTP referrer are sent with a payment completion tracking event that is attached to the site owner.

Data Synced (?): PayPal transaction ID, PayPal transaction status, PayPal product ID, quantity, price, customer email address, currency, and payment button CTA text.

Because payments are processed by PayPal, we recommend reviewing its privacy policy.

SOCIAL MEDIAS

Data Used:  actuall we use social media plugins. If you are logged in in your personal sociyl medi account, they logged your website- visitors useing. We use facebook (to pivacy) / twitter (to privacy) / Instagram (to privacy) / Google+ (to privacy) & other Google Services. Please see at our „Contact“ Site what social media services we exactly use actually.

SUBSCRIPTIONS

Data Used: To initiate and process subscriptions, the following information is used: subscriber’s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user’s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given in order to access the page (REQUEST_URIandDOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.

Activity Tracked: Functionality cookies are set for a duration of 347 days to remember a visitor’s blog and post subscription choices if, in fact, they have an active subscription.

VIDEO HOSTING

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, referring URL, timestamp of event, browser language, country code. If Google Analytics is enabled, video play events will be sent there, as well.

Activity Tracked: Video plays.

WORDPRESS.COM SECURE SIGN ON

This feature is only accessible to registered users of the site with WordPress.com accounts.

Data Used: User ID (local site and WordPress.com), role (e.g. administrator), email address, username and display name. Additionally, for activity tracking (see below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity Tracked: The following usage events are recorded: starting the login process, completing the login process, failing the login process, successfully being redirected after login, and failing to be redirected after login. Several functionality cookies are also set, and these are detailed explicitly in our Cookie documentation.

Data Synced (?): The user ID and role of any user who successfully signed in via this feature.

WORDPRESS.COM STATS

Data Used: IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Important: The site owner does not have access to any of this information via this feature. For example, a site owner can see that a specific post has 285 views, but he/she cannot see which specific users/accounts viewed that post. Stats logs — containing visitor IP addresses and WordPress.com usernames (if available) — are retained by Automattic for 28 days and are used for the sole purpose of powering this feature.

Activity Tracked: Post and page views, video plays (if videos are hosted by WordPress.com), outbound link clicks, referring URLs and search engine terms, and country. When this module is enabled, Jetpack also tracks performance on each page load that includes the Javascript file used for tracking stats. This is exclusively for aggregate performance tracking across Jetpack sites in order to make sure that our plugin and code is not causing performance issues. This includes the tracking of page load times and resource loading duration (image files, Javascript files, CSS files, etc.). The site owner has the ability to force this feature to honor DNT settings of visitors. By default, DNT is currently not honored.

WORDPRESS.COM TOOLBAR

This feature is only accessible to registered users of the site who are also logged in to WordPress.com.

Data Used: Gravatar image URL of the logged-in user in order to display it in the toolbar and the WordPress.com user ID of the logged-in user. Additionally, for activity tracking (detailed below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code.

Activity Tracked: Click actions within the toolbar

ADMIN data & privacy

Contact for information or delete your storage data: