YipYap Privacy Notice

Version yipyap-privacy-2026-09-17-v1. This version is effective from the date it is first published at yipyap.magneum.co/privacy.html; that publication date is shown with this notice.

Magneum Industries LLC operates YipYap (Language) and its companion integrations. This notice explains the information we use to provide your account, personal vocabulary, connected-AI features, pronunciation audio and optional weekly notifications.

This notice covers YipYap's United States release. YipYap is designed for adult language learners, and minors may use it. Connected AI services have their own eligibility and permission requirements; access to YipYap does not grant access to another provider's account or service.

A parent or guardian with a question about a child's information can contact support@magneum.co. Please start with a brief description and avoid sending a child's private vocabulary, credentials or full conversations. We will explain the verification and information needed to address the request.

Information we use and why

• Account and sign-in information. We use an account identifier and the information needed to sign you in through Apple or Google. Your email can be contact information; an email address alone does not establish account ownership or merge accounts.
• Your vocabulary and preferences. We store words and phrases, meanings, their language and script, active or archived status, capture information, your instruction language, teaching level, Learning Mode choice and related settings. We use these to provide and synchronize your personal vocabulary and the learning features you choose.
• Limited learning and activity records. We retain supported vocabulary proposals, edits, archives, rendering and playback records, and supported review records. An AI suggestion, an item appearing in text, or the fact that a word is saved does not establish that you recalled it correctly or mastered it.
• Connections and security. We keep integration permissions, credential verification records, temporary authorization and request-coordination records, and limited security history for grants, revocation, exports and account deletion. These protect access and prevent a delayed request from acting for a different account.
• Audio and notification information. If you use these features, we process pronunciation audio and related records, your pronunciation permission, weekly schedule and timezone, device notification permission and routing information, and delivery history as explained below.
• Support. An in-app verified support case records limited account-verification facts. If you email us, we also receive your email address and the message you choose to send. Please do not send passwords, access tokens or full AI conversations.

Our current app and account service do not use advertising, marketing analytics or cross-app tracking. We use operational and security information to run the service, investigate failures, protect accounts and handle support requests.

Connected AI services

You choose which supported AI integrations can access YipYap and what access to grant. A connected service may receive your permitted language settings and limited vocabulary context, or the personal vocabulary projection you explicitly request, and may send supported vocabulary proposals or actions. Learning Mode is controlled in YipYap; installing a plugin or signing in does not enable it.

We do not request or store your full AI conversations or prompts through the YipYap integration. The service rejects transcript-shaped fields. A short saved word or meaning can nevertheless contain information copied or paraphrased from a conversation, including personal information. A restricted data format cannot establish where every word came from. We do not receive your AI provider's sign-in credential through the integration.

Your AI provider separately handles the conversations and other information you give it under its own terms and privacy policy. Revoking a YipYap connection stops further authorized access to our service; it does not erase information that the provider already received or conversations stored in that provider's app.

We store hashes of integration access credentials in the account service, rather than their raw secret values. The connected app or plugin keeps the credential needed to authenticate. This differs from notification routing tokens, which must be retained in usable form to deliver notifications.

Optional Google pronunciation

Google saved-word pronunciation is off unless you explicitly allow it for your account in Settings. You can leave it off and keep using your saved words. Signing in, enabling Learning Mode, connecting an AI service, allowing notifications or granting a microphone permission does not provide this pronunciation permission.

When pronunciation is available and you allow it, saving or changing a supported word or phrase can start audio generation, including changes made through connected AI integrations. Generation can occur before you press Play. Pressing Play may also request missing audio. Turning pronunciation on does not scan words already saved.

We send the exact saved target word or phrase to Google Cloud Text-to-Speech to create pronunciation audio. We do not add your account identifier, email address, saved meaning or AI conversation to the synthesis request. Service authentication and technical request information are separate. The target text itself can contain personal information. This feature does not record your voice.

Google processes the text through its global service. The United States locations described below for our account database and functions do not mean that speech synthesis occurs only in the United States. Google processing is subject to the Google Cloud agreement accepted by Magneum Industries LLC for the YipYap project and its data-processing terms, including any applicable service-security and abuse-handling provisions; we do not promise that Google never retains submitted text.

We store generated audio and its processing records privately with your account. Those records can include target text, saved meaning and an item reference. We can cache audio in the app for playback. Editing or archiving a word may withdraw access to an earlier recording without physically erasing its processing record. Private server audio and jobs have no automatic timed expiry and can remain until account deletion unless removed earlier.

You can turn Google pronunciation off in Settings across your account's devices and connected integrations. A confirmed change stops authorization for new generation. Requests already starting or in progress may still reach Google, but results belonging to the withdrawn permission will not be attached to your account. Existing audio can still be played or downloaded under normal account and item access. Turning pronunciation off does not delete saved words, audio or processing records. If the app cannot confirm the change, it tells you that new generation may continue until confirmation.

We retain one current pronunciation permission record, containing the choice, wording version, revision and server update time, until it is replaced or the account is deleted. It is not a complete history of all past permission changes. Saving a private phrase does not publish it or automatically add it to a shared library. Any separately approved, customer-neutral library recordings are independent of your account.

The app can retain previously verified pronunciation downloads, with their saved text and meaning, on this device for the same signed-in account across app restarts. The Downloaded pronunciations view identifies these as last-verified copies. There is no time-based expiry for this offline access. While disconnected, the device cannot detect a remote word edit, archive, account deletion or access change. When the account reconnects, the app suspends the old copies until it verifies their current status; an unsuccessful check leaves them unavailable pending a connection check. Playing a retained download does not generate new audio.

Signing out or switching accounts on this device removes access to retained downloads. Confirmed account deletion on this device also removes that access. The app attempts to erase the corresponding cached files; a device or cleanup failure can delay physical erasure. An offline device can retain a last-verified copy after a remote change until it reconnects or you sign out locally. The device may remove cached files to free storage, and downloads are not guaranteed to survive removal of the app or incompatible updates. Turning generation off does not itself delete or revoke access to existing audio.

Optional weekly notifications

Weekly notifications require a separate choice for each app installation, as well as operating-system notification permission. We keep the selected account schedule and timezone, device binding and routing token, consent and registration state, and summary and delivery records. Your device may suggest a timezone; travel does not silently change the selected schedule.

The notification reports how many personal vocabulary items were added during a completed weekly period and identifies that period. It does not report mastery or a score. Its visible content and message data do not include your vocabulary, meaning text, account identity or AI conversations. The private routing information needed to reach your device is separate.

For the iPhone app, delivery uses Expo Push Service and Apple's Push Notification service (APNs). Those services process the notification and routing information to deliver it. Expo describes temporary queueing and possible staff access to content during active debugging. A notification can appear on your lock screen according to your device settings.

You can disable weekly notifications in YipYap or change device notification permission. Confirmed disable, sign-out, account change or deletion prevents further delivery authorization for that registration. A notification already handed to a delivery provider may still arrive; we cannot promise to recall it. Offline disable suppresses local presentation while server cancellation remains pending. The app identifies unconfirmed changes and offers a retry.

First opt-in, re-enabling, and schedule changes require a new complete eligible week. The first summary may take more than seven days. Notifications are best-effort and may be delayed or unavailable. One device's permission does not opt in another device.

Retention

The periods below distinguish access expiry from physical deletion. Scheduled cleanup runs in bounded batches, so a record becoming eligible for deletion is not a guarantee that every stored copy disappears at that instant. Account deletion and recovery copies are described separately below.

Your choices, export and deletion

Use Settings in the iPhone app to change Learning Mode and available feature permissions, manage connected integrations, choose Export my data, or start account deletion in Your account data. Export and deletion do not ordinarily require emailing support. We verify that a deletion request is intentional and comes from the account holder.

Your export includes account and Learning Mode state, personal vocabulary, retained learning events, integration grants, settings, baseline migration data, hidden-content identifiers, verified support cases, active-account security history, weekly preferences and retained summary/consent history, and your current pronunciation permission record when one exists.

The standard export excludes authentication secrets and codes, device push secrets and private delivery routes, and internal service mechanics such as derived views, request-replay records, indexes and page cursors, migration controls, export leases, deletion jobs, cleanup cursors, recreation-prevention records, reply-coordination records, and push worker leases/provider tickets. It also excludes generated pronunciation audio and pronunciation processing-cache/job records. These export exclusions do not limit applicable rights to request personal information through our verified support process.

Once a deletion request is accepted, your account is locked against further access while we remove its live data and sign-in record, revoke connected access, and remove associated notification routes and private pronunciation data. A failed deletion remains locked and is retried or referred for authenticated support completion. We do not describe an unconfirmed request as completed. Our account-deletion completion limit is 30 days, including the database recovery-copy window below.

For an account linked to Sign in with Apple, the normal app flow asks Apple to verify the account and revokes its Apple sign-in authorization before deleting YipYap data. If automatic revocation is unavailable or fails, the app offers a separate, clearly described deletion option and tells you to remove YipYap from Sign in with Apple in your Apple Account settings. Deleting YipYap does not delete your Apple or Google account.

After live account deletion, we retain a limited deletion-completion record for 30 days and a separate marker to prevent stale credentials from recreating the account. That marker is set for 30 days at the request and refreshed for 30 days at completion. These records contain no vocabulary, conversation or prior account-history content. Scheduled cleanup can lag their expiry. Internal deletion-recovery checkpoints may remain while completion is pending.

For help, sign in and create a verified support case when possible, then email its case ID to support@magneum.co. If you cannot access the account, contact that address for a verification process. Email alone is not proof of ownership. You may request access, correction or deletion of personal information to the extent applicable law provides those rights; the standard export is not the only request route. Copies you save or share outside YipYap, and conversations held by another app, remain under those separate controls.

Database recovery copies

We retain protected database backups and point-in-time recovery data for up to seven days. Deleted live records can remain in those protected copies until that window expires. Recovery copies are not used for ordinary service access. Before a restored system is used, completed deletions and revoked integration and notification access must be reapplied. This database window does not describe all processing by Google or other service providers, and it is separate from the limited deletion records described above.

Providers and processing locations

Google Cloud and Firebase provide account authentication, database storage and account-service infrastructure. Our Firestore account and vocabulary database uses Google's United States multi-region, and account-service functions run in Iowa, United States. Google Cloud Text-to-Speech uses a global synthesis endpoint. Expo and Apple process iPhone notification delivery. Amazon Web Services receives inbound support email and forwards it to a Google mailbox. These providers also handle the technical connection and security information needed to operate their services under the applicable terms. We require providers acting on our behalf to protect the information they process consistently with this notice and applicable requirements.

Connected AI providers receive only the access you authorize through the supported integration, in addition to information you independently give those providers. Their own privacy policies govern their separate handling. The locations of our database and account functions do not guarantee that every provider operation occurs in the United States.

Changes and contact

We will identify the current notice and its effective date when we publish an update. Where a change requires notice or renewed permission, we will provide it before the changed processing. This privacy notice explains our practices; reading it does not itself turn on pronunciation, notifications or Learning Mode.

Privacy questions and requests: support@magneum.co, Magneum Industries LLC.