Privacy Policy

Account data: your name and email address when you create an account.

Phone number: collected during onboarding and used to send transactional SMS for approval flows (gig advances, invoice drafts, content briefs). Not used for marketing. You opt in to SMS at signup and can disable it from account settings.

Public profile data we auto-discover: when you tell us your artist name at signup, we search Resident Advisor, Spotify and Last.fm for public profile details (genre, bio, profile image, upcoming gigs) to pre-fill your account. This data is public and we only store what you confirm during onboarding.

Instagram data: when you trigger an Instagram scan from within Broadcast Lab, we fetch your public profile information and recent posts. This only works on public Instagram accounts. We do not store your Instagram password or any private data. See the Instagram Data section below for the provider used.

Content data: captions, media files, scheduled posts, and release campaign data that you create inside the platform.

Platform analytics: engagement metrics (likes, comments, reach) fetched from connected accounts to display inside your analytics dashboard.

Gig and financial data: touring, invoice, and contract information you enter into Tour Lab.

To provide the core service: post scheduling, campaign management, gig planning, and invoicing.

To publish content to your connected social accounts when you explicitly trigger a post or schedule.

To send automated DM replies to followers who comment a trigger keyword on your posts, when you have enabled that feature for a specific post.

To retrieve and display performance metrics from your connected accounts.

We do not sell your data. We do not use your data to train models. We share data with third parties only as required to operate the service: Supabase (data storage, EU region), Cloudflare (hosting, EU region), Anthropic (the language model that powers content drafting), Stripe (payments), Resend (transactional email), Twilio (SMS approval flows), HikerAPI (public Instagram data), Meta Graph API (account-authorised actions). No data is shared for advertising.

Age requirement: you must be 16 or older to use Signal Lab OS. We do not knowingly collect data from anyone under 16.

Signal Lab uses two separate Instagram data paths.

Public profile data. When you click "Scan my Instagram" inside Broadcast Lab, we fetch your public profile information and recent posts through HikerAPI, a third-party service. This only works on public Instagram accounts. Data fetched: profile name, bio, follower count, post captions, media URLs, engagement metrics. We never receive private messages, private posts, or anything you have not made public.

Connected account actions (Meta Graph API). If you separately authorise Signal Lab through Meta's official OAuth flow, we receive an access token that lets you publish content, read comments on your own posts, and send DM replies via the Meta Graph API. This is opt-in per action and tokens are stored encrypted.

You can disconnect your Instagram from within Signal Lab OS at any time. This revokes access and stops the data fetch.

To request deletion of all your data, email advancingabsolute@gmail.com or use the data deletion option in account settings.

Essential cookies only. Signal Lab uses Supabase auth cookies to keep you signed in. These are strictly necessary and cannot be disabled.

Analytics without cookies. Product analytics run through PostHog (EU data residency) in cookieless mode. No tracking cookies are set, no cross-session profile is built. Page-view and feature-usage events are captured per browser session only and used to debug and improve the product.

We do not use Google Analytics, Meta Pixel, or any cross-site tracking service.