Data protection approach
Guardian Wallet is designed with encryption, access controls, structured audit logs, and operational monitoring practices. We avoid claiming certifications unless they have been formally completed and verified.
Trust
Security
Guardian Wallet is designed to reduce exposure, isolate recurring payments, and keep sensitive account actions behind authentication.
Details
Built around real subscription control.
Each section keeps the same launch-site rhythm: concise, practical, and grounded in what Guardian Wallet actually supports.
Authentication and account security
customer dashboard access is protected by Clerk authentication and Guardian Wallet account security controls. Customers should never share passwords, one-time codes, or authenticator setup keys with support.
Payment isolation concept
supported subscriptions can use merchant-specific virtual cards so merchants do not freely charge your primary funding card.
Email alias privacy
supported subscriptions can use unique Guardian Wallet aliases that forward messages to the email address on your account.
What Guardian Wallet does not store
Guardian Wallet should not store CVVs, raw funding credentials, raw auth tokens, passwords, or unnecessary identity documents.
Support safety
do not send passwords, full card numbers, CVVs, one-time codes, raw bank credentials, or identity documents in support messages.
Responsible disclosure
security concerns can be reported to support@guardianwallet.ca with Security in the subject line.