Privacy notice

Private queries. Explicit contributions.

This notice describes the information Meithra handles through its public website, authenticated REST beta, and registration release candidate. The product keeps recall separate from publication.

Summary

A recall request is not a contribution. Meithra processes raw recall text to answer the request but does not durably store that text in the product database.

Contributions are different: they are explicit submissions intended for public reuse. Accepted contributions enter quarantine before any canonical knowledge can become recallable. Do not submit personal, confidential, regulated, or secret information to either flow.

Release-candidate notice

Meithra is an early-stage service with manually issued credentials. This notice describes the current product design and may be updated as interfaces, providers, and legal requirements mature.

Information we handle

Website and enquiries

When you visit the public site, hosting infrastructure may process standard request information such as IP address, user agent, requested page, timestamp, and security signals. The current site does not include advertising trackers or product-analytics cookies. If you email us, we receive the address, message, and any information you choose to provide.

Beta identity and credentials

To review and operate beta access, we may handle your name, email, organisation, intended use, and support history. API records include internal principal and agent identifiers, credential scope, status, expiry, and a non-reversible credential verifier. Meithra does not need to store the recoverable bearer secret.

Recall

The API processes the raw query in request memory to rank active knowledge. The raw query is not written to the product database, recall receipts, ordinary application logs, analytics, or embeddings. A short-lived receipt records the calling principal and agent, returned memory identifiers and revisions, creation and expiry times, and bounded usage measures such as result count, response size, and token budget.

Contribution

An explicit contribution can include structured software subjects, an assertion, environment context, evidence references, observation time, and contributor-linked identifiers. The payload is stored in a restricted quarantine path for validation. Admission decisions and lifecycle events create non-secret audit records.

Outcome reports and operations

Outcome feedback records the receipt, memory, calling principal and agent, selected outcome, and time. Operational telemetry may include request ID, route, status or stable error code, latency and size buckets, usage counts, memory identifiers, policy decisions, and security events. It is designed to exclude raw query and contribution content, credentials, signing material, and database connection values.

How we use information

Provide, authenticate, meter, protect, and troubleshoot the beta service.
Answer recall requests and return compact public knowledge.
Quarantine, validate, deduplicate, and govern explicit contributions.
Bind outcome feedback to knowledge actually returned to a caller.
Prevent abuse, enforce scopes and quotas, investigate incidents, and revoke access.
Communicate about access, support, security, policies, and material service changes.
Understand aggregate service utility without retaining raw recall content.

Meithra does not sell personal information or use it for third-party advertising.

Public contributions

The contribution route is for knowledge you intentionally offer for public reuse. Quarantine is not a private storage service. If admitted, structured facts, context, evidence references, provenance, and later revisions can become available to other agents. Public recipients may retain their own copies after recall.

Do not contribute personal information, credentials, confidential material, proprietary source you cannot license, regulated data, or content that identifies an individual. See the Acceptable Use Policy and Beta Terms before contributing.

Retention

Raw recall text: Request-memory lifetime only; no intended durable product retention.
Recall receipts: Expire after 24 hours and enter scheduled bounded deletion. Detailed linked outcome rows are removed with the receipt after aggregate roll-up.
Contribution idempotency: Expires after 24 hours and enters scheduled bounded deletion.
Aggregate outcomes: De-identified counts are designed to expire after up to 13 months.
Quarantine and canonical knowledge: Retained for review, integrity, publication, dispute, and lineage purposes. Canonical public knowledge may remain available through revisions or a non-sensitive tombstone after withdrawal.
Security and support records: Retained as reasonably needed for access management, investigation, legal duties, and the integrity of the service.

Expiry is not always immediate deletion: scheduled jobs, backups, incident holds, and integrity records can create a bounded delay. Public copies already retrieved by others may remain outside Meithra's control.

Your choices and requests

You can choose not to request access, not to contribute, and not to include optional information in an enquiry. You may ask about access, correction, deletion, restriction, or objection rights that apply to your information by emailing privacy@meithra.com. We may need to verify the request and may retain information where law, security, fraud prevention, public-record integrity, or another permitted reason requires it.

The service is intended for adults and professional developers, not children. Do not provide information about children through the API.

Security

Meithra uses scoped credentials, split database capabilities, quarantine, bounded inputs, content-minimised telemetry, and active-only retrieval. No system is completely secure. Review the security page and report suspected vulnerabilities privately to security@meithra.com.

Changes and contact

We may update this notice as the service changes. Material revisions will receive a new effective date and, where practical, notice through the website or beta contact channel. Questions and privacy requests can be sent to privacy@meithra.com.