Your clients trust you with their data. Here's how we protect it.
Row-level security, dedicated databases, two-factor sign-in, and full data isolation — included from $99/mo. Not an enterprise add-on. Standard.
Built for multi-tenant deployments from day one. Your data stays in your chosen region. We never contact your end users or market to them.
- Isolated database per customer
- AES-256 at rest · TLS 1.2+ in transit
- Row-level security on every plan
- Two-factor sign-in on every plan
- US or EU region, no cross-region copies
- DPA, BAA and FERPA addendum available
The three things your clients will ask about
When you bring a BI platform into a client engagement, they want to know their data is isolated, your brand is the only one they see, and no one's mining their users. Here's the short answer to each.
"Can Client A see Client B's data?"
No. Data Tags filter every query automatically — each user sees only the rows that belong to them. Configured once, enforced on every report, every export, every scheduled email. You build one report, every client sees only their own.
How row-level security works →"Will my clients see DashboardFox branding?"
No. White-label is included in every plan. Custom domain, your logo, your colors, your email sender. Your clients see your product — not ours. We have no interest in marketing to the people using your dashboards.
White-label details →"Will DashboardFox contact our users?"
Never. We only communicate with account administrators for billing and product updates. Your clients' users — their data, their identities — stay entirely within your instance. We don't export, analyze, or reach out to them.
See our privacy promise →Follow your data from your database to your users
Five checkpoints, and what protects your data at each one.
Connect: your data stays where it is
We don't need a copy of your data to help you visualize it.
Direct database connections
For database connections, we query your data live — nothing is copied or stored in DashboardFox. We read it when you run a report, then it's gone.
Read-only by design
DashboardFox only reads your data — we have no functionality to write to your database. We still recommend read-only credentials as a best practice so both sides are covered.
Encryption in transit
TLS 1.2+ on all connections — to our platform, between services, and to your databases. No exceptions.
IP restrictions
Limit access to your instance to specific IP addresses or ranges. Combine with static egress IP to lock down traffic in both directions.
Secure credential storage
Database credentials, API keys, OAuth tokens, and uploaded driver files are stored in encrypted secrets management — never in plaintext, never in code.
Store: isolated and encrypted
Every customer gets their own database, encrypted and kept in the region you choose.
Dedicated customer databases
Every customer gets their own isolated database. No shared multi-tenant data pools — your data is never commingled with others.
Imported data stays isolated
When you use Excel uploads or API sources, that data is stored in your dedicated customer database — encrypted at rest and completely separate from every other customer.
Encryption at rest
All customer databases use AES-256 transparent data encryption (TDE). Backups are encrypted with AES-256 before leaving our servers.
Containerized isolation
Kubernetes-based architecture with customer isolation by design. Resources are separated at the infrastructure level.
US & EU data regions
Choose your data region at signup. Your data stays in that region for the life of your account — no cross-region replication.
Sign in: only the right people get in
A secure sign-in baseline is switched on for every plan, including Starter.
Control who can access your dashboards and how they authenticate. Every DashboardFox Cloud site starts with a secure sign-in baseline already switched on — on every plan, including Starter.
- Password security — 12-character minimum, screened against common and publicly breached passwords. Breach checks use k-anonymity, so passwords never leave your site
- Account lockout — Five failed sign-in attempts lock the account for five minutes. Administrators can unlock it at any time
- Two-factor authentication — Authenticator app, email code, or text message on every plan. Set it to Off, Optional, or Required, with backup codes and 30-day remembered devices
- Self-service recovery — Users reset a forgotten password or sign in with a one-time email link — no support ticket. Turn either off if everyone signs in through your own identity provider
- User controls — Invite users by email, disable or unlock accounts, force a password change, and reset a user's 2FA
- Service accounts — Mark integration, embedding, and Server Sync accounts so they skip 2FA and keep your automations running
- Cisco Duo, your own SMS provider, and header-based SSO — Duo push or passcode, text messages through your own Twilio account or SMS gateway, and sign-in through your own identity layer (Scale tier+)
- Session management — Tokens expire on inactivity; concurrent sessions automatically invalidate
- Public & shareable views — Share reports via direct link or enable a Guest View Library portal. Both are anonymous and view-only — no row-level security, no saved views
- IP restrictions — Limit access to specific IP addresses or ranges
- Audit trail — Every sign-in event and administrative action is recorded — password resets, link sign-ins, lockouts, 2FA enrollments and challenges, backup-code use, and admin resets
- Password security & breach screening
- Account lockout after 5 failed attempts
- 2FA available to every user (Optional mode)
- Password reset & email sign-in links
- Require 2FA for everyone, or keep it optional
- Authenticator app, email code, text message
- Invite, disable, unlock, force password change
- Service accounts for integrations
- Cisco Duo push & passcode
- Your own text-message provider
- Header-based SSO
See: every user sees only their rows
Row-level, field-level and role-based security, enforced on the server for every report, export and scheduled email.
Security at the data level
Row-level security, field-level security, role-based access control, and audit logs — all available from $99/mo. No plan upgrade required.
- Row-level security — Users see only their data, automatically filtered across every report
- Field-level security — Control which columns each audience sees by building tailored Apps (semantic layers). For Raw SQL and Stored Procedures, field access is managed within the query
- Role-based access control — Granular permissions on reports, dashboards, and data sources
- Audit logs — Track report execution, security events, and admin changes. Retention is tiered by plan. GDPR/compliance logging follows regulatory requirements regardless of plan
- Secure sharing — Share reports without exposing underlying data or credentials
One instance, many clients — each in their own lane
Serving multiple clients from a single DashboardFox instance? Data Tags create airtight isolation between tenants — no per-client database required. One report template, hundreds of clients, zero cross-contamination.
- Data Tags — Dynamically filter data so each user sees only their tenant's data, automatically applied to every report
- Security Policies — Define rules once, enforce everywhere across all reports and dashboards
- Dynamic data connections — Route users to different databases, schemas, or credentials based on who's logged in (Enterprise tier)
- One report, many tenants — Build once, serve hundreds of clients — each seeing only their own data
Prove: we'll pass your security review
No SOC 2 report yet, and we'll say so up front. Here's what we have instead.
We pass customer security assessments
- We've passed enterprise security reviews, including a healthcare organization running PHI on DashboardFox under a signed BAA.
- Questionnaires are completed by the engineers who run the service, not a sales rep reading from a deck.
- Government, healthcare, finance, and compliance-sensitive teams often need more than a webpage. If you're evaluating vendors against a formal checklist — data handling, subprocessors, breach notification, audit procedures — talk to us directly. We'll go through it line by line.
Everything a vendor security questionnaire asks, answered in the order reviewers ask it
- Service and deployment model
- Hosting and sub-processors
- How customer data is handled
- Encryption and secrets
- Workforce access
- Authentication and authorization in the product
- Logging, monitoring, and audit
- Security testing and vulnerability management
- Change management and secure development
- Incident response and breach notification
- Business continuity and disaster recovery
- Physical and endpoint security
- Compliance and insurance
- Documents available on request
What we have today
Testing
- Continuous automated penetration testing by an independent third party, plus quarterly external vulnerability scans by a PCI Approved Scanning Vendor
- PCI DSS — validated annually by self-assessment (SAQ A-EP), with quarterly external vulnerability scans by an Approved Scanning Vendor. We never store payment card data
Agreements
- HIPAA-ready infrastructure — BAA available on any plan with the Compliance Tier
- FERPA-ready — education data addendum available on request
- GDPR-ready DPA available now
- CCPA/CPRA compliant data handling
Controls
- Full audit trails on all administrative actions
- Two-factor sign-in, breached-password screening, and account lockout on every plan
- Dedicated DB per customer
- Right to deletion and data export support
- 30-day data retention after account closure
Insurance & transparency
- Cyber liability insurance coverage
- Public status page with real-time system status and incident updates
A straight answer on SOC 2
We don't have a SOC 2 report today. SOC 2 Type II and ISO 27001 are on our roadmap. SOC 2 Type II requires 6–12 months of audited operational evidence; until we complete it, we answer your questionnaire directly, walk your team through our architecture and controls, and share supporting documents under NDA where appropriate.
Row-level security is typically an enterprise upgrade. Not here.
Most BI tools lock row-level security and audit logs behind expensive tiers. We include them in every plan — because security shouldn't be a selling point for an upgrade. See how to set up row-level security in the Academy →
- Row-level security (Data Tags)
- Field-level security
- Audit logs
- Dedicated isolated database
- White-label included
- Multi-tenant support
- Row-level security (Pro only)
- Audit logs (Pro only)
- White-label (separate add-on)
- Shared infrastructure (cloud)
- Dedicated database per customer
- Multi-tenant (complex setup)
- RLS: DAX roles in Power BI; centralized policies need Tableau Enterprise
- Per-seat pricing (idle users count)
- White-label (not available)
- Dedicated database per customer
- Multi-tenant agency model
- MAU pricing
We don't market to your clients. Ever.
Your end users see your brand, not ours. Their data stays in your instance. We never export, analyze, or market to the people using your dashboards — they may not even know DashboardFox exists. We only communicate with account administrators for billing and product updates, and you can opt out of those anytime.
Where it runs
- Shared CloudYour own isolated database on our servers, US or EU. HIPAA BAA on any plan with the Compliance Tier.
- Enterprise Dedicated CloudA server and database of your own, managed by us.
- Self-HostedDashboardFox can run entirely on your own servers — Windows, Linux, or Docker. Air-gapped capable. One-time license from $4,995.
AI, secured by design
AI features are on our roadmap, and we're building them the way we build everything else — security first. When they arrive, they'll operate inside your existing row-level and field-level security, enforced by the platform rather than trusted to a model. And because they'll be grounded in the semantic layer you define, they're designed to answer from your real fields and joins — not to guess. As noted in the FAQ below, we don't use your data to train models, and that won't change.
Security FAQs
