Murli One Privacy Policy

Last updated: 6 November 2026

This Privacy Policy applies to Murli One and its associated services on soultosupremesoul.com. The privacy contact for the Murli One operator is rajasekaran.th@gmail.com.

Using Murli One

Murli One provides Murli reading, historical retrieval, audio and source-based study answers. No account creation or sign-in is required. We do not require your name, email address or phone number to read, search or request an answer.

Local searches and information on your phone

FAQ searching, ranking and passage selection run on your phone. A language archive may first be downloaded from our website. Normal local FAQ searches do not automatically send search words or selected passages to us.

The app stores settings, language/font choices, reading positions, bookmarks, Saved passages, question drafts, request references/keys and downloaded content locally. It keeps up to four downloaded answer topics and twenty recent local question-and-language request records; older entries may be displaced. Bundled answers and Saved passages are separate.

Saved and Clear Saved do not upload your saved passages. Clear Saved removes those local passages, not server request records. Refresh content clears cached web resources while preserving local Saved items and request details. Android Clear storage or uninstalling can remove app-private data, including the keys needed to check requests. These actions do not delete server records, exported documents or existing backups.

Android device backup/transfer may include eligible preferences and WebView data, depending on device settings. Native FAQ archive bundles are stored in the app's no-backup location.

Website connections and security records

Opening a Murli, PDF, archive or audio file sends the requested resource address to our website. It can reveal the reading date, language and part. Website infrastructure receives your IP address and ordinary HTTP metadata.

The FAQ request service stores a SHA-256-derived IP record with an hourly bucket and request count to limit abuse. The application does not use that record to infer your physical location. Hashing does not guarantee anonymity. Old hourly buckets are removed when a later new request triggers cleanup; there is no guaranteed hourly deletion job. Website infrastructure can also keep operational/security logs. We have not established a fixed retention period for all infrastructure logs or backups.

Explicit FAQ submissions

Choosing Request a summary sends the question, selected language and a random request key to our website. We retain the question, language, reference, creation time, archive revision and hashed lookup/key records. Checking for an answer sends the reference and key. These keys are for request lookup/deduplication; they are not user accounts or advertising IDs.

Questions are used to prepare and deliver Murli study answers. The operator may read submitted questions and use OpenAI-assisted tools for source research, drafting and review. Questions and selected Murli evidence can therefore be processed by OpenAI. The dedicated FAQ server does not itself call an AI API or send email. Preparation depends on an available authoring environment and has no guaranteed completion time.

Submit only general Murli study questions. Do not include names, contact details, private personal narratives, health or financial records, or information identifying other people. A question can disclose religious beliefs or other personal information if you choose to include it, even though the app does not ask for an identity or religious profile.

Published answers

The current answer-delivery format includes the exact submitted question and language in a published answer file. Anyone who obtains its random-reference download URL can read that file without a request key. The normal status check requires the key, but that does not make the answer file private.

We do not intend personal or identifying narratives to be published as study answers. New answer publication requires a recorded review of the complete file for safe general-study content and verified processing/publication disclosure. A personal question may need to remain on hold rather than be published. This review is not a guarantee that every possible private detail will be detected. Do not submit confidential information.

Missing-Murli requests

A supported missing-reading request sends its reading identity, language, date/part, action and random request key. The service retains request references, timestamps and lookup/security records. It may send the operator a website/email alert with the reading identity and request reference. It does not require a reader email address. This service is separate from FAQ summaries.

Optional speech, exports and external services

Speak invokes the phone's installed speech-recognition provider. That provider may process speech online under its settings and terms. Murli One receives recognised text and does not itself save a raw voice recording. Device read-aloud can use a network-backed voice provider. Listening to a pre-generated Daily MP3 downloads a recording and does not upload your voice.

TXT export saves to the location selected through Android's document picker. Selecting cloud storage can send the exported document to that provider. External apps and websites opened from links have their own privacy practices.

Website hosting processes requests and downloads. Missing-reading alerts pass through website/mail services and the operator's email service. Privacy emails sent to the address above are handled through Gmail. OpenAI-assisted preparation is described above. Actual provider/account settings govern their own retention; this policy does not promise zero retention or apply an API-specific retention rule to the operator's chat account.

Advertising and security

Murli One v25 does not include advertising, advertising-ID collection, analytics or crash-reporting SDKs. Request identifiers are not used for advertising profiles. Hosting logs, website behaviour and chosen external services are distinct from the absence of an app analytics SDK.

The app uses HTTPS for its controlled request routes and blocks cleartext network traffic. This protects data in transit; it is not end-to-end encryption. The operator and processing services can read submitted text, and public answer access is as described above. Absolute security cannot be guaranteed. We do not sell user data through the Murli One app or request service.

Retention and privacy requests

The current service has no automatic age-based deletion of FAQ requests or published answers. Copies may also remain in operator authoring files, request emails, service logs and backups. Proposed 90-day request retention and 30-day log retention are not implemented guarantees and are not the current policy.

You may email rajasekaran.th@gmail.com to ask about your information or request removal. Include the request reference if available and describe the request without adding unnecessary private information. Do not send passwords or private request keys by email. Requests require manual review; there is no in-app server-deletion button or automatic all-copy deletion facility. We may need proportionate verification to avoid deleting another person's request.

We will review what can be removed from operator-controlled records and explain relevant limitations or necessary retention. We cannot remotely remove copies already downloaded by other people, separately exported documents or backups held outside our control. This policy does not promise immediate or fixed-deadline erasure from every backup or third-party system. Local Clear Saved, Clear storage and uninstalling are not server-deletion requests.

Contact and changes

For privacy inquiries: rajasekaran.th@gmail.com. We will update this page when our data practices change. The date above identifies this version.