Optional analytics are off unless you allow them. Necessary reading access, security and payment records are separate. Refusing analytics does not prevent use of the service. Browser storage notice · Privacy choices and requests
Real Nova World Corporation operates Bondora and is responsible for the personal information described in this notice. Our business contact address is 5538 E Galbraith Rd, Apt 38, Cincinnati, OH 45236, United States. Contact real@realnova.world for privacy questions and requests. You may also contact real@realnova.world for help directing a request.
This notice covers visitors, people who request or pay for readings, people whose information is supplied for a reading, and people who contact us. It does not govern a payment provider’s or another external service’s independent activities. Those providers issue their own privacy notices.
2. Information we collect
Information for a reading. New readings collect a relationship situation, question and any included follow-up questions you submit. The new form does not request names or birth profiles. Your free text may nevertheless identify you or another adult. Older saved readings may retain names or aliases, birth dates and optional birth times or places originally supplied under the applicable earlier notice; removing those fields from the new form does not erase older records.
Generated information and inferences. For new reflections we store your original statements, displayed clarification questions, actual answers or skips, input revisions, preparation status, preview, full report and follow-up answers. Clarification questions and unselected options are not recorded as your facts. Earlier fixed-exercise reports retain their original identifiers and text. We retain relevant generation records, including input statements, outputs, model and prompt versions, processing status and error or safety information. Legacy readings may contain structured signals, scores, labels or earlier generated interpretations. These records can be personal information even when an interpretation is uncertain or wrong.
Purchase information. We receive information needed to administer a transaction, such as the PayPal order and capture references, amount, currency, payment or refund status, and timestamps. Payment-provider responses may also contain payer contact or account-identification information. PayPal handles payment credentials within its own flow and hosted card fields. Eligible checkout may also offer Apple Pay or Google Pay. Their browser SDKs and payment sheets handle wallet eligibility and authorization; wallet payment data is passed directly to PayPal, and Bondora does not receive full card numbers or security codes. Only the saved order reference is sent to Bondora for capture and status checks. No relationship question or report is sent to wallet providers. Do not send us your PayPal password or full payment card details.
Before a new purchase, we record your actual personal-use and adult/legal-capacity confirmations. We do not ask for a service country, state, city or postal code. When you first create a reading and when an order is created, trusted hosting request information may provide approximate country and first-level region. We retain available values, their source, observation time, quality status and approximate accuracy; missing, malformed or untrusted information remains unknown. Country can be known while region is unknown. Network/VPN changes or differences from PayPal billing information do not automatically reject a purchase, remove access or trigger a refund. These observations are not verified residence, domicile, nationality, tax residence or service-receipt location. No GPS permission, precise coordinates, city, postal code or full IP is added to these financial observations. PayPal billing facts remain separately sourced.
These minimal observations are used only for restricted financial administration, compliance and disputes, with the accepted product, price, legal and tax-arrangement versions, actual fees/net receipts, delivery and refund records. They are not sent to AI prompts, advertising profiles or optional product analytics. Unpaid reading observations follow the existing seven-day draft/preview cleanup policy. Immutable order-time observations follow RNWC's seven-year minimal financial voucher policy and remain separate from private relationship content. Authorized RNWC personnel may securely export the necessary financial facts for its confirmed accountant or legal advisers; no automatic external disclosure occurs. Financial exports exclude reports, questions, third-party names and private access credentials. Missing fee, final tax classification or payable-tax facts remain unknown until established, without changing the agreed final customer total.
Technical and usage information. Our website and infrastructure receive information needed to deliver and secure a connection, such as IP addresses, request times, browser or device information, requested resources, and error information. Private session identifiers protect access to readings. Where you permit optional analytics, we use limited interaction events to understand navigation and product use. A pseudonymous identifier or an event connected to a reading is not necessarily anonymous.
Choices, permissions, and correspondence. We record relevant policy versions, the time and scope of an agreement or choice, reading and support references, and communications about support, refunds, or privacy requests. We do not ask you to submit a government identity document as a routine condition of using the reading service.
Service eligibility. Ordinary access does not require a geographic declaration or a market cookie. Age, legal capacity, permitted personal use and actual privacy/terms choices remain separate. Historical geographic declarations remain part of their original records; narrowly authorized legacy controlled tests retain their original scope.
3. Where information comes from
Information comes from you, the browser or device used to access Bondora, our service providers, our generation processes, and—when someone requests a compatibility reading—another person who submits your details. A person submitting someone else’s information is asked to have informed permission or other lawful authority and to share this notice. That request does not replace our own obligation to establish an appropriate legal basis or provide information where required.
We do not request your precise current device location or a birth place in the new reflection form. Do not provide a home address, private correspondence, identity numbers or sensitive personal details in a reading question.
4. Why we use information
We use reading information to create the preview or report you request, supply included follow-ups, maintain the reading’s state, and provide paid access. We use purchase records to verify payment, prevent duplicate charging, reconcile transactions, handle refunds and disputes, and meet financial recordkeeping obligations.
We use necessary technical information to maintain service availability, investigate errors, protect private readings, prevent abuse, and respond to security incidents. We use support and rights-request information to verify a request proportionately, communicate with you, and resolve it. Authorized personnel may review relevant information when necessary for these purposes; the service is not represented as end-to-end encrypted or inaccessible to its operator.
With your choice where required, optional analytics help us assess which features are useful and identify usability problems. Reading questions, names, birth details, private access credentials, and report text are not permitted as product-analytics event properties. Operational generation records are separate from product analytics and may contain reading content.
We do not sell personal information or share it for cross-context behavioral advertising. We do not use private reading content to train our own or a provider’s general-purpose AI models. Those commitments do not mean that no service provider processes information to supply or secure the service. Any future materially different use would require an appropriate notice, legal basis, and choice before it begins.
5. AI processing
Bondora uses the OpenAI API to decide whether optional clarification would help and to write new reports. Requests include your original situation, the actual clarification history and relevant revisions. Full generation also uses the saved opening and private outline. For follow-ups on new reports, the saved article and source statements accompany your new question. Earlier fixed-exercise reports continue to use their original selection method. No payment credentials, separate names, birth profiles or astrological signals are needed. Older generation records and saved reports may reflect the earlier method described in their original notice. Do not assume that text sent to AI is anonymous.
OpenAI states that API data is not used to train its models by default unless the customer opts in. Its API services may retain content for abuse monitoring and other service-specific purposes, subject to its current terms, settings, and applicable exceptions. This is not a promise of zero retention. Bondora’s own saved reading and generation records are separate from a provider’s retention. The current provider and processing information is available through our Privacy Choices and Requests page or from real@realnova.world.
AI interpretations are not verified facts about you. We do not use reading scores to make decisions about your eligibility for employment, credit, insurance, housing, or similar opportunities. You may contact us about inaccurate personal information or an inference associated with you.
6. Who receives information
We provide information to service providers only as relevant to their role: hosting and content delivery; database storage and backup; AI generation; security and operational support; payment processing; and delivery of support or transaction communications. Providers may process information under our instructions or, for activities such as a payment provider’s fraud prevention and legal compliance, under their own legal responsibilities.
We may disclose information when necessary to comply with a lawful requirement, protect rights and safety, investigate fraud or security problems, or establish or defend a legal claim. We assess the scope of a request and do not treat every request for information as automatically valid.
If the business is reorganized, sold, or transferred, relevant information may be disclosed with appropriate safeguards and subject to applicable notice and other requirements. The recipient must respect applicable legal restrictions. We do not publish your private reading merely because you use the service. Sharing a copy yourself can expose information about both participants, so consider their privacy first.
7. Browser storage and analytics choices
We use a reading-specific browser cookie to help authorize access to your private reading. In the current session design, that cookie expires 30 days after it is issued. Cookie expiry is not the same as deletion of a reading from our databases, and it does not define or override the access period of a purchase.
Cookies, session storage, local storage, and similar technologies are explained in the Cookie and Browser Storage Notice. You can manage optional analytics through Privacy Choices. Necessary access, security, payment, and choice-recording functions cannot be switched off through an analytics preference, although browser settings may block them and affect functionality. Refusing optional analytics does not prevent you from purchasing or receiving a reading.
8. How long we keep information
We retain identifiable information only for a justified purpose and for as long as that purpose and applicable requirements call for it. We determine periods by the type of information, the promised access period, the need to complete delivery or resolve an issue, applicable financial recordkeeping requirements, the potential for a relevant claim, and the sensitivity of the information.
The 30-day online access period for a new purchase is a supply commitment, not a rule that all information is deleted after 30 days. Access expiry, a request acknowledgement and receipt of a deletion request do not establish that deletion has occurred. Reading content, generation records, financial evidence, support records, logs and backups require their own applicable retention and deletion treatment.
We do not keep unpaid or abandoned readings solely because a paid product might be offered later. Paid reading content and included follow-ups are retained to provide the promised access and to address related support or remedy obligations. Generation records are retained only as needed for a defined operational, safety, or dispute purpose; they are not an unrestricted permanent training archive.
For new records covered by this notice, RNWC's internal targets are seven days for unpaid drafts and previews; the purchased 30-day access period plus up to seven further days for relationship content needed for recovery or fault handling; 30 days for ordinary minimized technical events; and 90 days after actual closure for closed support correspondence. These periods do not shorten an earlier purchase, an approved access remedy, or a legally required preservation period. Unresolved payments, undelivered purchases, disputes and legally justified holds require a separate review before clearing content. Clearing records is an operator-reviewed process; reaching a time limit or expiring a cookie does not prove deletion occurred.
Minimal transaction, refund, and agreement records may need to be retained after the associated reading content is erased. Where possible, we separate those records from birth details, questions, and reports. A legal hold can require limited records to be kept longer, but it does not justify keeping unrelated information indefinitely.
Deleting information from active systems may not immediately remove it from a restricted backup. Backup information is removed through the applicable backup cycle and protected from ordinary use; when a backup is restored, applicable deletion restrictions must be reapplied. Contact real@realnova.world for the retention information relevant to your request, including any reason a limited record must be retained.
9. International processing and regional information
Our service providers may process information in countries other than the country where you live. The actual providers, processing locations, and any applicable international-transfer arrangements are described in /privacy/providers. You may request further information at real@realnova.world.
Where the EEA or UK data-protection rules apply, our regional privacy supplement at /privacy/eea-uk explains the relevant legal bases, information about data received from another person, any required regional contact, and the actual safeguards for restricted international transfers. We do not represent that a transfer is covered by a certification or contract merely because a provider offers that option.
10. Your rights and choices
Depending on the law that applies to you, you may have rights to know about or access personal information, obtain a copy, correct inaccuracies, request deletion, restrict processing, obtain portable data, or object to processing. Where we rely on consent, you may withdraw it for future processing without affecting the lawfulness of earlier processing. A privacy notice acknowledgement is not a substitute for a separate consent where one is needed.
Right to object. Where processing is based on legitimate interests, you may object for reasons relating to your circumstances, subject to the applicable legal rules. You may object to direct marketing at any time. Use real@realnova.world or Privacy Choices to communicate your objection.
Certain US state laws may also provide rights to opt out of sale, targeted advertising, or specified profiling, to limit certain uses of sensitive personal information, to use an authorized agent, and to appeal a request decision. Those rights depend on the applicable law and whether it covers the activity. We do not sell information or share it for cross-context behavioral advertising. A recognized Global Privacy Control signal is treated as a request to opt out of any covered sale or sharing, and our Privacy Choices explain its interaction with optional analytics. A legacy “Do Not Track” header is a different signal; it does not establish a universal technical instruction across all providers.
We will not discriminate against you for exercising a privacy right. We may need to explain when deleting or restricting information makes it impossible to continue a feature that actually needs that information. You can also complain to the relevant data-protection or consumer-protection authority. You do not have to resolve a complaint with us before contacting an authority.
11. Making a request—including requests by the other person
Email real@realnova.world or use the working request options on Privacy Choices. Explain the action you are requesting and provide a reference you have, without sending passwords, access cookies, or unnecessary sensitive details. A reading reference helps locate a record but is not proof that you are entitled to see it.
We will use proportionate verification, provide information about any necessary further step, and respond within the period required by applicable law. Where an extension is legally available, we will explain it within the required period. If we cannot grant all or part of a request, we will explain the applicable reason and any available appeal or complaint route.
You may make a request even if someone else supplied your information and you do not have a Bondora account. We will protect the rights and information of both people: for example, a request to access one person’s information does not automatically authorize disclosure of another person’s private question or correspondence. Verification must not rely only on a publicly known name or birth date.
For current report updates, OpenAI receives this topic’s original situation, actual clarifications, prior user additions, latest question and saved report to prepare a revised standalone full report. Later explicit corrections take precedence. Reports are not combined across topics. New full versions, a short update summary, the request number and fulfillment record are retained so a lost response can be recovered without generating or consuming an update twice.
A private customer record links your own topics, purchase snapshots and membership grants. A signed HttpOnly customer cookie lasts up to 30 days per issuance; it is an access credential, not a purchased service term. Identity is established by authorized private access and verified recovery, never inferred by matching a PayPal email, IP address or device fingerprint. For membership reports, relationship content is retained through the later of active membership and 30 days from the report’s latest complete delivery funded by membership, plus up to seven days for recovery or fault handling. The same separate review, dispute holds and deletion rights apply. Financial records and entitlement dates are retained separately from private report content.
12. Security, children, and updates
We use access controls and other measures designed to protect information. No internet service or storage method is completely secure, and we do not promise absolute confidentiality. Protect the device and browser through which you access a reading and tell us about suspected unauthorized access.
Bondora is intended for adults aged 18 or older and does not permit readings about minors. Contact real@realnova.world if you believe a child’s information has been submitted. We will assess the situation, stop inappropriate processing, and take the steps required by applicable law. An age statement does not excuse ignoring information that indicates a child is involved.
We may update this notice to reflect changes in the service or legal requirements. The effective date and version identify the current notice. We will provide additional notice and obtain a choice where required before materially changing how we use information. Questions and complaints can be sent to real@realnova.world or 5538 E Galbraith Rd, Apt 38, Cincinnati, OH 45236, United States.
Optional report sign-in
Saving a report is optional and is not required before payment. A passkey links the reports you are already authorized to access to a stable private customer record. We store its credential identifier, public key, signature counter, transport and backup status, creation and last-use times, and revocation state. Bondora does not receive your fingerprint, face scan, device PIN or passkey private key. Your device or credential provider manages private keys and any synchronization under its own settings. We do not promise that a passkey is available on every device.
If you choose email sign-in, we store the verified address and its verification and revocation status, and send a short-lived code through the transactional mail provider listed in our provider register. The message contains the code and sign-in instructions, not your report or relationship story. Codes expire after 15 minutes and allow at most five verification attempts. Stored code proofs are hashed. Expired challenges and rate-limit records are eligible for cleanup after one further day; cleanup runs when another challenge is created, so that interval is not a guarantee of completed deletion. We use keyed hashes of network identifiers for short-term abuse limits, not device fingerprints.
We retain sign-in records while needed to provide and secure your saved access and assess applicable deletion requests and justified holds separately. Removing a sign-in method revokes it; it does not erase purchase evidence, delete a passkey from your device provider, cancel an entitlement or prove that all stored records were deleted. Sign out removes private access from this browser. On a shared device, also avoid saving a passkey in a shared device account. A payment email, typed address or report URL alone cannot connect reports. Only verified ownership evidence can do so; prior recovery history remains available for exceptional support review. These controls do not enable advertising or invitations, and do not extend a purchased access period.
Optional background from your own report (confirmed-background-20260928-v1)
Background reuse is off unless you choose it. You can select one original user statement from a current, available report owned by your signed-in account, check its relationship and date, edit it or cancel. AI explanations, examples, actions and suggestions are not imported as facts. Copied reports cannot be copied again in this first version. Continuing manually works without reuse.
Ordinary follow-ups do not automatically read or combine other topics. This optional choice is different: you separately select, edit and submit your own original words as a new input. It never imports an old AI report.
Only the statement you confirm becomes a saved input to the new report. We retain its source report and version, statement labels, confirmation date, account identifier, notice version and whether you edited it, so we can track the copy and process content requests. The candidate and edits stay in page memory before submission; leaving or changing accounts clears them. No extra model request is made to list or select background. Confirmed input uses the same report-generation purpose and providers as your new question.
Before submission, a changed source, identity, version or permission requires clearing or confirming background again. After submission, the confirmed snapshot is an independent new input: the source's later expiry or deletion alone does not erase it. Canceling the picker before submission creates no copy.
Signed-in report owners can open My reports → Manage report content. Review either one entire report or the exact connected group formed by confirmed background copies. The displayed scope includes all saved versions and later content in each listed report, not just the copied statement. A changed group requires another scope confirmation. A single-report request leaves confirmed input in other reports; a connected-group request includes the listed source and copied reports.
A committed request immediately restricts server access and further processing for its listed reports. PENDING_RESTRICTED means review or cleanup is still pending; it is not deletion. ONLINE_ERASED is shown only after every listed report has an actual online-content cleanup receipt. Unsettled provider work, payments, refunds, disputes, controlled evidence and other retained obligations can require review. The request does not reset or cancel other reports, membership, financial records or support and refund rights. Keep the request reference to check progress or ask support for help.
Already delivered browser content, downloads and printed copies cannot be recalled. Online erasure does not claim deletion from providers or all backups. Minimal copy links, consent scope, identifiers, dates and cleanup progress remain to prevent deleted or restricted content from returning during a restore; financial and rights evidence follows its existing retention rules. Restores must replay externally preserved completed cleanup receipts and pending restrictions, verify completeness against the original primary, and remain unavailable when that proof is missing.