Who and what this notice covers
IO Limited is responsible for information collected through this corporate website. This notice covers general enquiries, the requests directory and CMS access. An operating business’s customer service or employment process may have a separate notice.
Use privacy requests for questions or rights requests. Formal corporate particulars can be requested through corporate information.
What is collected and why
Forms collect your name, reply email, organisation if supplied, request category, message and the contextual fields shown on the form. They are used to route, assess and respond to the matter, prevent misuse and keep an appropriate handling record.
A request identifier prevents duplicate submissions. A pseudonymous rate-limit key derived from a technical request identifier helps prevent repeated abuse; the application does not store raw IP addresses in its enquiry records. Hosting and security providers may process IP addresses and technical logs to deliver and protect the service.
CMS access uses an authorised email, verification challenges, a salted password hash and session records. Passwords are not stored in readable form.
Keep submissions proportionate
Required fields are marked in the form. Without a reply address and sufficient context, a request may be impossible to verify or answer. Do not include passwords, payment-card details, full identity documents or unrelated personal information.
Sending an enquiry does not enrol you in marketing. This site does not use advertising pixels or audience analytics. Fonts and site imagery are served locally.
How long records remain
Website intake is not a permanent case archive. On the standalone public deployment, the application removes closed submissions 90 days after their last update and removes intake records 365 days after receipt. A matter requiring a longer legal or operational record must be transferred by its responsible reviewer to an approved, separately governed record system before that limit. Do not rely on this inbox for a legal hold.
Authentication challenges expire after 10 minutes and CMS sessions after 8 hours. Expired authentication and rate-limit records are removed by scheduled maintenance. Notification queue metadata is removed 30 days after the related submission is gone. Provider backups and technical logs follow the provider’s retention controls.
Access, correction and concerns
You may have rights to access or correct information and other rights under the law applicable to your relationship. Use the privacy request form and describe the records or action concerned. Identity and authority may need to be verified before action is taken.
A request will be assessed against applicable legal requirements and any justified limitations. You can raise a concern about our handling through the same route and may complain to the competent data-protection authority.
Changes to this notice
This notice is updated when the website’s data handling changes. The edition at the top identifies the current text. A new purpose or material operational change must be assessed before the corresponding collection or processing is introduced.