Frequently Asked Questions

No. Om Saravana Bhava is an independent devotional and educational platform. A page will state explicitly when information comes from an official temple or authority.

No complete-all-songs claim is made. The Song Library separates verified full-song records, reviewed extracts, source registers and requested titles that still need edition and rights evidence.

A literary identity or source may be known while the complete redistribution-safe text is not yet verified. Such pages remain source registers or partial-reviewed records rather than filler.

It is a separate learner field based on the canonical Tamil text. It may adjust word spacing and punctuation only after human comparison; it never silently replaces the source wording.

Only media explicitly labelled documentary photography should be treated as real-world photography. Current devotional illustrations and interface art are labelled as such.

Human recordings require ownership, licence or permission evidence. When permitted, device read-aloud may be offered from reviewed Tamil text and is labelled separately from a human recording.

The current governed search and command palette operate locally in the browser using static indexes. A remote generative service is not claimed by these features.

They are designed as browser-local data. They are not claimed to sync to an account or cloud service. Use Personal Data tools to export or restore supported datasets.

Compatible browsers may offer PWA installation after the site and service worker have loaded. The Apps page shows the verified web-app route and withholds native-store links until official URLs are recorded.

Legacy URLs are preserved for continuity and evidence. The governed route directory and platform hubs identify current canonical experiences; release-numbered pages are not automatically treated as core devotional content.

Use the Corrections page to prepare a structured request with page URL, current issue, proposed correction, source and rights note. The template is generated locally.

No bulk deletion is part of the recovery programme. Files are classified first. The public Pages artifact includes governed routes and dependencies, while internal evidence remains preserved in the repository.