Privacy Policy

1. Who we are

arxi ("arxi", "we", "us") is a delegated-intelligence assistant that operates inside messaging channels. It is built and run by arxi lab, a small independent project based in Barcelona, Spain. For anything about your privacy, write to privacy@arxi.me — the full legal and contact details of the data controller are at the end of this Policy (Section 14).

Because arxi is operated from Spain and processes data on infrastructure located in the European Union, this Policy is written to comply with the EU General Data Protection Regulation (GDPR) and Spanish data-protection law (LOPDGDD). It applies to all users regardless of where they are located.

2. Scope

This Policy explains what personal data arxi collects, why, who we share it with, how long we keep it, and the rights you have. It covers the arxi iOS app, Telegram bot, connected services, and the arxi.me website.

3. What data we collect

3.1 Identity & account data. An arxi account identifier, a channel identifier where applicable (for example, your Telegram user ID), and the email address and plan label returned after you approve OpenAI authorization. We do not receive your OpenAI password. The iOS app stores only opaque arxi session tokens in the iOS Keychain.

3.2 The content you send to arxi. The messages, questions, instructions, and files you send. arxi is an assistant, so by design it processes the content of your conversations in order to answer and act on them.

3.3 Memory ("what arxi remembers about you"). To be useful over time, arxi maintains a private memory profile derived from your conversations (facts, preferences, reminders, contacts, and similar). This memory is private to you and is never made public. It is stored in your personal workspace and can be inspected, exported, or deleted by you (see Section 8). This processing may include building a profile of your preferences; we describe it transparently here for that reason.

3.4 Workspace files (Vault). Files you upload or that arxi creates on your behalf are stored in your personal workspace ("Vault").

3.5 Connected-service data. If you choose to connect Google Calendar, arxi receives the calendar list and access roles, event details, and free/busy information needed to answer your calendar questions and perform the calendar actions you request. This can include event titles, descriptions, times, locations, attendees, conference links, and the names of calendars shared with you. We also store the OAuth tokens needed to keep the connection working; those credentials are encrypted.

3.6 Usage & billing data. Subscription tier and status, plus language-model usage metadata (such as token and estimated-cost counts) for reliability and reporting. In the iOS app, model usage is supplied by the ChatGPT subscription you connect and is not billed by arxi. Any separate arxi service payment is handled by our payment provider; card details are never stored by arxi.

3.7 Technical, notification & analytics data. Limited metadata needed to run and improve the service: timestamps, model/route, latency, token counts, explicit app interaction events, a pseudonymous account identifier, an ephemeral random website-page identifier, push tokens, crash reports, performance data, and error events. The website identifier lives in page memory and is sent with explicit PostHog events; after a Telegram CTA it may also be held by arxi in a one-use attribution handoff. That handoff expires after 15 minutes and is deleted on use or by a cleanup pass within the following minute. Website analytics use no cookies, automatic page/DOM capture, input capture, heatmaps, or session replay, and honor browser Do Not Track and Global Privacy Control signals. We do not send the text of your messages to PostHog or Sentry and do not log message text in our operational logs. Chat content is still stored as conversation history and processed to provide the assistant, as described above.

4. Why we use your data, and our legal bases

We do not sell your personal data, and we do not use the content of your conversations to train our own models.

5. Who we share data with (providers and connected services)

arxi relies on a small number of third-party providers. Some are used for core processing; others are only used when arxi performs a specific action you asked for ("tool-time"). Each receives only the data needed for its function.

Core processing (used to operate the service)

Tool-time processing (only when arxi performs that action for you)

Google API Services User Data

arxi's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements. We use Google Calendar data only to provide or improve the user-facing calendar features you request. We do not sell Google user data, use it for advertising, or use it to train generalised or non-personalised AI or machine-learning models. We do not transfer Google user data except as necessary to provide those requested features, for security, or to comply with applicable law. Humans do not read your Google Calendar data unless you give explicit permission for support, security, or legal purposes.

Calendar event details may appear in the conversation or private memory when that is necessary to answer your request or remember something you asked arxi to retain. You can disconnect Google Calendar at any time; this revokes or removes the stored connection credentials. Disconnecting does not automatically erase calendar details already included in your conversation or private memory, which you can delete using the controls in Section 8.

We enter into data-processing agreements with our processors where required by GDPR Art. 28. The list above reflects services that are active. We do not enable optional/legacy providers without updating this Policy.

6. International data transfers

Your data is stored at rest in the European Union (Hetzner, Germany).

However, some processing is performed by providers that may process data outside the EU (for example, OpenAI, Apple, Expo, Sentry, Google, Browserbase, and X are headquartered outside the EU or may route requests through non-EU regions). Where data is transferred outside the EEA, we rely on the European Commission's Standard Contractual Clauses (SCCs) and the providers' applicable transfer frameworks (e.g. the EU–US Data Privacy Framework where the provider is certified).

7. How long we keep your data

• Conversation content & memory: kept for as long as your account is active, so arxi can remember and assist you. You can delete it at any time (Section 8).
• iOS local data: conversation history and the outgoing queue remain on the device until account deletion, logout where applicable, or removal of the app.
• Voice recordings: local originals used for retry and playback are kept for at most 30 days. An uploaded recording that has not been consumed is removed from our server after at most 7 days; a consumed original is removed after at most 30 days. Cancelling removes the unsent local copy; logging out removes local copies and revokes that device session but does not shorten the server limits above. Account deletion removes the recording and its linked transcript immediately.
• Push registrations: kept while notifications are enabled or the account remains active.
• Google Calendar connection: OAuth credentials are kept until you disconnect Calendar or delete your arxi data. Calendar data is fetched when needed; details included in conversations or memory follow the retention rule above.
• Operational metadata/logs: kept for a limited period for security and debugging, then rotated.
• Billing records: kept as required by applicable tax and accounting law.

When you delete your data or close your account, your workspace, memory, and files are removed and the running environment is destroyed.

8. Your rights

Under the GDPR you have the right to: access your data; correct it; delete it ("right to be forgotten"); restrict or object to processing; data portability; and to withdraw consent.

arxi gives you direct, self-service control:

• iOS Settings → Delete account and data — deletes your iOS account record, conversation history, workspace, memory, files, push registrations, and OpenAI connection.
• /pleasedeletemydata in Telegram — deletes that channel's workspace, memory, and files, and destroys its environment.
• You can ask arxi to show or export what it remembers about you at any time.

To exercise any right, use the in-product commands above or contact privacy@arxi.me. You also have the right to lodge a complaint with the Spanish supervisory authority, the Agencia Española de Protección de Datos (AEPD), or your local EU authority.

9. International users and regional rights

arxi is available to users outside the European Union. Because arxi is operated by an EU-based controller on EU infrastructure, this Policy and the GDPR standard apply to all users, wherever you are located. We do not apply a lower standard to non-EU users.

Some regions grant additional rights, which we honour where they apply:

California residents (CCPA/CPRA). You have the right to know what personal information we collect and how we use it (described above), to request access to or deletion of your personal information, and to be free from discrimination for exercising these rights. We do not sell your personal information, and we do not share it for cross-context behavioural advertising. To exercise these rights, contact privacy@arxi.me or use /pleasedeletemydata.

Other jurisdictions (e.g. the United Kingdom, Brazil, Canada) have data-protection laws that closely mirror the GDPR; the rights and protections described in this Policy are intended to satisfy them. If a mandatory local right applies to you and is not covered above, contact us and we will honour it where legally required.

10. Security

All connections to external services use encryption in transit (HTTPS/TLS). Each user runs in an isolated virtual machine; environments are not reused between users. Credentials you store are kept encrypted, and the model never sees raw provider credentials (they are proxied). Memory and files are private to your workspace.

11. Public prompt, private memory ("Verified AI")

A core principle of arxi: the instructions that define arxi's behaviour (its "prompt") are public and verifiable — published with a hash and a changelog. What arxi knows about you is the opposite: it is private to you and never published. Transparency applies to how arxi behaves; privacy applies to your data.

12. Children

arxi is not directed to children under 16 (or the minimum age of digital consent in your country). We do not knowingly collect data from children below that age.

13. Changes to this Policy

We may update this Policy. Material changes will be announced through the service. The "Last updated" date at the top reflects the current version.

14. Contact

Questions or requests: privacy@arxi.me

Data controller: Trofim Pochinkov, trading as arxi lab. Privacy and legal notices can be sent to the addresses above.

the mind is public. the memory is yours.