Tuesday, October 20, 2026

Monday, October 19, 2026

Privacy Policy

Effective date: October 19, 2026

This policy explains how the LexBrain mobile app handles information when you use it to translate text and study saved cards.

Information stored on your device

LexBrain stores your saved source text, translations, language choices, study settings, and translation cache in app storage on your device. The mobile app does not upload your saved cards or study progress to LexBrain servers, and it does not require a LexBrain account.

You can remove saved cards in the app. Clearing LexBrain's app storage or uninstalling the app removes locally stored cards, settings, and cached translations.

Text sent for translation

When you request a translation, the selected text and language settings needed for that request are sent directly to Google Translate. Do not submit text you are not authorized to share with that service. Google processes requests under its own privacy terms: Google Privacy Policy.

LexBrain does not send saved cards or study progress to Google. A translation already in the on-device cache can be reused without sending another request.

In-app purchases

If you use LexBrain Pro purchase or restore features, Google Play processes the transaction and RevenueCat helps verify purchase entitlements. These services may receive purchase and transaction details, app and device identifiers, and technical or diagnostic information needed to provide and support purchases. LexBrain does not send your card text or study progress to these services.

See the RevenueCat Privacy Policy and Google Privacy Policy for their handling of information.

How information is used

Information is used to provide translations, store and display your cards on your device, remember your settings, and provide or restore purchases. LexBrain does not sell your personal information and does not use it for advertising.

Retention and your choices

Local app data remains on your device until you delete it or clear the app's storage. Google, RevenueCat, and Google Play handle information they receive according to their own policies and retention practices. You can avoid sending text for translation by not using the translation feature. Purchase and payment history is managed through Google Play.

Children

LexBrain is not designed to collect personal information from children. The app does not ask users to provide a name, email address, or account profile.

Changes to this policy

This policy may be updated if the app's data practices change. The effective date above indicates when it was last revised.

Contact

For privacy questions, contact the LexBrain developer at trucbinh@datamerge.xyz.

Friday, November 28, 2025

Configuring CSP for Dynamics 365 Event Registration Forms with hCaptcha on Power Pages

When embedding Dynamics 365 event registration forms that use hCaptcha on Power Pages, you need to configure the Content Security Policy (CSP) correctly to ensure the form loads and functions as expected.

Required CSP Directives

Add the following CSP directives to allow the form and hCaptcha to load without violations:

connect-src

'self' https://content.powerapps.com https://*.microsoft.com https://cxppusa1formui01cdnsa01-endpoint.azureedge.net https://public-apj.mkt.dynamics.com

default-src

'self' https://cxppusa1formui01cdnsa01-endpoint.azureedge.net https://public-apj.mkt.dynamics.com https://*.hcaptcha.com

font-src

'self' https://fonts.googleapis.com https://fonts.gstatic.com https://*.sharepointonline.com http://*.cdn.office.net https://*.microsoft.com https://content.powerapps.com

form-action

'self'

frame-ancestors

'self' https://*.hcaptcha.com

frame-src

'self' https://*.hcaptcha.com

img-src

'self' data: https://content.powerapps.com https://*.microsoft.com https://*.azureedge.net https://public-apj.mkt.dynamics.com

object-src

https://cxppusa1formui01cdnsa01-endpoint.azureedge.net

script-src

'self' 'unsafe-inline' 'unsafe-eval' https://*.microsoft.com https://content.powerapps.com https://cxppusa1formui01cdnsa01-endpoint.azureedge.net https://public-apj.mkt.dynamics.com https://www.gstatic.com https://www.google.com https://*.hcaptcha.com

style-src

'self' 'unsafe-inline' https://fonts.googleapis.com https://*.microsoft.com https://content.powerapps.com

Tip

Always verify these settings in your Power Pages site configuration and test the form to ensure hCaptcha renders properly without CSP violations.

Thursday, May 2, 2024

Permission error when running "Power Platform Backup Environment" in Azure DevOps

When we run action "Power Platform Backup Environment" in Azure Devops with an App Registration account, we get the error "Principal with id '...' for application *** does not have permission to access the path 'https://10.0.1.21:20414/providers/Microsoft.BusinessAppPlatform/environments/.../backups?api-version=2020-08-01' in tenant ...". This means this account is missing the permission to run the backup. However we cannot setup the permission for it in Power Platform Admin Center for Microsoft 365 Admin Center. You can setup this permission by using powershell with the guideline in this link: https://learn.microsoft.com/en-us/power-platform/admin/powershell-create-service-principal#registering-an-admin-management-application


$appId = "CLIENT_ID_FROM_AZURE_APP"

# Login interactively with a tenant administrator for Power Platform
Add-PowerAppsAccount -Endpoint prod -TenantID $tenantId 

# Register a new application, this gives the SPN / client application same permissions as a tenant admin
New-PowerAppManagementApp -ApplicationId $appId

After that, the action can run successfully.

Thursday, March 21, 2024

Error (ESLint) i.CLIEngine is not a constructor in Visual Studio 2019

To correct the ESLint error 'i.CLIEngine is not a constructor' in Visual Studio 2019 with ESLint version 8.57.0, you can follow these steps:

1. Navigate to the following file path and open the file in a text editor: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\ServiceHub\Services\TypeScriptLintingService\TypeScriptLintingService.all.js. It is recommended to create a backup of the original file before proceeding.

2. Locate the function e.prototype.eslint within the file and replace it with the following code:

e.prototype.eslint = function(e) {

return new Promise(async (resolve) => {

try {

var config = JSON.parse(e);

var ESLintModule = this.dynamicRequire(config.linterPath + n.sep + "node_modules" + n.sep + "eslint");

var results = [];

if (ESLintModule.ESLint) {

var options = {

cwd: config.projectRoot,

resolvePluginsRelativeTo: config.linterPath

};

var eslintInstance = new ESLintModule.ESLint(options);

results = await eslintInstance.lintText(config.fileContents, { filePath: config.fileName });

} else {

var optionsLegacy = {

cwd: config.projectRoot,

ignorePattern: ["wwwroot/lib/**", "**/node_modules/**", "**/bower_components/**", "**/jspm_packages/**"],

resolvePluginsRelativeTo: config.linterPath

};

if (config.parserPath) {

optionsLegacy.parser = config.parserPath;

}

results = new ESLintModule.CLIEngine(optionsLegacy).executeOnText(config.fileContents, config.fileName).results;

}

var report = results[0];

if (report) {

report.messages.forEach(this.addRuleIdToParseError);

var validMessages = report.messages.filter((message) => message.ruleId != null);

validMessages.forEach(this.addLocationInfoFromSourceCode);

resolve({ lintMessages: validMessages });

} else {

resolve({});

}

} catch (error) {

resolve({ errorMessage: error.message });

}

});

}

3. After making the changes, save the file and restart Visual Studio to apply the update.

Saturday, July 15, 2023

Power Automate Desktop error: The request content is not valid and could not be deserialized: 'Unexpected character encountered while parsing value: %. Path '', line 0, position 0.'

When you use "Invoke web service" action with URL that has special character "%", you can escape this character with "%%". But when you run, this error happens.

I got this error and I tried many methods. Only one method helped me to solve this. I turned the option "Encode request body" to Off in the Advanced setting of "Invoke web service" action.

Sunday, September 12, 2021

Tips for setting lookup value of using Dynamics 365 Web API

Working with Dynamics 365 CRM, when you set a value for lookup field, maybe you will get the error “Invalid property ‘your_field' was found in entity ‘the_entity’. ---> Microsoft.OData.ODataException: Does not support untyped value in non-open type” or error “An undeclared property ‘your_field' which only has property annotations in the payload but no property value was found in the payload. In OData, only declared navigation properties and declared named streams can be represented as properties without values.”. This means you are not setting this field incorrectly.

The first situation is you are not using the field schema name.

The second situation is you are not setting it correctly. There are several situations with the lookup field to do this:

Non-activity entity/table, single lookup field (lookup to only one table)

entity[<your_schema_field_name>@odata.bind] = “/<entity_logical_name in plural>(<entity_id>)”

For example: A custom field new_account lookups to account table

entity[new_accountid@odatabind] = “/accounts(b2ce603e-5bb9-eb11-8236-0022481736ba)”

Activity entity/table, single lookup field

entity[<your_schema_field_name>_<ActivityName>@odata.bind] = “/<entity_logical_name in plural>(<entity_id>)”

For example:

entity[new_accountid_PhoneCall@odatabind] = “/accounts(b2ce603e-5bb9-eb11-8236-0022481736ba)”

entity[new_accountid_Task@odatabind] = “/accounts(b2ce603e-5bb9-eb11-8236-0022481736ba)"

For regarding field

entity[<your_schema_field_name>_<entity_lookup_logical_name>@odata.bind] = “/<entity_logical_name in plural>(<entity_id>)”