Spots 
A repair usually means handing your device to someone else, sometimes for days. Even when the shop is honest, things can go wrong: a motherboard swap can lock your drive, a reset can wipe your files, or a session left open can expose an account.
This guide gives you a practical checklist for phones and laptops, including a section for developers who keep keys, tokens and repos on their machine. Step 1: Back up (and verify the backup) A backup you have never opened is not a backup. iPhone: iCloud Backup, or a backup to a Mac/PC. Android: Google backup, plus copy photos and files to a computer or cloud storage. Open the backup destination and confirm that recent photos, chats and files are actually there. Copy your important folders to an external drive or cloud storage. Keep a second copy if the data matters (the 3-2-1 idea: 3 copies, 2 media types, 1 offsite). Keep a second copy if the data matters (the 3-2-1 idea: 3 copies, 2 media types, 1 offsite). Check that the files open on another device. Check that the files open on another device. Step 2: Save your encryption recovery keys
This is the step most people miss. Some repairs, especially a motherboard replacement, can make an encrypted drive ask for its recovery key on the next boot. Without it, the data can be lost for good. Store the key somewhere that is not on the device being repaired**. Step 3: Move your two-factor codes Authenticator apps often keep codes only on the device. Use your app's export or transfer feature, or Save the backup codes from each important account (email, banking, GitHub, cloud provider). Do this before the repair. If the phone is dead, you may need those backup codes to get back in. Step 4: Sign out and remove what you can Take out the SIM and memory card. Log out of banking, email and payment apps if the phone still works.
Ask the technician why they need Find My iPhone / Find My Device turned off, since some repairs do require it. Turn it back on when you get the phone back. Sign out of your browser profiles and cloud accounts. Sign out of your browser profiles and cloud accounts. Remove or deauthorize licensed software if it limits the number of devices. Remove or deauthorize licensed software if it limits the number of devices. If the repair does not involve the storage drive, ask whether the drive can be left out or removed during the work. If the repair does not involve the storage drive, ask whether the drive can be left out or removed during the work. Step 5: Developer checklist If you write code on the device, add these: SSH keys in ssh make sure they are passphrase-protected. SSH keys in ssh make sure they are passphrase-protected.
API tokens and .env files: do not leave production secrets in plain text. Move them to a password manager or secrets tool.
API tokens and .env files: do not leave production secrets in plain text. Move them to a password manager or secrets tool. Git credentials: log out of credential helpers, and push or stash unfinished work to a remote. Git credentials: log out of credential helpers, and push or stash unfinished work to a remote. Docker, cloud CLIs and package registries:** run the logout commands (for example docker logout). Docker, cloud CLIs and package registries:** run the logout commands (for example docker logout). Browser sessions: GitHub, cloud consoles and admin panels stay logged in for a long time. Browser sessions: GitHub, cloud consoles and admin panels stay logged in for a long time. Local databases: export or back up anything you can't recreate. Local databases: export or back up anything you can't recreate.
Afterwards, rotate any token you are not fully comfortable with, and remove old SSH keys from the services that trusted them. Step 6: Record the current state Take photos of the device from all sides (scratches, dents, screen condition). Take photos of the device from all sides (scratches, dents, screen condition). Note the serial number, and the IMEI on a phone (dial *#06#). Note the serial number, and the IMEI on a phone (dial *#06#). Write down what was wrong and what you asked to be fixed. Write down what was wrong and what you asked to be fixed. Step 7: Get the terms in writing Ask before the device leaves your hands: What exactly will be repaired, and at what price? Which parts will be used (original, OEM or compatible)? What warranty is provided, and for how long? Will you need my passcode? Can the test be done in front of me? Will data be touched?
Is there a chance of a reset or reinstall? If the answers are vague, or you are pressured to decide quickly, treat that as a warning sign. Step 8: Use a temporary passcode If the technician needs to unlock the device for testing: Set a temporary passcode or a separate guest/test account. Set a temporary passcode or a separate guest/test account. Change it as soon as you get the device back. Change it as soon as you get the device back. Do not share your main account password or your password manager master password. Do not share your main account password or your password manager master password. Step 9: After you get the device back Test the screen, camera, speakers, charging, Wi-Fi and keyboard before leaving. Test the screen, camera, speakers, charging, Wi-Fi and keyboard before leaving. Change your passcode and, if you shared anything, the passwords for your main accounts.
Change your passcode and, if you shared anything, the passwords for your main accounts. Check for unknown apps, profiles, browser extensions or user accounts. Check for unknown apps, profiles, browser extensions or user accounts. Turn Find My / Find My Device back on if you disabled it. Turn Find My / Find My Device back on if you disabled it. Confirm that your backup restores properly, then keep the invoice and warranty paper. Confirm that your backup restores properly, then keep the invoice and warranty paper. [ ] Backup done and verified
A repair usually means handing your device to someone else, sometimes for days.