Wingify Data Residency

Overview of Wingify's Data Centers

Until January 2022, all Wingify data (both Wingify customer data and visitor data on the customer’s website) was stored and processed in the US East data center of the Google Cloud Platform (GCP). This setup complies with the General Data Protection Regulation (GDPR) and similar regulations. Currently, it serves over 3,000 customers globally, with more than 1,000 in the EU and India.

To meet global regulatory requirements and customer preferences, Wingify offers regional data centers:

• US data center: Situated in Northern Virginia (us-east 4 of GCP), this data center caters to those who prefer to store and manage their visitor data within the United States of America.
• EU data center: Situated in Belgium (europe-west1 of GCP), this data center caters to those who prefer to store and manage their visitor data within the EU.
• India data center: Situated in Mumbai (asia-south1 of GCP), this data center caters to those who prefer to store and manage their visitor data within India.

Note: The India data center only caters to accounts that are enabled with Data360.

Wingify collects visitor data in accordance with the Data Protection Agreement (DPA) for entities that choose to configure their accounts with these data centers. But Wingify’s actual customer account data, such as Wingify account information and Wingify campaign metadata, is stored only in the US data center.

Note: Storing customer account information and campaign metadata in the US data center does not affect Wingify’s compliance with the General Data Protection Regulation (GDPR) for the EU or the Personal Data Protection Bill for India. Wingify continues to store and process end-user data only within the respective regions for accounts configured with those data centers. Wingify does not handle any end-user data, including personally identifiable information (PII), outside the respective regional boundaries.

We recommend you review our Data Protection Addendum, which outlines the terms and conditions governing data protection.

Note: Wingify supports data center changes for all Wingify paid plans after signing up. Trial accounts are not eligible for data center changes.

Data Center Assignments and Change Requests

Wingify automatically assigns a default data center during account signup based on your location.

The following data center locations are available:

• Google Cloud Platform (GCP) – USA (Northern Virginia)
• Google Cloud Platform (GCP) – EU (Belgium)
• Google Cloud Platform (GCP) – APAC (India)

You cannot change the assigned data center directly from the Wingify application. After completing the account signup, you can find your Data Center under Settings > Account > General > Data Region. This field is disabled and serves as a point of reference only. You can also view your assigned data region in the application footer.

Request a Data Center Change

Wingify supports data center changes through a formal request process. This service is available as a managed add-on and is handled by the Wingify Sales team.

To change your assigned data center, raise a request to your Account Manager (AM) or Customer Success Manager (CSM).

Wingify processes each request through the following steps:

• Review and approval by Wingify’s Legal and Compliance teams
• Execution of a contractual amendment or updated Order Form, where applicable
• Migration and implementation by Wingify’s Engineering team

All contracts and order forms explicitly specify the applicable data center location. Wingify permits a post-signup data center change only after the above process is successfully completed.

Once the migration is complete, the AM or CSM formally confirms the data center change. This process typically takes 2–4 business days and does not impact your ongoing campaigns.

Eligibility for Non-US Data Centers

Irrespective of your plan or location, you can request data residency in any of the available data centers. However, we recommend selecting a data center located in the same region as your primary end users.

Wingify assigns a default data center to your account during signup based on your location. To request a different data center, contact your Account Manager (AM) or Customer Success Manager (CSM).

Wingify Data Classification

Wingify classifies the entirety of the data gathered into the following two categories:

• Customer account data: This is Wingify customer-specific data through which Wingify offers its services and includes campaign configurations, account configurations, billing configurations, and other similar data necessary to run the application.
• Visitor data: This is the data of the visitors (who arrive at the customer’s website) that Wingify collects as part of the campaigns executed via Wingify.

Data Flow Between Data Centers

If your account is configured with the US data center, Wingify stores and processes your campaign, account, and visitor data within the US. But in a non-US data center, the entire visitor data is stored, while only the campaign and account information reside in the US.

Wingify designs information processing so that visitor data never leaves the respective regions. The application servers for the non-US data centers fetch campaign and account information from the US and process them in their respective regions, along with the visitor data stored there.

The following table explains the information residency for the accounts configured with a non-US data center:

Type	Information	US Data Center	Non-US Data Center
Account Information & Campaign Metadata	Wingify account settings and Wingify user login details
	Campaign definitions
	Hypotheses and observations
Visitor Data	Session recordings
	Survey data
	Heatmap data
	Test campaign data
	Forms
	Goals and funnels

Note:

1. As of now, Wingify Engage does not support the EU and India data centers. The data collected through Wingify Engage will be stored in the US data center.
2. The visitor data collected by the servers is maintained in their respective server locations only and cannot be transferred or accessed by one another. To know more, refer to this article.

Technical Differences in Non-US Data Center Accounts

The Wingify application's functionality remains server-agnostic.

If your account is configured with a non-US data center, you can observe the following changes:

• Any API call from the application that handles visitor data uses an ‘eu01’ URL path prefix for the EU data center (app.wingify.com/eu01) and ‘as01’ for the India data center (app.wingify.com/as01).
• All data collection calls from websites, FME SDKs, and mobile app SDKs have an ‘eu01’ URL path prefix for the EU data center and ‘as01’ for India.
• Any API request (that handles visitor data) in the wrong location redirects to the correct location. For example, if an account configured with the EU data center attempts to access app.wingify.com, the system identifies the location and redirects the link to app.wingify.com/eu01. For India, it redirects to app.wingify.com/as01.

FAQs

• Is it possible to migrate the data of the existing clients from the US data center to a non-US data center?
  Yes. But Wingify needs to schedule data migration, as it may involve some downtime. Contact your account manager for details.
• What are the key things users need to take care of for a non-US data center? Primarily, the following guidelines apply to accounts configured with a non-US data center:
  • In case of using Wingify REST APIs, we recommend you add the respective path prefix to the URLs. For example, the REST API call to get all the campaigns in an account/sub-account will be in the following format:
    1. For the EU data center: https://app.wingify.com/eu01/api/v2/accounts/{account_id}/campaigns
    2. For the India data center: https://app.wingify.com/as01/api/v2/accounts/{account_id}/campaigns
  • For offline conversions, proceeding without the path prefix in the URL results in the conversion calls being rejected. This is because the visitor information actually resides in the respective non-US data center for an account configured accordingly. Using a URL without the path prefix routes the call to the US data center, where it gets rejected.

Glossary