MARi privacy policy

01

Scope and roles

This policy applies to MARi, a locally operated Signal knowledge assistant provided by Metispace LLC. It explains the information MARi processes when an organization or individual installs, configures, and runs the software.

The person or organization operating MARi chooses its documents, Signal groups, device, settings, users, and retention practices. That operator controls the MARi content stored on its device and is responsible for providing any notices, permissions, access controls, and lawful basis required for its use. The Metispace Website Privacy Policy applies separately when someone visits metispace.io or contacts Metispace.

02

Local-first design

MARi is designed to run its document search, embeddings, optical character recognition, vision processing, answer generation, and review tools on the operator's device. The standard configuration uses locally installed Ollama models and does not require MARi questions, source documents, retrieved passages, prompts, or answers to be sent to a Metispace-operated server or a cloud AI model.

Metispace does not receive, remotely access, or monitor MARi's local content merely because the software is installed or used.

03

Signal information

When MARi is connected to Signal, it may process incoming group events and messages available to MARi's Signal account. This can include message text, sender name, phone number or Signal identifier, group identifier and name, message timestamp, and mention information.

MARi checks messages to determine whether it was mentioned and whether the group is permitted. Questions addressed to MARi are used to retrieve local source material, generate a response, return that response to the same Signal group, and create local operational and review records. MARi is a participant in every group where it is added, so authorized users should treat the MARi device as an intended recipient of messages in those groups.

04

Documents and derived data

The operator may add text files, Markdown files, PDFs, Word documents, screenshots, scans, and document photographs. MARi processes their text locally and may create searchable chunks, vector embeddings, source references, indexes, and OCR or vision transcripts.

These materials can contain personal, confidential, or sensitive information selected by the operator. Operators should add only material they are authorized to use and should separate collections or restrict access when different teams should not use the same sources.

05

Logs, replies, and human review

MARi creates local runtime logs that may contain incoming Signal event details, sender and group identifiers, message excerpts, matched questions, retrieved source references, generated reply text, delivery status, and errors.

MARi also stores local interaction records for reply review. These records can include the full question, answer and reply; sender and group information; timestamps; retrieved source chunks and similarity scores; response time; automated audit flags and notes; and feedback entered by a reviewer. Test questions entered in the local dashboard create similar records.

06

Settings and account data

MARi stores local configuration such as its Signal phone number, allowed group identifiers, mention trigger, active document collection, model choices, retrieval settings, and local service address. Signal registration and session information is maintained locally by signal-cli outside MARi's document collection. Downloaded model files are maintained locally by Ollama.

07

How information is used

MARi uses information to receive and respond to authorized questions; search operator-approved documents; generate and send source-backed answers; manage collections and settings; test and improve response quality; provide activity, audit, and feedback tools; troubleshoot errors; prevent duplicate processing; enforce allowed-group settings; and protect the operation of the local service.

08

Signal and other third parties

Signal transports MARi messages and provides end-to-end encryption between group participants. Signal is an independent third-party service, and its handling of account information, encrypted delivery, message history, and backups is governed by the Signal Privacy Policy. Encryption protects messages in transit, but MARi must decrypt messages on its device to process them as an intended group participant.

MARi uses the independent signal-cli software to connect its Signal account and uses Ollama to run models. Ollama states that prompts and data are not visible to Ollama when models run locally. Operators who enable Ollama cloud features, choose a cloud-hosted model, change MARi's model service address, expose local services, or connect other providers create a different data flow governed by those choices and providers. See the Ollama privacy and local-processing information.

MARi is not affiliated with or endorsed by Signal or Ollama.

09

Disclosure and sale

MARi does not send local documents, indexes, Signal questions, answers, or review records to Metispace in its standard local configuration. Metispace does not sell or rent that information and does not use it for targeted advertising or to train Metispace AI models.

Information can still be disclosed by the operator or users—for example, through Signal group membership, device access, backups, exports, remote-access tools, support attachments, or a changed model configuration. The operator is responsible for those disclosures.

10

Retention and deletion

MARi does not currently impose an automatic retention period. Source documents, generated indexes, transcripts, settings, runtime logs, and interaction-review records remain on the operator's device until the operator deletes or replaces them, clears the relevant local files, or removes the MARi support data.

The dashboard can delete individual source documents and interaction records. After deleting or changing a source document, the operator should rebuild the active index so text derived from the former source is removed from that index. Backups, exported files, Signal message history on participant devices, and copies stored outside MARi must be deleted separately.

Metispace cannot view, recover, correct, or remotely delete information that exists only on the operator's MARi device.

11

Security responsibilities

Operators should protect the MARi device and its backups, use operating-system access controls and disk encryption, restrict MARi to approved Signal groups, limit access to source documents and the local dashboard, keep dependencies updated, and review logs and answers appropriately.

The Ollama service and MARi dashboard are intended to remain on the local device and should not be exposed directly to the public internet. Any remote access should use appropriate private networking, authentication, and access controls. No system or security measure can guarantee protection from every form of unauthorized access.

12

Rights and requests

Requests concerning messages, documents, logs, or review records stored by a locally operated MARi installation should be directed first to the organization or person operating that installation. Metispace ordinarily cannot fulfill a request for data it does not possess.

Where Metispace receives information through support, email, or the website, applicable access, correction, deletion, restriction, objection, portability, withdrawal, appeal, and complaint rights may apply. Send those requests to legal@metispace.io. We may need to verify identity and authority.

13

International processing

MARi's local content remains in the locations chosen by the operator unless the operator enables backups, remote access, cloud models, or other transfers. Signal and any other third-party services may process information in other countries under their own terms and privacy practices. Metispace support and website information may be processed in the United States or another country as described in the Website Privacy Policy.

14

Children

MARi is designed for organizational knowledge work and is not directed to children under 13. An operator should not deploy MARi for children or process children's information without appropriate authorization, safeguards, and compliance with applicable age requirements.

15

Changes

We may update this policy when MARi's functions, providers, security boundaries, or legal obligations change. The revised policy will appear on this page with an updated date, with additional notice where legally required.

16

Contact

Metispace LLC
8401 Mayland Dr Ste A
Richmond, VA 23294
United States

Phone: +1 571 720 0270
Email: legal@metispace.io
Virginia SCC Entity ID: 12056141