What MySafe claims now, and what it does not claim yet.

MySafe is designed around organization-scoped document access. A document uploaded into one organization workspace is not visible to other organizations.

Access is not based on a shared generic folder. Read access is granted to named users within the organization. A controlled link is the exception: it needs an approved request, and anyone who has the link can open it until it expires or is revoked.

The organization that uploads and manages the document remains responsible for deciding who should have access, why access is needed, and when access should be reviewed or removed. Depending on the pilot setup, that decision sits with the workspace owner or an approved organization-side decision-maker. MySafe’s role is to support controlled handling: clear document state, version history, access boundaries, and audit visibility.

External access is not assumed by default. Where external access is required for a pilot workflow, it should be explicitly scoped before use: who receives access, which document or workflow is involved, why access is needed, and when that access should end or be reviewed.

This supports data protection principles such as controlled access, security, accountability, and storage limitation without treating MySafe as a substitute for the organization’s own legal or compliance obligations.