To keep the state in Presenter or Interactor for click events?

I'd prefer to keep things stateless if possible
A Stream is perfect for that but too much work
So keeping the state for click events
But can't make up my mind between the Interactor and the Presenter
Any recommendations?

A typical Interactor:

override fun didBecomeActive() {
        super.didBecomeActive()
        getDataAsync()
               .subscribe { theData ->
                       // to keep theData as state here or not?
                       presenter.present(theData) // or inside the Presenter? 🤔 
               }
}

// upon user click, we need to theData again
fun onClick(theData: TheDataType) {
}

Review the Interactor entry points shown in the issue, including didBecomeActive(), getDataAsync(), and onClick(), alongside the Presenter call. Compare the two proposed state locations and the stateless Stream alternative; the issue is complete when the project has a decided, documented approach for handling click-event state.