Privacy & data handling

How ResearchFM handles your data.

ResearchFM turns academic papers into source-reviewed listening releases. This page describes the data flows implemented by the web and mobile clients.

Account and sign-in

Protected features use Google sign-in through Firebase. The service receives the Firebase identity needed to associate your profile, drafts, entitlements, and audit events with your account. Discovery and public catalog browsing can be used without signing in.

Manuscripts, scripts, and audio

Creator uploads, extracted text, scripts, transcripts, author-verification evidence, and generated audio are handled as workspace content. Manuscripts and verification evidence remain private. An approved publication exposes only the release metadata, evidence map, and media intended for that release.

Extracted manuscript text is sent to the configured OpenRouter model for source analysis and script generation. Narration text is sent to the configured OpenRouter audio model. The service keeps these calls server-side; provider credentials are not placed in the browser or mobile app.

Listening and billing

Saved papers, favorites, listening history, queue and resume state, playback preferences, and offline audio are stored on the device for the local library experience. Stripe checkout and Google Play purchases are verified server-side before credits or listener access are granted.

Deletion and questions

For a deletion or data-handling request, email robopioneer.product@gmail.com from the account address, or contact the workspace administrator who manages your ResearchFM account. Requests may require account verification. We do not claim that payment, security, or legally required records can be removed immediately.

ResearchFM does not present generated interpretation as an author conclusion: the product labels source statements, evidence-supported inferences, and system interpretation separately.

Last updated: August 31, 2026 · Support & data requests