What this site collects, where it goes, and how to get it back or get rid of it. This describes what the software actually does, not what a template says it might do.

Last updated 23 July 2026. Divinity Atlas is operated by an individual; contact details are on the contact page.

The Short Version

To make a reading, this site asks for a name, a date of birth, a time of birth, a place of birth and optionally a gender. That is sensitive information, and there are two things you should know before you type it in.

Beyond that: we keep an account for you, we keep the charts you save, we keep a record of what you bought, and we log server errors, which includes your IP address. We do not sell anything to anyone and we do not run advertising. One measurement tool, Google Tag Manager, exists in the site's code but is switched off today. When analytics is enabled it loads on every page, can set cookies and send usage data to Google - see cookies.

What We Collect

Account details, birth data, purchases, your profile, messages, forum posts, abuse reports, and error logs.

Your account. When you register we store your email address, a display name if you give one, whether the account is active and whether the email has been verified, your role on the site, the date you last signed in, and the dates the record was created and changed. If an account is suspended, the reason is stored with it. We do not ask for a postal address or a phone number and there is nowhere to enter one.

Chart data - the sensitive part. Each chart you save stores a first name, middle name and last name, a date of birth, a time of birth, a place of birth, and a gender selected from a fixed list. If a place of birth is resolved to coordinates, the latitude, longitude, time zone and UTC offset are stored too. Charts belong to the member who created them.

You can save charts for other people - a relationship or family reading is several charts in one group - and a group also stores a title you choose (for example "Alice and Bob"), a display name and a seat label for each person, and the family role or relationship type. If you enter someone else's birth details, you are responsible for having their agreement to do so. We have no way of contacting them or checking.

Purchases. For each payment attempt, approved or not, we store the provider you used, the amount, the currency, the provider's reference for the transaction, the status, and the raw response the provider sent back. That raw response is stored so a disputed charge can be traced. It is whatever the provider chose to return, and for PayPal in particular it can include the name, email address and country held on your PayPal account. Separately we store your entitlement: which package and which sections you bought, and when.

Generated reports. The text of a generated reading is stored so you can read it again without paying twice. Where a reading is rendered to a PDF, the file is stored on the server with its name, path and size, along with a record of who it belongs to and which chart it was made from. That file contains the full birth details.

Forum and comments. A thread stores its title, the member who opened it, whether it is pinned or locked, and a view count. A post or a comment stores its text and the member who wrote it. Comments carry a moderation status and a count of how many times they have been reported. The forum does not record IP addresses.

Your profile. If you fill in a member profile we store what you put on it: a short bio, a location you type in, the beliefs, practices, disciplines, religions, holidays and traditions you pick from the atlas, and any education credentials you enter. What appears publicly is up to you - see your public profile.

Your avatar. If you upload an avatar, the image file is stored on this server until you replace or remove it.

Friends and blocks. We store who your friends are, friend requests sent and received, and any members you have blocked.

Messages. Direct and group messages are stored so that the people in the conversation can read them. They are not end-to-end encrypted - they exist on the server in readable form. We do not read them in the ordinary course of running the site; they are accessed only to investigate abuse, to protect the security of the service, or where the law requires it.

Abuse reports and moderation records. If you report a profile, avatar, message, username or comment - or someone reports yours - the report is stored: who reported what, and why. We also keep enforcement records: warnings, strikes and the dates they expire, suspensions, bans, and the reasons for each. The conduct rules explain how these are used.

Error logs. See Error logs below - this is the one place your IP address is routinely stored.

What we do not collect. There is no advertising on this site, no marketing pixel of our own, and no fingerprinting. The one third-party measurement tool is Google Tag Manager, which is switched off today; when analytics is enabled it loads on every page and is described under cookies. Nothing here profiles you, scores you, or makes any automated decision about you. The reading itself is generated text, not a decision.

Your Chart Goes to an AI Provider

This is the most important disclosure on this page.

Reports on this site are written by Claude, a large language model operated by Anthropic PBC. When you generate a report, this server makes a request to Anthropic's Messages API at api.anthropic.com. The request contains:

• the full name on the chart - first, middle and last, each also sent individually, because the report explains the etymology of each;
• the date of birth, written out in full;
• the time of birth, where one was entered;
• the place of birth, where one was entered;
• the computed correspondences for that person - the sign, ruler, decan, numbers, animal, fixed stars and deities derived from those birth details;
• the site's own reference data for the sections you bought - the tables of planets, signs, tarot cards, sephiroth, elements, numbers, deities and so on. This part is encyclopedia content and contains nothing about you.

Your email address, your password, your payment details and your forum activity are not sent. Only the chart and the reference data go.

This transfer is necessary to provide the product. If you do not want your birth details sent to Anthropic, do not buy a report - the rest of the site, including the encyclopedia and the forum, works without it.

Anthropic is a United States company, so buying a report involves your data being processed in the United States. Anthropic's handling of API data is governed by its own terms and privacy policy, published at anthropic.com/legal/privacy. We have no control over their systems and cannot make promises on their behalf; please read their policy if this matters to you.

Payments

Card numbers never reach this server.

Card payments (Authorize.Net). The card fields on the checkout page are not part of a form that posts to us. They are read by Authorize.Net's own Accept.js script, which sends the card number, expiry and security code directly to Authorize.Net from your browser and returns a one-time opaque token. Only that token is posted to this server, and only the token is used to take the payment. The card number, expiry and CVV are never transmitted to this server, never written to our database, and never appear in our logs.

PayPal. PayPal's buttons run in your browser and you approve the payment with PayPal directly. This server then asks PayPal to capture the approved order using its own credentials. We never see your PayPal password. We do store PayPal's response, which may name you - see "Purchases" above.

Apple Pay. Apple Pay is handled by your device. The encrypted payment token your device produces is passed through this server to the payment processor. We do not receive your real card number; Apple Pay uses a device-specific number.

Each provider is an independent controller of the data it collects from you and handles it under its own privacy policy.

Passwords and Sign-In

Passwords are hashed with PBKDF2-SHA256 at 120,000 iterations. We cannot read them.

Your password is never stored. What is stored is a verifier derived from it using PBKDF2 (Rfc2898DeriveBytes) with SHA-256, 120,000 iterations, a 16-byte salt generated at random for your account alone, and a 32-byte output. Verifiers are compared in constant time so a failed sign-in leaks nothing about the stored bytes. Plaintext passwords are discarded the moment they are hashed and are never logged. Nobody, including the site owner, can recover your password; a reset replaces it.

Password resets create a single-use token with an expiry, stored against your account and sent to your email address.

Passkeys. If you register a passkey we store its credential id, its public key, a signature counter, the transports it supports, its authenticator model identifier, and a nickname you choose. A public key cannot be used to sign in as you. The private key never leaves your device.

Sign in with Google, Facebook or Apple. If you use one of these, we receive and store the provider's identifier for you, plus the email address and display name they return. We do not receive your password for that account, and we do not get access to anything else in it.

Error Logs

When the site throws an error we record your IP address and browser.

If a page fails, the server writes a log entry containing the error message and type, the full stack trace, the URL you requested, the HTTP method, the response status code, your member id if you were signed in, your IP address, and your browser's user-agent string. Your IP address is taken from the X-Forwarded-For header where a proxy sets one, otherwise from the connection. The same information is emailed to the site owner so the fault can be fixed.

These entries exist to diagnose faults, not to watch you, and they are written only when something breaks - not on ordinary page views. Be aware of two limits, stated plainly because they are real:

• The error log is append-only. Unlike every other table on the site it has no soft-delete flag, and there is currently no automatic purge. Entries persist until deleted by hand.
• A URL or stack trace captured in an error can incidentally contain identifiers from the page you were on.

If we block an IP address for abuse, that address and the reason are stored.

Cookies and Local Storage

Three functional cookies of our own. Google Tag Manager exists in the code but is off by default, and there is no cookie consent banner because nothing that needs one runs today.

This site sets no advertising cookies of its own. The cookies it sets itself are functional:

• The sign-in cookie. A standard ASP.NET forms-authentication cookie issued when you sign in, holding your email address in signed form. It is what keeps you signed in. Signing out clears it.
• The session cookie. A standard ASP.NET session cookie. It is how a report you have configured but not yet paid for survives the trip to the checkout page. It expires when the session does.
• The device cookie (.DIVINITYDEVICE). A random identifier for the browser you are using - not for you. It contains no name, email, IP address or anything derived from your machine, and it is signed so it cannot be edited. It does two jobs: it is how we notice a sign-in from a browser you have not used before, so we can email you about it; and it is how a page view is counted once instead of twice (see below). It lasts two years and is refreshed as you browse. Clearing your cookies removes it, and the site works normally without it.

Counting readers. We record which entries and which category and section pages get read, so we can tell what the atlas is actually being used for. What is stored is one row per page per reader: the page, an identifier for who read it, when it was first and last read, and how many times. The identifier is your member id if you are signed in, and otherwise the random device cookie above - no IP address and no browser string is stored with a view. Opening the same page twenty times counts once. Nothing about the order you read things in, how long you stayed, or where you came from is recorded, and none of it is shared with anyone.

Two consequences worth stating plainly. If you browse signed out on a phone and a laptop, that is two readers as far as this count is concerned; if you later sign in on both, the two are merged into one and your earlier reading is attached to your account. And because the count is sent by a small script after the page loads, blocking scripts means you are not counted at all.

Your browser also keeps some settings in local storage, which never leaves your device and is never sent to the server: your light or dark theme choice (divTheme), your text-size choice (divFont), and the state of the music player - volume, current album or video, track index, and whether the player is showing (divpVol, divpMode, divpId, divpIdx, divpVis, divpAlbum). None of these identify you and none are used for tracking. Clearing site data in your browser removes them.

Google Tag Manager. Google Tag Manager (container GTM-NG3DKXTG) exists in this site's code, but it is switched off today: it does not load and nothing runs. If it is switched on, it would load on every page of this site. It is a Google service: loading it sends your IP address and browser details to Google, it can set cookies of its own, and tags loaded through it can send usage data - such as the pages you view - to Google. Blocking it with a content blocker would not break the site.

Cookies and consent. There is currently no cookie consent banner on this site, because there is currently nothing here that needs one. The three functional cookies above are necessary to sign in, to keep a session, and to remember your device; none of them are used for advertising or tracking, and none require consent under any regime we are aware of. Google Tag Manager is switched off, so it sets no cookies and sends no data today. If it, or any other measurement or advertising tool, is switched on in the future, a consent mechanism will be put in place before it runs, and this page will be updated to say so.

Other third-party embeds set their own cookies - see below.

Everyone We Send Data To

The complete list. There is nobody else.

• Anthropic - your chart, to generate a report. See above.
• Authorize.Net - your card details, sent by your browser, not by us.
• PayPal - if you pay with PayPal.
• Apple - if you pay with Apple Pay.
• Google, Facebook, Apple - only if you choose to sign in with them.
• YouTube (Google) - the music player is a YouTube embed, and the YouTube player script loads on every page of this site. That means Google receives your IP address and user agent on every page view and may set its own cookies, whether or not you press play.
• Google Tag Manager (Google) - exists in the code but is switched off today; if it is switched on it loads on every page of this site, can set cookies, and can send usage data to Google. See cookies and local storage. Today, YouTube is the only third-party request that happens without any action from you.
• Our email provider - for password resets and error notifications.
• Our web host - which necessarily processes traffic to the site.

We do not sell personal information, we do not share it for advertising, and we do not disclose it to anyone else except where the law requires it.

The Forum

Anything you post in the forum or in comments is public and is shown next to your display name. Choose a display name accordingly, and do not post birth details you would not want read by strangers. Moderators can edit, hide or remove posts. See the Terms for the rules and for the licence you grant by posting.

Your Public Profile

Public by default, with a switch for every part of it.

Member profiles are public by default. Anything a public profile shows - your display name, avatar, location, the beliefs, practices and other lists you chose, your friends, favourites, quiz activity and credentials - is visible to anyone on the internet, signed in or not, and can be read by search engines. Every item has its own show-or-hide control, and the whole profile can be made private, at any time, from your account.

Avatar files are stored under random, unguessable names, but the file itself is public once its address is known - and any page that displays your avatar hands that address to everyone viewing the page. Removing your avatar deletes the file from the server, not just the link to it.

Shared Report Links

A generated report can be given a share link. That link contains a random token and, while sharing is switched on, anyone holding the link can read the report without signing in - and the report contains the full birth details it was made from. Treat a share link as public. Sharing can be switched off again, and a link can be given an expiry date. Turning sharing off invalidates the link.

Retention and Deletion

Deleting from the site marks a record as deleted. It does not erase it.

This is worth understanding properly, because it is not what most people assume. Nearly every table on this site uses a soft delete: deleting a chart, a post, a group or an account stamps a deletion date on the row and the site stops showing it everywhere. The row itself remains in the database. This is deliberate - it makes an accidental deletion recoverable and keeps a purchase history intact for accounting and dispute handling - but it means "deleted" is hidden, not gone.

Deleting your account yourself. You can delete your account from your account's Security page, and it takes effect immediately: you are signed out everywhere and can no longer sign in, your profile disappears, your friendships and pending friend requests end, and where something you wrote stays visible - a comment, a forum post, quiz or challenge activity - it is shown as "Deleted member" rather than under your name. Access to reports you bought ends with the account. Under the hood this is the soft delete described above: hidden, not gone.

The 30-day recovery window. For 30 days after you delete the account we can restore it - email us from the address on the account and it comes back as it was. Once the window has passed, your username and your profile's address are permanently reserved and will never be given to anyone else, so nobody can register your old name and appear to be you.

If you want your data genuinely erased rather than hidden, ask. Email us from the address on the account, say what you want erased, and we will remove the rows themselves. What that involves:

• Charts and reports can be erased outright, including any stored PDF files.
• Your account can be erased. Forum posts are usually detached from the account rather than removed, so that other people's conversations do not lose their replies; say if you want the posts gone too and we will remove them.
• Payment records we will normally keep, in the smallest form that still works: what was bought, when, for how much, and the provider's reference. Tax and accounting rules require a business to keep records of its sales, and a payment provider needs them to resolve a chargeback. Tell us if you object and we will explain what we are keeping and why.
• Error log entries are the awkward case, since they are append-only. We can delete rows matching your member id or IP address on request, but this must be done by hand.

The owner still needs to set retention periods. At the time of writing this site has no automatic deletion schedule: charts, reports, forum posts and error logs are kept until someone removes them. A defined retention period for each - particularly for the error log - should be decided and stated here.

Your Rights

Depending on where you live, data protection law may give you the right to see the data we hold about you, to have it corrected, to have it deleted, to get a copy in a portable form, to object to or restrict some processing, and to complain to a regulator. Exercise any of these by emailing us; we will answer within a month and will ask you to confirm you control the account before we act.

You can also do a good deal yourself: charts can be edited or removed from your account page, sharing can be switched off, and you can sign out to clear the sign-in cookie.

A note on scope. Divinity Atlas is available worldwide, so visitors from the UK, the EU and California may well be covered by the UK GDPR, the EU GDPR or the CCPA. We have written this policy to describe the system accurately and to honour the requests above wherever you live, but we do not claim certification or formal compliance with any particular regime. If you need a statement about a specific law - a lawful basis, an international transfer mechanism, or a data processing agreement - please ask.

Children

This site is not intended for children. Accounts and purchases are for adults; the minimum age is set out in the Terms. If you believe a child has given us personal information, tell us and we will delete it.

Changes to This Policy

If this policy changes we will update the date at the top. If a change alters what happens to your data in a way that matters - a new recipient, a new category of data - we will say so on the site rather than quietly editing the text.

Questions about any of this: see the contact page. See also the Terms.