Privacy policy

Controller and contact

SirenEdge is the controller for personal data collected through CyberSiren public pages and enquiry channels.

• Controller: SirenEdge (United Kingdom)
• General: [email protected]
• Security: [email protected]

What we collect on this website

• Website access logs and request metadata for security and reliability
• Contact details and message content you submit
• Pilot, partner, and security correspondence
• Basic anti-abuse form signals used to protect contact routes

Legal bases (website and enquiries)

• Legitimate interests: website security, reliability, and abuse prevention
• Legitimate interests: routing and responding to enquiries
• Pre-contract steps at your request: pilot or partner discussions
• Legal obligations where records or disclosures are required

How we use website and enquiry data

• Respond to enquiries and route requests to the right team
• Assess pilot, partner, and integration fit
• Operate and secure the website and contact channels
• Collect technical metadata for signup security and abuse prevention: approximate country, signup time and consent status. Your IP address is checked at signup to block abuse and is not stored
• Maintain reliability and investigate abuse or misuse
• Meet legal, compliance, and recordkeeping obligations

Service providers

We use a small number of carefully selected service providers for hosting, security and email delivery. They handle personal data only on our instructions and only for these purposes.

Product updates

If you sign up for product updates, we keep your email address, your name if you give it, and your consent. We use them only to send you updates about CyberSiren. We keep them until you unsubscribe or ask us to delete them, which you can do at any time by emailing [email protected].

Customer deployments and pilots

• This policy does not define customer deployment data handling
• Pilot and production handling is governed by contract and agreed scope
• Operational roles, approvals, and data responsibilities are defined per engagement

Typical retention periods

• Website security and delivery logs: up to 30 days (longer if needed for an incident)
• Technical signup metadata is retained for operational review and abuse prevention
• Enquiries and pilot/partner correspondence: up to 24 months from last material contact
• Contract and compliance records: as required by law or contract