Opening proof path
SIRJ is loading the workspace, connector, or public page with the same proof path intact: ad spend, lead, booked job, invoice, paid.
Review SIRJ security, credential handling, tenant and client scope, data lineage, connector health, exports, deletion paths, privacy, terms, and disclosures in one procurement hub.
Buyer questions
The Trust Center is written for buyers who need to understand security, data lineage, product boundaries, and data exit paths before client reporting can move forward.
The Trust Center routes buyers to SIRJ security controls, data lineage, connector health, data routing, disclosures, privacy, terms, export paths, deletion behavior, and Enterprise rollout planning.
A reviewer does not have to assemble the trust story from disconnected pages before deciding whether client revenue data can enter the platform.
Open related pageSIRJ uses encrypted credential envelopes, tenant and client scope, role-scoped memberships, session claims, redaction, and request context checks before integrations, dashboards, reports, exports, or compliance jobs can use data.
Connected ad, CRM, booking, invoice, payment, and call data can support reporting without turning every user into an account-wide administrator.
Open related pageRevenue proof depends on connector health, normalized records, data routing, metric definitions, attribution methodology, Ask Data citations, weekly insights, and frozen report snapshots before a number is treated as client-ready.
Trust is not just storage security. The buyer can inspect how a claim moves from source records into dashboards, reports, and answers.
Open related pageExports and destinations explain PDF outputs, report history, scoped data packages, deletion and retention workflows, while privacy, terms, and disclosures explain public data-handling and product-boundary expectations.
A governed buyer can see how data leaves SIRJ, how deletion is scoped, and which product claims have explicit public limitations.
Open related pageTrust route map
Security, data lineage, connector health, metric support, exports, and public policies each answer a different procurement question. The Trust Center keeps those paths visible from one place.
Route map
A trust hub converts better when it does not force every concern into one vague security promise. Each row points to the deeper surface that explains the control or boundary.
| Area | Review question | Proof path |
|---|---|---|
| Security controls | How are credentials, tenant scope, client memberships, sessions, and audit records protected? | Security explains encrypted credential envelopes, redacted token material, role-aware access, tenant scope, audit records, and compliance workflows. |
| Account security | How do signup, login, Google access, password recovery, sessions, and invited access stay scoped? | Account security and recovery explains email and Google access, signed OAuth state, scoped sessions, password reset behavior, invite acceptance, and redacted auth responses. |
| Data lineage | Which public claims map to source records, validation paths, and user-visible reporting surfaces? | Data lineage maps route-level claims to the source paths, validation gates, and reporting surfaces that make those claims supportable. |
| Connector health | How does SIRJ show stale data, missing setup, reconnect needs, or provider failures before reporting? | Connector health exposes setup state, sync cadence, recent runs, reconnect needs, stale data, repeated failures, and severity before reports use a source. |
| Metric support | Which dashboard, Ask Data, weekly insight, and report numbers are defined before buyers rely on them? | Metric definitions explain ROAS, cost per lead, attributed revenue, campaign performance, source filters, unsupported states, and required evidence. |
| Exports and deletion | How can data leave the system, be retained, or be removed safely inside client scope? | Exports and destinations explain PDF report exports, report history, scoped tenant data packages, retention workflows, and destination boundaries. |
| Public policies | Where are customer-facing data, product, billing, privacy, and legal boundaries written down? | Disclosures, privacy, and terms name attribution limits, AI-assisted answer boundaries, integration dependencies, billing rules, privacy expectations, and customer responsibilities. |
Procurement checklist
These are the practical review lanes most likely to block adoption: credentials, client separation, report evidence, and data exit paths.
| Requirement | Reviewer sees | Proof path |
|---|---|---|
| Credential and source access review | A security route that explains encrypted credential envelopes, redaction, provider scope, connection context, and the difference between stored credentials and visible status. | Credential encryption and redaction are implemented in the security core and verified by security tests before connector routes expose credential state. |
| Client data separation review | Client workspace pages, security copy, and data lineage pages that explain account scope, client scope, memberships, viewer roles, and cross-client rejection. | Tenant, session, client access, dashboard, report, and compliance tests reject records outside the active account or client before output is returned. |
| Reporting evidence review | Metric definitions, attribution methodology, data routing, sample reports, and Ask Data routes that name the source path behind reported numbers. | Dashboard cards, Ask Data answers, weekly insights, and report snapshots rely on normalized records, supported metrics, citations, and report context. |
| Data exit and policy review | Exports, disclosures, privacy, and terms pages that explain report exports, scoped data packages, deletion workflows, retention boundaries, and legal responsibilities. | Compliance workflows use scoped table allowlists, child-first deletion order, retention jobs, audit records, and public disclosure pages. |
Review workflow
The route should help a buyer move from basic trust questions to a rollout plan without waiting for a private handoff to reveal the basics.
| Step | What happens | Visible proof |
|---|---|---|
| Start with the trust hub | A governed buyer starts at the Trust Center to see which security, data lineage, policy, export, and Enterprise pages answer the review questions. | The route acts as a single procurement map instead of making the buyer search footer links for every trust boundary. |
| Confirm access and credential controls | Security controls explain credential envelopes, redaction, tenant scope, session claims, client access, audit records, and compliance workflows. | The buyer can separate source connection status from raw provider secrets and understand how user roles limit account and client data. |
| Trace the reporting claim | Data lineage, data routing, metric definitions, attribution methodology, and sample reports explain which source records support dashboard and report claims. | The buyer can move from a public number to the route that explains source readiness, metric rules, match logic, and frozen report output. |
| Review data exit paths | Exports and destinations, privacy, terms, and disclosures explain PDF outputs, report history, scoped data packages, deletion workflows, retention, and product limits. | The buyer can review what leaves SIRJ and which public policy pages govern connected data before rollout. |
| Plan governed rollout | Enterprise rollout routes SSO planning, procurement review, private connector scope, custom retention, workspace rollout, and executive reporting to the right discussion. | Teams with security or finance review can see which rollout needs belong in Enterprise planning before connecting client data. |
Proof standards
The Trust Center stays useful by naming the failure modes it avoids: unsupported badges, hidden data-exit paths, vague claims, and client scope shortcuts.
The Trust Center points to implemented controls, public policies, route-level evidence, and product boundaries instead of claiming external certifications that are not present.
Exports, deletion, retention, privacy, terms, and disclosures are linked directly from the trust path and backed by compliance workflow tests.
Every Trust Center row carries a related route, source lineage, and a user-facing proof path before it appears in the public hub.
Trust Center copy routes client separation to tenant, session, client access, dashboard, report, and compliance checks that reject cross-scope rows.
FAQ
The FAQ keeps the hub honest: it routes deeper review instead of overstating certifications or hiding product boundaries.
No. The Trust Center is a procurement map. The security page gives the deeper explanation of credential envelopes, tenant scope, client access, audit records, compliance workflows, and source validation.
No. The Trust Center only routes to implemented controls, public policy pages, product disclosures, and source-backed evidence currently represented in the product and repository.
Start with the Trust Center, then review Security, Data lineage, Exports and destinations, Disclosures, Privacy, Terms, and Enterprise rollout before connecting client revenue data.
Use Data lineage first, then Data routing, Metric definitions, Attribution methodology, Connector health, Ask Data, and Sample report pages to inspect the source path behind a number.
Ready when the numbers need to hold up
Start with security controls, then trace the reporting claim through data lineage and export paths.