Skip to content

Commit

Permalink
COOKIE - Adding Cookie Policy & Info
Browse files Browse the repository at this point in the history
Adding a cookie policy and general cookie info for Font Awesome.
  • Loading branch information
alexpoiry committed Nov 9, 2022
1 parent 3e6dc2d commit 134e42b
Show file tree
Hide file tree
Showing 3 changed files with 98 additions and 1 deletion.
39 changes: 39 additions & 0 deletions Font_Awesome_Cookie_Info.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,39 @@
# FONT AWESOME COOKIE INFORMATION (DRAFT)

## Classification Level
Publicly available

## Review Information

__Mandatory Review Period__

Yearly

__Date of Last Review__



## Introduction

This cookie information document helps users identity what information we collect in cookie form and provides general
information about how and why we use cookies.

## Cookie Usage Statement

Usage of cookies aligns with our (privacy policy)[https://fontawesome.com/privacy]. Our general goal is to collect no more
data about a user than is necessary to provide our service and prevent abuse.

## Cookies

| Cookie Key | Domain | Path | Cookie Classification | Cookie Type | Expiration | Description |
|------------|--------|------|-----------------------|-------------|------------|-------------|
| __cf_bm | .vimeo.com | / | Strictly Necessary | Third-party | 30 minutes | This cookie is used by Cloudflare to distinguish between humans and bots. |
| m | m.stripe.com | / | Functionality | Third-party | 2 years | This cookie is used to manage payment activities with Stripe. |
| guardian_deafult_token | fontawesome.com | / | Strictly Necessary | First-party | 3 months | This cookie is set after login and used for authentication. |
| _ga | .fontawesome.com | / | Performance | First-party | 2 years | This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. |
| _gid | .fontawesome.com | / | Performance | First-party | 1 day | This cookie stores and updates a unique value for each page visited and is used to count and track pageviews. |
| _gat_gtag_UA_30136587_4 | .fontawesome.com | / | Targeting | First-party | 2 hours | This cookie is part of Google Analytics and is used to limit requests (throttle request rate). |
| __stripe_mid | .fontawesome.com | / | Functionality | First-party | 1 year | This cookie is part of a fraud prevention measure in Stripe's payment service. |
| __stripe_sid | .fontawesome.com | / | Functionality | First-party | 30 minutes | This cookie is part of a fraud prevention measure in Stripe's payment service. |
| _ALGOLIA | fontawesome.com | / | Functionality | First-party | 6 months | This cookie is used to manage Algolia search within Font Awesome. |
| fontawesome | fontawesome.com | / | Functionality | First-party | Session | This cookie manages session state within Font Awesome. |
58 changes: 58 additions & 0 deletions Font_Awesome_Cookie_Policy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
# FONT AWESOME COOKIE POLICY (DRAFT)

## Classification Level
Publicly available

## Review Information

__Mandatory Review Period__

Yearly

__Date of Last Review__



## Introduction

A cookie policy helps users identity what information we collect in cookie form while also providing guidance on how and
when it is acceptable for developers to add or modify cookies plus any specific steps required before rolling out cookie
changes.

### Goal Statement

The cookie policy should specify how we address cookie related issues specifically. All technical aspects should be governed
by other the appropriate policies such as the privacy policy or change management policy (as it may apply practically). This
policy should also clearly layout what cookies we use and why.

### Background Statement

We, at Fonticons, Inc., know our culture and general attitude toward privacy concerns, etc. It is entirely reasonable for
others planning to use our technology to desire to understand our goals and commitments around security and privacy. Cookie
related questions have become common enough that it is appropriate to address specifics with an official policy.

## Definitions

### Terms

* The word "we" shall mean Fonticons, Inc., all Fonticons, Inc. employees and any individuals contracting with Fonticons, Inc. to complete work.
* Cookie shall mean a text file placed on you computer by our website. They have many purposes, mostly to allow for more advanced functionality that would not other be possible via a static webpage. Some of these are absolutely necessary to provide a safe and functional experience.

## Policy

1. This policy applies to all employees.
1. Cookies are collected for the purpose of:
1. Providing a consistant experience across the website by managing state between pages
1. Securing the site from bots and other unauthorized individuals
1. Determining user traffic on the site
1. Allowing for secure payment schemes
1. Cookies must not be used for the purpose of:
1. Providing any third-party advertisement
1. Gaining data or information about users not explicitly required for Font Awesome's confidentiality, integrity, or availability
1. Specific information about all cookies used on Font Awesome must be maintained and made generally available to anyone interested in the information.

## Procedures

1. An employee that detects any violation of this policy must report the issue to their supervisor, the head of development, the head of design, the head of security, or the CTO.
1. Intentionally or maliciously violating this policy is a serious offense and grounds for termination of employment.
1. Any questions, concerns, or clarifications should be directed to the head of security or privacy@fontawesome.com
2 changes: 1 addition & 1 deletion Incident_Response_Policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,5 +65,5 @@ understand how we deal with issues, especially those that might result in a loss

## Procedures

1. An employee that detects any violation of this policy must report the issue to their supervisor, the head of development (Rob Madole), the head of security (Alex Poiry), or the CTO (Travis Chase).
1. An employee that detects any violation of this policy must report the issue to their supervisor, the head of development, the head of security, or the CTO.
1. Intentionally or maliciously violating this policy is a serious offense and is grouds for termination of employment.

0 comments on commit 134e42b

Please sign in to comment.