Our Zero-Retention Commitment
Zero retention is Mparanza's design objective for Customer Content on systems that Mparanza controls. Customer Content means files, datasets, prompts, instructions, recordings, transcripts, reports, comments, and workflow outputs submitted for processing.
We avoid receiving Customer Content when a workflow can run locally. When Mparanza does receive Customer Content, our objective is to keep it only for the shortest period needed for the feature you requested and then delete or de-identify Mparanza-controlled copies.
Zero retention does not mean that Mparanza keeps no information of any kind or that every optional hosted feature deletes data instantly. Authentication, delivery, security, legal, saved-feature, and external-service records are addressed below.
Scope
This policy applies to mparanza.com, Mparanza-hosted tools, downloadable plugins, authentication and download flows, support communications, and other Mparanza services that link to it. It explains both retention and the wider handling of personal information.
Mparanza-controlled systems are systems that Mparanza operates or can directly administer. Your own device, chosen AI environment, connected services, email provider, and other externally operated systems are not Mparanza-controlled systems.
If you use Mparanza for an organization, you are responsible for giving required notices and obtaining the rights and permissions needed for information you choose to process.
Local Plugin Workflows
Mparanza's core plugins run in the AI environment and workspace you choose. Installing or using a plugin does not by itself upload workspace files to mparanza.com. Mparanza does not receive, access, or retain Customer Content that stays within that environment.
Your chosen environment, connectors, and other services may process information under their own arrangements. If a plugin clearly invokes a Mparanza-hosted feature, the hosted portion is covered by the next section.
Optional Hosted Features
When you explicitly use a Mparanza-hosted feature, the content needed for that feature reaches Mparanza-controlled systems. Hosted processing may create uploads, temporary files, session or job state, extracted content, generated outputs, recordings, transcripts, or review artifacts.
Some hosted features 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's product development is focused on local plugins and reducing these hosted retention exceptions.
Limited Information We Retain
Depending on how you use Mparanza, 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 an optional hosted feature;
- 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 only as needed:
- 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 using the minimum information reasonably needed; and
- to comply with law, enforce terms, and protect rights, safety, and security.
Uses We Reject
Mparanza 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 will not use Customer Content for a materially different purpose unless that purpose is clearly disclosed and separately authorized where required.
Retention Today
Our objective is to move every Mparanza-controlled Customer Content workflow toward zero retention. The following describes current retention behavior and therefore the present limits of that objective:
- Local plugin content: Mparanza retention is zero because Mparanza does not receive content that remains in your chosen environment.
- 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: server working files are ordinarily removed through periodic cleanup after about seven days; some job metadata uses a shorter, event-triggered cleanup. Cleanup is not guaranteed to occur at an exact instant.
- Hosted Voice call capture: live video remains in the browser and is not uploaded to Mparanza. 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. Startup and periodic cleanup remove abandoned call-capture state after interrupted processing.
- Saved hosted features: 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
A plugin operates inside the AI environment and workspace you choose. Mparanza does not control that environment or make promises about its handling of data; its terms apply separately.
When a Mparanza-hosted feature requires an external service, only the information reasonably needed to perform the requested operation may be transmitted to that service. External systems are not Mparanza-controlled systems, and their terms apply separately.
When Information May Be Shared
Mparanza 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 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-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 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 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.