Signalant Privacy Policy

Effective date: June 29, 2026

Last updated: June 29, 2026

1. Information You Provide

When you create an account, configure your show, or contact us, we collect:

• Account information — name, email address, and password (or Google OAuth credentials)
• Profile information — display name, profile image, and account preferences
• Show information — show name, niche, target audience description, episode format, recording platform, and publishing platform
• Guest and lead data — names, contact details, company information, social profiles, ICP scores, outreach history, and booking decisions you enter or import
• Podcast production data — episodes, stages, recording dates, call sheets, contracts, schedules, and follow-up sequences
• Knowledge Base content — brand voice, show description, ICP definition, offer overview, success stories, and objection library you author
• Agency and business information — if you use Signalant on behalf of an agency or multiple clients, information about those clients and shows
• Communications and support — messages, emails, or other content you send to us

2. Automatically Collected Information

When you use Signalant, we and our service providers automatically collect:

• Device and browser information — browser type and version, operating system, device type, and screen resolution
• IP address and approximate location — used for security, fraud prevention, and regional compliance
• Login and session activity — timestamps, session duration, and authentication events
• Usage activity — pages visited, features used, button clicks, and navigation paths within the platform
• Error, performance, and security logs — error messages, crash reports, and performance metrics collected by Sentry
• Authentication cookies and tokens — short-lived session tokens issued by Supabase to keep you signed in; no persistent tracking cookies are set by Signalant for advertising purposes

3. Subscription and Payment Information

Billing for paid Signalant plans is processed by Stripe. When you subscribe, Stripe collects your payment card details directly. Signalant does not receive or store your complete card number, CVV, or bank account credentials. We receive from Stripe a customer identifier, subscription status, plan tier, and last-four digits of your card for display purposes.

Signalant does not facilitate payments between users. There is no user-to-user payment system, marketplace, or escrow function within the platform. All subscription fees are paid directly to Juming Delmas Studios LLC.

4. Google User Data

Signalant offers Google Sign-In as an authentication option. When you choose to sign in or sign up with Google, Supabase (our authentication provider) requests access to your Google account using the following OAuth 2.0 scopes:

• email — your Google account email address and email verification status. Used to create or connect your Signalant account and to identify you on subsequent logins.
• profile — your Google account display name, profile picture URL, and Google account identifier. Used to pre-fill your Signalant account name and display your profile image within the application.

What Signalant does not access via Google:

• We do not request or access your Gmail messages, Google Drive files, Google Calendar, Google Contacts, or any other Google service beyond basic account identity.
• We do not access your Google search history, YouTube activity, or advertising profile.

How your Google account data is used:

• To authenticate you and verify your identity on each login
• To create or connect your Signalant account record
• To secure your account and prevent unauthorized access
• To display your name and profile image within the Signalant application

Storage and retention:

• Your email address and display name received from Google are stored in our database (Supabase) as part of your account record.
• Your profile image URL may be stored for display purposes.
• Google authentication tokens are managed by Supabase and are not stored in application-level code or logs.
• Google account data is retained for as long as your Signalant account is active. You may request deletion as described in Section 10.

Sharing:

• Your Google account email and name are stored in Supabase (our database and authentication provider) and on Vercel (our hosting provider) as part of normal server-side operations.
• Your Google account data is not sent to Anthropic or any other AI provider. The Claude AI features in Signalant (pitch writer, prep kit, warm-lead scorer) operate on podcast and guest content you explicitly enter into those tools — not on your Google authentication data.
• Your Google account data is not sold, shared with data brokers, or used for targeted advertising.

Revoking access:

You can revoke Signalant's access to your Google account at any time from your Google Account's Third-party apps & services page. Revoking access will not delete your Signalant account but will prevent future Google Sign-In. You can request full account deletion at signalant.io/data-deletion.

5. How We Use Your Information

We use the information we collect to:

• Provide, maintain, and improve Signalant features and functionality
• Authenticate users and protect account security
• Manage subscription plans, billing, and payment processing through Stripe
• Operate guest discovery, production tracking, outreach, and pipeline tools
• Generate AI-assisted drafts, prep documents, scores, and follow-up suggestions
• Send transactional emails (account confirmation, password reset, billing receipts, call sheet reminders) via Resend
• Respond to support requests and communications
• Monitor for and prevent fraud, abuse, and security incidents
• Monitor application performance and error rates via Sentry
• Comply with legal obligations
• Send service-related announcements when required (we do not send marketing email without your consent)

6. AI-Assisted Features

Signalant uses the Anthropic Claude API to power AI features including the Pitch Writer, Guest Prep Kit, and Warm-Lead Scorer. These features generate drafts, preparation documents, ICP scores, and suggested outreach content based on the podcast, show, guest, and knowledge-base information you have entered.

• All AI-generated outputs require your review and approval before any action is taken.
• Signalant does not automatically send outreach messages, emails, or communications without your explicit action.
• Content you provide to AI features (show descriptions, guest profiles, pitch drafts) may be transmitted to Anthropic's API for processing under Anthropic's data-handling terms.
• Your Google account data (email, name, profile image) is not sent to Anthropic or used to generate AI outputs.
• Signalant does not claim, and does not believe, that user data is used by Anthropic to train general-purpose AI models under Anthropic's current API terms. You should review Anthropic's Privacy Policy for their data-handling commitments.
• Signalant does not use Google user data to train any AI or machine-learning model, generalized or otherwise.

7. Information Sharing and Disclosure

We share your information only with the service providers necessary to operate Signalant:

• Supabase — database storage and user authentication. Your account data, show data, guest data, and activity logs are stored in Supabase-hosted PostgreSQL.
• Vercel — application hosting, serverless function execution, and CDN delivery. Request logs including IP addresses may be retained by Vercel.
• Stripe — subscription billing and payment processing. Stripe receives your payment card details and billing address directly.
• Resend — transactional email delivery (account confirmation, receipts, call sheet reminders). Your email address is shared with Resend to deliver these messages.
• Sentry — application error monitoring. Error reports may include anonymized stack traces and session context; we configure Sentry to minimize inclusion of personal data in error payloads.
• Anthropic — AI content generation via the Claude API. Podcast and guest content you submit to AI features is processed by Anthropic under their API terms. Google authentication data is not included.
• Google — OAuth-based authentication via Supabase's Google provider. Google receives the OAuth handshake and returns basic profile data as described in Section 4.

We do not sell your personal information. We do not sell Google user data. We do not use Google user data for targeted advertising or share it with advertising networks or data brokers. Data is disclosed to third parties only as needed to operate features you have requested, to comply with applicable law, or to protect the security and integrity of the platform.

8. Google API Limited Use

9. Data Security

We implement industry-standard safeguards to protect your information:

• All data is transmitted over encrypted HTTPS/TLS connections
• Database data is encrypted at rest via Supabase (AES-256)
• Row-level security policies restrict database access so each user can only access their own data
• Authentication tokens have limited lifespans and are rotated regularly
• Access to production systems is restricted to authorized personnel
• Application errors and anomalies are monitored via Sentry

No security system is guaranteed to be completely secure. If you believe you have discovered a security vulnerability, please contact us immediately at support@signalant.io.

10. Data Retention and Deletion

We retain your account data, show data, and usage history for as long as your account is active and as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce our agreements.

You may request deletion of your account and associated data at any time. See our Data Deletion page for instructions. Upon verified deletion:

• Your account, show, guest, episode, outreach, and pipeline data will be permanently deleted from active systems.
• Backup copies are purged on the schedule maintained by Supabase (typically within 30 days).
• Some information may be retained for legal, fraud-prevention, accounting, or security reasons — for example, transaction records required by tax law, consent logs required for regulatory compliance (minimum 3 years), and records of abuse or policy violations.

11. Your Controls and Rights

Depending on your location, you may have rights under GDPR, CCPA, CASL, or other applicable laws. Regardless of location, Signalant provides:

• Account information — update your name and profile in Settings → Profile
• Show information — update or delete your show data in Settings → Show
• Google access — revoke Signalant's Google access from your Google Account permissions page
• Subscription — cancel your subscription at any time in Settings → Billing
• Account and data deletion — request permanent deletion via our Data Deletion page or by emailing support@signalant.io
• Access and portability — request a copy of your data by emailing support@signalant.io
• Correction — request correction of inaccurate personal data

To exercise any of these rights, contact us at support@signalant.io. We will respond within 30 days (or the timeframe required by applicable law).

12. Children's Privacy

Signalant is not directed to children under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have inadvertently collected such information, please contact us at support@signalant.io and we will promptly delete it.

13. Changes to This Policy

We may update this Privacy Policy periodically. We will notify you of material changes by email or by posting an in-app notice at least 14 days before the changes take effect. The effective date at the top of this page reflects the most recent revision. Continued use of Signalant after changes take effect constitutes acceptance of the updated policy.

14. Contact Us

Questions or concerns about this Privacy Policy or our data practices?