- Notifications
You must be signed in to change notification settings - Fork165
Add disclaimer on fullstory#1038
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Uh oh!
There was an error while loading.Please reload this page.
Merged
Changes fromall commits
Commits
Show all changes
7 commits Select commitHold shift + click to select a range
07596de Add disclaimer on fullstory
NimRegev39e357e Update footer.html
NimRegev839d0cd Update full-story.md
NimRegev013e6b9 Update footer.html
NimRegev93acd4f Update full-story.md
NimRegev03bb956 Update privacy-policy.md
NimRegevf712228 Update privacy-policy.md
NimRegevFile filter
Filter by extension
Conversations
Failed to load comments.
Loading
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Jump to file
Failed to load files.
Loading
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,67 @@ | ||
| --- | ||
| title: "FullStory in Codefresh docs" | ||
| description: "" | ||
| toc: false | ||
| --- | ||
| ## Full Story - Data collection and tracking User Behavior | ||
| Our documentation website uses [FullStory](https://www.fullstory.com/), a third-party tool to collect data on how users interact with our content. | ||
| FullStory helps us better understand how our users navigate and engage with our website, allowing us to improve our documentation and overall user experience. | ||
| ### What kind of data do we collect with FullStory? | ||
| When you visit our documentation website, FullStory may collect the following types of data: | ||
| - **Interaction data** | ||
| Includes clicks, scrolls, mouse movements, and keystrokes (except for sensitive data such as passwords or payment information). This data helps us analyze how users interact with various elements of our website. | ||
| - **Session data** | ||
| Record of your browsing session on our site, including the pages you visit, the time spent on each page, and the sequence of actions taken. | ||
| - **Technical data** | ||
| Information about the device you are using, including your browser type, operating system, screen resolution, and IP address (anonymized). | ||
| - **Demographic data** | ||
| General demographic information like your location (country or city level) and language preference, which helps us tailor content more effectively. | ||
| Please note that demographic information is limited to generalized, location-based information. | ||
| ### Why do we collect the data? | ||
| We use the data collected by FullStory for the following purposes: | ||
| * **Improve user experience** | ||
| We analyze user behavior to identify areas where documentation is missing, and where it can be improved, ensuring that it is clear, helpful, and easy to navigate. | ||
| * **Monitor website performance** | ||
| By understanding how users interact with our site, we can optimize its performance and address any issues that may affect usability. | ||
| * **Maintain relevant content** | ||
| We use the insights to refine the content on our site, making sure it meets the needs of our users. | ||
| ### Data privacy and security | ||
| We take the privacy of our users seriously. | ||
| FullStory does not collect any sensitive personal information (such as passwords, payment details, or personal identification numbers). | ||
| All data collected is anonymized and aggregated, ensuring that individual users cannot be personally identified. | ||
| * **Anonymization** involves removing or obscuring personal identifiers, such as names, email addresses, or IP addresses. Data can be anonymized by replacing these identifiers with hash values as hashing creates a fixed-size output that cannot easily be reversed. | ||
| Hashtags can be effectively applied to anonymize sensitive data in various contexts. Common uses of hashtags include hashing user IDs when analyzing user activity, instead of storing raw user identifiers, hashing email addresses to track user behavior without exposing the raw data, and hashing IPs to analyze geographic trends without compromising user anonymity. | ||
| * **Aggregation** involves summarizing data collected at a group rather than an individual level. This allows trends to be analyzed without exposing personal details. For instance, instead of storing individual browsing history, data can be grouped and analyzed to show general trends such as "X% of users visited this page." | ||
| You can learn more about how FullStory handles data by reviewing their [privacy policy](https://www.fullstory.com/legal/privacy-policy). | ||
| ### Opting Out | ||
| If you do not wish to have your data collected by FullStory, you can opt out by enabling the "Do Not Track" setting in your web browser. | ||
| For more information, see this [article](https://www.cookieyes.com/knowledge-base/cookies-101/what-is-do-not-track/){:target="\_blank"}. | ||
| Additionally, you can visit FullStory's [opt-out page](https://www.fullstory.com/optout) to prevent data collection. | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,19 +1,19 @@ | ||
| <footer class="bd-footer text-muted"> | ||
| <div class="container-fluid p-3 p-md-5"> | ||
| <ul class="bd-footer-links"> | ||
| <li> | ||
| <a href="{{ site.baseurl }}/docs/assets/full-story/">FullStory implementation inCodefresh docsite</a> | ||
| </li> | ||
| {% comment out begin %} | ||
| <li> | ||
| <a class="text-uppercase" href="{{ site.link_plugins }}" onclick="ga('send', 'event', 'Footer', 'Docs links', 'Open Plugins');" target="_blank" rel="noopener">Plugins</a> | ||
| </li> | ||
| <li> | ||
| <a class="text-uppercase" href="{{ site.link_community }}" onclick="ga('send', 'event', 'Footer', 'Docs links', 'Open Community');" target="_blank" rel="noopener">Community</a> | ||
| </li> | ||
| {% endcomment %} | ||
| </ul> | ||
| <p>© {{ 'now' | date: '%Y' }} <a href="https://codefresh.io">Codefresh.io</a></p> | ||
| </div> | ||
| </footer> | ||
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.