What we hold, and why

The short version

• We hold your account, your projects and the code built for them.
• We use prompts and generated code to improve Ripping's models, with your name and email stripped off and secrets removed. Failed builds and work you undid are not used. You can opt out by emailing us.
• The records inside the apps you build belong to you and your app's users. We store them so the apps work; we do not train on them and we do not read them except to fix a fault you report.
• We never see your card number. Stripe handles payment.
• There is no advertising here, no third-party analytics, and no selling of anyone's data.
• You can export everything and delete your account from Settings.

1. What we collect

Your account. Your email address, and your name and profile picture if you sign in with Google. Passwords are handled by our sign-in provider and stored hashed; we never see them.

What you build. Your prompts, the project files, the code the models write, the notes and design settings attached to a project, versions of each build, and any image you attach to a brief.

How builds went. Which model ran, how long it took, how many tokens it used, what the automatic checks found, and any error. This is what the ledger holds, and it is what tells us whether the product is getting better or worse.

Billing. Your plan, your token balance and usage, and your invoices. Card details go to Stripe, not to us.

Using the site. Ordinary server logs (IP address, browser, pages requested, timestamps) and product events — an account created, a project published, a build finished — kept in our own database.

Things you connect. If you connect a database, GitHub, an email provider or anything else, we store the credentials you give us, encrypted, and use them only for your projects.

What we do not collect. We do not buy data about you, we do not run advertising or third-party analytics trackers, and we do not ask for anything we have no use for.

2. Why we hold it

To run the service you asked for: to build your app, show it in the preview, keep versions so you can go back, host it when you publish, charge you correctly, send you receipts and notices, keep the service secure and stop abuse, and understand where the product fails so it can be fixed. And, as section 3 describes, to improve the models that do the building.

3. Using your work to improve our models

Ripping trains its own AI models on the work done here. This is central to the product, so it is worth being exact about it.

What is used: the prompt you wrote, the project context sent with it, and the code the model produced — but only when that build passed our automatic checks and nothing contradicted it. A build that failed, that you undid, that you regenerated, or that you marked with a thumbs down is not training material.

What is removed first: your name and email are not attached; the row carries an opaque account identifier instead. Anything shaped like an API key, password, token or bearer credential is stripped before storage. Images you attach are not stored with it.

What is never used: the private data inside your apps; output from AI providers whose terms do not allow training; and anything from an account that has asked to be excluded.

Opting out: email support@getripping.com and we will exclude your account from training. Your apps keep working exactly as before.

4. Data inside the apps you build

When someone uses an app you built — signs up, saves a record, uploads a file — that data is stored so the app works. It belongs to you and to them, not to us. We do not train on it and we do not look at it, except when you ask us to investigate a specific problem, or where the law requires it.

If your app collects personal information, you are the one responsible for telling its users what you collect and why. An app published from Ripping needs its own privacy notice; the starter code includes one for you to fill in.

5. Who else processes it

We use other companies to run Ripping. They may only process data on our instructions and for these purposes:

We also share information when the law requires it, to protect someone's safety, to enforce our Terms, or as part of a merger or sale of the business — in which case you will be told before your information moves.

We do not sell personal information and we do not share it for cross-context behavioural advertising.

6. Cookies

We use cookies to keep you signed in and to remember preferences like light or dark mode. That is all. There are no advertising cookies and no third-party tracking pixels, so there is nothing here to consent to beyond keeping you logged in. The Cookie policy lists every one of them by name.

7. How long we keep it

• Your account and projects: until you delete them or close your account.
• Build history and versions: with the project, so you can restore earlier work.
• Training rows: kept as part of the dataset used to train our models, with identifiers removed. Excluding your account stops new rows and removes existing ones from future training sets.
• Billing records: kept as long as tax and accounting law requires, typically seven years.
• Server logs: weeks, not years.
• Backups: deleted data disappears from backups as they age out, normally within 30 days.

8. How we protect it

Traffic runs over HTTPS. Credentials you connect are encrypted before storage. Access to production data is limited to those who need it to run the service. Apps you build run in a sandboxed frame that cannot reach your Ripping session. No system is perfectly secure, and we will not pretend otherwise: if a breach affects your information, we will tell you and say what happened.

9. Your choices

• See and export: your projects can be downloaded as a zip or exported to GitHub at any time; Settings exports your account data.
• Correct: change your name and email in Settings.
• Delete: delete a project, or close your account from Settings, which removes your projects and takes published apps offline.
• Opt out of training: email us and we will exclude your account.
• Disconnect: remove a connected service at any time from Connections.
• Ask us anything: support@getripping.com. We answer privacy requests within 30 days.

10. Children

Ripping is for people 18 and over. We do not knowingly collect information from children. If you believe a child has given us information, write to us and we will delete it.

11. Where it is held

Ripping is operated from the United States and your information is stored and processed there by us and the companies listed above. It is intended for people in the United States; if you use it from elsewhere, you are sending your information to the United States.

12. Changes

If we change this policy in a way that matters — new information collected, a new use, a new company processing it — we will email the address on your account and update the date at the top before the change takes effect.

13. Contact

0DTE Holdings, a Wyoming limited liability company, which operates Ripping. Privacy questions, deletion requests and training opt-outs: support@getripping.com, or by post to 5830 E 2nd St, Ste 7000 #20884, Casper, WY 82609.