Team Allocation: implement privacy deletion

[JGStyle]

✨ What is the change?

This PR implements the privacy deletion feature for the team allocation CPM

It registers the deletion handler using the sdk functinality.

Upon the deletion, the corresponding records in: allocations, student_team_preference_response, student_skill_response, tutor related to the requesting subject is deleted.

📌 Reason for the change / Link to issue

As part of the bigger effort described in https://github.com/orgs/prompt-edu/discussions/683

🧪 How to Test

As a user with team allocation data, request deletion:

1. click your user profile in the top right corner

2. click privacy

3. click deletion

4. request a deletion

5. approve the deletion as an admin
   Then, verify that the data from the self allocation cpm was deleted
   f.e. by looking at the team allocations and verifying that the student was removed. (or by inspecting the db)

🖼️ Screenshots (if UI changes are included)

full deletion flow

2026-07-14.at.21.58.30.mp4

(the old deletion result screen is from an earlier test and wouldn't be surfaced to a normal user)

✅ PR Checklist

• Tested locally or on the dev environment
• Code is clean, readable, and documented
• Tests added or updated (if needed)
• Screenshots attached for UI changes (if any)
• Documentation updated (if relevant)

[coderabbitai]

Warning

Review limit reached

@JGStyle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 66b8d60b-a2c9-459f-9982-691ce0cb8ecd

📥 Commits

Reviewing files that changed from the base of the PR and between 9178d5f and 308be7b.

📒 Files selected for processing (5)

• servers/team_allocation/db/query/privacy.sql
• servers/team_allocation/db/sqlc/privacy.sql.go
• servers/team_allocation/main.go
• servers/team_allocation/privacy/main.go
• servers/team_allocation/privacy/service.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/gdpr-data-deletion-team-allocation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[JGStyle]

optimally, merge #1747 first.