Privacy Policy
Last updated: November 5, 2026
Memova is provided by MEMOVA LLC. Memova helps users capture, transcribe, organize, and understand information from conversations, notes, recordings, images, PDFs, documents, and other materials they choose to provide.
We design Memova with privacy in mind. Our goal is to process your information only to provide the features you choose to use, give you meaningful control over your content, and be transparent about how information is handled.
1. Categories of Information Collected
We collect information that you choose to provide or that is necessary to provide Memova.
User-Provided Content
Depending on how you use the app, this may include:
- Audio captured during conversations, meetings, consultations, interviews, or personal note-taking
- Speech from you and other participants, such as mentors, colleagues, healthcare providers, legal or financial advisors, managers, clients, or peers
- Transcripts generated from audio
- Heart rate and heart rate variability (HRV, measured as SDNN) read from Apple Health through HealthKit when you grant the relevant permission, and related health context used as described in Section 11
- Notes, edits, tags, prompts, questions, and instructions you enter
- Photos, screenshots, PDFs, documents, and other files you upload
- Summaries, extracted information, answers, drafts, and other AI-generated outputs
- Information you save, organize, search, or ask the app to use as context
- Information you authorize Memova or a connected agent to retrieve from selected services, workspaces, repositories, or accounts
- Personal Manual, HTML Page, Living Book, email, calendar, and other outputs created from the context you choose
Account and Transaction Information
If you create an account or purchase a subscription, we may collect:
- Name, email address, login information, and account settings
- Account identifiers, authentication information, and authorized basic profile information returned by the third-party sign-in provider you choose
- Subscription status and billing-related information
- Payment information processed by our payment providers
- Customer support communications
- Email addresses and communication preferences you provide when you join an early-access list, request updates, or contact us through the website
Technical and Usage Information
We may collect limited technical information necessary to provide, secure, and operate Memova, such as:
- Device type, operating system, app version, and language settings
- Diagnostics, crash reports, and performance data
- Network connection information, approximate location derived from it, and log data
- Cookies or similar technologies if you use our website or web-based services
Website Analytics and Cookies
We use Google Analytics 4, with measurement ID G-9YJQ994J98, to understand how people find and use our public website and whether iOS early-access journeys are useful. Google Analytics may process page URLs and titles, referral information, interaction events, browser and device information, approximate location derived from connection information, and cookie or consent status. We do not send the private notes, recordings, transcripts, documents, or agent memory you provide to Memova as analytics event content.
Advertising storage, advertising user data, and ad personalization are disabled in our Google tag configuration. Where consent is required, analytics storage defaults to denied until you allow it. Our website provides an Analytics privacy choices panel where you can allow or reject analytics. After making a choice, use the persistent Privacy choices button to change or withdraw that choice at any time.
We use analytics information to measure website performance, diagnose navigation problems, understand acquisition sources, and improve the public iOS early-access funnel. Google acts as an analytics service provider and may process data in countries other than your own. Analytics retention is controlled through our Google Analytics property settings; aggregated reports may be retained longer than event-level data. You may contact hello@memova.ai with questions or requests about website analytics.
2. Audio and Recording Data
You may record on iPhone or Apple Watch. Recording and transcription take place on your device and support offline use. Original audio may be retained for playback under your cleanup setting and the app-managed original-audio limit in Section 12.
Original recordings and voiceprint models remain on your device and are not uploaded to Memova or its cloud providers. The recording content submitted for cloud analysis is limited to transcript text and textual context you authorize; the original audio is not submitted. Health measurements require the separate permission described in Section 11.
Local transcript text enters cloud processing only when you choose and authorize the processing described in Section 6. Recording, saving locally, or granting microphone permission does not by itself provide that authorization. Recordings a feature allows you to retain locally are managed on your device.
3. Files and Documents
When you upload photos, PDFs, documents, or other files, we process them only to provide the features you request. This may include extracting text, identifying relevant information, creating summaries, answering questions, or generating new content based on the materials you provide.
You should only upload files that you have the right to use, process, and store.
4. AI Features
Memova uses AI to support transcription, meeting identification and summaries, hour notes, My Day daily recaps, Spark exploration and creation, Ask Memova, and related pages and illustrations. Other features may extract information, organize documents, draft content, or connect saved context using the material you provide.
Cloud features involve Memova and providers of the capabilities needed to complete the task. Microsoft Azure AI services provide relevant cloud AI capabilities. Depending on the feature and your authorization, processing may include transcript text, notes, questions, images, attachments, relevant conversation history, cited material, recording markers, timestamps, speaker information, and generated outputs. Health measurements are handled separately under Section 11. Before personal information is submitted to a third-party AI service, we explain the data scope, recipient, and purpose and obtain the relevant permission.
Speech transcription is performed on your device. Cloud model inference and content generation process the material authorized for the task. We do not use your private recordings, transcripts, notes, conversations, or generated content for advertising or to train general-purpose AI models. Providers acting for us may process content only as necessary for the relevant feature, not for their own advertising, general-purpose model training, or unrelated purposes. These use restrictions do not mean content never passes through the cloud or that all temporary material, response records, security logs, or other copies are erased immediately after processing. Section 12 describes the relevant retention rules.
AI may generate a Personal Manual, page, or proposed action from the context you choose. These outputs remain subject to your review. Generation alone does not authorize publishing content, sending email, or creating or changing calendar events.
AI outputs may be incomplete, inaccurate, or unsuitable for your circumstances. Verify them before relying on them, particularly for medical, legal, financial, employment, education, or other high-impact matters. Consider the recording context and actual content when deciding whether cloud processing is appropriate.
5. Use of Information
We use your information only to provide Memova and the features you choose to use.
This includes using your information to:
- Record and transcribe audio on your device when you choose to use recording or transcription features
- Generate transcripts, summaries, answers, drafts, structured notes, and other outputs you request
- Analyze uploaded photos, PDFs, documents, and other files when you choose to upload them
- Store, organize, search, and retrieve your content for your use
- Use your saved context to answer your questions or generate content at your request
- Connect information across sources you choose and generate Personal Manuals, HTML Pages, Living Books, and proposed actions
- Sync or back up your content if you enable those features
- Provide account access, customer support, billing, and subscription management
- Maintain the security and basic functionality of Memova
- Comply with applicable laws and enforce our terms
We do not use your private content for advertising or to train general-purpose AI models.
6. Local-First Design and Cloud Processing
Memova uses a local-first design. Where possible, content is processed and stored on your device. On-device storage, cloud task processing, and local display of generated results are separate stages.
Initial Privacy Notice and Consent
Upon initial use of the application, the complete local and cloud privacy notice is presented as the first step, with the complete Privacy Policy available for review. The notice describes content storage, the conditions for transmission outside the device, the parties responsible for processing, and your available choices. Agreement to the notice and Privacy Policy is required before entering the Apple Watch connection process. If you do not agree at that time, you do not enter that process.
Consent at this stage applies to the basic privacy notice and this policy. It does not enable cloud AI or authorize sharing your records or Apple Health measurements with a third party. Reading or acknowledging the notice, continuing setup, registering, or creating an account does not grant cloud processing permission. Recording, saving locally, purchasing a subscription, or granting microphone, file, health-data, or other device permissions also does not authorize third-party AI sharing. Use of cloud AI requires the relevant permission for the feature's data scope, recipient, purpose, and mode. Cloud sharing of health measurements requires the separate permission described in Section 11.
Local Features and Account Requirements
After agreement to the basic privacy notice and completion of Watch connection and setup, local recording, local transcription, and offline search are available free of charge without an account or subscription. Account registration is optional and serves account-based features. Local use does not require cloud AI. Separate account, payment, or support services may still process information needed for those services.
Stopping cloud use or switching to local mode does not automatically withdraw material previously submitted to the cloud or a provider, or delete existing cloud information. Existing tasks are governed by the applicable feature cancellation rules. Stopping future automatic processing, canceling a task, and deleting content have different effects.
Cloud Processing Scope
Cloud processing may support synchronization, backup, accounts, customer support, payments, AI processing, or cross-device access. Depending on the feature, Memova and its providers may supply cloud infrastructure, object storage, or model inference and process the necessary authorized text, images, documents, context, or generated results. Original recordings and voiceprint models remain on your device as described in Section 2. Microsoft Azure AI services provide the relevant AI capabilities. Section 4 describes the data categories, and Section 12 covers retention.
Cloud features require an account and network connection. Feature availability, version support, and subscription requirements follow the in-app description. The actual scope of a request depends on the feature, the material submitted or cited, and your authorization.
Microsoft Cloud Services: Purposes and Information
Microsoft provides the following cloud capabilities used according to the feature, actual support, and your authorized task. This does not mean every request uses all services or sends every data category; some features may also use other providers.
- Azure Container Apps — Purpose: Backend interfaces, background processing, and scheduled tasks. Data involved: Content required by the feature, business requests, and task status.
- Azure Database for PostgreSQL Flexible Server — Purpose: Structured business records, processing status, and retrieval metadata. Data involved: Account permissions, meeting notes, transcripts, tasks, and retrieval vectors.
- Azure Blob Storage — Purpose: Storage of uploaded material and certain saved outputs. Data involved: Authorized text, images, attachments, project material, some generated files, and knowledge-base content.
- Azure Cache for Redis — Purpose: Task queues, caching, short-lived status, and temporary computation. Data involved: Queue information, cached material, temporary state, and computation data.
- Azure AI model services — Purpose: Summaries, questions and answers, generation, and text-vector retrieval. Data involved: Necessary text, images, context, generated results, and retrieval vectors.
- Azure AI Document Intelligence — Purpose: Text and layout extraction from images, scans, and supported documents. Data involved: Submitted material and extracted text or layout.
- Azure AI Content Understanding — Purpose: Analysis and extraction for actually supported and submitted project material. Data involved: The relevant project material and extracted results.
- Azure Translator — Purpose: Language conversion in the relevant translation paths. Data involved: Text to translate and translated results.
- Azure Key Vault — Purpose: Management of backend access credentials and sensitive configuration. Data involved: Service credentials for databases, storage, AI services, and related integrations.
- Azure Monitor and Log Analytics — Purpose: Operational monitoring, log queries, and anomaly alerts. Data involved: Request status, operational metrics, and necessary diagnostic logs.
- Azure Communication Services Email — Purpose: Delivery of login verification-code email. Data involved: Recipient email address, verification email content, and sending status.
- Azure Container Registry — Purpose: Storage of application images for backend operation and release. Data involved: Application software and build artifacts.
Microsoft Azure provides infrastructure and cloud processing capabilities. Memova is responsible for in-app account permissions, content ownership, processing flows, and business-data management. Azure Key Vault manages backend credentials and sensitive configuration; it does not establish user-exclusive at-rest encryption keys. Microsoft manages the at-rest keys for the main file storage and database described above.
Business storage, temporary computation, provider response records, and security logs may have different retention periods. Use of a particular service does not expand your authorized task or imply immediate deletion of every provider copy.
Manual Cloud Processing
In manual mode, you select the relevant feature's submission scope and use the Upload action or other applicable confirmation to submit it. Entering a selection interface, reading the notice, or canceling selection does not submit content. For hour-based organization, the selection unit is a particular date and recording period, rather than all records by default.
Question-and-answer or continuous conversation features may also process relevant history from the current conversation and material you have cited to understand the request and generate an answer. Manual submission therefore does not mean a request contains only the latest sentence. Such context remains limited to the feature and processing scope you authorize.
Automatic Cloud Processing
In Memova Watch automatic cloud mode, the authorized scope includes completed local transcript text already available on the day the mode is enabled and transcript text completed later that day. The setting continues for each subsequent day's transcript text and does not automatically backfill earlier dates. Once enabled and authorized, processing continues within that scope without a manual upload for each transcript.
My Day recaps and To explore content update after the end of your configured Working time, based on authorized and available material. The corresponding daily recap is not generated, and these ideas are not automatically displayed, before that time. Working time is adjustable and separate from the Watch recording schedule. Before it ends, you may still enter a Custom record and initiate Spark.
You may disable automatic mode or switch to local mode to stop the relevant features from initiating subsequent automatic processing. Previously submitted material is not automatically withdrawn, and existing tasks remain subject to the applicable cancellation rules. Section 12 describes deletion of saved cloud content.
Cloud Outputs for Individual Meeting Records
Choosing cloud generation for an individual Meeting Note may authorize its completed local transcript and original notes to be processed together as one task to generate a title, highlights, summary, and meeting page. This choice is available in either mode. Viewing a generated result on your device does not establish that generation occurred entirely on-device. In-app viewing and web-link access may use different mechanisms. Access scope depends on the feature and link type, including valid-link access for some older pages described in Section 18.
Local and cloud choices do not replace the recording and content-use responsibilities in Section 10 or the health permission described in Section 11.
7. Information Sharing
We do not sell personal information. We may share information in the following limited circumstances.
Service Providers
We may use providers of hosting, cloud infrastructure, object storage, AI inference, payments, customer support, security, and similar capabilities. Microsoft Azure AI services provide relevant AI capabilities. Depending on the feature and authorization, providers may receive text, images, documents, related context, or generated results. Original recordings and voiceprint models are not uploaded.
Providers may process content only as necessary for the relevant service, not for their own advertising, general-purpose model training, or unrelated purposes. We require third parties with access to personal information we share to provide the same or an equal level of protection as stated in this policy and required by applicable requirements. Memova business records and temporary content, response records, or security logs created during provider processing may follow different retention rules, as described in Section 12.
User-Directed Sharing
If you publish a page, share a Personal Manual or Living Book, export content, or send content through a connected service, we process and disclose selected content as necessary to carry out your instruction. Page access mechanisms differ across versions and features. Some older meeting pages are accessible without sign-in to anyone holding a valid link. Review the content and access mechanism before sharing or forwarding a link; Section 18 provides further information.
Legal and Safety Grounds
We may disclose information where we reasonably consider it necessary to:
- Comply with applicable law, regulation, legal process, or government requirements
- Protect the rights and safety of users, MEMOVA LLC, or others
- Detect, prevent, or address fraud, abuse, security, or technical issues
- Enforce our terms and policies
8. Restrictions on Information Use
We do not sell personal information or use private recordings, conversations, transcripts, notes, uploaded files, or generated results for advertising or to train general-purpose AI models.
These use restrictions are distinct from cloud processing needed to provide a feature. They do not mean that content never passes through the cloud or that all copies are erased immediately after processing. Cloud processing, temporary storage, saved business outputs, and provider retention follow their respective rules.
Recordings are transcribed locally. Original recordings and voiceprint models remain on your device and are not uploaded to cloud services, as described in Section 2.
9. User Choices and Controls
In Memova Watch, you may decline cloud AI permission and continue using local recording, local transcription, and offline search free of charge. Agreement to the initial privacy notice and policy does not remove that choice. Cloud processing requires the relevant authorization. Stopping cloud use does not automatically withdraw previously submitted content or delete existing information. Existing tasks follow the applicable cancellation rules.
Depending on the app version and settings, available controls may include:
- Deleting transcripts, notes, files, summaries, and generated content
- Editing or removing extracted information
- Managing microphone, photo, file, notification, and other device permissions
- Disabling synchronization, backup, or cloud features where available
- Switching between local, manual cloud, and automatic cloud modes and managing health-data reading permission and local association
- Reviewing proposed email, calendar, page, or other actions before execution or sharing
- Disconnecting integrations, revoking tool authorization, or managing connected services
- Changing or withdrawing website analytics choices through Privacy choices where available
- Exporting content where supported
- Requesting account deletion, which may require renewed identity verification and account confirmation
- Requesting access, correction, deletion, or a portable copy of personal information
Stopping new tasks, canceling a task, deleting content, revoking a share, and deleting an account have different scopes and do not substitute for one another. Send privacy requests to hello@memova.ai.
10. Recording Consent and Use Responsibilities
You are responsible for using Memova in compliance with applicable laws and professional obligations.
Laws about recording, transcription, consent, and monitoring vary by location and context. In some cases, you may need to notify or obtain consent from other participants before recording, transcribing, summarizing, or analyzing a conversation.
This is especially important for conversations involving healthcare, legal, financial, employment, education, or other sensitive or regulated contexts.
11. Sensitive Information
Your content may include sensitive information, such as health information, legal matters, financial details, employment information, educational records, personal relationships, or information about other people.
When recording conversations or uploading files containing sensitive information, you should assess the relevant content carefully. Sensitive information should be submitted only where necessary for your use of the application and where you have the right to provide it.
Memova Watch can read heart rate and HRV (SDNN) from Apple Health through HealthKit after you grant permission for each data type. It associates actual measurements with the relevant recording times and speech identified as yours through on-device voiceprint matching. The measurements describe the wearer, not other speakers. Daily averages shown to check reading access do not replace the actual measurements used for an associated passage; missing measurements are not filled with invented readings or baselines.
When health association is enabled and you have given permission for the applicable cloud AI processing, matching measurements may be sent with relevant text through Memova's servers to Microsoft Azure AI services. This supports your own physical and mental wellbeing review by showing health context, surfacing passages related to changes in your own condition, and assisting with interpretations that are presented as inferences. Health measurements do not determine the importance of ordinary meeting topics, work content, or Spark ideas. Heart rate or HRV does not by itself establish a particular emotion or a medical diagnosis. We do not use health information for advertising, marketing, sale, or general-purpose model training.
HealthKit reading permission or a local association setting does not by itself authorize third-party cloud sharing. You can manage reading permissions in Apple Health and turn off local associations in Memova. Turning off local associations stops associations, hides measurements, and clears their local cache without changing the original Apple Health records. The association cache is excluded from the app's iCloud backup. Previously saved cloud content is handled under Section 12. Health information contained in text you choose to provide is not automatically removed when you turn off local association.
Reading or agreeing to the basic privacy explanation at first use, creating an account, or enabling ordinary cloud AI without health data does not authorize cloud sharing of Apple Health measurements. Sending matched heart rate or HRV to cloud AI requires your relevant permission for that health information use, assessed separately from system read permission and the local association setting. Without that health information permission, Apple Health measurements are not added merely because an ordinary cloud mode is enabled. Health information in text you enter or choose to provide is still handled within your authorization for that text; the health measurement setting does not automatically identify or remove health information in text.
12. Retention, Deletion, and Account Closure
App-Managed Original Audio
You can set when the app clears original audio. Original recordings managed by the app are retained for no more than 30 days. This maximum applies only to app-managed original audio, not to voiceprint models, transcripts, notes, summaries, other saved outputs, or logs, which have their own retention rules. It does not delete copies you have exported outside the app. The ordinary backup and background-cleanup provisions in this policy do not extend this in-app original-audio maximum.
Saved Content and Temporary Material
Cloud transcripts, notes, and generated results formally saved for continuing review and use are retained until you manually delete them, subject to applicable legal requirements, account deletion rules, and service availability limitations. Material needed temporarily to execute a task may expire and be cleaned up. Expiry of temporary computation material does not delete the corresponding saved business output.
Task completion, mode changes, disabling local association, signing out, or clearing local cache do not constitute deletion of existing cloud content. Original recordings and voiceprint models remain managed locally within the product scope described in Section 2.
Content Deletion and Background Cleanup
You may delete saved content through the relevant controls. Such content is not moved to a recycle bin. Interface removal, access invalidation, completion of background cleanup, and expiry of backups or other retained copies are separate stages. Some cleanup runs in background tasks and may require retries after storage or network failures. A deletion action does not mean that all online data, caches, logs, backups, and provider copies undergo irreversible physical erasure at the same time.
Deleting a transcript does not automatically delete existing notes, summaries, Personal Manuals, webpages, or other saved content that previously used or cited it. You manage or delete those items separately. If the original transcript or audio has been deleted, reviewing the source text or playing the original recording may no longer be available. Further use of retained content remains subject to the scope you authorize. Copies already downloaded, shared, or delivered to an external service are managed separately. Task cancellation, link revocation, and business-content deletion may also take effect through different mechanisms.
Account Deletion
Memova provides an account deletion request process. To prevent unauthorized deletion, it may require renewed identity verification and confirmation of account information. Once the request is accepted, relevant account access is disabled, related login sessions and tool authorizations are revoked, and associated integration connections stored in Memova are cleared. Cloud data is then handled through background processes.
Acceptance of the request and completion of all cleanup are different states. Background handling may involve several steps. Content and certain billing or security records may be handled differently. Account closure cannot automatically delete copies delivered to other services, downloaded to other devices, or retained by others.
Other Retention and Provider Records
Other personal information is retained only as reasonably necessary to provide services, maintain accounts, meet legal obligations, resolve disputes, enforce agreements, and protect security. Residual information is deleted or de-identified within a reasonable period after deletion. Limited records or copies may remain where required or permitted for legal compliance, security, backup, fraud prevention, or dispute resolution, for no longer than necessary for those purposes.
Memova business records and temporary content, response records, or security logs maintained by cloud providers may have different retention rules. Deletion in Memova does not mean every provider copy is physically erased at the same time. Restrictions on general-purpose model training do not imply an absence of temporary storage or immediate cleanup. Operational logs, business content, and security credentials may have different lifecycles.
Early-access contact information is retained while you remain subscribed or as reasonably necessary to administer the program. You may unsubscribe from marketing updates at any time; limited suppression records may remain to respect your choice.
13. Information Security
Transmission and Cloud Storage Encryption
Client connections to Memova production interfaces use HTTPS/TLS. The main Azure Blob Storage file storage and Azure Database for PostgreSQL business database use Azure-provided AES-256 encryption at rest, with the relevant at-rest encryption keys managed by Microsoft. That file storage requires HTTPS with a minimum TLS version of 1.2; the database requires TLS connections. This specified scope should not be interpreted as identical encryption configuration for every cache, log, or backup. These safeguards work together with authentication and access controls. Memova and relevant providers still process the content required for an authorized task. Transmission and storage encryption do not promise device-exclusive decryption, end-to-end encryption, or an inability of the service providers to access content.
Identity, Content Ownership, and Logical Isolation
We use authentication, content-ownership checks, and access controls to restrict access to protected private meetings, notes, files, and tasks. Signing in does not grant access to another account's content. Relevant resource flows also check workspace membership, authorized scope, credential validity, and whether content is deleted or expired, according to the feature.
Private content belonging to different accounts is logically isolated through these application-layer rules. File downloads have relevant permission checks; some download authorizations expire. Account-based content access, shared links, and temporary download authorization are different access mechanisms. Section 18 describes valid-link access for some older meeting pages.
Operational Logs and Credential Filtering
We record necessary operational information to maintain services, diagnose faults, and investigate anomalies. This may include request identifiers, operation types, processing status, duration, and necessary error diagnostics. We filter recognized access-token, password, and key fields, and authorization credentials in certain links, from logs to reduce accidental recording or exposure of credentials.
Filtering covers the relevant sensitive fields and recognized credential forms. It does not mean that all logs are anonymized or that arbitrary private content is automatically identified and removed. Log retention and cleanup follow Section 12.
We also use reasonable technical, administrative, and organizational safeguards, including access management, secure infrastructure, monitoring, and internal policies. No transmission or storage method can guarantee absolute security.
14. Children’s Privacy
Memova is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, please contact us.
15. International Data Transfers
If you use Memova from outside the country where we or our service providers operate, your information may be processed in countries that may have different data protection laws than your own.
Where required, we use appropriate safeguards for international transfers of personal information.
16. Policy Changes
We may update this Privacy Policy from time to time. If we make material changes, we will update the “Last updated” date above and provide additional notice where required.
17. Third-Party Sign-In and Connected Services
Memova offers Google, Apple, or Microsoft account sign-in through supported clients and sign-in entry points. Third-party sign-in is used to verify your identity, create or link your Memova account, and maintain your signed-in session. We process only the account identifiers and related basic profile information authorized and actually returned by the sign-in provider. Available sign-in methods depend on the client you use.
- Google sign-in. If you choose Google sign-in, we may receive an account identifier and basic profile information, such as your name, email address, and profile image, for sign-in and account linking.
- Sign in with Apple. If you choose Sign in with Apple, we may receive an account identifier returned by Apple and the name and email address you choose to share. If you choose Hide My Email, we may receive an Apple-provided private relay address rather than your personal email address.
- Microsoft sign-in. If you choose Microsoft sign-in, we may receive an account identifier returned by Microsoft and basic profile information, such as your name, username, or email address, depending on the permissions actually granted. The information returned depends on the account and authorization scope; not every sign-in returns every field.
Account sign-in and access to email, calendars, contacts, cloud-drive files, or other account content serve different purposes. Using one of these sign-in methods does not itself authorize access to that content or uploading local recordings, transcripts, or health measurements. Such content is processed only within the explained scope after you choose the relevant feature and grant the applicable permissions.
- Gmail permissions. Memova uses Gmail permissions only if you choose to connect Google Workspace features and confirm a related email action. Depending on the action, Gmail permissions may allow Memova to process email draft content, recipients, subject lines, message bodies, attachments you choose to provide, and related metadata only as needed to help you draft, review, and send emails from within Memova. Memova will not send emails without your authorization and explicit confirmation.
- Google Calendar permissions. Memova uses Google Calendar permissions only if you choose to connect Google Workspace features and confirm a related calendar action. Depending on the action, Google Calendar permissions may allow Memova to read existing calendar availability and event information to help detect scheduling conflicts, avoid duplicate events, show relevant calendar context, and help you create or update calendar events from within Memova. Memova will not create, update, delete, or share calendar events without your authorization and explicit confirmation.
- Use limits for Google user data. We do not use Google user data for advertising, unrelated purposes, or to train generalized AI models. Google user data is used only for the account sign-in you choose and the Google Workspace features you request and confirm. Memova will not automatically send emails or create calendar events without your authorization and explicit confirmation. Sending an email or creating or changing a calendar event requires your permission and a clear user-confirmed action.
- Limited use. Memova’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Service providers. Google user data may be processed by our service providers only as necessary to provide user-requested Memova features, such as authentication, secure infrastructure, AI-assisted drafting, email actions, calendar actions, support, security, and similar services. These providers are not permitted to use Google user data for advertising, general-purpose model training, or unrelated purposes.
- User controls and deletion. You can manage third-party sign-in permissions granted to Memova through the relevant sign-in provider’s account settings, and disconnect Google Workspace authorization through your Google account permissions or Memova settings, where available. Revoking third-party authorization and deleting a Memova account or saved content are different actions; revocation does not automatically delete saved account information or outputs. Contact hello@memova.ai to request deletion or removal of related information, or deletion of your account data.
The sign-in provider’s own privacy rules apply to its handling of information during authentication. Microsoft account sign-in and the Microsoft Azure cloud services described in Section 6 are separate features. Using Azure infrastructure does not automatically authorize Memova to access the content of your Microsoft account.
18. Early Access, Page Access, and Connected Services
Early Access
If you provide an email address for early access or product updates, we use it to administer the program and send requested communications. Unsubscribe through a message link or contact hello@memova.ai.
Meeting Pages and Link Access
In-app viewing and access through a web link may use different mechanisms. Displaying a result on your device does not establish that preceding generation occurred entirely on-device. Review access scope according to the feature, version, and link type.
Some older cloud meeting pages use valid-link access: anyone holding a valid link can view them without signing in. They cannot all be described as accessible only to the account owner or authorized accounts. Check the actual mechanism before forwarding a valid link to sensitive content.
When publishing or sharing a page, Personal Manual, or Living Book, or exporting or sending content, review recipients, link permissions, content, and information about other people. Links can be forwarded. Link revocation, content deletion, and expiry of temporary download authorization may take effect through different mechanisms. Copies already downloaded, copied, or saved elsewhere are not automatically erased from a recipient's device when the original link expires.
Connected Tools, Services, and Revocation
Connectors, plugins, or supported AI tools accessing Memova require valid authorization credentials and are limited by granted scopes. Connecting a tool does not automatically grant all permissions for the account. Reading content, retrieving files, and other controlled operations require the relevant authorization conditions and checks of account ownership, credential status, and content status.
Revoked or expired authorization affects later access using that authorization. It cannot automatically retrieve content already delivered, downloaded, or copied. Retention and use of external copies also depend on the receiving service's rules. Revoke access through the relevant provider or, where supported, Memova settings.
Proposed Actions
Generating a page, email, calendar event, or other proposal does not execute it. External actions require your review and confirmation unless you separately enable and are clearly informed of the applicable automation setting.
19. Regional Privacy Rights
United States
Depending on where you live and whether an applicable state privacy law covers Memova, you may have the right to confirm whether we process your personal information; access, correct, or delete it; receive a portable copy; and opt out of certain sales, sharing, targeted advertising, or profiling. You may also have the right to limit certain uses or disclosures of sensitive personal information and to appeal a decision on your request.
Memova does not sell personal information or share it for cross-context behavioral advertising. We do not use private content for targeted advertising. The categories of information we may collect, the sources from which we collect it, the purposes for which we use it, and the types of service providers to which it may be disclosed are described in Sections 1, 5, and 7. Our retention criteria are described in Section 12.
We may need to verify your identity before completing a request. Where permitted, you may use an authorized agent. We will not discriminate against you for exercising an applicable privacy right. If applicable law gives you a right to appeal our decision, reply to our response or contact hello@memova.ai and state that you are submitting an appeal.
Canada
If Canadian federal or provincial privacy law applies, you may request access to or correction of your personal information, withdraw consent subject to legal or contractual restrictions and reasonable notice, and raise a concern about our privacy practices. We collect, use, and disclose personal information only for purposes that a reasonable person would consider appropriate in the circumstances and as otherwise permitted by applicable law. Information may be processed by service providers outside Canada and may be subject to the laws of the country where it is processed.
Other Regions
If the laws where you live provide additional mandatory rights, those rights remain available to you. This may include rights to object to or restrict processing, withdraw consent, or complain to a local data protection authority. The availability of a right depends on the law that applies to Memova and your use of the Service.
To exercise a regional privacy right, contact hello@memova.ai and identify your country and state or province. We will respond within the period required by applicable law.
20. Contact Information
If you have questions, requests, or concerns about this Privacy Policy or our privacy practices, please contact us at:
MEMOVA LLC
hello@memova.ai