|
This article covers the following: |
Overview
Wingify Privacy Center helps you configure what data you want to collect from your website visitors. Using this option, you can ensure visitor privacy by defining what data you would like to track and at what level.
To access the Privacy Center:
- Navigate to the Profile menu in the top right and click Settings.
- Go to Accounts > Privacy Center.
Wingify allows you to configure the privacy settings for your website visitors in the following ways:
IP Addresses
Wingify uses IP addresses to check for both traffic and to get location information. This setting only controls how the IP value is stored in Wingify servers. The option to configure how location information is stored in Wingify is available in the next section. By default, Wingify anonymises the last part of the IP address to protect visitor privacy as explained below:
- For IPv4 addresses, the last octet (the last set of digits after the third dot) is replaced with 0. For example, 34.107.218.251 is stored as 34.107.218.0.
- For IPv6 addresses, Wingify anonymizes the last 5 segments (the last 5 sets of hexadecimal numbers separated by colons). For example, 2401:4900:60f3:229d:acb4:23a2:fadc:8b72 is stored as 2401:4900:60f3::.
You can adjust how Wingify stores the IP addresses by selecting one of the following options in Settings > Accounts > Privacy Centre under the Select how Wingify will store IP address of your website visitors dropdown.
Visitor Tracking Storage Location
Wingify provides a dedicated setting to control where visitor tracking data is stored in the user's browser. By default, this data is stored in Cookies. You can change this location to Local Storage of your browser from the Privacy Center using the Visitor Tracking Storage Location setting.
Prerequisite: You must have Admin permissions to modify the Visitor Tracking Storage Location setting.
To change the visitor tracking storage location:
- Navigate to the Privacy Center by clicking the Profile menu located in the top-right corner and selecting Settings from the menu.
- Go to Privacy Center > Visitor Tracking Storage Location.
- Based on where you want to store the tracking data, select Cookies or Local Storage.
- Cross-domain tracking (tracking visitors across multiple related domains or subdomains) is not supported when Local Storage is enabled.
- When you switch the storage location, Wingify automatically migrates all existing visitor tracking information, including the visitor's unique identifier (UUID), from the previously selected location to the newly selected location. For example, if the current storage location is Cookies and you switch to Local Storage, the visitor's UUID will be migrated from the browser cookies to the local storage.
Location
Wingify stores location information of your website visitors which includes- country, region, and city. Using the Store Location Information option present in Profile menu > Settings > Accounts > Privacy Center, you can specify what level of visitor location information you want to store. If you do not want to track visitor location, simply uncheck the option. This option does not impact your geo-targeting for campaigns; it only decides how the location information is stored in Wingify.
You can use the location filter during reports segmentation, only if this option is enabled.
Data Security
You can configure your privacy settings not to record or track any information about your website visitors. All modern browsers allow visitors to select if their activities on the browser can be tracked like websites visited, and so on.
If you select the option Adhere to Do Not Track Settings, the Wingify app will respect the visitors' browser settings and will not track any activity. Also, Wingify will not drop any cookies on the visitor's browser. To know more about cookies in Wingify, refer to Cookies stored by Wingify.
By default, this option is not selected, and Wingify tracks the visitor activities regardless of whether or not the visitor has configured the Do Not Tracking option in their browser settings.
If you are self-hosting your test files on your own server, the Adhere to Do Not Track Settings feature will not work.
Configure SameSite Attribute
With the version 80 update of Google Chrome, there is a criterion that allows cookies to be accessed with 3rd-party context only when their SameSite attribute is set to None and secure. This means you intentionally allow the cookie to be accessed with a third-party context.
This improves privacy by preventing cross-domain information leakage, but this update might affect how visitors are uniquely tracked if parts of your website (or the entire website) load in an iframe.
To know more about the SameSite cookie attribute, refer to SameSite Cookie.
Anonymize Page URLs
Wingify by default prevents any sensitive information such as emails, phone numbers, passwords from reaching the Wingify servers. You can use this section to customize the default set by Wingify. All anonymized query parameters are displayed as wingify_anonymized to the end-user. By default, Wingify detects information formats for email addresses and phone numbers and looks for query parameters that may contain authentication tokens, passwords, and usernames. Using the Anonymize Query Parameters you can:
- Disable the query parameters for which you want to ensure that no sensitive information is captured and sent to Wingify. You can do this by entering the query parameters in the Blacklist (List of query parameters to anonymize) field
- Enable the query parameters which according to you must be sent to Wingify servers as they do not hold any sensitive information. This can be done by entering the parameters in the Add Whitelist (List of query parameter to be excluded from anonymization) field For example, to define a regex value for email, you can add the following query parameters as Email=[a-zA-Z0-9_.+-]+@[a-zA-Z0-9-]+\.[a-zA-Z0-9-.]+
By default, Wingify blacklist’s the following- email address, credit card number, passwords, SSN, and IP address.
Note:
- The password field is always anonymized, regardless of whether you whitelist it.
- For numerical inputs such as credit card numbers, Social Security numbers, or CVV codes, enabling anonymization replaces the actual input with zeroes.
- By default, Wingify replaces the last octet of an IP address with
0before saving it.
IP Addresses to Exclude
Excluding IP addresses enables you to avoid tracking certain individual IP addresses, IP ranges, and regular expressions on the web pages where the Wingify SmartCode is running. To learn about excusing the IP addresses, refer to How to Exclude IP Addresses from Wingify Tracking?
Need more help?
For further assistance or more information, contact Wingify Support.