Set Shared-Phone Boundaries

Agree on the loan before handing over the phone

Privacy works better with a narrow task and an explicit return point. Do not use hidden monitoring, impersonation or coercive controls. If trust, consent or safety is uncertain, provide a different device or supervise the intended task openly.

Verify the real phone state

1. 01State the permitted task and expected duration plainly.
2. 02Open only the necessary app or use a guest, pinned or separate-device option when suitable.
3. 03Do not share the device unlock code if the task can be completed without it.
4. 04Avoid secret surveillance or accessing the borrower’s accounts and communications.
5. 05End the loan, close the task, review unusual changes and restore normal notification settings.

Keep useful evidence, not message content

Record only operational facts when needed: loan purpose, time, device state, restrictions and return check. Do not create a surveillance log of another person’s private activity.

Stop the loan when

• The borrower is asked to surrender their own messages or credentials.
• The owner intends to record activity secretly.
• The loan requires broad access when a spare device or assisted task would suffice.

App entry is not system-wide privacy

Not operating-system-wide E2EE, Android enterprise management or app provider account recovery. Test Android notifications, message-provider behavior and recovery separately.

Run the final independent check

Before the handoff, make sure the boundary is understandable without technical language. The borrower should know the permitted task, when to return the phone and what to do if another notification or app appears. The owner should know when to stop. Respect and consent are operational controls; secret monitoring and vague rules create risk instead of solving it.

Resolve these before lending