Principle
Creator-owned relationship
Subscribers join a specific creator, not a generic Seamline marketing list. The list belongs to the creator — not to us.
Trust infrastructure
Audience trust is a product feature.
Seamline helps creators build a direct thread with their audience. That only works if visitors know what they are joining, who will email them, and where their data will not go.
Boundary promise
Creator content can power AI. Subscriber identity cannot.
This is enforced as a product design rule, not a marketing footnote.
Core principles
Principle
No subscriber PII in AI
Lead emails, names, and subscriber-identifying data stay out of model prompts. Only creator-authored project descriptions go to Claude.
Principle
Clear unsubscribe expectation
Capture surfaces and email flows must keep exit paths visible and honest. No buried opt-outs, no dark-pattern re-subscriptions.
Principle
No dark-pattern capture
Seamline optimizes for trust and clarity — not pressure mechanics, fake urgency, or hidden consent. We build trust infrastructure.
Data boundaries
Exactly what goes where.
Used for creator intelligence
- Project descriptions
- Creator-approved voice settings
- Aggregate capture counts
- Aggregate source quality
- Creator feedback on generated copy
Never sent to AI
- Lead email addresses
- Lead names
- Raw subscriber identity
- Private payment data
- Unapproved subscriber preference text
Used only after explicit setup
- Email dispatch via verified sender domain
- Stripe billing events
- Custom-domain routing
- Durable preference storage
Executable guardrails
Promises that fail closed.
These are not policies we hope to follow. They are automated rules: when one would be broken, the change is refused. None of these checks ever reads subscriber personally identifiable information.
Prompts are checked before they ship
Automated checks block subscriber emails, names, and raw lead records from ever reaching an artificial intelligence (AI) prompt. A change that breaks this rule cannot be released.
Checked on every build
Plan limits are enforced on our servers
What your plan includes is decided from our own billing records, never from anything a browser claims. Over a limit means a clear refusal, not a quietly degraded result.
Checked on every request
Progress without identity
When we track a creator’s milestones, we count totals. Individual subscribers are never written into progress records.
Aggregate counts only
Where we are
Building in public. Launching when it’s ready, not before.
Early creators can already build a hub and capture subscribers. We will not announce a public launch until each of these is verified, and we would rather be late than wrong about it.
See live platform status →- Email from a creator arrives reliably and replies reach a real person.
- Hub pages stay fast on slow mobile connections.
- Every theme stays readable for every visitor.
- Account sign-in meets our security bar before we invite everyone in.
Subscriber promise
What a visitor should understand before joining.
They are joining a creator-specific relationship, not a platform newsletter.
The creator controls the message and the list relationship; Seamline supplies infrastructure and measurement.
Preference signals are optional, consented, and aggregate-first — they help the creator improve the thread without turning the subscriber into a data product.