LAUNCHCREW / PRIVACY
Privacy Policy
What we collect, how we use it, and how you can delete it.
Last updated: November 3, 2026
COLLECTION
What we collect
LaunchCrew collects only what it needs to run the service:
- Account identity: the profile and email address returned by the sign-in provider you choose (Google or Facebook OAuth, profile and email scopes only).
- Owner-provided facts and content: the product facts you confirm, drafts you write or edit, approvals, schedules, and publishing receipts.
- Connection tokens: access tokens you provide or authorize for owner-initiated integrations, described below.
- Usage records needed to run the service: run history, checker verdicts, and session records.
USE
How we use it
We use your data to operate LaunchCrew: to sign you in, to generate drafts from your confirmed facts, to audit those drafts against your facts, to record your approvals, and to publish only the exact versions you approve to the accounts you connect.
MODELS
Model processing
Content you submit is sent to the Meta Model API (Muse Spark) to generate drafts and to check them against your confirmed facts. If you use the optional photo check, the photo is processed for segmentation. We do not use your content to train models.
INTEGRATIONS
Integrations
Every integration is owner-initiated and optional:
- Google Drive import: you pick files; the app reads only the files you select.
- Social connections (Instagram today): you provide or authorize an access token, which is stored encrypted and used only to publish owner-approved content and to verify the result.
You can disconnect any integration at any time.
SECURITY
Storage and security
Data lives in the app Postgres database and AWS infrastructure in us-east-1. Social connection tokens are encrypted at rest and are never returned in API responses, logs, UI payloads, or receipts. The Drive Picker token is different by design: it is a short-lived, one-time token handed to your signed-in browser only to complete the file pick you started. It lives in server memory only until claimed or expired and is never written to the database, logs, or receipts. Sign-in uses an opaque session cookie backed by server-side sessions.
SHARING
Data sharing
We do not sell personal data and we run no third-party advertising. Data is shared only with the service providers needed to run the product (hosting and the model API named above) and with the platforms you explicitly connect.
RETENTION
Retention and deletion
You can request deletion of your data at any time by contacting us at the address below, and you can disconnect integrations yourself at any time, which removes the stored token while keeping your past approvals and exports intact.
COOKIES
Cookies and sessions
LaunchCrew sets a single session cookie that holds an opaque session identifier. It is HttpOnly, Secure, and SameSite Lax, and it expires with your session. Your theme choice is stored locally in your own browser, not in a cookie. There is no third-party tracking on this site.
CHANGES
Changes to this policy
If this policy changes, we will update the date above and note the change here. Material changes will be announced in the product before they take effect.
CONTACT
Contact
For privacy questions or deletion requests: [email protected]