Encryption in transit and at rest, strict workspace isolation, role-based access for your team, and a real human on the other end of contact@vividsphere.co. The boring stuff, done right — across PrimeBase and Pocket CRM.
Short list. No marketing fluff. Every line below describes something running in production today, not a roadmap.
TLS 1.3 in transit. AES-256 at rest on Google Cloud Platform with envelope encryption managed by the cloud provider.
Every record carries a workspace ID. Postgres row-level security enforces it on every read and write — not in app code, in the database.
Custom roles, granular permissions, and access rules. Your admins decide who can see and do what inside the workspace.
If a security incident affects your data, we tell you — directly, by email, with what happened and what to do.
Defense-in-depth, designed so a failure at any single layer doesn't compromise the whole. Here's what each layer looks like in production today.
Every record in PrimeBase carries who created it, who last updated it, and when — across CRM, projects, accounting, documents, and inventory. Customer-facing activity flows into a dedicated feed for sales and field work.
Created-by and updated-by tracked on every record across modules.
Customer activity feed for visits, calls, notes, and route stops.
Workspace-scoped — activity is isolated to your tenant by row-level security.
CSV export of customers and inventory batches is self-serve for admins.
Authentication events (sign-in, OTP requests, integration connect/disconnect) are recorded per-workspace.
Our products are hosted on Google Cloud Platform in the United States. Your workspace data is encrypted at rest, backed up daily, and isolated from every other customer by row-level security.
Compute, storage, and managed Postgres run on GCP in the United States.
Encryption at rest on every layer; Postgres row-level security enforces workspace isolation.
Rolling encrypted backups handled by Google Cloud. Point-in-time recovery configured at the database layer.
Operated by VividSphere LLP, Bangalore. Administrative access from India; production data resides in the US.
Have a hosting question? Email contact@vividsphere.co and a real engineer will answer — backup details, retention, or anything else your security team needs to know.
A real engineer reads contact@vividsphere.co. If a security incident affects your workspace, we tell you directly — what happened, what to check on your side, and what we're doing to fix it.
Platform alerts and customer reports surface anomalies to our engineering team.
On receipt, an engineer triages scope: which workspaces, which data, what the suspected cause is.
If confirmed, affected services are isolated and suspect sessions or credentials are revoked.
If your workspace data is impacted, we email your admin(s) directly — what happened, what to check, what we're doing.
Root cause fixed in production. We write up what changed and what to watch for, and share it with affected customers.
Researchers acting in good faith are welcome — we'll acknowledge your finding, work with you on the fix, and credit you publicly if you'd like. We don't yet run a paid bounty program.
Security isn't a feature you ship — it's the floor you keep raising. We build like we're the customer.
Most "security" pages list what the vendor does. Here's what you get to do, the moment you sign up.
Build custom roles. Grant per-module, per-action access — restrict who can see and do what in your workspace.
Scope users (or roles) to their own records, assigned records, or specific tags — per module. Set by your admins.
Sign in with a one-time code sent to email — no shared password to phish. Password-based login is also available for users who prefer it.
Admins can export customers and inventory batches as CSV without a support ticket. More entities are on the roadmap.
Every record carries a workspace ID. Postgres row-level security blocks cross-tenant access at the database layer.
Workspace admins can close their workspace from in-product settings. Data deletion completes within 30 days; we confirm by email.
If you don't see yours, email contact@vividsphere.co — a real engineer replies.
Send your security questionnaire or ask anything about how we handle your data. A real engineer reads contact@vividsphere.co — no sales rep in the middle.