Privacy

    Privacy Policy

    Your history, your settings. You decide how much context Vyorah may use, what you add to your account history, and what you keep or remove.

    Approach

    Clear language, scoped storage, evolving portability, and user-controlled context for deeper guidance.

    Connected AI

    Connected AI History Import

    You can optionally connect a supported AI service to prepare journal, history, and life-event entries you intentionally choose to submit. Vyorah receives only those prepared entries; it does not use the connector to retrieve your whole AI chat history.

    The connector cannot read your existing Vyorah history and cannot directly create canonical Events. It stages a temporary plaintext batch for you to review in Vyorah before anything is imported. If you choose Encrypted Notes, encryption happens in your browser during final import; your encryption phrase never goes through the connector, staging, or our server.

    Staging is retained only while usable: receiving batches for up to 24 hours after the latest append, ready or partially ready batches for up to 7 days, finalized batches for up to 1 hour, and cancelled batches immediately. An hourly cleanup deletes expired staging batches and records. The recipients are Vyorah and the AI service you choose under that service's own terms; you can choose whether to authorize or revoke the connection.

    Do not use connected import for medical records or other PHI, payment-card information, government identifiers, passwords, API keys, OTP codes, or other authentication secrets. Sensitive personal life events that are not these prohibited records remain your choice to preserve.

    Principle

    Decide How Much Context Vyorah Uses

    Vyorah works from the history you choose to give it. Basic guidance can use structured context like dates, phase, valence, categories, significance, recurrence, and card history.

    Deeper guidance may use saved notes according to your AI Context setting. Encrypted notes are stored as ciphertext separately and are not sent to AI automatically.

    Storage

    What We Store

    We store the account data required to operate the product, along with the history you intentionally create: events, forecasts, optional reflections, and personalization settings tied to your experience.

    Vyorah does not store payment card numbers. Payment and transaction records may be handled or retained separately by Google Play and/or Stripe under their own legal, platform, and accounting requirements.

    Retention

    Details and Retention

    Saved event details may be available for guidance according to your AI memory setting while they remain in your history.

    Private Note Storage controls how event notes are stored. Encrypted Notes require an unlock phrase on this device to view or save note text, and decrypted note text is only sent for a forecast after you unlock note history for that reading.

    Structured history such as date, phase, valence, significance, category, recurrence, and forecast/card records can continue to support continuity even when you choose not to share deeper text context.

    When account deletion completes, Vyorah deletes account-linked data, except for limited records that may need to be retained for legal, security, fraud-prevention, or financial-recordkeeping obligations.

    Generated History

    Forecasts and Insights

    Generated forecasts, insights, and narratives may remain as part of your history until you remove history or delete your account.

    These generated outputs can reflect the context available at the time they were created. Forecasts run with unlocked encrypted notes are not saved to Forecast History.

    Conversation

    What Vyorah Remembers From Chat

    When you are signed in, ordinary conversation with Vyorah can keep short notes about useful things you tell it, so a later conversation still knows what is going on. That might be a preference, a plan you are weighing, something you are worried about, a stable detail about your life, or a situation that has not resolved yet.

    These notes come from what you actually say. Vyorah's own guesses, suggestions, and interpretations are not saved as things you told it.

    Conversation memory is separate from your saved Events and from the material your Forecasts are built on. Mentioning something in chat does not turn it into an Event on your timeline and does not feed it into a forecast — saving an Event stays a separate step you confirm yourself.

    It is stored as ordinary account data, the same way your saved events are. It is not stored as encrypted-note ciphertext, so please do not treat it as encrypted storage.

    You can ask Vyorah in conversation to forget something it has remembered. Remove History clears conversation memory along with the rest of your history, Delete Account removes it with your account, and it is included when you export an archive of your data.

    Separately, Vyorah keeps one short note to itself about where your most recent conversation had got to, so reopening Chat does not mean starting over. There is only ever one of these notes: each conversation replaces the last, and it is cleared when there is nothing to carry. It is not a transcript, it is not part of an exported archive because it is replaced too often to be a meaningful copy, and Remove History and Delete Account both clear it.

    Portability

    How Data Handling Works

    The backend is designed so history can power your experience without trapping you in the system. Your account uses stored history to render forecasts and continuity, while our data-handling approach continues to evolve.

    User-facing controls around personal history may change over time as the product's privacy and portability approach matures.

    Any future portability tools should preserve user control without exposing more personal detail than intended.

    Protection

    Scoped Access

    Access to personal records is scoped per user in the backend. Administrative and automation access is kept separate, and we avoid broad exposure of personal history as part of the product model.

    We also aim to minimize unnecessary third-party visibility. Payment processing may be provided by Google Play and/or Stripe, which may handle or retain payment and transaction records under their own legal, platform, and accounting requirements. Vyorah does not sell your personal history or use it for third-party advertising.

    Control

    Your Control

    The main history tools live in the Home page's Manage History section, where you can reset a time range or remove stored history while keeping your account.

    Remove History clears events, conversation memory, and derived forecast/cache history, deleting saved history and data while keeping your Vyorah account.

    To permanently delete your Vyorah account, go to Settings → Danger Zone → Delete Account → type DELETE → Confirm Delete. Delete Account removes your Vyorah authentication account and account-linked data, including profile and account data, saved events and history, forecasts and derived forecast/history data, conversation and life memory, imported-history staging data, and personalization and settings data associated with the account.

    Payment and transaction records may be handled or retained separately by Google Play and/or Stripe under their own legal, platform, and accounting requirements. Vyorah does not store payment card numbers.

    The core principle is simple: Vyorah should work from the context you choose to share, under the settings you choose to keep.

    Privacy controls live in Privacy Settings. This Privacy Policy page explains the data-handling side; Privacy Settings controls the app behavior.