Privacy Policy

Short version

• MemoryOS stores your captured memory content on your device.
• If iCloud sync is enabled and available, MemoryOS syncs supported app data through your private iCloud account using Apple's CloudKit infrastructure.
• MemoryOS does not operate a MemoryOS backend for storing your memory content.
• The current MemoryOS release does not use third-party product analytics SDKs, crash-reporting SDKs, advertising SDKs, or third-party cloud LLM providers.
• MemoryOS uses RevenueCat to present the paywall, manage subscription entitlements, and process purchase status. RevenueCat does not receive your captured memory content, wiki Markdown, AI prompts, or AI responses.
• Apple processes App Store purchases, subscriptions, iCloud, and Apple Intelligence features under Apple's own terms and privacy practices.

Data controller

For the purposes of this Privacy Policy, Pysagor is responsible for MemoryOS privacy practices described here. For privacy requests, contact hello@pysagor.com.

Data you create in MemoryOS

MemoryOS is designed for personal knowledge and memory capture. Depending on how you use the app, you may create or import:

• Text captures, source titles, notes, and manually entered web links.
• Manual voice recordings that you explicitly start and save.
• Images, screenshots, and files that you select or share into the app.
• Source metadata such as local source type, creation date, local revision, file size, and content hash.
• Local memory objects, source-backed claims, citations, review proposals, wiki pages, and generated Markdown files.
• Local search indexes, review states, sync state, and content-free audit metadata.
• Temporary export copies when you export your local Markdown vault.

This content is sensitive personal data if you choose to store sensitive information in MemoryOS.

Local storage

MemoryOS stores app data in local app-controlled storage, including a local SQLite database, local source asset files, and an app-controlled Markdown vault. Local storage may include raw sources, source assets, generated wiki Markdown, review proposals, search metadata, sync metadata, and local export files.

MemoryOS does not upload this local memory content to a MemoryOS-operated server.

iCloud sync

MemoryOS can use Apple's iCloud and CloudKit infrastructure for private sync when iCloud sync is available, configured, and enabled. Synced data may include supported source records, source assets, active memory metadata, wiki metadata, review state, and related sync metadata.

Some scalar CloudKit fields are stored using CloudKit encrypted values where supported. Source asset files are stored as private CloudKit assets because CloudKit does not support storing file assets inside encrypted value fields.

iCloud sync depends on your Apple ID, iCloud account status, available iCloud storage, device restrictions, network availability, and Apple's infrastructure. Apple processes iCloud data under Apple's own terms and privacy practices.

Apple Intelligence and on-device AI

MemoryOS can use Apple on-device Foundation Models / Apple Intelligence features when available on your device and when you explicitly start an AI action. These features are used for bounded, review-gated suggestions, such as proposed memory or wiki updates.

MemoryOS does not use third-party cloud LLM providers. MemoryOS does not persist raw AI prompt transcripts, raw model responses, provider debug text, or separate prompt/response logs. Reviewable AI output is stored only when it becomes part of a local proposed change that you can review.

Apple Intelligence availability depends on your device, operating system, Apple settings, language, region, and Apple's feature availability rules.

Purchases and subscriptions

MemoryOS uses RevenueCat and RevenueCatUI to present the paywall, manage subscription entitlements, process purchase status, and restore purchases. Apple processes App Store payments and subscription billing.

RevenueCat may process purchase-related data needed to provide subscription services, such as an app user identifier, product identifiers, receipt or transaction information, subscription status, store country or region, app version, device/store metadata, and entitlement state. RevenueCat may also provide subscription reporting such as customer history, charts, and entitlement status based on purchase events.

MemoryOS does not send raw captures, source files, wiki Markdown, search content, AI prompts, AI responses, or local diagnostics content to RevenueCat.

RevenueCat acts as a service provider for purchase and entitlement infrastructure. RevenueCat's privacy practices are described at https://www.revenuecat.com/privacy.

For App Store privacy disclosures, RevenueCat purchase handling should be treated as purchase history collection for app functionality and subscription reporting, not tracking.

MemoryOS does not use RevenueCat customer attributes to send your name, email address, phone number, or memory content to RevenueCat unless a future version clearly adds an account or support feature and this policy is updated.

Legal page website logs

When you visit the public legal pages at pysagor.com, the website host or content delivery network may process standard web request logs such as IP address, browser user agent, requested URL, referrer, timestamp, and basic security diagnostics. The legal pages also load Vercel Web Analytics through the global site layout; Vercel states that Web Analytics stores anonymized data and does not use cookies. These logs and analytics are used for security, abuse prevention, reliability, traffic measurement, and delivery of the legal pages. They are not used by MemoryOS for advertising or cross-app tracking.

Future analytics and diagnostics

MemoryOS does not currently include product analytics or crash-reporting SDKs such as PostHog, Sentry, or Mixpanel. If MemoryOS adds analytics or crash diagnostics in a future release, this Privacy Policy and the App Store privacy disclosures must be updated before that release ships.

Any future analytics or diagnostics implementation must be configured not to send raw captures, source files, wiki Markdown, search content, AI prompts, or AI responses as event payloads.

Data MemoryOS does not collect

In the current release, MemoryOS does not collect or use:

• Third-party product analytics events or crash reports.
• Advertising identifiers.
• Tracking data across apps or websites.
• Third-party advertising SDK data.
• Contact lists.
• Precise location.
• Health data.
• Browser history.
• Hidden or background voice recordings.
• Remote web crawling or automatic remote web metadata fetching.
• Third-party cloud LLM prompts or responses.
• MemoryOS server accounts or MemoryOS-hosted user profiles.

Share Extension

The MemoryOS Share Extension lets you send supported content from other apps into MemoryOS. The Share Extension writes a local handoff package into the App Group container. It does not use RevenueCat, StoreKit, Apple Intelligence, CloudKit sync, analytics, or network upload.

Permissions

MemoryOS may request permissions only when needed for app features:

• Microphone access is used for manual voice capture that you explicitly start.
• Photo, file, document, and share access are used only for content you choose to import or share into MemoryOS.
• iCloud access is used for private sync when supported and enabled.

Delete and retention

Local MemoryOS data remains on your device until you delete it, delete the app, or use MemoryOS deletion controls.

MemoryOS includes Delete All Data flows for local app data. When iCloud sync is configured, deletion may also target the configured private iCloud sync zone. If cloud deletion cannot be confirmed immediately, MemoryOS may keep a durable retry intent until deletion can be completed or the issue can be surfaced.

Deleting the app from a device may remove local app data from that device, but it may not remove data already stored in iCloud or retained by Apple or RevenueCat for purchase, billing, tax, fraud prevention, legal, or account purposes. Use in-app deletion controls where available if you want MemoryOS to attempt both local and supported iCloud deletion.

Purchase and subscription records are retained by Apple and RevenueCat according to their own legal, tax, fraud prevention, and service requirements.

Data sharing

MemoryOS shares data only as needed to provide the app and comply with legal obligations:

• Apple may process iCloud sync data, App Store purchase data, subscription data, crash/system data controlled by Apple settings, and Apple Intelligence functionality.
• RevenueCat processes purchase and entitlement data for subscriptions and restore-purchase functionality.
• We may disclose information if required by law, legal process, or to protect rights, safety, and security.

MemoryOS does not sell your memory content.

Security

MemoryOS uses platform security features such as app sandboxing and Apple's private iCloud infrastructure where applicable. No method of storage or transmission is perfectly secure. You are responsible for protecting your device, Apple ID, passcode, iCloud account, and exported files.

Children

MemoryOS is not directed to children under 13. Do not use MemoryOS if you are not old enough to use the app under the laws of your country or region without parent or guardian consent.

International processing

Apple and RevenueCat may process data in countries other than where you live. RevenueCat states that it stores service data on AWS in the United States. Apple and RevenueCat process data according to their own policies and applicable legal safeguards.

Your choices

You can:

• Choose what content to capture or import.
• Avoid enabling iCloud sync if you do not want MemoryOS data synced through iCloud.
• Cancel or manage subscriptions in your Apple ID subscription settings.
• Use Restore Purchases to restore an active subscription entitlement.
• Use MemoryOS deletion controls where available.
• Contact us about privacy requests.

Contact

For privacy questions or requests, contact hello@pysagor.com.

Changes to this policy

We may update this Privacy Policy as MemoryOS changes. If we make material changes, we will update the effective date and publish the new version at:

https://pysagor.com/memoryos/privacy