[PR-22981] [Documentation] Clarify params encryption logic (#342)

Co-authored-by: Bohdan Zhuravel <[email protected]>

source/advanced_features/params_encryption.rst

@@ -15,7 +15,7 @@ So, instead of sending params in plain text, you can send them encrypted.
 Site public encryption key
 --------------------------
 
-To get your unique site public encryption key, go to **All Site Settings → Integrations → API integration → Public encryption key for email addresses**.
+To get your unique site public encryption key, go to **All Site Settings → Integrations → JS integration → Public encryption key**.
 
 Passing email as a GET parameter to Standalone Campaign
 -------------------------------------------------------
@@ -160,6 +160,11 @@ Node.js Example
 Front-end Part
 --------------
 
+.. important::
+   Do not use params encryption for :ref:`Talkable backend API <api_v2/origins>`.
+
+   Params encryption is only for JS integration.
+
 Please modify the front-end using this pseudo code example:
 
 .. code-block:: html