The default "internal" access mode is similar to "protected". It's less granular, but that's to be expected since Swift does not (yet?) allow partitioning of a single app or library into different namespaces.
"protected" would allow you to modify a member of a class when you inherit from it, whether it is in the same module or not.
using "internal" or "public" with a comment saying "please only use this when you subclass" the class is not as neat and tidy.