KICKHOST LEGAL
Information Security Policy
The principles, controls and responsibilities KickHost uses to protect our customers, our services and their data.
01Purpose and scope
This policy sets out how KickHost protects the confidentiality, integrity and availability of the information we handle, including customer data, our platforms, our staff systems and the services we provide.
It applies to our staff, contractors, suppliers and anyone who accesses KickHost systems or data. It supports the commitments in our Privacy Policy and Data Processing Addendum.
Security is a shared responsibility. We protect the platform; customers are responsible for their own applications, plugins, passwords, forms and email accounts.
02Governance and responsibilities
Security is led from the top. Management approves this policy, provides resources, reviews security risks regularly and is accountable for the security programme.
Every team member is responsible for following this policy and for reporting suspected security issues promptly. Access to sensitive systems is granted by role and reviewed periodically.
We maintain an asset inventory, classify information by sensitivity, and apply controls proportionate to the risk. We review risks when we change the platform, adopt a new supplier or enter a new market.
03Access control
Access to systems and data is limited to people who need it for their role. We use individual accounts, strong authentication, least-privilege permissions and prompt removal of access when someone changes role or leaves.
Administrative access to production systems is restricted, logged and reviewed. We avoid shared credentials and require a stronger authentication step for sensitive actions.
Customer account access is protected by authentication and session controls. We may require verification before making sensitive changes, and we never ask for your password by email or ticket.
Third parties receive access only for an agreed purpose, for a limited period, and under confidentiality and security obligations.
04Data protection and encryption
We encrypt data in transit using current TLS, and protect stored data with access controls and, where appropriate, encryption at rest.
Payment card details are handled by our payment providers in the secure checkout rather than stored on this website. We receive confirmation of payment, the amount, currency and a transaction reference.
Backups are protected with the same access controls as production data. Backups are tested and retained according to the service and legal requirements.
We minimise the data we collect and keep it only for as long as needed for the purpose described in our Privacy Policy, or as required by law.
Customers must not store highly sensitive data, such as full card numbers, private keys or special-category personal data, on a service that is not designed for it.
05Infrastructure and network security
Our services run on hardened platforms behind firewalls, with network segmentation and monitoring designed to limit the impact of a single issue.
We apply vendor security updates, track vulnerabilities and prioritise remediation by risk. Emergency patching may be carried out without prior notice where a threat requires it.
We use anti-abuse controls, rate limiting and filtering to protect the platform and our customers from spam, malware and denial-of-service activity.
Changes to production systems follow a controlled process with testing, review and rollback where appropriate.
Data-centre partners provide physical access controls, environmental protection and redundant power and connectivity.
06Monitoring and logging
We collect and review logs and alerts to detect and investigate suspicious activity, protect services and respond to incidents.
Logs are protected against tampering, retained only as long as they remain useful for security, troubleshooting and legal obligations, and access is restricted.
We monitor for unusual authentication, privilege changes, outbound abuse and signs of compromise. Alerts are triaged and investigated.
We do not routinely monitor the content of a customer’s website or email. We may inspect content where necessary to investigate abuse, respond to a legal requirement or protect the platform.
07Incident response
We maintain an incident response process to assess, contain, eradicate and recover from security incidents. The process covers roles, escalation, communication, evidence handling and post-incident review.
Where an incident affects personal data, we notify the relevant authority and affected customers as required by law, and we cooperate with their own notifications. Our Data Processing Addendum explains the processor notification commitment.
We may take protective action such as suspending a compromised account, resetting credentials, blocking traffic or isolating a system. We restore normal service as soon as it is safe.
After an incident we review what happened, update controls and share lessons where appropriate. We do not publish details that would put customers at risk.
08Backups and continuity
We keep backups of critical systems, test restores and maintain continuity arrangements designed to keep essential services running during disruption.
Backup coverage and retention depend on the service and are described in the service scope. A backup is a safeguard, not a complete archive of every change.
Customers remain responsible for keeping independent copies of critical data and for testing their own restore process.
We review business-continuity and disaster-recovery arrangements periodically and after a significant change.
09Supplier security
We assess the security and privacy posture of suppliers who handle data or support our services, and require them to protect information to a comparable standard.
Suppliers are bound by confidentiality and, where they process personal data, by data-processing terms. We review critical suppliers periodically and when the relationship or the risk changes.
Our Third-Party Code of Conduct sets out the wider standards we expect from partners.
10People and awareness
Staff receive security and data-protection guidance appropriate to their role, including onboarding, acceptable use, phishing awareness and incident reporting.
Access to sensitive information is subject to confidentiality obligations that continue after a person leaves.
We run background and reference checks where the role and the law allow it, and we apply the same principle of least privilege to contractors as to employees.
11Vulnerability management and testing
We track vulnerabilities in our platform and dependencies, prioritise them by exploitability and impact, and apply fixes within a risk-based timeframe.
We may test our own systems and commission independent testing. Testing is authorised, scoped and logged so that it does not affect customers.
External researchers should follow our Responsible Disclosure Policy. Unauthorised testing against customer services is not permitted.
12Review and contact
We review this policy at least annually and whenever a significant change affects our services, risks or legal obligations. The date at the top of this page shows the current version.
Security questions: use our contact page or email abuse@kickhost.com. Privacy and data-protection questions: privacy@kickhost.com.
This policy describes our programme and does not create a warranty beyond the commitments in your service agreement.
