← Back to home

Privacy Policy

Last updated: May 2026

1. Introduction

This Privacy Policy describes how Cantic Ltd, a company registered in the United Kingdom (“Cantic”, “we”, “us”, or “our”), collects, uses, stores, and discloses information in connection with your use of the PocketBot mobile application (the “App”). PocketBot is a service provided by Cantic Ltd. This policy applies to all users of the App and forms part of the agreement between you and Cantic.

The nature of the App is material to the scope of this policy. PocketBot is a personal assistant that, subject to your authorisation, connects to third-party services you already use — including email, calendar, messaging, and document services — ingests the activity and content within them, processes that material into summaries (“briefings”) and a curated list of items that may require your attention, and, on your instruction, performs actions on your behalf. The provision of these functions necessarily requires the receipt, storage, and processing of a substantial volume of your personal information. This policy sets out those arrangements in full.

By using PocketBot, you consent to the collection and use of information as described in this policy. If you do not agree to these terms, you should not use the App.

Contact: For any privacy enquiry, contact anton.may@new.ox.ac.uk.

2. Information We Collect

2.1 Pseudonymous Account Identifiers

The App does not require an email address, password, or other personal registration. Your account is generated automatically from a limited set of non-identifying identifiers:

  • User ID — a randomly generated identifier (UUID) that represents you without disclosing your identity
  • Device ID — an application-generated UUID, which is not your hardware serial number, IMEI, or advertising identifier
  • Platform — iOS or Android, recorded to provide platform-appropriate behaviour
  • Timestamps — the dates on which your account was created and last active

Your workspace and its contents are organised under this pseudonymous identity. We do not independently hold your real-world name unless it appears within content you elect to connect, as described in Section 2.2.

2.2 Content from Connected Services

This is the most significant category of information we process. When you authorise the App to connect to a third-party service — for example Gmail, Google Calendar, Google Drive, Slack, Outlook, or Notion — the App ingests the relevant activity and content from that service onto our server. Depending on the service and the access scopes you grant, this may include:

  • Incoming and recent emails, including sender, recipients, subject lines, and message bodies or excerpts
  • Calendar events, including titles, times, descriptions, and the identities (often email addresses) of attendees
  • Chat and messaging activity, including channels, authors, and message text
  • Documents, spreadsheets, presentations, and files that you direct the assistant to read
  • Associated metadata, including identifiers, timestamps, and the source of each item

Connected-service content is recorded as discrete events in our database and is retained so that your briefings remain consistent over time and the assistant has the context required to function. For the avoidance of doubt, the substantive contents of your connected services are received by our server and transmitted to an artificial-intelligence service for processing, as described in Section 4.

2.3 Briefings, To-Do Items, and Profile Data

The App does not merely store ingested content; it processes that content to generate derived outputs. On a recurring basis, the App synthesises your connected-service activity into the following:

  • A briefing — a periodically updated summary of activity across your connected services
  • To-do items — a curated, prioritised, and categorised list of items that may require your attention, each retaining a reference to the source material (which may include participant email addresses) from which it was derived
  • A “soul” profile — an evolving, AI-generated profile of you. This is a summary of limited length describing, in the assistant's own terms, your apparent characteristics, communication style, observed patterns, the people of significance to you, and the broader context of your activity. Its sole purpose is to enable the assistant to operate with continuity and relevant context.

These outputs are derived from your data and are stored on our server under your pseudonymous identity. They are used solely for your benefit and for the operation of the assistant.

2.4 Action Agent Activity

When you instruct the App to perform an action — such as drafting a reply, sending an email, posting a message, scheduling an event, or creating a document — it invokes an autonomous action agent. To carry out the instruction, this agent may access fuller content from your connected services than is required for a briefing (for example, the complete body of an email thread rather than an excerpt) and compose the corresponding action.

Actions that alter anything in the outside world are subject to your approval. The agent proposes an action, and you determine whether it proceeds. We record information relating to this process — including logs of agent runs, the permissions you have granted or withheld for particular categories of action, and records of computational usage — in order to maintain an auditable record, to give effect to your preferences, and to operate the service reliably.

2.5 Subscription Status

We store your subscription plan tier and the opaque transaction identifiers necessary to verify your purchase and determine your entitlements. We do not receive or retain any payment or billing information (see Section 8).

2.6 Optional Device Permissions

In addition to your connected services, and only with the device permissions you expressly grant, the App may access certain signals from your device to provide the assistant with additional context. Each is optional, individually revocable, and used solely to provide relevant context to the assistant:

SignalWhat We AccessPurpose
LocationApproximate or precise coordinatesTo provide the assistant with geographic context for the items it surfaces and the actions you request
MicrophoneSpeech you dictate, transcribed on-deviceTo enable voice input to the assistant; raw audio is not transmitted to our server
NotificationsPermission to deliver push and local notificationsTo notify you of briefings, proposed actions awaiting your approval, and time-sensitive items

Background operation: on Android, the App may run a foreground service to maintain its connection to our server. Where it does so, the operating system displays a persistent notice. You may disable any of these signals at any time by revoking the corresponding permission in your device settings.

2.7 Information Retained Only on Your Device

The following data is held locally on your device and is not transmitted to our servers:

  • Authentication tokens (stored within the iOS Keychain using hardware-backed encrypted storage)
  • Credentials for services you connect directly on the device, such as Google or Monzo authorisation tokens, held in encrypted secure storage
  • Application preferences (theme, server endpoint, onboarding state)
  • Device permission state and local preferences

2.8 Information We Do Not Collect

  • No account email addresses or passwords
  • No browsing history
  • No record of other applications installed on your device
  • No hardware identifiers (IMEI, serial numbers)
  • No third-party analytics or behavioural tracking of any kind, including Firebase Analytics, Amplitude, or comparable telemetry software development kits
  • No advertising identifiers and no advertising SDKs
  • No biometric data (fingerprint or facial geometry)
  • No financial or payment card information (see Section 8)

3. Purposes of Processing

We process your information for the following purposes:

  • To operate the assistant — ingesting connected-service activity, generating briefings, curating to-do items, and maintaining your profile
  • To perform the actions you request — accessing the content necessary to complete a task and executing approved actions on your connected services
  • To authenticate your device — maintaining your session with our server
  • To facilitate your connections — establishing and maintaining the OAuth authorisations you initiate (via Composio and Nango)
  • To perform AI-driven processing — transmitting your data to our AI provider (AWS Bedrock) for the synthesis and action described in this policy (see Section 4)
  • To verify purchases — validating transaction data via RevenueCat to determine your subscription tier
  • To maintain security and reliability — maintaining audit logs of agent activity, giving effect to your action permissions, preventing abuse, and recording computational usage

4. Artificial Intelligence and Automated Processing

The App's functions depend on large language models, which are not run on your device but are invoked in the cloud. This section describes that processing.

4.1 AI service provider

The AI processing is performed by Amazon Web Services (AWS) Bedrock, a managed cloud service operated by Amazon Web Services, Inc., which hosts the Anthropic Claude family of models used by the App. This processing takes place in AWS data centres in the United States. Refer to the AWS Privacy Notice and the AWS Service Terms.

4.2 Data transmitted to the models

To perform its functions, the App transmits to AWS Bedrock the material the models require to process your information. This may include:

  • Summaries and excerpts of your connected-service activity, such as email senders, subjects, and snippets; calendar titles, times, and attendees; and message authors and text
  • Where you request an action, the fuller content relevant to that task, such as complete email threads or document text
  • Your “soul” profile, your existing to-do items, and your prior briefing, provided as context
  • The identifiers (frequently email addresses) of individuals appearing in the foregoing

4.3 Recurring synthesis

On a regular basis, a Claude model reviews your latest activity against your stored context and produces an updated briefing, amends your to-do list (creating, closing, or reprioritising items), and updates your “soul” profile.

4.4 Action agent

When you instruct the App to act, a Claude model operating as an autonomous agent accesses the content it requires, formulates the proposed action, and — subject to your approval for any action that alters the outside world — executes it through your connected services.

4.5 Training, retention, and consent

  • Your data is processed by AWS Bedrock solely to generate the outputs requested by the App on your behalf
  • Your data is not used to train the underlying AI models
  • AWS Bedrock does not retain your prompts or outputs after a request has been served

Consent to AI processing: AI-driven processing of your connected-service content is integral to the operation of the App. By connecting a service and using the App, you consent to that content being processed as described in this section. If you do not wish such processing to occur, do not connect the relevant service.

5. Storage, Security, and Data Location

5.1 Where your data is stored

Your workspace — comprising ingested events, briefings, to-do items, your “soul” profile, connection records, action logs, and preferences — is stored in a managed PostgreSQL database, organised under your pseudonymous User ID. Data is encrypted in transit, and server access is restricted to authorised personnel.

5.2 International transfers

Your data may be stored and processed in Europe and the United States. Our sub-processors, including AWS Bedrock, Composio, Nango, and RevenueCat, may process data in the United States.

Where you are located in the European Economic Area (EEA), transfers of your data to the United States are safeguarded by Standard Contractual Clauses approved by the European Commission, or by a provider's adherence to an equivalent data-protection framework. These measures are intended to ensure that your data receives a level of protection substantially equivalent to that guaranteed within the EEA.

5.3 On-device storage

Sensitive material held on your device — including authentication tokens and the OAuth credentials for services you connect directly, such as Google and Monzo — is stored within the iOS Keychain by means of Flutter Secure Storage, which provides hardware-backed encryption. Non-sensitive preferences are stored using standard application storage.

5.4 Authentication security

  • Device-based JWT authentication (no passwords are stored)
  • Access tokens expire after 30 days
  • Refresh tokens expire after 365 days
  • Revoked tokens are recorded server-side to prevent reuse

6. Third-Party Services and Sub-Processors

The App relies on a limited number of external providers. Each receives only the information required to perform its function and is contractually obliged to protect your data.

6.1 AWS Bedrock (Artificial Intelligence)

Receives your connected-service content, context, and requests in order to perform the AI processing described in Section 4. Does not train on your data and does not retain it after processing.

6.2 Composio and Nango (Connection Brokers and API Proxies)

When you connect third-party services, the App uses Composio and/or Nango to conduct the OAuth authorisation process, to hold the resulting access tokens, and to proxy API requests to those services. These providers therefore hold the credentials that authorise access to your connected accounts and process the API traffic that passes through them. Refer to Composio's Privacy Policy and Nango's Privacy Policy.

6.3 RevenueCat (Subscription Verification)

Verifies in-app purchases and manages subscription entitlements. RevenueCat receives an application-generated User ID (not linked to your identity), the transaction receipts forwarded by Apple, and your plan tier and expiry. It does not receive your name, email, or payment details. Refer to RevenueCat's Privacy Policy.

6.4 Apple (Purchases and Push Delivery)

Subscriptions are transacted through Apple's in-app purchase system, and push notifications are delivered via the Apple Push Notification service. Apple processes all payments; we do not receive your card details. Refer to Apple's Privacy Policy.

6.5 Connected Service APIs You Authorise

When you connect services — including Gmail, Google Calendar, Google Drive, Google Docs, Sheets, Slides and Tasks, YouTube, Outlook, Slack, Discord, Notion, Reddit, LinkedIn, Strava, Google Maps, and others — the App accesses them through OAuth within the scopes you grant, reading content and performing approved actions. Each such service is governed by its own privacy policy, which you should consult.

6.6 Monzo (Optional Banking Connection)

If you connect Monzo, the App performs the authorisation on your device and stores the resulting credentials in encrypted secure storage on your device. This connection may make financial information, such as balances and transactions, available to the assistant. You should connect it only if you accept this. Refer to Monzo's Privacy Notice.

6.7 WhatsApp (Optional Messaging Connection)

Where offered and enabled, a WhatsApp connection enables the assistant to process messaging activity. You should connect it only if you accept that such content will be handled as described in this policy.

6.8 Tally.so (Website Waitlist)

If you sign up via the waitlist form on our website (getpocketbot.com), your email address is collected by Tally.so. This is separate from the App and is not linked to your PocketBot account. Refer to Tally's Privacy Policy.

7. Disclosure of Data

  • We do not sell your personal data
  • We do not share your data with advertisers
  • We do not use third-party analytics or tracking SDKs
  • Your data is disclosed only to the sub-processors listed in Section 6, and only to the extent necessary to provide the service you have requested
  • Each sub-processor is bound to provide your data with protection consistent with this policy
  • We may disclose data where required by law or legal process, or where necessary to protect the rights and safety of our users or the public

8. In-App Purchases

The App offers subscription plans transacted through Apple's in-app purchase system (StoreKit). All payment information is collected and processed solely by Apple. We do not receive or store your card number, billing address, or any other payment detail; we receive only a transaction receipt confirming your subscription status and plan tier.

9. Children's Privacy

The App is not directed at children under the age of 13 (or 16 in the European Economic Area). We do not knowingly collect personal information from children. If we become aware that we have done so, we will delete it promptly. If you believe a child has provided us with data, contact us at anton.may@new.ox.ac.uk.

10. Your Rights and Choices

10.1 Access to your data

You may review your briefings, to-do items, and connections within the App at any time. To request a comprehensive export of your server-side data, contact us.

10.2 Deletion of your data

  • Disconnect any individual service to stop further ingestion from it
  • Delete your account from Settings, which permanently removes your server-side workspace — including ingested content, briefings, to-do items, your “soul” profile, and associated records — together with your local application data

10.3 Revocation of permissions

  • Device permissions (location, microphone, notifications) may be withdrawn at any time through your device settings
  • Third-party connections may be disconnected from within the App's Settings
  • Action permissions for the agent may be configured so that it must always seek your explicit approval

10.4 AI processing

AI-driven processing of your connected-service content is integral to the operation of the App. By connecting a service and using the App, you consent to that processing as described in Section 4. To decline such processing, do not connect the relevant service.

11. GDPR Rights (European Economic Area)

11.1 Legal bases for processing

Under Article 6 of the General Data Protection Regulation (GDPR), we process your data on the following legal bases:

  • Performance of a contract (Article 6(1)(b)) — processing necessary to provide the assistant service you have requested, including ingesting your connected-service content, generating your briefings and to-do items, maintaining your profile, executing the actions you approve, and managing your account
  • Legitimate interests (Article 6(1)(f)) — maintaining security and audit logs, preventing abuse, recording revoked tokens, and ensuring the reliability of the service
  • Consent (Article 6(1)(a)) — accessing optional device capabilities (location, microphone, notifications) as you expressly permit through system prompts, and connecting each third-party service as you elect. You may withdraw any such consent at any time by revoking the permission or disconnecting the service

11.2 Your rights

If you are located in the European Economic Area, you have the following rights under the GDPR:

  • Right of access (Article 15) — to request a copy of your data
  • Right to rectification (Article 16) — to correct inaccurate data
  • Right to erasure (Article 17) — to request deletion of your data
  • Right to restrict processing (Article 18)
  • Right to data portability (Article 20)
  • Right to object (Article 21)

To exercise any of these rights, contact anton.may@new.ox.ac.uk. We will respond within 30 days.

12. Data Retention

  • Connected-service content, briefings, to-do items, and your “soul” profile — retained for as long as the relevant connection and your account remain active, to maintain continuity; removed when you disconnect the service or delete your account
  • Agent run and action logs — retained to maintain an auditable action history and to give effect to your permissions
  • Subscription data — retained for as long as your account is active
  • Authentication tokens — access tokens expire after 30 days; refresh tokens after 365 days
  • Revoked-token records — retained for security purposes
  • AI prompts and outputs at AWS Bedrock — not retained by the AI provider after a request is served

13. Changes to This Policy

We may revise this Privacy Policy from time to time. Where we make material changes, we will update the “Last updated” date above and may notify you within the App. Your continued use of the App after such changes constitutes acceptance of the updated policy.

14. Contact

If you have questions about this Privacy Policy, or wish to exercise any of your data rights, contact us by the following means:

We will respond to all enquiries within 30 days.