Clear, limited and consent-based.

Cookie choices

Necessary storage remembers your consent choice. Anonymous analytics are disabled until you accept them. You can reject them and continue using Seek normally.

What analytics collect

With consent: page paths, CTA clicks, scroll milestones, form start and submission events, referrer domain, UTM campaign fields, device category, viewport width and approximate session duration.

What analytics never collect

Seek does not store field contents, passwords, keystrokes, session video or IP addresses in its analytics records. Form submissions are stored separately because you explicitly send them.

What happens to a form submission

When you send the Early Access or contact form, Seek stores what you typed — your name, email address, product URL and the product context you wrote — in its own database, and the team reads it from an internal inbox. Your email address is added to Seek's contact list, which is what makes replies, preference changes and unsubscribes possible. Two emails leave immediately: a confirmation to you and a notification to the Seek team. Your IP address is read only to rate-limit the form and is never written next to your submission.

100 SaaS challenge submissions

When you submit a SaaS URL to the 100 SaaS challenge, Seek stores the URL, optional ideal-customer context, optional email address, optional note and your publication-permission choice. The email is not added to marketing contacts by this form. Checking publication permission does not guarantee publication, and named scans are manually reviewed before they can appear publicly. Your IP address is used only for rate limiting and is not stored with the submission.

Acquisition measurement

Early Access and newsletter submissions also record one acquisition event: the referrer domain and UTM campaign fields that brought you, plus an automated relevance score computed from what you wrote about your product. The score helps Seek understand which kinds of product apply; it accepts and rejects no one on its own. The event carries no IP address and no plain-text product domain.

Retention and requests

Analytics use a random session identifier rather than an account identity. For privacy questions or deletion requests, contact support.seek.team@gmail.com.

Email processing

Seek uses Mailjet to send transactional, marketing and digest emails. Mailjet is a sub-processor that stores only what is needed to deliver a message; it does not use the data to train models or share it with other customers.

Consent and preferences

Marketing and newsletter emails require an explicit double opt-in. Transactional emails (beta confirmation, access decisions, contact acknowledgment, support acknowledgment) are sent because they are necessary to fulfill your request and do not rely on marketing consent. You can manage your preferences at any time through the link in every marketing email or at /email/preferences.

Suppressions

If you unsubscribe, bounce permanently, report spam or are blocked, Seek records the suppression locally. A global suppression blocks all external emails except strictly required transactional messages. A marketing-only suppression continues to allow transactional emails.

Logs and retention

Outbox records, event logs and suppression entries are retained for 24 months for deliverability and compliance purposes. Newsletter tokens expire after 24 hours and are deleted immediately after use. Contact identifiers are kept indefinitely only while the contact remains active or has an unsubscribed consent state that must be respected.

Data subjects rights

To exercise access, rectification, erasure or portability rights, contact support.seek.team@gmail.com. Suppression and preference requests are honored within 72 hours.

Last updated: August 31, 2026. This is a product policy and not legal advice.