Private by default, clear when data leaves your device

Who is responsible for your information

The Vedic Sky Clock product owner is the data controller for personal data processed by the service. For privacy questions or to exercise your data-protection rights, email [email protected].

What Vedic Sky Clock stores

Your selected current place and your birth profile are saved in your browser's local storage so the app can remember them on that device. The birth profile can include an optional name, birth date, birth time, birthplace, coordinates and time zone.

Vedic Sky Clock does not currently operate a user account system that uploads that saved profile to a Vedic Sky Clock account database.

Place and time-zone lookups

Some features need an external lookup. Those requests go directly from your browser to the relevant service. They are not the same as saving your profile in a Vedic Sky Clock database.

• Using device location asks your browser for coordinates only after you press the location button and approve the browser permission. Those coordinates may then be sent to BigDataCloud to resolve a readable locality name.
• Manual current-place search sends the place name you type to Open-Meteo's geocoding service.
• Birthplace search sends the place name you type to OpenStreetMap's Nominatim service. After you choose a result, coordinates may be sent to TimeAPI to identify the time zone.
• The website itself is hosted through Cloudflare Pages, so normal web requests can expose network information such as IP address and request metadata to the hosting infrastructure.

Information used by the private calculation service

When you use the application, a reading request sends the requested date and time, the selected current-place latitude and longitude, its time zone and the chosen reading type to Vedic Sky Clock's service hosted on Cloudflare. Day, Week and Month views make several such requests.

Personal readings also send two values calculated on your device: your natal Nakshatra index and natal Moon-sign index. Your saved name, birth date, birth time and birthplace record are not included in these reading requests. The service uses the supplied values to return the requested reading; application code does not persist request bodies or include these values in analytics.

To limit automated requests, the hosting gateway derives a SHA-256 key from the connection IP address and sends that key and the reading type to its private rate-limit service. This is a network-derived identifier, not an anonymous identity or a saved birth profile. People sharing a network share an allowance. A private Cloudflare counter stores only request counts and time-window boundaries, with deletion scheduled when its last window expires (within one minute). Expired counts stop applying immediately; cleanup can be delayed by the provider. Cloudflare recovery history may retain previous counter states for up to 30 days. No reading body or birth value is stored in this counter. Normal hosting metadata remains subject to Cloudflare's policies.

The public beta sends calculation requests only when application features need a sky reading. The fail-closed maintenance rollback serves static information pages and makes no calculation requests.

Anonymous evidence about how the product works for people

When product observability is enabled, Vedic Sky Clock sends a deliberately small set of anonymous product events to PostHog's EU service. These events show which main product view was reached, the previous view, a broad time-on-view bucket, whether the initial location gate was completed, anonymous client-error fingerprints and any feedback you deliberately submit.

The telemetry does not include your saved place name, coordinates, time zone, birth profile, birth date, birth time or name. Vedic Sky Clock does not create a PostHog person profile for these events and does not save an analytics identifier in cookies, local storage or session storage. A random identifier exists only in memory for the current page runtime so events from one visit can be understood as a sequence; reloading creates a new identifier.

GeoIP enrichment is disabled and a non-routable placeholder IP is supplied with each event so the connection IP is not copied into the stored event payload. PostHog still receives the connection at network level to deliver the request.

If you use the Feedback control, the text you type is transmitted only when you press Send feedback. The form asks you not to include birth details, a precise location, contact information or other personal information.

Why information is used

Location is used for place-dependent sky calculations such as the local horizon, sunrise and sunset. Birth information is used to calculate a personal natal reference and relative Vedic timing measures. Browser storage remembers information you deliberately enter or select so you do not have to re-enter it on every visit.

Where Vedic Sky Clock processes technical request data, lookup data, anonymous product events or submitted feedback, it relies on legitimate interests under UK data-protection law: providing the feature you requested, operating and securing the service, diagnosing faults, and improving whether the product is understandable and useful. These interests are limited by the local-first design, data minimisation, non-persistent analytics identifiers, disabled analytics profiles and GeoIP enrichment, and the exclusion of birth and precise-location data from telemetry.

Information may also be processed where necessary to comply with a legal obligation, including responding to valid data-protection requests. Vedic Sky Clock does not use the saved birth profile or selected place for advertising, cross-site tracking or solely automated decisions with legal or similarly significant effects.

How long information is kept

• Local browser data remains on that browser until you clear it, your browser removes it, or you use an available in-app clear or reset control. Vedic Sky Clock cannot retrieve or remotely delete this local copy.
• PostHog product events and deliberately submitted feedback are retained for no longer than 12 months, then deleted or anonymised. The short-lived analytics identifier itself is discarded when the page runtime ends.
• Privacy correspondence is normally retained for up to six years after the matter closes where needed to demonstrate compliance or handle legal claims.
• Cloudflare and lookup providers may retain technical request information under their own retention policies.

In the public beta, Your data provides in-app controls to inspect the presence of and delete Vedic Sky Clock records stored in this browser. My Sky also provides local-data controls. If the site is temporarily serving the no-script maintenance rollback, you can still remove those records through your browser's site settings.

No advertising storage or analytics cookies

Successful sky readings may be reused in temporary browser memory for up to five minutes to reduce repeated requests. The cache is limited to 256 readings, is cleared when the page reloads, and is not written to browser storage or shared with analytics.

Vedic Sky Clock uses browser local storage for requested product functionality, including remembering your chosen place, birth profile, teaching preferences, first-run choice and selected lookup results or time-zone values. Anonymous product observability does not write its runtime identifier to browser storage and does not use analytics cookies. The application does not use Vedic Sky Clock storage keys for behavioural advertising or cross-site tracking.

Services involved in delivering Vedic Sky Clock

Cloudflare hosts the website, private calculation service and rate-limit service. PostHog EU receives the limited observability events described above. BigDataCloud, Open-Meteo, OpenStreetMap Nominatim and TimeAPI receive a lookup only when you use the relevant feature. When your browser contacts a provider directly, that provider may process technical information such as your IP address under its own privacy notice.

Providers may process information outside the UK or European Economic Area. Where Vedic Sky Clock appoints a processor, appropriate contractual safeguards are used where required. Direct lookup providers may act under their own terms and safeguards. Vedic Sky Clock should therefore be understood as local-first, not completely offline.

Data-protection rights and complaints

Depending on the circumstances, you may have rights to be informed; obtain access to personal data; correct inaccurate data; ask for deletion or restriction; object to processing based on legitimate interests; and receive data you provided in a portable form where the legal conditions apply. These rights are not absolute. Because Vedic Sky Clock's analytics is deliberately anonymous and non-persistent, it may not be possible to identify a particular event as yours without collecting additional information.

To make a request, email [email protected]. You will normally receive a response within one month. You may also complain to the UK Information Commissioner's Office at ico.org.uk/make-a-complaint. Please contact Vedic Sky Clock first if you are comfortable doing so, so there is an opportunity to resolve the concern.

Last updated: 22 September 2026.