Privacy Policy

Seamline is built on the belief that creators should control their own audiences and data. This policy explains what we collect, what we never do, and your rights.

What we collect

Account information

When you create a Seamline account: your email address, display name, and optional bio and social links. If you sign up via OAuth (GitHub, Google), we receive your name and email from that provider.

Project and hub content

Descriptions, titles, and URLs you add to projects. This content is what Seamline uses to generate Artificial Intelligence (AI) magnet copy — it’s creator-authored and you control it.

Usage and analytics

Aggregate usage signals (pages viewed, features used, magnet generation counts) via Cloudflare Workers Analytics Engine — a first-party, privacy-first mechanism that does not use cookies, never stores your raw IP address, and never builds a personal profile.

Support feedback

If you choose to report a problem or rate a help article, we record the product task, page, selected problem or usefulness category, and report status with your account. You can optionally add a short comment and a reviewed description of that product context. Do not include subscriber information, passwords, private links or other people’s personal information. You separately choose whether Seamline may contact your existing account address about the report.

Lead and subscriber data

When a visitor submits their email on a creator’s hub, that email and any optional name are stored in Seamline’s database — isolated per creator (RLS-enforced). This data belongs to the creator whose hub was used.

When you subscribe to creator updates, we record when and why you signed up. A waitlist request is recorded separately and does not by itself subscribe you to creator updates.

Subscribers can use a private link in creator emails to choose topics, projects, a maximum email frequency, or a 30-day pause. A separate unsubscribe link records an opt-out immediately, which future marketing send checks honor. Saving preferences never reverses an unsubscribe. Delivery status is shown only when there is evidence of a provider delivery event.

Event responses

When you respond to an Event Thread, we store your name, email, response, party size, answers to the host’s questions, and attendance status so the host and event cohosts can operate that event. Responding to an event does not subscribe you to marketing. A separate, optional checkbox is required before Seamline adds you to the creator’s subscriber list.

How we use your data

• To provide and operate Seamline (auth, hub rendering, lead capture, Event Threads, AI generation)
• To send transactional emails (event confirmations and reminders, email confirmations, receipts)
• To send creator updates to people who subscribed, subject to their preferences and unsubscribe choice
• To improve the product using aggregate, anonymised signals
• To enforce tier quotas and billing via Stripe

We do not sell your data or use it for ad targeting. Service providers below process the information needed to operate Seamline, including storing subscriber records and delivering email. Subscriber lists are not shared with other creators.

We use support feedback to investigate problems, explain the team’s response and ask whether a change helped. Individual reports are private to you and Seamline’s support team. We measure resolved problems and repeated failures in aggregate; support feedback is not used for advertising or sent to an AI provider.

Importing a public page

Jina reads the public page you select. Claude drafts profile and project details from that page for your review. Nothing is published automatically. Use a public page without login details, query parameters or fragments. Do not import subscriber lists or private information.

Third-party services

• Supabase — 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.

Data retention

Account data is retained for as long as your account exists — we do not automatically purge or delete data based on inactivity. Deletion only happens when you request it: if you delete your account from Settings, your creator data, projects, leads, events, and event responses are deleted within 30 days. Event guests may request access, correction, or deletion through the event host or by contacting Seamline. Stripe retains billing records per their legal obligations.

Support feedback and its response history are retained while your account exists and are included when you request access or delete the account, under the same account-data deletion period described here.

Your rights

• Access — request a copy of the data we hold on you
• Deletion — delete your account and all associated data from Settings
• Portability — export your subscriber list as CSV (Studio+ tier)
• Correction — update your account information in Settings

For GDPR or CCPA requests: founder@vaultsparkstudios.com

Cookies

Seamline uses a small number of first-party cookies and browser storage entries, all set by Seamline itself. No tracking cookies. No ad cookies. No fingerprinting. Nothing is shared with a third party.

• Sign-in session — keeps you signed in to your dashboard (Supabase authentication).
• Homepage headline (_hero_ab) — we test which homepage headline explains Seamline best. This remembers which one you saw so the page does not change between visits. It holds only the headline letter, never anything about you, and expires after one year.
• Theme preference — remembers light or dark mode in your browser’s local storage. It never leaves your device.
• Optional reading bookmark — where Save this path is offered, saving is your choice. It stores the public path URL, reading position, content version, and save and expiry dates in this browser only. It keeps one bookmark per creator, up to 20 in total, and expires after 30 days. It does not synchronize with your account, identify subscribers, track reading, or go to an AI provider.
• Notifications — only if you choose to turn on browser notifications for your dashboard. You can switch them off at any time in your browser.

A reading bookmark can be cleared, reset or exported from the reading controls. If browser storage is unavailable, those controls explain that saving failed. Expired bookmark data is physically removed on the next visit to the feature; you can also clear it yourself or clear browser storage. Closing the browser does not remove those bytes immediately, and deleting your account cannot remotely clear a closed browser.

Contact

Questions about this policy: founder@vaultsparkstudios.com
Seamline is a product of VaultSpark Studios LLC.