Data and Privacy

Data and Privacy

How Beesla Handles Candidate Data and Privacy

Beesla is built to help teams source candidates efficiently while handling data responsibly. This page explains how Beesla approaches data collection, storage, access, and privacy so teams know what happens to candidate and company information.

This is a high-level overview. More specific details are covered in the related sections.

Data Beesla Works With

Beesla works with professional candidate and company data relevant to recruiting.

This includes:

• Publicly available professional information
• Role-relevant experience and career history
• Company-level information when requested

Beesla does not require resumes to be uploaded and does not rely on user-submitted applicant data.

How Data Is Collected

Data is retrieved when:

• You run a search
• You request company details

Data retrieval is intentional and tied to user actions. Beesla does not continuously scrape or collect data in the background.

Each retrieval event is associated with token usage, making data access explicit and auditable.

How Data Is Stored

When data is retrieved:

• Candidate profiles are stored in your workspace CRM
• Company records are stored when company details are requested
• Historical context is preserved

Data storage exists to support review, collaboration, and sourcing history. Stored data does not incur additional cost.

Data Access and Visibility

Data inside a workspace is shared among authorized team members.

Access is controlled through:

• Workspace membership
• Role-based permissions

Only users with appropriate roles can retrieve new data. Reviewing stored data is available to all authorized members.

Data Usage Boundaries

Beesla does not:

• Sell customer workspace data
• Reuse customer searches for other customers
• Expose workspace data outside your organization

Data retrieved for your searches is isolated to your workspace.

Privacy by Design

Beesla is designed with privacy considerations built in:

• Data retrieval is user-initiated
• Access is role-controlled
• Stored data supports collaboration, not redistribution

Teams remain in control of how data is used within their hiring process.

What Beesla Does Not Do With Data

Beesla does not:

• Train public models on customer workspace data
• Automatically export data to third parties
• Modify or enrich data without user action

Any enrichment or retrieval is explicit and traceable.

Why This Matters for Hiring Teams

Responsible data handling helps teams:

• Maintain trust with candidates
• Stay aligned with internal policies
• Avoid uncontrolled data spread
• Keep sourcing activity transparent

Beesla is designed to support professional recruiting standards, not bypass them.

What’s Next

For more detail:

• See Sources to understand where data comes from
• See Security for technical safeguards
• See Teams and Access for permission controls