Privacy Policy

Last updated: September 2026

Yusiva helps users reflect on relationship patterns and decisions. We aim to collect only what is needed to provide the service.

Information you may provide

Adult-only service

Yusiva is currently limited to adult relationship situations where both people are 18 or older. We ask for age-range confirmation to enforce this boundary. If either person is identified as under 18, the relationship analysis is stopped before it is sent to the analysis service.

How information is used

We use your inputs to generate relationship clarity results, saved check-ins, trend views, and decision-support guidance.

While you move through a check-in, an in-progress draft may be kept in session storage on your device so a refresh does not immediately erase your progress. The draft is limited to the current browser tab session and is removed when you return to the start, log out, or delete your account. Earlier persistent draft keys are removed when the current app starts.

Relationship context and questionnaire answers are sent to the Yusiva analysis service when you request a result. They are saved to your account history only if you choose to log in or create an account and save the check-in.

The optional Yusiva Hidden Relationship Clarity check accepts structured categories rather than names, messages, screenshots, account details, or third-party identity. Its analysis endpoint does not save the submitted answers or use them for model training. You may use it anonymously without saving. If you explicitly choose “Save on this device,” the browser stores structured decision and follow-up signals, controlled situation categories, and summary levels in local storage so you can return later. This local device storage is not encrypted by Yusiva, and another person with access to the same browser profile on a shared device may be able to see it. You can avoid saving or remove the device record from the follow-up screen. Connecting an account does not save a check-in. If you actively save an initial or follow-up checkpoint to your Yusiva account, it includes controlled categories for duration, visibility, promises, observed actions, deadline and delay status, contact control, desired outcome, and whether a safety override was triggered. It does not include the specific safety concern, free text, names, messages, screenshots, account credentials, or third-party identity. These structured checkpoints use the same account history, export, and deletion controls described below.

Product feedback submitted while you are logged in is linked to your account so it can be included in account export or deletion. If you are logged out, a contact email is used only for follow-up you consent to and does not by itself establish account ownership.

A random product-feedback session identifier may be kept in session storage for the current browser tab so related beta feedback can be grouped. It is not kept as a persistent cross-session identifier, and earlier persistent feedback-session keys are removed by the current app.

Anonymous product lifecycle and acquisition measurement

Yusiva may count a small set of product lifecycle actions so we can understand whether the service is working, which public entry points people use, and where people stop before reaching a report. These measurements are stored only as daily aggregate counts. Lifecycle categories may include viewing an acquisition page, choosing a clarity path, starting or completing an assessment, being presented with a report, saving a checkpoint, reopening a check-in, submitting feedback, or starting checkout.

For acquisition measurement, the browser may classify a visit into a limited set of categories such as acquisition source, medium, campaign, content, and landing page. The normalized classification may be kept in session storage only for the current browser tab so the original entry source can remain consistent while you move into Yusiva. This measurement does not create a persistent cross-session identifier, advertising identifier, or device fingerprint.

Yusiva product measurement does not store your name, email, account ID, session ID, device ID, IP address, relationship answers, relationship details, safety responses, feedback text, report content, or exact event time. It also does not store raw search terms, raw UTM parameters, the raw referring URL, the full page URL, or the URL query string. The browser may read URL or referrer information only to derive the normalized acquisition categories; those raw values are not included in the Yusiva product measurement event or daily aggregate table.

Aggregate product measurement records are retained for up to 90 days. This first-party measurement does not use cookies, cross-site tracking, third-party behavioural analytics, or persistent tracking identifiers. Website performance measurement provided separately by Cloudflare is described below.

Website performance measurement

Yusiva uses Cloudflare Real User Monitoring (RUM) through Cloudflare Web Analytics to understand whether public pages load reliably and quickly. The performance beacon processes the landing page URL, the referring page URL, and browser performance data such as navigation, resource, paint, and page-load timing measurements for the page being viewed.

Cloudflare states that the RUM beacon does not read or write cookies, localStorage, sessionStorage, or IndexedDB. Cloudflare receives the source IP address as part of normal request handling, then discards it at the nearest Cloudflare data centre without storing it in RUM core databases or logs. Cloudflare operates a global network, so RUM performance data may be processed in a country or region different from where it originated.

Data rights

Where available in your account area, you can request deletion of your history or account. Yusiva does not sell personal relationship data to advertisers.

Safety note

Yusiva is not emergency, legal, medical, or professional counselling support. If you feel unsafe, seek trusted local help or emergency services.

Back to Yusiva