If this is going to make it in to the existing code (and stay), however polished it will be by the next release, I'd like to see it clearly marked as experimental, until it is available as a complete and coherent framework for encrypting table contents.
So, I suggest moving the relevant classes into an "experimental" sub-package, and minimizing references to them in other code. I looked for a built-in "@Experimental" annotation, but couldn't find one, so we could create one for this sort of thing (but I still prefer the sub-package until it is no longer experimental). I do not think that they should be marked as "@Deprecated" because that implies a completely different point in the life cycle of the code (in fact, it implies the opposite end of that life cycle).
That said, what exactly are the next actions, and the timeline for polishing this feature? From the previous comment, I gather "tests", and "tidiness" (which I interpret to mean QA refactorings, but not functional changes that incorporate critical feedback). Are there more anticipated actions that I've overlooked?