Dara Hayes I had a quick look at the cache persistor class you linked and looks good to me. Would it make sense (instead of exposing the cache to the user) to create a destroyClient() function or something similar in the sdk which can do this instead. We can then just say "on logout or whatever we recommend you call destroyClient()" as this seems a bit neater and then if there is anything else we need to clean up in future we can do it here.

ps destroyClient isn't a great name but you get me.