Data Deletion Guide

Deletion guidance last updated: July 13, 2026

Reploom has no user account. Most data lives only in the app's private container on your iPhone, so deleting the app removes that local data. Apple Health records and a legacy TestFlight ranking row live in different systems and must be handled separately.

Deletion contact. Email showep12@gmail.com. The legacy ranking removal flow does not depend on email; use the in-app action while the old random ID is still on the phone.

1. Delete local Reploom data

The local app container can include:

workouts, sets, cardio, food logs, and body-composition entries;
daily goals, programs, settings, and local profile values;
Combat Power history and in-app progress; and
a small local cache of Health-derived values used by the interface.

On the iPhone Home Screen or App Library, touch and hold Reploom.
Choose Remove App, then Delete App.
Confirm deletion. This removes Reploom's private local app container from that device.

Offloading an app can preserve its documents and is not the same as deleting it. Use Delete App when your goal is local data removal. The release build excludes the app-managed fitness and health SQLite database directory, including its database, WAL, and SHM files, from iCloud device backup.

2. Revoke Apple Health access or delete Health records

Removing Reploom does not delete a workout or body measurement already written to Apple Health. Apple Health is controlled separately.

Stop future access: open the Health app or iOS Settings, find Reploom under Health access, and disable its read/write permissions.
Delete an existing Health record: locate and remove that record in the Health app.

Reploom cannot remotely change Apple Health permissions or erase an Apple Health record for you after app deletion.

3. AI-assisted logging inputs

Remote AI is off by default, requires an 18+ confirmation, and its consent setting is removed with the local app container. If you enable it and choose workout parsing, voice transcription, typed meal estimation, or meal-photo estimation, the selected input passes through Reploom's Cloudflare Worker to Groq. The Worker application code does not write request bodies or results to D1, KV, R2, or another Reploom application store. There is therefore no Reploom account copy to delete from those stores. Reploom deletes request-time voice recordings and app-cache meal-photo copies after each request or cancellation. If an interrupted app session prevents that cleanup, the next launch sweeps the dedicated recording and selected-photo cache directories.

Groq says inference content is not retained by default. It may temporarily log inputs and outputs for platform reliability or suspected-abuse investigation for up to 30 days, or longer if legally required, and separately retains usage metadata that it says excludes customer inputs and outputs. Reploom cannot remove provider-side records that it cannot identify or control. Reploom's release-candidate Worker configuration disables Cloudflare Worker observability/application logs; this becomes an operational statement only after that exact version is deployed and verified. Cloudflare still processes ordinary network and security metadata under its own service policies. Review Groq's data documentation and privacy policy before enabling Remote AI. The built-in v1 sportswear character uses no personal photo and makes no remote avatar request.

4. Delete a legacy TestFlight ranking entry

Public leaderboards are not available in v1, and v1 submits no new ranking data. An earlier TestFlight build may have stored a handle, random app-generated device ID, Combat Power, weekly gain, grade label, optional crew code, and update time in Cloudflare D1. Deleting the app alone does not automatically remove that old server row.

Before deleting Reploom, open its Settings tab.
Choose the legacy leaderboard data deletion action, if it is shown.
Keep the app open until it confirms that the server row was deleted. Reploom then clears the old handle, crew code, and random ranking ID from local settings.
Continue with Apple Health cleanup and Delete App if you also want all local data removed.

The delete request contains only the random ID already associated with that row. If the action is not shown, the app does not hold a legacy ranking ID. Do not delete the app before using the action: without the locally held random ID, Reploom has no account identity with which to match the row keyed by that ID. A user-chosen public handle in the row may itself be identifying.

5. No account to delete

Reploom does not create an email, password, Sign in with Apple, or social account. Deleting the app therefore removes the local profile rather than closing an online account. The legacy ranking row described above is keyed by a random app-generated ID, but its user-chosen handle may be identifying; it is service data, not a login account.

6. Complete removal checklist

If Settings shows the legacy ranking deletion action, run it and wait for confirmation before deleting the app.
Revoke Reploom's Apple Health read and write permissions.
Delete any Reploom-written Health records you no longer want in the Health app.
Choose Delete App, not Offload App, to remove Reploom's local container.

For questions, email showep12@gmail.com.