Secure transport
The public website is expected to run over HTTPS in production.
Security and privacy
Practical safeguards, with legal-review gaps called out.
This page states verified public practices and marks unverified security or privacy claims as Content required.
Public inquiry handling
Website inquiries are routed for human follow-up; they are not represented as automated approvals or regulated advice.
Security evidence
Content required: approved security-control summary, retention schedule, subprocessors, and incident contact process.
Current public practices
Use only verified statements
Public site metadata identifies info@ikanisa.com and WhatsApp +356 9971 1145 as intake routes.
The repository includes /.well-known/security.txt for vulnerability contact routing.
Client-facing packages are intended to remain human-reviewed before external use.
Sensitive or regulated claims require legal review before publication.
Content required
Security and privacy gaps for review
Content required: approved privacy notice refresh.
Content required: approved data retention and deletion schedule.
Content required: approved subprocessors and hosting summary.
Content required: approved incident response and vulnerability disclosure policy.
IKANISA prepares operational, administrative, analytical, and decision-support work. It does not issue licensed audit, legal, tax, assurance, investment, or regulatory opinions. External filing or submission requires human authorization.
Boundary
Professional boundary
IKANISA prepares operational, administrative, analytical, and decision-support work. It does not issue licensed audit, legal, tax, assurance, investment, or regulatory opinions. External filing or submission requires human authorization.
Next step
Need diligence evidence?
Use WhatsApp or email for RFP, procurement, vendor diligence, or accessibility questions. Missing facts stay marked as Content required until a human-approved source is available.
Request capability brief