That's correct. Also, in the event a token is inadvertently activated early - and a member wants to de-activate it - we can do that on the support team after a recent backend admin systems upgrade. So if that happens, let us know and it's no trouble to fix it.
Thanks to a sharp-eyed network member, we recently fixed a bug where folks checking token status with the cryptostorm.nu 'tokenizer'
for tokens that had not yet been activated
sometimes saw them suddenly "go active" as a result of the check. That's now resolved, and a different script is called to check tokens, versus validating network sessions.