Privacy Policy: How a Browser-Based Attribution Tool Handles Personal Data
This page explains, in practical terms, what personal information is collected when someone visits the provider's marketing site, what is collected when someone becomes a customer, and — most importantly — what is not collected about visitors to a customer's website.
Use the checklist below to identify which situation applies to you before contacting anyone.
Who we are and how to use this policy
This policy describes the kinds of personal information that may be handled when you browse this marketing site or open a customer account, and it explains why visitors to a customer's own website are outside that scope. The operator's legal name, registration number, postal address, privacy contact, and the date of the latest revision are recorded in the site's policy register and should be inserted here before publication; until those details are confirmed, treat this page as a framework rather than a final notice. Questions about the policy can be directed to the privacy contact listed in that register. To find the part that applies to you, start with the situation that matches yours: browsing this marketing site (see the visitors section), holding a customer account (see the customers section), visiting a third-party site that runs the attribution script (the operator of that site, not this provider, controls the data and should be contacted directly), or asking for access, correction, deletion, objection, or portability in respect of information the provider itself holds (use the privacy contact and the response period set out under your rights).
How the tool works — and what it does not collect
The product is a JavaScript tool installed on a customer's own website. When a visitor arrives, the script runs in that visitor's browser to identify the marketing channel they came from — for example Paid Search, Organic Search, or Referral — and stores that result in a first-party cookie on the customer's domain.
When the visitor submits a form, the script places the attribution result into hidden form fields. The customer's own form tool, such as Webflow, HubSpot, or Gravity Forms, captures the submission and sends it to the customer's chosen destination.
The key distinction is architectural: the product operates no servers that receive end-user data. Information about website visitors or form submissions does not reach the provider's infrastructure. Processing happens in the visitor's browser and inside the customer's own systems.
In practical terms:
- The provider does not collect, store, or process information about visitors to customers' websites.
- The provider does not see or store form submissions made on customers' websites.
- The provider has no access to customers' leads, contacts, or form data.
- The provider is not a data processor for end-user data; it supplies software that runs in the visitor's browser.
Example: a visitor arrives from Paid Search, the script records that channel in a cookie on the customer's domain, and on form submission the channel is written into a hidden field. The customer's form tool then delivers the completed form to the customer's destination. At no point does that visitor data pass through the provider.
What data is collected
Data is collected in only two contexts.
Visitors to the provider's website may provide or generate:
- IP address and approximate, city-level location
- Browser type, device type, and operating system
- Pages viewed and referrer URL
- Information submitted through site forms, such as name, email, company, and message
Customers who sign up for an account provide:
- Name and email address
- Password, stored hashed rather than in plain text
- Company name and website domain
- Billing information processed by Stripe; card numbers are not stored by the provider
- Account configuration settings
- Support communications, including emails and chat messages
How data is used
Website-visitor data is used to operate and improve the provider's website, respond to enquiries, measure marketing performance, and prevent fraud and abuse.
Customer data is used to provide the service, process billing and manage subscriptions, communicate about the account, provide support, and improve and develop the product.
Personal data is not sold, and is not used for targeted advertising outside measuring the performance of the provider's own marketing campaigns.
Who data is shared with
Service providers receive only the data necessary to perform their services:
- Stripe for payment processing
- Email providers for transactional and support emails
- Hosting providers for serving the website and the JavaScript
Data may also be disclosed where required by law, court order, or government request, or to protect rights and the safety of others. If the business is acquired, merged, or sold, customer data may transfer to the acquiring party, with advance notice to customers.
End-user data is not shared because it is not collected or stored by the provider in the first place. Visitor data stays in the visitor's browser and in the customer's own systems, and the product sends no visitor data to any third party.
Your rights
Data-protection law in your jurisdiction may give you the ability to see a copy of the personal information held about you, have errors corrected, ask for erasure, object to certain processing, or obtain your information in a portable format. Requests go to the privacy contact published in the site's policy register, and the applicable response period is the one recorded there; where no period has been fixed, the statutory deadline for the relevant jurisdiction applies. If your request concerns a website that runs the attribution script, the operator of that website is the right recipient, since that operator, not the software provider, decides what is collected through the site.
Security, transfers, cookies, children, changes, and contact
Safeguards described in this policy include encrypting information while it travels over HTTPS and while it is stored, keeping passwords only in hashed form, restricting staff access to customer records, reviewing security arrangements periodically, and leaving card details with Stripe, which handles them under PCI rules, rather than holding them internally. No system can be guaranteed completely secure; where a breach affecting you comes to light, notice will be given to you and to the competent authorities to the extent the law requires. Some suppliers, including Google, Stripe, and certain hosting companies, process information in the United States and other countries, so using the service from elsewhere can involve a cross-border transfer; appropriate safeguards are meant to keep those transfers consistent with applicable data-protection law. On this marketing site, essential cookies support sign-in and core functionality, and Stripe sets payment cookies for fraud checks at checkout; browser settings let you block cookies, though blocking the essential ones can impair parts of the site. The attribution cookie you may encounter on a customer's website is a different thing: it is first-party to that customer's domain, holds attribution data for that site alone, and is not readable by the provider. The service is aimed at adults and is not intended for children under 13, or under 16 in the European Economic Area, and information from children is not knowingly gathered; if you think a child's information has been collected, write to the privacy contact and it will be removed. This policy may be revised from time to time; material changes will be announced to customers by email and reflected in the revision date shown at the top, and continuing to use the service after a revision means you accept the updated version. Contact details, including the privacy email and postal address, are kept in the site's policy register.
Frequently asked questions
Does the attribution script send visitor data to the provider?
No. The script runs in the visitor's browser, stores attribution in a first-party cookie on the customer's domain, and writes it into hidden form fields. The customer's own form tool then captures and sends it within the customer's systems. Nothing about that visitor or submission reaches the provider's servers.
I visited a website that uses this kind of script and want my data deleted. Who do I contact?
Contact the website operator directly. That operator is the data controller for information collected through their website, not the software provider.
How do I exercise my data rights?
Send your request to the privacy contact published in the site's policy register, stating whether you want access, correction, deletion, objection, or portability. The response period is the one recorded alongside that contact; if none has been fixed, the statutory deadline for your jurisdiction applies.
What cookies are used on the provider's own website?
Essential cookies support authentication and basic functionality, and payment cookies support fraud detection during checkout through the payment processor. Disabling essential cookies may break parts of the site. The attribution cookie seen on customer websites is separate: it is set on the customer's domain and is not accessible to the provider.