Account & Data Deletion
Official self-service deletion request mechanism for the I AM mobile application and account services.
Verify Your Account
This is the official page for permanently deleting an I AM account and associated personal data. To protect account holders, verify that you own the I AM account before deletion can occur.
1. Service & Application Identification
This portal serves as the official, public deletion request mechanism for:
- Application: I AM — A Five-Minute Daily Biblical Identity-Formation Practice
- Package Name:
com.iamin5.app(Google Play Store) - Developer / Service: I AM (iamin5.com)
- Contact:
coachbrian@iam.app
2. How to Request Account Deletion
We provide two distinct, fully functional pathways to delete your I AM account and all associated personal data:
- Web Self-Service (Without App Installed): You can verify your identity directly on this page using your registered email address (via 6-digit one-time code) or Google account. Once verified, confirm deletion to permanently erase your account immediately.
- In-App Self-Service: If you have the I AM mobile application installed on your Android or iOS device, open the application, tap your Account profile icon, scroll to the bottom of the account modal, and select Delete Account.
3. Data Associated with Your Account That Is Deleted
Upon successful identity verification and confirmed deletion, our production systems immediately and permanently delete the following personal data categories:
- Account Credentials & Profiles: Your Supabase authentication record, email address, display name, profile avatar, and security metadata.
- Formation Progress & History: All daily session completions, listening and speaking repetition records, streak counters, and formation milestones.
- Personal Favourites & Library: All saved favourite declarations and custom library collections.
- Reminder Schedules & Notifications: Configured daily reminder times, delivery logs, timezones, and push notification tokens.
- Hardware & Installation Links: Device installation identifiers and app instance registrations linked to your user account.
- Entitlement Records: Membership status mappings and historical user entitlement associations.
4. Data Retained & Statutory Retention Reasons
Consistent with Google Play policies and international data protection laws (including GDPR and UK Data Protection Act), certain non-personal or statutory records are managed as follows:
- Financial & Commercial Records: Where purchases have been completed through Google Play Billing, transactional proof records (such as Google Play purchase tokens, order reference numbers, and taxation amounts) may be retained in an anonymised state for statutory periods required by applicable taxation, accounting, and anti-fraud regulations. These records do not contain passwords or ongoing profile data.
- De-identified Aggregate Telemetry: Historical diagnostic performance logs (such as app open counts) have their user identification keys permanently cleared (set to
NULL) and are retained exclusively in anonymised, aggregate form to monitor platform reliability. - Canonical Application Content: Global biblical identity declarations, scriptural passages, and theological reference texts are public application content and are unaffected by individual user account deletions.
5. Google Play Subscriptions Notice
Important Notice for Premium Subscribers: Deleting your I AM account does not automatically cancel an active Google Play subscription.
In accordance with Google Play Billing rules, subscriptions are billed and renewed by Google Play. If you purchased an active Premium subscription on Android, you must cancel your subscription through Google Play to prevent subsequent renewal charges.
You can view and cancel your Google Play subscriptions at any time via: https://play.google.com/store/account/subscriptions
6. Identity Verification & Security Protections
To protect users against malicious deletion attempts, entering an email address alone will not delete an account. Every deletion request requires cryptographic ownership verification through either a time-limited 6-digit one-time code sent directly to the registered email address, or direct Google OAuth authentication. Privileged service credentials are never exposed client-side.
