# Anki Encrypt \[support thread\]

**URL:** <https://forums.ankiweb.net/t/anki-encrypt-support-thread/62327>\
**Category:** Add-ons\
**Created:** [June 7, 2025, 1:14pm UTC](https://forums.ankiweb.net/t/anki-encrypt-support-thread/62327 "2025-06-07T13:14:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Eltaurus](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.ankiweb.net/eltaurus/32/10287_2.png) [@Eltaurus](https://forums.ankiweb.net/u/Eltaurus)\
**Post date:** [June 8, 2025, 10:14am UTC](https://forums.ankiweb.net/t/anki-encrypt-support-thread/62327/3 "2025-06-08T10:14:49Z")

</div>

> [@dae](#):
>
> I think you’ve documented the risks fairly well

I’ve also added a warning regarding cards’ JS, following [your comment here](https://forums.ankiweb.net/t/support-password-memorization/17725/11). Can you comment on whether returning to the Deck screen is enough to purge unwarranted JS from the webview? It seems to work this way on Desktop, according to my tests, and on AnkiDroid, it shouldn’t be the issue in the first place, as the current reviewer resets the webview on each card flip, afaik. However, I don’t know anything about how this is treated in Anki Mobile.

* * *

> [@dae](#):
>
> the majority of users would be better served putting their passwords in a password manager instead

That might be, but as [described in this comment](https://forums.ankiweb.net/t/support-password-memorization/17725/12), a password manager by itself is not a perfect solution either. There are also cases when retrieving the information quickly is important, and nothing can beat having it directly in your memory.

---

_[View the full topic](https://forums.ankiweb.net/t/anki-encrypt-support-thread/62327)._