Privacy — How Your Data Is Handled

Chart calculation runs in your browser. Birth fields are not sent as part of calculation or a Cabinet of Twelve lookup; they leave your device only if you sign in to sync saved charts, share a link that carries them, or type them into an assistant message. Aura sends one public wallet address—not your birth or chart data—to a blockchain-data provider for a read-only lookup. Accounts, remembered Aura data, and the weekly email are optional and off by default. We show no ads and use no cross-site tracking.

AI integration candidates

The public-sky ChatGPT candidate needs no birth information or account. When enabled, its tool arguments and results pass through the assistant provider and calculations run on Zodiacs infrastructure. The adapter saves no requests or results, writes no argument logs, uses uncacheable responses and refuses personal fields. Hosting and provider request metadata have separate retention policies; those policies require review before activation. The candidate is disabled by default and has not been publicly submitted.

The developer plugin computes locally over stdio and makes no outbound requests. An assistant connected to it can still send its tool arguments and results to its provider. Natal positions and exported records can reveal a birth instant; they are not anonymous. Keep them out of public links, analytics, screenshots and issues. The hosted candidate does not offer personal-chart computation or storage.

Who operates this site

Zodiacs LLC, a New Mexico limited liability company (“Zodiacs,” “we,” “us,” or “our”), owns and operates Zodiacs.org and is responsible for the personal information described in this policy. Where data-protection law uses the term “controller,” Zodiacs LLC is the controller for that information.

What happens when you use a calculator

Every chart you calculate here is computed on your own device. When you enter a birth date, time, and place, that information is used by code running in your browser to calculate the chart. It is not transmitted to our servers, logged, or stored by us as part of that calculation. It leaves the device only if you later sign in to sync a saved chart, share a link that carries it, or put it in an assistant message. This is a deliberate design choice, described in full on our methodology page.

Place search downloads from zodiacs.org a city file chosen by the first letter you type, and searches it in your browser. For a birth before 1970, the calculator also downloads a file of historical clock changes chosen by the birthplace's time zone. Neither request goes to any other service. Which files are requested shows our host the first letter of the city you typed and, for a birth before 1970, a group of time zones that includes the birthplace's. When a page shows the signs of a birth chart, it first requests the pictures of all twelve signs, in the same order for every chart, so those requests do not show which signs the chart has.

Guide

Guide sends the questions you type, recent Guide messages, and enabled public page or sky context to our cloud service. It does not automatically attach your saved birth chart or personal chart placements. Avoid entering private birth details in Guide.

When you send a question to Guide, that message, recent Guide messages, and the visible Guide context are sent to OpenAI for an input safety check and to generate a draft reply. That generated draft reply is then sent back to OpenAI for a second safety check before you see it. Every Responses API request uses store: false. The current web Guide conversation stays only in this browser session, is not synced to an account, and is not stored as text on Zodiacs.org servers, whether or not you are signed in. OpenAI states that API data is not used to train its models by default, and that its abuse-monitoring logs keep submitted content for up to 30 days, or longer where the law requires it or where that is needed to protect its services or others from harm. To enforce the daily limit, we keep a salted one-way identifier derived from your IP address, never the raw IP, with its daily count and a record of each request. Each later quota check deletes counts older than the previous UTC day and request records older than 48 hours. We do not send that identifier to OpenAI or put conversation text in provider metadata. Guide also sets a session cookie holding a random, signed identifier. It is used to limit simultaneous requests from one browser, lasts until the browser session ends, and is not stored with your messages.

Charts you save

When you save a chart, it is stored in your browser's local storage — on your device, under your control. It is not sent anywhere unless you sign in to an account (below) or share it. Clearing your browser's site data removes saved charts. Unless you sign in, we cannot see them and cannot recover them for you.

Share links and invitations

Share links keep chart data after the “#” in the address, which browsers do not send to servers. A full-details link carries the chart's name, birth date, time, place, and coordinates. A positions-only link carries the chart code described under “Daily brief, calendar, and notifications” instead. Anyone who has either link can open it, including anyone it is forwarded to.

Every image you can make of a chart, a pair of charts or a return — the chart sheet and chart cards, the images of a reading, an aspect pattern or an explorer section, the compatibility and composite pictures, and the solar and lunar return images — is drawn on your device and goes only where you share or save it. Unless you choose to show birth details on the chart sheet, none has a birth date, time, place, or coordinates, and none has a name except a compatibility picture, which shows the names of the two charts; none shows more of a birth than its positions-only link does. A chart's planet positions are those at the birth time in UTC rounded to the whole minute, which still give the birth date and time to the minute; the ascendant and midheaven are shown only to the whole degree, and Placidus houses are left out. A return image is found from those positions and gives the return to the whole minute, as does its calendar file. A chart without a birth time is drawn from the sky at 12:00 UTC on the birth date, as its link is, which gives the date but nothing about the birthplace; the Moon's sign is shown only when the Moon stayed in it all that day everywhere, and a picture of two charts leaves such a person's Moon out. Each image alone narrows a birthplace no more than a link does, but images shared together narrow it further. For a birth in Lyon in 1987, a link alone leaves an area of about 19,100 km²; a link and one solar return image cast at the birthplace, as return images are by default, leave about 3,900 km², about five times smaller; a link with two solar return images and four lunar return images leaves about 1,500 km².

If you are signed in and create a compatibility invitation from a synced chart, our server stores the chart's name (up to 24 characters), its Sun sign, its positions-only chart code, and whether the birth time is known. An invitation lasts up to 14 days, and whoever opens it sees that name and those positions. The positions are erased when the invitation is used, withdrawn, or expires, and the rest of the record 30 days after that. If you ask, we email you throughResendwhen the invitation is completed.

Your page: your name and chart cards

The name you choose for your profile page is stored in this browser alongside your saved charts; its first letter, on your Sun sign's colour, stands in for a picture there and in the site menu. It leaves your device only inside a chart card you choose to send (below), and clearing your browser's site data removes it.

A chart card is a link you create from the chart marked as yours. It carries the name you chose and the chart code described under “Daily brief, calendar, and notifications”, so its planet positions still give your birth date and time. The card travels in the part of the link after the #, which browsers do not send to our servers. Anyone who has the link can open it, including anyone it is forwarded to. When someone opens it, their browser reads it and removes it from the address bar; it is kept on their device only if they choose to add it, and we keep no copy.

Living Chart moments

Living Chart lets you save an optional category or short note beside a dated copy of the personal forecast and factual sky receipt you saw. A first save stays in this browser. If you separately choose Keep this on every device, the entry's date and time precision, category, note, frozen forecast, and chart identifier are sent to Supabase and stored for your signed-in account. Account access is restricted with row-level security and Supabase encrypts stored data at rest. This is not end-to-end encryption: Zodiacs.org and Supabase can technically process the stored entry to provide synchronization, support, export, and deletion.

Living Chart sync has its own consent, separate from saved-chart sync. We do not make entries public, index them, send them to Guide or another AI provider automatically, use them to generate horoscopes, sell them, or intentionally include their text in analytics or application logs. Withdrawing Living Chart sync deletes the remote entries and advances a consent version so an old offline tab cannot upload them again. Copies already kept on a device remain until you delete them there or clear this site's browser data. Deleting an entry removes its note, category, forecast, chart identifier, and date from the device and cloud record. A content-free technical deletion marker may remain so a delayed request cannot restore it. The timeline provides portable JSON and readable Markdown export, per-entry edit and deletion, and a retry control when sync needs attention.

The Cabinet of Twelve and public wallet addresses

The Cabinet of Twelve reads one public wallet address and the dated sky side by side. If you choose to add a chart already saved in this browser, its summary is an optional on-device comparison layer. The pattern and any symbolic reflection are composed on your device. When you compose or refresh an Aura, our holdings endpoint receives the public address and forwards it to the configured blockchain-data provider to check which Zodiacs.org Registry entries are present. The configured provider is currently PublicNode, operated by Allnodes. The provider receives the lookup from our server, not from your browser. The request does not include birth fields, chart names, chart placements, or chart geometry. When the feature is enabled, Zodiac Terminal's optional public Shelf uses the same endpoint and sends one public Solana address, the one you enter, only after you press View; it does not send chart or birth data. When Aura is off, the illustrative Shelf makes no address or provider request.

Zodiacs.org does not connect wallets, request signatures, or submit transactions. Public address lookups use an address you paste. Purchase links open independent services with their own terms and risks.

A public address is public but not necessarily anonymous. Its on-chain holdings and history may be visible and may become linked with a person or other activity. Vercel, the configured blockchain-data provider, and their infrastructure may process routine request metadata and operational or security logs, such as IP address, time, and browser information. We do not promise that a public-address request is never logged by infrastructure providers whose retention practices we do not control.

Public Astrofolio, Terminal, and Registry data sources

When a relevant Zodiac Terminal or Registry market panel is displayed, your browser may request public market data from Dex Screener, public chart data from GeckoTerminal, or public attention data from Wikimedia. Those automatic requests do not include a wallet address, birth fields, chart data, or Aura results. The independent service still receives ordinary web-request metadata, such as your IP address, browser information, and request time, and its own privacy terms and retention practices apply.

Each sign’s Registry profile is read-only. It shows public market data and verified token addresses, but it contains no purchase route or link to a trading venue. The profile does not connect a wallet, request a quote, receive your public address, or ask for a transaction. No birth or chart data is included in these market-data requests.

Aura browser storage and sharing

By default, Aura keeps the public address, chain, Registry sign results, lookup time, and optional selected chart identifier in this tab's session storage. It becomes ineligible for restoration after eight hours. The unchecked “Remember this address on this device” option stores the same fields in local storage and makes them ineligible after 24 hours. Ineligible records are deleted the next time Aura reads them; if you do not return, the browser may retain the expired bytes until you clear site data. “Forget address / Clear Aura data” removes both Aura records from this browser; it cannot erase public blockchain history or infrastructure logs.

Aura share images are composed on your device. The image omits the public address, chart name, birth fields, exact placements, and chart geometry. The seal image shows which signs are held, how many of the twelve, and a date. The cabinet image shows the chain, the date, which signs are held, and each one's edition, which reflects the balance, with a count of gold sculptures up to 99+. Neither includes a saved-chart fact. A browser share sheet or download sends the image to a destination you choose, whose privacy terms then apply. Clearing Aura cannot recall copies that other people or services have saved or reposted.

Optional account (sync across devices)

You can create a free account to keep your saved charts on more than one device. This is entirely optional and the tools work fully without it. If you create one:

You sign in with a one-time link sent to your email address — there is no password to store.
We store your email address and every chart saved in your browser while you are signed in, including those saved before you signed in, with their birth details, with our database provider, Supabase, so they can appear on your other devices. Access is restricted to your own account.
We also store your house-system setting and a record of each chart you delete (its identifier and when), so the deletion reaches your other devices. These are kept until you delete the account.
While you are signed in, a sign-in token is kept in your browser so you stay logged in. Signing out removes it.
You can delete your account and its stored charts at any time by emailing admin@zodiacs.org. Copies in our weekly backups expire within 90 days (see Backups).

Email

Account holders can opt in to a weekly email summarizing the coming week's sky for their saved charts. It is unchecked by default. If you opt in, we store that preference and send the email through our email provider, Resend. Every email includes a one-click unsubscribe link, and you can turn it off from your profile at any time.

Your account email address is used to send sign-in links and, if you ask for it, a note when someone completes a compatibility invitation you sent. We do not sell or share it.

Daily brief, calendar, and notifications

The daily brief reads computed positions from a chart saved on your device.

A calendar file you download from the Transits page is built in your browser from your chart as calculated there, not from the chart code, and its times are exact. Anyone you share it with, or any online calendar you import it into, can work out from them your birth date and time, and your birthplace from those for your ascendant or midheaven; without a birth time the chart is calculated for noon at your birthplace, so they give its time zone or, before standard time, its longitude.

Public People pages

The People directory uses names, public birth dates and places, life dates, disciplines, and licensed portraits from reviewed Wikidata, Wikipedia, and Wikimedia Commons records. The chart is computed from those sourced facts and describes the recorded sky and its uncertainty; it does not make claims about a person's health, conduct, relationships, finances, or private life. Profiles of living people are not submitted to search engines. To request a correction, withholding, or removal, email people@zodiacs.org. We honor a subject's removal request even when the underlying public source remains unchanged.

The Race

If you join a team in the Race, we store a one-way code derived from the Race cookie, with your team, the season, when you joined, and your weekly check-ins. To limit repeat joins we also keep a one-way code derived from your IP address, which is deleted after the next UTC day. No name, email address, account, or wallet is involved.

Backups

Once a week we copy the database, which holds accounts, synced charts, and the other stored records this page describes. The copy is encrypted with AES-256 before it is stored with GitHub, and each copy is deleted after 90 days. Deleting your account removes it from the live database; it can remain in a backup until that backup expires.

The compute API

The compute API is for programs: it computes a chart, positions, houses, events, a local time, a sky fact or the stretches of time in which chosen conditions hold, from what a program sends it. The site's own calculators do not use it. It reads the body of each request, which can hold a birth date, time and place, and nothing from the query string. Nothing from a request or its result is written to a log, a file or a database, no error repeats what was sent, and every response is marked so that no cache stores it. When a request ends, including a refused or failed request, the server clears its last calculated frame and epoch-selected ephemeris segments and discards that request's time zone lookup maps. Fixed public tables remain available to later calculations. This removes application-held references; it does not guarantee discarded memory is overwritten or describe every log the hosting platform may keep. To enforce the rate limit, the API sends the request's headers, which include your IP address, to Vercel's firewall, which counts the requests from each address; it never sends the body. Our host's logs, described below, keep the full web address of each request, so birth details belong in the body, not in the address.

Hosting, logs, and analytics

The site is hosted on Vercel. Like all web hosts, their servers process the requests your browser makes and may keep short-lived technical logs (such as IP address and browser type) to deliver the site and guard against abuse. We do not run advertising, and we use no cross-site tracking cookies or third-party marketing pixels.

We count page views and anonymous feature usage with Plausible, a cookieless analytics service. To avoid counting the same device repeatedly during one day, Plausible briefly processes the IP address and user agent to derive an identifier scoped to this site, device, and day. The raw IP and user agent are not stored; the salt used for that identifier rotates and is deleted every 24 hours. Plausible receives no birth data, public address, chart identifier, connected account identifier, or exact held-sign list. It also receives no cross-site identifier. Aura events carry only allowlisted categories such as an outcome and a coarse held-count bucket; other events similarly record “a chart was saved,” never whose.

Cookies

We do not use advertising or tracking cookies. Three first-party cookies are sent to our server by design: Guide's session cookie, until the browser session ends; the Race's cookie, for up to a year; and an invitation cookie, for up to 14 days while you use a compatibility invitation. The rest is first-party browser storage for features you use: what you save (charts, comparisons, Living Chart moments, learning progress), working state for the tools you use (such as Guide's conversation and cached calculations), bounded Aura session data, an optional remembered Aura address, site preferences, copies of the site's own files for offline use, and, if you sign in, a sign-in token. Apart from these cookies and what the sections above describe, this storage stays on your device, and none of it is used to track you across other sites.

Children

The site is intended for a general audience and is not directed at children under 13. We do not knowingly collect personal information from them.

Your choices

Use every calculator with no account; nothing you enter is stored off your device unless you sign in or share a chart.
Use the Aura example without a chart, address, wallet connection, or purchase.
Paste a public address instead of connecting third-party wallet software.
Leave Aura's “Remember” option unchecked and clear its browser data at any time.
Delete saved charts by clearing your browser's data for this site.
Delete an account and its synced data by emailing us.
Turn the weekly email off with one click, any time.
Withdraw a compatibility invitation from your profile before it is used.
Request correction, withholding, or removal of a People profile.

Changes

If we change how we handle data, we will update this page and its date. Material changes to the account or email features will be reflected here before they take effect.