Your birth data is not ad inventory.

When you create a chart, the name or nickname, birth date, birth time, birthplace label, coordinates, and timezone are sent to the chart endpoint to perform the calculation. The endpoint returns the calculated chart and does not write those raw birth inputs to a user database.

Server and infrastructure providers may process short-lived request metadata and security logs needed to operate and protect the service. Do not use a legal name when a nickname is enough.

When you use the Astrology.ac plugin in ChatGPT, ChatGPT sends our server only what the request needs: the birth date, the birth time if you give one, and the birthplace (a city name, a place id, or coordinates with a timezone). A comparison also sends the second person’s details and an optional short label such as a first name. A transit request also sends the date range.

OpenAI adds request metadata to each call, such as anonymized user and conversation identifiers, your locale, and a coarse location hint. Astrology.ac uses the anonymized identifiers only in short-lived memory to limit how many requests one person can make, and does not use the location hint. We never receive your name, email address, or ChatGPT account details.

Birth details are used only to calculate the chart, comparison, or transits, and the result is returned to ChatGPT. Astrology.ac does not store them: they are not written to a database, file, or application log, and they are not used for advertising, sold, or shared. Our hosting provider keeps short-lived request logs, such as the time, path, status, and IP address, for security and reliability; those logs do not contain birth details.

• What ChatGPT keeps from your conversation is governed by OpenAI’s privacy policy.
• Birthplace lookups use a city list stored on our own server, so no other service receives your search.
• There is no account and nothing saved to delete. You can turn the plugin off in ChatGPT’s settings at any time.
• Only enter another person’s birth details with their permission.

A share link contains an authenticated-encrypted payload of calculated placements, the display name you chose, and time-confidence state. It excludes the raw birth date, birth time, birthplace, age, latitude, longitude, and timezone.

Exact degrees remain encrypted. Public receipts show sign-level results and categorical aspect evidence, and compatibility and current-weather views use sign-level positions so repeated requests cannot become a degree oracle. Anonymous capability links expire after one year. Anyone with a link can open it, so share it carefully.

Orbit Check sharing creates a separate, redacted result-only link. It removes both names, both reusable chart links, and all birth information, and expires after thirty days. “Fits,” “Partly,” and “Not us” feedback is stored only in the current browser and is not added to either shared link.

If you choose “Hold this reading to it,” the frozen current-sky prompt, method version, review date, optional before-hindsight expectation, later verdicts, and optional outcome note are stored in local browser storage. There is no server backup or account copy.

The ledger payload does not contain raw birth inputs, exact natal degrees, or the reusable chart link. Private expectation and outcome notes never enter analytics. Operational events may include counts such as the number of prompts captured or reviewed, without the note text.

• Anyone using the same browser profile can see local notes.
• Clearing site data deletes the ledger from that browser.
• Entries can be exported as JSON or deleted inside the tool.
• Copied Reality Receipts omit private expectation and outcome notes.

On this website, birthplace suggestions are provided by Open-Meteo’s geocoding service. Your city search text is sent to that service so it can return matching places and timezones. Astrology.ac does not attach your name or birth date to a place-search request. Review the Open-Meteo terms and privacy information.

In ChatGPT, birthplaces are matched against a city list stored on our server, built from GeoNames data (CC BY 4.0). No third party receives that lookup.

The site uses Vercel Web Analytics and Speed Insights to understand aggregate usage, reliability, and performance. Private chart and match tokens are replaced with generic route labels before analytics events leave the browser.

The anonymous release does not install account tracking, persist raw charts in local storage, sell personal data, or build advertising audiences from birth or relationship inputs. The only deliberate browser persistence is user-created Sky Ledger entries and local-only Shared Friction feedback described on this page.

Google AdSense and other advertising tags are not enabled as of the updated date above. If advertising is activated, third-party vendors, including Google, may use cookies, web beacons, IP addresses, device identifiers, and similar technologies to serve, limit, personalize, and measure ads based on visits to this and other sites.

Google’s use of advertising cookies enables it and its partners to serve ads based on prior visits. You can manage personalized ads in Google Ads Settings. Read how Google uses information from sites that use its services. Other authorized vendors will be disclosed through the consent interface when applicable.

Before serving ads where consent is legally required, Astrology.ac will use a Google-certified consent management platform, provide a clear choice before applicable storage or personalized advertising, and provide a way to revisit that choice.

• Birth and relationship inputs will not be used for ad targeting.
• Private chart, match, card, loading, error, and form states will not carry ads.
• Ads on public content will be clearly distinguishable from tools and navigation.
• Only real account identifiers and authorized sellers will be published.

Astrology.ac does not persist saved charts, account profiles, raw compatibility inputs, ChatGPT plugin requests, or Sky Ledger notes on a server. The only messages kept are the ones you send through the contact form, for up to 12 months as described below. If optional accounts, cloud-synced charts, or reminders are added, they will be opt-in and this notice will be updated before those features launch.

Capability links are self-contained and expire after one year; there is no central chart record attached to an account in the anonymous flow. Infrastructure logs follow the retention controls of the hosting services used to operate and secure the site.

The contact form collects the email address you want a reply at, an optional name, a topic, your message, and an optional page link. We use them only to answer you and fix what you report.

Messages are kept in private storage with our hosting provider, are not shared, sold, or used for marketing, and are deleted automatically after 12 months, or sooner if you ask. Your IP address is checked briefly in memory to stop abuse and is not stored with the message.

Send privacy questions and applicable data-rights requests through the contact form with the topic “Privacy or data request.” Because anonymous chart inputs are not stored as user records, include only the minimum information needed to understand the request.

Use the same form for product issues or corrections. Do not send a full private chart link or someone else’s birth details.