Privacy Policy

Operator and contact

TwinSky is operated by Dreamie Tech Limited, a limited company incorporated in Hong Kong (company number 81310931). Registered address: Flat/Rm 917A, Blk A, 9/F, New Mandarin Plaza, No. 14 Science Museum Rd, Tsim Sha Tsui, Hong Kong. The company is the party to the service contract, the seller of points and responsible for handling personal data on this site.

Email for support, privacy, account questions and complaints: support@twinsky-ai.com. Describe the issue and the account concerned, and never send passwords or verification codes. When handling a data request we may need to verify your identity and your rights to the data.

What data we process and why

• Account and sign-in: your email, Google account identifier, verification status, necessary session data and sign-in security records, used to create your account, verify your identity and prevent unauthorized access. Google sign-in only asks for your identity and email address; it does not read Gmail, contacts or Drive, and we do not store Google access tokens.
• Birth profiles: the note, birth date and time, gender, birthplace coordinates, time zone and chart settings you enter, used to produce and save BaZi, Vedic astrology (Jyotish) and period data. The place search is only used to convert your birthplace; it does not read your live location.
• Q&A and compatibility readings: questions, relevant earlier conversation, answers, tool facts, evidence locations, the two people selected and the relationship topic, used for ongoing analysis, compatibility readings, displaying results and tracing them back. A compatibility reading does not invite the other person and never sends them the report.
• Share links and PDF export: when you choose to create a share link for a reading, we store a random link id, the answer it points to, when it was created, whether it has been turned off and how many times it was opened. Anyone with the link can see that question and reading, but not birth details, other conversations or your account. You can turn a link off on the account page at any time; deleting that conversation, the profile or the account also takes the page down. A PDF export is made by your browser on your device; this site does not keep the PDF.
• Operations and feedback: task status, usage, timing, errors, and any feedback you choose to send with related content, used for troubleshooting, security and quality evaluation. Necessary troubleshooting by a person may involve this content; it is not inaccessible to everyone.
• Technical information: receiving network requests involves IP addresses, browser request information and timestamps; the application uses hashed identifiers to prevent abuse. The hosting provider's own network or access logs are not the same as the hashed records inside the application. On a first visit, before you choose a language, the interface language follows your browser's language setting; that setting is not stored.
• Usage statistics and error reports: the dates on which an account opened the site (dates only, not pages or counts); daily totals of steps such as visiting the home page, opening the sign-in box, opening the daily reading and copying, sharing or exporting an answer, and which website or campaign tag a home-page visit came from, none of which are linked to an account, network address or device; and, when a browser error occurs, the page path, error text, code position and browser type, without the account, question or answer. These records are kept only in this site's database and used to understand whether features work and to fix faults. This site uses no third-party analytics or advertising service and sets no cookie for this. Active dates are deleted with the account and included in your account export.
• Point purchases: the order number, the pack bought, amount, currency, payment status and time, and the payment ids returned by the payment provider (Airwallex; Stripe before 15 October 2026), used to credit points, reconcile payments, handle chargebacks and refunds, and keep the accounting and tax records required by law. Card numbers, expiry dates and security codes are collected by the payment provider directly on its payment page; this site never receives or stores them. We prefill your sign-in email on the payment page so you can receive the receipt.
• Membership and report emails: for each membership payment, the payment ids, the amount, currency and points it added, and the membership status and end date (for monthly memberships that renew automatically and were started before 15 October 2026, also Stripe's subscription, customer and invoice ids and whether renewal was cancelled). We use them to apply member benefits, credit points, handle chargebacks and refunds, and keep accounting records. Members' weekly and monthly readings are worked out for the profiles chosen on the account page (up to three; by default, the earliest one with an exact birth time) and show the names you give them and sent to the sign-in email; we record whether each one was sent and your unsubscribe choice. The readings are made on our own server by chart rules, never sent to an AI model provider, and delivered through our email-sending provider.
• Invites and redemption codes: your own invite code; the invite code you used, the link between the inviting and the invited account, the points each received, the reward status and time; and records of redeemed codes (code, account, points and time). To limit repeated invite rewards from the same network, when you sign up or add an invite code later the server uses a key to turn your network address at that moment into a check value that cannot be reversed directly; the address itself is not stored. On the account page an inviter sees only how many people they invited and the points earned, never the invited people's email addresses, profiles or conversations.
• Daily check-ins: whether you marked a day's reading accurate, partly accurate or inaccurate, an optional short note and that day's tone, used to show your streak, give streak rewards and measure accuracy. They are deleted with the profile or the account and included in your account export.
• Calibrate time: how sure you are of your birth time and the matching time range, your answers to the multiple-choice and TwinSky agent follow-up questions (which may cover the rough position and side of a noticeable mole, birthmark or scar, the number of siblings, whether your father was present at your birth, traits of your partner or family, changes in your life in certain years, and the optional months when you changed jobs or schools, moved, or began or ended an important relationship), the questions shown, the scores and explanation, and the payment and refund records, used to produce the calibration result and show it again later. They are kept with the profile, deleted with the profile or the account, and included in your account export.
• Earlier closed-beta invite codes: the verification hash of personal invite codes, invite labels, claim and deactivation times, account links, points balances, hold and settlement records, and the related model usage, used to limit the beta to invited people, prevent duplicate claims and reconcile points. The original invite code is not stored in the application database; the person who issued it keeps the copy created at issuance. Anyone holding a code can sign in to the linked account, so treat it like a password and do not forward it. Signing in with an invite code does not itself send a verification request to Google or Resend, and it does not change how questions are processed downstream.

You can browse public pages without signing in; signing in is required before you enter birth details. Missing birth information affects the chart, and no reading is started unless you ask a question. The profile note is optional; we suggest a nickname such as “me” or “family” rather than a name or contact details.

Ordinary users' birth profiles, conversations and compatibility readings are separated by account ownership; other ordinary users cannot read or change them. We do not sell user data and do not use birth data for advertising profiles. There is currently no feature that uses user data for model training; troubleshooting and quality evaluation are not the same as training a foundation model. Whether outside services retain data or use it for training is described below; our practices cannot be taken as proof of every downstream practice.

Cookies and records on your device

A necessary session cookie keeps you signed in, protects against forged requests and ties the verification code flow together. Refusing or clearing these cookies may sign you out. A language cookie remembers the interface language you chose for 1 year, and when you arrive through an invite link or a reading someone shared, a cookie of up to 30 days remembers the inviter's code so it can be filled in at sign-up. One-time verification codes are stored in the application database as check values that cannot be reversed directly, and expire after 10 minutes; the service that delivers the email still processes the email body that contains the code.

The workspace may also keep your compatibility selection, pending tasks and questions in the browser's local or session storage so the page can be restored. Clearing your browser data does not delete your account on the server, and deleting your account does not clear downloaded files, screenshots or browser storage on all your devices for you. After using a shared device, sign out and clear the site data.

Third-party processing and cross-border transfers

The following describes the services connected today; it does not mean that every action sends all data to every provider. A provider's public documents are not an independent audit for TwinSky, and “not yet verified” does not mean the processing does not happen.

Where the law requires separate notice, separate consent, contractual arrangements or a cross-border assessment for some processing, agreeing to the terms and this policy at sign-in does not replace those procedures. This version has not yet completed verification of every downstream identity, cross-border arrangement and contract; disclosing this status is not a statement that all requirements are met. Please avoid including ID numbers, bank card numbers, medical records, exact home addresses or other sensitive information that is not needed in your questions.

Retention periods and limits of deletion

Accounts, birth profiles and conversations are used to keep providing the service and are usually kept until you delete them or close your account. The application is configured to clean up details of completed or failed runs after 90 days and audit metadata after 180 days. These are clean-up targets for background jobs, not a single period for all data. Actual clean-up depends on job execution; pending tasks and answer text saved in conversations are not subject to the run-detail clean-up period.

Deleting on the account page removes the corresponding data and linked records from the application's main database. Minimal security audit metadata may be kept until its clean-up period ends. Deleting in the application does not automatically ask every provider to purge backups or logs, and it cannot recall content you have already copied, shared or exported.

Points balances and history are kept with your account and deleted when you close it. Purchase records are the exception: the order number, pack, amount, currency, status and time, and the payment provider's payment ids, together with membership payment records (including earlier subscription and monthly invoice records), are the company's business and accounting records. They are not deleted when you close your account and are kept for at least 7 years, as Hong Kong's Inland Revenue Ordinance requires for business records; they are linked only to an internal account number and contain no birth data or conversations. To prevent the sign-up bonus from being claimed repeatedly after closing an account, we use a server-side key to create check markers from verified emails and sign-in identities that cannot be reversed directly to the original values, and keep them for the same 180-day clean-up cycle as security audit records. These markers contain no birth data, conversation text, plain email address or plain Google identifier. Existing accounts never receive the bonus again because run logs were cleaned up. After an account from the earlier closed beta is closed, the hash and claim marker of the used invite code are kept and unlinked from the account, and will be cleaned up according to actual retention needs after the beta ends. An allowance expiring does not delete your profiles automatically. Report email records and report settings are deleted with your account; closing the account first cancels any automatically renewing membership started earlier, so no further payment is taken.

Daily usage totals and account active dates are kept for 400 days, and browser error records for 30 days, after which a background job deletes them.

Invite and redemption records are kept with the account. When an invited account is closed, its invite and redemption records are deleted with it. When an inviter closes their account, their own invite code is deleted; the invited account keeps its claim record (including the code it used and the network check value), no longer linked to the inviter, to prevent repeated claims.

Backups may temporarily contain data from before a deletion, which must be handled through actual backup rotation or deletion procedures; we cannot currently promise immediate purging of backups or a uniform number of days that has not been verified. Where applicable law requires keeping certain records, they must be handled within the corresponding scope and period and not used for unrelated purposes. This cannot be read as keeping all data indefinitely.

Viewing, exporting, correcting, deleting and complaining

After signing in to Account & data, you can view your birth profiles and conversations, export a single reading as a PDF, delete a single conversation, delete a profile and its related data, or close your whole account. For a copy of all your account data (as a JSON file), ask through the contact channel below and we will tell you how to download it. Save any copies you need before deleting; this site has no way for users to undo a deletion themselves. If birth details are wrong, you can delete the old profile and create a new one; this is not a lossless edit that keeps the full history.

You can stop using a feature, revoke Google access or close your account; signing out by itself does not delete data. Under applicable law you may also ask us to explain our processing rules, and request correction, deletion, restriction of or objection to processing, withdraw consent and make a complaint. Contact details and the channels currently available are under Operator and contact; you can also complain to a competent regulator as the law allows. Withdrawing consent does not affect processing carried out on a valid basis before the withdrawal.

Other people's data and minors

Only submit information you have the right to provide. Before creating a profile for someone else or running a compatibility reading, let them know the purposes, outside processing and deletion methods described here, and obtain the authorization required by applicable law. Data stored in your account does not mean you own another person's rights in their personal information.

Use by minors, or use of a minor's information, must also meet local guardian-consent and special-protection requirements. Separate children's accounts, guardian verification and dedicated children's privacy rules are not in place yet, and consent at sign-in is not verified guardian consent. Do not use astrology conclusions to give children fixed labels or to replace educational, medical or other professional judgment.

Security and changes to this policy

The application uses account-level access control, necessary session and request checks, hashed verification codes and rate limiting; the production site is served over HTTPS. No system can guarantee absolute security. Do not share verification codes, passwords or links to reports that contain personal data.

If a security incident involves personal information, remedial steps and notifications must follow the applicable requirements. When purposes, recipients or rights arrangements change significantly, this notice must be updated first, and valid consent obtained again where the law requires it; simply “continuing to use the service” cannot replace that. The page version distinguishes notices, and earlier sign-in records are never retroactively counted as consent to this new version.