Privacy Policy

This Privacy Policy explains what information Sablestar (a service of Iterategy LLC, Iterategy LLC, Delaware, USA) collects, how we use it, and the choices you have. Questions can be sent to support@mail.sablestar.com.

1. What we collect

To produce your natal-chart report we collect:

• Birth data: the name you provide, date and time of birth, and birthplace (with the latitude and longitude derived from it). This is the minimum required to compute a natal chart.
• Email address if you provide one at checkout, used for purchase receipts and customer support.
• Payment information is processed by Stripe and never reaches our servers. We receive only the metadata Stripe returns (order id, payment status, last 4 digits of the card). To fulfil and re-deliver your purchased report, we also store your birth details (name, date, time, and birthplace) in the Stripe Checkout Session metadata attached to your order.
• Operational logs: standard request logs (IP address, user agent, timestamps) retained for short periods to keep the service running and to detect abuse.

2. How we use it

• To compute and render your natal-chart report.
• To send your birth chart to our language-model provider (OpenRouter / Anthropic) so it can write the interpretation attached to your report. The provider acts as a processor and is instructed not to retain prompts for training.
• To process your payment via Stripe.
• To respond to support requests, prevent abuse, comply with legal obligations, and improve the service.

3. Retention & deletion

Sablestar does not maintain its own database of birth records. Your birth data is sent to our chart engine and to the language-model provider to generate the report. The report itself is delivered to your browser and as a PDF you can download; we do not retain a copy server-side.

When you pay for a report, your birth details (name, date, time, and birthplace) are stored in the Stripe Checkout Session metadata so that we can fulfil your order and re-deliver the report if needed. Stripe retains purchase records — including that birth-data metadata — for tax and accounting purposes per Stripe’s own privacy policy. You may request deletion of your data by contacting us at the address below. Standard request logs (including IP addresses) are kept for up to 30 days for security and abuse-prevention.

If you believe we are holding personal data about you and would like a copy or deletion, email support@mail.sablestar.com from the email address used at checkout. We will respond within 30 days.

4. Your rights (GDPR / CCPA)

Depending on where you live, you may have the right to access, correct, or delete the personal data we hold about you, to object to or restrict certain processing, or to data portability. California residents have additional rights under the CCPA, including the right not to be discriminated against for exercising them. We do not sell personal data.

To exercise any of these rights, contact us at support@mail.sablestar.com.

5. Subprocessors

We rely on the following third parties to deliver the service:

• Vercel — hosting and content delivery.
• Stripe — payment processing.
• OpenRouter / Anthropic — language-model API for the written interpretation.
• OpenStreetMap (Nominatim) — geocoding the birthplace you enter into latitude/longitude.
• PostHog — product analytics (first-party cookie; data is not used for advertising).

6. Cookies

We use sessionStorage in your browser to remember your in-flight birth details between the form and the report screen — it is cleared when you close the tab.

We also set a first-party analytics cookie, sablestar_did, via PostHog. This cookie assigns your browser a pseudonymous identifier used solely for product analytics (e.g. measuring which steps of the funnel are completed). It does not track you across other websites and contains no personal data. You can block or delete it through your browser settings.

7. Children

Sablestar is not directed to children under 16, and we do not knowingly collect personal data from them.

8. Changes

We may update this policy from time to time; the "Effective" date at the top reflects the latest version.