Example description¶

Example

Email¶

The contact email address for this plugin is <example.email@provider.com>.

EULA¶

By submitting a Plugin (as defined in Schedule 4 of the EULA), you acknowledge that you agree to the terms of the Jagex End User License Agreement (EULA) found at https://legal.jagex.com/docs/terms/eula (and all terms incorporated into it be reference) and acknowledge that such terms are legally binding on you. If you do not agree to the terms of the EULA, you must not submit a Plugin or use the Plugin functionality anyway. In such circumstances, Jagex does not licence the software to you, or grant you any of the relevant rights relating to the submission of Plugins set out in the EULA and you will not be permitted to access or use the Plugin functionality in any way whatsoever.

Permissions¶

HttpAccess¶

This plugin requests the HttpAccess permission for <http://example.url.com>. This permission is used to send information about <list information here> to the aforementioned website, where it is used for <list what the information is used for>.

Screenshot¶

This plugin requests the Screenshot permission. This permission is used to take screenshots of <describe situations screenshots are taken>.

File I/O¶

This plugin requests the File I/O permission. This permission is used to save files to the local device for <describe what files are created>. This permission is not used to load local files.

Combine permissions¶

The Screenshot and File I/O permissions are combined to save screenshots to the local device. These screenshots are only saved locally, and once they are saved the information is inaccessible to the plugin. Screenshots are not involved in http transfer.

Data Protection (case 1)¶

This plugin uses the following information <describe the information used e.g. character name, in-game chat, hashed identifier, game events>.

This information is not transmitted outside of the plugin under any circumstances.

Game information is not stored by the plugin between sessions, although plugin setting are stored between sessions. Screenshots are taken and saved locally, whereupon it is no longer accessible by the plugin.

For Jagex: I request that the supplied email is hiddden from public view.

Data Protection (case 2)¶

This plugin uses the following information <describe the information used e.g. character name, in-game chat, hashed identifier, game events>.

This information is transmitted to <http://example.url.com> that is in the UK, EU, EEA or a country that has full or relevant partial UK adequacy status as specified by http://developer.runescape.com/submission/adequacy.html. The developer's privacy notice is available at <http://example.url.com/>.

This endpoint secures the data by <list security methods>. The information can be accessed by <List users and methods by which the information can be accessed>. All data rights requests should be submitted to this email address given above.

Game information is not stored by the plugin between sessions. Plugin setting are stored within the plugin between sessions. Screenshots are taken and saved the local device, and are no longer accessible by the plugin after saving.

Data Protection (case 3)¶

This plugin uses the following information <describe the information used e.g. character name, in-game chat, hashed identifier, game events>.

This information is transmitted to <http://example.url.com> that does not have full or relevant partial UK adequacy status as specified by http://developer.runescape.com/submission/adequacy.html, however, Jagex and the Developer have put in place appropriate safeguards to protect your data. The developer's privacy notice is available at <http://example.url.com/>.

This endpoint secures the data by <list security methods>. The information can be accessed by <List users and methods by which the information can be accessed>. All data rights requests should be submitted to this email address given above.

Game information is not stored by the plugin between sessions. Plugin setting are stored within the plugin between sessions. Screenshots are taken and saved the local device, and are no longer accessible by the plugin after saving.