Privacy policy

What this policy covers

This policy covers murmur-live.com, its account pages and communications sent to Murmur support. The operator identified below is responsible for the personal information handled for those purposes. Eunoia and Murmur are brands; this notice does not represent them as separately incorporated companies.

The desktop app processes call audio, captions, translations and dictionary searches locally. Signing into the website does not upload call content, personal glossaries, scripts or notes. Website demonstrations use fictional sample content; their scratchpad text, searches and timer state stay in page memory and clear on reload.

Information we handle

Account registration and login: email address, account identifier, language preference, confirmation status, creation/sign-in timestamps and authentication/session records. With email/password registration, your password is sent to Supabase Auth; the website does not save a readable copy in browser storage.

Google sign-in: Google supplies an account identifier, email address and verification status, and may supply your name and profile picture through the basic profile permission. Supabase stores the corresponding identity and profile metadata. The account dashboard currently displays your email and account status, not the full Google profile.

Support: messages, your contact address and any attachments you choose to send. Hosting, authentication and email providers also process technical request/delivery/security information, which may include IP addresses, browser information, timestamps and request paths. We do not request call recordings, patient details or confidential case documents through support.

Why we use it

We use account information to create and authenticate your account, show its details, send confirmation and password-reset messages, answer requests and protect the service against abuse. We rely on providing the service you request, applicable legal obligations and proportionate security interests as appropriate. Optional uses that require consent need a separate choice.

An email address is required for the current account service. Without the necessary identity information, we cannot complete account access. Incorrect contact details can prevent confirmation, recovery and replies. Browsing the product page does not require creating an account.

We do not sell Google user data, use it for advertising, or use it to train AI models. The website does not make decisions with legal or similarly significant effects solely through automated profiling. Signing up does not grant a paid subscription, software license or computer activation.

Google sign-in

The Google option requests only OpenID identity, email and basic profile information. It does not request access to Gmail messages, Drive documents, contacts or calendars. Google authenticates you on its own pages; Murmur does not receive your Google password.

You can remove Murmur's Google access from your Google Account connections. Removing that connection does not itself delete the existing Murmur account record. For account deletion, use the contact below. Our use and transfer of Google-provided information is limited to the account purposes described here and the applicable Google API Services User Data Policy, including its Limited Use requirements where applicable.

• Manage Google connections
• Google API Services User Data Policy

Providers and international processing

We use Cloudflare to host and protect the website and store encrypted account backups in its R2 service, Supabase for account authentication and associated records, Resend for account-email delivery and support inbox handling, and Google when you choose Google sign-in. They receive the information needed for their role. We may also disclose information when legally required or necessary to address a security incident or legal claim.

GitHub Actions runs the daily account backup on a temporary hosted runner. Account records are processed there before encryption and upload to private R2 storage. The jobs are configured to log operational results and encrypted archive metadata, without uploading account records as workflow artifacts. The private recovery key is kept separately and is not given to GitHub. This backup process does not receive desktop call content, personal glossaries, scripts or notes.

These services can process information outside Ecuador. The current Supabase account project is in North Virginia, United States; Resend states that it stores customer data in the United States. Hosting, backup runners and provider subprocessors can involve other locations. The links below describe each provider's privacy practices. Contact us to ask about the providers involved in handling your account information.

• Cloudflare privacy information
• Supabase privacy information
• Resend privacy information
• Google privacy information
• GitHub privacy information

Browser storage and cookies

The account website uses sessionStorage to maintain your login within the browser tab. Google login also temporarily stores a PKCE verifier and a pending sign-in attempt, valid in the website for ten minutes. Login returns remove authorization parameters from the visible URL and consume the pending attempt once.

Passwords and email confirmation/reset token hashes are not saved by the website in browser storage. Signing out clears the tab's stored account session; merely closing the tab is not a guarantee that the server session is revoked, and browser session restoration may restore tab storage. Use Log out on shared computers.

Murmur does not use advertising cookies or tracking pixels for this account flow. Google and other providers have their own privacy/storage practices when you visit their services. Hosting providers still handle ordinary requests and security metadata.

Retention and deletion

Unused, unconfirmed email registrations become eligible for automatic cleanup after seven days. Confirmed accounts, accounts with sign-in history and accounts with owned files or linked records are excluded from this cleanup. Daily processing is bounded and may take longer while the service is paused or a safeguard requires review.

Account records are kept while needed to operate your account and handle related requests. We review ordinary support conversations for removal 30 days after resolution. Moving them to Resend Trash schedules deletion 30 days after that move; restoring a conversation cancels that deadline. New activity requires a fresh resolution review. Verified deletion requests are reviewed separately without waiting for routine aging, unless a legal duty or a necessary, proportionate security or legal purpose requires limited retention.

We make encrypted account backups daily and store them in private R2 storage under a seven-day expiry rule. Provider lifecycle processing can delay removal beyond the exact expiry time. An isolated recovery test has verified the stored backup. Older encrypted copies can still contain a deleted account until they expire; any recovery must reapply verified account deletions before restoring customer access. The private recovery key is held separately from the backup service.

GitHub workflow records and logs currently have a 90-day repository retention setting, separate from the seven-day encrypted backup expiry. Our backup jobs are configured to record operational outcomes and encrypted archive metadata, not account rows. Provider security logs and email-delivery records follow their own retention policies. We do not promise immediate removal from every provider copy or assume that active or archived support conversations expire automatically.

Your choices and rights

Contact the operator below to request information, access, correction, deletion, objection, restriction or portability, as applicable. You may also withdraw consent for a use based on consent. We may verify your identity before changing or disclosing account information; do not send passwords or login codes with a request.

You can contact Ecuador's Superintendencia de Protección de Datos Personales (SPDP) about a data-protection concern. Other mandatory rights may apply where you live. Professional services are not directed at young children; contact us if you believe a child has provided personal information.

• Ecuador's data-protection authority

Security and local call content

The account flow uses HTTPS, restricted browser connections, locally hosted scripts, non-cached account pages and server validation before displaying account identity. Direct database and pooler connections require TLS; backup clients also verify the database certificate. Outbound support email requires TLS delivery rather than falling back to an unencrypted connection; this is transport protection, not end-to-end email encryption. These protections reduce risk; they do not guarantee that every device, provider or communication is secure.

Keep your device and account secure. Do not email protected health information, confidential call content or internal documents to support. Local desktop processing and copying/capture restrictions do not, by themselves, certify a particular deployment or workflow as HIPAA compliant.

Changes and contact

Material changes to data use will be explained before the new use, with a new choice where consent is required. Contact the operator below for privacy questions, account-deletion requests or a copy of the applicable notice.