Bug 435325 - Stop collecting recent files and locations
Summary: Stop collecting recent files and locations
Status: RESOLVED DUPLICATE of bug 416271
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Dolphin Bug Assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-03 20:20 UTC by Norberto Bensa
Modified: 2022-07-22 19:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Norberto Bensa 2021-04-03 20:20:24 UTC 
SUMMARY

Just a few minutes ago I became aware that Dolphin saves recent documents and locations; while I think it is a good idea and it helps in usability terms, it's also a privacy invassion.

I would like to be able to disable collecting this information in Dolphin, KDE/Plasma, and all its applications.

Please note that I want to disable this functionality, hide it is not enough.

Thanks
Comment 1 2wxsy58236r3 2021-04-04 10:11:20 UTC 
I hope there can be a meta bug which tracks issue reports related to recent files, locations and documents.

Some examples:
- Bug 355399
- Bug 423732
- Bug 425755
Comment 2 Nate Graham 2021-04-05 16:35:15 UTC 
In fact this option already exists in the Activities KCM:

System Settings > Workspace Behavior > Activities > Privacy > Do Not Remember

The problem is, this is pretty un-discoverable. I don't think most people would guess that the setting lives on the Activities page. That's a UI issue though that we'll track separately with Bug 416271.
Comment 3 Norberto Bensa 2021-04-05 16:47:09 UTC 
Thank you Nate. 

Yes, and in fact, I was looking in System Settings before my original bug report, but yes, the option is totally undiscoverable :-)

I'll subscribe to #416271

Thanks!
Comment 4 Nate Graham 2021-04-05 16:55:05 UTC 
You're welcome!
Comment 5 Nate Graham 2022-07-22 19:26:36 UTC 

*** This bug has been marked as a duplicate of bug 416271 ***