Account and Data Deletion

Delete in the app

Sign in as the parent, open Parent Settings, choose Delete account, review the confirmation, and confirm. This is separate from deleting an individual child profile or Explorer, which is available from that profile's management screen.

What account deletion does

ROAMA removes the parent account, associated child profiles and Explorers, gameplay records, refresh sessions, password-reset records, notification token associations and preferences, and related push-delivery records from the application database. The app clears the local active child/Explorer selection after successful deletion.

If the production credential is configured, ROAMA requests deletion of the associated RevenueCat customer. RevenueCat handles its side of the request, which may be asynchronous; completion is not guaranteed by ROAMA. The local deletion steps are not a transactionally atomic database operation, and a database error may require follow-up.

MongoDB Atlas creates daily snapshots retained for 8 days, so removed data may remain in a snapshot until it expires. Records may be retained where applicable law requires it.

Provider deletion and notification-device records

If RevenueCat deletion fails or its server-only credential is unavailable, ROAMA attempts to queue the parent account identifier and retry deletion. A queued identifier is kept until RevenueCat returns success or reports that the customer is not found; retries run while the service is running and pause while it is stopped. There is no fixed expiry for a pending retry. If the retry record cannot be saved, the failure is logged and follow-up may be needed. Local account deletion proceeds independently.

Account deletion removes all push-token associations, notification preferences and activity, delivery receipts, idempotency records and device-permission records for all of the parent's devices. When a logout request includes the current installation's notification-device ID, logging out removes only that installation's push-token association and device-permission record; other devices and parent-level notification preferences and activity remain unchanged. A legacy logout request without a notification-device ID revokes authentication only and does not remove push records. While retained, each device-permission record contains the parent and app-generated device identifiers, permission state, whether another prompt is allowed, and timestamps, with no automatic expiry configured. The app-generated identifier remains in local app storage until that storage is cleared or the app is removed.

Subscriptions

Deleting a ROAMA account does not cancel an Apple App Store or Google Play subscription. Cancel the subscription separately in the store where it was purchased. Account deletion does not itself issue a refund.

Request help by email

If you cannot sign in or use the in-app option, contact the data controller, Kerem Eyüboğlu, at info@roama.tech and request account/data deletion. Where possible, write from the parent account email. Do not include a child's sensitive information. The controller may need to verify account ownership and will handle the request subject to applicable legal obligations.

Profile-only deletion

Deleting an individual child or Explorer is different from deleting the parent account. The app removes that profile's gameplay records and marks the profile record as deleted. No fixed retention period is configured for these individually soft-deleted profile records. Database snapshots follow the 8-day lifecycle described above.