Privacy Policy | Tupo
Privacy at Tupo

Your memos, kept close.

Tupo is local-first by design. Your library lives on your device. This page explains the few moments your data does leave it, and the care we take when it does.

Effective date October 29, 2026

This Privacy Policy explains how Talvie Inc., a Delaware corporation ("Tupo," "we," "us," or "our"), handles information when you use the Tupo mobile application, website, and related services (the "Service"). Talvie Inc. is responsible for the personal information it processes through the Service. Talvie Inc. is incorporated in Delaware and has operations based in Oakland, California.

Tupo is designed to be local-first. Your memo library is stored on your device by default. Your device turns recordings into text. The AI that writes summaries receives text, not your voice. Some features use cloud services for account authentication, AI summaries and recaps, optional encrypted backup, messaging and sharing, push notifications, app updates, support reports, and diagnostics. We do not sell your personal information, use memo content for advertising, or use third-party ad tracking.

Section 1

Information We Handle

Account and profile information

If you create an account, Tupo uses Supabase Auth to manage sign-up, sign-in, session handling, email verification, password reset, and account deletion. We may handle:

  • Email address.
  • Supabase user ID.
  • Display name.
  • Username.
  • Authentication state.
  • Multi-factor authentication status.
  • Session metadata.
  • Profile records used for connections, messaging, and sharing.

Authentication credentials and password handling are managed through Supabase and platform authentication systems. Tupo stores authentication tokens locally using secure device storage where supported.

Subscription and purchase information

If you buy a Tupo subscription, the purchase is processed by the Apple App Store, and Tupo uses RevenueCat to manage your subscription and confirm which plan you are entitled to. Tupo may handle:

  • Subscription status and the plan you are entitled to.
  • Product and transaction identifiers.
  • Purchase, renewal, and expiration dates.
  • Trial status.
  • A RevenueCat app user ID linked to your account so your plan syncs across your devices.

Apple handles your payment. Tupo does not receive your full payment card number or your Apple ID password.

Memo, journal, and meeting content

Tupo lets you record, process, organize, and review voice memos, meetings, reflections, and recaps. Depending on what you create and which features you use, Tupo may handle:

  • Audio recordings and audio segments.
  • Transcripts.
  • Summaries.
  • Daily and weekly recaps.
  • Meeting notes, key points, decisions, open questions, and action items.
  • Tags, moods, spaces, timestamps, dates, duration, and processing status.
  • People, places, and follow-ups mentioned in your content.
  • Memo photos and image attachments.
  • Profile avatar photos stored locally in the app.
  • User notes and edits.

Tupo may infer people and places from the content you record or type. Tupo does not currently request access to your device contacts and does not currently request precise GPS location. Places in Tupo are created from content you provide or edit.

Messaging, sharing, and connection information

If you use messaging, sharing, or connection features, Tupo may handle:

  • Connection requests and connection status.
  • Direct message threads and message metadata.
  • Direct text messages.
  • Direct voice messages.
  • Shared memo payloads and shared memo status.
  • Sender and recipient profile information, such as display name and username.
  • Read status, delivery status, timestamps, notification metadata, and thread previews.

Direct text messages are designed to be encrypted before they are stored or transmitted through Tupo's messaging service when both users' devices can exchange the required encryption keys. If a recipient's device has not completed that setup, Tupo may prevent message delivery until the recipient opens Tupo messages. Direct voice messages currently use Tupo's memo-sharing delivery path. They are access-controlled and transmitted over HTTPS/TLS, but they may include playable audio, transcript excerpts, summaries, or related memo details in Tupo-controlled cloud systems, and they are not end-to-end encrypted.

On-device transcription and AI summaries

Your device turns your recording into text. Tupo does not send audio to a transcription service. If transcription cannot finish, your recording stays saved so you can try again. Supported languages and speech tools depend on your device; an initial download may need internet.

For summaries, meeting notes and recaps, Tupo sends text and the context needed for the feature through its servers to Anthropic. The AI that does this work receives text, not your voice. Tupo tries to hide names and sensitive details before sending text, but this can miss details and does not guarantee anonymity.

Tupo does not use your memo content to train third-party foundation models. Text sent for AI processing is still read by the services that process it.

Tupo may temporarily store text, results and job information to finish processing and return the answer. Where supported, transcript and result fields are cleared after your device confirms it has saved the result.

Audio can still leave your device when you choose to share it or include it in an encrypted backup. Those features are explained separately below.

Scheduled recaps

Tupo can generate recaps locally from on-device summaries. When server scheduled recaps are used, Tupo sends compact recap-source summaries through Supabase Edge Functions, stores them encrypted for a short time, sends redacted summary context to Anthropic to generate the recap, and stages the completed recap encrypted for client pickup. After the app saves the recap locally, Tupo asks Supabase to clear the staged server result. Expired staging is cleaned up as a fallback.

Scheduled recap systems may store operational metadata such as preferred recap time, timezone, period, space, queue status, job status, timestamps, and error state.

Optional encrypted cloud backup and archive export

If you enable encrypted cloud backup, Tupo encrypts backup data before upload to private Supabase Storage. Encrypted backups may include selected parts of your Tupo data, such as memo details, summaries, transcripts, people and place records, recaps, original audio, memo photos, and message conversation key backup records.

Tupo does not receive your raw recovery passphrase. If you choose to save a backup passphrase on your device, Tupo stores it locally using secure device storage where supported. If you lose your recovery passphrase and do not have another recoverable copy, Tupo may not be able to restore your backup.

Tupo may also support encrypted local archive export. Exported files are controlled by you once they leave the app.

Device, notification, and app metadata

Tupo may handle device and app metadata needed to operate the Service, including:

  • Platform, app variant, app version, native build version, runtime version, and update ID.
  • Device name, device model, operating system name, and operating system version.
  • Expo project ID and Expo push token.
  • Notification permission status.
  • Native speech capability, routing decisions, and transcription status.
  • Network reachability status.
  • App configuration needed to operate enabled features.

Expo push tokens are stored in Supabase with user ID, platform, app variant, project ID, device name, device model, OS name, OS version, active status, and last-seen timestamp so Tupo can send push notifications for memo processing, messages, connection requests, and recap-related events.

Diagnostics, support, and feedback

Tupo uses diagnostics to understand crashes, reliability problems, background recording issues, memo processing failures, backup and restore failures, messaging failures, and other app behavior. Diagnostics may include:

  • Crash logs.
  • Stack traces.
  • Error messages.
  • Performance data.
  • Feature status counters.
  • Processing phase, route, provider, model, status, file size, duration, transcript length, and retry state.
  • Sanitized metadata about active recording, memo processing, backup, messaging, and scheduled recap state.

Tupo is designed to scrub or avoid sensitive diagnostic fields such as raw memo audio, full transcripts, summaries, prompts, passwords, passphrases, access tokens, refresh tokens, secrets, local file paths, signed URLs, and raw content. Diagnostics may still include account-linked user IDs, app state, device metadata, and sanitized operational metadata.

If you submit feedback, a bug report, recap issue, or tester review, Tupo may send your submitted text, selected severity, contact preference, app runtime snapshot, app context snapshot, and recent sanitized diagnostics through a Supabase Edge Function to Slack webhooks used by the Tupo team.

Permissions and local device features

Tupo may ask for access to:

  • Microphone, to record voice memos and meetings.
  • Speech recognition, to transcribe eligible recordings.
  • Notifications, to send reminders, memo-ready alerts, message alerts, connection alerts, and related app notices.
  • Camera and photo library, to attach photos to memos and set profile photos.
  • Local files, sharing, and printing features, for import, export, backup, archive, PDF, and share flows.
  • Face ID, fingerprint, passcode, or local authentication, to protect app access or saved credentials on your device.
  • Background audio capability, to support background recording where the platform allows it.

You can manage platform permissions in your device settings.

Section 2

How We Use Information

Tupo uses information to:

  • Provide account creation, sign-in, email verification, session management, password reset, and account deletion.
  • Process, restore, and manage subscription purchases and confirm which plan you are entitled to.
  • Record, save, transcribe, summarize, and organize voice memos and meetings.
  • Generate daily and weekly recaps.
  • Extract and maintain people, places, tags, follow-ups, key points, action items, decisions, and open questions.
  • Provide local search, browsing, export, archive, backup, restore, and storage-management features.
  • Turn recordings into text on your device.
  • Send transcript or recap context to AI providers to produce structured output.
  • Enable connections, direct messages, shared memos, voice messages, and notifications.
  • Store optional encrypted cloud backups and restore them when you provide the required recovery materials.
  • Send local notifications and push notifications you enable or trigger through app features.
  • Receive support requests, feedback, bug reports, and tester reviews.
  • Debug crashes, reliability issues, failed uploads, failed downloads, failed background processing, and security issues.
  • Protect accounts, prevent abuse, enforce Terms, and comply with law.
Section 3

What Stays Local and What Leaves Your Device

Tupo is local-first by design. Your memo library, people and place records, recaps, settings, and locally retained media are stored on your device by default.

Information may leave your device when:

  • You create or use a Tupo account.
  • You send text for background memo or meeting summaries.
  • You use AI parsing, summaries, or recap generation that requires cloud processing.
  • You enable encrypted cloud backup.
  • You use messaging, sharing, connections, or voice messages.
  • You register for push notifications.
  • You purchase, restore, or manage a subscription.
  • You submit feedback, support reports, bug reports, or tester reviews.
  • You export, share, print, upload, or otherwise move data outside the app.
  • Diagnostics or crash reports are sent to Sentry or Tupo-operated support systems.

Information processed only on your device is not accessible to Tupo unless you choose or use a feature that sends it off device.

Section 4

Third-Party Services

Tupo does not sell personal information. Tupo does not share memo content with advertising networks or data brokers. Tupo shares information with service providers only as needed to operate the Service, provide features you use, maintain security and reliability, or comply with law.

Tupo currently works with the following providers and recipients:

Supabase. Authentication, profile records, database, row-level access controls, realtime messaging infrastructure, private storage, Edge Functions, encrypted backup storage, account deletion, memo processing jobs, scheduled recap storage, push token registry, and server-side cleanup. Information involved includes account and profile data, user IDs, session-authenticated requests, database rows, private storage objects, temporary text-processing data, encrypted backup objects, messaging records, push token records, scheduled recap metadata, encrypted recap-source summaries, encrypted staged recap results, and operational metadata.

Anthropic. AI processing for structured memo parsing, meeting notes, summaries, daily recaps, and weekly recaps. Information involved includes transcript text, redacted transcript text, compact recap context, prompts, and metadata needed to return structured AI output.

Sentry. Crash reporting, error monitoring, performance diagnostics, and app reliability monitoring for the app and some Edge Functions. Information involved includes crash logs, stack traces, app metadata, device metadata, user ID where configured, sanitized diagnostic context, and operational error information.

Expo and EAS. App update infrastructure and push notification delivery. Information involved includes Expo push tokens, app identifiers, project identifiers, platform information, update identifiers, runtime version, and notification payloads needed to deliver app updates and notifications.

Slack. Internal handling of support, feedback, bug reports, recap issues, and tester reviews submitted by users. Information involved includes user-submitted report text, rating or review fields, contact preference, user ID, display name or username, app/runtime snapshot, app context snapshot, and recent sanitized diagnostics.

RevenueCat. Subscription and purchase management, entitlement checks, and receipt validation for in-app purchases. Information involved includes purchase and subscription events, product and transaction identifiers, subscription status, and an app user ID used to sync your plan across your devices.

Apple, Google, and device platform services. App distribution, operating system permissions, speech recognition, notifications, secure storage, biometrics, background audio, app review, in-app purchase and subscription billing, and crash or platform services. Information involved is limited to what the device, operating system, app store, or platform provider requires to perform the requested function.

Legal, safety, and compliance recipients. Compliance with law, legal process, security, abuse prevention, and protection of rights. Information involved is limited to what is reasonably necessary for the specific legal, security, safety, or compliance purpose.

Section 5

Security

Tupo uses safeguards designed to protect information, including Supabase authentication, private storage buckets, row-level access policies, secure token storage, local encrypted storage where supported, encrypted cloud backup, authenticated encryption for backup objects, local secure storage for certain secrets, provider-side API keys kept off the client, diagnostic scrubbing, and HTTPS/TLS for data transmitted between the app, Tupo-controlled services, and service providers.

No method of transmission or storage is perfectly secure. Tupo cannot guarantee absolute security. Your device security, passcode strength, operating system security, account security, recovery passphrase management, and sharing choices also affect the privacy and security of your information.

Section 6

Retention

Tupo keeps information for as long as needed to provide the Service, operate features you use, maintain security and reliability, comply with law, resolve disputes, and enforce agreements.

Current retention practices include:

  • Local app data stays on your device until you delete it, delete your account and local data, uninstall the app, or clear device storage.
  • Local audio is deleted after successful processing by default unless you choose to keep it. Audio needed to retry an unfinished or interrupted recording stays saved.
  • Completed server-side transcript and parsed-result fields are cleared after client acknowledgement where supported.
  • Encrypted cloud backups remain until overwritten, deleted by you, or deleted during account deletion where possible.
  • Push tokens remain until deactivated, replaced, deleted, or removed during account deletion.
  • Subscription and purchase records are kept as needed to provide and restore your subscription, meet tax and accounting obligations, and comply with app store and legal requirements.
  • Support and feedback reports are retained for as long as needed to respond, investigate, improve the Service, and maintain records.
  • Diagnostics are retained for a limited period needed for security, reliability, debugging, and service operation.
  • Account and profile data remain while your account is active and are deleted or de-identified after account deletion, subject to operational backups, legal obligations, and provider retention practices.
Section 7

Your Choices and Controls

You can:

  • Delete individual memos and local content in the app.
  • Export your Tupo data where export features are available.
  • Use encrypted local archive export where available.
  • Enable, unlock, restore, or delete encrypted cloud backup where available.
  • Delete your account from account settings.
  • Manage local audio retention settings.
  • Manage speech permissions and available on-device transcription settings.
  • Manage notifications in Tupo and in your device settings.
  • Revoke microphone, speech recognition, camera, photo library, notification, and biometric permissions in device settings.
  • Choose whether to submit diagnostics with feedback reports when the app provides that option.

Deleting the app may remove local data from your device but may not delete account data, cloud backups, messages, shared content, support reports, provider logs, or operational records stored outside the device. Use the in-app account deletion flow to request account deletion.

Section 8

Privacy Rights

Depending on where you live, you may have rights to request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or appeal of a privacy decision regarding certain personal information.

California residents may have rights to know, delete, correct, opt out of sale or sharing, limit certain uses of sensitive personal information, and not be discriminated against for exercising privacy rights.

Tupo does not sell personal information and does not share personal information for cross-context behavioral advertising.

To make a privacy request, contact us at info@trytupo.com. This email address is also Tupo's current privacy choices and "Do Not Sell or Share My Personal Information" contact method. Because Tupo does not sell personal information or share personal information for cross-context behavioral advertising, Tupo does not currently provide a separate opt-out link for sale or sharing.

We may need to verify your identity before fulfilling a request. Some information may be unavailable to Tupo because it is stored only on your device, encrypted before upload, deleted, or controlled by a third-party platform.

Section 9

GDPR, UK GDPR, and International Privacy Rights

If you are in the European Economic Area, the United Kingdom, or Switzerland, Talvie Inc. is the controller for personal information processed through the Service.

Tupo relies on the following legal bases where applicable:

  • Performance of a contract, to provide the Service and features you request.
  • Consent, where you grant device permissions, enable optional features, submit optional reports, or consent is otherwise required.
  • Legitimate interests, to secure, maintain, debug, improve, and protect the Service, provided those interests are not overridden by your rights and interests.
  • Legal obligation, to comply with applicable law, legal process, and enforceable government requests.

You may have rights to access, correct, delete, restrict, object to processing, receive a portable copy of personal information, withdraw consent, or lodge a complaint with your local data protection authority. Tupo has not appointed a Data Protection Officer. GDPR and UK GDPR questions may be sent to info@trytupo.com.

Section 10

Children

Tupo is not directed to children under 13 or to children under the minimum digital-consent age where a higher age applies. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to Tupo in violation of this policy, contact us at info@trytupo.com and we will take appropriate steps.

Section 11

Sensitive Content

Tupo is a general voice memo and journaling app. Because free-form voice, text, photos, messages, and recaps can include sensitive information, you should be thoughtful about what you record, process in the cloud, back up, export, message, or share.

Tupo is not intended to be a HIPAA-covered medical record system, emergency service, legal record system, financial advisory system, or safety-critical service.

Section 12

International Processing

Tupo and its service providers may process information in the United States and other countries. Those countries may have privacy and data protection laws different from the laws where you live. Where required, we rely on appropriate safeguards for international transfers.

Section 13

Changes to This Policy

Tupo may update this Privacy Policy from time to time. If we make material changes, we will provide notice by updating the effective date, posting the updated policy, sending an email, displaying an in-app notice, or another reasonable method.

Your continued use of the Service after the updated policy takes effect means you acknowledge the updated policy.

Section 14

Contact

Questions or privacy requests may be sent to:

Talvie Inc.

Email: info@trytupo.com

Website: https://trytupo.com