Your work is not mystery fuel.

What Pulse handles

• Account identity and workspace membership through Supabase Auth.
• Your captures, drafts, corrections, channel laws, campaigns, Field evidence, and delivery receipts.
• Social and Kit credentials encrypted on the server. Credential rows are never returned to browser clients.
• Uploaded publication media. The publication bucket is public by design; do not place private media there.
• Subscriber identity as a one-way workspace-scoped hash inside Pulse. Kit remains the holder of raw subscriber email.
• Billing state from Stripe; Pulse does not store full card details.

How it is used

To route and prepare work, enforce your chosen boundaries, deliver approved posts, reconcile email consent, attribute evidenced outcomes, improve drafts from your explicit corrections, prevent duplicates, and show operational health.

Processors and boundaries

Hosted operation uses Vercel, Supabase, Anthropic when model drafting is enabled, Buffer for supported social delivery, Kit for email, and Stripe for billing. Pulse does not sell subscriber data. It does not autonomously send comments or prospect DMs, scrape the whole social web, or claim access to private platform algorithms.

Early-access email

The public form sends the address directly to a configured Kit form using double opt-in. Pulse does not write that raw address to its own database. You can unsubscribe through any Kit email.

Access, export, and deletion

Workspace exports are available inside the product. For access or deletion help, email hello@signalstudiopublishing.com. Provider-side copies and already-published social posts must also be managed with the relevant provider.