The privacy field guide

Your first 15 minutes.

1. Review your email account’s recovery settings and active sessions.
2. Enable a passkey or authenticator-based two-factor authentication.
3. Replace reused passwords with unique passwords stored in a trusted password manager.
4. Review one public profile and remove details it doesn’t need.
5. Start a Safuy scan of your verified email and check each match.

A match deserves context.

Search results can be outdated, incomplete, or unrelated to you. Open the source, check the page address, and confirm that the information actually belongs to you. A public email mention is not proof that an account was breached.

Avoid links that ask for passwords, payments, or identity documents to “unlock” a result. Go directly to the provider’s official website whenever possible.

Ask for less. Share less.

A removal request works best when it identifies the relevant page and the information you want removed. Use Safuy to prepare a draft, replace the bracketed details, and submit it through the publisher’s official privacy or opt-out page.

Only share the minimum information needed to validate your request. If identification is required, check the publisher’s process before sending anything. Safuy does not need a copy of your ID.

After submitting, record the request in your workspace. When the publisher responds, check the live page again. Confirm removal only when you have verified it yourself.

Worried about a leak?

Start with the affected account’s official security page. Change reused passwords, end unfamiliar sessions, check recovery methods, and enable two-factor authentication. If payment details may be affected, contact the relevant provider through its official app or website.

You can check a reputable breach notification service directly. Safuy’s current scan searches the public web; it does not search stolen datasets or establish whether passwords were leaked.

Privacy is a practice.

No service can remove every record or prevent every exposure. Publishers, search engines, archives, and public blockchains work differently. A removed page may still exist in caches. Blockchain transactions are public and cannot be erased by Safuy.

Build a repeatable routine, keep evidence, and focus on changes you can control.