Privacy is part of the calendar architecture

A separate account boundary

Every personal resource belongs to the authenticated account The server derives identity from the validated session and does not allow a browser client to choose another user's userId

Private data is not public content

The calendar, history, settings and personal calculations are not SEO pages and are never included in the public sitemap

Subscription access is enforced server-side

When there is no active entitlement, the system does not send private data to the browser and then blur it with CSS Access is stopped before personal information is delivered

Payment cards

TaharaSmart does not store full card numbers Payment-method details are held by the payment provider according to the commercial implementation

PWA without offline storage of the calendar

Installing TaharaSmart on the home screen does not make it an offline-first application and does not introduce persistent offline caching of personal Halachic data