Privacy: know who will receive each piece of information
Reading a public page and opening a private account create different data relationships. Before completing a form, check the final destination address and its privacy notice. Identify the organisation collecting information, the stated purpose, retention period and method to request access or correction. Similar design on two addresses does not prove the same organisation controls them.
Use a minimal disclosure habit
An editorial correction can usually be described with a page address and a short explanation. A passport, payment card or account password is unnecessary. A separate account provider may have verification duties of its own, but check the request on its verified site. Do not upload a document from an unexpected message. Confirm the recipient before sending sensitive material.
Check devices and sessions
Cookies and local storage may support site functions, remember preferences or help measure visits. Read the controls presented to you. On a shared device, sign out and check saved permissions. Closing a browser tab might leave a private session active. Two websites can use separate storage despite a familiar look. Someone else using the device could see saved activity.
Route requests to the right controller
For data in an external player account, contact the controller named in that service's privacy notice. Keep the date and reference of your request. Koitos.org cannot read, amend or erase another organisation's records. For wording on this site, give the editor only the page and evidence needed for a correction.
Recheck a link before entering data
A bookmark or short link can end at an address different from the one you expected. Read the complete final address. A logo alone does not identify the recipient. If you cannot establish who operates the form, leave it unfilled until the question is answered.