Technology & Security

Secure by design. Honest about what is actually implemented.

Security is a set of controls that must be configured, tested and maintained — not a badge placed on a website.

Website security

Layers we plan to protect.

Production controls will be implemented and verified before the website is treated as a live customer system.

✓ HTTPS / TLS

✓ Secure forms

✓ Rate limiting / anti-spam

✓ Security headers

✓ No exposed API keys

✓ Updates & backups

✓ Data minimisation

✓ Tested recovery

AI assistant security

The branded elephant assistant should use a secure backend/API endpoint. Provider secrets must never be embedded in frontend JavaScript.

Requests should be rate-limited, sensitive information should not be requested, and the assistant should have a clear human hand-off route.

Future client operations

WHMCS will sit behind the website — when the business model is ready.

WHMCS can eventually manage client accounts, products, invoices, recurring services, domains, hosting and selected automation. It should be introduced only after services, suppliers, pricing, payment and support processes are validated.

Website

Marketing, service information and lead generation.

WHMCS

Customer/service management and recurring operations.

Infrastructure

Hosting, domains, payment providers and support integrations.

Important: KagišoTech should not claim to provide specialist cybersecurity services merely because the website uses security controls. Security-minded delivery is part of good IT practice; specialist cybersecurity is a separate capability that can be developed later.