Back to Yuho

Your space, your choice

Privacy Policy

Last updated: October 18, 2026

1. Who we are

Yuho is a voice diary app for iPhone that helps you capture walks, thoughts, and moments. Optional features can include location and transcripts. We operate the Yuho app and the website yuho.io, including public share pages at yuho.io/s/… when you choose to share a recording from the app.

2. What we collect

iOS app (on your device)

  • Voice recordings and related content — stored locally on your device by default. Using or enabling cloud AI, web sharing, or an export can send the relevant content to the services described below.
  • Metadata you create — such as titles, notes, timestamps, and optional location, as configured in the app.
  • App preferences and identifiers — for example a device identifier used to manage web shares or API access, stored according to platform APIs (e.g. Keychain) where applicable.

Accounts and purchases

  • Account information — your email address, account identifier, and any name or profile image supplied by your chosen sign-in provider. You can edit your Yuho nickname and choose a profile photo in Account management. Custom profile photos are stored in a private Supabase bucket and displayed using short-lived signed links; the app removes photo location metadata when preparing an upload. Email sign-in also uses authentication credentials. Supabase provides our account authentication and profile-photo storage; Apple or Google handles its own sign-in flow when selected.
  • Purchases and credits — subscription status, purchase identifiers, credit balances, and usage records needed to deliver purchases and process AI requests. Apple processes payments, and RevenueCat helps manage purchase entitlements. We do not receive your full payment-card details.
  • App usage and diagnostics — account and device identifiers, app version, feature events, request status, and timing information used to operate, troubleshoot, and understand use of Yuho.

Optional cloud AI

  • Content for processing — relevant audio for transcription, and text and context for polish, titles, tags, summaries, personal vocabulary, or Weekly Recaps. These features send the required inputs to our backend and AI service providers; they are not entirely on-device processing.
  • Your settings — AI processing can start automatically for eligible recordings when enabled in your current settings. Long recordings can require confirmation with a credit estimate. Recording itself does not require cloud AI.
  • Operational records — requests may create processing jobs, results, usage and billing records, and service or AI Gateway logs. We do not promise that cloud content is immediately erased after every request.

Web sharing (yuho.io) — when you share a recording to the web from the app

  • Audio file — uploaded to our storage so visitors with the link can play it.
  • Share metadata — such as title, duration, optional transcript segments, optional location or route summary, expiry, and a secret token embedded in the link so only people you share with can access the page.
  • Device / app authentication data — values the app sends so we can create, manage, or revoke your share (for example an app key and device identifier). We use these to enforce limits and let you delete a share from the app.

Visitors to yuho.io

  • Technical data — standard server and CDN logs (for example IP address, user agent, timestamps) processed by our hosting provider.
  • Product analytics — on marketing pages we may use analytics tools (for example PostHog) to understand aggregate usage. You can use browser controls or ad-blockers to limit this.
  • Share listening analytics — for shared recordings we may record aggregated events (such as plays or progress buckets) tied to the share ID and a short-lived hashed viewer identifier derived from connection metadata, to understand how content is used. We do not use this to sell personal profiles.

Optional Notion export — when you connect Notion and actively export a recording

  • Connection data — your Notion workspace and bot identifiers, encrypted OAuth access and refresh tokens, and the identifiers of the Yuho page and database created in your workspace.
  • Exported content — the text, metadata, and any photos or route image you select are sent to Notion only when you tap export. Yuho does not automatically sync recordings to Notion.
  • Export receipts — Yuho stores recording and Notion page identifiers, content fingerprints, and status information so repeated exports update the same page. We do not retain the exported diary text, photos, or route image in this receipt database.

We do not sell your personal information. We do not use your voice recordings to train third-party AI models. We do not show third-party ads in the product experience described above.

3. How we use it

  • To provide the Yuho app and its features
  • To authenticate accounts, manage subscriptions and credits, and provide cloud AI when used or enabled
  • To host, deliver, and revoke web shares you create
  • To connect your Notion workspace and deliver exports you explicitly request
  • To protect the service (abuse prevention, rate limits, security monitoring)
  • To improve reliability and fix bugs
  • To respond when you contact us

4. Web share links

Anyone who has the full link (including the access token in the URL) can play the shared recording until you revoke it or it expires, according to the options you chose in the app. Treat links like a private key: only send them to people you trust.

5. Who we share data with

  • Cloudflare — we host yuho.io, APIs, metadata database (D1), object storage (R2) for shared audio, and related infrastructure on Cloudflare.
  • Analytics providers — for example PostHog for website analytics where enabled.
  • Apple — when you download or purchase through the App Store, Apple processes that interaction under Apple’s terms and privacy policy.
  • Supabase and sign-in providers — account authentication and profile information; Apple or Google also processes sign-in information when you choose that provider.
  • RevenueCat — subscription and in-app purchase entitlements associated with your account.
  • AI processing providers — relevant requests are routed through Cloudflare AI Gateway. Depending on the feature and availability, processing can involve Groq, Mistral, or OpenRouter and its routed model providers, such as OpenAI or Google. Provider routing and fallback choices can change. These services process the inputs needed to return your requested result.
  • Notion — if you connect Notion, content you actively export is delivered to your chosen workspace and is then handled under your Notion account and Notion’s privacy terms.
  • Map tiles — share pages that show a map may load map imagery from third-party tile providers (for example OpenStreetMap-based services). Those requests may expose your IP to the tile host under their policies.

We do not sell lists of users or recordings to data brokers.

6. Data storage & security

  • Traffic between your device and our services uses encryption in transit (HTTPS / TLS).
  • Shared audio and metadata are stored in our cloud environment with access restricted to operating the service.
  • Notion OAuth tokens are encrypted at rest and are never returned to the iOS app.
  • No method of transmission or storage is 100% secure; we work to follow reasonable industry practices.

7. Data retention & deletion

  • Recordings that stay only on your phone are under your control; uninstalling the app or deleting entries follows iOS and in-app behaviour.
  • When you revoke a web share from the app, we remove access and delete associated hosted content according to our backend implementation and backups cycle.
  • Shares may expire automatically based on the expiry you selected.
  • Account, purchase, credit, processing-job, and diagnostic records can have different retention requirements. We retain records as needed to provide the service, resolve failures or billing issues, prevent abuse, and meet applicable obligations. AI providers may also retain request data under their service terms and applicable configuration.
  • Disconnecting Notion removes Yuho’s stored tokens and export receipts. Pages already created in your Notion workspace remain there for you to keep or delete.
  • In Yuho, open Settings → Account management → Danger Zone → Delete account to initiate permanent account deletion. This removes the cloud account and custom avatar, owned hosted shares, Notion connection and export receipts, cloud AI job/cache data, and the associated purchase profile and unused credits. Your recordings, journals, and photos on this device remain available. Copies you previously exported to other apps remain under your control there.
  • Deletion may proceed in stages. A private recovery receipt lets a confirmed deletion resume after a network failure; completed receipts no longer contain your account ID and are eligible for cleanup after seven days. Minimal deletion markers prevent old tokens, late callbacks, or purchase webhooks from recreating the deleted account’s data. Provider logs, required security records, backups, and store transaction records follow their applicable retention requirements.
  • Deleting a Yuho account does not cancel an Apple subscription or automatically revoke Sign in with Apple permission. Use the in-app subscription-management link to manage or cancel subscriptions. Apple sign-in users are also shown how to stop using Apple sign-in for Yuho in Apple Account settings. Email privacy@yuho.io for help or other privacy requests.

8. Your rights

Depending on where you live, you may have rights to access, correct, export, or delete personal data we hold, or to object to certain processing. Contact us at privacy@yuho.io and we will respond within a reasonable time. If you are in the EEA or UK, you may also lodge a complaint with your local supervisory authority.

9. Children

Yuho is not directed at children under 16. We do not knowingly collect personal information from children. If you believe we have, contact privacy@yuho.io and we will take appropriate steps.

10. International transfers

Our service providers may process data in the United States and other countries. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for transfers from the EEA, UK, or Switzerland.

11. Changes

We may update this policy from time to time. We will post the new version on this page and update the “Last updated” date. For material changes affecting web sharing, we may also provide notice in the app or by email where appropriate.

12. Contact

Questions about privacy? Email privacy@yuho.io.