From 9c49e75d0f7c95c2d7528f95c82dfbbd916b0b77 Mon Sep 17 00:00:00 2001 From: Christoph Wurst Date: Thu, 6 Jul 2023 09:45:23 +0200 Subject: [PATCH] fix(devmanual): Clarify privacy requirements of unified search providers Signed-off-by: Christoph Wurst --- developer_manual/digging_deeper/search.rst | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/developer_manual/digging_deeper/search.rst b/developer_manual/digging_deeper/search.rst index 084fd7319..b2e22325a 100644 --- a/developer_manual/digging_deeper/search.rst +++ b/developer_manual/digging_deeper/search.rst @@ -416,3 +416,8 @@ The unified search is available via OCS, which means client application like the $entry->addAttribute("boardId", "567"); .. note:: This method was added in Nextcloud 21. If your app also targets Nextcloud 20 you should either not use it or add a version check to invoke the method only conditionally. + +Privacy +------- + +All search providers have to value privacy and prevent leaking of sensitive data by default. Therefore search terms must not be sent to third parties by default. If a search provider makes use of third party services, user consent has to be acquired, e.g. by an opt-in toggle in the user's personal settings.