Legal
Privacy Policy
Last updated: May 2026
What We Collect
We collect your email address when you create an account. We store the content you enter during guided check-ins, including your private reflections, topic descriptions, and relationship names. We also store consent records and subscription status.
We do not collect browsing history, location data, device fingerprints, or behavioral tracking data from third parties.
How Your Data Is Used
Your private entries are used to generate shared pattern maps and personal debriefs. When OpenAI is used for synthesis, your entry text is sent to OpenAI's API for processing. OpenAI does not train on API data. Your entries are never sold, shared with third parties, or used for advertising.
What Other Users See
Other participants in your shared intake session can see the synthesized pattern map — not your raw private entries. Raw text stays private unless you explicitly choose to reveal it. Consent is required before any shared summary is generated.
Data Storage and Security
Your data is stored in Supabase, a SOC 2 compliant database provider. Your password is hashed and never stored in plain text. We use Row Level Security to ensure you can only access your own data.
Your Rights
You can request deletion of your account and a copy of your stored data by contacting support@univenturestudio.com. Self-serve export and deletion settings are not part of the current member workflow.
Cookies
We use essential session cookies for authentication. No tracking cookies, advertising cookies, or third-party analytics cookies are used.
Contact
For privacy questions, contact us at support@univenturestudio.com.
Plain-language version
Need the simpler trust summary first?
Start with the plain-language privacy and consent page, then use the trust guides if you want the exposure, detail, pause, and fit questions answered directly before reading policy language.
Trust questions first
Privacy policy readers usually need the plain-language trust answers next.
These guides keep the next click focused on privacy, trustworthiness, and what a consent-first relationship product should protect before anyone shares vulnerable material.
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.
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.
Guide
Consent-first in a relationship app means private by default, shared by choice.
Use this page when you want a plain-language answer to what a shared relationship intake should protect before anyone is asked to be vulnerable.