Use only the information needed for the introduction.
MyProfile separates public professional information from private buyer enquiries. Public profile browsing does not require a buyer account.
Privacy notice version 2026-08-v1Public directory
Published professional profiles contain information the profile owner has explicitly chosen to publish. Subscription tier, private email addresses, authentication identifiers and unpublished profile drafts are not included in the public profile API.
Shortlist
The buyer shortlist is stored locally in the browser in this release. Work Being does not create a server-side buyer behaviour profile simply because someone saves or compares professionals.
Private consulting enquiries
When a visitor sends a consulting enquiry, Work Being stores the information needed to route the message privately to the selected consultant. The enquiry is not displayed publicly.
- Name and email address are required so the consultant can respond.
- Organisation, role and timing are optional.
- The message should contain only context relevant to the proposed collaboration.
- The selected consultant can see the enquiry in their private MyProfile inbox and may reply by email.
- Work Being stores the privacy-notice version and consent-text version associated with the submission.
Sending an enquiry does not create a contract, booking or therapeutic relationship.
Professional controls
Professionals can mark an enquiry read, archive it, reply outside the platform by email, or permanently delete it from their MyProfile inbox. Deleting an enquiry removes the enquiry record; the audit log records only that a deletion action occurred, not the deleted message content.
Evaluation evidence
Evaluation data follows a separate trust and consent model. MyProfile only displays evaluation content that qualifies for public display under the Work Being Evaluation publication rules. See Evaluation integrity.
Current infrastructure boundary
MyProfile API execution and the MyProfile Azure SQL data layer are hosted in Sweden Central. The public frontend is delivered through Azure Static Web Apps. Direct access to the linked Function backend is blocked; public API traffic is routed through MyProfile.