Security
Security
Last updated November 5, 2026. Applies to getripping.com and the Ripping software.
Ripping makes your reels on your own computer, with your own Claude plan. This page explains what runs there, what getripping.com can send it, and how your keys and accounts are kept apart.
Made on your computer
- Your reels and their scripts are made on your own Mac, Windows PC (inside Ubuntu, Windows' own Linux) or Ubuntu computer: by your own Claude Code on your own Claude plan, with your own ElevenLabs and HeyGen accounts if you use them.
- Ripping runs in the background as your own user, in a folder of its own (~/Ripping).
- Writing for your board and Research runs Claude Code with no tools at all, in an empty folder, so it can only write text back. Research's searches get web search and nothing else.
- Screenshots of websites are taken in Ripping's own copy of Chromium with Chromium's sandbox on, never in your own browser.
Your keys and sign-ins
- Claude Code signs itself in on your computer. Ripping never keeps, sees or passes on your Claude login.
- Your ElevenLabs and HeyGen keys stay on your computer: in the Mac's Keychain, or on Ubuntu and Windows PCs in a private file only your user can open. Ripping uses them there to call ElevenLabs and HeyGen, and never sends them to getripping.com.
- Your Instagram connection is kept on getripping.com, with its access token encrypted, so your reels can post while your computer sleeps.
One computer, one account
- Each computer gets its own key when you connect it, and that key works only for your account.
- Only the account's owner can connect a computer, and only from a browser on the same network as that computer. The owner gets an email each time one connects.
- Your computer checks every answer from getripping.com, and refuses any answer meant for another account.
- The account's owner can disconnect a computer or Instagram from Connections at any time. A disconnected computer's key stops working at once.
What getripping.com can send
Your computer only works for your account, and for your own sub-accounts if you have them. getripping.com can send it:
- reels to make: your script or your own recording, your notes, the look and the voice;
- style jobs: your references and notes, with the steps your Claude follows to make the style;
- your own styles, and other members' Public styles once they're approved (below);
- writing and research jobs, reads of public Instagram pages (signed out), and transcripts made with your own ElevenLabs key;
- voice and avatar changes you ask for on your board, like adding a voice, or renaming or deleting one you made;
- Reconnect Claude, which opens Claude's own sign-in page on your computer for you to click Authorize;
- a new version of Ripping (below).
Other members' styles
- Your own styles are made on your computer by your own Claude. They stay in your account unless you make them Public.
- Another member's Public style reaches other members' computers only after Ripping reviews and approves it.
- Its files are frozen and fingerprinted (SHA-256) when it's made, and the approval is tied to those exact files. Your computer installs another member's style code only when it matches those fingerprints.
Updates
- Ripping updates itself between reels, never in the middle of one.
- Since Ripping 0.4.30, every release is signed with a key that never reaches getripping.com, and your computer installs a release only if that signature and the download's SHA-256 fingerprint both check out.
- If a new version doesn't start, Ripping puts the one before back.
- A published version never changes. A fix always comes as a new version.
- Every release and what it changed is listed on Updates.
Keeping Ripping apart
If your main computer holds sensitive work, you can give Ripping a place of its own:
- a separate computer, used only for Ripping;
- an Ubuntu virtual machine. Ripping runs on Ubuntu 22.04 or later, with or without a desktop, on Intel, AMD or Arm, and keeps its keys there in a private file;
- on a Mac, a separate macOS user just for Ripping, with its own home folder and Keychain. Its worker runs while that user is logged in.
Each needs 25 GB free and Claude Code with a Claude plan, like any other computer.
How we work
- We review our own code and servers for security problems. The last full review was on October 28, 2026.
- We notify affected users and the authorities of a security breach as required by law (Privacy Policy, Section 11).
Reporting a problem
If you find a security problem in Ripping or getripping.com, email support@getripping.com with “Security” in the subject. Tell us what you found and how to see it.
This page explains how Ripping works today. It isn't a contract and creates no warranty or obligation: the Terms of Use and the Privacy Policy apply. We may change it at any time.
Ripping