Disclosures
Clear product boundaries before a buyer connects revenue data.
Last updated: July 5, 2026
SIRJ is built for source-backed revenue attribution. These disclosures explain where attribution depends on connected sources, how AI-assisted answers are constrained, and what buyers should verify before relying on reports.
These disclosures summarize product boundaries. The Privacy Policy and Terms of Service remain the controlling public policies for personal data, subscriptions, acceptable use, and liability.
Attribution depends on connected source data
SIRJ can only compute attribution from the systems a customer connects and the records those systems make available. Missing ad, call, CRM, booking, invoice, or payment data can limit what a dashboard or report can prove.
- Unsupported metrics should stay hidden, flagged, or explained until the required source exists.
- Historical backfills depend on provider API access, selected resources, and available source history.
- Attribution windows, match confidence, and source freshness affect how complete a revenue story can be.
AI-assisted answers require source support
Ask Data and reporting copy are intended to summarize supported rows, not invent performance claims. When a question cannot be answered from connected data, the product should return an unsupported response or explain the missing evidence.
- AI-assisted answers should cite computed rows, date bounds, and metric context when the data supports the answer.
- Generated summaries are not a substitute for reviewing the underlying dashboard, report export, or source records.
- Customers are responsible for checking reports before using them in client, finance, or operating decisions.
Integrations depend on third-party providers
Connected providers control API availability, scopes, rate limits, field names, data history, and account permissions. SIRJ can surface setup and sync issues, but a third-party outage or permission change can affect reporting.
- A provider connection may require OAuth approval, API keys, webhook setup, pipeline mapping, or selected resource configuration.
- A disconnected, expired, or setup-incomplete integration should not be treated as a healthy data source.
- Integration pages describe imported objects and the buyer questions each source can support.
Pricing, billing, and cancellation
Public pricing reflects the plan information shown on the pricing page and the checkout flow at the time of signup. Taxes, annual billing, custom implementation, private connector work, and enterprise terms may vary by agreement.
- Public plans can be canceled through the billing portal, with access continuing through the current paid period.
- Enterprise agreements may include custom workspace volume, security review, retention terms, or implementation scope.
- Any guarantee, onboarding offer, or promotional term is limited to the written offer shown during signup or in the signed agreement.
Roadmap and beta language
Roadmap, beta, launch-track, or future integration language describes planned direction, not a purchase commitment. Availability can change as provider APIs, security reviews, customer demand, and implementation work evolve.
- Buyers should make purchase decisions based on available plan features and confirmed implementation scope.
- Private connector or custom workflow commitments belong in the customer agreement or implementation plan.
- Screenshots, demos, and sample data may illustrate product behavior without representing a customer's live account.
Privacy, security, and data handling
SIRJ uses account, integration, and reporting data to operate the service. Privacy, security, export, deletion, and tenant-scope details are covered in the dedicated trust and legal pages.
- Connected credentials and tokens should be stored encrypted and never shown back to users.
- Customer records should remain scoped to the active account and client workspace.
- Privacy, security, and terms pages provide the controlling public policy language.
Related trust pages
Disclosure FAQ
Does SIRJ guarantee every revenue number is complete?
No. SIRJ can only compute from connected sources and available records. The product makes unsupported or incomplete data visible instead of presenting it as complete proof.
Can AI-assisted answers be used without checking the data?
No. AI-assisted answers are meant to summarize supported rows and citations. Customers should review dashboards, exports, and source context before using reports for decisions.
Can provider API changes affect reporting?
Yes. Third-party providers control scopes, fields, rate limits, account permissions, and availability. SIRJ surfaces setup and sync issues when they affect reporting.
Where are privacy and legal terms handled?
Privacy, data handling, billing, acceptable use, and liability terms are covered in the Privacy Policy and Terms of Service. This disclosures page summarizes key product boundaries.