Privacy
heistclips collects as little as it can.
- Clips you render on the site stay with you. They are cut in your browser from the stream’s public video. We do not receive them unless you press a Post button, which uploads that one clip so it can be sent to the platform you chose.
- Clips cut or posted for you. A clip cut through the connector’s cut_clip tool, or uploaded to be posted, is stored under a random link for up to 72 hours and then deleted.
- YouTube and TikTok posting. If you connect an account, we store the access tokens that platform issues, encrypted, and use them only to upload the clips you ask us to post. On YouTube we request the upload permission alone (youtube.upload): heistclips cannot read your channel, videos or Google account. heistclips’ use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements; it is never sold, used for advertising, or read by people. On TikTok we request your basic profile (display name) and permission to upload and publish videos. Disconnect on the posting page at any time and the tokens are revoked and deleted; you can also remove access in your Google Account or TikTok settings. Posting through heistclips uses YouTube API Services, so the YouTube Terms of Service and Google Privacy Policy apply to what you post there.
- A random browser id. Your browser makes a random id to count free clips and votes. We store a keyed hash of it with a count, nothing else.
- Purchases. Card payments are handled by Stripe. We keep the Checkout Session id as your licence key and a count of clips used. We never see your card.
- Feature requests. What you type on the request board is public on that board, except the optional contact field, which only the builder sees, by email.
- Autopilot queue. If you use the queue we store the channels you watch and which clips you exported or skipped, under a secret link only you hold. An email address or a notification subscription is stored only if you give one, is used only to tell you clips are ready, and is removed when you turn it off.
- Analytics. Vercel Web Analytics (no cookies) and PostHog count page views and tool use so we can see what works.
- MCP server. Calls to heistclips.com/mcp are not tied to any person; cutting and posting use a random account code your assistant passes back. We log which tool was called, whether it worked and how long it took, never its arguments. Tool arguments are used to answer the call; feature requests filed through it are stored like the board above.
Questions or deletion requests: aidan@brickandmortar.dev.