This privacy policy has been compiled to better serve those who are concerned with how their 'Personally identifiable information' (PII) is being used online. PII, as used in US privacy law and information security, is information that can be used on its own or with other information to identify, contact, or locate a single person, or to identify an individual in context. Please read our privacy policy carefully to get a clear understanding of how we collect, use, protect or otherwise handle your Personally Identifiable Information in accordance with our website.
What personal information do we collect from the people that visit our blog, website or app?
We do not collect Personally identifiable information from visitors of our site.
When do we collect information?
We collect Personally identifiable information from you when you email it.
How do we use your information?
We do not.
How do we protect visitor information?
We do not use vulnerability scanning and/or scanning to PCI standards.
We use regular Malware Scanning.
We use an SSL certificate
— " We only provide articles and information, we never ask for personal or private information like email addresses, or credit card numbers.
Do we use 'cookies'?
Yes. The 2 cookies we use, have been actually planted by Google Analytics. They are displayed below:
__utma=24503404.1008436988.1440882060.1440882060.1440882060.1;
The __utma Cookie
This cookie is what's called a "persistent" cookie, as in, it never expires (technically, it does expire…in the year 2038…but for the sake of explanation, let's pretend that it never expires, ever). This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase.
Source: http://www.morevisibility.com/blogs/analytics/from-__utma-to-__utmz-google-analytics-cookies.html
_ga=GA1.2.1008436988.1440882060; _gat=1
cookieName text _ga
In order for Google Analytics to determine that two distinct hits belong to the same user, a unique identifier, associated with that particular user, must be sent with each hit.
The analytics.js library accomplishes this via the client ID field, a unique, randomly generated string that gets stored in the browsers cookies, so subsequent visits to the same site can be associated with the same user.
By default, analytics.js uses a single, first-party cookie named _ga to store the client ID, but the cookie's name, domain, and expiration time can all be customized.
Source: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookies-user-id#configuring_cookie_field_settings
We use cookies to:
— " Compile aggregate data about site traffic and site interactions in order to offer better site experiences and tools in the future. We may also use trusted third party services that track this information on our behalf.
You can choose to have your computer warn you each time a cookie is being sent, or you can choose to turn off all cookies. You do this through your browser settings. Each browser is a little different, so look at your browser's Help menu to learn the correct way to modify your cookies.
If you disable cookies off, some features will be disabled. It won't affect the users experience that make your site experience more efficient.
Third Party Disclosure
We do not sell, trade, or otherwise transfer to outside parties your personally identifiable information.
Third party links
Occasionally, at our discretion, we may include or offer third party products or services on our website. These third party sites have separate and independent privacy policies. We therefore have no responsibility or liability for the content and activities of these linked sites. Nonetheless, we seek to protect the integrity of our site and welcome any feedback about these sites.
Google
Google's advertising requirements can be summed up by Google's Advertising Principles. They are put in place to provide a positive experience for users. https://support.google.com/adwordspolicy/answer/1316548?hl=en
We do not use Google AdSense Advertising on our website.
We have implemented the following:
— " Demographics and Interests Reporting
We along with third-party vendors, such as Google use first-party cookies (such as the Google Analytics cookies) and third-party cookies (such as the DoubleClick cookie) or other third-party identifiers together to compile data regarding user interactions with ad impressions, and other ad service functions as they relate to our website.
No personal information is stored
COPPA (Children Online Privacy Protection Act)
When it comes to the collection of personal information from children under 13, the Children's Online Privacy Protection Act (COPPA) puts parents in control. The Federal Trade Commission, the nation's consumer protection agency, enforces the COPPA Rule, which spells out what operators of websites and online services must do to protect children's privacy and safety online.
We do not specifically market to children under 13.
CAN SPAM Act
The CAN-SPAM Act is a law that sets the rules for commercial email, establishes requirements for commercial messages, gives recipients the right to have emails stopped from being sent to them, and spells out tough penalties for violations.
We have no email lists.
If there are any questions regarding this privacy policy you may contact us using the information below.
a (at) grifare.ca
Last Edited on 2016-05-17