In short, if you preserve your data well, you might end up having to hand-type it in (or at least go through it with your own eyeball character by character to fix scanning errors) to restore the unencrypted version. Assuming you can do that and don't mind doing that then this method could possibly work.
If you're talking about several kB, that's going to be very annoying to do. At least add partial checksums per line or multiple lines.
Say this is your data (from
random.org:
oKp30Otodg07mSc83Nxw
3EdM4CFypmOfSupspfcd
OO9LL0I4QEc4dx5HhdlQ
lXSDsvm17tzQNhlEwYH0
mJPcDPPE2pQaD4Q9oaBu
pFhODlJNXz8V8vAunpzn
xeRTGwg4c5jYCzLqDNJL
4eIzVtQGEUtBJzCyhGtx
q4Vw92cwd0PqsLj9sGff
Ip6y9986cNfkEg36OYs4
A simple
md5sum per line would be:
43dbfbbc3fe9eecccc313b5ed4707bec -
7d2f3295028a1dfb41df0c9e696d9d9b -
b75dbc5c69502db35d76028643314996 -
24d8f8420aaf27e25d93787cd434a7b9 -
5833cf59445a9657c2da7088ae7a4119 -
5952f16a3f33d8c87e5846605cc95cac -
6989ed58a32c2622dda4418eab730c65 -
844a3c31527f88588c3dd7f22ccdf883 -
c5dca4c2ee7ac2d7c0c1874d267a8b7a -
32b5dc97587bd5e7e34f58f55f90353d -
This makes it much faster to check where you have a reading error.