Security & privacy
Privacy
policy.
What we collect, how we use it, and the choices you have. The full picture of how #memory handles your information.
This Privacy Policy explains how Recall Innovations Inc. ("we," "us," or "our") collects, uses, and protects your information when you use the #memory applications on iOS, iPadOS, Android, macOS, and Windows ("the App") and visit www.usememory.com ("the Site"). We are committed to protecting your privacy and being transparent about our data practices. Recall Innovations LTD distributes the apps through Apple’s App Store, Google Play, and Microsoft Store; Recall Innovations Inc. is its parent company.
1. Information We Collect
Information you provide
- Account information: when you sign in with Apple or Google, we receive your name and email address from your identity provider. We use these to create and manage your account.
- Purchases and subscriptions: when you make a supported purchase, we process purchase-verification and entitlement information to provide paid features. Depending on the purchase route, this can include transaction identifiers, the product, purchase and expiry dates, renewal or refund status, price and currency, and the #memory account associated with the purchase. The billing provider handles your payment details; we do not receive your full payment-card number from app-store purchases.
- Memories: the notes, keywords, and attachments (photos, videos, files, links, voice recordings, and, if you add one, a location) you create in the App or send to it through the share sheet or Siri. These are your content and are stored to provide the service.
- Sharing data: when you share, we process your display name, your public @handle, the share links and tokens you create, the email addresses of people you invite, group and channel membership, and the copies of shared memories held by recipients. People you share with see your display name, and anyone opening a public link or channel sees your public @handle; they do not see your email address. Members of a group see each other’s display names. The email address of someone you invite is visible only to you, the person who sent the invitation; someone else who opens that invitation link while signed in to a different account sees only a masked form of it. A public channel’s record, including its owner’s display name and @handle, is readable by any signed-in user.
- Assistants you connect: if you connect an assistant, we store the connection, approved permissions, optional keyword limits, credential records, and expiry and revocation status to provide and secure that access. You choose whether it may read, save, or delete eligible memories. The assistant receives permitted content when its connection is used; its provider handles that information under its own policies. You can revoke access in your account, but revocation cannot remove copies already received by the provider. OAuth connections expire after 30 days unless you connect again. Personal access keys remain active until revoked.
- Connected cloud accounts: if you connect Dropbox to link files into memories, we store the access token Dropbox issues and the email address of the connected account. We use the token to fetch the files you link and, when you share a memory that links a Dropbox file, to add recipients as members of that file in Dropbox, to create a Dropbox shared link for a public share, and to copy the file into our own storage so recipients keep access. We revoke the grants created under your connection and delete the token when you disconnect or delete your account; a grant another group member created for their own file is not revoked when a member is removed and lasts until that member’s share ends.
- Email address: when you sign up for the waitlist on the Site, or when you sign in to the App. Both add your address to our product-updates list; every such email includes an unsubscribe link.
- Email engagement: our email delivery provider uses a small remote image and tracked links to record message opens and link requests. These requests can include IP address and email-client information. We use aggregate provider statistics and message-linked campaign clicks to diagnose delivery and evaluate onboarding. Automatic image loading and security scanners can produce these signals, so they do not establish that a person read a message. Website analytics preferences do not control tracking inside an email.
- Beta enrollment: when you join the beta on the Site, we store your email address, chosen platform, referral source and campaign, and the state of your invitation and install, and pass your email address to Apple (TestFlight) or Google (a beta distribution group) to deliver the build.
- Contact messages: the name, email address, and message you submit through the contact form are emailed to our support mailbox and kept there as long as needed to respond.
Information collected automatically
- Usage analytics: we collect events such as app launches, feature usage (e.g. creating or recalling memories, search queries, onboarding steps), screen views, and interaction patterns. These events are associated with your account when you are signed in. We use analytics to understand how the App is used and to improve the experience.
- Device information: app version, build number, and operating system (such as iOS, Android, macOS, or Windows) may be included with analytics events.
- Optional iOS campaign measurement: when available, you can enable Campaign measurement in the App's Settings to let AppsFlyer measure installs and app opens. It is off by default. AppsFlyer receives app and device identifiers, device model, app version, operating system, installation and event timestamps, Wi-Fi status and network information including IP address. It may derive approximate regional location from that IP address. This integration uses the SDK without Apple's advertising identifier (IDFA), does not receive your memories or account details, and blocks sharing with advertising partners. Turning it off stops future measurement; it does not delete information already received.
- Device identifiers: a device-level install identifier is generated by our analytics provider and used to associate pre-sign-in activity with your account after you sign in.
- IP address: collected by our service providers with API requests and analytics events.
- Diagnostic logs: when enabled for your account, the App may send diagnostic logs, together with your account email, to a logging server we operate with a hosting provider, to help us identify and fix issues. These logs include your device model, platform, app version, and technical event data. Diagnostic logging is not enabled by default and does not include the content of your memories.
- Website analytics: if you accept analytics on our public website pages, Google Tag Manager loads Google Analytics 4 and Microsoft Clarity. Google Analytics reports visits, campaign labels, download-link clicks, and successful new mailing-list submissions. Clarity provides heatmaps and session recordings of public page interactions, with text masked. These services may receive browser and device details and set analytics cookies. They are excluded from account, authorization, administration, and shared-memory pages. You can decline or withdraw permission using here in the privacy policy. Separately, for A/B testing and page statistics the Site derives an identifier from stable properties of your browser (screen size, timezone, platform, hardware, and a canvas rendering test) plus a per-visit suffix, keeps it in your browser’s session storage, and sends it to us with your IP address, user agent, the page and referrer, and the action taken (variant shown, scrolling, demo interactions such as typing, saving, and recalling, taps on download links, and blog reads). Our own website event tracking excludes note text, search text, email addresses, and filenames. Older events may contain some of these fields and follow the retention practices below. We store those events, and the stable part of the identifier lets us recognize the same device across visits. Opening a shared memory or channel page also sets a first-party cookie (
ms_vid) for one year that we record with the open and with later actions by the same visitor.
2. How Your Data Is Stored
Offline-first architecture
The App is designed to work offline first. Your memories are stored locally in the App’s database on your device and are available even without an internet connection. The interactive demo on some versions of the Site’s homepage keeps what you type in your browser’s local storage on that computer, unencrypted, until you clear the site data; it is not sent to us unless you sign in there, after which it syncs to your account.
Cloud sync
When you are signed in and connected to the internet, your memories are synced to our cloud infrastructure so they are backed up and accessible across your devices. Sync is handled through a hosted sync service, which maintains a real-time connection between your local database and our cloud database.
Attachments
Photos, videos, files, and voice recordings you attach are uploaded to object storage at our content-storage provider under long, unguessable keys derived from your account and memory. Attachments are delivered through direct content-network URLs that are not signed and do not expire, so anyone in possession of such a URL can retrieve the file until the attachment is deleted, including after a share has been stopped; if the stored file’s removal fails when you delete an attachment, its URL may keep working until we remove it. Files linked from a connected cloud account stay in that account and are fetched on demand, except where we copy them into our storage to keep a share working (see Connected cloud accounts).
Siri and Spotlight
On supported Apple systems the App keeps an on-device index of your memories for Siri and Spotlight. That index never leaves your device. Requests you make to Siri are processed by Apple under Apple’s privacy terms.
Authentication credentials
We use authentication tokens to manage your signed-in session. Token storage and session handling depend on the App, operating system, or browser you use.
3. How We Use Your Information
- Providing the service: to store, sync, and display your memories across your devices.
- Account management: to authenticate you, manage your session, and link your data across devices.
- Paid access: to verify purchases, manage access to paid features, respond to billing questions, and handle renewal, refund, or revocation updates from the billing provider.
- Sharing: to deliver the memories, links, invitations, groups, and channels you choose to share to the people you choose, and to let you stop them.
- Analytics and improvement: to understand how the App and Site are used, measure feature adoption, run A/B tests, and improve the user experience.
- Attribution: to connect your pre-sign-up activity (such as waitlist signups) with your account after you sign in, so we can measure the effectiveness of our outreach.
- Communications: to send you confirmation emails, the invitations you ask us to send, and product updates (you are added to that list when you create an account or join the waitlist, and can unsubscribe at any time).
- Security: to detect abuse, prevent fraud, and maintain the integrity of our services.
4. Service Providers
We use service providers to help operate the App and Site, including providers that process information on our behalf under contractual obligations. Sign-in providers and app stores also process information for their own services under their own privacy policies:
- Authentication, database hosting, and data synchronization: the services that hold your account and memories and keep your devices in sync.
- Content storage and delivery: object storage and a content delivery network for attachments.
- Product analytics (EU-hosted): usage analytics and feature flags in the App.
- Google: Google Tag Manager deploys website tags and Google Analytics provides visit and campaign statistics after you accept analytics.
- Microsoft Clarity: heatmaps and masked session recordings of public website interactions after you accept analytics.
- AppsFlyer: optional iOS install and app-open campaign measurement after you enable Campaign measurement in the App's Settings. This is separate from website analytics preferences and product analytics.
- Former internal AI assistant: we previously used a third-party model provider for an internal usage assistant, which could receive analytics events, account names and emails, keywords, and short previews of memory content under API terms that exclude model training. That assistant has been removed and no longer sends data to the provider. Its removal does not itself delete previously processed data.
- Dropbox: only if you connect it, to fetch the files you link into memories.
- Hosting: hosting for the Site and our diagnostic-log server.
- Apple and Google: sign-in providers; Apple also processes Siri requests and TestFlight beta delivery, and Google also hosts a beta distribution group.
- Email delivery: a transactional email service for confirmations, invitations, and updates.
App stores and billing providers. Apple’s App Store, Google Play, and Microsoft Store distribute the apps and handle store-account, download, and purchase information for their services. Where a store bills you, it processes the payment and may provide purchase-verification or subscription-status information used to provide paid access. Their own handling and retention of information are described in the Apple Privacy Policy, Google Privacy Policy, and Microsoft Privacy Statement. Deleting your #memory account does not delete your store account or the store’s purchase records, or cancel a subscription. See our subscription and cancellation guidance.
We do not sell, rent, or share your personal information with third parties for their own marketing or advertising purposes.
Legal disclosure
We may disclose personal information if we believe in good faith that disclosure is reasonably necessary to satisfy applicable law, regulation, legal process, or an enforceable governmental request; to enforce our Terms of Service, including investigating potential violations; or to detect, prevent, or address fraud, abuse, or security issues. Where the law allows, we will tell you before disclosing your data in response to such a request.
5. Cookies and Tracking Technologies
The App
The App does not use cookies. Analytics are provided by our analytics service using a device-level identifier. Optional iOS campaign measurement uses AppsFlyer only after you enable it in Settings. Its SDK does not collect IDFA, and sharing with advertising partners is blocked in this integration.
The Site
We use a first-party cookie to remember UI preferences and, on shared-memory and channel pages, the one-year ms_vidvisitor cookie described in section 1. If you accept website analytics, Google Analytics and Microsoft Clarity may set analytics cookies. We store your analytics choice in local storage. You can change it using Analytics preferences; withdrawing consent stops future collection by these website tags, but does not itself delete previously collected information or existing cookies. We do not use third-party advertising cookies. For A/B testing and page statistics we use the browser-derived identifier described in section 1; its local copy lives in session storage and is cleared when you close your browser, while the events we received are retained as analytics data. It is not used to track you across other websites.
6. Data Retention
- Memories and account data: retained for as long as your account is active. If you delete your account, your data is removed from our servers.
- Local data: memories stored on your device persist until you delete them or uninstall the App.
- Shared content: Copy links expire 14 days after they are created and cannot be stopped earlier; Public links, invitations, groups, and channels last until you stop or withdraw them or delete your account. When a share ends (you stop it, withdraw it, remove a member, or a member leaves), whatever each recipient had received becomes an ordinary memory in that recipient’s account, attachments included, and remains there; the same applies to copies recipients saved while the share was live.
- Connected cloud tokens: kept until you disconnect the account or delete your account.
- App analytics data: retained for up to 24 months, then deleted.
- Website events (including the browser-derived identifier, IP address, and user agent): not yet deleted on a schedule; kept until we clear them.
- Diagnostic logs: deleted after a short period, currently 60 days.
- Email addresses (product updates and waitlist): after you unsubscribe we stop emailing you immediately and keep the address as a suppression record so you are not emailed again; the mailing-list record is removed when you delete your account.
- Website session storage: the local copy of the browser-derived identifier lasts only for your browser session and is cleared when you close your browser.
7. Data Security
We implement appropriate technical and organizational measures to protect your personal information, including:
- HTTPS with Transport Layer Security (TLS) encrypts connections between your device and our services, helping protect your notes, keywords, and attachments from being read or changed in transit.
- Authentication tokens and session controls to limit access to signed-in accounts.
- Row-level security on our cloud database, limiting each account to its own data plus content shared with it.
- Secure database access controls and password-protected administrative interfaces.
We use information to provide and maintain #memory. We may need to access relevant account information and memory content to resolve a support request, investigate suspected abuse or a security incident, or meet a legal obligation. Information is also used for the communications and service analysis described in sections 3 and 4. Access is limited to the relevant purpose and is subject to applicable data-protection law and confidentiality obligations.
8. Your Rights
Depending on your location, you may have the following rights regarding your personal data:
All users
- Access: request a copy of the personal data we hold about you.
- Deletion: delete your account from Settings in the App or at usememory.com/delete-account. This removes your memories, attachments, shares, invitations, memberships, and connected-cloud tokens from our servers.
- Correction: request that we correct inaccurate data.
- Data export: your memories are always accessible on your device. You can share individual memories from within the App.
- Unsubscribe: opt out of marketing emails at any time via the unsubscribe link in each email.
European Economic Area, UK, and Switzerland (GDPR)
If you are in the EEA, UK, or Switzerland, our legal bases for processing your data are:
- Contract performance: processing necessary to provide the #memory service (storing and syncing your memories).
- Consent: when you voluntarily provide your email address for the waitlist or sign in to the App. Optional iOS campaign measurement also relies on your consent when you enable Campaign measurement in Settings. Turning it off withdraws that consent for future collection without affecting your use of the App or the processing already performed.
- Legitimate interest: for product analytics and product improvement, balanced against your privacy rights.
You also have the right to data portability, restrict processing, and lodge a complaint with your local data protection authority.
California (CCPA/CPRA)
If you are a California resident, you have the right to:
- Know what personal information we collect and how it is used.
- Request deletion of your personal information.
- Opt out of the sale or sharing of personal information. We do not sell your data.
- Non-discrimination for exercising your privacy rights.
Canada (PIPEDA)
Canadian users may access, correct, or request deletion of their personal information by contacting us.
9. International Data Transfers
Your data may be transferred to and processed in the United States and other countries where our service providers operate. Our product-analytics provider operates from the EU. When we transfer data outside your region, we ensure appropriate safeguards are in place, including standard contractual clauses where required.
10. Children’s Privacy
The App and Site are not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have collected data from a child under 13, please contact us and we will promptly delete it.
11. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by updating the "Last updated" date at the top of this page and, where appropriate, through the App or by email. We encourage you to review this policy periodically.
12. Contact Us
If you have questions about this Privacy Policy or want to exercise your privacy rights, contact us at:
Recall Innovations Inc.
Email: admin@usememory.com
Let’s keep it clear
Privacy deserves
a straight answer.
Have a question about your information or your choices? We’re here to help.
Talk to us