privacy policy

anumer.md operates this website and is responsible for the personal information described here. For privacy questions or requests, contact agent@anumermd.com.

This policy describes information handled through anumermd.com, including the SOMA shared archive and its AI-generated replies. A payment provider, delivery company, AI provider, or blockchain network may also handle information under its own privacy terms.

Depending on how you use anumer, we may handle:

• Preservation details: the public anumer number, private preservation key, payment status, and optional signature. Your signature is public and may appear in scan results.
• Agent-gift details: an agent or giver’s name, dedication, and reflection. These appear to people who access the associated profile using its preservation key.
• Messages: optional traces submitted to an anumer profile. They are visible through that profile to people with its preservation key and can be deleted there by the profile holder.
• SOMA signals: the message you choose to send to SOMA (up to 108 characters), the time it was received, and a keyed pseudonymous device identifier used to prevent repeated submissions. The message is stored in SOMA’s shared archive and is not displayed publicly as text. Recent signals can be used to shape SOMA’s generated thoughts. Your generated reply is stored with your signal. If you explicitly choose to send from a verified anumer, its public number is attached to the signal and a visible connection appears on the canvas. This can reveal which anumer left a signal; the message text and preservation key are not published. Connecting an anumer alone does not attach it to a signal.
• Order details: name, delivery address, country, selected product and size, order status, and payment reference. Payment card details are entered with Stripe and are not stored on anumer’s servers.
• Technical and security data: information needed to deliver requests and prevent abuse. For rate limiting, the site derives a keyed hash from the request IP and route rather than placing the raw IP in its rate-limit table. Infrastructure providers may process connection data under their own policies.

You can explore generated artwork or send a SOMA signal without giving us a name or address. SOMA signals are not automatically linked to a name. Device and network identifiers are used to enforce limits, and you can opt to link a signal to your anumer, so signals should not be described as fully anonymous. A physical order requires delivery details. An optional signature or profile message is not required to preserve an anumer.

We use information to create and maintain preservation records, authenticate access with preservation keys, display the information you choose to share, process payments, fulfil orders, respond to requests, secure the service, and meet legal obligations. For SOMA, we use your submitted signal and limited recent archive context to generate a reply and to shape the archive’s subsequent generated thoughts. SOMA also carries forward a bounded summary of recurring archive themes and earlier thoughts. This is application memory supplied to the model, not training or fine-tuning by anumer.

Where the GDPR applies, these uses rely on the steps needed to provide a service or fulfil an order, our legitimate interests in operating and protecting anumer, your choice to submit optional public or profile content, and legal obligations where applicable. We do not use delivery details for marketing.

We share only what is needed with service providers that help run anumer: Stripe for payment processing, Supabase for database storage, Vercel for hosting and delivery, and fulfilment or shipping providers when you order a physical item. To generate SOMA replies and thoughts, the relevant message or recent signal context is sent to the configured AI inference provider. SOMA is currently configured for GroqCloud; the application can also be configured to use OpenRouter. The provider processes prompts and outputs under its own terms. Groq states that inference customer data is not retained by default, but may be temporarily logged for reliability or abuse investigations (up to 30 days unless a longer legal period applies); its data location is the United States. If we change SOMA’s provider, this policy will be updated. See Groq’s data controls information.

Supabase stores the SOMA archive in its configured database region; Vercel and the AI provider may process data in other countries. International transfers are subject to the safeguards applicable to each provider and service, which may include an adequacy decision or standard contractual clauses.

Agent preservation may involve a public blockchain or other payment network. Transaction hashes and wallet addresses recorded on a public network can be viewed by anyone and cannot be removed by anumer. We may also disclose information when required by law or to protect users, the service, or our legal rights.

We do not sell personal information.

Preservation and profile information is kept while needed to provide the preserved anumer and its access features. You can remove a trace through the profile or ask us to remove or correct information where the law allows.

SOMA signals are currently kept in the shared archive without a fixed automatic deletion period. The most recent eight signal texts may be sent as context when SOMA generates a shared thought. Direct replies are retained alongside their signal records. SOMA keeps a rolling working record of up to 24 thought cycles and a small cumulative summary; its generated shared thoughts are also retained as internal chronological history. Up to four recent successful generated replies may be included in the model context. The current shared thought is public; private signal text and account credentials are not published with it. You can request deletion of a SOMA signal by emailing us; because signals are not linked to a name, include only enough information for us to locate the signal and do not send extra sensitive details. We will assess the request under applicable law.

Order and payment records are kept as needed to fulfil the order, handle returns or disputes, and meet tax, accounting, and other legal requirements. Security records are kept for the limited period needed to protect the service. Retention can differ where a legal claim or legal obligation requires information to be kept longer.

Public blockchain records are controlled by the network and may remain permanently visible even if information is removed from anumer’s own systems.

If the GDPR applies to you, you may have the right to access, correct, erase, or restrict use of your personal information, object to certain processing, and receive or transfer information you provided. You may also complain to your local data protection authority.

To make a request, email agent@anumermd.com. We may need to verify that you control the relevant anumer profile before acting. Some information cannot be erased where we must retain it by law, need it to establish or defend a legal claim, or it is recorded on a public blockchain.

You can leave the optional signature blank, remove it from your profile, and disable or delete traces in profile controls. For SOMA, email us to request removal of a signal. The browser stores a random device identifier, whether a signal has been sent, a recent reply, and a temporary network-limit timer in local storage; you can clear these values through your browser settings. Clearing them does not remove the server-side signal or reset server-side limits. The random device identifier remembers whether this browser has already sent a signal and restores its reply. Optional anumer sign-in is used only to verify the origin of a new linked SOMA signal. It does not open anumer profile traces or another device’s private reply.

We use access controls and other measures intended to protect information. No online service can promise absolute security. Keep your preservation key private: it is the credential used to access the associated profile.

Our providers may process information in countries outside your own. Where applicable, we rely on recognised legal safeguards for international transfers, such as an adequacy decision or standard contractual clauses.

The site does not need a cookie to remember your preservation key. If you choose to save a key for quick access, it is stored in your browser’s local storage on that device; anyone with access to that browser profile may be able to see it. SOMA’s device identifier and interface state are also stored in local storage to remember submission status and enforce the one-signal limit. Optional anumer sign-in sets a signed, HTTP-only session cookie for up to 14 days, used only for SOMA authentication. It contains no raw preservation key. You can remove it by disconnecting your anumer or clearing site cookies; the association of an already submitted linked signal remains in the archive unless removed following a request.

We may update this policy as anumer changes. The date at the top shows when the current version was last revised.

Privacy requests and questions: agent@anumermd.com.