Acknowledgements

Credits & Third-Party Notices

This site is built on other people’s work as well as our own. Every entry below says the same four things in the same place: who holds it, under what terms, where on this site it is used, and what those terms require of us.

39 entries in 10 categories · 36 of them someone else’s work · last reviewed 2026-09-09

SaivaPriest original work

What is ours, stated narrowly — and stated as a claim over EXPRESSION, not over the facts, dates or mathematics the site presents. Anything compiled from a source is cited on the page that uses it and is not claimed here.

Site text, ceremony guides, learning material and the Panchāṅgam implementation

Published here
Held by
Sri Kumar Naganathan Gurukkal (SaivaPriest.com)
Under what terms
All rights reserved, in the expression only
Where it is used
Throughout
What that requires of us
None on us. Reproduction of the writing and design by others requires written permission; the facts, dates and algorithms it presents are free to anyone.

Claimed: the WRITING and the DESIGN — the wording, the arrangement and the presentation. NOT claimed: the astronomical algorithms the Panchāṅgam implements, which are published mathematics credited under Astronomical sources; compiled factual material such as festival dates, temple offering names and historical terminology, which is cited on the page that uses it; public-domain material; and the third-party software, typefaces and scholarship credited in the categories below.

The wording, the arrangement and the visual design of SaivaPriest.com — the ceremony guides, the learning material, the prasādam reference and the presentation of the Panchāṅgam — are published as the site's own work and are all rights reserved.

What that claim does not cover is stated deliberately, because a claim that reaches too far is the one that fails when it matters. It does not cover the astronomical mathematics the Panchāṅgam implements: those are published methods, credited under Astronomical sources, and anyone may implement them. It does not cover festival dates, temple offering names or historical terminology, which are facts, are cited on the page that uses them, and belong to no one. It does not cover public-domain material, and it does not cover the software, typefaces and scholarship credited in the categories below, each of which remains its owner's.

Sri Satyanarayana Katha — Family English Retelling; Ganapathy Homam — Scholar-Priest Companion

Downloadable PDFs
Held by
Sri Kumar Naganathan Gurukkal
Under what terms
All rights reserved; free personal and family devotional use
Where it is used
The ceremony guides
What that requires of us
Each PDF carries its own notice and permitted-use statement on page 1.

Reviewed and approved for publication by Sri Kumar Naganathan Gurukkal on 20 August 2026.

Two documents can be downloaded from the ceremony guides. Both are original work written for this site, and both carry their own copyright notice and permitted-use statement on the first page. They may be printed and shared freely for personal and family devotional use; they may not be republished, sold or reproduced elsewhere without written permission.

Sri Satyanarayana Katha — Family English Retelling is a retelling, deliberately not a word-for-word translation and not a recitation text. It follows the traditional five-chapter narrative in newly written English prose. In preparing it we consulted the Louisiana Folklife Program’s published English presentation of the Katha alongside other references. That page is copyrighted; we credit it as a source consulted and reproduce none of its text.

Ganapathy Homam — Scholar-Priest Companion is a work of family education, not a priest’s ritual manual: it publishes no mantra, count, nyāsa or homa-dravya formula. It names its sources rather than paraphrasing them anonymously, and its suggested reading includes Greg Bailey’s translations of the Gaṇeśa Purāṇa, Alice Getty’s iconographic monograph, and Paul B. Courtright’s Gaṇeśa: Lord of Obstacles, Lord of Beginnings. The last of these is a modern academic study whose interpretive claims have been widely contested, particularly within Hindu communities; the companion lists it as scholarship to be read critically and in context, not as an account of the tradition as devotees hold it.

Both documents were reviewed and approved for publication by Sri Kumar Naganathan Gurukkal on 20 August 2026.

The muhūrtham ruleset

Ships with this site
Held by
SaivaPriest.com
Under what terms
All rights reserved
Where it is used
assets/data/tradition-profile.js — the interpretation layer behind the muhūrtham page
What that requires of us
None on us. It is listed here because the honest statement is what it is NOT derived from.

Not taken from any published almanac, book or website. Every active rule was extracted from material this site already publishes with its basis stated, and each rule records where it came from and whether Sri Kumar Gurukkal has reviewed it.

The interpretation layer — which periods are set aside, which tithis are avoided for beginning something, how Guḷika Kālam is treated — is not derived from any published almanac, book or website. It is held in assets/data/tradition-profile.js, and every active rule in it was extracted from material this site already publishes with its basis stated: the methodology page, this site’s own ceremony catalogue, and the day-quality classification that has been on the homepage since launch. Each rule records where it came from and whether Sri Kumar Gurukkal has reviewed it.

Since October 2026, on the owner’s instruction, the ruleset also carries rules with the status sourced: Tārā Bala, Chandra Bala and Chandrāṣṭamam, the lagna and the houses, eclipse and Saṅkrānti restrictions, planetary combustion, and the nakṣatra, tithi and weekday tables for six rites. They are taken from the classical texts (see “The classical muhūrta texts” below), cited rule by rule and stated in this site’s own words — not copied from any almanac — and they have not been reviewed by Sri Kumar Gurukkal. The elements still recorded as proposed and inactive are named on the muhūrtham page as not evaluated.

Open-source software

Code or data written by other people that reaches your browser through this site. Since v27 there is one: the planetary and lunar series in the Panchāṅgam engine were extracted from the MIT-licensed astronomia package, whose notice is reproduced below as its licence requires. The in-browser assistant was retired on 9 September 2026; its two records are kept, marked retired, because a notice is a record of what was distributed.

astronomia (JavaScript port of Meeus’s Astronomical Algorithms) 4.2.0

Data extracted at build time and shipped inside assets/js/panch.js and assets/js/grahas.js
Held by
Sonia Keys and Commenthol
Under what terms
MIT
Where it is used
The truncated VSOP87D and ELP/MPP02 series and the IAU 1980 nutation table the Panchāṅgam engine evaluates; generated by tools/build_ephemeris_series.js
What that requires of us
Include the copyright notice and the permission notice. Reproduced in full on this page.

The truncated VSOP87D and ELP/MPP02 series and the nutation table the engine evaluates were extracted from astronomia 4.2.0, a JavaScript port of Meeus’s algorithms, under the MIT licence:

The MIT License (MIT)

Copyright (c) 2013 Sonia Keys
Copyright (c) 2016 Commenthol

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

WebLLM (@mlc-ai/web-llm) 0.2.84

Retired 9 September 2026
Held by
the MLC-AI authors
Where it is used
Was loaded from a pinned jsDelivr specifier, and only if the visitor pressed “Enable advanced AI”. Retired with the assistant on 9 September 2026; nothing on this site loads it now.
What that requires of us
Apache-2.0 §4(d) asks that a NOTICE file be reproduced. Checked 17 August 2026: the repository publishes none and none ships in the package, so there is nothing of that kind to reproduce.

The model ran in the visitor's browser through WebLLM (@mlc-ai/web-llm 0.2.84, loaded as a pinned module from the jsDelivr CDN by way of esm.run), Copyright © the MLC-AI authors, licensed under the Apache License, Version 2.0. The model identifier requested was Llama-3.2-1B-Instruct-q4f16_1-MLC. Nothing on this site loads WebLLM now.

Apache-2.0 asks that a project's NOTICE file be reproduced by anyone who redistributes it. We checked on 17 August 2026: the WebLLM repository publishes no NOTICE file, and none shipped in the released package, so there was nothing of that kind to reproduce.

loglevel

Retired 9 September 2026
Held by
Tim Perry
Under what terms
MIT
Where it is used
Was a transitive dependency of WebLLM and reached the visitor only with it. Retired with the assistant on 9 September 2026.
What that requires of us
Retain the copyright and permission notice.

Listed because a removed direct import does not establish that no bundled code remains — this one arrives inside WebLLM.

WebLLM depends on loglevel, Copyright © 2013 Tim Perry, MIT licensed. It reached a visitor's browser only if they enabled the assistant, and only inside WebLLM. With the assistant retired, it reaches nobody.

AI and model technology

This site runs no AI model, and no page asks your browser to download one. The optional in-browser assistant, which offered Meta's Llama 3.2 1B Instruct on request and ran it entirely on the visitor's own device, was retired on 9 September 2026. The record below is kept, marked retired, as the honest history of what this site once offered.

Llama 3.2 1B Instruct 3.2

Retired 9 September 2026
Held by
Meta Platforms, Inc.
Where it is used
Was offered as an optional in-browser assistant until 9 September 2026 — downloaded only if the visitor pressed “Enable advanced AI”, and never on page load. No model is downloaded or run by this site now.
What that requires of us
Display “Built with Llama” prominently (§1.b.i(B)); reproduce the copyright notice; observe the Acceptable Use Policy.

Weights come from the community build mlc-ai/Llama-3.2-1B-Instruct-q4f16_1-MLC on Hugging Face. Llama is a Meta trademark, used solely to satisfy the licence's attribution requirement. This site is not affiliated with, endorsed by or sponsored by Meta. The assistant was retired on 9 September 2026; see provenance/assistant-retired-2026-09-09/ for what it was and why it went.

Built with Llama. Until 9 September 2026 this site offered an optional in-browser assistant. If a visitor pressed “Enable advanced AI”, their browser downloaded Meta's Llama 3.2 1B Instruct and ran it entirely on their own device; nothing typed into it was ever sent to this website or to any server. The assistant has been retired. No page asks your browser to download a model, and this site runs no AI model of any kind.

Llama 3.2 is licensed under the Llama 3.2 Community License, Copyright © Meta Platforms, Inc. All Rights Reserved.

The full licence: llama.com/llama3_2/license · Acceptable Use Policy: llama.com/llama3_2/use-policy

The weights were fetched from the community repository mlc-ai/Llama-3.2-1B-Instruct-q4f16_1-MLC on Hugging Face — a 4-bit quantised build of Meta's meta-llama/Llama-3.2-1B-Instruct, prepared by the MLC-AI project for in-browser use.

Llama is a trademark of Meta Platforms, Inc., named here solely to satisfy the attribution requirement of the Llama 3.2 Community License. This site is not affiliated with, endorsed by or sponsored by Meta.

This notice is kept rather than deleted. It is the record of what this site once distributed, and that record does not stop being true because the feature has gone.

Fonts and icons

Six typefaces, all under the SIL Open Font License 1.1. They are served by Google Fonts; this site does not redistribute the font files. Every icon on the site is now drawn for it — the one borrowed glyph left with the assistant button on 9 September 2026, and its notice is kept below.

The notices, in full, and the SIL Open Font License 1.1 they are given under:

  • Cormorant Garamond — Copyright 2015 the Cormorant Project Authors
  • Marcellus and Marcellus SC — Copyright © 2012 Brian J. Bonislawsky DBA Astigmatic (AOETI), with Reserved Font Name “Marcellus”
  • Spectral — Copyright 2017 The Spectral Project Authors
  • Noto Serif Devanagari — Copyright 2022 The Noto Project Authors
  • Noto Sans Tamil — Copyright 2022 The Noto Project Authors
  • Noto Sans Telugu, Noto Sans Kannada and Noto Sans Malayalam — Copyright 2022 The Noto Project Authors. Named in the stylesheets as fallbacks only; never fetched, and shown only if your own device already has them.

Cormorant Garamond

Served by Google Fonts
Held by
the Cormorant Project Authors (2015)
Where it is used
Display type
What that requires of us
Retain the copyright and licence notice.

Marcellus and Marcellus SC

Served by Google Fonts
Held by
Brian J. Bonislawsky DBA Astigmatic (AOETI), 2012
Where it is used
Headings and small-caps labels
What that requires of us
Retain the notice AND the Reserved Font Name “Marcellus” — a derivative may not use that name.

Spectral

Served by Google Fonts
Held by
The Spectral Project Authors (2017)
Where it is used
Reading text
What that requires of us
Retain the copyright and licence notice.

Noto Serif Devanagari, Noto Sans Tamil (loaded); Noto Sans Telugu, Kannada, Malayalam (named as fallbacks only)

Served by Google Fonts
Held by
The Noto Project Authors (2022)
Where it is used
Indic scripts. The three fallback families are never fetched — they appear only if the visitor's own device already has them.
What that requires of us
Retain the copyright and licence notice.

Feather Icons — the message-square glyph

Retired 9 September 2026
Held by
Cole Bemis, 2013–2023
Under what terms
MIT
Where it is used
Was the glyph on the assistant button. Retired with the assistant on 9 September 2026; no Feather icon is used on this site now.
What that requires of us
Retain the copyright and permission notice.

Every other SVG on this site was checked against Feather and matches nothing in it — the rest were drawn for this site in the same idiom.

The square speech-bubble icon on the assistant button was message-square from Feather Icons, Copyright © 2013–2023 Cole Bemis, MIT licensed. It left the site with the assistant on 9 September 2026. Every other small line icon here was drawn for this site in the same idiom, and was checked against Feather to be sure.

Astronomical and scientific sources

Where the Panchāṅgam numbers come from. Algorithms are facts and cannot be owned, but a reader checking the numbers deserves to know their source — and to know that no commercial Panchāṅgam website is consulted, scraped or compared against, and none ever has been.

Jean Meeus, Astronomical Algorithms (Willmann-Bell), ch. 25 and ch. 47

Method, implemented here
Held by
Jean Meeus / Willmann-Bell
Under what terms
Cited as scientific method; periodic terms reproduced as astronomical data
Where it is used
assets/js/panch.js — lunar latitude, rising and setting; the ΔT and nutation formulation
What that requires of us
Accurate citation. The implementation is our own; no code was copied.

Since v27 the Sun's and Moon's longitudes come from VSOP87D and ELP/MPP02 (below); Meeus's methods remain for latitude, rise and set, and the reductions.

Since v27 the Sun's and Moon's longitudes come from VSOP87 and ELP/MPP02 (below). The engine still uses the methods of Jean Meeus, Astronomical Algorithms (Willmann-Bell), for the Moon's latitude, rising and setting, ΔT and the reductions; the earlier abridged series of chapters 25 and 47 are kept in assets/js/panch.js only for comparison. The implementation is our own work. With gratitude to Jean Meeus, whose book made this kind of calculation possible for everyone.

ELP-2000/82 lunar theory

Method, cited
Held by
M. Chapront-Touzé and J. Chapront
Under what terms
Cited as scientific method
Where it is used
By way of Meeus's abridgement, in the lunar series
What that requires of us
Accurate citation.

Espenak & Meeus (2006), Polynomial Expressions for Delta T, NASA Eclipse Web Site

Method, implemented here
Held by
Fred Espenak and Jean Meeus / NASA
Under what terms
Cited as published scientific method
Where it is used
assets/js/panch.js — the ΔT term added 2026-09-07
What that requires of us
Accurate citation.

Added when measurement showed every tithi boundary was landing about 81 seconds late for want of this term. Since v27, 2005–2030 uses the IERS observed and predicted values, joined to the polynomial at 2030.

Lahiri (Chitrapakṣa) ayanāṃśa

Method, implemented here
Held by
Published standard
Under what terms
Cited as method
Where it is used
assets/js/panch.js — the OFFICIAL definition since v27: 23°15′00.658″ true at 1956-03-21 0h TT, IAU 1976 precession, true = mean + Δψ
What that requires of us
Accurate citation.

Since v27 the ayanāṃśa is the official Lahiri definition of the Indian Astronomical Ephemeris and the Rashtriya Panchang — 23°15′00.658″ true at 21 March 1956, 0h TT, carried by the IAU 1976 precession, true = mean + nutation — not an approximation. See the Panchāṅgam methodology page.

JPL Development Ephemeris DE421

Build-time check only
Held by
Jet Propulsion Laboratory, California Institute of Technology / NASA
Under what terms
Public domain (US Government work)
Where it is used
tools/oracle/de421_transitions.py and tools/verify_ephemeris.js — every tithi, nakṣatra, yoga, karaṇa and saṅkrānti of 2026–2028 is checked against it on every build
What that requires of us
None. Cited because being checkable matters.

Folkner, Williams & Boggs (2009), IPN Progress Report 42-178.

Every build checks the engine against JPL DE421, the Jet Propulsion Laboratory's numerical ephemeris: all 5,622 tithi, nakṣatra, yoga and karaṇa transitions and the 36 saṅkrāntis of 2026–2028 agree to within a few seconds (tools/verify_ephemeris.js). The reference values were computed once with JPL's published ephemeris and are stored with the site's build tools.

IAU 1980 theory of nutation

Method, implemented here
Held by
International Astronomical Union
Under what terms
Cited as scientific method
Where it is used
assets/js/panch.js — nutation in longitude
What that requires of us
Accurate citation.

ELP/MPP02 lunar theory, DE405 fit

Truncated series, shipped
Held by
J. Chapront and G. Francou, Observatoire de Paris
Under what terms
Cited as scientific method; series reproduced as astronomical data
Where it is used
assets/js/panch.js — the Moon's longitude since v27
What that requires of us
Accurate citation.

Chapront, J. & Francou, G. (2003), Astronomy & Astrophysics 404, 735.

VSOP87 planetary theory (VSOP87D)

Truncated series, shipped
Held by
P. Bretagnon and G. Francou, Bureau des longitudes / IMCCE
Under what terms
Cited as scientific method; series reproduced as astronomical data
Where it is used
assets/js/panch.js (the Sun) and assets/js/grahas.js (Mercury … Saturn)
What that requires of us
Accurate citation.

Bretagnon, P. & Francou, G. (1988), Astronomy & Astrophysics 202, 309.

NOAA solar position algorithm

Build-time check only
Held by
US National Oceanic and Atmospheric Administration
Under what terms
Public domain (US Government work)
Where it is used
tools/verify_panchangam.js — an INDEPENDENT second implementation used only to check the engine on every build
What that requires of us
None. Cited because being checkable matters.

Since 2026-08-31 the engine is checked, on every build, against a second and independent implementation: the NOAA solar position algorithm, written out separately in tools/verify_panchangam.js from the published equations rather than shared with panch.js. Sunrise and sunset agree to better than a tenth of a minute across nine dates and locations. The Moon is checked against physical constraints — the synodic and sidereal periods, and the physically derived bounds on tithi length — rather than against a second copy of the same series, which would prove nothing. No commercial Panchāṅgam website is consulted, scraped or compared against, and none ever has been.

Northern-California Panchāṅgam references

Consulted, not reproduced
Held by
Various published almanacs
Under what terms
Dates are facts and are not anyone's property; the almanacs made the checking possible
Where it is used
The festival and observance calendar, anchored on Fremont
What that requires of us
Say honestly how each date was arrived at. Every date carries an internal validation grade and the calendar states it in plain words.

A date is either validated against a Northern-California Panchāṅgam source, derived for the Fremont anchor from tithi and nakṣatra rules, or regional and organiser-dependent — in which case the entry asks you to check with your temple.

Festival and observance dates are compiled for the Fremont / Bay Area anchor and checked against Northern-California Panchāṅgam references. Every date carries an internal validation grade. Open a date on the calendar and it tells you in plain words how that date was arrived at — validated against a Northern-California Panchāṅgam source, derived for the Fremont anchor from tithi and nakṣatra rules, or regional and organiser-dependent, in which case the entry also asks you to check with your temple. Dates are facts, not anyone's property, but we are glad to say that published almanacs made the checking possible. Sources for the prasādam reference are listed on that page.

IANA Time Zone Database — zone1970.tab and the northamerica file

Data, reproduced here
Held by
IANA / the tz database contributors
Under what terms
Public domain
Where it is used
assets/data/us-zones.js — the 29 IANA zones the United States uses, each with the database's OWN representative coordinates and region description, and the state-to-zone table with its county exceptions
What that requires of us
None in law: the database's maintainers place it in the public domain. Cited because a visitor is entitled to know that the zone list and the reference points are the authoritative ones and not a hand-typed approximation.

Added 4 October 2026. The zone data shipped in Gate 10 and was not recorded here at the time, which is exactly the omission this manifest exists to prevent; the gap is closed rather than backdated. Offsets are never taken from this file — they are read from the platform's own zone rules by Intl at the instant in question. What is reproduced is the LIST and the reference points.

IAU SOFA (Standards of Fundamental Astronomy), through the pyerfa package

Development only, not distributed
Held by
International Astronomical Union, SOFA Board; pyerfa: the Astropy project
Where it is used
tools/oracle/erfa_lagna.py computed 400 reference ascendants; tools/verify_muhurtham_checks.js checks the site's lagna against them on every build
What that requires of us
Credit as a verification reference. No SOFA or pyerfa code is shipped, so no redistribution terms apply.

The rising sign (lagna) the muhūrtham finder uses is checked on every build against 400 reference ascendants computed with the International Astronomical Union's SOFA library (through pyerfa) at three places across 2026–2028; the largest difference is under half a minute of arc (tools/verify_muhurtham_checks.js). SOFA was used only to make the reference values; none of its code is part of this site.

Scholarly and editorial references

Published scholarship this site relies on, names rather than paraphrases anonymously, and in one case is licence-bound to credit by name.

Andrea Gutiérrez, “Jewels Set in Stone”, Religions 9(9):270 (2018)

Cited, not reproduced
Held by
Andrea Gutiérrez
Under what terms
CC BY 3.0
Where it is used
The prasādam reference — the most-used scholarly source, supporting 15 record fields
What that requires of us
CC BY PERMITS the reuse but REQUIRES attribution by name. Cited with author, journal, licence and DOI.

Louisiana Folklife Program — published English presentation of the Satyanārāyaṇa Katha

Consulted, not reproduced
Held by
Louisiana Folklife Program
Where it is used
Consulted while writing the family retelling
What that requires of us
Credit as a source consulted. NONE of its text is reproduced.

Paul B. Courtright, Gaṇeśa: Lord of Obstacles, Lord of Beginnings

Named, not paraphrased
Held by
Paul B. Courtright
Under what terms
Listed in suggested reading only
Where it is used
The Gaṇapati Homam companion's bibliography
What that requires of us
Named, not paraphrased.

A modern academic study whose interpretive claims have been widely contested, particularly within Hindu communities. Listed as scholarship to be read critically and in context, not as an account of the tradition as devotees hold it. The same bibliography names Greg Bailey's translations of the Gaṇeśa Purāṇa and Alice Getty's iconographic monograph.

Wikipedia, “Tamil calendar”

Consulted; facts used, prose not reproduced
Held by
Wikipedia contributors
Under what terms
CC BY-SA 4.0
Where it is used
assets/js/panchangam-extra.js — the twelve Tamil solar month names and their order, the rule that the months follow the Sun’s shift from one rāśi to the next, the six ṛtus with their month pairs, and the anchor for the 60-year cycle (2026–2027 is Paraapava, the fortieth)
What that requires of us
CC BY-SA requires attribution and share-alike FOR THE TEXT. No sentence of it is reproduced — what is used are names, an order and a date correspondence, which are facts and not expression. Attributed anyway, with the consultation date, because a reader deciding whether to trust a year name is entitled to know it rests on one general reference and not on a traditional almanac.

This is the weakest source behind any field on this site, and the field it supports — the Varuṣam — is marked single-source on the page and in the review checklist rather than presented like the computed fields beside it.

The classical muhūrta texts, in the translations consulted

Cited, not reproduced
Held by
Nārada Purāṇa, tr. G. V. Tagare (Motilal Banarsidass); Bṛhat Saṃhitā, tr. N. Chidambaram Iyer (1884); Agni Purāṇa, tr. N. Gangadharan; Sūrya Siddhānta, tr. E. Burgess (1860); Dharmasindhu, condensed English, Sri Kanchi Kamakoti Peetham; P. V. Kane, History of Dharmaśāstra vol. V
Under what terms
The Sanskrit texts are in the public domain; the modern translations are copyrighted and were consulted only
Where it is used
The sourced rules of the muhūrtham ruleset (assets/data/tradition-profile.js, status 'sourced') and the finder that applies them (assets/js/muhurtham-checks.js, muhurtham.html)
What that requires of us
Credit as sources. The rules are paraphrased and cited by chapter and verse; NONE of the translations' text is reproduced.

The muhūrtham finder's sourced rules — the houses from the lagna, Jupiter and Venus combustion, eclipses, saṅkrānti, the nakṣatras, tithis and weekdays for each rite, and the birth-star checks — are taken from the classical texts and cited by chapter and verse on each rule. They were read in the translations named above, through Wisdom Library and the Kanchi Kamakoti Peetham's site; the rules are stated in this site's own words and no translation is quoted. They have not yet been reviewed by Sri Kumar Naganathan Gurukkal.

Tamil calendar publishers consulted for the daily-sheet fields

Consulted, not reproduced
Held by
Each publisher listed on the Panchāṅgam page under “Sources for the Tamil daily fields”
Under what terms
Copyrighted; consulted only
Where it is used
The Gowri names, Yōgam, Sūlam and parikāram, Chandrāṣṭamam, Kari nāḷ, Nōkku and Agni Nakṣatram rows on panchangam.html (assets/js/tamil-daily.js)
What that requires of us
Credit as sources consulted. Traditional tables were compared across publishers and described in this site's own words; no almanac, page or layout is reproduced. None is affiliated with this site or endorses it.

Platforms and services

Third parties that receive data when you use a particular feature. What each one gets is set out on the privacy and cookies pages.

Cal.com scheduling embed

Third-party service
Held by
Cal.com, Inc.
Under what terms
Service terms
Where it is used
The final step of the request wizard
What that requires of us
Disclose that the wizard summary — including the free-text box — is passed into the embed. privacy.html and request.html both say so.

Booking is handled by Cal.com, an independent scheduling service — see our privacy page.

Google Fonts

Third-party service
Held by
Google LLC
Under what terms
Service terms; the faces themselves are OFL
Where it is used
Serves the typefaces listed above
What that requires of us
Disclosed in privacy.html and cookies.html.

Google Analytics and Microsoft Clarity

Only where enabled and consented to
Held by
Google LLC; Microsoft Corporation
Under what terms
Service terms
Where it is used
Measurement
What that requires of us
Run only on consent, and say so. cookies.html does.

Where enabled and consented to, Google Analytics and Microsoft Clarity are used for measurement; see our cookies page.

Media and photography rights

Every photograph and drawn mark on this site is its own. No stock library, no third-party photograph and no third-party illustration is used anywhere — the sitewide provenance audit of 17 August 2026 looked for them and found none.

Photographs of Sri Kumar Gurukkal

Published here
Held by
Supplied by Sri Kumar Naganathan Gurukkal
Under what terms
All rights reserved; not licensed for reuse
Where it is used
The homepage, the About page and the request pages
What that requires of us
None on us for publication here. They are not licensed for reuse, and we answer any query about a photograph at gurukkalkumar@gmail.com.

Recorded as SUPPLIED rather than as owned outright: copyright in a photograph belongs to whoever took it unless it was assigned in writing, and being the person pictured does not by itself transfer it. The photographer is not recorded for these images. They are published with the subject’s consent, which is what governs their use here; a reuse licence would need the photographer’s.

Photographs in the lineage account, including the portrait of Sri Pichai Sivachariyar

Published here
Held by
Supplied by Sri Kumar Naganathan Gurukkal
Under what terms
All rights reserved
Where it is used
about.html — the account of Gurukkal's teacher and lineage
What that requires of us
Publish only what the family is content to have published, and correct it on request.

These are personal photographs of named people, published as part of a biographical account rather than as decoration. If you are pictured, or represent someone who is, and would rather a photograph were not here, write to us and it will be removed.

The site emblem, favicon and line icons

Ships with this site
Held by
Drawn for SaivaPriest.com
Under what terms
All rights reserved
Where it is used
The header, the browser tab and small labels throughout
What that requires of us
None on us.

One glyph on this site was not drawn for it — the message-square icon from Feather Icons, which was the mark on the retired assistant button. It is credited under Fonts and icons and is no longer used on any page.

Trademarks and non-affiliation

Names used descriptively, to say where something comes from. None of them implies a relationship. SaivaPriest.com is an independent reference and is not affiliated with, endorsed by, sponsored by or connected to any of the organisations named on it.

Temples named on this site

Named for reference
Held by
The respective temples and their trusts
Under what terms
Named for reference only
Where it is used
The temple and prasādam reference pages
What that requires of us
Every temple page carries a non-affiliation notice. Nothing here implies endorsement by any temple.

Temple names are used descriptively, to say where an offering comes from. SaivaPriest.com is an independent reference and is not affiliated with, endorsed by or connected to any temple or its administering body. Temple names and marks belong to their institutions.

Tirupati Laddu — Geographical Indication no. 121

Named, not claimed
Held by
Tirumala Tirupati Devasthanam
Under what terms
Registered GI, class 30, on the register to 30-03-2028
Where it is used
prasadam/laddu.html
What that requires of us
State that SOMEONE ELSE holds the right; scope it to Devasthanam-made laddu; disclaim any claim, licence or connection. No recipe is published.

Palani Panchamirtham, GI 550, is treated the same way on its own page.

Llama, WhatsApp, Google, Microsoft and Cal.com

Named for reference
Held by
Meta Platforms, Inc.; Google LLC; Microsoft Corporation; Cal.com, Inc.
Under what terms
Trademarks of their owners
Where it is used
Wherever the corresponding technology or service is described
What that requires of us
Use nominatively, to identify the thing itself, and never in a way that suggests sponsorship or endorsement.

WhatsApp and Llama are trademarks of Meta Platforms, Inc. Every mark named on this site is used nominatively — to identify the thing itself — and never to suggest that its owner sponsors, endorses or is connected to SaivaPriest.com.

Corrections

If we have used your work and got the credit wrong, or missed it, please write to gurukkalkumar@gmail.com and we will fix it.

That includes a photograph you appear in, a source you would rather saw cited differently, and a licence obligation we have read too narrowly. Corrections are made on this page and dated.

Last reviewed: 2026-09-09. This register is generated from assets/data/third-party-notices.json, and the build fails if a notice on it disappears.