A full-cohort source-check range is not summarized on this page. The dated package retains row-level source checks and historical publication limits. The package-check date records offline acceptance, not a source refresh.
100 reviewed FullStory company accounts. Evidence includes official subprocessor list or data-processing agreement; official policy or product handbook; official published pdf. Claims apply only to the recorded property, product or workload.
FullStory source composition | Source class | Count | Scope |
|---|
| Official subprocessor list or data-processing agreement | 48 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Official policy or product handbook | 42 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Official published PDF | 5 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
| Company-specific FullStory loader configuration in HTML | 5 | Reviewed public evidence within the recorded property or workload; execution and payment remain unverified. |
|---|
Contexts in the FullStory research: Qualitative property, workload, service-role or cohort-selection statement directly described by the accepted report; presence only, no prevalence claim. WhosBuilt review of the saved accepted report and approved examples; no source refresh.
Accepted report describes the retained list. Qualitative roles show presence, not prevalence. Counts refer only to the named recorded classifications; no source-by-context intersections are released. The displayed date is the package date. Source dates remain as recorded in the package; no source was refreshed for this analysis.
- Public sources do not verify paid subscriptions, organization-wide deployment or purchasing intent.
- Source retrieval dates record access; they do not make an older statement or historical deployment current.
- Published contact channels do not establish outreach permission, mailbox deliverability or purchasing authority.
- Supplier and historical disclosures retain their source and age limits; they are not proof of continued use.
- Published configuration does not establish browser execution or successful service operation.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.