Privacy Policy
LaunchGenius is a product of Born2Be LLC, the company responsible for the data described on this page. “We” below means Born2Be LLC.
LaunchGenius stores the content you commit to a launch, your email address, and — if you connect a social account — OAuth tokens used solely to publish the content you approved, at the time you scheduled. We never post anything you didn't explicitly commit and approve. Tokens are stored encrypted and can be revoked at any time by disconnecting your account.
Connected social accounts
Connecting an account is optional and is always started by you. When you connect one, we receive and store only what is needed to show you which account you connected and to publish on your instruction: the platform's account ID, the username or handle, the profile picture URL, and OAuth access and refresh tokens. Tokens are encrypted at rest with a key held by our publishing service alone.
Instagram. With the instagram_business_basic and instagram_business_content_publish permissions we read your professional account's ID, username and profile picture, and we publish the image or video post you scheduled, at the time you scheduled it. With instagram_business_manage_insights we read the performance figures — views, likes, comments, shares — for the posts we published for you, so we can show you how your launch performed. We look them up by the post ID we recorded when we published; we do not read your existing posts, your comments, your direct messages, or your followers.
Threads. With the threads_basic and threads_content_publish permissions we read your Threads account's ID, username and profile picture, and we publish the post you scheduled, at the time you scheduled it. With threads_manage_insights we read the performance figures — views, likes, replies, reposts — for the posts we published for you, looked up by the post ID we recorded when we published. We do not read your existing threads, your replies to others, or your followers.
Facebook. LaunchGenius publishes to Facebook Pages, never to your personal profile or timeline. With pages_show_list we read the list of Pages you manage so you can choose where to post; with pages_read_engagement and pages_manage_posts we publish the post you scheduled to the Page you chose. We store each Page's ID, its name, its picture and its Page access token. We never store or reuse your personal Facebook user token — it is discarded as soon as the Page tokens have been retrieved. pages_read_engagement and read_insights let us read the performance figures — views, likes, comments and shares — for the posts we published to your Page, looked up by the post ID we recorded when we published, so we can show you how your launch performed. We do not read your Page's other posts, its comments or messages, or its followers, we do not read the Page's own audience or demographic reports, and we do not read anything at all from your personal profile beyond the list of Pages.
Because a Page is what we connect, disconnecting removes one Page, not your whole Facebook connection. If you connected three Pages and disconnect one, the other two stay connected and can still publish what you scheduled to them; disconnect each Page you want removed, or revoke LaunchGenius entirely from Facebook's own settings.
TikTok. With user.info.basic, user.info.profile and video.publish we read your display name, avatar, username and open ID, and we publish the video you scheduled. With video.upload we can instead place a scheduled video in your TikTok inbox as a draft, where you finish and publish it yourself in the TikTok app. With video.list we read the view, like, comment and share counts for the videos we published for you, matched by the video ID we recorded when we published. We do not read your comments or your followers, and we do not read videos you posted yourself.
YouTube. With youtube.force-ssl we read your channel's ID, title and picture, and we upload the video you scheduled with the title, description and settings you chose. With yt-analytics.readonly we read the view, like and comment counts over the first days of the videos we uploaded for you, matched by the video ID we recorded at upload, so we can show you how your launch performed. We do not read your channel's other videos, your subscribers, your watch history, or any revenue data.
Google user data. We encrypt it in transit and at rest, and only our publishing service can decrypt it. No other system or person at LaunchGenius has access. Your channel ID, video IDs, and performance metrics are retained for as long as your account is active, so your launch history stays intact. Disconnecting your YouTube account deletes the stored OAuth tokens immediately, not on a schedule. Requesting full account deletion (see Deleting your data) removes everything, including all Google user data we hold.
Across every platform the rule is the same: we read performance figures only for posts we published on your instruction, identified by the post ID we stored at the moment we published it. We never survey your account, and we never read a post you made yourself.
Who sees those figures. A launch is a coordinated campaign, so the performance of the posts we published for you — views, likes, comments and clicks on those posts only— is visible to the organizer and to the other members of the workspace that ran the launch. This is true even if you are not a member of that workspace yourself, which is the usual case when you joined through an invite link. It is how an organizer judges whether the launch worked. Nothing else about your account is shared with them: not your other posts, not your followers, not your account's own totals. If you would rather the organizer did not see these numbers, do not connect the account — you can still take part, and we will remind you to post at the scheduled time instead.
We never post content you did not write, commit and approve in advance, and we never post at a time you did not choose. Platform data is used only to provide the publishing feature you asked for. We do not sell it, we do not use it for advertising or profiling, we do not use it to train machine-learning models, and we do not share it with third parties beyond our own infrastructure providers (Cloudflare, which hosts the application and database, and Resend, which sends our email).
Disconnecting an account deletes its tokens from our database immediately. See Deleting your data for how to remove a connection or your entire account.
Analytics
We use PostHog, hosted in the EU, to understand how the product is used. We record page views and a small set of named product events — for example that a launch was created, a post was submitted, or a tracked link was clicked. We do not use session recording, and we do not use automatic capture, so the text you write is never collected: your draft posts, briefs and participant names stay out of our analytics.
This applies to everyone who uses LaunchGenius, including participants who joined a launch through an invite link rather than signing up themselves. If you took part in someone else's launch and would prefer not to be included, email us at the address below and we will delete your analytics data.
Clicking a tracked link in a launch post records the click, the referring site and the country it came from, so the organizer can see how their launch performed. We do not store your IP address, your browser's user agent, or any cookie for this.
We send sign-in links and launch notifications to the address you gave us. Organizers can import contacts to invite people to a launch; an invitation is only ever an invitation — nothing is posted from anyone's account unless they join and connect it themselves.
Contact: privacy@launchgenius.app