# 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.

## 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**: vuid  
  **Duration**: 1 year 1 month 4 days  
  **Description**: These cookies are used by the Vimeo video player on homepage.

- **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**: 1 year 1 month 4 days  
  **Description**: Custom cookie data only collected when user explicitly fills out and submits website forms.

- **Cookie**: cookieyes-*  
  **Duration**: 1 year  
  **Description**: CookieYes sets this cookie for consent solution management.

- **Cookie**: utm_source  
  **Duration**: Never Expires  
  **Description**: This cookie is used to record from where the visitor came to the website originally. This information is used by the website operator to know the efficiency of their marketing.

## 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  
  **Description**: LinkedIn sets the lidc cookie to facilitate data center selection.

- **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**: __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  
  **Description**: Google Analytics sets this cookie to store and count page views.

- **Cookie**: _ga  
  **Duration**: 1 year 1 month 4 days  
  **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 recognize 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**: 15 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  
  **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  
  **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.

- **Cookie**: _twpid  
  **Duration**: 1 year 24 days  
  **Description**: This is a tracking and marketing cookie set by Twitter/X Corp. (static.ads-twitter.com). It is primarily used to identify website visitors, track ad conversions, and optimize the relevance of advertisements you see across different platforms.

- **Cookie**: __Secure-YNID  
  **Duration**: 6 months  
  **Description**: YouTube cookie used to protect user security and prevent fraud, especially during the login process.

- **Cookie**: __Secure-YEC  
  **Duration**: past  
  **Description**: Description is currently not available.

- **Cookie**: _twsid  
  **Duration**: 1 year 24 days  
  **Description**: This cookie is set by the X (formerly Twitter) pixel script (uwt.js). It assigns a unique identifier to the visitor to track website usage, attribute conversions from X ad campaigns, and deliver targeted advertisements to the user on X.

- **Cookie**: _twclid  
  **Duration**: 1 year, 24 days  
  **Description**: This cookie is set when a user arrives at the website by clicking an advertisement or link on X (formerly Twitter). It stores a unique click identifier (_twclid) to track campaign attribution, measure ad effectiveness, and accurately log conversion events back to the X Ads platform.

## Uncategorized

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

No cookies to display.

# Salesforce developer overview

InCountry’s 2GP Managed Package for Salesforce makes it possible to use Salesforce or Hyperforce instances from multiple regulated locations. Multinational companies can continue to run a single global Salesforce org or a few regional orgs. The package handles data residency requirements for each configured country.

## InCountry Managed Package for Salesforce

## InCountry offers the following components for Salesforce

### Web Services

- Data Residency Application
- JavaScript SDK
- Apex SDK
- Salesforce Cross Border
- InCountry UI API

### Data Residency Application for Sales, Service and Experience Clouds

The application provides Sales, Service and Experience Cloud Lightning Web Components that look & feel as the core Salesforce components. For example, for Sales Cloud Customers can use Detail View, Highlights Panel, Related Lists, List Views, Reports and other components. Every component intercepts User’s request, verifies their permission and splits the data flow: non-regulated data and metadata are transmitted from Salesforce Backend, regulated data is transmitted from InCountry PoP via a browser request (Javascript Fetch API). The client-side mutual TLS is established using JWT that are generated for every action on a page. Our Product team ensures that all custom LWCs are updated regularly and the connection between LWC and InCountry PoP (point of presence) is secured.

### JavaScript SDK

Many Salesforce Customers have their own custom LWCs or Aura components. InCountry’s JavaScript SDKs works with both frameworks, and it helps to satisfy Data Residency requirements without implementing custom integration with InCountry PoP. Customers can just import InCountry ES modules into their code and start performing operations with the Point of Presence: CRUD, Search, Serverless, etc. The SDK handles access control checks, JWT authorisation and authentication and client-side connection to InCountry PoP behind the scenes. It is especially useful for customers who are running Redacted model, where regulated data cannot be transferred to Salesforce server.

### Apex SDK

It provides an Apex interface to InCountry Point of Presence operations, such as CRUD, Search, Add Attachment, Hash, etc. The SDK is synchronous, so any Customer who is running their own custom Apex, can call Apex SDK actions from Triggers, Batch Jobs, Queueable Jobs, Future Jobs, Anonymous Apex, Controllers, Invocable Actions and any other Apex code. Unlike JavaScript SDK, Apex SDK establishes a server-side connection from Salesforce Backend to InCountry Point of Presence. The connection is secured by the OAuth2 flow.

### Salesforce Cross Border

This solution can help customers who are running several Salesforce or Hyperforce instances to replicate and anonymize regulated data in near-real time. Let’s say, a customer has a local Hyperforce instance in China and a global Salesforce org in US, and they want to replicate some portion of Chinese records from China to US for global reporting. The data must be anonymized due to regulation restrictions, and the connection must be secure. Salesforce Cross Border application uses InCountry Proxy to perform near-real-time migration. It supports retries, guaranteed order of events, logging and monitoring.

### InCountry UI API

This API works similarly to Salesforce UI API, and it provides high-level access to InCountry CRUD operations. Customers, who are running their own Lightning Web Components, can use the API without worrying about non-regulated and regulated records. The API automatically splits data flow based on the package configuration. All regulated records and fields are stored to the InCountry PoP, all non-regulated records and fields are stored to the Salesforce database.
