Decide whether you are stopping or changing the arrangement
Name the reason in practical terms: different schedules, too many routine requests or a preference for managing rules yourself. A replacement person needs their own invitation and consent; they should not inherit an obligation by surprise. Avoid sharing account passwords to transfer the role. You can discuss a new arrangement without disclosing old request notes or private conversations.
Review the connection in Warden
On the owner phone, open Your Warden and its options. Current versions provide Remove Warden and Replace Warden. Read the confirmation before completing either action. The current confirmation explains that requests to that person stop, saved rules stay, and Warden rules need a new connection. If your version shows different options, inspect its message rather than guessing from this article.

Check saved rules and outstanding requests afterward
Disconnecting a person is not a promise to clear every local restriction. Review Standard, Warden and Lockdown rules individually and inspect any active commitment. Check the displayed status of pending requests; do not rely on an old notification as a current approval. Reconnect or change eligible rules deliberately, and keep emergency access separate from ordinary editing.
Example: a one-week study agreement ends
Two friends agreed to try evening support for a week. At the review, one says work makes replies difficult. They thank each other and end the arrangement without extending it by default. The owner removes the connection, verifies that the saved study schedule is still listed and reviews its access mode. A future invitation is a new agreement, not an automatic continuation of the old one.
Keep account and subscription decisions separate
Removing a Warden connection is different from deleting your account, signing out or cancelling a subscription. Do not perform those broader actions merely to end a relationship in the app. If the change fails, check connectivity and the current connection state before trying again. Use support for an unclear state, without sending passwords or sensitive request contents.



