Effective date: 10 June 2026
Operational security practices for SmartMaya product and public sites.
Reconciled sources
Interim status
This is an interim SmartMaya-specific update published on 10 June 2026 so our public notices match current product operations while preserving the customized WiselyWise policy details already published. It is pending formal legal review.
SmartMaya is a WiselyWise product owned and operated by WiselyWise Pte. Ltd., Singapore. These notices describe SmartMaya public sites and product services at smartmaya.ai and go.smartmaya.ai.
These notices are informational and do not create a compliance certification. Where we mention laws or frameworks, we mean that the product is being aligned operationally and contractually, not that a regulator or auditor has certified the service.
Existing WiselyWise WordPress policy pages last reviewed from the public site on 10 June 2026. Several pages show a prior update date of 25 March 2025.
Contact details preserved from WiselyWise
Data Protection Officer: Mr. Chandrakumar Natarajan, [email protected].
Postal address: WiselyWise Pte. Ltd., 28 Upper Serangoon View #15-33, Singapore 534207.
Policy and privacy contact email: [email protected].
Policy and privacy contact phone number: +65-94815474.
Current controls
Existing WiselyWise privacy language says technical, administrative, and physical security measures are used to protect information, while no internet transmission or security measure can be guaranteed as perfect. This position is preserved.
SmartMaya uses Supabase authentication, role-based admin restrictions, row-level security where implemented, rate limiting, security event logs, content safety checks, incident response procedures, and deployment validation gates.
Security is a shared responsibility. Customers must protect credentials, manage workspace members, configure integrations responsibly, and avoid uploading unnecessary sensitive data.
Incident handling
Security incidents are triaged by severity, with evidence preservation, containment, provider key rotation, user notification, and regulatory assessment as applicable.