Legal · Privacy
Privacy Policy
Publication review in progress
What information Innuro currently processes, how it is used, and which controls are available today.
Policy summary
The short version
Four current facts. The complete policy and its boundaries remain below.
Processed during a session
Voice audio is processed while an active voice session is running.
Records that may be stored
Transcript text and other supported session records.
Personal information is not sold
Innuro does not sell personal information.
Available requests
Request export or deletion for supported data classes and privacy flows.
Clear boundaries for sensitive information
This policy describes what Innuro currently processes and the controls currently available. It does not claim that every system is risk-free or that every data class follows the same export, deletion, or retention path.
Current implementation
Three current privacy boundaries.
These limits stay in view before the complete policy continues below.
What you share
Content you submit remains yours, subject to the Terms. Innuro processes it to provide supported features.
Current boundary
Transport security + storage controls
- Selected reflections and session text can be used to produce responses and possible connections for you to review.
- Voice audio is processed during active sessions so Innuro can generate transcript text and emotion signals.
- Innuro does not sell personal information. Service providers may process information needed to operate the service.
Supported deletion controls
You can request session or account deletion through the flows available today. Coverage varies by data class.
Current boundary
Coverage varies by data class
- Supported deletion flows remove the currently implemented account and session data classes.
- Some operational, data-handling, and legal-acknowledgment records have separate retention paths.
- The current implementation does not guarantee automatic session deletion after a fixed period.
Policy versions and consent
Policy versions are tracked, and account flows can store versioned legal acknowledgments.
Current boundary
Versioned consent records
- Consent records can include the version, choice, source, and date recorded.
- Account flows may require acceptance of a current legal acknowledgment.
- Review the current text on this page; this policy does not promise advance notice through a particular channel.
What information we collect
Things you give us directly
- Your contact and account information
- Email submitted for launch updates; account identifiers and authentication data if you create an account
- Your sessions
- Text you submit and transcript text created from voice input
- Your voice input
- Voice audio is processed during active sessions to generate transcript text and emotion signals.
Things we collect automatically
- Product usage
- When you use the app, features used, session length
- Device basics
- Device type, operating system, app version
- Product analytics
- Privacy-screened usage events; some events may use hashed identifiers. This is not a claim that all analytics are anonymous.
How we use your information
- To make Innuro work for you
- Produce session responses, compare selected reflections over time, and offer possible connections for you to review
- To show crisis resources during a session
- Innuro is not an emergency service. It does not monitor you or guarantee it will recognize a crisis. If you mention a crisis during an active session, Innuro may show support resources. It does not contact a service or another person for you. If you might be in immediate danger, contact local emergency services or a crisis line now.
- To make Innuro better
- Use privacy-screened product analytics. Some events may use hashed identifiers, and optional marketing-site analytics are controlled by your consent choice. On this website, turning on site analytics also turns on session replay, which records your visit with form inputs masked. Turning on campaign measurement stores the campaign source, referrer, and landing page that brought you here for 30 days, refreshed each visit.
- To stay in touch
- Send launch and availability updates you requested, plus important account and privacy notices.
Current security boundaries
- Transport and storage controls
- Transport security and hosted storage controls are used; field-level encryption for transcripts and derived records is not yet complete
- Operational access
- Access controls are used for operational systems. This is not a claim that staff cannot access data.
- No blanket security guarantee
- Security controls reduce risk but do not make any system risk-free. This policy does not claim an independent certification.
- Redacted support bundles
- Support bundles currently available default to minimal or redacted files and are designed to exclude transcript and message content; this does not describe every operational record
Controls currently available
Depending on the data class and available flow, you can:
- See supported account and session metadata
- Request export for implemented data classes
- Correct information through supported flows
- Request deletion for the implemented scope
- Change optional consent choices
The legal details
- Data retention
- Completed session records are configured for deletion after 90 days by default. This timing depends on the retention process being enabled and running. A supported deletion request may remove covered data sooner, while operational, service-provider, analytics, and legal-acknowledgment records can follow separate retention paths.
- Age requirement
- Account onboarding requires an 18+ affirmation. Innuro does not independently verify age in the current flow.
- Policy changes
- This policy remains under publication review. A verified effective date will be shown when that review is complete. Account flows may separately require acceptance of a current legal acknowledgment.
- After you delete
- A successful account-deletion flow removes the data classes currently covered by that flow. Some operational or third-party service records can follow separate retention rules. When a legal acknowledgment is recorded, Innuro retains one separate consent audit record containing a one-way hashed reference derived from the former user ID, the accepted Terms and acknowledgment versions and text, and the acceptance and deletion dates. It contains no name, email, or session text. Once it is older than 2,190 days (about six years), it is scheduled for deletion.
Privacy control
Ask about your data.
Use the privacy address for export, correction, deletion, and questions about how information is handled.