Sections
  1. 1. What this policy covers
  2. 2. Information processed on your device
  3. 3. Microphone use, raw audio, and voice recognition
  4. 4. Information we receive directly
  5. 5. Website information, cookies, and tracking
  6. 6. Downloads, backups, exports, and device permissions
  7. 7. Sale, advertising, and AI training
  8. 8. When information is disclosed
  9. 9. Retention, deletion, and your controls
  10. 10. Security
  11. 11. Children and minimum age
  12. 12. Privacy rights and processing locations
  13. 13. Changes and contact

Memvia — Privacy Policy

Effective date: [EFFECTIVE_DATE]
Operator: [LEGAL_OPERATOR_NAME]
Address: [BUSINESS_POSTAL_ADDRESS]
Privacy contact: [PRIVACY_EMAIL]
Website covered: [WEBSITE_URL]

1. What this policy covers

This policy explains how [LEGAL_OPERATOR_NAME] (“Memvia,” “we,” “us,” or “our”) handles personal information in the Memvia applications, the website identified above, and support communications.

Memvia is a memory and productivity app that helps people capture, organize, summarize, and retrieve information and manage tasks. Different features can involve different information. Information processed by an app on your device is distinct from information sent to us, our service providers, or an independent service you choose.

This policy is a notice about data practices. It is not a blanket authorization to record other people or a substitute for consent required for a particular activity.

2. Information processed on your device

[VERIFY LOCAL PROCESSING: retain the next two paragraphs only if they are true for every supported capture, transcription, AI, search, and speech feature, including fallback paths.]

Memvia processes the content used by its core memory features on your device. This can include text you enter, audio you choose to capture, transcripts, saved memories, AI-generated summaries and responses, tasks, and the local search data needed to retrieve them. We do not receive that private content merely because you use those features.

We do not send your recordings, transcripts, memories, prompts, or generated responses to an external AI or speech-recognition service for processing. If a required on-device feature is unavailable, Memvia explains the limitation instead of silently switching to cloud processing. Downloads needed to install models or software are described in section 6.

These statements do not mean that no information ever leaves your device. Information you deliberately send to support, website requests, purchases, exports, and device-managed backups are addressed separately below. Features that transmit private content must be specifically disclosed before they are used.

Account requirements: [ACCOUNT_DETAILS — confirm whether there is no Memvia account, or identify the account provider, identifiers collected, purposes, storage, retention, and deletion controls.]

3. Microphone use, raw audio, and voice recognition

Microphone and recordings

Microphone access is used to provide voice-capture features that you activate. You can stop capture using [STOP_CAPTURE_CONTROL] and revoke microphone permission in your device's system settings. Revoking permission prevents future microphone access through that permission; it does not by itself delete information already saved.

When capture runs: [CAPTURE_BEHAVIOR — describe user initiation, any background or continuous capture, lock-screen behavior, pause/stop controls, and the visible or audible recording indication.]

Raw-audio handling: [AUDIO_HANDLING — state whether audio remains only in memory, is written to temporary files, or is saved as recordings; specify the actual maximum lifetime or retention rule for each, cleanup after failure or crash, and any user-controlled saving.]

Transcripts and derived information: [DERIVED_CONTENT — identify exactly which transcripts, summaries, memories, tasks, and search representations are stored, whether saving is automatic or user-directed, and how each can be deleted.]

Deleting raw audio does not automatically remove a separately saved transcript, summary, memory, or task. These derived records can contain personal or sensitive information even when the original recording no longer exists.

Speech recognition and speaker identification

Converting speech to text is different from identifying a person by their voice. A voice profile or voiceprint can involve biometric information.

Features in this release: [VOICE_FEATURES — explicitly state either that Memvia does not create or use voiceprints/speaker profiles, or describe the actual speaker-identification feature and complete the disclosures below. Do not use a “no biometrics” statement for a build that creates speaker embeddings used to identify people.]

[IF SPEAKER PROFILES ARE ENABLED: disclose enrollment samples and derived templates; the specific purpose; whether enrollment is optional; whose profiles may be created; where each type is processed and stored; every recipient; the retention and destruction triggers; the exact deletion/withdrawal control; and the separate notice and consent process. Remove this instruction only after a complete, accurate disclosure and any required biometric policy are in place.]

A recording permission or acceptance of general terms is not a substitute for any separate biometric consent the law requires. Speaker identification is not reliable proof of identity and does not ensure that bystanders' voices are excluded from capture.

Other people in a conversation

Before capturing a conversation, users must inform participants and obtain permission as required by our Terms and applicable law. Processing on a device or deleting the audio does not remove the privacy interests of the other people involved.

If you believe a Memvia user captured your information improperly, contact [PRIVACY_EMAIL]. We can address information we actually hold or control and explain available options. We cannot inspect or remotely erase another person's device-only records merely because we receive a request.

4. Information we receive directly

Support and other communications

When you contact us, we receive the contact details, message contents, and attachments you choose to send, together with ordinary delivery metadata. We use them to respond, troubleshoot, handle privacy requests, and maintain appropriate records of those interactions. Sending content to support takes it outside the app's local processing environment.

Do not send passwords, unnecessary recordings, or other people's sensitive information. We will request only information reasonably needed to address the issue.

Support provider and processing locations: [SUPPORT_PROVIDER_AND_COUNTRIES]
Retention: [SUPPORT_RETENTION — specify the period or objective deletion criterion and any narrowly defined legal-retention exception.]

Purchases, if offered

If you buy Memvia or an in-app purchase through Apple, Apple processes the purchase under its own terms and privacy practices. We do not receive your full payment-card number from an App Store transaction.

Information available to Memvia: [PURCHASE_DATA — identify the transaction, entitlement, subscription, refund, financial-report, or account information actually received; identify any validation server/provider and retention. If no paid features exist, say so and remove in-app-purchase claims.]

Diagnostics and usage information

Actual practice: [DIAGNOSTICS — state whether Memvia receives any app analytics, crash reports, error logs, performance data, identifiers, or Apple-provided reports. Name each recipient, list data fields and purposes, explain whether participation is optional, provide the control, and specify retention. If none is received, state that only after verification.]

Any crash or support report deliberately shared with us is information we receive, even when the core app otherwise runs offline. Do not assume that a diagnostic report is anonymous merely because it lacks a name.

5. Website information, cookies, and tracking

Opening our website sends technical information needed to deliver the page to the website infrastructure, such as a network address. The specific information retained depends on the configuration described below.

Hosting, CDN, security, and embedded-content providers: [WEBSITE_PROVIDERS]
Data received or logged: [WEBSITE_DATA — specify actual IP-address, request, browser/device, referral, security, and form data, including what the operator can access.]
Purposes: [WEBSITE_PURPOSES]
Retention and processing countries: [WEBSITE_RETENTION_AND_COUNTRIES]

Cookies, pixels, local storage, and similar technologies: [COOKIE_DETAILS — list each technology, provider, purpose, duration, and consent/withdrawal control, or state that none is used after checking the host, embeds, fonts, analytics, forms, and anti-bot services.]

Browser Do Not Track response: [DNT_RESPONSE — describe the actual response; do not confuse this signal with Global Privacy Control.]
Global Privacy Control and applicable opt-out preference signals: [GPC_RESPONSE — explain the actual response and the relevant opt-out controls where required.]

If the site offers a contact form or optional mailing list, information entered is used for [FORM_AND_EMAIL_PURPOSES] and handled by [FORM_AND_EMAIL_PROVIDERS] for [FORM_AND_EMAIL_RETENTION]. Any marketing subscription must be optional and include a way to unsubscribe. [REMOVE THIS PARAGRAPH IF NO FORMS OR MAILING LIST EXIST.]

6. Downloads, backups, exports, and device permissions

Model and software downloads

Installing or updating the app or downloading an on-device model can require a network connection. A download does not itself require sending your memories or conversations to a model provider.

Actual download behavior: [DOWNLOAD_DETAILS — identify Apple or any separate download host, the request metadata it receives, retention where controlled by us, and whether any content or identifiers accompany requests.]

Backups and synchronization

On-device processing does not, by itself, exclude app files from an operating-system backup. Depending on settings and app configuration, a device backup or synchronization service can create a copy outside the device.

Memvia's actual behavior: [BACKUP_AND_SYNC — state whether app-managed synchronization exists; whether private databases, audio, voice profiles, attachments, and other files are included in or excluded from iCloud/device backups; explain any user controls and material limits.]

We do not gain access to a backup merely because you create it with an independent provider. That provider's practices apply to its own service. An exported copy, a computer backup, or a copy shared with another person can remain after the original is deleted from Memvia. Deleting the app or offloading it is not a reliable substitute for following the deletion instructions below.

Exports and sharing

If an export or sharing feature is available, content you choose to send is delivered to the destination you select. Review the destination and the content before sharing it. Recipients and independent services may keep their own copies.

Available controls and destinations: [EXPORT_AND_SHARING_DETAILS — list actual features, or state that export/sharing is unavailable.]

Other permissions

Permissions besides the microphone: [OTHER_PERMISSIONS — list each permission actually requested and its specific purpose, including speech recognition, notifications, files, contacts, calendar, Bluetooth, or location only if used. Explain which features stop working when permission is denied.]

You can manage operating-system permissions in your device settings. Withdrawing a permission does not automatically delete previously stored data or revoke a separate authorization granted to another service.

7. Sale, advertising, and AI training

[VERIFY THESE COMMITMENTS across the app, website, SDKs, and providers before retaining them.]

We do not sell your personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. We do not use your private recordings, transcripts, memories, prompts, or generated responses to train shared or general-purpose AI models. We do not authorize our providers to use private content you send us for their own advertising or model training.

Using saved information to retrieve a relevant memory or generate a response on your device is different from using it to train a shared model.

Local learning, if any: [LOCAL_LEARNING — disclose whether the app changes model weights or speaker profiles using personal content; explain storage, controls, and deletion. If it only retrieves context, do not describe that as model training.]

8. When information is disclosed

For information we actually receive or control, disclosure is limited to the purposes and recipients explained in this policy:

  • Providers acting for us: the hosting, support, diagnostics, payment-validation, or other providers specifically identified above, only as needed for the described service and subject to appropriate privacy and security obligations.
  • Your instructions: a disclosure you request, such as sending an export or submitting material for support.
  • Legal and security purposes: when required by valid legal process or otherwise permitted by law and reasonably necessary to protect rights, investigate misuse, or address a security issue. A legal request does not give us access to device-only records that we do not possess or control.
  • A business transaction: information we actually hold may be transferred in a lawful merger, acquisition, or similar transaction, subject to applicable notice, consent, and continuing privacy obligations. This does not authorize harvesting device-only memories or ignoring earlier privacy promises.

We require providers handling information on our behalf to protect it consistently with our commitments and applicable requirements. Independent services you choose, such as your own backup or export destination, act under their own terms. These distinctions do not remove our responsibilities for services we select or configure.

9. Retention, deletion, and your controls

We retain personal information only for a stated purpose and applicable retention period. The audio, voice-profile, website, support, diagnostic, and purchase-specific periods must be described in the sections above.

Local-content retention: [LOCAL_RETENTION — specify whether memories, transcripts, tasks, search indexes, and attachments remain until deleted, expire automatically, or follow another rule.]

Delete one item: [ITEM_DELETION_STEPS]
Delete all local content: [ALL_CONTENT_DELETION_STEPS]
Delete a voice profile and enrollment samples, if present: [VOICE_DELETION_STEPS]
Delete a Memvia account, if present: [ACCOUNT_DELETION_STEPS_OR_NO_ACCOUNT]
What deletion removes and when: [DELETION_SCOPE — include associated transcripts, summaries, search indexes/embeddings, temporary files, logs, and any residual copies; state what is not removed.]

If content exists only on your device, use the device's controls to manage it. A request to our support team cannot erase data to which we have no access. For information we hold, submit a request to [PRIVACY_EMAIL]. We may verify identity proportionately and apply legal exceptions, such as preserving a necessary transaction record or a record subject to a legal hold. We do not collect extra private memories merely to answer an unrelated privacy request.

Copies in backups or independently shared files may need separate deletion. We do not promise forensic erasure of every physical storage block merely because an item disappears from the app. Any limitation that affects our own data or backups must be disclosed specifically; it is not a general exemption from deletion duties.

10. Security

We use reasonable safeguards appropriate to the information and systems we control. [SECURITY_VERIFICATION — identify any specific protection you intend to claim and confirm it is actually implemented; do not claim end-to-end encryption, a particular encryption standard, zero access, or certification without evidence.]

No storage method or system is completely secure. Protect your device and any backups, review notification previews, and use current software. This explanation is not a waiver of our security obligations or your legal remedies. Where applicable law requires notification of a security incident, we will provide the required notice.

11. Children and minimum age

[VERIFY AUDIENCE: this section assumes a general-audience service that is not directed to children under 13. It must match the app, marketing, age controls, and actual known use.]

Memvia is not directed to children under 13. The minimum age for using the Services is [MINIMUM_AGE], as explained in the Terms of Use. We do not knowingly collect personal information from children under 13 through the Services without the legally required authorization.

If you believe we received such information improperly, contact [PRIVACY_EMAIL]. We will investigate and take steps required by applicable law, including stopping unauthorized processing and deleting information where required. This age statement does not replace any applicable parental-notice, consent, or other child-privacy obligation.

12. Privacy rights and processing locations

Depending on your location and whether a particular law applies, you may have rights to know about, access, correct, delete, or obtain a portable copy of personal information; withdraw consent; object to or restrict certain processing; or opt out of certain uses. You may also have a right to appeal a denied request or complain to an appropriate regulator. These rights can be subject to lawful exceptions.

Contact [PRIVACY_EMAIL] to make a request or appeal. We will respond within the period required by applicable law and explain any applicable exception. We will not unlawfully discriminate against you for exercising a privacy right. Where required, an authorized agent may act for you subject to appropriate verification.

Our operator is located in [OPERATOR_COUNTRY]. The provider and processing locations for information leaving your device are [PROCESSING_COUNTRIES_AND_PROVIDERS]. Device-only content is treated as described in sections 2 and 6. Any international transfer we arrange must meet applicable legal requirements.

[REGIONAL REVIEW: determine which U.S. state notices, sensitive-data consents, appeal mechanisms, or other requirements apply. Before offering the service in the EEA, UK, or other markets, add the required jurisdiction-specific information, including applicable legal bases, transfer safeguards, and representative details where required. Do not claim universal compliance on the strength of this paragraph.]

13. Changes and contact

We will post the effective date of an updated policy and provide appropriate notice of material changes. When a new use requires consent, we will obtain it before that use begins. Updating this policy alone does not authorize a materially inconsistent new use of information previously collected or cancel a prior promise.

Contact us about privacy, data rights, or this policy at:

[LEGAL_OPERATOR_NAME]
[BUSINESS_POSTAL_ADDRESS]
[PRIVACY_EMAIL]

Read the Terms of Use