GeoLira Observatory

Measurement

Privacy Policy

Privacy Policy is a dedicated GeoLira view for this part of the observatory. It combines the route-specific interface with the same source, freshness, privacy and evidence boundaries used across the platform.

Foundation

GeoLira separates private account data, anonymous community participation, operational delivery data and public scientific content. Data collection is minimized by feature.

This is the BUILD_ONLY legal and privacy baseline. Operator identity, contact details and jurisdiction-specific production notices must be completed at deployment before production activation.

Private account data

Private My-area data is owner-scoped through WordPress authentication and private REST responses use no-store caching.

  • Personal Journal entries are private to the authenticated owner.
  • Dreams and synchronicities entries are private to the authenticated owner.
  • Meditation sessions and the meditation Telegram web-account link are private owner-scoped data.
  • The My Data page provides a complete private-data export and DELETE_ALL_MY_DATA workflow for the private domains currently implemented.

Anonymous participation

Public participation features do not attach a WordPress owner ID to the submitted application record.

  • Community Check-ins use anonymous records and a one-time deletion credential.
  • Global Intentions use anonymous records and return a one-time deletion token. The server stores only the token hash.
  • Sacred-place editorial suggestions use anonymous records and return a one-time deletion token. They never auto-publish.
  • Deletion tokens are not placed in URLs. Save the returned ID and token if you may need to delete an anonymous record later.

Retention

Anonymous and operational records have bounded retention where the product can do so without breaking the feature contract.

  • Anonymous Community Check-ins: 30 days.
  • Anonymous Global Intentions: 120 days.
  • Anonymous sacred-place suggestions: 365 days.
  • Terminal Telegram delivery rows in DELIVERED or DEAD state: 30 days.
  • Private owner data has no automatic TTL because it is user-controlled. It remains until the user deletes it or the deployment applies a documented account-retention policy.

Security controls

GeoLira applies common controls around authenticated writes, public abuse resistance and outbound provider access.

  • Private WordPress write actions require authentication and a valid REST nonce.
  • Anonymous public write endpoints use bounded JSON size and rate limits. The application rate limiter stores a pseudonymous bucket key, not a raw IP address.
  • Scientific outbound requests are HTTPS-only and use WordPress unsafe-URL rejection. Literal private, loopback and link-local IP targets are rejected.
  • Bot tokens and bridge secrets are not part of browser responses or packaged web assets.

Cookies and browser storage

The GeoLira web application does not introduce advertising or analytics cookies in this build.

  • No advertising or third-party analytics runtime is included in the current web bundle.
  • Authenticated My-area access may use WordPress authentication/session cookies supplied by the hosting WordPress deployment.

Access, export and deletion

Deletion mechanisms depend on whether data is owner-scoped or intentionally anonymous.

  • Authenticated private data can be exported and deleted through My Data.
  • Anonymous records can be deleted with the record ID and one-time deletion token returned at submission, where the feature supports an anonymous record lifecycle.
  • Production operator contact details and any jurisdiction-specific data-request process are a deployment requirement, not invented by the BUILD_ONLY package.