[GH-ISSUE #5957] [feature]: Optional clearing of local workspace data on explicit logout #2341

Open
opened 2026-03-17 00:01:14 +03:00 by kerem · 4 comments
Owner

Originally created by @edlyra on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5957

Is there an existing issue for this?

  • I have searched the existing issues

Summary

Add an optional setting to clear locally persisted workspace data on explicit logout only.

The default behavior should remain unchanged, so local data continues to be preserved unless the user enables this option.

Why should this be worked on?

The current behavior makes sense for offline/disconnected continuity, and this should be preserved.

However, explicit logout is a different scenario. When a user intentionally clicks "Logout", there may be an expectation that locally cached workspace data should no longer remain accessible in that browser, especially on shared or public machines.

A good compromise would be to add a user-controlled option to clear local workspace data only on explicit logout, while keeping the current behavior as the default.

This cleanup should not happen when:

  • the network connection is lost
  • the backend is temporarily unavailable
  • session validation fails unexpectedly
  • a token expires during normal use
  • the app is operating offline

This would support both use cases:

  • preserving offline/disconnected continuity
  • improving privacy on shared devices for users who explicitly want local data removed on logout

This would also help in support scenarios on customer machines.

In practice, it is easy to forget opening Hoppscotch in a private/incognito window before starting a support session. When that happens, manually clearing browser storage afterward is inconvenient and not always practical, especially in a customer environment.

An optional setting to clear local data on explicit logout would provide a safer and more convenient fallback, while still preserving the current default behavior for offline/disconnected use.

Originally created by @edlyra on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5957 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Add an optional setting to clear locally persisted workspace data on explicit logout only. The default behavior should remain unchanged, so local data continues to be preserved unless the user enables this option. ### Why should this be worked on? The current behavior makes sense for offline/disconnected continuity, and this should be preserved. However, explicit logout is a different scenario. When a user intentionally clicks "Logout", there may be an expectation that locally cached workspace data should no longer remain accessible in that browser, especially on shared or public machines. A good compromise would be to add a user-controlled option to clear local workspace data only on explicit logout, while keeping the current behavior as the default. This cleanup should not happen when: - the network connection is lost - the backend is temporarily unavailable - session validation fails unexpectedly - a token expires during normal use - the app is operating offline This would support both use cases: - preserving offline/disconnected continuity - improving privacy on shared devices for users who explicitly want local data removed on logout This would also help in support scenarios on customer machines. In practice, it is easy to forget opening Hoppscotch in a private/incognito window before starting a support session. When that happens, manually clearing browser storage afterward is inconvenient and not always practical, especially in a customer environment. An optional setting to clear local data on explicit logout would provide a safer and more convenient fallback, while still preserving the current default behavior for offline/disconnected use.
Author
Owner

@statxc commented on GitHub (Mar 6, 2026):

@jamesgeorge007 Can I take on this? I'd like to contribute! thanks

<!-- gh-comment-id:4012541031 --> @statxc commented on GitHub (Mar 6, 2026): @jamesgeorge007 Can I take on this? I'd like to contribute! thanks
Author
Owner

@luongquochai commented on GitHub (Mar 10, 2026):

hi @jamesgeorge007 Can I try on this ?

<!-- gh-comment-id:4032331500 --> @luongquochai commented on GitHub (Mar 10, 2026): hi @jamesgeorge007 Can I try on this ?
Author
Owner

@statxc commented on GitHub (Mar 10, 2026):

@luongquochai Sorry, I am working on that now. Almost ready for PR 🙁

<!-- gh-comment-id:4032360095 --> @statxc commented on GitHub (Mar 10, 2026): @luongquochai Sorry, I am working on that now. Almost ready for PR 🙁
Author
Owner

@luongquochai commented on GitHub (Mar 10, 2026):

@statxc I'm sorry I missed your comment. Please keep going 👍

<!-- gh-comment-id:4032663656 --> @luongquochai commented on GitHub (Mar 10, 2026): @statxc I'm sorry I missed your comment. Please keep going 👍
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#2341
No description provided.