Privacy

Synastry Stories (“we”, “us”) is operated by DAN-GABRIEL TOMESCU, an independent developer established in Romania. We are the data controller for the personal information described in this policy. Because we are established in the European Union, the GDPR applies to us directly.

For any privacy question or request, email privacy@synastrystories.site. You can always reach us through Support.

We collect the birth details and nicknames you enter so we can compute a chart and write a scene. We store that encrypted. We send derived chart information (never your raw birth date, time, or coordinates) to Anthropic to generate the text. We do not sell your data, we do not run advertising, and we use no third-party analytics. You can download everything we hold on you and delete your account from inside the app.

Birth and identity details you enter. Nicknames for yourself and the other person, birth date, optional birth time, optional birth place, and the time zone we resolve from it. If you leave birth time blank, we mark the chart as low-confidence and withhold time-dependent statements rather than guessing.

Account details, if you create one. Email address, an optional display name, and a password. We store a bcrypt hash of the password, never the password itself.

What you play. Which scenes you start, the choice you pick, the generated story, reveal, and bridge text, the bridge tools you earn, share cards you create, and any scene rating or report you submit. This lives in your browser and, when you are signed in, on our servers so it can sync across your devices.

Two-sided invites. If you invite someone, we store the invite, the scene snapshot, and both parties’ birth details. See Information about someone else.

Friend Council. If you ask friends what they would do in a scene, we store the question: the scene title, the scene setup, the answer choices, the relationship type, and the choice you picked. The link you share shows the scene title, setup, and choices, but never your own pick, your nickname, birth details, or private notes. Each vote is stored as the choice the friend tapped, tied only to an anonymous browser identifier so one browser votes once; we do not record who voted.

Usage events and device information. An opaque client identifier, user-agent string, browser locale, timestamps, and a salted, truncated hash of your IP address. The IP hash exists to enforce rate limits and free-usage quotas, so that clearing your cookie does not reset them. It is never displayed, never joined to your account, and never used for advertising. We do not store your raw IP address.

Payment information, once paid plans are live. The store you bought through, the product, the amount, the order or transaction identifier, and subscription status. Card and bank details go directly to the store and never reach our servers.

Support correspondence. Whatever you send us, including your email address and the contents of your message.

The app is built around two people, so you can enter another person’s nickname, birth date, and optionally their birth time and place. That person may not know you are using the app. Please only enter details about someone you would be comfortable telling, and do not use the app to surveil, monitor, or pressure anyone.

If someone entered information about you. You can ask us to remove it without creating an account. Email privacy@synastrystories.site or use Support with enough detail for us to find the record, such as the link you were sent. We will delete the birth details, nicknames, and generated text relating to you and tell you what we removed.

What an invite link reveals. When you send someone their side of a story, that link shows your nickname, the relationship type, and the scene text. It does not reveal your birth time or place, which choice you picked, or any private notes. The other person’s birth details are used to generate the bridge scene and are not exposed on the invite page itself.

Relationship difficulties are personal, and some of what you type may touch on mental health, abuse, or crisis. We treat that carefully.

We check your input for safety signals. Before a scene is generated, and again on the reveal and brief steps, we scan the text you entered for indicators of self-harm, violence, threats, stalking, or coercion. If we detect one, we stop generating the scene and show support information instead, including crisis helplines for your region.

We do not keep the text that triggered it. We record only that a safety check fired and which categories matched, so we can measure whether the safety net is working. The wording you typed is not stored for that purpose.

Where you have told us about your health or safety, we process that information on the basis of your explicit consent, given by choosing to enter it, and solely to keep you safe and to avoid producing harmful content. We do not use it to profile you, advertise to you, or share it with anyone beyond the service providers listed below.

Under the GDPR and UK GDPR we need a legal basis for each purpose. Where you are outside those regimes, the “why” column still describes what we do.

• To compute your chart and generate your scenes - performance of our contract with you.
• To create and secure your account, sync your data, and let you sign in - performance of our contract.
• To prevent abuse: rate limits, quotas, and fraud prevention - our legitimate interests in keeping the service available and affordable for everyone.
• To run safety checks and show crisis support - our legitimate interests in protecting users, and your explicit consent where the information concerns health or safety.
• To take payment and manage subscriptions - performance of our contract, and our legal obligations to keep financial records.
• To answer your support requests - our legitimate interests in helping you, and performance of our contract.
• To understand how the product is used in aggregate - our legitimate interests in improving it. This uses our own first-party events only.

We do not use your information for automated decision-making that produces legal or similarly significant effects about you. The AI writes reflective text; it does not decide anything about you.

Stories, reveals, briefs, and bridge scenes are written by Anthropic’s Claude. What we send for each request is:

• chart placements derived from your birth data - planet positions by sign, element, and modality, the ascendant sign and degree, aspect descriptions, derived relationship tags, transit lines, and a confidence line;
• the nicknames you entered;
• the relationship type; and
• the free text you typed for that particular reading.

Raw birth date, birth time, coordinates, time zone, and birth-place text are never included in the request. Under Anthropic’s commercial terms, inputs and outputs are not used to train their models; see their commercial terms.

We do not sell your personal information, and we do not share it for advertising or cross-context behavioural advertising. We use no advertising services and no third-party analytics. These are all the organisations that receive personal information from us:

• Anthropic (AI provider, United States) - the derived chart placements, nicknames, relationship type, and free text listed above.
• OpenStreetMap / Nominatim (geocoding) - the birth-place text you type, so it can be turned into coordinates. The request carries only that text, with no account or device identifier.
• Wikimedia / Wikidata (public-figure lookup) - the name you search for. This feature is limited to signed-in users on the premium plan and only runs when you use it.
• LemonSqueezy (web payments) - when billing is enabled on the website, your order and customer identifiers, product, amount, and subscription status. Card details never reach us.
• Our hosting and database providers - the application is hosted on Vercel and the database runs on a managed PostgreSQL host. They process data on our instructions as processors.
• Professional advisers and authorities - only where we are legally required to disclose, or need to establish or defend legal claims.

We are established in Romania, in the European Union. Our hosting and database providers, and several of the processors listed above including Anthropic, are located in the United States, so the personal information we hold is transferred outside the EEA.

For those transfers we rely on appropriate safeguards under Chapter V of the GDPR - principally the European Commission’s Standard Contractual Clauses with each provider - together with a transfer risk assessment and, where necessary, supplementary measures. You can ask us for more detail about the safeguards we rely on using the contact details below.

We use a small number of first-party cookies. None of them are for advertising, and we do not use third-party tracking cookies.

• ss_cid - an anonymous identifier for your browser. It lets you use the app before creating an account and keeps your saved state across visits. Lasts up to 2 years. Session-only for page scripts: it is marked HttpOnly, so no page code can read it.
• ss_user - your signed-in session token, set only when you sign in. Cleared when you sign out or delete your account.
• ss_admin - a separate session cookie for our internal admin tools. Ordinary users never receive it.

All three are first-party, marked HttpOnly and SameSite=Lax, and set as Secure over HTTPS.

Local storage. Your in-progress and saved app data is kept in your browser’s local storage so the app works offline and loads quickly. This copy is not encrypted, so anyone with access to your device and browser profile can read it. “Reset local data” in the You tab clears it.

• Account and synced app data - your account, birth profiles, relationships, story history, and earned bridge tools are kept until you delete your account.
• Usage events - deleted automatically 90 days after they are recorded, including the salted IP hash, by a daily cleanup job.
• Two-sided invites that are never accepted - deleted 30 days after they are created.
• Friend Council questions and their votes - deleted 30 days after the question is created.
• Purchase and subscription records - kept as long as tax and accounting law requires, even after you delete your account. These records are held by the payment provider and by us and are limited to what the law requires.
• Support correspondence - kept while your request is open and for a reasonable period afterwards so we can follow up.
• Deletion audit records - when an account is deleted we keep a record that the deletion happened, containing no birth data, names, or story content, so we can show the request was honoured.

• Encryption at rest. Birth dates, birth times, time zones, coordinates, birth-place text, and nicknames are encrypted with AES-256-GCM before they are written to the database. The keys are held separately from the data.
• Passwords are stored only as bcrypt hashes and can never be read back.
• Transport. Traffic to and from the app is served over HTTPS only.
• Access control. Internal admin tools require a separate login and session, and privileged actions are written to an audit log.
• Abuse controls. Mutating requests are checked for cross-origin origin, and the main endpoints are rate limited to prevent scraping and resource abuse.
• Data minimisation. We do not collect advertising identifiers, contacts, location, camera, or microphone data, and the Android app requests only the internet permission.

No system is perfectly secure. If we ever become aware of a breach affecting your personal information, we will notify you and the relevant authority as required by law.

Depending on where you live, you may have some or all of the following rights. We honour these requests for everyone, wherever you are:

• Access - get a copy of the personal information we hold about you.
• Portability - receive it in a structured, machine- readable format.
• Correction - have inaccurate information corrected.
• Erasure - have your account and personal information deleted.
• Restriction and objection - ask us to limit or stop certain processing.
• Withdraw consent - where we rely on consent, withdraw it at any time without affecting what we did beforehand.
• Non-discrimination - we will not degrade the service because you exercised a right.

Self-service. While signed in, download everything we hold on you as a JSON file from your data export, and delete your account from the You tab. To clear only the copy on this device, use “Reset local data”.

If you cannot sign in. Follow the steps on Delete your account, or email privacy@synastrystories.site. We respond within 30 days, usually much sooner, and we may ask you to confirm your identity first so we do not delete the wrong person’s data.

California residents. We do not sell or share your personal information as those terms are defined by the CCPA/CPRA, and we have not done so in the past 12 months. We do not use or disclose sensitive personal information for purposes beyond providing the service. You may exercise the rights above, and an authorised agent may act for you.

Synastry Stories is for adults aged 18 and over. We do not knowingly collect information from anyone under 18. If you believe a minor has used the service, email privacy@synastrystories.site and we will delete the associated data promptly.

If we change how we handle your information we will update this page and change the date below. For material changes we will also tell you in the app or by email before the change takes effect.

Email privacy@synastrystories.site for anything in this policy, or use Support. If you need our postal address, for example to serve a legal notice, ask us and we will provide it.

If you are not satisfied with how we have handled your request, you have the right to lodge a complaint with a supervisory authority. In Romania that is the National Supervisory Authority for Personal Data Processing (ANSPDCP), dataprotection.ro. If you live in another EU or EEA country, you may complain to your own national authority instead. We would appreciate the chance to put things right first.