TRUE SUN Legal & help
Privacy policy
Account data, selected places, store transaction IDs, rule acknowledgements, refund records, and AI processors; website reading page data, source records, consented ad measurement, and retention.
Last updated
About this policy
This policy explains how TRUE SUN / 正阳易理 collects, uses, discloses, and retains personal information for accounts, reports, daily reminders, in-app purchases, and the website reading page. We handle your information under Malaysia’s Personal Data Protection Act 2010. For personal data collected in Singapore, we also comply with Singapore’s Personal Data Protection Act 2012 (PDPA).
Information we collect
Account data: sign-in email, one-time-code session, account id, and previous emails after a change (used to match purchases).
Profiles and questions: names, birth details, gender, occupation, birth place or Question place (city, country, timezone, and coordinates of the place you select), question text, generated reports, and look-back feedback you add after a Question.
Purchase verification: store transaction IDs, product IDs, and receipts or notifications from the app store, used to write entitlements. The app does not collect card numbers or full payment credentials.
Rule acknowledgements: time, rules version, and context (birth confirm, relationship comparison). Refund-review usage consent is stored separately and is not invalidated by a rules-version bump.
Relationship comparison invites: the relationship type, how it is shown (the same report or separate versions), status and times. Codes are stored only as an irreversible hash, never as the code itself. The time and rules version of the other person’s agreement, both display names (up to 40 characters), the report text, and related notices.
Refund records: the original store transaction id and account flag after a store refund or void, used to remove unused quota and notice repeat refunds.
Feedback: the feedback type and message you submit in the app, an optional reply email, app version, device platform, and interface language, used to handle and reply to your feedback.
Push notifications: once you allow notifications, this device's push token, device platform, and interface language; the “Remind me daily” switch and time. Deleted with your account.
Support records: When you use the Help Center we keep your account ID, the issue type, related report or purchase IDs, app version, platform, the short message you write, and a log of how we handled it. These records never include your birth details or payment card data. We use them to fix your issue, improve the service, and as evidence if a dispute arises. Records are kept for 24 months. Deleting your account deletes these records unless the law requires us to keep them.
What you must provide
Your sign-in email is required to have an account. Birth details, gender, and the relevant places are required for reports, daily reminders, and relationship comparisons. Occupation and referral codes are optional; chat memory is on by default for all users and can be turned off at any time in memory settings.
If you do not provide required information, we cannot provide the related feature. Leaving out optional information does not affect other features.
Place data and current location
Birth place is searched or selected by you. For a Question you may type or search a place, or tap Use current location. Only that tap asks the system for while-in-use location and reads coordinates once, to convert local time and local solar time. You may refuse and search or type a place instead. We do not track you in the background and we do not use location for ads.
Coordinates are sent to a third-party place service to resolve city, country, timezone, and a place label. Typed or searched places also go through that service. After you confirm, the label, city, country, timezone, and coordinates are stored with that question on the account and the report request, and are used by the chart calculation that runs on our cloud servers and by the AI service that writes the report text. Retention matches that question and the delivered report.
How information is used
Data is used for services you choose: charts and reports, daily reminders, push notifications (report ready, “Remind me daily”), Outcome reminders, entitlement checks, order matching, support, and removing unused access after a store refund under our rules. Outcome reminders can be turned off in account settings.
We do not sell birth details to unrelated parties, and we do not infer relationships you did not set.
Purchase verification and refund-review usage information
In-app purchases are processed by the app store, and web purchases by Stripe. Our server writes entitlements only after it verifies a store receipt, Stripe payment record or notification.
When the app store reviews a refund or chargeback for a purchase on this account, we give it delivery and usage information for that purchase (such as the transaction ID, whether it was delivered, generation times, uses consumed and the share used, days used, failures, and our suggested handling) only if you have separately agreed. You agree through the toggle in Me → Data and privacy; it is off by default and can be withdrawn at any time. This information does not include report text, chat content, or birth data. If you have not agreed or have withdrawn, we do not send it. A tick on an older version of the usage rules does not count as this consent. Whether or not you agree, we keep internal delivery and usage records to verify usage, apply post-refund usage-balance rules, handle refunds and disputes, and keep the service operating reliably. None of this decides whether the app store grants a refund.
Processors
Accounts and profiles are stored in a third-party cloud database. App APIs and chart calculation run on a third-party cloud computing platform. Payments are processed by the app store (in the app) or Stripe (on the web). Place search uses a third-party place service. Reports, profile analysis, and chat are generated by third-party AI workflow platforms and AI model providers. Feedback notification emails are sent through the email delivery provider Resend. Report-ready and “Remind me daily” push notifications are sent through a third-party push notification service. Those processors receive data only as needed to provide the service. What each type of processor does and receives is on the Third-party services and processors page on this site.
Data in transit uses HTTPS. The app does not include an advertising identifier or a tracking SDK.
The app stores one acquisition source (link parameters, the app install source, or a channel you tap), an optional referral code, and product events that do not include question text, for account operations and referral settlement.
A referral code only records who introduced you. Entering or sharing one gives neither person a reward, discount, or extra counts. When a referral link is opened or a referral code is entered, we record only the code, the event type, and the time. The network address used for rate limiting is kept only as an encrypted hash, never in raw form, and is not used for ad tracking.
Under the Malaysian and Singapore personal data protection laws (PDPA), you can access, correct, or delete your data, including referral codes and two-person reading invite records. Contact details are on the Contact page of this site.
Chat history and chat memory
The chat drawer can turn saved history off. New chats then stay in the current session; the server keeps quota and de-duplication records without message text. When history is on, the account keeps chat text and expired text is removed on a schedule.
Chat memory is on by default for all users and can be turned off at any time in memory settings. When it is on, we remember what you share in chat that helps later conversations continue naturally, such as what you care about, your preferences, or where the last chat left off. When something is remembered, the chat shows a short remembered note. You can view, correct, or delete any memory item in memory settings; turning memory off stops new memories, and deleting removes that item. Memories unused for 4 months are deleted automatically. Memories are used only for your own chats and are never shown to other users. We may use anonymised, aggregated patterns that contain no names, birth data, or quoted messages to improve answer quality. Chart and report results are calculated on request and are not stored as chat memory.
Chat is sent to third-party AI providers to generate replies. This service’s chat-text retention does not mean those providers’ logs, backups, or legal holds are deleted on the same day.
If you say in chat that a reading was inaccurate or the opposite of what happened, we store a separate note: ID and card numbers in your words are masked, together with how many days had passed since that reading was cast and the timing window noted on the report. The note stays on your account so you can ask us to delete it. We use it only to improve readings, not to identify you, and not for advertising or marketing. It is deleted with the account. You can also ask us to delete it sooner through this site’s Contact page.
Please do not enter other people’s ID, card, or other sensitive numbers in chat.
Cross-border transfers
Our processors’ servers may be located outside the country where you live, including outside Malaysia and Singapore. We transfer data only as needed for the features you use, and we choose providers that commit in their terms or data processing agreements to protect personal data, so that transferred data receives protection comparable to applicable law. When you use those features, your data is processed abroad as described in this policy.
Retention and deletion
Account data is kept while you use the service. Payment, refund, and usage-balance records are retained for tax, dispute handling, and refund and entitlement reconciliation even after the sign-in account is deleted; those records have email and plain purchase tokens removed. For deleted accounts, plain store transaction IDs and purchase tokens are not kept; related identifiers are stored only as one-way hashes. Refund and usage-balance records are usually kept for up to seven years after the last related transaction or the close of a dispute, or longer where the law requires; after that we delete them or irreversibly de-identify them.
After in-app deletion, people, chat, memories, and report text are removed from this service and are not restored if you sign up again. Store subscriptions must be cancelled in the app store. This page and the contact page are a backup if you cannot open the app. They are not the in-app deletion path.
After deletion we do not keep the email address, name, or purchase token in plain text. To recognise the same email, keep that self and an active store subscription, and keep current-period usage and paid credits consistent with the account before deletion, we keep a server-keyed hash of the email, a hash of the self birth details, a hash of the store subscription identifier, and the usage, credit, refund, and self-lock state required for that. A hash cannot be turned back into the original value. A different email is a new account and cannot take the previous subscription.
Your rights
You may correct profiles in the app where the lock rules allow. You may also ask support to give you access to or a copy of your data, correct inaccurate data, restrict processing, or withdraw an optional consent (some features may then stop working).
We reply within the time the law requires; access and correction requests are generally handled within 21 days. To protect your data, we may ask you to write from your sign-in email so we can verify it is you. Mandatory legal rights are not reduced by this policy.
Data protection officer and data breaches
We have appointed a data protection officer (DPO) to handle questions, access and correction requests, withdrawals of consent, and complaints about personal data. Email: truesun391@gmail.com.
If a data breach happens, we will contain it and assess its impact promptly. Where applicable law requires notification (for example, in Singapore, when 500 or more people are affected or significant harm is likely), we will notify the authority within the legal deadline and tell affected users.
Relationship comparison invites: what each side sees
Before the other person taps Agree, they see nothing about the person who invited them; the person who invited learns that they joined only after they agree.
After that, each side sees only the other’s display name (up to 40 characters) and the report. Neither side can see the other’s birth details, chart, or other reports. During generation, both people’s birth details are used for that one calculation only and are kept with that generation request, not shown to either side.
The report is shown per reader: each person reads themselves as “you”. With “Separate versions”, the invited person does not see which relationship was picked; the “Getting closer, naturally” part of Someone I like is shown only to the person who invited.
If either side deletes the comparison, both copies of the report text are removed from the service, and the other side only gets a notice that it is no longer available, not who deleted it. To take part, the invited person needs their own account and their own birth details, which are handled under this policy and section 3 of the terms of service.
Information about other people
If you enter a family member or another person, you confirm you have their consent and that the details are accurate. If you enter a child, you confirm you are their parent or legal guardian. Relationships are set by you. The system does not infer them.
Typed-in details for a relationship comparison: the other person’s birth details and nickname you enter are kept in your account only with that one comparison (its generation request and report). They are not added to your family list and are not shown to the other person or any other user. The nickname is shown only in the app and is never sent to the AI service. You must confirm the other person agreed before generating. They are deleted when you delete your account.
Contact and changes to this policy
Send privacy requests, questions, and complaints through this site’s Contact page. Operator details are on that page.
When we update this policy, we change the date on this page; material changes are announced in the app in advance.
Website reading page: what we collect
This section and the ones after it cover our website reading page, where you can see a free birth chart and a general 2027 preview, and leave your email to get a personal AI reading. The free chart is calculated on our server: the birth details you enter are sent to our server, which returns the chart and does not store your details at this step. The general 2027 preview is the same for every visitor and does not use your details. When you search for a birth city, the words you type go through our server to a third-party place service, which returns the city, country, timezone, and coordinates.
When you ask for the AI reading, we collect your email; the birth date, birth time, gender, and birth place (city, country, timezone, and coordinates) you enter; and the consents you tick (privacy policy, being at least 18, using your birth details to create the analysis, and optional marketing email), each with its version and time. The email code is stored only as a one-way hash.
Where you came from: the link parameters on the page you arrived at (utm parameters such as source, medium, campaign, content, and term), the referring page, the landing page address, and the time of your first visit. Ad click IDs (such as fbclid, ttclid, and gclid) are kept only if you accept ad cookies, as explained below.
To stop automated bulk sign-ups, the site uses a third-party bot check service, which receives your IP address and browser details to run the check. We count submissions using server-keyed hashes of your IP address and email. We do not store your IP address in plain text.
Fair use: in your browser, the site turns basic browser details (browser type, language, timezone, and screen size) into a device hash that cannot be reversed, and sends only that hash with each request. Our server keys it once more and uses it only to count use and limit how often requests can be made. The hash is not used to identify you and is not stored with your email or account. The raw browser details never leave your browser.
How we use website data
To send a 6-digit code to the email you enter and confirm the email is yours.
To use your birth details to create the AI reading and a 2027 preview and show them on the page only. The website readings (your personal AI reading, your personal 2027 preview, and the general 2027 preview) are not saved to your account and are not shown in the App.
If the email has no account with us yet, we use it to create one and save your birth details and chart, your own profile, the analysis the App creates for a new account, and today’s daily reminder in it, so they are there when you sign in to the App with the same email. The website readings are not among them. If the email already had an account before you used the website, we do not change anything in that account.
If you later change your birthday on the website, we update the birth details in the account only while the account has not yet been opened or confirmed in the App; after that, the website only shows a preview and does not change the account.
To count which channels and ad campaigns bring visitors, sign-ups, and later use. We do this in our own systems (first-party). Internally we combine the source with whether the account signed up, opened the App, or bought something. These figures stay with us and are not given to ad platforms.
To send marketing email, only if you ticked the separate marketing box.
Source records, cookies, and ad pixels
The site keeps the source details and your cookie choice (with its version and time) in your browser’s storage. This is first-party data, used only as described above. Your first source is kept for 30 days, and later visits in that time do not replace it.
So you can pick up the same reading after a refresh or when you reopen the page, your browser keeps a resume reference in its local storage for up to 24 hours, and then it expires. It does not contain your email, birth details, the question you typed, or the reading text.
The cookie bar has equal Accept and Decline buttons, and no ad tag loads by default. Only if you tap Accept does the site load the Meta and TikTok pixels and the Google Ads conversion tag, and keep ad click IDs (fbclid, ttclid, gclid). If you tap Decline, no ad tag loads, click IDs are discarded, and we keep only which platform you came from.
Pixel and conversion tag events carry only the event name (email confirmed or account created) and an event ID. They never carry your email, birth details, or reading text.
Ad measurement with your consent
Only if you accept ad cookies, our server sends events to Meta, TikTok, and Google Ads, only to measure which ads bring website sign-ups. It sends just two website events: when you confirm your email (Lead), and when the site creates an account for you (CompleteRegistration). Each event has the event name, time, and ID, the page address, the ad click ID (kept only with your consent), and a SHA-256 hash of your email after spaces are trimmed and it is changed to lower case. The server sends only this hash, never your plain email. Your IP address and browser details are passed along with the request; we do not store them.
We never send your plain email, birth details, or reading text. A hash is not anonymous: the ad platform can match it to an account on its side. If you do not accept, we send no events.
App activity and purchases are not shared with ad platforms
We do not send App usage, in-app purchases, subscriptions, renewals, or any App event linked to your email, App account, or device to Meta, TikTok, Google Ads, or any other ad platform. The App has no ad SDK and does not read the advertising identifier.
Withdrawing consent and unsubscribing
Ad cookies: use the “Change choice” link on the website at any time and pick Decline. The site then stops loading pixels and conversion tags, and we stop sending ad measurement events. Events already sent are handled under the ad platform’s own policy, and you can manage them in that platform’s settings.
Marketing email: use the unsubscribe link in any marketing email, or contact us. After you unsubscribe, we keep only your email and the opt-out record so we do not email you again.
Other consents: contact us as described in “Your rights” above, or delete your account in the App. If you withdraw consent to use your birth details for the analysis, we can no longer create a website reading for you.
How long we keep website data
Submissions where the email was never confirmed: deleted after 7 days.
Accounts created through the website that were never signed in to in the App: deleted after 90 days through our normal account deletion process.
Birth details and the calculated chart on website submission records: cleared after 90 days.
Ad click IDs: deleted after 180 days; we keep only which platform you came from.
Records of ad measurement events: deleted after 90 days. They never include the email hash or IP address.
Marketing email data: kept until you unsubscribe.
Once you sign in to the App, your account data follows “Retention and deletion” above.
Website age requirement
The website reading and accounts created through it are only for people who are at least 18 years old. You must confirm you are 18 or older before you get the AI reading. We do not knowingly collect data from anyone under 18, and we delete it if we find out.
Website processors and cross-border transfers
For the website we use a web hosting and bot check provider, a cloud database, the email delivery provider Resend (codes and marketing email), a place service, AI workflow platforms and AI model providers, and, only with your consent, Meta, TikTok, and Google Ads. Their servers may be outside Malaysia and Singapore; these transfers follow “Cross-border transfers” above. Provider names are on the Third-party services and processors page on this site.