OmnaSense Beta Program Terms
Effective Date: August 26, 2026
Last Updated: August 26, 2026
These Beta Program Terms (the "Beta Terms") apply to Customer's access to OmnaSense
features, services, or programs identified as alpha, beta, preview, pilot, early access,
evaluation, or pre-release (collectively, the "Beta Services"). Capitalized terms not defined
here have the meanings in the OmnaSense Terms of Service (the "Terms").
By joining or using the Beta Services, Customer agrees to these Beta Terms, the Terms, the
Acceptable Use Policy, and acknowledges the Privacy Policy. If these Beta Terms conflict
with the Terms about a beta-specific issue, these Beta Terms control.
1. Closed Beta Eligibility
The Beta Services are offered only to businesses and professionals approved by
OmnaSense. Users must be at least 18 and authorized to act for the participating business.
OmnaSense may accept or decline an application, limit workspaces or features, require an
approved business email, or revoke access at any time.
An invitation is personal to the invited organization and may not be sold, transferred, or
shared outside that organization without OmnaSense's written approval. Customer may invite
Authorized Users only through supported workspace functions and remains responsible for
them.
2. Beta Period and Cost
Unless the invitation states a different period, the beta period is 30 days beginning when
Customer's workspace is activated. OmnaSense may extend or shorten the period on notice.
The closed beta is provided without charge, requires no payment card, and does not
automatically convert to a paid plan. If OmnaSense later offers paid access, Customer will
receive the price and material billing terms and must affirmatively agree before being charged.
Beta participation does not guarantee a discount, continued free access, a production
release, or availability of any feature.
3. Purpose and Permitted Use
The Beta Services allow Customer to evaluate OmnaSense's outside-in website tracking and
marketing observability features. Depending on availability, Customer may create website
crawl monitors, record and replay test journeys, schedule checks, inspect browser-side and
server-side evidence, view screenshots and artifacts, and receive incident alerts.
Customer may use the Beta Services only for its internal business evaluation and authorized
client services. Customer may not resell or white-label beta access, use the Beta Services as
a managed service for an undisclosed third party, or represent that OmnaSense has certified
a website, analytics implementation, consent program, marketing platform, or legal
compliance.
4. Authorization for Every Target
Customer represents and warrants that it owns, controls, or has express authorization to
monitor every website, domain, application, account, endpoint, journey, tag manager,
server-side container, and marketing destination it submits. Authorization must cover the
configured scope, actions, frequency, accounts, integrations, and collection of evidence.
An agency or consultant monitoring a client site must maintain documented client
authorization and provide reasonable evidence of it if OmnaSense asks. Customer must
immediately stop a monitor if authorization expires, changes, or is disputed. Technical access,
a public URL, or possession of credentials does not by itself establish authorization.
5. Synthetic Traffic and Test Safety
Beta monitors act through automated browsers and server-side requests. They can generate
page views, analytics events, advertising-platform events, server logs, form submissions, and
other application behavior. Customer must:
• use dedicated test accounts and synthetic, non-sensitive data;
• avoid real purchases, donations, bookings, messages, account changes, or other
consequential transactions unless the target is expressly configured for safe testing;
• avoid recording production passwords, payment-card data, health information,
government identifiers, biometric information, or children's personal information;
• use narrowly scoped, revocable integration credentials;
• set reasonable schedules, crawl depth, page limits, and traffic rates; and
• confirm that alert recipients and connected accounts are authorized.
Customer is responsible for reversing or cleaning up test records and for the effect of
synthetic events on its reporting, audiences, attribution, billing, and downstream automations.
6. Pre-Release Nature
The Beta Services are incomplete and under active development. OmnaSense may add,
remove, rename, restrict, or redesign features; change data formats or evidence
classifications; reset or migrate beta data; impose usage limits; or suspend or discontinue the
Beta Services at any time.
Beta Services may contain defects and may experience interruptions, data loss, security
issues, inaccurate results, performance degradation, or incompatibilities. Documentation may
be incomplete or outdated. OmnaSense has no obligation to release a production version or
make a beta feature generally available.
Customer should not place data in the Beta Services unless it can tolerate loss or corruption
and should maintain independent copies of information it needs.
7. Evidence and Alert Limitations
Monitoring is evidence-based but not exhaustive. Results can be affected by browser
behavior, consent state, account permissions, network conditions, anti-bot controls, sampling,
target changes, provider APIs, provider retention, server-side routing, and other systems
outside OmnaSense's control.
The Beta Services may produce false positives, false negatives, incomplete screenshots,
missed pages, stale results, delayed or duplicate incidents, and delayed or failed alerts.
Server-side or marketing-destination evidence may be unavailable even when an event was
delivered. "Not confirmed" or a similar status means available evidence was insufficient and is
not proof of failure.
Customer must independently investigate important results. Customer may not rely on the
Beta Services as its sole method of validating analytics, advertising measurement, consent,
regulatory compliance, revenue, conversions, site availability, security, or any other
business-critical system.
8. Evidence, Screenshots, and Incidental Data
Evidence may include URLs, page content, event names and parameters, network metadata,
data-layer values, tag identifiers, screenshots, timestamps, server-side evidence, and hashes
of selected identifiers. OmnaSense is designed to limit unnecessary raw values and mask
obvious sensitive inputs where practical, but automated redaction cannot guarantee that
every personal, confidential, or sensitive value will be removed.
Customer must choose test routes, accounts, and data that are safe to capture. Customer
may not intentionally cause OmnaSense to collect sensitive or regulated data prohibited by
the Terms. Customer must promptly notify OmnaSense and delete or request deletion if it
discovers such information in an artifact.
9. Third-Party Systems
The Beta Services may depend on third-party sites, APIs, tag managers, analytics and
advertising services, server-side platforms, authentication, storage, and email delivery. Third
parties may change or withdraw access, impose limits, reject synthetic traffic, or return
incomplete data. Customer is responsible for complying with third-party terms and maintaining
valid authorization.
OmnaSense is not responsible for third-party outages, acts, omissions, fees, data, or access
decisions. Beta results may classify unavailable evidence as provider unavailable, not
confirmed, not configured, or another non-verification status.
10. Feedback and Beta Communications
Customer agrees that OmnaSense may contact Authorized Users about onboarding, service
operation, security, support, interviews, surveys, and beta feedback. Users may opt out of
non-essential research or marketing messages but may still receive transactional and
beta-administration messages while participating.
Customer grants OmnaSense the feedback rights stated in the Terms. OmnaSense may use
aggregated or de-identified beta metrics to analyze and improve the Services. OmnaSense
will not identify Customer in a public case study, testimonial, or logo list without permission.
11. Confidential Beta Information
Non-public Beta Services, documentation, roadmap details, security information, and
communications identified as confidential are OmnaSense Confidential Information under the
Terms. Customer will not disclose non-public vulnerabilities, access methods, screenshots of
restricted functionality, or benchmarking results without OmnaSense's written approval.
This Section does not prevent Customer from giving accurate information to a regulator or
law-enforcement authority, reporting a vulnerability privately to the in-product Help & support channel, or
making a disclosure protected by law. Customer should not include Customer Data or
third-party personal information in a public report.
12. Support and Service Levels
Beta support is provided on a reasonable-efforts basis through [SUPPORT CHANNEL OR
EMAIL]. OmnaSense does not promise a response or resolution time, uptime, availability,
recovery objective, service credit, or service-level agreement for the Beta Services.
OmnaSense may prioritize issues based on security, impact, reproducibility, and development
plans.
13. Security Responsibilities
OmnaSense uses safeguards designed for the nature of the Beta Services, but beta software
carries additional risk. Customer must use strong authentication practices, limit workspace
membership, use least-privilege test credentials, review artifacts, and promptly report
suspected compromise.
Customer may conduct security testing only with OmnaSense's prior written approval and
within the approved scope. Good-faith vulnerability reports should be sent to [SECURITY
EMAIL] with enough detail to reproduce the issue and without accessing, changing, or
retaining other customers' data.
14. Data During and After the Beta
The Privacy Policy explains OmnaSense's data practices. Customer controls Customer
Monitoring Data as described in the Terms. OmnaSense may impose or change beta
retention and storage limits on notice and may preserve evidence associated with an open
security, abuse, or operational incident for a reasonable period.
Customer should export needed reports and evidence before beta access ends. After
termination or expiration, OmnaSense may disable access and delete Customer Data after a
reasonable wind-down period, subject to an applicable DPA, backups, legal obligations,
security records, and unresolved disputes. OmnaSense does not promise migration of beta
configurations or history to a future version.
15. Suspension and Termination
Either party may end beta participation at any time. OmnaSense may immediately suspend a
monitor or account for unauthorized targets, excessive traffic, security risk, prohibited data,
unlawful activity, harm to a third party, or breach of the Agreement. Where practical and
lawful, OmnaSense will explain the reason and allow Customer to cure.
Upon termination, Customer must stop using the Beta Services and OmnaSense confidential
materials. Terms that by their nature should survive will survive, including confidentiality,
ownership, feedback, disclaimers, liability limits, and indemnity.
16. Beta Disclaimers and Liability
THE BETA SERVICES ARE PROVIDED "AS IS" AND "AS AVAILABLE" FOR TESTING AND
EVALUATION. TO THE MAXIMUM EXTENT PERMITTED BY LAW, OMNASENSE MAKES
NO WARRANTY THAT BETA SERVICES WILL BE RELEASED, UNINTERRUPTED,
SECURE, ACCURATE, COMPLETE, OR FREE OF DEFECTS, OR THAT DATA OR
CONFIGURATIONS WILL BE PRESERVED.
THE DISCLAIMERS, LIMITATIONS OF LIABILITY, EXCLUSIONS, AND INDEMNITY IN THE
TERMS APPLY FULLY TO THE BETA SERVICES. NOTHING IN THESE BETA TERMS
EXCLUDES RIGHTS OR LIABILITY THAT CANNOT LAWFULLY BE EXCLUDED.
17. Changes to These Beta Terms
OmnaSense may update these Beta Terms as the program changes. We will post the
updated version, update the date above, and provide reasonable notice of material changes
through the Services or by email. If Customer does not agree, its remedy is to stop using the
Beta Services before the change takes effect.
18. Contact
OmnaSense
Mailing address available through the in-product Help & support channel.
Beta support: the in-product Help & support channel
Legal: the in-product Help & support channel
Security: the in-product Help & support channel