MemoRay Trust-First Local AI Memory
Privacy Policy

MemoRay Privacy Policy

This Privacy Policy explains how MemoRay handles website, access request, Founder Access, licensing, support, and app-related information, and the additional processing planned for paid checkout. MemoRay's current core document workflow is designed around local processing, while access requests and support interactions use website and CRM tools.

Last updated: October 2, 2026

Current Policy

MemoRay app document data is handled differently from website and access request data.

The policy below distinguishes current Windows Founder Access processing from purchase-related processing that will begin only when paid checkout becomes available. Paid checkout is not yet live.

1. What this policy covers

This Privacy Policy covers:

  • The MemoRay website.
  • MemoRay access requests and the Founder Access program.
  • Founder Access onboarding and related communications.
  • Support and contact channels.
  • Current app-related privacy behavior.

2. Important distinction: app document data vs. website data

Imported documents, document text, local text-reading output, local search data, queries, and file names are part of the app/local workflow.

Email address, access request responses, optional survey fields, consent records, and support or contact submissions are website/CRM data.

3. MemoRay app document workflow

For the current core local workflow, MemoRay does not require document content to be uploaded to a cloud service. Import, text extraction, local processing, search, retrieval, and Ask MemoRay results with sources are designed to run locally on the user's device.

Document reading, OCR/text extraction, search preparation, retrieval and Ask MemoRay run on the Windows device. Network access is used for Founder Access activation and validation, application update checks, and support pages or reports you choose to open or share. MemoRay does not send document content, filenames, local file paths, queries, extracted text, search data or search indexes to MemoRay licensing or update services for the core workflow. Opening source files in cloud-synchronized folders may involve your storage provider outside MemoRay’s boundary.

4. Website, access request, CRM, and email tools

Users may submit access request or contact information through forms. RayAI LLC may use third-party providers for hosting, forms, CRM, email delivery, and communication management.

HubSpot processes Founder Access request information. Current request fields include first and last name, email, Windows compatibility, primary use case, a question you want to ask across your documents, willingness to test, and consent records. Page context and submission details may also be processed. Older requests may contain additional survey responses.

5. Website tags and support information

The MemoRay application does not collect document/query analytics. Bounded app diagnostic records are stored locally. An issue report is prepared as a local file and is not automatically sent. You choose whether to include diagnostics and share the report. Review it first: your issue description and attachments may contain information you intentionally provide. Website analytics and consent controls are separate.

Public website pages load Google Tag Manager to manage website tags. Loading this service sends browser requests to Google. Website tags and analytics are separate from MemoRay's local document workflow. The Founder download and support form pages do not load Google Tag Manager.

Support requests send the details you enter and attachments you choose to provide. Review screenshots and logs before sending them, and do not include passwords, license keys, or private document content unless support specifically requests the document.

6. Current Founder licensing data

Founder Access activation and validation may process the approved email address, license identifiers, device and activation status, validation results, and bounded operational records needed to provide and protect access. These licensing services do not receive document content, filenames, local file paths, queries, extracted text, or search data for the core document workflow.

7. Planned paid purchase processing

Paid checkout is not yet live. When paid checkout becomes available, RayAI LLC intends to use a hosted checkout operated by a Merchant of Record or payment provider. The checkout and provider terms will identify the seller of record and explain the provider's processing.

When paid checkout becomes available, the Merchant of Record or payment provider may process purchase contact and billing information, payment and tax information, transaction references, subscription status, renewals, cancellations, refunds, and fraud-prevention information. RayAI LLC may receive the customer's name and email, transaction and provider references, product and amount information, discount and tax status, payment/subscription/refund status, and licensing or entitlement details needed to fulfill and support the purchase. RayAI LLC does not need or intend to receive full payment-card details.

8. How we use information

RayAI LLC may use submitted website, access request, support, and operational information to:

  • Manage access requests.
  • Provide Founder Access updates.
  • Prioritize onboarding.
  • Improve product direction.
  • Respond to inquiries.
  • Provide and validate licenses and, when paid checkout becomes available, fulfill and support purchases.
  • Maintain service reliability.
  • Comply with applicable obligations.

9. Sharing and processors

RayAI LLC may share limited website, access request, support, or operational information with service providers that help operate the website, CRM, email, hosting, analytics, security, licensing, or support workflows. When paid checkout becomes available, purchase-related information may also be shared with the Merchant of Record and providers needed for fulfillment and transaction support. These providers are not used to process MemoRay document content for the current core local workflow.

10. Local storage and device responsibility

MemoRay stores app data locally on the user's device for the current core workflow. Users are responsible for device security, operating system updates, backups, malware protection, passwords, and controlling access to their device.

11. Current storage limits

MemoRay stores imported copies, document details, extracted text and search data locally. For documents marked Protected, MemoRay encrypts the saved copy and retained derived content used for search and review, including extracted text, search data and sensitive history. Unlocking is required to search or view it; locked items hide identifying details. Standard content is not protected by the Protected Documents password. Original files outside MemoRay and external backups remain separate. Protection does not defend an already-unlocked device against malware, an administrator or screen capture.

The Protected Documents password is created locally and is separate from the Founder Access license key. RayAI/MemoRay cannot recover it. If it is forgotten while Protected documents remain, recovery requires removing the current MemoRay workspace and reimporting from originals before setting a new password. If the library contains only Standard documents, the password can be cleared in Settings. Original files outside MemoRay are not deleted. See the password recovery guidance before taking action.

12. How long we keep your information

RayAI keeps personal information only while needed to provide access, respond to requests, operate securely, or meet legal obligations.

  • Founder Access requests and general inquiries: up to 12 months after our last meaningful interaction, unless you become a member or request ongoing communications.
  • Member and license records: while needed to provide and verify your access or license. We review these records when that relationship ends.
  • Purchase and transaction records after paid checkout becomes available: as needed for fulfillment, accounting, tax, refund, dispute, fraud-prevention, legal, and audit obligations. The Merchant of Record applies its own retention policy to information it controls.
  • Support messages: up to 12 months after the issue closes.
  • Support attachments: deleted within 30 days after the issue closes, unless needed for an ongoing investigation or legal obligation.
  • Technical and security records: retained for troubleshooting and security only while needed for those purposes.

We review retained information regularly and delete information no longer needed. Limited records may be kept longer where necessary to meet legal obligations, resolve disputes, or honor communication preferences.

Deletion from service-provider backups may take additional time under their backup schedules.

You can request deletion or another privacy action through RayAI's contact form. Choose General inquiry and state that the message is a MemoRay privacy request. You do not need to be an existing customer or HubSpot contact. Do not send passwords, license keys, full payment-card details, or private document content. We may need to verify your identity and retain information required for an ongoing service or legal obligation.

This retention policy concerns information RayAI receives. Your MemoRay library stays on your device and is managed by you, except for information you choose to send to support.

13. Your choices

  • Unsubscribe from emails.
  • Request deletion or correction of submitted access request or contact information.
  • Manage or delete local files and local app data on your device.

Local document data stored on your device may require action on that device because it is part of the local app workflow.

14. Documents about other people

You are responsible for having the right to import, store, and process documents you choose to use with MemoRay, including documents that contain information about family members, clients, customers, employees, contractors, or other individuals.

15. Children's privacy

MemoRay is not directed to children under 13. Adults may choose to import documents that contain information about family members or dependents, but they are responsible for ensuring they have the right to do so.

16. Future optional cloud features

Future features such as sync, backup, mobile access, or team workflows may have different privacy behavior and will require separate disclosure and user choice before use.

17. Changes to this Privacy Policy

RayAI LLC may update this Privacy Policy as MemoRay evolves. When the policy changes, this page will be updated with a new last updated date.

18. Contact

For privacy questions or requests, use RayAI's contact form, choose General inquiry, and state that the message concerns MemoRay privacy. This route accepts requests from customers and noncustomers.