1. Scope and operator
This notice covers Minerva Advisor, operated by Ready-Market Online Corporation, 3F-1., No. 143, Sec. 1, Keelung Rd., Xinyi Dist., Taipei City 110, Taiwan. It applies when you open Minerva from Gmail, paste or upload content, use the Decision Room, configure model access, maintain a customer profile, or use subscription and invoice functions.
2. Information Minerva processes
- Content you intentionally paste, upload, or add to a Decision Project.
- The currently opened Gmail thread when you explicitly invoke the Gmail add-on. Minerva does not search your mailbox or read other threads automatically.
- Project data created through the service, including selected sources, model-generated analysis, discussion, decisions, action assignments, and results you report.
- Your Google or Workspace identity for authentication, stable owner isolation, and access control. A verified email address may change without changing the internal customer ID.
- Customer and billing profile data you provide, including customer type, contact name, billing email and phone, billing country, legal name and tax ID where applicable, billing address, invoice or receipt preference, and consent versions.
- Subscription, payment, invoice, refund, dispute, reconciliation, and support records. Each checkout keeps an encrypted, immutable snapshot of the customer profile version used for that transaction.
- If you choose bring-your-own-key (BYOK), the provider credential you enter and limited status information such as provider, fingerprint, revision, and test time.
- Operational metadata such as request status, source identifiers, counts, timing, and error class. When first-party marketing measurement is enabled, Minerva may also record an anonymous session journey ID, event ID, social post key, UTM campaign dimensions, locale, relative page path, product-evidence and call-to-action stage, and server receipt time. The event contract rejects email addresses, prompt or decision content, account or tenant identity, IP address, user-agent, referrer, and arbitrary extra fields. Source-trace, usage, and marketing-funnel logs are designed not to contain Gmail message bodies, uploaded content, free-form discussion, raw customer profile fields, payment-card data, or API keys.
3. Why the information is used
Minerva uses project information to reconstruct roles and events, distinguish evidence from inference, identify missing context and decision risk, compare options, support human review, maintain the Decision Project you asked it to save, and prepare editable drafts or action plans. It uses customer and billing information to identify the account owner, select the correct regional payment provider, administer a subscription, issue or correct invoices and receipts, reconcile payments, process refunds and disputes, prevent duplicate subscriptions, meet tax and accounting obligations, and provide customer support. It does not send, modify, delete, archive, or label email automatically.
4. Google API data
Google user data is used only to provide or improve the user-facing Minerva decision-support functionality. It is not sold, used for advertising, or used to build advertising profiles.
5. Service providers
Minerva currently uses Google Cloud for authenticated hosting, encrypted data storage, key management, and access control, and Anthropic's commercial API for requested model processing. Selected context and instructions may be transmitted to these providers solely to operate the requested service. ECPay processes Taiwan recurring card payments and related Taiwan invoice operations; PayPal processes monthly recurring payments and one-time annual payments for all other billing countries. Payment-card and payment-account credentials are entered on the selected provider's page and are governed by that provider's terms and privacy practices.
If you enable BYOK, Minerva uses that credential only to test access and make the requested model calls. The credential is not placed in URLs, browser storage, analytics events, or project exports.
6. Storage, encryption, and retention
Minerva stores each encrypted Decision Project so you can return to the same context instead of starting over. A project can contain the source content you explicitly selected, analysis, discussion, a confirmed decision, action status, and user-reported results. Project content is protected using authenticated encryption and a wrapped data key, and records are partitioned by the verified owner identity.
Customer profiles and checkout snapshots use authenticated envelope encryption with owner-scoped records. Operational payment, invoice, dispute, and reconciliation ledgers store pseudonymous customer and checkout identifiers instead of duplicating profile fields. A saved customer profile may be updated; the historical checkout snapshot attached to an existing transaction remains immutable so invoices, refunds, disputes, and audits use the facts accepted for that transaction.
A project remains available until you permanently delete it, your account or contracted access is closed, or Ready-Market must remove it for security, abuse prevention, legal compliance, or service operation. The in-product permanent-delete control removes the encrypted project record from the active application database and creates a minimal audit event recording that deletion occurred. You can also archive a project without deleting it or export the complete project as JSON before deletion.
Customer profile data may be corrected or removed after account closure when it is no longer needed, but payment, invoice, tax, refund, dispute, fraud-prevention, reconciliation, and minimal audit records may remain for the period required by applicable law, accounting rules, payment-provider obligations, or the establishment and defense of legal claims. Deleting a Decision Project, uninstalling the add-on, cancelling renewal, or closing a subscription does not automatically erase those legally required records.
For long Gmail threads, an Apps Script relay may temporarily cache encoded thread context for up to 30 minutes so the user can open the Decision Room. BYOK credentials remain encrypted until you delete or replace them or the related access is terminated. Operational and security logs may retain content-free request metadata according to applicable infrastructure settings; Minerva does not promise a fixed retention period for those logs or minimal audit records.
7. Sharing and human access
Minerva does not sell personal information. Human access to specific customer content is not part of normal operation and should occur only with documented customer approval for support, or when necessary for security, abuse investigation, or legal compliance.
8. Your controls
- Do not invoke Minerva on a thread you do not want processed, and add other sources only when you want them in the project.
- Export a project as JSON, archive it, restore it, or permanently delete it from the Decision Room.
- Review and update your customer, contact, billing-country, tax, address, and invoice preferences from the authenticated Member & Billing page.
- Review provider status and request cancellation of the next automatic renewal. Cancellation does not erase a paid term or legally required accounting records.
- Delete or replace a saved BYOK credential from Model Access.
- Uninstall the Gmail add-on or revoke the application's Google access.
- Ask Ready-Market to investigate account-wide access, correction, deletion, invoice, refund, or privacy questions through the support channel below.
9. Security and changes
Minerva uses authenticated access, owner-scoped authorization, least-privilege Gmail access, encryption in transit, authenticated envelope encryption for saved projects and credentials, and separation between the private decision service and this public trust center. No system can guarantee absolute security. Material changes to this notice will be posted here with a revised date.
10. Contact
Email service@ready-market.com and identify the request as “Minerva privacy.” Do not include passwords, tokens, API keys, or unnecessary email content.