Memry explains how it handles private household email

Memry collects account and profile information such as your name, email address, timezone, authentication identifiers, notification preferences, and subscription status.

When you forward email into Memry, we may collect sender and recipient details, message subject lines, plain-text or HTML bodies, raw inbound email records, attachment files or attachment metadata, and processing timestamps.

Memry also stores product output and activity records such as AI-generated summaries, extracted events, action items, confidence signals, review edits, billing events, device or push-delivery records when enabled, and audit logs used for security and supportability.

We use account and contact information to authenticate users, operate the dashboard, send digests or summary emails when enabled, process subscriptions, and respond to support, billing, privacy, or deletion requests.

Forwarded email and supported attachment text may be processed to generate summaries, categories, urgency, event suggestions, and action items. Memry is designed to keep raw inbound email separate from structured AI output where possible.

We also use operational metadata and audit logs to troubleshoot failures, protect the service, investigate abuse, and replay failed message processing when needed.

Memry offers an optional Google Calendar connection. You choose whether to connect it, you are shown the specific permissions before granting access, and you can disconnect at any time. Forwarding email into Memry does not connect Memry to your Gmail account or grant Memry access to Gmail APIs.

Google Calendar. When you connect Google Calendar, Memry requests permission to view and edit calendar events (calendar.events) and to see the list of calendars you are subscribed to (calendar.calendarlist.readonly). Memry uses these only to create, update, and remove calendar events for items you confirm, and to identify your primary calendar’s name and time zone so events land on the right calendar. Memry does not read the contents of your existing calendar events.

Google data accessed and derived. The raw Google data Memry accesses is the subscribed-calendar list metadata needed for destination selection and the identifiers, status, and contents of events that Memry itself creates or manages. Derived records include the selected destination calendar, Memry-to-Google event mapping, and synchronization status. Memry does not create aggregated or anonymized datasets from Google API user data.

Use and transfer. Memry uses this raw and derived Google data only to provide, maintain, secure, troubleshoot, and improve the Google Calendar integration described above. It is processed by Memry and its hosting and infrastructure providers only as necessary to operate that feature. Memry does not sell it, use it for advertising, credit or lending decisions, or transfer it to data brokers, advertisers, or other unrelated third parties.

Protection. Google OAuth tokens and integration records are protected in transit using TLS and at rest in encrypted, access-controlled infrastructure. Memry limits production access by role, requests only the scopes needed for Calendar synchronization, and uses audit and operational records to detect and investigate failures or abuse.

Retention and deletion. OAuth tokens and integration metadata are retained while Calendar is connected and as needed for security and operational records. Disconnecting Calendar revokes the Google refresh token when possible and removes locally stored access and refresh tokens. Account deletion removes or de-identifies remaining integration records subject to the limited legal, security, backup, and operational exceptions described below.

AI and machine learning. Memry does not use raw or derived Google Workspace API user data to develop, improve, or train any general or shared AI or machine-learning model. Memry does not transfer Google Workspace API user data to a third-party AI provider for model training. The optional Calendar integration does not send Google API responses to Memry’s AI processors.

You can disconnect the Calendar integration at any time from Memry’s settings, or revoke Memry’s access directly at myaccount.google.com/permissions. Disconnecting stops further access; information already processed is handled under the Retention and deletion section below.

Memry’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Memry uses Google user data only to provide and improve the features you connected, does not transfer or sell that data for advertising, and does not let humans read it except with your consent, for security or to comply with the law, or as strictly necessary to operate the service.

Memry relies on third-party infrastructure and service providers to run the product. In this environment, that includes:

• Amazon Web Services: Hosting, storage, authentication, inbound email delivery, background queues, and operational infrastructure.
• Local development auth fallback: Development-only authentication path for local or test environments.

Memry uses a small number of strictly-necessary cookies to keep you signed in, protect forms against cross-site request forgery, and remember preferences you set while using the product. These cookies are required to operate the service and cannot be disabled without breaking sign-in.

Memry does not set advertising cookies and does not sell or share cookie data with ad networks. Because only strictly-necessary cookies are used, no cookie consent banner is presented. If that changes in the future, this page will be updated before any non-essential cookie is set.

Questions about this Privacy Policy can be sent to support@projectmemry.com. Memry is operated by Hasmita LLC.