← Back to home

Privacy Policy

Last updated: April 2026

1. Introduction

This Privacy Policy describes how PocketBot (“we”, “us”, or “our”) collects, uses, and protects your information when you use the PocketBot mobile application (the “App”). PocketBot is developed and operated by PocketBot Ltd.

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

Contact: For privacy inquiries, email anton.may@new.ox.ac.uk

2. Information We Collect

2.1 Account Information

PocketBot does not require an email address, password, or any personal registration. Your account is created automatically using:

  • User ID — a randomly generated unique identifier (UUID), not linked to your identity
  • Device ID — an app-generated UUID (not your device's hardware identifier or IMEI)
  • Platform — iOS or Android
  • Timestamps — when your account was created and last active

2.2 Chat Messages

When you use the chat interface to create automations, your messages are sent to our server and forwarded to a third-party AI service (see Section 5.1). We do not retain your chat messages after processing.

2.3 Automation Data

When you create automations (“pocks”), we store:

  • Automation title, description, and JavaScript source code
  • Trigger configuration (schedule, webhook, location, chain)
  • Required service connection identifiers
  • Execution logs: timestamped records of automation runs, kept in a circular buffer of up to 1,000 entries per automation (older entries are automatically overwritten)

2.4 Subscription Data

We store your subscription plan tier and Apple transaction identifiers for the purpose of verifying your purchase and determining your plan level. We do not receive or store any payment or billing information (see Section 7).

2.5 Device Data

PocketBot accesses device data only when your automations require it. We do not passively collect device data in the background. Data types that may be accessed include:

Data TypeWhat We AccessHow It's Used
ContactsNames, phone numbers, emailsLook up contacts referenced in automations
CalendarEvent titles, times, descriptionsCalendar-based automation triggers
HealthStep count, distance, caloriesHealth-based automation triggers
LocationLat/lon (50m foreground, 500m background)Location-based automation triggers
MessagesSMS compose (iOS); read/send (Android)Messaging automations
Camera & PhotosPhoto capture, gallery access, OCRImage-based automations
BluetoothPaired device names, connection statusDevice-based automation triggers
MicrophoneSpeech-to-text (processed on-device)Voice input for creating automations
Device InfoBattery, network, model, OS versionDevice state-based automations

On iOS, SMS messages cannot be sent programmatically. The App opens the native message compose sheet, and you must manually tap Send.

Background location: Location data may be collected in the background when you have configured a location-based automation trigger. Continued use of GPS running in the background can decrease battery life. You can disable background location at any time in your device's Settings app.

Apple HealthKit data: Health data accessed via Apple HealthKit is used solely to power the automation triggers you configure. HealthKit data is not used for advertising or marketing purposes, is not sold to data brokers or any third parties, is not shared with third parties (including AWS Bedrock or any AI service), and is not used to determine insurance eligibility, lending decisions, or for any purpose other than the automation triggers you configure within the App.

2.6 Data Stored Only on Your Device

The following data is stored locally and never transmitted to our servers:

  • Authentication tokens (stored in iOS Keychain via encrypted storage)
  • App preferences (theme, server URL, onboarding state)
  • Local automation analytics (run counts, success rates)
  • OAuth tokens for directly-connected services (Google, Monzo)

2.7 Information We Do Not Collect

  • No email addresses or passwords
  • No browsing history
  • No installed app lists
  • No hardware identifiers (IMEI, serial numbers)
  • No third-party analytics or tracking (no Firebase Analytics, Amplitude, or similar)
  • No advertising identifiers or advertising SDKs
  • No biometric data (fingerprint, face geometry)
  • No financial or payment information (see Section 7)

3. How We Use Your Information

  • Provide the automation service — creating, running, and scheduling your automations
  • Authenticate your device — maintaining your session with our server
  • Connect third-party services — managing OAuth connections you initiate (via Nango)
  • AI-assisted automation creation — your chat messages are sent to a third-party AI service (AWS Bedrock, operated by Amazon Web Services) to generate automation code; this only occurs after you provide explicit consent (see Section 5.1)
  • Verify purchases — Apple transaction data is validated via RevenueCat to determine your subscription tier
  • Maintain execution logs — enabling you to review automation results and debug issues

4. How We Store and Protect Your Data

4.1 Server Storage

Your automation data is stored on our server, organised by your anonymous User ID. Data is encrypted in transit. Server access is restricted to authorised personnel only.

4.2 Data Location and International Transfers

Your automation data is stored on servers located in Europe and the United States. Our third-party service providers (AWS Bedrock, Nango, RevenueCat) may also process data in the United States.

If you are located in the European Economic Area (EEA), transfers of your data to the United States are protected by Standard Contractual Clauses (SCCs) approved by the European Commission, or by the provider's participation in equivalent data protection frameworks. These safeguards ensure that your data receives a level of protection equivalent to that provided within the EEA.

4.3 On-Device Storage

Sensitive data (authentication tokens, OAuth credentials) is stored in iOS Keychain via Flutter Secure Storage, which provides hardware-backed encryption. Non-sensitive preferences use standard app storage.

4.4 Authentication Security

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

5. Third-Party Services

5.1 Third-Party AI Processing (AWS Bedrock)

PocketBot uses a third-party AI service to create automations from your chat messages. Before any data is sent, the app asks for your explicit permission via an in-app consent screen.

5.1.1 Who receives your data

Your data is sent to Amazon Web Services (AWS) Bedrock, a cloud AI service operated by Amazon Web Services, Inc. AWS Bedrock hosts the AI models (Anthropic Claude) that process your requests. See AWS Privacy Policy and AWS Service Terms.

5.1.2 What data is sent

When you use the chat feature to create or modify automations, the following data is sent to AWS Bedrock:

  • Your chat messages — the text you type in the chat interface describing the automation you want
  • Automation source code — JavaScript code being generated or edited for your automation
  • Basic device context — your timezone and, if relevant to the automation, approximate location
  • Connected account identifiers — the names or email addresses associated with your connected services (e.g. your Gmail address), so the AI can personalise automations to your accounts

5.1.3 What data is never sent to the AI service

  • Your passwords, OAuth tokens, or API credentials
  • Your real name (unless it appears in a connected account label you authorised)
  • Content from your connected services (emails, messages, files, etc.)
  • Your contacts, calendar, health data, or photos
  • Any hardware identifiers

5.1.4 How your data is used by the AI service

  • Your data is processed solely to generate automation code in response to your request
  • Your data is not used to train AI models
  • Your data is not retained by AWS Bedrock after processing is complete
  • AWS Bedrock provides the same or greater level of data protection as described in this policy

5.1.5 Your consent

The app displays a consent screen the first time you use the chat feature, clearly explaining what data will be sent and to whom. You must tap “I Agree” before any data is sent to the AI service. No data is sent to the AI service until you have reviewed and accepted this consent.

Important: AI processing is a core feature of PocketBot. By accepting the consent screen and using the app, you agree to your chat messages being processed as described above.

5.2 Nango (OAuth & API Proxy)

When you connect third-party services (Gmail, Slack, GitHub, etc.), PocketBot uses Nango to manage OAuth tokens and proxy API requests. Nango receives:

  • Your anonymous User ID
  • Connection identifiers
  • API requests to your connected services (only when your automations run)

We do not store your OAuth tokens directly; they are managed by Nango. See Nango's Privacy Policy.

5.3 RevenueCat (Subscription Verification)

PocketBot uses RevenueCat to verify in-app purchases and manage subscription entitlements. RevenueCat receives:

  • An app-generated User ID (not linked to your identity)
  • Apple transaction receipts (forwarded by Apple's StoreKit)
  • Your subscription plan tier and expiration date

RevenueCat does not receive your name, email, payment details, or any other personal information. See RevenueCat's Privacy Policy.

5.4 Connected Service APIs

When you connect services like Gmail, Google Calendar, Slack, GitHub, Discord, Notion, Linear, Spotify, or others, PocketBot accesses those services through OAuth with the permissions you authorise. Data is accessed only when your automations run, and only within the scopes you granted. Each service has its own privacy policy.

5.5 Tally.so (Waitlist)

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

6. Data Sharing and Disclosure

  • We do not sell your personal data
  • We do not share data with advertisers
  • We do not use third-party analytics or tracking SDKs
  • Data is shared with third-party services only as described in Section 5, solely to provide the automation service. These third parties are: AWS Bedrock (AI processing), Nango (OAuth proxy), RevenueCat (subscription verification), and the connected service APIs you authorise (Gmail, Slack, etc.)
  • Each third-party service listed above provides the same or equal protection of your data as described in this policy
  • We may disclose data if required by law, legal process, or to protect the rights and safety of our users

7. In-App Purchases

PocketBot offers subscription plans managed through Apple's in-app purchase system (StoreKit). All payment information is collected and processed entirely by Apple. We do not receive or store your credit card number, billing address, or other payment details. We receive only a transaction receipt confirming your subscription status and plan tier.

See Apple's Privacy Policy for details on how Apple handles payment data.

8. Children's Privacy

PocketBot 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 learn that we have collected data from a child under these ages, we will delete it promptly. If you believe a child has provided us with data, please contact us at anton.may@new.ox.ac.uk.

9. Your Rights and Choices

9.1 Access Your Data

You can view all your automations and execution logs within the App. Contact us to request a full export of your server-side data.

9.2 Delete Your Data

  • Delete individual automations and their logs from within the App
  • Delete your entire account from Settings, which permanently removes all server-side data, connected service credentials, and local app data

9.3 Revoke Permissions

  • Device permissions (camera, contacts, location, etc.) can be revoked at any time through your device's Settings app
  • Third-party service connections can be disconnected from within PocketBot's Settings

9.4 AI Processing

AI processing is a core part of how PocketBot creates automations. By using the app and accepting the in-app data sharing consent, you agree to your chat messages being processed by the third-party AI service described in Section 5.1.

10. GDPR Rights (European Economic Area)

10.1 Legal Basis for Processing

Under Article 6 of the GDPR, we process your data on the following legal bases:

  • Contract performance (Article 6(1)(b)) — processing necessary to provide the automation service you have requested, including creating and running automations, AI-assisted automation generation, and managing your account
  • Legitimate interest (Article 6(1)(f)) — maintaining security logs, preventing fraud, tracking revoked tokens, and ensuring the reliability of the service
  • Consent (Article 6(1)(a)) — accessing device capabilities (contacts, calendar, health, location, camera, microphone, Bluetooth) as explicitly permitted by you through system permission prompts

10.2 Your Rights

If you are located in the European Economic Area, you have the following rights under the General Data Protection Regulation:

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

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

11. Data Retention

  • Chat messages — not retained after processing; used only to generate automations and then discarded
  • Automation data — retained until you delete your account or individual automations
  • Execution logs — circular buffer, max 1,000 entries per automation; older entries are automatically overwritten
  • Subscription data — retained for as long as your account is active
  • Authentication tokens — access tokens expire after 30 days; refresh tokens expire after 365 days
  • Revoked token records — maintained for security purposes

12. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the “Last Updated” date at the top and may notify you through the App. Your continued use of PocketBot after changes constitutes acceptance of the updated policy.

13. Contact Us

If you have questions about this Privacy Policy or wish to exercise your data rights:

We aim to respond to all inquiries within 30 days.