Mparanza LLC ยท Privacy notice

Zero Retention Policy

Mparanza LLC's products use two processing categories: ordinary plugin functions and Mparanza LLC-hosted services. Ordinary plugin functions run in the OpenAI Codex or Anthropic Cowork account and workspace you choose. Mparanza LLC does not receive or retain Customer Content merely because you use these functions, and the plugins do not automatically anonymize that content. Mparanza LLC-hosted services receive the Customer Content needed to provide those services and handle it according to the retention and deletion rules described below.

Effective July 31, 2026

What Zero Retention Means

Zero retention is a design objective for Customer Content on systems that Mparanza LLC controls, not a claim that every hosted service stores nothing. Customer Content means files, datasets, prompts, instructions, recordings, transcripts, reports, comments, and workflow outputs submitted for processing.

Ordinary plugin functions run in your selected OpenAI Codex or Anthropic Cowork account and workspace without sending Customer Content to Mparanza LLC. Mparanza LLC-hosted services receive the content described for each service and follow the retention and deletion arrangements below.

Authentication, delivery, security, legal, saved-service, and external-service records are also addressed below.

Scope

This policy applies to mparanza.com, Mparanza LLC-hosted tools, downloadable plugins, authentication and download flows, support communications, and other Mparanza LLC services that link to it. It explains both retention and the wider handling of personal information.

Mparanza LLC-controlled systems are systems that Mparanza LLC operates or can directly administer. Your own device, selected Codex or Cowork account and workspace, connected services, email provider, and other externally operated systems are not Mparanza LLC-controlled systems.

If you use Mparanza LLC for an organization, you are responsible for giving required notices and obtaining the rights and permissions needed for information you choose to process.

Ordinary Plugin Functions

Ordinary plugin functions run in your selected OpenAI Codex or Anthropic Cowork account and workspace. Files, scripts, and outputs may stay on your computer, while content the selected host reads can enter its model context under that account. Mparanza LLC does not receive, access, or retain that Customer Content merely because you use the plugin, and the plugin does not automatically anonymize it.

Your selected Codex or Cowork account, workspace settings, connectors, and other services process information under their own arrangements. If a plugin clearly invokes a Mparanza LLC-hosted service, that category is covered by the next section.

Vera and Clara are available as plugins for Codex and Cowork. They work with material supplied in the session and with callable connected apps. Direct folder access, persistent project files, local tools, and durable deliverables depend on the selected host and its capabilities.

Vera's Studio Archive uses two non-hosted message routes. Gmail is searched through a separately connected Gmail connector in ChatGPT, Codex, or Cowork. WhatsApp is inspected only from Codex Desktop with Computer Use in the WhatsApp Desktop app already opened and authenticated by the professional. Neither route creates a Gmail or WhatsApp message store on Mparanza LLC-controlled systems. Content read by the selected host may still enter the model context under the user's OpenAI or Anthropic account.

Mparanza LLC-Hosted Services

When you explicitly use a Mparanza LLC-hosted service, the content needed for that service reaches Mparanza LLC-controlled systems. Hosted processing may create uploads, temporary files, session or job state, extracted content, generated outputs, recordings, transcripts, or review artifacts.

Some hosted services process a request without intentionally preserving durable feature state. Others intentionally save a deck, template, checking session, interview, report, or output so it can be resumed, reviewed, shared, retried, or retrieved. Those saved records are exceptions to the zero-retention objective until they are deleted.

Closing a browser, completing a job, archiving a project, or allowing a link to expire does not necessarily delete the underlying hosted data. Mparanza LLC's product development is focused on ordinary plugin functions and reducing these hosted retention exceptions.

Limited Information We Retain

Depending on how you use Mparanza LLC, we may retain:

  • account and authentication information, such as your email address and profile details used to sign in;
  • Customer Content and feature state that you explicitly submit to or create with a Mparanza LLC-hosted service;
  • limited download, transactional-message, and delivery records, including email addresses or protected email identifiers and relevant timestamps;
  • communications, feedback, support requests, and other messages you send to us; and
  • technical and security information such as IP address, browser information, request path, timestamps, cookie or session identifiers, error logs, and security events.

How We Use Information

We use retained information for:

  • to perform the workflow or provide the feature you requested;
  • to authenticate users, secure sessions, prevent abuse, and protect the Service;
  • to deliver requested downloads and transactional messages;
  • to troubleshoot failures and provide support; and
  • to comply with law, enforce terms, and protect rights, safety, and security.

Uses We Reject

Mparanza LLC does not sell personal information, share it for cross-context behavioral advertising, or use Customer Content to train a generalized AI model. We do not claim ownership of Customer Content.

Mparanza LLC will not use Customer Content for a materially different purpose unless that purpose is clearly disclosed and separately authorized where required.

Retention Today

Retention differs by service. The following describes the current behavior:

  • Ordinary plugin functions: Mparanza LLC retention is zero for content Mparanza LLC does not receive. Content that Codex or Cowork reads is handled under the terms and data controls of your selected OpenAI or Anthropic account and workspace; local storage is not anonymization.
  • Plugin updates and feedback: startup checks request the public plugin-version manifest and may poll the status of a previously submitted request. Those checks contain no Customer Content, although the technical records described below may be logged. Feedback or suggestion content is transmitted only through the explicit submission workflow and remains a support record until administrative deletion.
  • Request-scoped hosted tools: the application does not intentionally preserve a durable feature copy after the response, although temporary system handling and technical logs may occur.
  • Check Entries: the workflow does not call a Mparanza LLC-hosted service and creates no working files on Mparanza LLC-controlled servers. It reads journal and supporting-document inputs and writes its outputs in the local folders available to your selected Codex or Cowork environment. If you use an optional authorized accounting-system connector, that provider materializes an export locally before Check Entries runs, and the provider's own terms and data controls apply.
  • Hosted Voice call capture: live video remains in the browser and is not uploaded to Mparanza LLC. Uploaded audio, upload chunks, and transcription work files are deleted before a completed package can be returned. On terminal package retrieval, transcript and package job state are scrubbed before the server sends the response; if that scrub fails, retrieval is blocked. When an authenticated launch includes compact case context, it is held in owner-bound opaque-token metadata and used to guide transcription. Token access expires after eight hours; startup and periodic cleanup remove expired launch metadata and abandoned call-capture state after interrupted processing.
  • Retail data bridge: Scraped retailer evidence used by Retailer Signals and Brand Fit, together with mapping worksets, mapping submissions, structured product records, taxonomy, and accepted mappings, is retained as durable service data. Product-image bytes and generated reports are not uploaded by the plugin.
  • Saved Mparanza LLC-hosted content: slide projects, templates, and hosted interviews are retained until manual or administrative deletion. Archiving a deck or expiration of an interview link is not deletion.
  • Authentication: signed sessions normally expire after 12 hours. Sign-in links are single-use and normally expire after 15 minutes, although related delivery and technical records may remain separately.
  • Technical records: web access logs currently use 14 daily rotations. Other application logs, download records, message records, caches, exports, and backups do not yet share one automatic deletion schedule and remain until rotation, cleanup, or administrative deletion.
  • Diagnostic recording: where replay or diagnostic recording is enabled for a hosted workflow, prompts and outputs may remain until administrative deletion. Such a workflow is not a zero-retention workflow.

External Services

Ordinary plugin functions run in your selected OpenAI Codex or Anthropic Cowork account and workspace. Mparanza LLC does not control that account or workspace or make promises about its handling of data; the relevant provider's terms and data controls apply separately.

When a Mparanza LLC-hosted service uses an external service, the content described for that hosted service may be transmitted to it. External systems are not Mparanza LLC-controlled systems, and their terms apply separately.

For Studio Archive, a separately connected Gmail connector accesses the mailbox selected by the user in ChatGPT, Codex, or Cowork, while Codex Desktop Computer Use can inspect the WhatsApp Desktop interface on the user's own computer. The WhatsApp route runs only in Codex Desktop. Gmail, WhatsApp, OpenAI, and Anthropic are external systems under their own terms and controls. The professional signs in to those services directly; Vera must not request passwords, QR codes, authentication cookies, tokens, or one-time codes through chat.

When Information May Be Shared

Mparanza LLC may share information only:

  • with service providers and contractors as needed to perform the purposes described in this policy;
  • with your organization or workspace administrator when you use an organization-controlled account or project;
  • to comply with law, legal process, or an enforceable request from a public authority;
  • to protect rights, property, security, or safety;
  • in connection with a corporate transaction; or
  • with your consent or at your direction.

Deletion Requests and Privacy Rights

You may ask Mparanza LLC to identify, access, correct, or delete information associated with you. We may verify your identity and ask for the feature, approximate date, or identifier needed to locate the information.

A deletion request covers Mparanza LLC-controlled systems. It does not remotely delete files in your workspace, messages already delivered to recipients, recipient copies, or information held in systems that Mparanza LLC does not control. Limited information may also be retained where required for law, security, fraud prevention, or the protection of another person's rights.

Depending on where you live, you may also have rights to portability, restriction, objection, withdrawal of consent, or appeal. Users in the EEA, UK, or Switzerland may complain to their local data-protection authority. Applicable legal bases may include performance of a contract, legitimate interests, consent, and compliance with legal obligations.

For California residents, Mparanza LLC does not sell personal information or share it for cross-context behavioral advertising.

Security and International Processing

We use administrative, technical, and organizational measures designed to protect information. No online service, transmission, storage system, or model-based workflow can be guaranteed to be fully secure. Keep independent copies of important content and secure your account and devices.

Mparanza LLC is based in the United States. Hosted and external-service processing may occur in the United States and other countries whose data-protection laws differ from those where you live.

Children

The Service is not directed to children under 18, and we do not knowingly collect personal information from children under 18. If you believe a child has provided personal information to us, contact us so we can take appropriate action.

Changes

We may update this Zero Retention Policy as our workflows and controls change. The effective date identifies the current version. An updated version is effective when posted unless it says otherwise, subject to applicable law.

Contact

Zero-retention, deletion, and privacy requests should be sent to fabio@mparanza.com.