THE DEDI
Security at THE DEDI
Last updated: 6 November 2026
THE DEDI uses account checks and server-side access controls to help protect merchant workspaces and their data. Security measures change as the service develops.
Account access
Product sign-in uses Google to authenticate a person. A Google identity alone does not grant access to a merchant workspace. Merchant access depends on an invitation or an existing merchant membership, and Founder access is separately checked.
Founder-sensitive access requires an enrolled, verified authenticator factor and a higher-assurance session. This requirement is separate from merchant sign-in.
Merchant data boundaries
The application checks merchant access on the server and uses database row-level security as an additional boundary for merchant-owned records. Browser-supplied business identifiers do not grant authorization.
Infrastructure and operations
THE DEDI uses hosted application and database services. Access to operational systems is restricted to authorized use. The public site is served over HTTPS.
We do not publish internal project identifiers, detailed access rules, key locations or recovery procedures on this page. A recent encrypted database recovery checkpoint passed an isolated restore rehearsal. Backup pruning is manual. This database recovery evidence does not describe Storage-object recovery or provider-controlled logs.
Questions or security concerns
Report a security concern to help@thededi.my. This is the confirmed support mailbox; its provider-side access and retention controls remain under review. Do not include passwords, authentication codes, keys or unnecessary customer information.