You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running the Editor for a few dozens of seconds, even without doing anything in particular, two system popups appear indicating that the application wants to have access to the user's Contacts, then another one appears requesting access to the user's Calendar.
No explanation is given as to why this would be needed and this seems like a clear invasion of privacy.
Having basic respect for the user's privacy instead entail to:
Not attempt to use user's private data (contacts, calendar) until the point they are actually needed.
Provide a proper written explanation as to why accessing these data is useful to the application's operations.
Sign the application with GateKeeper so at least, if the application is found to be corrupted by the OS, it can automatically revoke these authorizations.
Absent these requirements, the application should not attempt to obtain users's data.
Cheers,
Laurent
The text was updated successfully, but these errors were encountered:
With Mojave if you try to access ~/Library/Calendars and such, the system shows an alert. There is no need to explicitly ask to access calendars or contacts.
IIRC Core Data Editor scans ~/Library to search for models and such and thus triggers the Calendars pop-up and co.
After running the Editor for a few dozens of seconds, even without doing anything in particular, two system popups appear indicating that the application wants to have access to the user's Contacts, then another one appears requesting access to the user's Calendar.
No explanation is given as to why this would be needed and this seems like a clear invasion of privacy.
Having basic respect for the user's privacy instead entail to:
Absent these requirements, the application should not attempt to obtain users's data.
Cheers,
Laurent
The text was updated successfully, but these errors were encountered: