InCountry Cookies Policy

InCountry uses data collected by cookies and JavaScript to improve your browsing experience, analyze site traffic, personalize content, and increase the overall performance of our site.

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

Necessary

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

• Cookie: FT_Date_First_Website_Visit
  Duration: 1 year 1 month 4 days
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: Landing_Page
  Duration: 1 year 1 month 4 days
  Description: custom cookie to save user first landing page and send this info to Salesforce on form submission

• Cookie: __cf_bm
  Duration: 1 hour
  Description: This cookie, set by Cloudflare, is used to support Cloudflare Bot Management.

• Cookie: _cfuvid
  Duration: session
  Description: Calendly sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services

• Cookie: cookieyes-consent
  Duration: 1 year
  Description: CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors.

• Cookie: First_Page_Converted
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: Last-Page-Converted
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: banner
  Duration: 3650
  Description: Custom cookie data for news banner at top of the page.

• Cookie: FT_UTM_Campaign
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: Referral_URL
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: FT_UTM_Content
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: FT_UTM_Term
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: FT_UTM_Medium
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

• Cookie: FT_UTM_Source
  Duration: 3650
  Description: Custom cookie data only collected when user explicitly fills out and submits website forms.

Functional

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

• Cookie: li_gc
  Duration: 6 months
  Description: Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.

• Cookie: lidc
  Duration: 1 day 1 minute
  Description: LinkedIn sets the lidc cookie to facilitate data center selection.

• Cookie: yt-remote-device-id
  Duration: Never Expires
  Description: YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.

• Cookie: ytidb::LAST_RESULT_ENTRY_KEY
  Duration: Never Expires
  Description: The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future.

• Cookie: yt-remote-connected-devices
  Duration: Never Expires
  Description: YouTube sets this cookie to store the user's video preferences using embedded YouTube videos.

• Cookie: yt-remote-session-app
  Duration: session
  Description: The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.

• Cookie: yt-remote-cast-installed
  Duration: session
  Description: The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.

• Cookie: yt-remote-session-name
  Duration: session
  Description: The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.

• Cookie: yt-remote-fast-check-period
  Duration: session
  Description: The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.

• Cookie: __Secure-ROLLOUT_TOKEN
  Duration: 6 months
  Description: __Secure-ROLLOUT_TOKEN Is used by YouTube to manage the phased rollout of new features and updates. This cookie helps assign users to specific test groups for experimental features, such as changes to the user interface or video player.

Analytics

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

• Cookie: _gcl_au
  Duration: 3 months
  Description: Google Tag Manager sets the cookie to experiment advertisement efficiency of websites using their services.

• Cookie: ga*
  Duration: 1 year 1 month 4 days 1 minute
  Description: Google Analytics sets this cookie to store and count page views.

• Cookie: _ga
  Duration: 1 year 1 month 4 days 1 minute
  Description: Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.

• Cookie: _fbp
  Duration: 3 months
  Description: Facebook sets this cookie to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising after visiting the website.

Performance

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

• Cookie: test_cookie
  Duration: 16 minutes
  Description: doubleclick.net sets this cookie to determine if the user's browser supports cookies.

• Cookie: bcookie
  Duration: 1 year
  Description: LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.

• Cookie: muc_ads
  Duration: 1 year 1 month 4 days 1 minute
  Description: Twitter sets this cookie to collect user behaviour and interaction data to optimize the website.

• Cookie: personalization_id
  Duration: 1 year 1 month 4 days 1 minute
  Description: Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.

• Cookie: YSC
  Duration: session
  Description: Youtube sets this cookie to track the views of embedded videos on Youtube pages.

• Cookie: VISITOR_INFO1_LIVE
  Duration: 6 months
  Description: YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface.

• Cookie: VISITOR_PRIVACY_METADATA
  Duration: 6 months
  Description: YouTube sets this cookie to store the user's cookie consent state for the current domain.

Uncategorized

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

No cookies to display.

Discussion with InCountry Founder & CEO Peter Yared

InCountry Founder & CEO Peter Yared sat down with staff to discuss the present and future of data residency. Here’s Part II, featuring wider-focused industry-related questions.

-What’s your main prediction for data residency in 2022?

PY: I think there’s going to be more and more data protection in Asia. Asia is high growth markets, and I think we’re going to see more data protection there.

-What industries are most affected by data compliance ?

PY: Financial services and healthcare are the two primary sectors that we see as highly-regulated and most affected. The governments care and the citizens care about how that data is handled.

-Did Covid have any impact on the way healthcare data was prioritized?

PY: Yeah, the thing was, a lot of people still operated by paper or internal systems, and all of a sudden now they have to take it all off. They have to do telehealth, they have to make their systems accessible to people online. A lot of in-person stuff, especially in global markets, shifted online very quickly which meant they had to get online providers and make sure those providers managed data regulations in their respective countries.

-Other than the obvious places, what are some countries to watch?

PY: We have the top ten on our website, and those places are 45% of the world population, 35% of GDP. Again, data regulations are very popular and will only get moreso over time.

-How will the Cloud Act affect hyperscalers?

PY: It has and it hasn’t. It’s happening already, where you have Gaia in Europe trying to build their own cloud infrastructure, in China they have several to choose from, so they aren’t as impacted, but really we see it as impacting more government business. For example, Sweden does not want their visa application process posted in Amazon’s US databases.

-How does the demise of the Privacy Shield affect US-EU data transfers?

PY: It’s become really painful because you have to do standard contract clauses, and that adds a whole layer of expensiveness to the whole thing, and it’s sort of fragmenting the internet. Now there are sites that just don’t operate some places. They’ll just block their website in markets where they don’t want to deal with data regulations.

-Do you think there’ll be a resolution to the situation in the near future?

PY: It doesn’t seem like it, because there’s a massive disconnect. The US just doesn’t have an equivalency, and that could be a real problem in the future. It all boils down to a lack of compromise in government. The process has to be bipartisan, but we can’t get there because there’s such little compromise. There are fifty different breach reporting standards for the states, and things badly need to be distilled down to a unified law, and that’s what some of the businesses want, they would prefer to have one breach reporting standard rather than fifty.

-What is the endgame of data governance?

PY: There’s no endgame to this, so it’s going to continue. What’s going to happen is more and more countries are going to have more and more rules. I’m old, I’ve been operating in the tech industry for a long time; thirty years ago, nothing was regulated, and now everything is regulated. And it’s not going to stop, people are tired of breaches and data being mistreated. Everyone sitting there and saying okay to cookie consents does not make things better. People want their data handled correctly and properly.