| GDPR | Restrict profile access | Ownership and permitted sharing govern profile and Team Space access; you can hide profile sections. Authorised account administrators can see names, surnames and email addresses for account management. Private performance reviews remain subject to team-role permissions; service-admin status alone does not grant access. | In place |
|---|
| GDPR | Export account data | The authenticated Account control downloads a JSON copy that includes owned Journeys, coaching and action plans, authorised projects, calendar events and milestones, and readable performance reviews. Availability does not depend on plan tier. | In place |
|---|
| GDPR | Record terms and honour AI choices | Account terms acceptance is recorded. A Declined AI preference blocks processing; an unset preference may allow it after terms acceptance. Some features require additional consent. | In place |
|---|
| GDPR | Reduce identifiers sent to AI | Shared outbound checks remove common identifiers, and supported workflows use request-scoped person references. New Personal Journey and Team Manager Journey summaries store references with authenticated, encrypted local name mappings; authorised responses restore names. Older analyses have not been retroactively rewritten. Pseudonymisation reduces exposure but does not guarantee anonymity. | Applied with a defined scope |
|---|
| GDPR | Provide confirmed account erasure | Account deletion requires explicit confirmation. Shared-work and lawful audit records may remain; purpose-limited post-deletion abuse-prevention records have a three-year expiry. Legacy records await a reviewed migration. Access and portability processes remain subject to operational review. | Applied with a defined scope |
|---|
| GDPR | Limit post-deletion abuse records | New records use purpose-separated keyed matches for email or phone, not copied names or raw contact details, and retain the existing three-year expiry. Legacy rows remain until a reviewed migration; pseudonymous matching data is still personal data. | Applied with a defined scope |
|---|
| GDPR | Protect data sent to service providers | Hosting, payment, email and AI services can process data needed to operate Team-Buddy. We do not sell personal data or share it for third-party advertising. AI workflows reduce common identifiers. This status covers technical safeguards, not a completed legal review of provider agreements, retention or international transfers. | In place |
|---|
| EU AI Act | Record human review of AI results | In Role Fit, job matching, Match Lab, Team Match and team analysis, people can record whether they used a result as one input, changed it before use, or did not use it. AI does not make the app’s final decision. This record supports transparency; it does not establish the system’s legal classification or compliance. | In place |
|---|
| EU AI Act | Human-led scoring with AI assistance | Scoring draws on information provided by users and human-defined calculation rules. In some workflows, AI also assesses evidence or contributes a score to support complex analysis. Supported AI workflows minimise direct identifying details before processing. Results support people's judgement: users review the information and retain the final choice. This status covers the safeguards described here, rather than a blanket legal compliance claim. | Applied — defined scope |
|---|
| Assessment quality | Document AI governance and human oversight | Team-Buddy documents AI and privacy safeguards and expects human review of consequential decisions. This describes internal governance, not an external certification, business associate agreement or conformity assessment. | Applied with a defined scope |
|---|