PlexWizz holds real operational data, conversations and payments. Isolation and ownership are enforced by the system — not promised in a paragraph.
Every query, every socket, every login is bound to its owner's world — enforced at the application and database layer.
Agencies and businesses grant their own connections — and revoke them at any time, independently of us.
Mail is read live from the owner’s mailbox — never stored beyond short-lived, self-clearing caches. Leaving means one-click export and complete erasure, guaranteed by database integrity rules.
Granular roles on both sides — agency staff and business teams — with immutable owners against lockouts.
Administrative actions are logged with who, what and when — reviewable and exportable.
Minimum scopes, encrypted credentials, and adherence to the Google API Services User Data Policy, including Limited Use.
Sovereignty isn't a slogan here — it's how the system is built. Each environment belongs to its owner, and the infrastructure stays invisible.
The business's world and the agency's world touch only where growth needs them to. On exit, either side takes its data and leaves nothing behind — export in one click, erasure guaranteed by database integrity rules.
Its leads, conversations, customers, bookings and payments — everything sensitive lives in the business's own portals, for its own team and its own customers. Mail lives in its own mailbox and is never stored by the platform.
Only what growth needs — performance, funnel and operational signals. Never the business's leads. Never sensitive data. Access is granted by each owner and can be revoked at any time, independently of us.
And the governing rule on top: changes to a business's accounts — budgets included — are proposed with evidence, and approved by the owner.
We adhere to the Google API Services User Data Policy, including its Limited Use requirements — see how access works and our Privacy Policy.
We describe the guarantees, not the blueprints — what matters is what the system enforces.