We design Ameeba to need less information about you.
Ameeba uses encrypted identity and aliases instead of requiring a phone number, email address, public profile, or password as the foundation of your Ameeba identity. Some information still has to be processed to operate, secure, synchronize, and improve the Services. We explain those categories below without treating pseudonymous data as if it can never relate to a person.
Privacy by design
This Privacy Policy applies to Ameeba products, websites, applications, and services that link to it, including Ameeba Chat, Pseudopod, Max AI, Vault, Nucleus, Notes, Secret Notes, Spaces, Inbox, and Ameeba Compute (collectively, the “Services”).
Ameeba is built around data minimization. You can create and use an Ameeba identity without making your name, phone number, email address, or a conventional public profile the basis of that identity. We use aliases, encrypted identifiers, trusted-device authentication, and encryption to reduce unnecessary exposure.
Privacy is not the same as invisibility.
Network providers, operating systems, app stores, websites you visit, connected services, other participants, or a remote compute host may process information under their own systems and policies. Encryption protects data in defined contexts; it does not make every endpoint or execution environment unable to see the information it must process.
Information we process
Identity and authentication data
We may process your alias, encrypted or pseudonymous identifiers, public-key or verification material, trusted-device relationships, session and authentication tokens, recovery-related state, organization or Space membership, and security events needed to authenticate and authorize access. Ameeba does not require a phone number, email address, or password to establish your core Ameeba identity.
Device and technical data
We may process limited technical information such as application version, operating-system family, device capabilities, crash information, diagnostic events, performance data, and security signals. Pseudopod and Compute may also surface hardware characteristics such as CPU, GPU, available VRAM, runtime compatibility, and device availability when those features require them.
Network data
Internet services necessarily receive network information, including an IP address, while establishing connections. Ameeba is designed to minimize retention of IP addresses and not use them as the identity layer for your Ameeba account. Network infrastructure or service providers may temporarily process network information for delivery, security, abuse prevention, rate limiting, or reliability.
Content and encrypted payloads
Depending on the feature you use, the Services may transmit or store messages, files, notes, calls, Vault objects, Inbox content, tasks, events, AI prompts, AI outputs, and related metadata. Where a feature is end-to-end encrypted, Ameeba is designed so protected content remains available to the intended participants and trusted devices rather than being readable as ordinary server-side content.
Support and information you choose to provide
If you contact support, submit a request, report a bug, or otherwise communicate with Ameeba outside the encrypted product experience, we process the information you choose to provide so we can respond. That information may include contact information if you voluntarily include it.
How we use information
We process information as reasonably necessary to provide and operate the Services, authenticate trusted access, deliver and synchronize content, enable features you request, maintain reliability, protect users and infrastructure, prevent abuse, troubleshoot problems, improve the product, comply with applicable law, and enforce our Terms.
- We do not sell your personal information.
- We do not build Ameeba around advertising profiles or cross-site behavioral advertising.
- We do not require conventional real-world identity as the default access model for Ameeba.
- We may use aggregated or de-identified measurements to understand reliability, performance, and product usage where appropriate.
Product-specific processing
Ameeba Chat, Notes, Secret Notes, Spaces and Inbox
These features process the content and delivery information needed to communicate and collaborate. Messages and files described as end-to-end encrypted are protected between intended participants and trusted devices. Features such as organization membership, Spaces, delivery state, and synchronization can require associated operational metadata even when message content is encrypted.
Vault
Vault is designed for encrypted storage. Ameeba may store encrypted objects and the operational metadata needed to store, retrieve, synchronize, version, or manage them. Protect your trusted devices and recovery material; encryption cannot protect content after an authorized endpoint has decrypted it.
Pseudopod
Pseudopod is Ameeba’s encrypted workspace for AI, communication, knowledge, files, tools, and connected applications. Local workspace data may remain on hardware you control. If you choose synchronization, connected applications, web browsing, or third-party tools, information is also processed by the relevant destination or provider according to the action you take.
Max AI
Max processes the prompts, workspace context, files, tool inputs, memory you enable, and other information necessary to perform the request you make. Where Max runs locally through Pseudopod, inference can occur on hardware you control. Where an AI request uses hosted infrastructure, a connected provider, or remote compute, the information required for that request is processed in that execution environment. AI output may be inaccurate and should be independently evaluated for important decisions.
Ameeba Compute
Compute sharing is opt in. When you enable Share Compute, Ameeba may process device availability, hardware capacity, compatibility, workspace membership, job state, and routing information needed to match workloads with eligible devices. A remote device performing inference necessarily processes the workload it executes. Encrypted transport protects information in transit but does not make a remote execution host unable to inspect information available to that workload. Only share compute with devices and participants you trust.
Nucleus and organizations
Nucleus and organizational features may process organization membership, verification state, roles, access relationships, and administrative events needed to provide verified organizational access and Spaces. An organization may separately control information it places into its workspace and may have its own privacy obligations to its members.
Security and encryption
Ameeba uses technical and organizational safeguards intended to protect information, including encrypted identity, trusted-device authentication, encryption in transit, end-to-end encryption for supported communication and content, access controls, and security monitoring.
No system is perfectly secure. You are responsible for protecting your devices, recovery material, active sessions, and any credentials or secrets you choose to place into connected third-party services. If another participant or authorized endpoint can access content, encryption cannot prevent that participant or endpoint from copying or disclosing it.
Retention and deletion
We retain information for as long as reasonably necessary to provide the feature you use, maintain security and integrity, satisfy legal obligations, resolve disputes, and enforce agreements. Retention depends on the type of information and the product context.
Deleting content or an Ameeba identity may remove or disassociate information from active systems, but deletion may not immediately remove data from encrypted backups, security records, another participant’s device, content another participant has saved, third-party services, or systems we are legally required to preserve. Ephemeral features may use shorter retention by design.
Your privacy rights
Depending on where you live, applicable law may give you rights to access, correct, delete, restrict, object to, or obtain a portable copy of certain personal information, and to appeal or complain to a data-protection authority. California and other U.S. state laws may provide additional rights concerning access, correction, deletion, and certain disclosures or uses of personal information.
Because Ameeba minimizes conventional identity information, we may need enough information to verify that a request relates to the requester without collecting unnecessary new identity data. Some requests may be limited where we cannot reasonably link information to you, where data is end-to-end encrypted, or where retention is required by law.
Ameeba does not sell personal information or use it for cross-context behavioral advertising as those concepts are generally understood under U.S. state privacy laws.
Children's privacy
The Services are not directed to children under 13, and you may not use the Services if applicable law does not permit you to do so. We do not knowingly seek personal information from children in violation of applicable law. If you believe a child has provided information to Ameeba unlawfully, contact us so we can evaluate and take appropriate action.
International use
Ameeba may operate infrastructure and use service providers in more than one country. Information may therefore be processed in jurisdictions other than the one where you live. Where applicable law requires safeguards for international transfers of personal information, we use appropriate transfer mechanisms or other recognized protections.
Changes to this policy
We may update this Privacy Policy as the Services, technology, or law changes. When changes are material, we will provide notice appropriate to the circumstances, such as updating the effective date, posting a notice, or providing an in-product notice where appropriate. Your continued use of the Services after an updated policy takes effect is subject to the updated policy.
Contact
For privacy questions or requests regarding your information, contact us through the Ameeba Support Center. When submitting your request, identify it as a privacy or data request so it can be routed appropriately.
When contacting us, please do not send recovery material, private encryption keys, passwords, or sensitive content that is not necessary for your request.
Privacy is part of the architecture.