Information We Process

• A guest or connected account identifier, authentication session metadata, app language and settings, and security information used to separate and protect each person’s data. You may optionally connect Apple, Google, or email. Firebase App Check uses Apple App Attest on supported Apple devices and Play Integrity on supported Android devices to issue short-lived integrity tokens for protected requests. Tarivyn also creates a random installation identifier and derives salted rate-limit keys from installation and request-network signals for abuse prevention.
• Private-session data: invitation code, selected journey and curated question, answer text, selected symbol, readiness state, agreed or proposed action, completion status, and timestamps. Sessions normally expire after 24 hours.
• Relationship Space data you choose to create: a Decision Room topic, options, sealed rankings and final choices; a Time Capsule title, opening date, sealed text and readiness; time zone and availability windows for finding overlap; and approval records for memories, actions, and opened capsules. The relationship map and year recap are derived from those approved records rather than from a relationship score. Tarivyn does not request GPS location for these tools.
• Shared and private memories you choose to complete. A shared memory contains each participant’s answer and symbol plus the action both people confirmed.
• Safety information you choose to submit, including a report reason and—only with your explicit confirmation—a snapshot of visible session content. Blocks are stored so blocked people cannot pair with each other again.
• If you allow notifications, Tarivyn registers an Expo push token linked to your app user and device platform. Notification delivery uses generic alert text and a private in-app room route; the lock-screen title and body do not include a question, answer, expression card, action, capsule, ranking, or room code.
• Purchase and subscription information from Apple, Google, or RevenueCat, including product identifier, entitlement status, purchase date, renewal state, app/SDK interaction metadata, and app user identifier. We do not receive full payment-card details.
• If you choose rewarded access, Google Mobile Ads / AdMob and Google UMP process consent state, advertising and device identifiers, ad interaction and limited diagnostics. Tarivyn requests a non-personalized rewarded ad and sends one random, expiring challenge identifier for server-side reward verification. It sends no invitation code, question, answer, symbol, action, name, or email in ad request metadata.

When you visit tarivyn.com, Cloudflare processes request information needed to deliver and protect the site, such as IP address, User-Agent, requested path, and security or diagnostic metadata. A Together link contains an invitation code. Tarivyn does not add advertising trackers or advertising cookies to the public site.

Privacy and Safety Controls

Before mutual reveal, the other participant’s answer and symbol are not returned to your app. Sealed Decision Room rankings and Time Capsule text remain private until their separate mutual conditions are met. These bounded text exchanges let two participants communicate directly, but there is no unrestricted chat, public feed, stranger discovery, photo, voice, or file sharing. Session mutations are performed through a protected server function. Answer text is checked for length, contact details, links, and narrowly defined severe unsafe content. You may skip, leave, report, or block. Reports include session content only when you explicitly choose that option. Real rooms may request notification permission after a successful join; the reviewer demo does not request it.

How We Use Information

• Provide private sessions, mutual reveal, shared decisions, time capsules, common availability, approved recaps, neutral room-update notifications, solo reflections, memories, and optional rewarded access.
• Authenticate users, restore purchases, prevent misuse, verify rewarded completion, and enforce blocks.
• Operate, secure, troubleshoot, and improve service reliability. Firebase product analytics and automatic screen reporting are disabled. Tarivyn requests non-personalized rewarded ads and does not build its own cross-app tracking profile.

Service Providers and Sharing

We use Supabase for guest and optional-account authentication, database storage, Realtime signals, and Edge Functions; Apple and Google for optional identity connection; Firebase App Check with Apple App Attest or Play Integrity for supported-device request integrity and Firebase Remote Config for operational settings; Expo Push Service and Apple Push Notification service or Firebase Cloud Messaging for notifications; Google Mobile Ads / AdMob and Google UMP for optional rewarded ads, consent, and server-side reward verification; RevenueCat for subscription entitlement management; Apple App Store or Google Play for purchases; and Cloudflare for DNS, TLS, hosting, and security for tarivyn.com. These providers process information under their published terms and applicable safeguards. We do not sell personal information or use it for cross-app tracking. We may disclose information when legally required, to protect users or the service, or as part of a lawful business transfer.

Retention and Deletion

Incomplete sessions expire after 24 hours. The release target schedules expired or abandoned transient session content and command-response snapshots for deletion after a seven-day operational window. Completed memories, Decision Rooms, Time Capsules, availability preferences, and recap approvals remain while the related relationship and account remain active. Hiding a memory removes it from your view but is not the same as deleting the underlying shared record. A push token remains enabled until it is replaced, rejected by the provider, revoked on logout, or removed with the account. Safety reports and limited pseudonymous security, purchase, fraud-prevention, and legal records may be retained as needed to protect users or meet obligations.

In Settings, Delete Account and Data permanently removes the current account, its private answers and user-owned saved content, the linked RevenueCat customer profile and purchase history, and local app data. Relationship records that are keyed to the deleted account are removed by the server’s deletion constraints; shared records may continue only with the other participant’s remaining content and rights. Apple and Google provider-token revocation is attempted when the required token is available. A failed RevenueCat erasure stops account deletion so it can be retried. Removing an account does not cancel an App Store or Google Play subscription; subscriptions must be managed separately in the store.

Your Choices

You can decline notifications, open notification settings from Tarivyn Settings, use a guest profile, optionally connect an account, avoid completing or approving a shared record, hide a memory from your view, leave a session, report with or without content, block another participant, restore or manage purchases, and delete your account and data from Settings.

Children and International Processing

Tarivyn is not intended for children under 13. Information may be processed in countries other than your own, subject to reasonable contractual and security safeguards.

Reflection and Communication Disclaimer

Tarivyn supports reflection and communication. It does not diagnose a relationship, guarantee outcomes, or replace medical, legal, financial, psychological, or other professional advice.

Contact

Email: semih@ilysia.app
Support: tarivyn.com/support