Private mode
Start alone without analyzing private data from the other person.
Guided relationship check-in
Trust is not a settingspage. It is the product.
Trust is not a settings page. It is the product.
Private entries are private by default. Shared summaries require explicit consent rules. If you need deletion, export, or privacy help today, use the support path while self-serve controls stay narrower.
No AI judge
Maps the loop without deciding who won.
Consent-aware
Shared mode requires explicit permission.
Safety first
Risk is not treated as ordinary conflict.
Privacy and consent
Recharge View
A calmer map of the same moment.
Fact
What happened, separated from story.
Meaning
What the moment seemed to say.
Fear
What each person may be protecting.
Pattern
What repeats when repair is missed.
Repair
What can be named next without blame.
Current trust boundary
The privacy promise should stay narrower than the long-term controls list.
The current live member workflow stays centered on private entries, consent checkpoints, and shared summaries that do not expose raw wording. If you need deletion, export, or billing help today, use support while broader self-serve controls stay outside the current launch claim.
Private entries stay private by default.
Shared output should not appear without real consent.
Support is the current path for deletion, export, and billing-help requests.
Shared consent
Create shared summaries only after both people explicitly agree.
Export and deletion
Keep memory, reports, and shared artifacts user-controlled.
Plain-language promise
The product should earn trust before it asks for vulnerability.
Shared mode is designed around consent states and careful separation between raw entries and shared maps. When someone needs deletion, export, or billing help today, the honest path is support rather than a wider self-serve settings promise.
Contact support@univenturestudio.com if you need help with privacy, deletion, export, or billing requests.
If the summary still feels too exposing
That matters even when raw text stays private. A trust-first product should make preview, slowdown, and stop decisions feel real instead of treating discomfort like friction.
Pause is part of consent
A real consent model does not assume every pause is a delayed yes. It keeps timing, control, and free choice visible all the way through the shared flow.
Trust questions first
Use the plain-language trust guides before you read deeper policy detail.
These pages answer the strongest early trust questions directly: what stays private, what makes the product feel trustworthy before vulnerability, and what consent-first should actually protect in a relationship app.
Guide
Privacy questions are not a side concern in a relationship app.
Use this page when someone asks the hard trust questions first: what is stored, who sees what, and whether the product earns enough safety to be used at all.
Read guide
Guide
One more reassurance can protect trust or quietly rescue momentum.
Use this page when the flow sounds softer after hesitation, but you still need to know whether the extra reassurance is protecting trust or trying to recover movement toward the next step.
Read guide
Guide
A relationship tool feels trustworthy when the trust rules are visible before vulnerability.
Use this page when you want a plain-language answer to what makes a relationship tool feel trustworthy instead of generic privacy buzzwords.
Read guide
Ready when the pattern is repeating