Encrypted when saved.
Saved provider credentials are encrypted. This is a specific statement about credential storage, not a blanket promise of encryption everywhere.
Trust / Clear by design
Your business data.
Handled deliberately.
A clear account of the safeguards that are implemented, the access that providers require, and the claims we don't make.
Implementation facts, not a certification claim.
Read our Privacy Policy and Terms.
Tenant separation.
Tenant separation is implemented to keep business workspaces distinct. This is an implementation fact, not a claim of independent security certification.
Provider calls stay server-side.
Calls to connected providers are made server-side. HTTPS is deployed. Connection scope and available data still depend on each provider's permissions.
Disconnect. Delete. Decide.
Disconnect and delete controls are implemented. Scoped, read-only TV sessions give shared screens a narrower purpose than your working dashboard.
Access / The boundaries matter
Connected with
the right permissions.
A provider adapter is the start of a connection—not proof that every account, credential, or sign-in flow is ready for every customer.
Your provider accountAccount permissions and source coverage
Server-side connectionEncrypted saved provider credentials
Your business viewTenant separation · HTTPS deployed
Not always one click.
Some sources need credentials. Others depend on OAuth configuration or specific account permissions. Some customer OAuth sign-ins require operator setup before they can be used.
Read provider access notesNot always the same access.
AI costs and usage may require organization, team, enterprise, or admin access. A personal account is not a substitute for the reporting permissions a source requires.
Read AI reporting distinctionsThe honest boundary
Useful safeguards. No borrowed credibility.
No SOC 2 or ISO certification, independent audit, SSO, SLA, audit log, or encryption-everywhere claim is made here. Pricing and checkout are unimplemented. Email verification and password reset are not configured. Clear expectations matter as much as a polished interface.
Questions, answered plainly
The details
worth asking.
Access, reporting, account controls, and the limits to know before you connect.
Are all 38 integrations available to every customer?
No. There are 38 implemented provider adapters, not 38 customer-accepted connections. Access depends on provider requirements, account permissions, and configuration. Some OAuth customer sign-ins require operator setup. Explore the catalog and access notes.
Does PixoDash show real-time data?
There is no universal real-time guarantee. Refresh timing and provider reporting delays vary. Source-specific freshness, connection errors, and manual sync help you understand the state of a connection; requesting a sync does not remove upstream reporting delays.
Can I track my personal ChatGPT or Claude subscription?
No personal subscription tracking is promised. OpenAI and Anthropic adapters report organization costs and usage with the appropriate access. Other AI sources report distinct measures such as balances, credits, quotas, or requests—not all eleven report dollar spend.
Is my TV wallboard a public share link?
No. TV wallboards are private, read-only views using scoped TV sessions. They are separate from regular dashboard access and should not be described as public dashboards.
Can I disconnect a source or delete it?
Disconnect and delete controls are implemented. Review the applicable controls in the dashboard. For retention and deletion questions, contact us. No independently verified deletion policy is claimed here.
Is PixoDash certified or independently audited?
PixoDash makes no SOC 2 or ISO certification claim and no third-party security audit claim. It also does not promise SSO, an SLA, audit logs, or encryption everywhere. The specific implemented safeguards are listed above.
Can I buy a plan here?
No. Pricing, checkout, and plan entitlements are not implemented. Access is by invitation during beta, with availability specific to each provider. Contact us about invited beta access and the sources you need.
Are email verification and password reset available?
Email verification and password reset are not configured. Contact us for account access questions; self-service recovery and verification flows are not available.
Where are Privacy and Terms?
Read our Privacy Policy for data-handling information and our Terms for use of the website and invited beta. This trust page describes implementation facts and access expectations. For legal or data-handling questions, email info@pixodash.com.
Why can store revenue and settlements differ?
They measure different events and may cover different reporting windows. Store sales, refunds, and net revenue are kept separate from payment settlements and AI spend. Multi-currency displays should be read with the disclosed FX context, not assumed to be directly comparable.
A clearer view.
Clearer expectations.
See the product story, with source context built in.