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.

Become PCI DSS Compliant with Payment Vault

Payment Vault enables payment processing integration, data distribution, and the localization of payment data for companies. It secures retention and facilitates PCI compliance with minimal to no changes.

Expand your business into new markets and stay PCI compliant

Data compliance with the InCountry Payment Vault

Features

• Compliant with the PCI DSS global industry standard
• Meets local requirements for payment data storage in country of origin
• Seamless integration into your product or service sales pipelines
• Versatile security of payment card data

Benefits

• Eliminate borders for business expansion
• Minimize investments into PCI compliance
• No changes to your infrastructure or business operation
• Secure customer data against any potential threats
• Reduce local compliance risk

How it Works

1. Create an integration with Payment Vault on the InCountry Portal.
2. Payment Vault intercepts all payment requests through the pre-defined endpoint.
3. Payment Vault encrypts and saves the payment card data to the InCountry platform.
4. Payment card data is passed to the payment provider for processing.
5. Tokenized card data is provided to your application backend.

Frequently asked questions

What payment providers are supported?

Currently, Payment Vault only supports Stripe, but we are working hard to expand the list of supported payment providers. Please let us know what payment provider and countries you need by dropping an email to us.

Why do I need to keep payment card data in its country of origin?

Some local regulations require the financial information of the country’s citizens to stay within the country of origin. Such requirements already exist in China, Russia, India, and Indonesia, and the list is sure to expand in the future, as several countries have corresponding legislation pending.

How does the InCountry platform secure payment card data while storing?

Payment Vault encrypts the string containing the cardholder’s name, card number, and expiry date with the AES-256 algorithm. This encrypted data is further stored on the InCountry platform in the country of origin.

Why do you tokenize data when passing it to my application?

Tokenization is applied to the payment card data to preserve the capability to save the customer’s payment card data in your database. This tokenized data can be further used to identify the required payment card when performing recurring payments.

Does the InCountry platform store CVC/CVV codes?

No, CVC/CVV codes are not stored on the InCountry platform.

How do I modify my current sales pipeline?

In general, you just need to create a Payment Vault integration and call our payment form when your customers initiate a payment transaction.

Is your solution PCI DSS compliant?

Yes, yes, and yes. Payment Vault has proven itself to be PCI DSS compliant time and time again.