For both sh.tangled.* records and org.tangled.* records.
For sh.tangled.* records, make it clear that those are just for archival purpose and Tangled doesn't even read/write those data today. If you are happy with what you see today, you are fine to delete them.
For org.tangled.* records, this will be complete Tangled profile removal, so end result will be signout. Worth mentioning they can temporarily deactivate their account instead, and ask user for auth again with larger scope including:
repo:org.tangled.actor.profile?action=delete
Clients should not request this permission for typical use, because users will always get a profile record on active session.
Actually, we can have way more options depending on their exact need:
- keep
org.tangled.*data in PDS but remove all synced/cached data from Tangled (the company) - keep all data untouched and mark their atmosphere account as deactivated
- keep all data untouched and mark their Tangled profile as deactivated through label. This will let them keep Tangled data, deactivate their Tangled profile, while keep using other atmosphere apps normally. idk if this is possible / good pattern in atproto.
- actually remove all
org.tangled.*data from PDS and signout from current client.