Security & Row-Level Security (RLS) Architecture
Enterprise-grade encryption, tenant isolation, and Google OAuth 2.0 API protection.
1. PostgreSQL Row-Level Security (RLS)
Uprise Tools utilizes native PostgreSQL Row-Level Security policies at the database engine layer. Every ad account, briefing setting, client onboarding record, and negative keyword mutation is scoped directly to your agency organization ID using strict session variables. Non-authorized database roles are physically prevented from reading or writing data across tenant boundaries.
2. Encryption Standard (AES-256-GCM & TLS 1.3)
All data transmitted between your browser, our Next.js edge servers, and the Google Ads API is protected using TLS 1.3 encryption. OAuth refresh tokens, integration secret keys, and client communication tokens are encrypted at rest using AES-256-GCM.
3. Google Ads API OAuth 2.0 Verification
Our integration operates via official Google Ads API OAuth 2.0 protocols. Your agency administrative credentials are never exposed or stored in plain text. You can inspect or revoke Uprise Tools' access at any time directly through your Google Account Security Dashboard.
4. Vulnerability Disclosure & Support
If you believe you have discovered a potential security vulnerability or have questions about our data safety infrastructure, please report it to our engineering team at alerts@uprisedigital.com.au.