Protecting data collected for track events created in code blocks
Hello,
Our team is attempting to embed track events within code blocks to capture some of our user data. However, we also know that custom code blocks are not protected under the same policies and practices as the other blocks.
I would love to know what the policies or preventions are in place to prevent malicious code or attacks from exploiting a code block.
For reference, we are using this article as a template for our track event embedded in a guide.
0
コメント
could you add some sort of hash? It makes me think of SRI work a bit, but I'm not 100% familiar with best ways to lock it down.
サインインしてコメントを残してください。