How it starts
We first learn about your problem. Then we agree with you on the scenario, the tasks and what a useful result would look like.
Pilot path
MySafe should be entered through a narrow operational path, not through vague platform expectations. The current objective is to validate a real document workflow end-to-end.
We invite organisations to explore one document process with us through a guided pilot with an agreed scope.
We first learn about your problem. Then we agree with you on the scenario, the tasks and what a useful result would look like.
One organisation, one agreed process, 2–5 active participants and at most 10 accounts, and up to 50 synthetic or public test documents. No archive migration and no custom integrations. This is the agreed scope of the pilot, not a limit enforced by the product. New tasks are discussed separately.
Agreed individually: the length of the pilot, the pace of work and when we review the results. There is no fixed 14- or 30-day period.
Taking part in the pilot is free (Founding Access). No card is required, and there is no automatic charge or automatic move to a paid plan. Any paid continuation or paid service needs a separate written agreement once a matching offer is ready. We do not promise discounts or special launch terms. The pilot does not include open-ended free support or every requested change.
We use findings about your organisation publicly, including anonymised findings, only with your separate written consent.
Pilots use synthetic or public documents. A client's real documents are used only after MySafe's readiness review for real data is complete and MySafe has confirmed in writing for that pilot. That review includes backup and restore, data deletion, monitoring, account protection, an independent security review, incident procedures, and legal review of the privacy notice and pilot terms. It is not complete yet, and we do not give a date for it. The product does not block uploads, so please do not upload real documents until you have that written confirmation.
We review it and, if suitable, send an onboarding invitation. Public self-registration is not available.
After invitation and sign-in, MySafe is organization-scoped. Document work starts only after the organization boundary exists.
After organization setup, MySafe takes you into the Documents workspace and shows the first-document empty state.
Use the first-document upload action with a synthetic or public document. The initial upload creates a structured document record instead of an untracked loose file.
After upload, MySafe takes you straight to the document details page so you can review state, versions, and next actions.
From document details, continue with version uploads, access and review actions, lifecycle transitions, and workspace guidance. The Audit page is informational and read-only.
The current pilot path is for bounded validation of invited onboarding, organization setup, organization-scoped documents, document detail review, version history, access grant and review loops, controlled links with approval by a different owner or admin account, lifecycle transitions, and audit visibility.
It is not a promise of full matter-pack management UI, broad migration tooling, deep integrations, or unrestricted enterprise rollout. Access is not self-serve.
Contact info@mysafeflow.com for written follow-up.
Submit an access request. We review it and, if suitable, send an onboarding invitation. Existing users can sign in or recover access.
Prefer written contact? Email info@mysafeflow.com
If your browser does not open email automatically, copy the address and send a message manually.