First, understand what they can and cannot do. A .uiid file is only as powerful as your Security Settings allow. At Data Backup Only it cannot sign in anywhere. At Login Support it can sign in to your UIID account. At Application Authentication it can also authenticate to applications under a specific alias.
Step 1 — Lower the tier immediately. Open Security Settings at uiid.me and set the feature to Disabled or Data Backup Only. This is the fastest way to reduce what the leaked file is worth.
Step 2 — Review what is connected. Check which applications you have granted access to and which AI agents hold permissions. Revoke anything you do not recognize or no longer use. Revoking is immediate.
Step 3 — Check your other routes. Make sure your backup codes are still somewhere only you can reach, and that your sign-in routes are the ones you expect.
Step 4 — Export a fresh file if you need one, and store it away from the device it came from — an encrypted drive or a password manager's secure file storage, never email or a shared drive.
Do not delete your UIID as a reaction. Deletion is one-way, and we cannot guarantee you could create a new verified identity afterwards.
Tell us: [email protected] — include when you think the file was exposed and what you have already changed.