Privacy and data handling.

01 · Information you provide

The Instrument asks for what the calculation needs, and nothing beyond it.

• ◆  Birthplace
• ◆  Birth date
• ◆  Exact birth time
• ◆  Email address, only when you request the Diagnostic Folio

02 · Place suggestions

The birthplace field requests suggestions from Open-Meteo Geocoding. The service receives the place text needed to return possible matches. The selected record supplies latitude, longitude, and an IANA time-zone identifier for the calculation.

03 · Calculation and birth-data retention

The selected birthplace, birth date, and birth time are processed transiently to calculate planetary positions and the qualifying aspect count. The calculation runs through Astrology-API.io, which receives the coordinates, the date, and the time in order to return those positions. Its published terms describe the service as stateless and state that end-user birth inputs and calculation results are discarded after the response.

Abundanosa does not retain the submitted birth fields in its database, subscriber record, or analytics. The Flodesk subscriber record contains the email address and assigned Art, not the birth chart.

04 · Email and the pathway

When you request the Diagnostic Folio, your email address and assigned Art are sent to Flodesk. Flodesk finds or creates the subscriber record and assigns the segment corresponding to the calculated Art. The address delivers the Folio and begins the pathway.

Abundanosa does not sell, rent, or trade email addresses. Unsubscribing through the link in any email stops the email. If you want the subscriber record itself removed, ask, and it will be deleted.

05 · Analytics and consent

Birth inputs are not sent to analytics or advertising systems.

No analytics tracker, advertising pixel, or consent-management software runs in your browser. Nothing is written to your device, no cookie or identifier is set, and nothing you do here is tied to you or followed to another site.

The Instrument keeps counts. When a calculation completes, when a verified result opens, and when a Folio is requested, a total goes up by one. What a count is allowed to carry is fixed in advance: which of those three events occurred, which Art was assigned, whether the signature was single, dual, multiple, or indeterminate, and which page or site the visit arrived from. Those labels come from a reviewed list. Anything not on the list is counted as other. Aggregate usage counts are stored in Upstash Redis, connected through Vercel.

The counts are totals and nothing else. No record of an individual visit exists, and nothing in them leads back to a person. Recording anything that would identify a visitor requires this page to change first.

Typefaces are requested from Google Fonts. That request reaches Google and carries your IP address, as a request to any outside server does.

Serving a page requires a request to reach a server, and the hosting provider receives that request. It carries your IP address, your browser type, and the time and address of what you asked for. Providers typically retain this in standard server logs. Abundanosa does not use those logs for analytics or advertising, and does not join them to subscriber records.

06 · Retention

• ◆  Birth inputs: processed transiently and not retained by Abundanosa.
• ◆  Email address and assigned Art: retained in the Flodesk subscriber record until removed under the subscriber or deletion process.
• ◆  No birth chart is stored in Flodesk.
• ◆  Instrument counts: totals only, kept without an expiry date. They hold no information about an individual visit.
• ◆  Server logs: held by the hosting provider under its own retention schedule, not by Abundanosa.

07 · Contact and deletion

For questions about data handling, or to request deletion of subscriber information, contact hello@abundanosa.com.