Return-Path: Delivered-To: alvarochf@traceseis.com Received: from cs510.bluehost.com by cs510.bluehost.com with LMTP id gFdoKSCi42jQ/QQAWiBQxw (envelope-from ) for ; Mon, 06 Oct 2025 05:04:00 -0600 Return-path: Envelope-to: alvarochf@traceseis.com Delivery-date: Mon, 06 Oct 2025 05:04:00 -0600 Received: from mta-174-84-123.intercom.com.sparkpostmail.com ([192.174.84.123]:23816) by cs510.bluehost.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1v5j0a-00000001Xba-22gB for alvarochf@traceseis.com; Mon, 06 Oct 2025 05:04:00 -0600 X-MSFBL: goVrO0rcROzs3StaFeePwGZyTyI32aHbjG3Zf4d2eLQ=|eyJyIjoiYWx2YXJvY2h mQHRyYWNlc2Vpcy5jb20iLCJtZXNzYWdlX2lkIjoiNjhlMTE0YTJlMzY4NmQyNTE 2OTIiLCJjdXN0b21lcl9pZCI6IjEiLCJzdWJhY2NvdW50X2lkIjoiNDg5NzMiLCJ 0ZW5hbnRfaWQiOiJpbnRlcmNvbSJ9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cryptolens.io; s=intercom; t=1759748628; i=@cryptolens.io; bh=mfMNmNMHzPdqwLIJXJ5pH1bzfLujaXr6ufVzIdTASgI=; h=To:Content-Type:List-Unsubscribe-Post:Message-ID:Subject:From: List-Unsubscribe:Date:From:To:Cc:Subject; b=H+DaYPw5Q6YPSjrIh6cbGuyQCsn2kJ12k+Nu4G3AF6SjPSLRLseadOI52yXv5cElp K2MsaPtP3vzWcRJiYtVycpCHQJTY+P3dNfS1327cg6bLWMhOdLKBKqv+F6O0l7MMyC V1Nn0GgRZSQOw8m5fNvwJfRes1VxlpuLz1ahzod4= Received: from [10.90.19.152] ([10.90.19.152]) by i-0a8c43c2a000a19b7.mta2vrest.sd.prd.sparkpost (ecelerity 5.1.0.74619 r(msys-ecelerity:tags/5.1.0.13)) with REST id 29/69-03161-412A3E86; Mon, 06 Oct 2025 11:03:48 +0000 To: alvarochf@traceseis.com Content-Type: multipart/alternative; boundary="_----Z/3v6CccfhyFeSojOelHYw===_78/69-03161-412A3E86" MIME-Version: 1.0 X-Mailgun-Variables: {"app_id":"uyf5hx0o","conversation_id":"215471164879135","user_id":"68c6995456bc4a9d3338e95c","intercom_localized_email_content_id":"43748720"} X-Auto-Response-Suppress: OOF, AutoReply Reply-To: Artem from Cryptolens X-Intercom-App-Id: uyf5hx0o X-Intercom-Bin: 200 List-Unsubscribe-Post: List-Unsubscribe=One-Click Message-ID: <731d3b5e-7c36045e-1759748627-215471164879135-1000832@outbound.intercom.cryptolens.io> X-Report-Abuse: Please report spam or abuse to abuse@intercom.io Subject: Tips and best practices for using Cryptolens From: "Artem from Cryptolens" List-Unsubscribe: , Date: Mon, 06 Oct 2025 11:03:47 +0000 --_----Z/3v6CccfhyFeSojOelHYw===_78/69-03161-412A3E86 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Tips and best practices for using Cryptolens =0A Hi there, =0A By now, you'= ve learned about Cryptolens and should be ready to explore some best practi= ces. Using our libraries effectively can streamline your work and enhance s= ecurity. =0A Here are a few tips: =0A - When performing key verification, i= t's a good idea to save the license to a file. That way, if there is a netw= ork problem or the customer is offline, you can fall back on the license fi= le instead. It is possible to limit how long a license file can be used bef= ore it needs to be updated, which we covered in this article. =0A- Make sur= e that the access token used in your client application is scope restricted= . In most cases, it should have only the Activate permission set. =0A- If y= ou are developing an add-in or mobile application, we recommend that you re= view the following page to see if there are any issues you need to consider= . =0A- Make sure that the license key is not hard-coded. If you need to off= er a trial to all users, it's better to use this approach. =0A For detailed= instructions and other pro tips, visit our documentation page. =0A As alwa= ys, for direct support, reach out to us at support@cryptolens.io or via the= chat box. =0A If you are ready to upgrade or just want to learn more about= what is included in our plans, check out our pricing page. =0A Artem =0A S= ome useful resources =0A Developer docs, FAQ, GitHub, Pricing, Book a meeti= ng --_----Z/3v6CccfhyFeSojOelHYw===_78/69-03161-412A3E86 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="UTF-8" =0A=0A=0A=0A Tips and best pract= ices for using Cryptolens=0A =0A = =0A =0A =0A =0A =0A = =0A =0A=0A =0A=0A =0A=0A=0A =0A=0A=0D=0A
=0D=0A=0A =0A =0A=0A
=0A =0A =0A=0A = =0A =0A = =0A
=0A
=0A =0A = =0A
=0A=0A=0A<= /table>=0A
=0A
=0A
=0A

Tips and best practices for us= ing Cryptolens

=0A

Hi there,=0A

By now, you've learned about C= ryptolens and should be ready to explore some best practices. Using our lib= raries effectively can streamline your work and enhance security.

=0A

Here are a few tips:

=0A
    = =0A
  • When performing key verification, it's a good idea to save the licen= se to a file. That way, if there is a network problem or the customer is of= fline, you can fall back on the license file instead. It is possible to lim= it how long a license file can be used before it needs to be updated, which= we covered in this article.
    • =0A
  • Make sure that the access toke= n used in your client application is scope restricted. In most cases, i= t should have only the Activate permission set.
    • =0A
  • If you are devel= oping an add-in or mobile application, we recommend that you review the followi= ng page to see if there are any issues you need to consider.
    • =0AMake sure that the license key is not hard-coded. If you need to offer a t= rial to all users, it's better to use this approach.=0A
=0A

For detailed instructions and other pro tips,= visit our documentation page.

=0A

As always, for direct support, reach o= ut to us at support@= cryptolens.io or via the chat box.

=0A

If you are ready to upgrade or just want to learn more about wha= t is included in our plans, check out our pricing= page.

=0A

Artem

=0A

Some useful resources

=0A

Develop= er docs, FAQ, GitHub, Pricing, Book a meeting

=0A
=0A=0A =0A =0A =0A=0A
=0A=0A
=0A =0A =0A =0A =0A = =0A =0A =0A =0A
=0A 3D"intercomavatar" =0A =0A Artem from Cryptolens=0A
=0A 		=0A =0A =0A=0A =0A=0A =0A=0A
=0A Unsubscribe from our emails=0A =0A
=0A
=0A=0A=0A=0A
Powered by Intercom
=0A
= =0A
=0A
=0A

=0A

=0A=0A=0A3D"intercom"=0A= =0D=0A3D""=0D=0A=0A --_----Z/3v6CccfhyFeSojOelHYw===_78/69-03161-412A3E86--