Some supplementary information about how to make this kind of "embodied data" act a little more like global variables:
You can set up a storage card for all of your data-holding widgets. One that (probably) your player will never navigate to (there are ways to make it harder to reach, as well, if your users are meant to navigate with arrow keys). It could have checkboxes for true/false, fields for text, grids for spreadsheet type data, etc.
And then you can set a sort of shortcut variable in the Deck level script (Accessible with with File > Properties > [Script...] Or if you're already in a script editor you can use File > Go to Deck to move to the other script directly.) which is a quicker path to the widgets on that specific card.
Here I'm setting a shortcut to the widgets on a hypothetical card called myvars (using Millie's example):
vars:myvars.widgets
And then be able to use that shortcut variable to streamline your other scripts when you're referring to your other stored data, like:
vars.field1.value
instead of having to write the longer address every time you want to refer to your stored information:
myvars.widgets.field1.value
It's often a little easier this way.
Or you can use this kind of shortcut to go directly to a single widget, if it's one you're updating and referencing often:
thatfield: myvars.widgets.field1
I hope this helps.