When you entrust your brand website to a platform for management, security is more than just a set of login credentials. Kanorio provides foundational protection across website connections, public-facing sites, accounts, and payment processes. Simultaneously, you still need to secure your Email or Google accounts, manage team permissions, and carefully select third-party services.
No service can guarantee zero risk, but understanding "what the platform handles" and "what you can do" can significantly mitigate the impact of common issues.
| What do you want to understand? | Recommended reading |
|---|---|
| What are the padlock icon, HTTPS, DDoS, or WAF? | How Your Website is Protected |
| How Kanorio handles visitor data, cookies, and third-party tracking | Visitor Privacy and Data Handling |
| How to prevent unauthorized account access | Account Security Guide |
| Are card numbers, store payouts, and refund processes secure? | Payment Security |
| What to do if you receive suspicious login emails, Google warnings, or discover a security issue | What to Do in a Security Incident |
This section explains the principles, protective measures, and handling procedures for platform and account security. It does not replace tutorials for website editing, domain settings, or payment processes; if you know the issue lies within a specific feature, prioritize going to the relevant section.
"Frequently Asked Questions & Contact" provides general troubleshooting, customer support, and content reporting entry points. This section focuses on unauthorized access, suspicious messages, visitor privacy, payment security, and public website protection. In case of a suspected security incident, please read What to Do in a Security Incident first.
Yes. All published Kanorio websites use the platform's basic edge protection. Feature benefits may vary by plan; please refer to the plan page for details.
The SOC 2 Type II, ISO 27001, and other certifications mentioned in this explanation refer to public certifications held by infrastructure service providers like Cloudflare, not necessarily Kanorio itself. For details, please read Visitor Privacy and Data Handling.
No. Kanorio automatically handles HTTPS and basic edge protection for published websites. If you are using a custom domain, you will still need to complete DNS settings as instructed; please read DNS Settings and FAQs.
The platform can mitigate many technical risks, but it cannot replace your responsibility for protecting login accounts, discerning suspicious messages, or deciding if a third-party service is trustworthy. A comprehensive approach involves both platform protection and diligent account management.