Skip to content

Security questions, answered

This page explains, in plain terms, where attribution data lives, what account information is kept, how payments are handled, and how releases are tested.

Use it to distinguish browser-side attribution from server-side storage before you install the script.

Visitor data stays in the browser

The key distinction is location. A small JavaScript snippet runs on your own site. On arrival, it works out the likely source channel, such as paid or organic search, and saves that attribution result in a first-party cookie in the visitor's browser. When a form appears, the snippet finds fields by name, ID or default value and copies the attribution result into hidden fields. On submission, your form tool receives those values and can pass them onward to a CRM or other tools. At no stage does visitor attribution data reach the provider's servers.

What is stored about your organisation

Account creation captures only the creator's first name, last name, email address and company name. That limited set is the whole account-data list described here. Card processing and billing are handled through Stripe, described as PCI-certified, with card numbers encrypted at rest using AES-256.

Testing and certifications: what is not claimed

There is no penetration testing and no ISO 27001 or SOC 2 certification. The rationale given is that commercially confidential information about customers, organisations or their customers is not stored, so those measures are treated as lower priority. If your own compliance review requires independent testing evidence or a named certification, treat that as an open procurement question rather than something this page can satisfy.

Release cadence

Updates are shipped regularly. During 2025, a new version went out more than once per month, combining feature work, support for more form builders and tools, and adjustments for changes in browsers, operating systems and device technology.

How accuracy is checked before release

Development, testing and production are kept separate. Changes are developed and lightly checked first, then moved to testing, where more than 1,500 manual and automated checks run. Those checks vary UTM parameters and organic channels across devices, browsers and operating systems, and cover each supported form tool. Only a release that passes moves to production. Regular production checks are also run so browser or platform changes that could affect recorded data are spotted early. Before installing, confirm that your form fields use the names, IDs or default values the snippet expects, and verify the hidden fields appear correctly in a test submission.

Pre-install checklist

Checklist: 1) Confirm attribution is browser-side and cookie-based. 2) Confirm only basic account details are stored. 3) Confirm card handling sits with Stripe. 4) Note the absence of penetration testing and ISO/SOC certifications. 5) Confirm your form fields match the expected identifiers. 6) Run a test submission and inspect the hidden fields before relying on the data in your CRM.

Frequently asked questions

Does the tool collect or store visitor, lead or customer information?

No. Attribution is calculated in the visitor's browser, saved in a first-party cookie there, and then written into hidden form fields. It is not sent to or stored on the provider's servers.

What company or employee information is stored?

Only basic account details for the person who created the account: first name, last name, email address and company name. Payment card handling is delegated to Stripe.

Is the application penetration tested or certified?

No penetration testing is performed, and no ISO 27001 or SOC 2 certification is held. The stated reason is that commercially confidential customer data is not stored.

How often are updates released?

Releases occur regularly, more than once a month during 2025. Changes cover new features, additional form builders and tools, and adaptation to browser, operating-system and device changes.

How is attribution accuracy tested?

Work moves through development, testing and production environments. Before production, more than 1,500 manual and automated checks cover UTM combinations, organic channels, devices, browsers, operating systems and supported form tools. Production is also tested regularly for external changes.

How can I ask another security question?

For any further security question, use the contact page linked from this site and describe what you need to know, such as how a specific form tool handles hidden fields or what your own compliance review would require. If you are evaluating the tool before installing it, it also helps to mention your form builder and the fields you plan to capture so the reply can be specific.