This Privacy Policy explains what information Stitch Factory collects during the current Founding Creator Beta period, how it’s used, and the choices available to you. Stitch Factory helps livestream creators capture moments they choose while live and turn them into short, social-media-ready clips.
In this policy, “Stitch Factory,” “we,” and “us” refer to Stitch Factory as it currently operates during this beta period.
Information you provide
Account information
When you create an account, Stitch Factory collects your email address and, if you sign up with a password, a securely hashed version of it (never the password itself). You can also create an account using “Continue with Google,” in which case Google shares your account information with us as part of that sign-in, subject to Google’s own privacy practices.
Beta signup
Beta signup collects your name, email address, age affirmation, and acceptance of the Terms, Privacy Policy, and creator agreements. We record your agreement version and acceptance time, workspace, trial start and end dates, and render-credit allowance to provide your 30 days free without a credit card. Information previously submitted through the creator application form remains part of your account history and is retained under this policy. The old /apply address now leads to signup.
Creator and workspace information
Using Stitch Factory as a creator involves a workspace: a name you choose for it, your role in it (owner, admin, or member), and the clips, sessions, and settings you create inside it.
Information collected automatically
Website analytics
Pages on the public marketing site (not the authenticated creator portal, admin area, or OBS control page) run a first-party analytics tracker we built and operate ourselves — this first-party tracker is separate from optional Meta advertising measurement. It records: the page you viewed, the referring site’s domain name only (never the full referring URL), any UTM campaign parameters in the link you followed, a coarse device/browser/operating-system category, and roughly how long you stayed engaged with the page. A randomly generated session identifier and visitor identifier (not derived from your name, email, or any other personal information) are used to distinguish visits from unique visitors.
Approximate location
We record an approximate country, region, and city for each analytics session, sourced from Cloudflare’s own edge network (the same infrastructure that serves the site) — not from a separate IP-lookup service, and not precise geolocation such as GPS coordinates.
IP addresses
We do not store your raw IP address. A one-way hashed version of it is used transiently, for a short window, solely to detect and rate-limit automated abuse of our analytics and application endpoints.
Cookies and browser storage
If you’re signed in, a session cookie keeps you authenticated. A separate, long-lived first-party cookie exists only to let an operator of this site exclude their own browser from analytics; optional Meta measurement may use advertising cookies only after you allow marketing. A small amount of browser local/session storage is also used for: the anonymous analytics identifiers described above, and, once you’re a signed-in creator, remembering interface preferences such as which streaming-software setup guide you last viewed and whether a portal section is expanded or collapsed — none of this is shared with anyone or used to identify you across other sites.
Optional Meta advertising measurement
When configured and you explicitly allow marketing, Meta Pixel receives public page categories, campaign identifiers, and events for a verified new registration, a beta signup, and the workspace owner’s first successfully created clip. We do not include names, email addresses, invitation tokens, stream keys, clip contents, or workspace identifiers in these event payloads. Meta also receives network information such as your IP address and browser information when your browser contacts Meta, and may use cookies to associate activity with ads.
You can reject or withdraw marketing consent using Cookie settings in the site footer. Global Privacy Control, Do Not Track, and the existing analytics opt-out override marketing consent. Campaign identifiers are kept in this tab for up to 24 hours after consent; rejecting marketing clears that storage. Consent preferences last up to six months. Minimal internal conversion records prevent repeat conversions; unclaimed events expire for tracking after seven days. Withdrawal stops future measurement; it cannot recall events already received by Meta. Learn more in Meta’s Privacy Policy.
Livestream, clip, and media processing
When you connect a live input to Stitch Factory, your stream is ingested through Cloudflare Stream. When you press CLIP, Stitch Factory captures that moment from the live feed as a clip. Clip metadata and your editing choices (captions, styling, timing) are stored in our database; the rendered video file is stored in Cloudflare object storage (R2).
If you use automatic captions, the audio for that specific clip is processed by Cloudflare Workers AI (an automatic speech-recognition model) to produce an editable transcript. You can edit or remove the generated captions before rendering.
Any image or video you upload as a top-media element or visual overlay is stored in Cloudflare object storage and used only to render your clips as you’ve configured them.
Connected streaming services
YouTube
Connecting a YouTube channel is optional. If you connect one, Stitch Factory uses it to send your live stream to YouTube as a destination you’ve chosen, and to publish clips you schedule to your channel as YouTube Shorts. Connecting YouTube does not publish anything by itself: a clip is uploaded only when you schedule it, at the time you choose. See Google user data below for exactly what Stitch Factory accesses and how it’s handled.
Restream
If you add Restream as a destination, you provide your own Restream server URL and stream key. The stream key is encrypted before storage and used only to send your stream to that destination.
OBS and Streamlabs
Stitch Factory doesn’t connect to OBS or Streamlabs through any account or API. It gives you a server URL and stream key to paste into OBS, or add as a Custom Destination in Streamlabs Desktop — the same way you’d add any other streaming destination. Credentials issued for the OBS Dock and Stream Deck CLIP button are stored one-way hashed, the same way a password would be, and can’t be read back by Stitch Factory once issued.
Google user data
What Stitch Factory accesses
If you use “Continue with Google,” Google shares your name, email address, whether that email address is verified, and your profile picture URL. Stitch Factory uses these to create and sign you in to your account.
If you connect YouTube, Stitch Factory requests the YouTube permission (https://www.googleapis.com/auth/youtube). It needs this permission to send your stream to YouTube and to publish the clips you schedule to your channel, and it uses it, through the YouTube API Services, only to:
- read your channel’s ID and name, so you can confirm which channel is connected;
- create a live broadcast and live stream on your channel and bind them together, so your stream can be sent to YouTube. The YouTube stream key is passed directly to Cloudflare Stream to deliver your stream and is not stored in Stitch Factory’s database;
- upload the clips you schedule to your channel, with the title, description (your caption), made-for-kids setting, and visibility Stitch Factory applies to scheduled posts, and record the resulting video ID and link so you can see what was posted.
Scheduled YouTube uploads
A clip is uploaded to YouTube only when you schedule it with your YouTube channel as the destination. At the scheduled time, Stitch Factory confirms the connected channel is still the one you chose and then uploads that clip’s rendered video through the YouTube Data API. If your YouTube connection has been disconnected or needs to be reconnected, nothing is uploaded and the post is marked as failed.
Stitch Factory does not read your existing videos, comments, subscribers, analytics, or other YouTube data.
How it’s used and stored
Google user data is used only to provide the features you turn on, as described above. We do not sell it or use it for advertising.
YouTube access and refresh tokens are encrypted (AES-GCM) before they are stored and are used only to operate your YouTube connection. The connected channel’s ID and name, the video IDs and links of posts Stitch Factory published, and your YouTube publishing preferences are stored with your workspace.
Sharing
We do not share Google user data with third parties except as needed to provide these features — the YouTube stream key is sent to Cloudflare Stream to deliver your stream, and all Stitch Factory data is stored and processed on Cloudflare’s platform (see Service providers below) — or when required by law or with your consent.
Retention
Stored YouTube tokens are kept until you disconnect YouTube. If you reconnect YouTube instead of disconnecting it, the earlier connection’s encrypted tokens remain stored until you ask us to delete them. Channel details, published video IDs and links, and publishing preferences are kept with your workspace until you ask us to delete them. Google sign-in details are kept for as long as your account exists.
Disconnecting YouTube
You can disconnect YouTube from your workspace at any time. When you do, Stitch Factory asks Google to revoke its access and deletes the stored YouTube access and refresh tokens; the disconnect completes even if Google’s revoke request fails. The record of which channel was connected (its ID and name) is kept with your workspace history. Videos already published to YouTube stay on your channel and are managed in YouTube itself. You can also remove Stitch Factory’s access at any time from your Google Account’s third-party access settings.
Google policies
Stitch Factory’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Stitch Factory uses YouTube API Services. By connecting YouTube, you agree to be bound by the YouTube Terms of Service. Google’s handling of your data is described in the Google Privacy Policy.
Deleting your data
To request deletion of your Google user data or any other personal information, email hello@stitchfactory.app from the address on your account.
How we use information
- To provide the core product: capturing, editing, rendering, and delivering your clips.
- To operate your account, workspace, and beta trial, and retain previous creator application records.
- To send account verification, beta setup, and service-related email, plus optional follow-ups subject to your email preferences.
- To maintain security: detecting abuse, rate-limiting, and recording operational/security events (such as failed render jobs or suspicious credential activity) for troubleshooting and protecting the service.
- To understand aggregate usage of the public marketing site through the first-party analytics described above.
We do not sell your information, and we do not use it for third-party advertising.
Service providers
Stitch Factory runs on Cloudflare’s platform: Workers (compute/hosting), D1 (database), R2 (file storage for clips and uploaded media), Stream (live video ingest), Images, and Workers AI (caption transcription). Account email (verification, invitations, and related notices) is sent through Resend. If you connect YouTube, Google processes that connection as your own YouTube account’s operator; if you connect Restream, your stream data passes through Restream’s own service under its own terms.
Storage and security
Passwords are stored as secure one-way hashes, never in plain text. OAuth tokens (YouTube) and streaming credentials you provide (Restream stream keys) are encrypted at rest. Device credentials for the OBS Dock and Stream Deck CLIP button are stored one-way hashed and cannot be recovered once issued — only reissued. Access to creator and workspace data is scoped to your own account and workspace membership.
Retention
We retain account, workspace, clip, and application information for as long as your account is active and as needed to provide the service. Analytics data is retained in aggregate/session form to support the usage reporting described above. We do not currently commit to a fixed deletion timeline for these categories.
Your choices and rights
- You can disconnect YouTube or Restream from your workspace at any time.
- You can edit or remove auto-generated captions before rendering.
- You may request access to, correction of, or deletion of your personal information by contacting us using the details below.
Children’s privacy
Stitch Factory is intended for use by people 18 years of age or older. We do not knowingly collect personal information from anyone under 18. We require confirmation that you are 18 or older during signup and creator agreement acceptance, but do not independently verify your age automatically; if we learn that someone under 18 has provided us personal information, we will take steps to delete it.
International data processing
Stitch Factory runs on Cloudflare’s global network, which may process and store data in locations other than your own.
Changes to this policy
We may update this policy as Stitch Factory changes, particularly as it moves beyond beta. We’ll update the date at the top of this page when we do.
Contact us
You can reach us at hello@stitchfactory.app, or on the Founding Creator Discord.