RecForMe Privacy Policy

Last updated: 2026-10-16

Current preparation build

RecForMe is in preparation. The foundation build provides settings, optional email sign-in, subscription infrastructure and technical diagnostics. Recording, transcription, speaker identification, memory and action features are not yet implemented. This policy distinguishes current processing from the approved boundaries that future features must satisfy.

Little Crab App operates RecForMe. Contact littlecrabapp@outlook.com for privacy questions.

Local data and planned audio boundaries

The current foundation stores app settings locally. The planned recording and transcription features must keep original audio on the user's Watch and iPhone, transfer audio only between those devices, perform transcription locally, and exclude original audio from cloud ASR, online AI, cloud synchronization and automatic cloud-backup paths. Voice embeddings must remain local by default. These features and backup exclusions are not available or verified in the foundation build. Their implementation must be verified before they ship.

A user's explicit export to another app is a separate user-directed action. Audio retention limits and capacity defaults have not been finalized. The future product must explain expiry, pending processing and unrecoverable loss before removing original audio. Uninstalling an app or losing a device can remove local data; no cloud copy of original audio is promised.

Optional authentication and text synchronization

You may choose email sign-in; an account is not required to view the foundation or use anonymous purchase and restore flows. Authentication processes an email address, verification and session metadata. Cloudflare operates the app-scoped authentication service and sends login email through the shared sending domain.

The synchronization infrastructure is app-scoped on Cloudflare. No product recording or conversation table is registered in the foundation. Future sync may transmit only the text and text-derived records that the user permits. Signing in must not cause original audio or voice embeddings to be uploaded. Sensitive text exclusions and redacted projections must apply consistently to both synchronization and AI input, with controls explained before use.

AI processing

The current build does not send user content to online AI. A Cloudflare-hosted text endpoint is provisioned for foundation checks. A successful infrastructure check is not a shipped content-analysis feature. Before any online AI feature is enabled, the in-app AI Data Use page and this policy must identify the exact text categories, named processors, purpose and on-device data. Unknown retention, training and deletion assurances are not promised. Local playback, export, editing and deletion must not depend on online AI success.

Subscriptions and payment information

Apple and Google process store payments and payment-card information. The app-scoped IAP backend receives transaction identifiers, product, billing period, status and account-claim information needed to verify, restore and manage access. An optional RecForMe account and a store transaction have separate ownership; restoring does not transfer a purchase to a different account.

The IAP service also records account-linked or anonymous installation information: country or region inferred from the network, device model and operating system, app version, device and app language, time zone, and first-seen time. Android may also provide Play installation-source information. These records support subscription operations and service analytics; they are not GPS location or conversation content. Subscription operational notifications may include email, an abbreviated user identifier, transaction and subscription summaries, and this technical profile. They are delivered through our shared notification service to an operator-controlled Feishu group. Cloudflare hosts the app-scoped backend; Feishu provides the operational collaboration service.

Analytics and crash diagnostics

Firebase Analytics and Crashlytics, provided by Google, collect technical app usage and crash information such as version, platform and diagnostic errors. The foundation records a technical foundation_boot event. It does not record conversation text, audio, voice embeddings or recording content in analytics. Future features must keep those contents out of logs and diagnostics too. The corrected foundation disables advertising-identifier support, IDFV collection and ad personalization. Installation identifiers and basic analytics remain enabled; disabling advertising identifiers does not make all telemetry anonymous.

Security, deletion and control

Network services use HTTPS. No network, storage, AI or transcription system is perfect; the product must expose actual saved and synchronized state rather than presenting an unverified success. The settings page provides optional account deletion through the shared services. The corrected test build first requests IAP record and local entitlement-cache cleanup, then synchronization cleanup, and finally account and session deletion. An incomplete cleanup returns a retryable error instead of being reported as successful account deletion. Deleting a RecForMe account does not cancel an Apple or Google subscription; manage recurring billing through the relevant store. No recording or memory data exists in this build. Future deletion must cancel pending work and propagate to related text, memory, indexes and permitted synced copies; those product-specific behaviors remain unimplemented.

For requests without opening the app, see RecForMe account deletion. The app deletion flow does not promise to erase store-held transaction records, aggregate service statistics, independent analytics, operational messages or backups immediately. Applicable retention and separate deletion requests must be reviewed for those services.

Changes and contact

We will update disclosures to match implemented features before enabling them. Use littlecrabapp@outlook.com to ask about access, correction or deletion of information processed by the current service.