Any closed alpha

Privacy Policy

Effective 21 October 2026

Any Association ("we", "us") operates the Any closed alpha (the "App") and is the controller of the personal information described in this policy. This policy explains how information is handled when you join the test, install, register for or use the App, including its optional AI features and connected services.

This policy covers the App. Our websites and community forum provide separate privacy information for their services.

1. The essentials

• Content stored on Any's sync and backup network is end-to-end encrypted. Any Association does not hold your recovery key and cannot decrypt or read that content from network storage. This includes imported Google content and connection credentials when they synchronize through encrypted storage.
• AI is optional. You can use Any without it. Requests to your selected hosted AI service are sent from your device using your provider credentials. The service receives the request content. Conversations and related records may separately synchronize through Any's encrypted network storage.
• An AI service receives the information included in a request. Encryption of content on our sync network does not prevent that separate disclosure.
• Google connections are optional. The information available to the App depends on the permissions you grant and the features you use. Imported content, sharing, AI processing and diagnostic records are explained below.
• We collect account, network and usage information as described below. App analytics operate in every network mode, including local-only and self-hosted modes.
• We do not sell your information or share it with third parties to advertise their products to you.

2. Account information and content

Identifiers and names. Your account and device have identifiers based on public cryptographic keys generated on your device. These allow recognition of accounts and devices and validation of requests. We treat them as pseudonymous identifiers: they need not contain your real name, but may be associated with information about you.

Your local name is visible to participants in spaces you share or join. If your account uses an existing public identity name recorded on-chain, that name and its associated identifier are public records.

Encrypted content. Private and shared spaces contain your content. Encryption keys are generated on your device; your recovery key is not stored on our servers. Shared-space encryption allows authorized participants to access shared content. Content stored on our network remains end-to-end encrypted.

When you switch to local-only mode or your own network, content created after that change is not stored on our network. Section 8 explains deletion of content stored on our network.

Connected services. When you connect an external service, the App stores connection information, such as the account identity, granted permissions and credentials needed to maintain access. Refresh credentials can synchronize between your devices through end-to-end encrypted account storage. Your devices use these credentials to obtain temporary access tokens and make requests to the service. Disconnecting a service does not delete content previously imported or used in conversations.

What encryption protects. Your authorized devices decrypt content for use in the App. Any Association cannot read the plaintext content held in encrypted network storage. Account and network metadata, and information you send directly to us for support, are handled separately as described in this policy. Authorized shared-space members can read content shared with them, and an AI provider can read information sent to it. Network encryption does not prevent those disclosures.

Alpha participation. We use information you provide in communications about joining or participating in the test to respond and manage your participation. The current closed alpha has no paid Any plans. AI-provider charges are handled under your separate provider account.

Support and surveys. We receive information you send us, potentially including your email, account identifier and troubleshooting details. If you include an AI prompt or response in a support message, we receive the material you send; normal AI requests do not pass through our servers. Do not send us recovery phrases, passwords, API keys or connection tokens.

Surveys are not linked to your account identifier, although a survey may ask for an email address. Information you publish in our community forum may be visible to anyone.

3. Network information and analytics

When you use our network, we may collect activation dates, usage events, device model, device family, memory size, operating-system information, account and device identifiers, and space and object identifiers. These support authentication, synchronization, deletion, security, troubleshooting and analytics. Registration IP addresses may be retained for up to seven days after account creation to prevent abusive registrations.

This network collection does not apply to activity on your own network or in local-only mode. Separate App analytics still apply in those modes.

App analytics include session lengths and counts; numbers of spaces, objects and blocks; App version, language, network mode and operating system; account and device identifiers; and error information with identifying details removed. These data help us understand usage and improve reliability. Linked identifiers are pseudonymous rather than necessarily anonymous.

Amplitude receives analytics through a proxy that prevents your device's IP address being disclosed to Amplitude. The current App has no analytics opt-out. It does not collect real-time precise location or use cookies. Google is not an App analytics provider. If you select Google for optional AI, it receives and processes your AI requests as described below. Separately, connecting Google services allows the App to make authorized requests to Google as explained in the Google connections subsection.

4. Optional AI and agents

Any currently supports AI using credentials you supply for your selected service. Credentials are managed by the App and can synchronize between your devices through end-to-end encrypted account storage. Requests to a hosted AI service are sent from your device. That service receives the request content. Any's sync network may separately store encrypted copies of conversations and related records.

Agents can use content available to them in Any and information from external services you connect. Access to a connected service depends on the permissions granted to that service. Agents can also create, edit and delete content inside Any. Permissions previously granted to a connected service may remain until revoked.

Agents sometimes ask for confirmation in chat, but do not ask before every action. Within an authorized task, an action can occur without another confirmation and may affect shared content or communications inside the App. Grant access and instructions with this behavior in mind.

Using AI may disclose your prompts, permitted App content and information retrieved from connected services to the selected service. That service needs access to the information sent for processing, even when the same content is encrypted on our sync network. Consider whether selected content includes personal information about you or others.

Information retrieved from connected services, including Google, can be included in AI requests and conversation history. Background assistant processes may use stored conversation history to create memories and summaries using the configured AI service. Imported content, conversation copies and derived records can remain after the external service is disconnected.

The supported integrations are OpenRouter, Anthropic, Google, and OpenAI. With OpenRouter, requests first reach OpenRouter and are then forwarded to a model provider according to the selected model and routing settings. Both OpenRouter and the downstream provider may process the content.

Provider processing is governed by the terms and privacy arrangements applicable to your provider account. Retention, training and human-review practices depend on the provider, service tier, model, and account arrangements. Supplying your own API key does not establish a universal no-training or no-retention commitment. Acknowledging this policy is not a blanket consent to additional processing by a provider.

The role of each recipient depends on the service and applicable agreement; the AI services you select are not automatically acting as Any Association's subcontractors.

Google connections

What the App accesses and why. Google connection features are being tested in the closed alpha; availability depends on your App version and test access. Connecting a Google account lets the App access information permitted by your Google authorization and the features you use. This can include your account email to identify the connection, Gmail message content and metadata, calendar and event information, and Google Drive file information and document text. These data support reading, search, selected imports and assistant features. Review the permissions shown by Google and your existing grants in Google Account settings. Earlier grants can remain until revoked.

Imports and sharing. Authorizing a connection does not itself start a recurring import. When you import information or enable a recurring import, the resulting content is stored in the destination Any space, where authorized members may access it. Review that space and its members before importing. Importing information into Any does not change permissions on the original Google item. The connection does not provide general continuous synchronization of all Drive files, and deleting an item in Google does not guarantee that an earlier copy in Any is removed.

AI processing. Google information retrieved for an assistant task can be sent to the configured AI service and retained in conversation history. The AI processing and background memory and summary behavior described above also apply to that history. End-to-end encryption of network storage does not protect information while a selected AI service processes it. Review the service, routing and account arrangements before using a connected account with AI.

Your controls. You can disconnect Google in the App or remove Any's access in your Google Account's third-party connections. The App attempts to revoke the Google grant when you disconnect and reports if revocation is not confirmed. Disconnection and revocation are separate from stopping recurring jobs and deleting previously stored content; Section 8 explains the copies that may remain. For connection support contact a@any.org; for privacy requests contact gdpr@anytype.io.

5. Purposes and legal grounds

We use information to manage and maintain the closed alpha, respond to support requests, improve security and reliability, understand usage, conduct surveys, prevent abuse, enforce our terms and address disputes. When you connect an external service, the App also processes the information needed to maintain that connection and provide the reading, search, import and assistant features you use.

Where the GDPR applies, the legal grounds for these activities are:

• Contract: processing necessary to provide services you request, including account and test-access functionality and related support.
• Legitimate interests: operating a reliable and secure test, understanding usage, investigating errors, evaluating feedback, preventing misuse, enforcing our terms and handling claims, to the extent those interests are not overridden by your rights and interests.
• Legal obligations: records and disclosures required by applicable law.
• Consent: specific processing for which consent is required and obtained. Where we ask for consent, the request explains its purpose. You can withdraw consent without affecting the lawfulness of earlier processing.

Acceptance of our Terms or acknowledgment of this policy does not automatically constitute consent to every use of personal information. You can contact us about the legal grounds for processing and exercise applicable rights, including the right to object, as described in Section 10.

6. Recipients

We use service providers subject to confidentiality and appropriate contractual restrictions. Our service providers include:

We also use contractors and infrastructure providers to operate and support the service. Your selected AI service and, for OpenRouter, downstream model providers receive request content as described in Section 4. Shared-space participants receive content you share with them or authorize an agent to share through actions available in the App, including imported information from connected services.

We may disclose information we hold to affiliates and contractors supporting the service or where required by law, court order or legal process. We make reasonable efforts to notify you of legally required disclosures unless prohibited. A legal request does not give us the ability to decrypt encrypted content on our network.

7. International processing

Our sync and backup network operates in Switzerland and the European Union. Service-provider processing includes the United States. AI processing locations depend on your chosen service, downstream providers and account arrangements.

International processing is subject to applicable data-protection law. Depending on the destination and recipient, relevant safeguards include adequacy decisions or recognized standard contractual clauses, with additional measures where required. Contact gdpr@anytype.io for information about the destinations and safeguards applicable to your data.

8. Retention and deletion

We retain personal information only for as long as needed for the purposes described in this policy or to meet applicable legal obligations. We determine retention according to the category of information, your use of the App, outstanding requests or incidents, and legal requirements:

• Encrypted content: content is stored to provide the synchronization and backup features you use. Contact gdpr@anytype.io to request account deletion or information about the relevant content and device-side removal steps. Deleting network content is separate from deleting local traces, derived records and copies held by other recipients.
• Google connection credentials: credentials are retained to maintain your authorized connection. Disconnect removes the stored refresh credential and initiates revocation with Google. Devices that are offline may not immediately receive synchronized changes; removing access in Google Account settings provides an additional way to revoke the grant.
• Google content and derived records: imported content, conversation copies and derived records can remain after disconnection or deletion of the original Google item and require separate removal. Recurring imports must be stopped to prevent information being imported again. Shared-space members and external recipients may retain copies they already received.
• Local diagnostics: execution records help review and troubleshoot assistant operations. Detailed local traces can contain Google API responses, including information omitted from the result displayed in a chat. The current default cleanup ages for trace bodies are 60 days for conversations and 30 days for other runs. These are cleanup thresholds, not guaranteed deletion deadlines. Run summaries can include content, synchronize through an encrypted Any space and have no automatic expiry; interrupted runs or other records may require separate cleanup. Disconnecting Google does not clear these records.
• Registration IP addresses: up to seven days after account creation for registration-abuse prevention.
• Account metadata: while needed to operate your account, authenticate devices, manage participation and complete account-deletion requests. Limited records may be kept longer where needed for an unresolved security incident, dispute or legal obligation.
• Analytics and errors: while needed to evaluate feature usage and reliability, investigate faults and assess whether fixes resolve them. When account or device identifiers are no longer needed for these purposes, we delete them or convert the information into a form that no longer identifies you.
• Support, surveys and communications: while needed to respond to the request, evaluate the feedback or administer the communication. Relevant records may be retained for follow-up issues or disputes; communication preferences may be retained to respect your choices.
• Legal records: where necessary to comply with a legal obligation or establish, exercise or defend a claim, for the applicable statutory period or until the matter is resolved and retention is no longer necessary.

Deleting encrypted content from our network is distinct from deleting these separate records. It does not automatically delete copies already held by shared-space participants, public blockchain records, or information already sent to an AI service. The service's account controls and retention arrangements apply to information it holds. Contact us if you need help understanding what an account-deletion request covers, including information stored on your devices.

A Google-data deletion request can cover imported items, conversation history, derived records and diagnostic traces. Contact gdpr@anytype.io for help identifying the relevant copies and device-side steps. We cannot remotely decrypt your encrypted content or erase independent copies held by other space members. Information already sent to an AI provider is also subject to that recipient's applicable deletion and retention controls. Do not send recovery phrases, passwords, API keys or OAuth tokens with a request.

9. Security

We use measures designed to protect information against loss and unauthorized access, use, alteration or disclosure. Our ability to protect information also depends on your device security. Some local data may be unencrypted on disk; use device encryption and protect access to your device.

The closed alpha is experimental and may have defects that result in data loss, corruption, unavailability, or unauthorized disclosure. Keep independent copies of important information. The Terms of Use explain these testing risks. Alpha status does not remove our obligations under applicable data-protection law or turn acknowledgment of this policy into a waiver of your rights.

Keep your recovery phrase safe. We cannot recover the phrase for you or restore access if you lose both your key and other means of accessing your account. Network encryption does not protect content you separately send to an AI service or disclose to another person. Report security concerns to security@anytype.io.

10. Your rights

Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal information; object to processing; withdraw consent; and complain to the competent supervisory authority, including the Swiss Federal Data Protection and Information Commissioner.

You may also have protections concerning decisions based solely on automated processing that produce legal or similarly significant effects. The App's AI features involve automated processing; that does not by itself mean every agent action is such a decision.

Contact gdpr@anytype.io to exercise your rights. Requests concern information within our control; contact your selected AI service about information it holds.

11. Age and policy changes

The closed alpha is for people aged 18 or older. We do not knowingly collect personal information from children through the App. Contact us if you believe a child has provided personal information contrary to this requirement so that we can address it.

We will update this policy when practices or requirements change, identify its effective date, and provide notices required by law. Previous versions will remain available. See the policy effective 13 September 2026.

12. Contact

Any Association
c/o Sielva Management AG
Gubelstraße 11
CH - 6300 Zug, Switzerland
gdpr@anytype.io

Our EU representative is Anylab Gmbh, Meinekestraße 27, Berlin, 10719, Deutschland. Email: gdpr@anytype.io.