Skip to content

[stable27] fix(devmanual): Clarify privacy requirements of unified search providers #10721

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ChristophWurst merged 1 commit into from
Jul 6, 2023
Merged

[stable27] fix(devmanual): Clarify privacy requirements of unified search providers #10721

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions developer_manual/digging_deeper/search.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.