This Privacy Policy explains how Namespace Inc., incorporated in the British Virgin Islands ("we", "us", or "our"), handles information when you use our website, documentation, dashboard, hosted API, and connected developer tools. It also covers beta invitations, the waitlist, and communications with us. Namespace Inc. is responsible for the processing described in this policy, except where we process information solely on an organization's instructions under a separate data-processing agreement.
It does not describe independent processing by a blockchain network, an AI client you choose, or someone operating their own deployment of our open-source software. Those operators are responsible for their own practices.
1. Information we receive
Account and organization information
We receive your email address, profile details you provide, organization and membership information, and invitations. We store authentication and session records, including public passkey credentials and relevant device, browser, and sign-in information. Private passkey material remains with your authenticator or passkey provider.
Wallet and operation information
We process public wallet and signer addresses, supported networks, session-key permissions, grants, operation requests, execution results, transaction identifiers, and usage records. Requests to execute or sign may include transaction parameters, messages, or typed data needed for the requested operation.
Wallet addresses and public transaction records can be associated with you or your organization. They should not be treated as anonymous merely because they do not contain your name.
Technical and service information
Our systems process IP addresses, browser and device information, request timing, response status, errors, traces, and security and audit events. We use these records to operate the service, investigate problems, and prevent abuse. IP addresses and other identifiers in diagnostic records can be personal information.
We use PostHog for product analytics and session replay across our website, documentation, and dashboard. This can include pages visited, interactions, device and browser details, identifiers, and recordings of the interface as you navigate it. We use redaction and masking controls to reduce sensitive information in diagnostics and recordings; this does not make all collected information anonymous.
Information you send us
We receive your email address when you join the waitlist, along with your registration time and the status of our follow-up. Joining the waitlist does not itself create an account. We also receive information you send through support requests and other communications.
2. What stays on your device
In Namera's self-custodial flow, session keys are generated locally. Export passphrases and private session-key material are not sent to the Namera API. The CLI stores imported keys encrypted locally and uses your operating system's credential store to protect the unlocking secret. MCP authorization credentials are also kept locally using the operating system's credential store.
Local signing does not mean all activity stays local. The CLI, SDK, and MCP server send authorized requests and the information needed to process them to your configured API. Transactions are submitted to network infrastructure, and their resulting blockchain records are public.
The CLI does not configure an automatic telemetry exporter. Requests it makes to our API are still subject to the API's operational logging and security controls. Your selected AI client has its own data-handling practices.
3. How we use information
We use information to:
- Authenticate users and manage organizations, invitations, and access grants.
- Register wallets and permissions, evaluate requests, and prepare and submit authorized operations.
- Track usage and apply service limits, including gas-sponsorship limits.
- Deliver sign-in messages, invitations, and relevant service or security notifications.
- Respond to support requests and follow up on waitlist interest.
- Send newsletters, blog updates, and other promotional email when you opt in.
- Diagnose failures, improve reliability, investigate abuse, and maintain audit records.
- Meet applicable legal obligations and establish or defend legal claims.
Where data-protection law requires a legal basis, the applicable basis depends on the purpose: performing our agreement with you, legitimate interests in operating and protecting the service, compliance with law, or consent where required. Consent can be withdrawn without affecting processing that was lawful before withdrawal.
We do not sell personal information, share it for targeted advertising, or use customer content to train AI models. Disclosure to providers to operate the service is described below.
4. When information is shared
Your organization and connected clients
Authorized organization members can access information according to their permissions. Clients and agents that you authorize receive the account and session-key access covered by their grants. Consider the client's own privacy practices before connecting it.
Service providers
We use Google Cloud for infrastructure in the European Union, Axiom in the European Union for observability, PostHog's European Union service for analytics and session replay, Resend for transactional and opt-in promotional email, and blockchain infrastructure such as Alchemy. These providers receive information needed for the relevant function, such as an email recipient, diagnostic event, interaction record, or operation submitted to a network.
Public networks and legal disclosures
Transactions and other information written to public blockchains are accessible to third parties. Blockchain explorers, validators, and other independent services may copy and analyze those records.
We may disclose information where required by applicable law, to address fraud or security incidents, or in connection with a corporate transaction subject to applicable privacy requirements. We do not describe diagnostic records as anonymous when they include identifiers.
5. Cookies and local storage
The dashboard uses cookies for authentication and related security flows. Browser storage may also retain interface preferences or temporary workflow state. Disabling necessary storage can prevent sign-in or other features from working.
The landing-page waitlist request sends your email to the API without authentication cookies. Dashboard diagnostics are sent through Namera's telemetry proxy rather than exposing provider ingestion credentials in your browser.
PostHog may use cookies or similar browser storage to associate interactions with a visitor or session. Analytics and session replay currently start automatically rather than waiting for a consent selection. This policy discloses that behavior; it does not treat visiting the site or reading this policy as consent. You can contact us about analytics processing and your applicable privacy rights. Browser storage controls may limit some tracking, but are not a guaranteed opt-out from all collection.
6. Retention and deletion
Different records serve different purposes. Retention decisions must account for whether an account is active, unresolved operations, security investigations, audit integrity, support needs, backup cycles, and applicable legal obligations.
Axiom diagnostic data, PostHog analytics events, and PostHog session recordings are retained for 30 days. Database backups are created manually and retained for no longer than 30 days from creation.
Account, operation, audit, and waitlist records do not all expire after 30 days. We retain them while needed for the purposes described above. You can request account closure and deletion of eligible offchain personal information by emailing hey@namera.ai. We complete deletion within 30 days of receiving your request, subject to identity verification and any applicable legal exceptions. If verification or a legal exception affects completion, we explain the reason and applicable timeframe.
Deleting information from the live database does not immediately remove an existing backup. Relevant backup copies expire within the 30-day backup retention period. If a backup is restored, we reapply completed deletion requests. Information retained under a legal exception is limited to what is necessary for that purpose and retained only while the exception applies.
Signing out, revoking a key, or completing a waitlist entry does not itself erase the associated records. Contact us for information about a particular category or deletion request.
We cannot remove or alter records on a public blockchain. Deleting data from Namera does not delete copies held independently by authorized clients, blockchain infrastructure, or other third parties.
7. Security and international processing
Namera uses access controls, encrypted transport, credential hashing or encryption where appropriate, and operational monitoring. These measures reduce risk but cannot guarantee that information will never be lost, accessed improperly, or disclosed.
Our primary infrastructure and our Axiom and PostHog deployments are in the European Union. Email delivery and other provider operations may involve processing elsewhere, including Japan for our Resend sending region. These deployment locations are not a guarantee that every provider, subprocessor, or support operation processes information only in those locations. Namespace Inc. is incorporated in the British Virgin Islands.
International processing is subject to the applicable data-protection requirements. Contact us for information about the recipients, locations, and safeguards relevant to your information. We do not claim that EU hosting alone establishes compliance or that Namespace Inc. holds a particular privacy certification.
Do not send private keys, recovery material, export passphrases, or authentication tokens in support messages.
8. Your choices and rights
Depending on your location and the applicable law, you may have rights to access, correct, delete, or receive a copy of your personal information; restrict or object to certain processing; withdraw consent; or complain to a data-protection authority. These rights are subject to applicable conditions and exceptions.
To make a request, email hey@namera.ai. We may need to verify your identity and your authority over an organization before acting. Do not include private signing material in a request.
You can stop using a connected client and revoke its grant through the available access controls. Onchain permission removal is separate and must be confirmed on each relevant network. To stop waitlist follow-up, contact us at the same address.
You can request account closure and deletion of eligible offchain personal information by emailing us. We may retain information where needed to meet legal obligations, address security incidents, or establish or defend legal claims, and will explain relevant limitations when handling your request. Self-custody does not prevent deletion of eligible information held by Namera, but you remain responsible for your keys and onchain permissions.
Promotional emails are opt-in. You can unsubscribe using the link in a promotional email or by contacting us. Unsubscribing from promotions does not stop authentication, security, or other necessary service emails.
9. Children
Namera is intended for adults and is not directed at people under 18. If you believe a child has provided personal information to us, contact us so we can investigate and take appropriate action.
10. Updates and contact
We will update this notice when our practices change and identify the date of the published version. Where required, we will provide additional notice of material changes.
For privacy questions or rights requests, contact hey@namera.ai or write to:
Namespace Inc., 2nd Floor, Ellen L. Skelton Building, Fishers Lane, Road Town, Tortola, British Virgin Islands VG1110.