No, I mean: C:\Users\AppData\Roaming\Your Co. Name\ (File::userApplicationDataDirectory)
When you’re referring to “data”… are you talking about sample content or resources for the plugin? You need to consider them as separate items if you are going to have additional content available for your plugin. If you only have a fixed set of data then you can put that in your AppData\Roaming path with the rest of the plugin’s resources and simply use File::userApplicationDataDirectory to get the path.
If you’re going to have expandable content then you need a mechanism to have the installer let your plugin know where the data was installed to… and it could be in multiple different locations… and for that I use a database to keep track of all the content… It also adds much more complexity to the whole plugin since you need to handle reloading presets from different users where one may not have the same content installed as another and you need to be able to resolve a saved sample to it’s file location on any system.
I personally don’t use BinaryData for my resources so that our graphic artist can easily change the resources without needing me to recompile.
Oh, and if your content is > 8GB you’ll need a custom installer for MacOS.