Delete your account
You can request deletion of your KlarFort account at any time, with or without the app installed.
KlarFort does not use an email address, name, or social sign-in as its account identity. The service uses a pseudonymous profile derived from the app's trial identifier or a verified store purchase. This page explains how to delete the active data attached to that profile and which security records must remain.
Two ways to delete your account
1. From inside the app (fastest)
If the app is installed:
- Open KlarFort.
- Open Settings.
- Choose Delete Account.
- Confirm. After the server confirms deletion, the app clears its local records and access token.
This is the most direct verification path because the request is authenticated by the pseudonymous access token already stored in the app.
Do not use Reset App Data as a substitute. Reset clears and disconnects the current device, but does not erase the pseudonymous service profile, stored AI outputs, custom rules, or submitted AI response reports. Use Delete Account first and wait for it to succeed before resetting or uninstalling.
2. By email (no app required)
If the app is unavailable, email a deletion request:
Email us
[email protected]Use the subject line "Account deletion request". Do not include financial records, an access token, or a full store purchase token in the initial email.
The email address you use is not tied to a KlarFort account and does not identify the pseudonymous profile. Support will ask for secure purchase or device-context verification sufficient to locate the profile without exposing or deleting another person's data. A store receipt or order may help establish control of a paid profile. If no safe link to a profile can be established, we will explain that rather than act on an unverified identifier.
What is deleted
On a successful authenticated deletion, or after a support request is securely verified, KlarFort removes the following active user-scoped data:
- Any push notification delivery token associated with the pseudonymous profile.
- Stored daily insight notes and the latest continuous-monitoring analysis.
- Server-stored custom rules.
- AI response reports submitted under the profile, including their message UUID, fixed category, and excerpt.
Deletion from inside the app also clears the locally stored access token and local app data, including portfolio records, documents, and chat history. Export anything you need before confirming deletion. The operation is permanent.
What is retained
These narrow security records are deliberately not deleted with active profile data:
- Trial-grant anchor: the raw client-generated UUID is transmitted for grant verification, normalized, and immediately transformed into a full one-way SHA-256 deduplication hash. Only that hash, the platform, trial start and expiration, and derived pseudonymous User ID are retained indefinitely to prevent replay or regrant for the same installation identifier. The raw UUID is not persisted and is not an advertising identifier or device fingerprint. Reset or uninstall may generate a new identifier.
- Subscription anti-replay anchor: a one-way hash of the stable store transaction or purchase identifier, product, tier, expiration, verification time, and first pseudonymous owner is retained indefinitely to prevent the same purchase from being bound to another profile. KlarFort does not retain the raw Play purchase token in this record.
- Daily AI rate-limit anchor: an internal database row ID, opaque pseudonymous User ID, UTC date, and integer request count are retained across deletion and verified recreation for up to 30 days. This generation-independent row prevents the same receipt or lifecycle subject from resetting its current daily AI cap. It contains no prompt, portfolio record, attachment, AI output, or report excerpt.
- Authorization lifecycle record and deletion-recovery ledger: the pseudonymous User ID, deletion time, authenticated token generation, and target deleted generation are retained so every pre-deletion access token remains invalid and erasure can be reapplied after database recovery. The append-only recovery record is written outside the database before active data is erased. An explicit recreation after verified store-purchase restoration marks the profile active under the current token generation; it does not restore erased content.
Security, operational, support, or legally required records may also be retained where necessary for fraud prevention, incident response, request handling, or a legal obligation. KlarFort does not use the retained anti-abuse anchors to rebuild deleted portfolio or AI-output data.
Time frame
An in-app deletion removes active server data as part of the successful request and then clears local app data. Email requests require verification first and are handled within the period required by applicable law. We will tell you if more information or a lawful extension is needed.
Your subscription
Active paid subscriptions are managed by Apple App Store or Google Play, not by KlarFort directly. Deleting your KlarFort account does not automatically cancel a store subscription. To cancel:
- iOS: open Settings → [your name] → Subscriptions, choose KlarFort, then Cancel Subscription.
- Android: open Google Play, then Payments & subscriptions → Subscriptions, choose KlarFort, then Cancel subscription.
If you do not cancel, the store will continue to charge for the subscription on its normal schedule even after the KlarFort account is deleted. Refund requests are handled by the store, not by us.
After deletion
Deleted active profile data and local portfolio data cannot be restored by KlarFort. Hourly database recovery images may physically retain earlier row bytes for up to seven days, but they are not served directly: startup requires the matching external deletion history and reapplies every deletion before a recovered database can accept requests, purging those rows again and keeping old tokens invalid. The email address used to contact support does not create or restore an account. Reinstalling creates local data again. The retained trial hash blocks only replay of the same installation identifier; reset or uninstall may generate a new identifier. The retained purchase anchor prevents a verified purchase from being reused against a different pseudonymous profile.
Questions
For privacy questions or to follow up on a deletion request, write to [email protected]. Detailed practices are described in the full Privacy Policy.