Privacy Policy

When you use Taylslate, we collect:

• Account email and name.
• Company.
• Brand and show profile data.
• Campaign briefs.
• Uploaded past-campaign files.
• Deal and payment records, including amounts, status, and Stripe identifiers. Taylslate does not store card numbers.
• Usage logs the app writes when something happens, such as a deal update or an operation record.

We use this information to run accounts, discovery, outreach, insertion orders, signatures, and payments, and to keep a record of what happened. [CONFIRM WITH COUNSEL] Any use beyond operating the service.

Taylslate may use aggregated, anonymized data from deals booked and completed through Taylslate to improve pricing and recommendations. Aggregates never identify a brand, and each one combines at least five brands. Files you upload stay private unless you choose to share them.

How the product applies that line

Anonymized patterns from deals booked and transacted through Taylslate feed a pooled dataset.

An uploaded past-campaign file joins that pool only if the brand opts in on the import screen. The checkbox is off by default. The terms version recorded is pooling-v1.

A brand's own uploaded past-campaign file stays private to that brand. It is not shown to other brands or shows. That file is never part of any aggregate unless that brand opted in. An imported insertion-order PDF becomes an ordinary deal and is pooled once it is signed.

These providers process data for the purpose named. Each one is in use in this product.

• Supabase: database and auth.
• Vercel: hosting.
• Stripe: payments and payouts.
• DocuSign: e-signature.
• Resend: email.
• Anthropic: AI drafting and scoring.
• Podscan: public podcast show data.
• YouTube Data API: public channel data.
• Cloudflare Turnstile: bot check on login, signup, and forgot-password.

[CONFIRM WITH COUNSEL] How long account, profile, brief, upload, deal, payment, and log data are kept, including after you ask for deletion.

Sign-in is an email code. Database access for a signed-in user is limited by row rules, and server-side writes use a separate service credential. Card numbers are collected by Stripe, not stored by Taylslate. This draft does not claim a certification, insurance, or an uptime level. [CONFIRM WITH COUNSEL] Any security statement that should be added.

Email [PRIVACY CONTACT EMAIL] to ask for access to, correction of, or deletion of your account data. [CONFIRM WITH COUNSEL] Any additional rights, and how long a response should take.

Taylslate sets cookies to keep you signed in. Those are the authentication session cookies. It also sets a short-lived cookie so a password reset form opens only after a recovery link, a short-lived cookie that returns a show to an outreach page after onboarding, and cookies an internal admin uses to switch a test view and to return to the admin account.

Taylslate does not install an advertising pixel or a third-party analytics script in this application. Login, signup, and forgot-password load a Cloudflare Turnstile script for a bot check. [CONFIRM WITH COUNSEL] What that script stores in the browser, and how long it is kept. [CONFIRM WITH COUNSEL] Whether a host such as Vercel or Supabase sets additional cookies we do not control in the browser.

Taylslate is not directed to children under 18. [CONFIRM WITH COUNSEL] Whether the minimum age should be stated differently.

This page is a draft. [CONFIRM WITH COUNSEL] How a change to this policy will be announced, and when it takes effect.

[COMPANY LEGAL NAME]
[MAILING ADDRESS]
Privacy contact: [PRIVACY CONTACT EMAIL]

The terms of service are at Terms of Service.