Birth details and charts
Birth dates, times, places, coordinates, time-zone choices, a partner's details and the names typed into the life path number calculator are processed in your browser. They are not sent to a server, stored in an account or included in analytics. Every chart, line, reading, ranking and card is calculated on your device.
Remember my details is on by default. While it is on, your most recent birth details (and a partner's, if you added one) are saved in this browser's local storage so your chart reappears next time. Details entered as a date alone, which the zodiac sign, compatibility and moon phase calculators accept, are not saved. The cities you add to your compare shortlist are kept the same way. While it is on, the map also keeps its last view in this browser tab's session storage (the results tab, the Best places choices, and the place you were reading with the list it came from), so a reload reopens it; that ends when the tab is closed. Switch it off to delete them and stop saving. They never leave the device either way; clearing your browser's site data also removes them. Your choice of light or dark theme and of kilometers or miles is stored the same way, and so is how tall the map's results were on your screen, a number the page uses to keep their space while they load.
Saved charts are kept only when you choose Save these details: that birth is saved in this browser's local storage under the name you give it, up to 30 charts, until you delete it, whether or not Remember my details is on. Saved charts never leave the device, and clearing your browser's site data removes them.
Place search and map data
The site downloads public data files as you use it: the world map, planetary tables for Chiron and four asteroids, a table of historical clock changes for old dates, the largest city in each time zone, and place lists from GeoNames. The moon phase page reads your device's time zone to open on the largest city in it; that table is the same file for everyone, so downloading it reveals nothing about your time zone. When you search for a place, your browser downloads the public list of places whose names begin with the same two or three letters, so that request reveals those first letters, not the rest of what you typed or the place you chose. Coordinates in a relocation link come from a place you tapped on the map, not from your birth details.
Share cards and downloads
Share cards and map images are drawn on your device. Cards show a line, a place and its meaning, never your birth date, time or place. A shared link to a card contains only the line (for example venus-dsc) and the city name. Saving or sharing an image is your choice, and the apps you share to apply their own policies. The site never posts anything automatically.
The map's PDF report is also built on your device. It contains your birth details, chart and shortlisted places, plus your partner's birth details and comparison when Rank for both of us is selected. The browser's print dialog lets you print it or save a PDF; on phones and tablets the report opens on the page first, and its Save as PDF button opens that dialog. On iPhones and iPads, Save as PDF makes the PDF file on your device instead and opens the share sheet with it, where you choose to save, print or send it. Sharing that file shares those details with the recipient; the site does not upload it.
Chart printouts also contain the details displayed in their results. A zodiac compatibility printout includes both people's entered birth details, signs, sign-change intervals and comparison. On iPhones and iPads, the chart's print action prepares a PDF on your device; Save PDF opens the share sheet, where you choose its destination. Other browsers use their print dialog, with a PDF file offered if that dialog does not open. Sharing a chart file shares its details with the recipient. The site does not upload it.
Transit and solar, lunar and Saturn return calendar files are generated on your device. They include the selected calculated dates and chart-derived results, without birth dates, birth times or birthplaces. Importing a file into another calendar app shares those results with that app under its own policy.
Full- and new-moon calendar files contain only the public phase dates and details for your selected year. They are generated on your device. We count the download action, without the year or time zone selected.
Ask your own AI
The Ask AI and Copy for my AI buttons copy a text summary of your results to your clipboard: planets, lines, places you shortlisted and readings, never your birth date, time or place. The summary is made on your device and this site sends it nowhere. It goes to an AI service only if you paste it there yourself, and that service's own policy then applies. We count only that the button was used, never the text.
The zodiac compatibility summary keeps both people's possible signs and all seven links, including uncertain pairings. It leaves out birth dates, times, places and sign-change clock intervals.
Birth, composite and Davison chart summaries keep the displayed chart's points, selected settings and all calculated aspects before filters. Relationship copies omit both people's birth details, your home city and the derived midpoint time and coordinates. Missing birth times remain labeled as uncertain.
Website delivery and task counts
Cloudflare receives ordinary connection information such as IP addresses, request paths and headers to deliver and protect the site. We keep aggregate first-party counts of page loads, charts and calculations made (and whether a birth time and place were given), place readings, best-places themes, cities added to a shortlist, card and image downloads and share actions, plus limited performance and error categories. Page-visit counts also note the domain of the website that linked to the page (if your browser shares one) and a broad source category taken from it or the link's campaign source tag, such as a named search engine or AI assistant. For the slowest response on a page, speed measurements note how the delay divided between waiting, running and redrawing, whether it followed a tap, click or key press, and the broad kind of control involved, such as a button, link or map. In browsers that report it, they also note whose script ran longest during that response (this site's, a browser extension's or another site's), how it was started, and how the time divided between scripts, page layout and drawing, never the script's address or name. Map interactions never include the place, coordinates or line selected. For page loading, they also note how the wait divided between connecting, the server's reply and fetching and drawing the largest image or text, whether that was text or an image, when the largest layout movement happened, and whether the page was opened fresh, reloaded, returned to or loaded in advance. Map and solar-return city calculation counts exclude example charts, automatically restored results and result redraws. Deliberately changing a city-ranking theme counts when its result is ready. We separately count starting and submitting a birth form, fixed validation categories (such as a missing date or place, which of the month, day or year was left empty, how many times those date lists had been tapped and changed on the page (0, 1, 2, or 3 or more) and whether they had held a whole date, whether the browser had translated the page, whether a place left unchosen was typed in Latin letters, another script or not at all, and whether the search found no place by that name, several to choose from, or only close spellings), calculation time, successful personal results, leaving a page while a calculation is still pending, examples, restored results and result-button actions. On the map pages, examples and restored results also note whether the page was opened fresh, reloaded or returned to, roughly how long the tab had been out of view before (in broad bands such as under two seconds or under a minute), and whether your last view was reopened; place readings note where they were opened from (the map, a list, a search or the Next button); and best-places rankings note the region and city-size filter chosen. Each map page view also sends a short summary when you leave it or switch away: which result tabs were opened, how many places were read and from where (the map, a list, the Next button or a search), how many rankings were made and for which themes, whether an image was saved or shared, a report or AI summary made, a report print asked for, a place shortlisted, the birth form opened or the map zoomed, how many screens down the page you scrolled, whether the results below the map came into view, and how long the page was in view. A random number made for that page view, never stored or reused, lets a later summary replace an earlier one; it is not linked to you, your chart or your device. Each print of a report or chart also notes whether the browser's print dialog opened and how long it stayed open, never what was printed. Saving a report or chart as a PDF file notes whether the file went through the share sheet or was downloaded and how long it took to make, never what was saved. Map reports also note whether your tap waited for the file to be ready. We also count deliberate Sun-sign and year-animal comparisons, without recording the signs or animals selected. These counts include only a broad source category for the current page, without carrying it between pages. These counts contain no birth details, places, coordinates, results or raw error messages. There are no ads, ad pixels, session recordings or third-party fonts.
Hosting diagnostics
Cloudflare keeps sampled request and error logs for up to seven days to help diagnose server failures. These hosting logs can include requested page paths (query strings are removed) and ordinary request metadata. They are separate from the anonymous tool counts described above; application inputs are not added to them.
Google Analytics
We use Google Analytics 4 to understand page visits and count successful chart calculations requested by the visitor. Example charts and automatically restored results do not send that completion event. The first calculation you request on a page also sends one fixed tool_used event with the page path. It may set first-party _ga cookies to recognize repeat visits. Google receives the page path, page title, limited campaign tags, the referrer's origin, and ordinary browser and connection information, including your IP address and the approximate location our hosting provider works out from it (country, region, city and approximate coordinates). Our server passes that location on because these requests reach Google through this website. Query strings and page fragments are removed, enhanced measurement and advertising features are off, and no birth details, places or chart results are sent. Event-level data is kept for 14 months; aggregate reports may stay available longer. See Google's Privacy Policy.
Google Analytics does not load for visitors in the EEA, UK, Switzerland or Quebec, when location is unknown, or when the browser sends Global Privacy Control. Automated and test traffic is excluded. You can remove analytics cookies through your browser's site-data controls.
Links to stores and services
When a page links to another company's product, the link goes through an address that begins with /go/. When you follow one, our server redirects you to that site and counts the click, the same way as a page view: which link, the page it was on and roughly how long after the page opened, but no identifier for you. Once we join a company's affiliate program, the redirect adds that program's referral code, so the company can credit a purchase or sign-up to us; its own privacy policy then applies.
Questions
For privacy questions, email hello@freeastrocartographychart.com. If you email us, your email provider and ours process that message. Please don't send anyone else's birth details. See the terms for using the site and its results.