Data changes by stage and role
Data we process
A visitor, applicant, and member do not need the same information. This grouping explains expected scope without claiming to be a final legal inventory.
Account
Name, email, language, verification, session, and security information.
Professional profile
Role, summary, skills, availability, work links, and public channels.
Program applications
Answers, links, state, review notes, and decisions connected to an application.
Membership and workspace
Program, role, capabilities, invitations, members, and work-related activity records.
Projects and rights
Work, catalog, capacity, or license-scope data when the product supports it.
Support and security
Issue descriptions, error information, and records needed for protection and diagnosis.
What you provide and what service use creates
Data sources
Data may come directly from you, from product activity, or from an organization inviting you into professional scope.
- Information entered during account, profile, or application creation.
- Public links you choose to provide to explain your work, organization, or capacity.
- State, decisions, and records created through review, membership, and workspace use.
- Technical information needed for security and operation, such as device, time, and error context within appropriate limits.
- Invitation or membership information provided by an authorized workspace member.
Why is this data needed?
Purposes
Data use should connect to a clear product purpose and be limited to what that purpose needs.
Operate the account
Authenticate, save preferences, recover access, and protect sessions.
Review programs
Understand role, fit, links, and make a decision or request a change.
Manage membership
Open appropriate capabilities and preserve program and workspace boundaries.
Support professional work
Organize a team, project, or catalog within what membership supports.
Security and Support
Detect abuse, diagnose issues, and protect accounts and workspaces.
Obligations and rights
Review a report, dispute, or capacity when retention or processing is needed for it.
A public profile is different from workspace data
Visibility and sharing
Some professional information may be public by choice. Applications, reviews, memberships, and team data remain private by default.
Public by choice
A professional name, summary, work links, or channels shown in a context that clearly marks them public.
Private to the application
Answers, state, and review notes are not treated as a public page.
Private to the workspace
Members, roles, internal materials, and records do not appear outside allowed access.
Service providers
Necessary data may be processed by operational services supporting hosting, security, or communication to provide the service.
Protection or enforceable request
Limited information may be kept or shared when needed to protect the service or address a dispute or enforceable request.
Limiting access is better than relying on secrecy alone
Protection
Data protection needs membership boundaries, permissions, and operating records in addition to safe user behavior.
- The workspace does not ask members to share a password or verification code with a team or administrator.
- Each workspace should remain isolated, with permissions enforced by the server.
- Do not upload sensitive documents into a general form or field not designed for them.
- Use Support immediately when a session, invitation, or access state appears unexpected.
Not all data is retained for the same period
Retention
Retention depends on data type, account or application state, and operating, security, or rights-related need.
Active account
Information needed to operate the account and membership remains while the service relationship continues.
Closed application
Its state and limited information may remain to understand decisions, prevent duplication, and address objections.
Ended workspace or membership
Access may end immediately while records needed for security, disputes, or work integrity remain.
Report or dispute
Specific information may need to remain until review ends or the reasonable need expires.
Access, correction, and deletion start with a clear request
Your choices
The response depends on data type, account state, and open workspace or dispute context. Identity verification may be required first.
Identify the data
Account, professional profile, program application, membership, or workspace data?
Identify the action
Access, correction, deletion, account closure, or objection to information visibility?
Use Contact
Send a limited description without sensitive documents until an appropriate verification route is provided.
Allow verification
Some records may not be deleted immediately when needed for security, rights, or an open dispute.
Frequently asked questions
Is my application data public?
No. Application answers, state, and review notes are not a public page and are used within application and membership workflows.
Can team members see all my data?
Not automatically. Visibility depends on workspace scope, role, permissions, and the purpose of the data.
Do I need to upload contracts or identity documents when applying?
Not in the public application unless a specialist flow explicitly asks. Begin with reviewable public information and links.
Does account deletion erase every record immediately?
Limited records may remain for security, disputes, or operating obligations. Final handling should be defined by the approved policy.
How do I request a data correction?
Use Contact and identify the data type, page, and requested correction without sending passwords or complete documents.
Is this a final approved privacy policy?
This is detailed, cautious product copy, but it needs legal review and final approval before being treated as binding policy.
Continue
Have a question about your data?
Identify the data and request type, then use Contact or Support without sharing sign-in information or sensitive documents in the first message.