Birth Data is not ordinary preference data.

In AstrologyGround, Birth Data means the birth date, time, and location used to create a natal chart. That chart is the anchor for the live astrology wallpaper.

AstrologyGround is designed so birth data stays local on your device.

Birth Data is not ordinary preference data

A theme color or window size preference is low-trust data. Birth Data is different.

It can feel intimate because it connects directly to a natal chart. A serious astrology product should treat that boundary clearly.

That is why AstrologyGround uses concrete privacy language instead of broad slogans.

What “birth data stays local” means

“Birth data stays local” means the app is designed around keeping the birth date, time, and location on the user’s device.

The product should not need a web account to turn that Birth Data into a natal chart wallpaper.

This matters because the chart is central to the experience. Privacy cannot be a decorative claim attached later.

App Privacy versus Website Privacy

App Privacy and Website Privacy are separate.

App Privacy covers what the AstrologyGround desktop app does with Birth Data, natal chart data, and live transit calculations.

Website Privacy covers the public website, including hosting logs, analytics, legal pages, and future marketing contact surfaces.

On your device Birth date, time, and location
  • Natal chart calculation
  • Chart settings and results
  • Live transit relationship
Public website Does not receive or infer your chart
  • Product information
  • Platform status
  • Privacy-respecting site analytics
App Privacy and Website Privacy are separate boundaries. Core chart calculation stays in the app; the formal details are in the Privacy Policy.

Why local calculation matters

Local calculation is a product proof point. It supports the promise that Birth Data can stay on the device while the wallpaper still uses a real natal chart.

AstrologyGround’s custom astrology engine helps make that possible. The app can calculate the chart experience without turning Birth Data into a web service dependency.

That technical choice serves a human trust question.

What the website can and cannot know

The website can describe the product, show platform status, and use privacy-respecting analytics to understand broad page usage.

The website does not read or infer a birth chart. Website analytics are not App Privacy, and they are not a pipeline into Birth Data. The distinction matters because live transits and natal charts belong to the app experience, not website analytics.

Where to read the formal policy

For the formal boundary, read the Privacy Policy. For the technical product story, read why we built a custom astrology engine.

The live astrology wallpaper guide explains how Birth Data fits into the product category.