Privacy, from the start.
Understand what happens when you visit this website, contact us or connect a website to Relentless.
Draft for review · 10 September 2026. The website behaviour below describes the current homepage implementation. The product process describes requirements for service activation, not a claim that customer capture is already operating.
When you visit this website
The homepage does not include advertising trackers, analytics collection or session replay. Account sign-in is a separate, optional setup flow. Copying the installation instruction writes that text to your clipboard; it does not connect your agent, install software or submit website data to Relentless. Copy feedback stays in the page and resets when you reload.
The site is hosted on Render. Hosting infrastructure may process technical request information, such as IP address, requested URL, browser information and timestamps, to serve and secure the site. Hosting log fields and retention must be confirmed before this notice is final. Do not put secrets or personal information in page URLs.
When you sign in or add a website
Where account setup is enabled, you can use a configured sign-in provider or enter an email address to request a sign-in link. Supabase handles authentication; configured email delivery uses Resend. These services receive the information needed for that request. The setup screen does not receive provider access tokens or read the secure sign-in cookies.
The account service stores account identifiers, sign-in and revocation records, workspace membership and website addresses you register. Necessary secure cookies bind a sign-in attempt to this browser and keep you signed in. Adding a website does not install tracking code, verify consent or authorise visitor collection. The separate walkthrough uses example websites whose changes reset on reload.
This describes the account implementation prepared for review. Hosted account availability, final processing terms, retention and deletion arrangements must be confirmed before service activation.
When you contact us
The Contact link opens your email application. If you send a message, your email provider and the receiving email service handle your address, message and any attachments. We use correspondence to respond to your enquiry. Please do not email credentials, payment details or raw visitor data. Sending an enquiry is not permission to add you to marketing email.
How website capture is intended to work
- Agree the scope. Identify the website, authorised users, collection purpose and permitted data before enabling capture. An installation instruction alone does not establish visitor consent.
- Check consent and exclusions. Honour supported consent signals and exclude sensitive routes. Hold nonessential capture when the permitted collection state is unknown.
- Minimise before sending. Mask input values and sensitive content in the browser before transmission. Treat URLs, page text, attributes and errors as potentially sensitive. Validate incoming data again at ingestion.
- Restrict access. Keep evidence scoped to the correct site and workspace. Grant agents and optional integrations only the permissions needed for the authorised task. Do not create a cross-site identity graph.
- Limit retention and honour withdrawal. Define retention separately for events, replay, reports, account records, logs and backups. Stop future capture after consent withdrawal and apply the agreed deletion process to controlled copies and derived evidence.
The planned evidence includes page and interaction events, coarse browser context, masked page structure and experiment information. The initial collection proposal excludes raw form values, request bodies, console messages and stack traces. Privacy controls must be tested on the actual website; automatic detection is not infallible.
Your agent and other providers
Pasting an instruction into your coding agent shares it with that agent’s provider under its own terms. When service connections become available, the setup must explain which providers receive data, for what purpose and with which permissions. Repository connections are optional and are separate from account sign-in. This draft does not approve any additional provider, data transfer or marketing integration.
Retention and deletion
No final customer retention schedule is established in this draft. The engineering proposal for short-lived test evidence is not a promise about customer data or backups. Before service activation, the notice and agreement must state retention periods or clear criteria, deletion and export arrangements, and how restored backups are reconciled with deletion requests.
Questions and privacy requests
Contact hello@relentlessengine.com to ask about data handling or request access, correction or deletion. Depending on applicable law, you may also have rights to restriction, portability, objection and withdrawal of consent, and to complain to your data protection authority. We may need proportionate information to verify a request; do not send identity documents unless specifically requested through an agreed secure process.
Before this notice becomes final
The operator’s legal identity and address, applicable legal bases, hosting and email processing details, provider locations and transfer safeguards, retention schedule, controller and processor responsibilities, request handling and effective date still require confirmation. Any customer-data processing agreement and visitor-facing notice must reflect the actual released service. Material changes to this notice should be dated and communicated as required.