paranoia-file-text-encryption 16.1.43 (new cask)

[ParanoiaWorks]

---

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes, including zap stanza paths.

---

[bevanjkay]

Please make sure you fill out the PR template.

[ParanoiaWorks]

local brew audit fails due to broken Xcode on this machine; install and uninstall verified working

[krehel]

Please address the failures.

[bevanjkay]

Please try to add a zap stanza. The linked documentation provides some recommended methods to create it.

[ParanoiaWorks]

Added zap trash: with the app's user config files (~/.ssefe.conf and ~/.ssepte.conf).

A bit of context on why these are the only paths listed: the application is a Java Swing app (packaged with jpackage), and it intentionally does not use the standard macOS preference locations like ~/Library/Preferences/.plist or ~/Library/Application Support/. Instead, it stores its two module configurations (File Encryptor and Text Encryptor) as plain dotfiles directly in the user's home directory — this keeps configuration portable across platforms (the same codebase runs on Windows and Linux, where those macOS-specific paths don't exist).