Publication and infrastructure data
Security.io’s hosting, security and content-delivery infrastructure may process standard request information such as IP address, user agent, requested URL, timestamp and security-event data. Security.io also uses audience analytics to understand aggregate publication use and improve the site.
Contact-form information
When a reader submits the protected contact form, Security.io may receive the reader’s name, email address, organisation, role, optional telephone number, inquiry category, message, consent choices, source page and technical anti-abuse information. The form must not be used to transmit passwords, private keys, active malware, regulated personal data, confidential customer records or material the sender is not authorised to disclose.
Research-report registration information
When a reader registers for a Security.io research report, Security.io may receive the reader’s name, work email address, role or function, company-size range, optional company or organization name, country, report identifier, source page, campaign or referrer information, submission timestamp, consent choice and technical anti-abuse information. Security.io uses this information to reserve or deliver the requested report, maintain report-access records, understand the professional audience using its research and improve future research products. Report registration by itself does not enroll the reader in a separate marketing list.
How contact information is used
Security.io uses contact submissions to evaluate and respond to editorial tips, corrections, commercial enquiries, events, media requests, licensing matters, technical issues, private briefing enquiries, privacy requests and related business communications. Information may also be retained as reasonably necessary to maintain records, prevent abuse, enforce site terms and meet applicable obligations.
Specialist introductions
When a reader separately authorises an introduction, Security.io may share limited contact details and a high-level request summary with a proposed independent specialist for the purpose of evaluating that introduction. Security.io may receive a disclosed referral fee if an introduction results in a commercial engagement. Referral consent is optional and does not affect editorial requests.
Retention and security
Security.io limits retention of contact submissions and related records according to operational, security, business and legal needs. Technical and organisational safeguards are used to reduce risk, but no internet-connected system can guarantee absolute security.
Privacy requests
Readers may use the protected contact form to ask questions about personal information handled by Security.io or to submit an applicable privacy request. Security.io will evaluate requests under the laws and circumstances that apply to the request.
Contact
Use the protected contact form for privacy requests, legal notices and questions about this policy. Select the privacy, legal or accessibility category.