Early-Access Terms · version 2026-08-13.v1
Controlled early-access product terms
These terms describe the intended Prismatics v2.0 early-access product boundary so the implementation, support process, and provider-review materials use the same language.
Early-access scope
The MVP is intended for a controlled cohort. The approved allowance is one user, one workspace, one client, and up to one authorised account/property for each supported source. The product may change during early access and unsupported enterprise or agency-scale workflows are outside this release.
Read-only product boundary
Prismatics analyses authorised data and can surface reviewable recommendations. It does not execute advertising or analytics changes and does not create, edit, pause, publish, or delete campaigns, budgets, targeting, ads, properties, or conversion definitions.
Source data and interpretation
Users remain responsible for choosing the correct source accounts/properties, business goals, reporting context, and conversion/outcome mappings. Prismatics labels source-reported, analytics-observed, unavailable, incomplete, stale, or suppressed information so unsupported conclusions are not presented as verified facts.
Recommendations
Recommendations are decision support, not automatic execution. They may include limitations, monitoring conditions, confidence/data-quality context, and reasons a recommendation is withheld. Users remain responsible for reviewing business context before acting outside Prismatics.
Availability and support
The controlled cohort does not receive a public uptime or response-time SLA. Prismatics uses an in-product status path and an actively monitored support contact before external early access. Verified incidents are communicated using the approved early-access incident process rather than speculative root-cause statements.
Disconnect and deletion
Users can disconnect supported sources. A confirmed account-deletion request stops source access and schedules product data deletion within 30 calendar days, subject to the minimal temporary security/audit retention described in the Privacy Policy.
Acceptable use
Do not attempt to bypass source permissions, access data you are not authorised to use, submit credentials through support channels, interfere with the service, or use Prismatics output to misrepresent source data or unsupported conclusions.
Release changes
Material privacy, terms, or connected-source data-use changes receive a new version and require renewed acknowledgement before a later source authorisation relies on them.