This section collects answers to the most common "How-to" questions about the InCountry Platform.
How do I set up an account in InCountry Platform?
- Open InCountry Platform.
- Sign up for a new account.
- Fill out the required information.
- Click Submit.
- Confirm your account.
- Log in to your account on InCountry Portal.
What should I use to store data in-country in a monolithic web app?
If you have a monolithic web app that manages regulated data, you can take advantage of the HTML Proxy component. It can handle the regulated data within the HTML output from the monolithic web app.
Please contact InCountry for a free consultation and details on this.
To use InCountry SDK, you need to connect SDK as a library into your application project. It will provide client-side data encryption for regulated data.
If you do not want to do this, you can perform HTTP requests and use the server-side encryption within InCountry REST API. It allows you to perform the same operations as InCountry SDK provides, but do this on the server-side of your application without full integration into its codebase.
InCountry REST API also provides the native integration with third-party SaaS solutions, like Salesforce and ServiceNow. It allows you to perform requests to InCountry REST API from your web-browser. You need to place all the request authorization details within the token.
For data localization in SaaS solutions, use InCountry REST API, as you will not be able to integrate InCountry SDK into it.
How do I process data in-country?
InCountry Serverless provides a capability to perform additional data manipulations on regulated data besides its storing in InCountry Platform. It lets you execute serverless functions in the origin country without transferring data for validation or aggregation to the country where the application server resides.
For implementing such complex scenarios, you can take advantage of Serverless. This component of the InCountry Platform lets you manage and execute serverless scripts against protected data in the data originating country without a necessity to leave it. This is extremely helpful when your application server is located in another country and you cannot perform validation or aggregation of protected data without leaving the originating country. As in this case, you will violate the compliance and data protection laws and regulations.
For the details on Serverless, please see the product documentation.
How do I use my own keys for encryption of protected data?
You can take advantage of our BYOK option (Bring Your Own Key) and use your own encryption keys for securing protected data that you store in the InCountry Platform. You can take full control over the encryption keys and get the required flexibility for key rotation. This way you can preserve the highest level of data security of your data in the InCountry Platform.
For the details on BYOK, please see our documentation.
How do I retrieve data in-country into the application frontend?
The way to fetch this regulated data for showing in the application frontend mainly depends on the way you write data to InCountry Platform. We strongly recommend you to use the same InCountry product for writing and reading data in-country. Integration of different InCountry products will require additional time and effort from youк side, so in most cases, they will be extensive. If you are not sure about the InCountry product to choose for a specific task of yours, please contact InCountry to get a free consultation.
How do I aggregate data across countries?
InCountry Platform provides the three data regulation models which you can use for handling regulated data. For the specifics of each data regulation model, please see the Data regulation models section.
Depending on the used data regulation model, you can either aggregate data across multiple countries or you will not be able to do this because of local country regulations. Before proceeding to implementation of a solution for handling regulated data from multiple countries, please request a consultation from the InCountry team
With InCountry SDK you can perform data read requests into multiple countries and further aggregate the received data the way you want. This can be done only for the replication and restriction of data models. In the case of the redaction model, InCountry SDK can pull data only if your backend runs in the origin country, otherwise, you will violate the compliance requirements.
You can also use InCountry REST API for this with the same specifics of data regulation models. InCountry Border will not handle this scenario. Here you should consider that both InCountry products can output up to 100 records at once.
How do I handle production data with InCountry?
When you need to move the production data to InCountry Platform, you can the bulk data import operations in InCountry REST API or in InCountry SDK. They allow you to write data batches into InCountry Platform.
To map the records' regulated data stored in InCountry Platform to the record data in your application database, use the current record identifier in your application database as a profile key in InCountry Platform.
How do I add data residency to my Salesforce?
You can use the InCountry for Salesforce solution which supports the three data regulation models for handling regulated data in Salesforce and redacting this data if viewing it outside the origin country.
For the details on this solution, please see the InCountry for Salesforce - Implementation Guide.
How do I add PCI-DSS compliance with data residency into my application?
You can use the Payment Gateway solution which can be integrated into your web application or web-based mobile application for iOS or Android.
It provides the web application form for entering the payment details. This form integrates with InCountry Platform, so your application does not directly process the payment information itself, while InCountry Platform handles this and routes this information to the service provider depending on the country to which credit or debit card attributes to.
How to connect the Payment Gateway module into your application, please see this documentation.