Privacy policy

Privacy emailprivacy@stackhorde.com

This privacy policy explains how Stackhorde processes personal data when you use this website or contact us. It is written to be clear and practical; it does not replace legal advice for your specific situation.

What we collect: if you contact us (by email or via the contact form), we may process your name, work email, company, role, and the content of your message, plus any information you voluntarily provide.

Why we process it and legal basis: we use these details to respond to your inquiry, discuss a potential engagement, and maintain our business correspondence (legal basis: legitimate interests and/or steps prior to entering into a contract). If we become engaged, we process additional data as necessary to perform the contract and meet legal obligations.

No analytics and no advertising cookies: we do not use analytics, marketing cookies, cross-site tracking, or advertising pixels on this website. We also do not sell personal data.

Technical logs and security: like most websites, our hosting and infrastructure providers may process limited technical data (such as IP address, user agent, and request logs) for delivery, reliability, and security. We use such data only to protect the service, prevent abuse, and troubleshoot issues.

Retention: we keep inquiry and correspondence data only as long as necessary for the purpose described above, and longer where required for legal compliance or to defend legal claims. We apply reasonable retention periods and delete or anonymize data when it is no longer needed.

Your rights: depending on your location, you may have rights to access, rectify, erase, restrict processing, object, and data portability. To exercise your rights, contact us using the email below. We may need to verify your identity before responding.

International transfers: when we work globally, service delivery and infrastructure may involve processing outside the EEA. Where applicable, we rely on appropriate safeguards (such as contractual protections) consistent with GDPR requirements.

Last updated: May 2026