ReviewSignal
Review your proposed service through serious buyer review.
New monitoring and reporting subscriptions are scoped individually. Review coverage, delivery examples, source limitations and permitted use before agreeing a proposal.
Buyer-ready means teams can inspect the whole delivery.
Inspect the sample files as delivery examples. Your proposal confirms the coverage and deliverables available for your request; historical data-license documents describe the existing file products.
Diligence pack
Product scope, source posture, security summary, operational dependencies, limitations, and the exact questions a data-sourcing team will ask.
Paid pack checklist
Required files, acceptance criteria, usage boundaries, and manifest precedence are documented for paid Early Access, Monthly, and Weekly packs.
Manifest-controlled delivery
coverage_manifest.json is the source of truth for row count, chain scope, freshness, backfill disclosure, and included files.
The diligence contract is about tier, delivery, and limits.
These are the items that should be clear before a buyer upgrades from sample inspection to a paid pack.
| Area | Diligence posture | Buyer evidence |
|---|---|---|
| Scope | Early Access, Monthly, or Weekly is selected before delivery. Chain and cadence limits are disclosed in the pack. | Stripe tier, data-room access state, and per-delivery manifest. |
| Files | CSV and JSON are standard. The current paid product is downloadable data-room files. | Sample files, data dictionary, and paid pack checklist. |
| Freshness | Monthly and weekly packs are ingest-window deltas. Manifests separate genuinely recent consumer activity from historical backfill. | fresh_this_period, ingested_at, latest event time, and event-freshness counts. |
| Security | Paid packs are not publicly browsable. Access is gated through authenticated data-room routes; payment is handled by Stripe. | Security summary, access notes, and production route smoke checks. |
| Rights | Internal use, no resale, no redistribution, no investment advice, no external model corpus without written permission. | Lite terms and paid pack checklist for the current self-serve tiers. |
| Non-claims | ReviewSignal does not claim predictive edge, guaranteed completeness, source-platform exclusivity, or buyer outcomes. | Methodology note, manifest caveats, and checklist limitations. |
Sample-to-paid path
- 1Buyer inspects the free sample and diligence docs.
- 2Buyer agrees a scoped paid pilot or subscription to evaluate the proposed deliverables.
- 3ReviewSignal delivers the matching data-room pack with manifest, methodology, and license files.
- 4The buyer accepts or cancels based on whether the manifest-governed delivery model is useful.
Security and compliance stance
ReviewSignal is not presenting a formal certification it does not have. The diligence pack gives a candid security baseline and the operational controls already implemented.
- APublic review data only; no private account scraping or hidden customer data in exports.
- BAuthor names are excluded from the v1 schema by default; optional text is sanitized where included.
- CSecrets and payment data are not exported; Stripe handles card processing.
- DDPA, security questionnaire, and vendor review answers are handled manually if a paid buyer needs them.
Send the material your buyer needs before they choose a paid tier.
Use this for data-sourcing review, vendor onboarding or legal review before agreeing your monitoring subscription. An independent example report is available before requesting a proposal.