Who we are
In this section, you should note your site URL, as well as the name of the company, organisation, or individual behind it, and some accurate contact information.
Our website address is: https://www.narma42.eu
What personal data we collect and why we collect it
In this section you should note what personal data you collect from users and site visitors. This may include personal data, such as name, email address, personal account preferences; transactional data, such as purchase information; and technical data, such as information about cookies.
You should also note any collection and retention of sensitive personal data, such as data concerning health.
In addition to listing what personal data you collect, you need to note why you collect it. These explanations must note either the legal basis for your data collection and retention or the active consent the user has given.
Personal data is not just created by a user’s interactions with your site. Personal data is also generated from technical processes such as contact forms, comments, cookies, analytics, and third-party embeds.
By default WordPress does not collect any personal data about visitors, and only collects the data shown on the User Profile screen from registered users. However some of your plugins may collect personal data. You should add the relevant information below.
use this subsection to note what personal data is captured when someone submits a contact form, and how long you keep it. For example, you may note that you keep contact form submissions for a certain period for customer service purposes, but you do not use the information submitted through them for marketing purposes.
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
|_ga [x4]||Google Tag Manager
||Registers a unique ID that is used to generate statistical data on how the visitor uses the website.||2 years||HTTP Cookie|
|_gat [x2]||Used by Google Analytics to throttle request rate||1 day||HTTP Cookie|
|_gid [x4]||Google Tag Manager
||Registers a unique ID that is used to generate statistical data on how the visitor uses the website.||1 day||HTTP Cookie|
|collect||Used to send data to Google Analytics about the visitor’s device and behaviour. Tracks the visitor across devices and marketing channels.||Session||Pixel Tracker|
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
|_fbp||Google Tag Manager||Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.||3 months||HTTP Cookie|
|ads/ga-audiences||Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor’s online behaviour across websites.||Session||Pixel Tracker|
|fr||Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.||3 months||HTTP Cookie|
|GPS||YouTube||Registers a unique ID on mobile devices to enable tracking based on geographical GPS location.||1 day||HTTP Cookie|
|IDE||Used by Google DoubleClick to register and report the website user’s actions after viewing or clicking one of the advertiser’s ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.||1 year||HTTP Cookie|
|PREF||YouTube||Registers a unique ID that is used by Google to keep statistics of how the visitor uses YouTube videos across different websites.||8 months||HTTP Cookie|
|test_cookie||Used to check if the user’s browser supports cookies.||1 day||HTTP Cookie|
|tr||Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.||Session||Pixel Tracker|
|VISITOR_INFO1_LIVE||YouTube||Tries to estimate the users’ bandwidth on pages with integrated YouTube videos.||179 days||HTTP Cookie|
|YSC||YouTube||Registers a unique ID to keep statistics of what videos from YouTube the user has seen.||Session||HTTP Cookie|
|yt-remote-cast-installed [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Session||HTML Local Storage|
|yt-remote-connected-devices [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Persistent||HTML Local Storage|
|yt-remote-device-id [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Persistent||HTML Local Storage|
|yt-remote-fast-check-period [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Session||HTML Local Storage|
|yt-remote-session-app [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Session||HTML Local Storage|
|yt-remote-session-name [x2]||YouTube||Stores the user’s video player preferences using embedded YouTube video||Session||HTML Local Storage|
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.
Who we share your data with
In this section, you should name and list all third-party providers with whom you share site data, including partners, cloud-based services, payment processors, and third party service providers, and note what data you share with them and why. Link to their own privacy policies if possible.
How long we retain your data
In this section you should explain how long you retain personal data collected or processed by the web site. While it is your responsibility to come up with the schedule of how long you keep each dataset for and why you keep it, that information does need to be listed here. For example, you may want to say that you keep contact form entries for six months, analytics records for a year, and customer purchase records for ten years.
Suggested text: 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.
What rights you have over your data
In this section, you should explain what rights your users have over their data and how they can invoke those rights.
Suggested text: You can 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
In this section, you should list all transfers of your site data outside the European Union and describe the means by which that data is safeguarded to European data protection standards. This could include your web hosting, cloud storage, or other third party services.
European data protection law requires data about European residents which is transferred outside the European Union to be safeguarded to the same standards as if the data was in Europe. So in addition to listing where data goes, you should describe how you ensure that these standards are met either by yourself or by your third-party providers, whether that is through an agreement such as Privacy Shield, model clauses in your contracts, or binding corporate rules.
Suggested text: Visitor comments may be checked through an automated spam detection service.
Your contact information
In this section, you should provide a contact method for privacy-specific concerns. If you are required to have a Data Protection Officer, list their name and full contact details here as well.
How we protect your data
In this section you should explain what measures you have taken to protect your users’ data. This could include technical measures such as encryption; security measures such as two-factor authentication; and measures such as staff training in data protection. If you have carried out a Privacy Impact Assessment, you can mention it here too.
What data breach procedures we have in place
In this section, you should explain what procedures you have in place to deal with data breaches, either potential or real, such as internal reporting systems, contact mechanisms, or bug bounties.
What third parties we receive data from
What automated decision making and/or profiling we do with user data
If your web site provides a service which includes automated decision making – for example, allowing customers to apply for credit, or aggregating their data into an advertising profile – you must note that this is taking place, and include information about how that information is used, what decisions are made with that aggregated data, and what rights users have over decisions made without human intervention.
Industry regulatory disclosure requirements
If you are a member of a regulated industry, or if you are subject to additional privacy laws, you may be required to disclose that information here.