Creator-scoped data
Subscriber records belong to one creator. Database row policies and server checks scope creator reads and writes.
Trust
Know what you are joining.
Subscribers join a specific creator, not a Seamline marketing list. The creator owns that relationship. Capture and email flows keep consent and unsubscribe choices visible.
AI uses creator-approved content and voice settings, feedback on generated copy, and aggregate activity counts. Creator email addresses, subscriber identities, and event guest details stay out of prompts.
Current controls
Subscriber data stays out of AI
AI uses creator-approved content and voice settings, feedback on generated copy, and aggregate activity counts. Creator email addresses, subscriber identities, and event guest details stay out of prompts.
Server-side plan checks
Plan limits are decided from server-side creator records. A browser cannot grant itself a paid tier or a larger generation allowance.
Email choices
Creator marketing sends check unsubscribe and subscriber preferences before contacting the email provider. Event service messages are handled separately.
Verified sender setup
Subscriber mail waits for a verified creator sender. A recorded signup is not presented as proof that an email was delivered.
Browser protections
Public responses set a content security policy, transport security and same-origin framing controls. Private signed-link pages prevent referrer sharing.
Service providers
These providers support specific product tasks. Subscriber identities are never sent to the AI provider. Collection and retention details are in the privacy policy.
Read the privacy policySupabase
Database and account authentication, including creator and subscriber records.
Anthropic / Claude
AI uses creator-approved content and voice settings, feedback on generated copy, and aggregate activity counts. Creator email addresses, subscriber identities, and event guest details stay out of prompts.
Jina Reader
Reads the public URL a creator chooses to import or compare. Receives that URL and retrieves its page content; account credentials and subscriber records are not sent.
Stripe
Payment processing and subscription records.
Brevo
Email dispatch and delivery events. Receives the recipient address and the message needed to deliver the email.
Cloudflare
Hosting, content delivery, custom-domain routing and first-party aggregate analytics.
Your data choices
- Delete your account from Settings. Your creator data, projects, leads, events and event responses are deleted within 30 days. Stripe keeps billing records under its own legal obligations.
- Export your subscriber list as CSV on the Studio plan and above.
- Event guests can ask the event host, or Seamline, for access, correction or deletion.
- For a GDPR or CCPA request, write to the address below.
Report a security or privacy problem
Email the address below with what you found, the page or request involved, and the steps to reproduce it. Please do not access, change or keep other people's data while testing, and do not include subscriber data in your report.
Seamline does not run a paid bug bounty. This page describes current product behavior; it is not a certification claim. The same contact is published in a machine-readable security.txt file.
Read the details.
Privacy
What we collect, how it is used, and your access, export and deletion choices.
Accessibility
Keyboard navigation, readable themes, reduced motion and ways to report a barrier.
Service status
Component health and availability, with update times and measurement limits.
Terms of Service
The agreement between you and Seamline.
Check the evidence.
Seamline is building in public. Service status describes availability; platform stats describe aggregate activity. Neither is evidence that a creator’s email reached an inbox or that a visitor became a subscriber.
View platform stats