Privacy by design
Collect only the information needed for a clear workspace or team purpose.
Learn more→Trust Centre
Trust is part of the product.
AutoTeams combines privacy controls, secure workspace boundaries, explainable AI and human review so team recommendations remain transparent and accountable.
Four trust pillars
Designed for responsible team decisions.
Trust is not a separate policy page. It is built into how users register, join workspaces, share Team DNA and review Atlas recommendations.
Explainable AI
Show the signals, scores and reasoning behind every Atlas recommendation.
Learn more→Human control
Authorised users can review, adjust or reject any suggested team outcome.
Learn more→Appropriate verification
Apply email verification and stronger security according to role and risk.
Learn more→Trust architecture
How information moves through AutoTeams.
The process keeps data inside the correct workspace and ensures users understand what happens at every stage.
◇
Private workspace boundary
AutoTeams never searches all registered users. Atlas only evaluates eligible Talent inside the active workspace.
Register and verify
Users create an account, verify their email and review security settings.
Join a private workspace
Access is controlled through workspace membership and assigned roles.
Provide explicit consent
Members choose whether Team DNA may be visible, matched or used in insights.
Build from eligible Talent
Atlas only evaluates people inside the active workspace and selected population.
Explain the recommendation
Every result shows the balance, strengths, gaps and reasons behind the selection.
Keep a human decision
The user remains responsible for accepting, changing or rejecting the result.
The Atlas Promise
What Atlas will and will not do.
Atlas is designed to support people making team decisions, not to make hidden or irreversible decisions about them.
✓Explain every recommendation
✓Keep a human in control
✓Stay inside the active workspace
✓Respect Team DNA consent
✓Avoid inferring sensitive characteristics
✓Allow users to export or remove their profile
Your controls
Review privacy, consent and account security.
Manage the information Atlas can use and understand the controls available to workspace members.
ENTERPRISE TRUST & SECURITY
Understand who can access what — and what Atlas can see.
Corporate adoption depends on clear boundaries. AutoTeams separates account access, workspace permissions, profile privacy and Atlas processing so organisations can understand how people and data are used.
Secure authentication
Account access is authenticated before protected workspace features are available.
Role-based workspace access
Administrator, Team Leader and Member roles separate workspace responsibilities.
Workspace boundaries
Team activity and recommendations operate within the active workspace and selected population.
Profile controls
Members control profile visibility, matching eligibility and approved discovery settings.
Controlled Atlas context
Atlas should receive only the information required for the requested team or support task.
Human review
Atlas recommendations are decision support. People remain responsible for final team decisions.
Who can see my information?
Access depends on workspace membership, role, profile visibility and the context in which information is being used.
| Information | Member | Team Leader | Administrator | Atlas |
|---|---|---|---|---|
| Basic member/profile information | Own profile | Approved workspace use | Workspace administration | When required for the task |
| Atlas profile signals | Own signals | According to profile sharing | According to authorised access | When required for analysis |
| Team membership | Relevant teams | Relevant teams | Workspace teams | When required for team analysis |
| Workspace settings | No | Limited | Yes | No |
| Passwords / authentication secrets | Never exposed | Never exposed | Never exposed | Never exposed |
Your profile belongs to you.Atlas Profiles remain personal. Workspace access should use only the profile information made available for the relevant team, matching or approved discovery purpose.
Only the context needed for the task.
When Atlas generates a recommendation or Team Insight, AutoTeams should send the profile, team and requirement information needed for that analysis — not passwords, authentication credentials or unrelated workspace information.
01WorkspaceRelevant people, profiles and team requirement
→02AutoTeamsApplies workspace and profile controls
→03AtlasAnalyses the information required for the task
→04Human reviewRecommendation is reviewed before use
AI processing transparencyModel-provider training, processing location, retention and sub-processor statements must match the production configuration and contractual terms. AutoTeams should not make stronger claims until those settings and terms are verified.
CURRENT PRODUCT CONTROLS
Controls AutoTeams can explain today.
Protected application access and verified account identity are handled separately from team intelligence.
Workspace roles and membership determine what people can manage inside a workspace.
Profile visibility, team-matching eligibility and approved discovery are controlled per profile.
Atlas team analysis is scoped to the active workspace and selected population.
Recommendations expose evidence, confidence, strengths, gaps and risks for human review.
AutoTeams should use information relevant to the requested profile, team or support task rather than unrelated workspace data.
ENTERPRISE ROADMAP
Controls corporate customers are likely to request.
These are roadmap capabilities, not claims about the current MVP.
PLANNEDEnterprise SSO / SAML / OIDCPLANNEDOrganisation-wide MFA enforcementPLANNEDSCIM user provisioning and de-provisioningPLANNEDEnterprise audit and administrator reportingPLANNEDConfigurable retention policiesPLANNEDOrganisation security policiesPLANNEDData-residency options where supportedPLANNEDEnterprise integration and security review packs
DATA LIFECYCLE
Corporate questions AutoTeams should answer clearly.
What information is collected and why is it required?
Which workspace roles and profile settings allow it to be used?
Which information is sent for a specific Atlas task?
How long are profiles, invitations, teams, recommendations and support conversations retained?
How can a member request, export, correct or delete their information?
How can a customer report a security or privacy concern?