Data boundary
What this package touches, what it does not, and who can delete what.
A — What the package introduces
Nothing that reaches outward.
The package is a set of skills and a local compiler step. It introduces no I.O.V backend, no API calls, no external logging service, no cookies and no marketing or advertising trackers.
It opens no network connection of its own. Any network behaviour you observe comes from your host environment, not from this package.
B — Where your inputs live
Inside your host environment.
The mandate fields you supply, the conversation around them and the four outputs stay within the host environment you already use. That environment's own settings and retention behaviour apply to them.
I.O.V has no visibility into that environment and cannot see, retrieve or delete what it holds.
C — Files you create
Yours to keep or remove.
The JSON draft, permission matrix, report and test specifications are files created in your environment. You control them.
To remove them, use your host's own deletion controls. This package provides no deletion mechanism of its own, and no statement here should be read as a retention guarantee or as a claim that any setting results in zero retention.
D — What I.O.V receives
No workflow data.
I.O.V does not receive your workflow data, mandate values, provenance notes or generated artifacts through this package.
If you choose to email support, whatever you include in that email reaches I.O.V — and only that.
E — Support contact
Support email is optional. If you use it, that correspondence is handled under the existing I.O.V privacy statement: hello@iov.agency.