Automation with control built in.
Berry OS is engineered from the ground up as a multi-tenant business operating system. We treat privacy, security, and human-in-the-loop governance as fundamental product requirements across our APIs, connected ad accounts, lead pipelines, and AI engines.
01 · OAuth 2.0 Authorization (No Shared Passwords)
Connecting advertising, analytics, and social accounts in Berry OS relies on standardized OAuth 2.0 protocols (such as Meta Login for Business and Google OAuth). Users never share account passwords. Access tokens are encrypted and stored securely server-side, with granular scopes restricted only to what is necessary for marketing operations.
02 · Strict Multi-Tenant Isolation
Berry OS enforces strict tenant separation at the schema and query levels. Workspace databases, lead pipelines, client retainers, and ad metrics are scoped to authenticated tenant IDs. Cross-tenant queries are blocked by architecture, ensuring zero risk of client data bleeding across agency accounts.
03 · Human-in-the-Loop Approval Gates
We believe automation should augment human operators, not act blindly. Critical or financial actions—such as modifying live Meta Ads budgets, publishing social content, or assigning high-tier sales leads—are staged in an Approval Queue. Connected APIs only execute when an authorized team member explicitly confirms the action.
04 · Role-Based Access Control (RBAC)
Granular team permissions allow workspace owners to assign roles (Agency Owner, Media Buyer, Strategist, Account Lead, or View-Only Client). Clients can inspect live dashboards and reports without gaining access to internal team billing, GST data, or media buying controls.
05 · Immutable Audit Logging
Berry OS maintains an immutable, tamper-resistant audit trail. Every automated recommendation, manual approval, rule trigger, and API execution is logged with exact UTC timestamp, user identity, IP address, and payload parameters. If a campaign budget is shifted, your team can inspect the exact before-and-after change record.
06 · Server-Side Credential & Secret Vaulting
AI model keys, payment gateway secrets (Razorpay/PayPal), SMTP credentials, and OAuth client secrets are safeguarded in server-side environment vaults. They are never rendered into browser HTML, bundled into client-side JavaScript, or exposed via public endpoints.
07 · Cryptographic Webhook Verification
Inbound events from Meta, WhatsApp Cloud API, and payment processors are verified using HMAC SHA-256 signatures before processing. Malformed, unauthenticated, or spoofed requests are rejected immediately with 401 Unauthorized.
Responsible Disclosure & Security Contact
If you discover a potential vulnerability or security concern, please contact our security team immediately at support@digitalberries.in. We review all responsible disclosures promptly.