alternatives

Published by Floriva · Updated 2026-04-28 · How Floriva checks its guides

After You Export Your Clue Data: What To Do Next

You have your Clue CSV, but your data is still on their servers. Delete the account, file a GDPR request, and move to an on-device tracker.

Exporting your Clue data is the right first step, but it's not the finish line. The export does not delete your Clue account, and your data remains on Clue's servers until you take several more steps. Here's what comes next, deleting the account, filing a GDPR erasure request, reading the CSV, and getting your history into a tracker that stores it on-device.

You exported. Here is what that actually did, and did not do.

Exporting your Clue data is the right first step. It is also frequently where people stop. They assume that having their own copy means the Clue copy is gone. It is not.

Exporting creates a copy for you. The original data remains on Clue's servers in Berlin. Your account is active. Your cycle history is still in their system. If Clue receives a subpoena, your data is still there to produce.

The export is step zero. The actual migration involves five more steps. This guide picks up where the export download left off.

For context on Clue's privacy posture and why some users are leaving despite Clue's clean record, see our Clue alternative overview.

Step 1: Read and parse the Clue CSV

Open the ZIP Clue emailed you. Inside is a CSV (sometimes named something like data.csv or your account email). Open it in Google Sheets, Excel, or Numbers.

The CSV includes columns for date, cycle phase, and logged entries for each day you tracked. Look for rows marked as period or cycle_start. These are the data points you need to seed a new tracker.

Sort the file by date, descending. Note the most recent 3-6 rows where period or cycle start is logged. Write them down or keep the file open. You will enter them into your new tracker in step 5.

Everything else in the CSV (symptoms, mood, energy, flow intensity) is yours to keep for reference. But cycle start dates are all the new app needs for the migration.

Step 2: Delete your Clue account

Open Clue and tap the menu icon (three horizontal lines) in the top-left corner. Go to Settings, then Privacy, then Delete Account.

Clue is GDPR-native, which means the deletion flow involves explicit confirmation steps. Read each prompt and complete each step. The account is not queued for deletion until you reach the final confirmation. Don't close the app partway through.

Deleting the Clue app from your phone is not the same as deleting the account. The app can be uninstalled at any point, but the account and its data remain on Clue's servers until you complete this in-app deletion process.

Step 3: File a GDPR Article 17 erasure request

This is the step most migration guides skip. It matters most for backup deletion.

Email [email protected] with the subject "GDPR Article 17 Erasure Request." In the body:

1. State the email address tied to your Clue account

2. Invoke your right to erasure under GDPR Article 17 (or CCPA Section 1798.105 if you are a California resident)

3. Request explicit confirmation that your data is deleted from active systems, backups, and any derived datasets

Clue has 30 days to respond under GDPR and 45 days under CCPA. Keep the email and any response. This is the legal mechanism that compels purging from backup systems. In-app account deletion alone does not guarantee that backup copies are wiped.

Step 4: Verify the deletion

Wait 48 hours after completing step 2. Open the Clue app or go to helloclue.com and try to log in with your old credentials. A successfully deleted account returns an "account not found" or "invalid credentials" error.

If you can still log in, the deletion did not complete. Return to Settings, then Privacy, then Delete Account and go through the confirmation sequence again. If the problem persists, contact Clue support and reference the date you initiated the deletion.

Step 5: Seed your new on-device tracker

Open the new tracker and go through its onboarding. When it asks for cycle history, enter the last 3-6 cycle start dates from your Clue CSV.

Three on-device trackers cover the Clue migration well:

Floriva is paid, local-first, and polished. Core cycle data stays on your phone. If optional sync is on, only end-to-end encrypted data leaves your device. Check current Floriva onboarding for import options before assuming a Clue CSV can be imported directly.

Euki is free and maintained by a reproductive health nonprofit. No account, no sync, no server.

Drip is free, open-source, and community-maintained. Available on Android.

All three are compared in our private period tracker roundup. For a detailed guide on rebuilding your history after switching apps, see our period history rebuild guide.

Step 6: Secure the CSV, then delete it

While your new tracker is accumulating history, keep the Clue CSV encrypted in a secure location, a password-protected folder or an encrypted app like Signal's note storage. Do not leave it in your Downloads folder.

Once your new tracker has 2-3 recorded cycles and predictions are stabilizing, you can delete the CSV. The data you wanted off a server should not sit unprotected on a local drive indefinitely. Your phone's file manager or Finder can locate and delete the file.

For more on what on-device storage means architecturally and why it changes the subpoena equation, see our on-device storage explainer and our guide on data portability across period trackers.