Does SeaText Store Personally Identifiable Information When Adapting Content for Referral Sources?

Direct Answer: No, SeaText Does Not Store PII

SeaText does not collect or store personally identifiable information (PII) when it adapts content for referral sources. The system only reads UTM parameters and referrer headers—non-identifying signals that indicate where a visitor came from. All processing happens server-side, and SeaText does not use cookies to track or identify individual users.

This means your referral traffic personalization works without compromising visitor privacy. SeaText sees the source (e.g., a specific email campaign or referring article) but not the person behind the click.

Comparison: Server-Side vs. Client-Side Tracking

To understand why SeaText is private, it is helpful to compare it to traditional tracking methods. Most tools rely on client-side pixels, whereas SeaText operates on the server.

Criteria	Client-Side Pixels (Traditional)	SeaText Server-Side
Data Storage	Stored in user browser/cookies	Processed in memory, not stored
Cookie Usage	Relies on 3rd-party cookies	No cookies used
Privacy Risk	High (data leakage to networks)	Low (data stays controlled)
Page Speed	Can cause 'flicker' or lag	Zero-flicker execution
Compliance	Requires complex consent	GDPR/CCPA friendly by design

Technical Architecture: Server-Side vs. Client-Side Processing

The fundamental difference lies in where the decision-making logic happens. In a client-side setup, a script runs in the visitor's browser. This script gathers data, sends it to a third-party server, and then modifies the page. This often causes a 'flicker' where the user sees the original content before the personalized version loads.

SeaText uses a server-side architecture. When a request hits the server, it passes through the SeaText edge layer before reaching the browser. The server analyzes the incoming traffic signals and rewrites the HTML instantly. The browser only receives the finished, personalized page. Because the logic happens on the server, no tracking scripts are ever executed on the user's device for the personalization process.

The Data Lifecycle: From Click to Page Load

Understanding how data flows helps clarify why PII is not captured. Here is the lifecycle of a request:

1. The Click: A visitor clicks a link in a newsletter or ad. The URL contains UTM parameters.
2. The Request: The browser sends a request to your server. This request includes the URL and the referrer header.
3. The Analysis: SeaText intercepts the request. It reads the utm_source or the referrer URL.
4. The Adaptation: SeaText matches these signals to your predefined content rules (e.g., 'if source is email, show headline A').
5. The Delivery: The server sends the modified HTML to the visitor.
6. The Discard: The session signal is used for that specific load and is not saved for later.

Regulatory Landscape: GDPR, CCPA, and Non-Identifying Signals

Privacy regulations like GDPR (Europe) and CCPA (California) focus on 'personal data.' This is defined as any information that can identify a specific person. This includes names, emails, and unique device IDs stored in long-term cookies.

SeaText operates using 'non-identifying signals.' A UTM parameter tells you where traffic came from, not who arrived. Because SeaText does not link these signals to a persistent user profile, it falls outside the high-risk category of data processing. This allows marketers to personalize experiences without the legal burden associated with tracking an individual's browsing history across the web.

Best Practices for UTM Structure and Personalization

To maximize personalization while maintaining privacy, marketers should structure their links carefully. Follow these guidelines:

• Use Generic Source Tags: Use utm_source to identify the campaign (e.g., 'newsletter_weekly') rather than specific user IDs.
• Avoid PII in URLs: Never include email addresses or names in UTM parameters.
• Focus on Intent: Use utm_content to categorize visitor's journey stage (e.g., 'comparison_guide') to trigger relevant content without identifying the user.
• Audit Your Links: Regularly ensure your marketing tools are not accidentally leaking sensitive data into the URL string.

What SeaText Actually Reads

When a visitor arrives from a referral source, SeaText looks at two things:

• UTM parameters – Tags like utm_source, utm_medium, and utm_campaign that you add to links in emails, articles, or ads.
• Referrer headers – The URL of the page that linked to your site, which the browser sends automatically.

These signals tell SeaText the source of the traffic, not the identity of the visitor. For example, it can see that someone came from a specific newsletter article, but it cannot see their name, email address, or any other personal detail.

Why This Matters for Your Compliance

If you're using SeaText to personalize content for referral traffic, you need to know that your privacy compliance isn't compromised. Here's why this matters:

• GDPR and CCPA compliance – Since no personal data is collected, you avoid high-risk processing.
• Trust with audience – Visitors who click from a referral source won't feel tracked.
• Simpler data governance – You avoid the burden of managing personal data you don't actually need.

Ignoring this could lead to unnecessary privacy risks. By using a tool that doesn't store PII, you keep your strategy clean and compliant.

How it Works With the Source Signal

SeaText uses the source signal to match the visitor to a content variant. This happens in real-time. SeaText processes the referral information on its servers, not in the visitor's browser. This means:

• No cookies are dropped on the visitor's device.
• No personal data is stored in SeaText's systems.
• The adaptation happens in real time, before the page loads, and the source signal is discarded after use.

This server-side approach is a key privacy advantage. It avoids the common pitfalls of client-side tracking, such as third-party cookies and data leakage to ad networks.

Limitations and When This Doesn't Apply

While SeaText doesn't store PII, there are some limitations to be aware of:

• Referrer headers can be stripped – Some browsers or privacy tools block referrer headers. In that case, SeaText relies on UTM parameters.
• UTM parameters are visible – They can be seen by the visitor and any analytics tools you use.
• No cross-device tracking – SeaText does not link a devices; personalization is limited to a single session.

If you need to personalize based on a returning customer identity, this is not the right tool.

Terminology: PII vs. Non-PII

PII (personally identifiable information) includes data like names, email addresses, and phone numbers that can identify a specific person. Non-PII includes data like UTM parameters, referrer URLs, and device types that don't identify an individual.

SeaText only deals with non-PII. This distinction is crucial for privacy compliance. By avoiding PII, SeaText sidesteps the heavy regulatory requirements that come with handling personal data.

Frequently Asked Questions

Does SeaText use cookies for referral adaptation?

No. SeaText processes referral signals server-side and does not set cookies on the visitor's browser.

Can SeaText see a visitor's email address or name?

No. SeaText only reads UTM parameters and referrer headers, which do not contain personal identifiers.

Is IP address considered PII, and does SeaText store it?

IP addresses can be considered PII in some jurisdictions. SeaText does not store IP addresses for referral adaptation; it only uses the source signal.

Do I need to update my privacy policy if I use SeaText for referral adaptation?

Since SeaText doesn't collect PII, you likely don't need to add a specific disclosure. However, it's always good practice to review your privacy policy with a legal professional.

How can I verify that SeaText isn't storing PII?

You can review SeaText's privacy policy and data-processing addendum, or contact their support team for details on data handling.

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

PII (Personally Identifiable Information) | CDP.comWhat Is PII (Personally Identifiable Information)?What is personally identifiable information (PII)?

Further reading and comparison sources

These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.

• PII (Personally Identifiable Information) | CDP.com
• What Is PII (Personally Identifiable Information)?
• What is personally identifiable information (PII)?

Learn more

Visit the website for more information.