Public discovery and private hiring data are kept separate.
This overview explains the product’s current data boundaries. Formal privacy requirements may vary by the jurisdictions where the service operates.
Public VA profiles
Only approved, available VAs who are enabled for directory visibility appear in the public directory. Public profile data can include name, avatar, professional headline, summary, specialty, skills, tools, industries, languages, experience, availability, schedule, and selected professional links.
Private hiring information
Email addresses, phone numbers, private resumes, account records, recruiter/admin notes, messages, role-service fees, and other non-public hiring data are not part of the public VA directory. Access is limited by account role and the relevant hiring relationship.
Role briefs and contact requests
Information submitted through a role brief or match request is stored so the team can understand and respond to the request. Hiring requests create a private pending job draft so the client does not need to re-enter the same details after signup. The draft is not made public automatically.
Product analytics
The application can record first-party page-view and conversion events such as page path, referring page, session identifier, signed-in user identifier when available, and event metadata. This is used to understand funnel performance and product usage.
Security and retention
Private files use signed access links and account data is protected through role-based database policies. Operational retention and deletion periods should be documented in the organization’s final privacy policy and data-governance procedures.