SSecuTest
DatasetsPricingBlogAbout
Log InTry for Free

Data protection

Privacy Policy

How SecuTest processes personal data while keeping Customer Intelligence separate from proprietary Global Intelligence.

Effective: October 12, 2026Version: 2026-10-12-v6Audience, country and historic aggregation update: October 28, 2026B2B only

1. Controller

CYBER CLUSTER LLC, 1209 MOUNTAIN ROAD PL NE STE R Albuquerque, NM 87110, is the controller for the processing described in this policy. A Privacy request may be submitted through the contact form.

2. Scope

This policy covers public-site visitors, account users, subscription customers, Dataset purchasers, business contacts, support contacts, and personal data that may appear incidentally in Customer Intelligence, billing records or service logs. SecuTest is a B2B infrastructure-intelligence service focused on business domains and externally observable infrastructure.

3. Data we process

CategoryExamples
Account and workspace dataBusiness email, verification state, workspace ID, plan, settings, authentication metadata and account status.
Customer IntelligenceDomains submitted or scanned by a Customer, scan results, raw DNS evidence, notes, statuses, selected columns, bulk runs and exports.
Global IntelligenceBusiness domains, externally observable technical signals, normalized observations, provider classifications, confidence labels, freshness metadata, commercial opportunity classifications and historical infrastructure changes collected independently by SecuTest.
Dataset Marketplace dataSelected filters, quote ID, filter hash, matching count, price, pricing version, purchase ID, export size and cryptographic export hash, purchase status and delivery status.
Technical and security dataRequest IDs, session identifiers, timestamps, errors, rate-limit events, service logs, performance metadata and a keyed one-way network reference derived from a client network address rather than storing its raw value in marketplace rate-event tables.
Product analyticsAllowlisted product events (page category, source category, CTA, plan/cadence and product actions). Anonymous public events have no browser reference. With optional prior consent, first-party public events may carry a one-way pseudonymized random browser reference, used only to deduplicate unique-browser statistics; the raw identifier stays in a first-party browser cookie and is not saved in the analytics database. Authenticated application events use a separate one-way hashed workspace reference. These identifiers are not linked. The analytics store does not record IP addresses, email addresses, prospect domains, full referrer URLs, query strings, browser user-agent strings or form contents.
Billing and transaction dataStripe customer, Checkout Session, Payment Intent and subscription references, plan, amount, currency, status, billing address and tax data where supplied.
Legal-acceptance evidenceTerms, privacy and cookie-policy versions and cryptographic hashes, business-use confirmation, company, order and delivery metadata.
Contact dataName, business email, company, topic and message.

4. Customer Intelligence boundary

Customer-submitted domains, uploaded prospect files and Customer scan history are processed for that Customer's workspace. They are not injected into SecuTest Global Intelligence, the proprietary global dataset or historical collection. SecuTest sources Global Intelligence through its own collection infrastructure.

5. Purposes and legal bases

We process data to provide accounts, scans, prospect intelligence, dataset quotes, purchases, exports, subscriptions and support; perform billing and contract administration; confirm delivery; prevent abuse and fraud; maintain service reliability; measure product and funnel performance; meet legal obligations; exercise legal claims; and improve technology where allowed.

Depending on the processing and applicable law, the basis may be performance of a contract, legitimate interests, legal obligation or consent. Optional unique-browser measurement relies on prior consent. Anonymous aggregate page-event processing is separate, and authenticated product events use the necessary application account context.

6. Sources

We receive data from users, Stripe, Formspree, our hosting/security infrastructure and public internet services used for authorized operations and our proprietary infrastructure collection. Provider inferences based on MX, DNS, TLS, HTTP or email routing are bounded by externally observable evidence, not proof of a company's complete internal environment. Public MX/DNS evidence cannot by itself establish whether native platform security, API-integrated email-security products, post-delivery controls, internal filtering or unsupported providers are present.

Country-level geographic statistics

For website audience statistics, SecuTest can inspect the network IP address transiently on its own server to infer an approximate two-letter country code from a locally hosted GeoLite2 Country database. The country code, not the raw IP, is added to first-party marketing page-view analytics. Country assignment may be incorrect due to VPNs, proxies or corporate networks. Anonymous page views contribute to country-level page-view totals; unique visitors are counted only for opted-in browsers. Historical traffic is not assigned invented countries.

This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com. GeoLite2 is used for country estimation, not for identifying an individual or street address.

First-party campaign attribution

SecuTest counts aggregate marketing page views and on-page calls to action for campaign-tagged visits. When a visitor arrives through a URL with supported utm_source, utm_medium, utm_campaign and optional utm_content parameters, only restricted source/medium categories and validated short, non-personal campaign or message slugs may be recorded. The analytics system does not retain the complete incoming URL, arbitrary query strings, email addresses, advertising click IDs or individual campaign-recipient identifiers. Campaign statistics include public page views without an optional unique-browser cookie, but there is no non-consenting cross-page identity or individual signup attribution. Aggregated campaign counts may be retained long term; individual event records remain limited to the existing 90-day analytics retention. Campaign owners must never put a person's name, address or identifier into UTM tags. Measurement clarification: October 29, 2026.

7. Providers

ProviderPurpose
Stripe, Inc. and affiliatesSubscription and Dataset checkout, payment, fraud prevention, taxation and billing.
Formspree, Inc.Contact-form delivery and abuse prevention.
OVH SASWebsite, API and infrastructure hosting in France.
OVHcloudBackup and related data storage.
Bunny Fonts (BunnyWay d.o.o.)Public-site web-font delivery, not analytics.

8. Retention

Retention depends on data type, product behavior, security and statutory requirements.

Legacy free scan reportsUp to 30 days.
Legacy paid reports and generated filesUp to 365 days.
Anti-abuse eventsUp to 48 hours under legacy policy; marketplace controls have their own short rolling security windows.
Application and security logsUp to 90 days unless needed for an incident, fraud investigation or legal claim.
Product analytics eventsUp to 90 days. Consented pseudonymized browser references and anonymous public events are deleted according to the analytics retention policy.
Daily aggregate product analyticsLow-cardinality daily category totals (such as page category, source category, two-letter country and event type), without individual identifiers, raw IP addresses or request details, may be retained long term to support all-time operational and marketing statistics. These aggregate totals do not allow reconstruction of individual visits or lifetime unique visitors. Only events available when aggregation began can be backfilled; previously purged events cannot be recovered.
Optional browser analytics identifierUp to 180 days in the first-party cookie, unless deleted or consent is withdrawn earlier; its expiry is not refreshed on visits.
Contact submissionsUp to 24 months after the last relevant interaction.
Billing, invoice, tax, legal-acceptance, paid Dataset purchase and delivery-evidence recordsUp to 10 years or the applicable statutory period.
BackupsRolling copies up to 14 days under current policy.
Global Intelligence historyMay be retained long-term under applicable law and valid rights requests where personal data is involved.

Customer prospect data may be retained while the workspace is active and according to product controls. Statutory billing, security and evidence retention can survive account closure.

9. Rights

Depending on applicable law, individuals may request access, correction, deletion, restriction, portability or objection, and may withdraw consent for optional browser analytics without losing site functionality. Use the Analytics preferences control to change the choice prospectively and the contact form to exercise applicable rights. Withdrawal stops future identified analytics but does not automatically delete historical pseudonymized events; requests for deletion can be assessed separately. Individuals in France may lodge a complaint with the CNIL.

10. Public infrastructure data and rights requests

If a domain or observable infrastructure record is associated with a natural person and constitutes personal data, eligible people may submit a privacy request identifying the relevant record. Reasonable identity and eligibility verification may be required.

11. Automated infrastructure inference

SecuTest classifies external technical signals and may generate provider labels, confidence levels, Gap or Sell Next context. In particular, failure to observe a recognized MX gateway does not establish the absence of native, API-based, internal or otherwise non-visible protection. These business infrastructure outputs are not intended for automated decisions producing legal or similarly significant effects about natural persons.

12. Security

We use least-privilege access, transport encryption, signed payment webhooks, HMAC-based anti-abuse references, rate limiting, logging, data-boundary controls and backups. No system is completely secure. Report vulnerabilities under the security policy.

13. International processing

SecuTest is operated by a U.S. company with providers in different countries. Appropriate safeguards and transfer mechanisms are used where legally required.

14. Cookies and browser storage

Optional first-party visitor statistics use st_analytics_visitor and st_analytics_first_source only after consent. The cookie st_analytics_consent records the user's choice. Anonymous event counts continue without any dedicated analytics identifier. Necessary authentication/session, checkout, anti-abuse and preference technologies remain separate. See our Cookie Policy.

15. Changes and contact

We update this policy when processing changes, and identify versions and effective dates. Questions and rights requests may be sent using the contact form.

ContentsControllerDataCustomer boundaryProvidersRetentionRightsSecurityCookies
Privacy PolicyTerms & ConditionsCookie Policy