OpengSpaceOpen workspaceWorkflow boundaries
A Shortcut can start an action, and connected storage can hold material you explicitly authorize. Neither one alone proves that saved material can be understood or recalled as an AI memory.
OpengSpace provides a published Apple Shortcut installation link. Apple still requires you to review the Shortcut, approve permissions and choose any system trigger yourself. Opening the link is not proof that a save completed.
When you explicitly connect Alibaba Cloud Drive, Baidu Netdisk or GitHub, OpengSpace can access the files or directories you choose to share for the feature you request. The available scope is determined by the authorization shown during setup.
The current privacy policy says OCR and AI features may send the input and related content needed for a request to Alibaba Cloud for model inference. Connecting storage does not mean every stored item is automatically sent for AI processing.
A completed save, retained source and a later retrieval are separate checkpoints. This page does not claim that installing a Shortcut or connecting a drive automatically creates searchable memory, source-grounded answers or automatic organization.
Review the published Shortcut, connect only the storage scope you intend to use, save one non-sensitive item and wait for an explicit success result. Then confirm the material is available before relying on the workflow.
Use Apple Shortcuts when the main problem is starting an action from an Apple device. Use connected storage when the main requirement is an authorized destination. Evaluate AI-memory behavior only from a completed product workflow, not from the presence of either component.
Frequently asked questions
Not necessarily. A Shortcut runs the actions it contains. Review the published Shortcut and the destination and permissions shown during setup before adding it.
No such automatic behavior is claimed here. The privacy policy describes AI processing for features you request and says the required input may be sent to the named model provider.
No. Saving, retaining the source and retrieving it later are different checkpoints and should be tested separately.