Privacy Policy

This Privacy Policy explains how TempleOS collects, uses, shares, retains and protects personal data. It applies to temple administrators, staff, applicants, devotees and visitors who use TempleOS websites, applications and connected services.

1. Who operates TempleOS

The service is operated by CODE SPECTRUM TECHNOLOGY LLP (LLPIN: ACB-8215; GSTIN: 29AASFC8852C1Z0) from Shop No. 107, D.No. 4-1-24A18, Surabhi Lotus, Brahmagiri Road, Near NH66, Brahmagiri, Udupi – 576103, Karnataka, India.

2. Our data roles

For account administration, billing, product security, support and our own website, CODE SPECTRUM TECHNOLOGY LLP determines why and how personal data is processed and acts as the applicable data fiduciary. For devotee, staff, transaction and temple-operational records entered by a customer temple, the temple determines the purpose and permitted use; TempleOS processes those records to provide the platform under the temple's instructions.

3. Personal data we process

• Account and identity: name, mobile number, email, username, role, authentication events and account status.
• Temple and staff: temple/trust details, addresses, contacts, staff records, permissions and configuration.
• Devotee and family: names, contact details, address, language preference, family relationships and voluntarily provided ritual details such as gothra, rashi or nakshatra.
• Transactions: seva, pooja, donation, hundi, hall, accommodation, inventory, accounting, receipt, invoice and payment-reference records.
• Communications: support requests, email and WhatsApp delivery status, consent/opt-out records and message content where required to provide the requested service.
• Technical and security: IP address, browser/device data, logs, audit trails, terminal identity, cookies and security events.

4. Purposes and permitted processing

Data is processed to create and administer accounts; deliver temple workflows; issue receipts and reports; process and reconcile payments; send requested notifications; provide support; secure and audit the service; prevent fraud; maintain backups; improve reliability; and comply with legal, accounting and tax duties. Where consent is the applicable basis, the request will identify the data and purpose and require clear affirmative action.

5. Consent and communication choices

Consent can be withdrawn through the relevant account settings, by using an unsubscribe or WhatsApp opt-out mechanism, through the responsible temple, or by contacting support. Withdrawal does not invalidate processing already completed and may prevent delivery of a service that requires the data. Transactional messages necessary to complete a requested booking, payment or security action are distinguished from promotional messages.

6. Payments

Payment providers process card, bank and UPI credentials under their own policies. TempleOS receives only the information required to identify, reconcile and support the transaction, such as amount, status, time and gateway reference. TempleOS does not store complete card numbers, CVV, UPI PIN or banking passwords.

7. Cookies and analytics

Strictly necessary technologies support sessions, security and saved preferences. Google Analytics or another non-essential analytics service is loaded on the public website only after the visitor accepts analytics cookies. Details and controls are provided in the Cookie Policy.

8. Sharing and subprocessors

Personal data is shared only as needed with the relevant customer temple, authorised users, contracted technology providers, professional advisers, payment institutions, or authorities where lawfully required. TempleOS does not sell personal data. Provider categories and purposes are listed in the Data Processing & Subprocessor Notice.

9. Retention and deletion

Account and operational data is retained while the service is active and for a limited period afterwards to support export, recovery, disputes and legal compliance. Pending paid-plan registrations may be retained for up to 30 days. Financial, tax and audit records are retained for the period required by applicable law. Rotating backups expire according to the backup schedule. When retention is no longer necessary, data is deleted or irreversibly anonymised.

10. Security and incidents

Safeguards include encrypted transport, role-based access, tenant isolation, audit logging, protected backups, monitoring and restricted administrative access. No system is absolutely secure. Where a personal-data breach requires notice, TempleOS will notify affected customer temples and/or individuals and the competent authority as required by applicable law. Security concerns can be reported through the Security page.

11. International processing

TempleOS primarily operates in India. Some contracted providers may process data in other jurisdictions. Where this occurs, TempleOS applies contractual, organisational and technical safeguards and observes any transfer restrictions notified under applicable Indian law.

12. Children

Children may not independently create administrative accounts. Data about a child may be recorded only by a parent, lawful guardian or authorised temple representative for a legitimate temple service. Required verifiable parental or guardian consent must be obtained before processing that relies on consent.

13. Your rights

Subject to applicable law, an individual may request a summary of personal data and processing, correction, completion, erasure, withdrawal of consent and grievance redressal. Requests relating to a temple's devotee records should normally be submitted to that temple first; TempleOS will assist the temple in responding. Identity may be verified before a request is fulfilled.

14. Grievances and appeals

Submit privacy requests or complaints to support@templeos.in. The acknowledgement, resolution and escalation process appears on the Grievance Redressal page. Statutory rights to approach the appropriate authority remain unaffected.

15. Changes

Material changes will be identified by a new effective date and communicated through the service, email or another reasonable channel. Where a new purpose requires consent, consent will be requested before that processing begins.