Terms without the guessing.

The formal terms

1. Who this agreement is with

These proposed terms govern access to Relentless, a service that helps website operators investigate website performance and prepare improvements. “Relentless”, “we” and “us” mean SENTRY AI LLC, a Florida limited liability company in the United States. Its registered company and approved public business and postal address is 7901 4th St N # 22469, St. Petersburg, FL 33702. “You” means the person or organisation entering the agreement through an authorised representative.

This version is a review draft and has no effective date. Visiting this page, copying an installation prompt, registering a website or viewing a demonstration does not constitute acceptance of this draft. Before contracting, we must provide the final terms and applicable order and processing documents, and obtain acceptance through a clearly identified process. No paid commitment arises from this draft.

The formal terms

2. Reading the terms together

The formal clauses set out the proposed contractual provisions. The adjacent explanations summarise those same provisions and do not introduce additional permissions, waive obligations or remove rights. Any apparent inconsistency must be resolved before acceptance; the explanations must not be used to misrepresent the agreement.

A final agreement must identify its incorporated documents and versions. A signed order governs its expressly agreed commercial particulars; a data processing agreement governs the processing it covers; these terms govern general service use. A privacy notice explains processing and rights but is not, by itself, permission to collect data. Mandatory legal rights apply notwithstanding any document.

The formal terms

3. What Relentless does

Within the features and limits expressly made available for your account, Relentless may receive permitted website measurements, organise evidence, identify potential issues, and produce recommendations or proposed changes for review. A demonstration, roadmap item or disabled control is not an available or purchased feature.

The service does not provide tax, legal, investment or other regulated professional advice. Findings depend on the available evidence, implementation, traffic and comparison method. Missing information is not evidence of success or failure. We do not guarantee a conversion increase, revenue amount, statistically conclusive result or particular time to improvement.

The formal terms

4. Initial evaluation and disabled features

The proposed initial evaluation is restricted to approved public pages and explicitly permitted measurements. Session replay and recording are excluded. A greyed-out replay control communicates unavailability and grants no recording permission. Any later replay offering requires a separate reviewed scope, verified safeguards, applicable notices and permissions, and express enablement; it must not activate automatically on an upgrade.

The installed integration may contain replay-capable code, but disabled replay must not collect or transmit snapshots or other data sufficient to reconstruct a session. The proposed control requires a current, authenticated per-site policy; missing or stale policy must leave replay off. Any later enablement requires both the account owner’s express authorisation and the site’s approved visitor-consent signal. Account creation, website verification, package download, installation, measurement activation and replay activation are distinct states. None implies completion of the next. Collection must remain disabled if the approved scope or required safeguards cannot be enforced. Synthetic testing and soft-launch status do not, by themselves, authorise collection from real visitors.

The formal terms

5. Accounts and authority

You must have authority to manage each connected website and to bind the organisation you represent. Website-control verification establishes the verified technical fact only; it does not establish ownership of all content, visitor consent or a lawful basis for processing.

You are responsible for accurate account information, authorised account use and protecting your credentials. Use separate, revocable permissions where supported and notify us promptly of suspected compromise through the designated support channel. Do not share session cookies, sign-in links, private credentials or another person’s account. We remain responsible for the security obligations applicable to our service.

The formal terms

6. Agents, recommendations and deployment

An installation prompt is an instruction for your chosen agent, operating under the permissions you grant that agent and its provider’s terms. Copying a prompt does not install software, establish visitor consent, grant repository access to Relentless or authorise deployment. A manual installation must meet the same verification and collection requirements. A site-specific installation instruction file may include public identifiers and a non-secret, expiring domain-control challenge, but must not include account credentials or reusable secrets. Preparing that file or a repository change does not prove deployment: website control must be verified against the issued path on the exact website origin.

Review generated recommendations, code and configuration for accuracy, suitability, security and compatibility. Deployment and experiments require the authority applicable to your website. Relentless must not treat a general improvement goal as unrestricted permission to publish changes, alter privacy controls, incur charges or expand collection. You retain responsibility for your approval decisions; this does not remove our responsibility for our own acts or service obligations.

The formal terms

7. Data that must not be collected

The initial evaluation must not collect, transmit to Relentless or store form contents or form-interaction data. This includes field values, selections, labels, validation messages, submission contents, uploaded files, focus and submission events, and identifiable activity within forms or editable regions. Masking, hashing or pseudonymising such material does not make it permitted under this scope.

Excluded information also includes tax or financial information, diagnostic answers and personalised results, identity or contact information entered by visitors, authentication credentials, payment details, health information, private documents and other protected or confidential material. Collection of raw page or DOM text, snapshots, session replay, URL query strings or fragments, request or response bodies, console or error contents, cookies, browser-storage contents and headers is outside the initial measurement scope.

Only expressly allowlisted event types, opaque approved page identifiers and permitted coarse technical measurements may be used. Sensitive, authenticated, personalised and user-input surfaces must be excluded by default. Do not send excluded information to agents, reports or support as a workaround. If exclusion cannot be demonstrated, collection must remain off. These restrictions define the required mode; this draft is not certification that a particular installation enforces it.

The formal terms

8. Visitor information and choice

Before enabling measurement, you and we must fulfil our respective obligations concerning purpose, lawful basis, transparency, storage or access technologies, and consent where required. You must provide an accurate website notice identifying the actual collection and recipients. Acceptance of these terms by a website operator does not constitute consent from its visitors.

Where the approved installation requires consent, unknown or denied consent must prevent collection and withdrawal must stop future collection promptly. Necessary account or security processing must not be described as optional measurement, nor used to justify unrelated measurement. You must identify the relevant audiences and regions and map the approved consent signal from your existing consent manager or equivalent mechanism. Relentless must not supply an additional banner or insert legal wording into your website without separate approval. Changes to purposes, event types or recipients require review and any further notice or permission required by law.

The formal terms

9. Data responsibilities and processing terms

The parties must document their actual data-protection roles for each purpose. Where you determine the purposes and means of visitor-data processing and Relentless processes solely on your behalf, an applicable data processing agreement must be executed before that processing begins. Separate processing for account administration or service security must be described in the relevant privacy notice and role assessment.

The processing agreement must specify its subject matter, duration, nature and purpose, data categories and data subjects, documented instructions, confidentiality, security measures, authorised subprocessors and change procedures, assistance with rights requests and incidents, assessment and audit support, international-transfer safeguards, and return or deletion at the end of services. It must identify actual recipients, locations and retention arrangements. No recipient or transfer is approved merely because it appears in a proposed architecture.

The proposed licence to process customer material is limited to supplying and securing the agreed service under those documented arrangements. It does not authorise sale of visitor data, cross-site identity profiling, unrelated advertising or training general-purpose models on customer or visitor material. Any proposed additional use requires separate review and an appropriate lawful arrangement; it cannot be inferred from silence.

The formal terms

10. Security and incidents

The final service and processing arrangements must define appropriate technical and organisational safeguards, including site and workspace separation, access restrictions, credential handling, secure transport and incident response. Neither party may represent controls, certifications or independent audits as completed without evidence. Security is a continuing obligation and not a guarantee that incidents can never occur.

On suspected unauthorised collection, access or disclosure, the affected processing must be assessed and contained. Each party must provide the assistance and notifications required by the applicable processing agreement and law; a processor must notify its controller of a personal-data breach without undue delay after becoming aware of it. Do not include raw visitor data or secrets in ordinary support correspondence. Incident channels and operational responsibilities must be confirmed before activation.

The formal terms

11. Retention, export and deletion

Before collection, agree a documented retention schedule for each relevant category, including measurement events, reports, account records, operational logs and backups. Indefinite retention must not be the default. Any legal-retention exception must identify its purpose, access restrictions and duration. This draft does not promise an unverified retention period or instant removal from backups.

The final processing arrangements must provide for authorised export and return or deletion on termination, including derived material and backup expiry, subject to applicable legal obligations. Disabling collection, disconnecting an agent and deleting retained data are separate operations. A deletion request must be confirmed through the agreed process, not inferred from uninstalling a script.

The formal terms

12. Other services and integrations

Optional agents, repository providers, authentication services and other integrations may operate under separate terms. The installation must identify the permissions and data flows involved. Authorisation for one integration does not authorise another. Disconnecting a provider may make dependent features unavailable.

Third-party dependencies may affect availability, but their involvement does not remove our obligations for providers we engage to perform the agreed service. Customer-appointed providers and Relentless-appointed subprocessors must be distinguished in the applicable documentation. Do not send private data to an external model or provider unless that recipient and purpose are authorised.

The formal terms

13. Ownership and permitted use

You and your licensors retain rights in your website, content and supplied data. Relentless and its licensors retain rights in the service software, documentation and branding. Subject to an effective agreement, your permission to use the service is limited to its agreed scope and duration. Third-party and open-source components remain subject to their applicable licences.

You must have the rights needed to supply material and permit the agreed processing. Any deliverable-specific intellectual-property terms must be stated in the applicable order; generated output may not be unique or free of third-party restrictions. Feedback does not give us permission to publish your name, brand, private data or results as a testimonial or case study.

The formal terms

14. Fair and authorised use

Do not use the service for unlawful surveillance, collection of excluded information, discrimination, deceptive interfaces, evasion of consent, unauthorised access or interference with others. Do not circumvent site boundaries, permissions, rate limits or security controls, introduce malicious code, or falsify measurement evidence.

Do not claim synthetic demonstrations, incomplete observations or unsupported comparisons as verified customer outcomes. Security testing of Relentless infrastructure requires an agreed scope, except where applicable law grants rights that cannot be restricted. Report suspected vulnerabilities through the designated security process without exposing third-party data.

The formal terms

15. Prices, subscriptions and cancellation

Any paid service requires an order stating the price and currency, applicable taxes, included usage, charging basis, billing period, renewal terms, cancellation method and applicable refund rights before acceptance. This draft creates no fee, minimum commitment, automatic renewal or right to charge a stored payment method.

An evaluation does not convert to a paid subscription without an expressly agreed arrangement. Additional usage charges and material price changes require the disclosure and agreement or notice required by the final order and applicable law. Cancellation must follow the disclosed process; mandatory cancellation and refund rights remain available. Any founding offer must identify its actual conditions and duration.

The formal terms

16. Service quality, suspension and exit

We must describe available functionality and material limitations accurately and perform the agreed service with the care and skill required by law and contract. Evaluation functionality may be incomplete or interrupted. No specific uptime commitment or support response time is created unless expressly agreed. Such limitations do not excuse obligations that cannot lawfully be excluded.

We may restrict affected access where reasonably necessary to contain a security threat, prevent unlawful processing or address a material breach. Restrictions should be proportionate. Where lawful and practicable, provide the reason, notice and a way to remedy the issue. Urgent containment may precede notice. A final agreement must define termination notice, remediation periods and continuity arrangements.

On termination, service access ends as agreed, while outstanding lawful payment obligations, confidentiality, applicable data return or deletion duties and provisions intended to survive continue. Removing website code, revoking provider access and ending retained-data processing must each be addressed in the exit process.

The formal terms

17. Responsibility and legal rights

Each party remains responsible for its own obligations, acts and omissions under applicable law and the effective agreement. The absence of a guaranteed business result does not remove duties concerning service performance, data protection, confidentiality or accurate representations.

Nothing in the proposed agreement excludes liability for fraud or fraudulent misrepresentation, death or personal injury caused by negligence where applicable law prohibits exclusion, or any other liability or remedy that cannot lawfully be limited. Mandatory consumer rights remain unaffected where they apply.

This draft sets no monetary liability cap, broad customer indemnity, forced arbitration requirement or class-action waiver. Any additional allocation of risk must be expressly drafted and reviewed for the actual service, parties and markets before acceptance. It must not be hidden in a plain-English summary or introduced retrospectively.

The formal terms

18. Changes, questions and disputes

Material changes to effective terms must be communicated in advance with their proposed effective date and any required acceptance or exit option. They must not retrospectively expand permission for data already collected. A new version of a webpage alone does not establish acceptance of materially different processing.

These proposed terms and contractual disputes arising from them are governed by the laws of Florida, United States, subject to applicable federal law and any mandatory protections that cannot lawfully be displaced, including consumer protections available where you live. This draft does not require exclusive proceedings in Florida or remove any right to bring proceedings in a court available under mandatory law. The final agreement must specify the formal notice and dispute-handling procedure before acceptance.

Questions about this draft may be directed to hello@relentlessengine.com. Before activation, confirm service and privacy contact channels, processing schedule, security and deletion commitments, and any order-specific terms. A lawyer may review the formal clauses and their explanations together. Legal review is not represented as completed by publication of this draft.