1. Does your plugin collect personally identifiable information (that includes IP addresses)?
Yes, but only if you enter that information into the plugin’s settings pages or otherwise tell the plugin to store personal data.
It does not collect any information about visitors who are not logged in.
2. If so, what types of personally identifiable information does your plugin collect?
It may store usernames and user IDs. For example, if you configure it to only allow one specific user to access AME settings, the plugin will store that user’s ID.
It may also store any information that appears in the admin menu, like menu titles, URLs, capabilitities and so on. Usually these do not contain any personal data, but if one of your other plugins happens to add some personal data to the menu – like showing a user’s name or email in a menu title – then Admin Menu Editor might store that information.
3. For what purpose(s) does your plugin collect personally identifiable information?
To enforce custom permissions and to control access to the plugin (e.g. by only allowing one specific user to change menu settings).
4. Does your plugin have a privacy policy that explains how you use my website visitors’ personally identifiable information?
Not yet. As I mentioned above, the plugin doesn’t store any information about regular visitors, but I’m planning to create a documentation page that describes what it may store about logged-in users.
5. Do your plugin use cookies or collect various types of data-usage information?
It doesn’t track usage statistics, but it does use cookies to store user preferences. For example, it uses cookies to remember if “compact layout” is enabled in the menu editor.
If you have enabled the “Highlight new menu items” feature, it will also use cookies to temporarily store the menu items that you have already visited so that it can stop highlighting those items.
-
This reply was modified 6 years, 9 months ago by
Janis Elsts.