Who to contact

This website is operated for the CyberCursor product project. For privacy requests, contact dewansh@cybercursor.com. A separately agreed deployment or customer contract may identify a different legal operator and data-processing scope.

Information you provide

The contact form collects your name, email, optional company and fleet range, topic and message. We use these details to review and respond to your enquiry. We rely on your enquiry consent to review and respond. The consent box records that permission; you may withdraw it by contacting the owner. Do not submit sensitive personal data or confidential endpoint records.

Storage and access

Requests are encrypted at rest on the project’s VPS in Amsterdam and accessible to authorised project administration. They are retained for up to 90 days in the intake system. Encrypted recovery copies may remain for a further 30 days before backup rotation. A continuing business relationship needs a separate retention scope. Contact the owner to request access, correction or deletion.

Website operation

Necessary connection information, such as IP address and request timing, is processed for website delivery and abuse prevention. Abuse prevention and reliable delivery serve our legitimate interest in operating the website. This website does not load advertising trackers, analytics cookies, external fonts or third-party media embeds. The authenticated portal uses separate essential session cookies.

Photography and product images

Editorial photographs are AI-generated illustrations. Product captures come from an owned test environment and do not represent customer data or production-scale deployments.

Service providers and your choices

The project uses Leaseweb hosting infrastructure. Contact requests are not sold or sent to an advertising platform or CRM. Providing them is voluntary and creates no contract; required form fields are needed to receive and answer your enquiry. We do not use them for automated eligibility decisions. You can request access, correction, erasure, restriction or portability where applicable, and raise a concern with your relevant data-protection authority.

Endpoint data is a separate scope

This notice does not authorise monitoring of someone’s device. A pilot requires agreed ownership, consent, collection, retention and deployment terms before endpoint data is processed.

Changes and requests

Updates will appear on this page with a revised date. Contact the project owner about this notice, withdrawal of enquiry consent or concerns about data handling.