Privacy Policy

1. Introduction

Screenpipe is committed to protecting your privacy. This policy explains how we collect, use, store, share, and delete your data, including data obtained through Google APIs.

2. Data Collection and Storage

By default, 100% of the data collected by Screenpipe stays local on your computer. It is stored in a SQLite database and as MP4 files. You own your data entirely.

3. Types of Data Collected

Screenpipe collects the following types of data:

• Screenshots (with accessibility-based text extraction, OCR fallback)
• Audio recordings (with transcriptions)
• Screen recordings
• Optional pseudonymous website and product analytics, after consent (see Section 4)

When you connect third-party services (see Section 7), Screenpipe may also access data from those services as described below.

5. Data Usage

We process personal data only for the purposes described here and under an applicable legal basis, such as providing the service you requested, your consent, our legitimate interests in security and service reliability, or a legal obligation.

Specifically, your data is used to:

• Power Screenpipe's local AI features (search, chat, automation)
• Display your screen history and transcriptions within the app
• Enable integrations you explicitly connect (e.g. Google Calendar)
• Improve Screenpipe through optional pseudonymous analytics and aggregated reporting

Screenpipe does not sell your screen content or use consumer screen, audio, or transcript data for advertising. Optional website campaign measurement and referral attribution run only after consent. Screenpipe does not use personal data captured by the consumer app to train AI or machine learning models.

6. Data Sharing

Screenpipe does not sell, rent, or share your personal data with third parties, except in the following circumstances:

• At your direction: when you explicitly connect a third-party service (e.g. Deepgram for transcription, OpenAI for AI features, Google Calendar for scheduling), the data necessary for that integration is sent to that service.
• Optional analytics and attribution: after consent, pseudonymous website and product events may be sent to the providers listed in Section 4.
• Legal requirements: if required by law, regulation, or legal process.

7. Third-Party Services and Google User Data

Screenpipe integrates with third-party services. When you use these services, your data is subject to their respective privacy policies.

Google API Services

Screenpipe's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Data Accessed from Google

When you connect your Google account, Screenpipe requests access to:

• Google Calendar (read-only): Screenpipe accesses your calendar events (event titles, times, attendees, and descriptions) to provide context-aware features such as meeting detection and AI-powered meeting summaries.
• Email address: Screenpipe accesses your Google email address solely to identify your account and associate your calendar connection.

How Google Data is Used

Your Google Calendar data is used exclusively to:

• Display your upcoming and recent calendar events within the Screenpipe app
• Detect meetings and provide context for AI features (e.g. meeting summaries)
• Correlate screen and audio recordings with calendar events for better organization

Screenpipe does not use Google user data for advertising, does not share it with third parties (except as needed to provide the features you requested), and does not use it to train AI or machine learning models.

Google Data Storage and Protection

Google OAuth tokens (access and refresh tokens) are stored in our database, associated with your Screenpipe user account, and protected by server-level access controls and transport encryption (TLS). Calendar event data fetched from Google is cached temporarily in memory to serve your requests and is not persisted long-term on our servers. Your Google data is not accessible to other users.

Google Data Retention and Deletion

You can disconnect your Google account from Screenpipe at any time through the app settings. When you disconnect, your stored Google OAuth tokens are immediately deleted from our servers. Cached calendar data is purged and no longer fetched.

You may also revoke Screenpipe's access to your Google account at any time via your Google Account permissions page.

Cloud AI Processing

When you use Screenpipe's built-in AI features (chat, search, automations), your queries are processed through our AI gateway hosted on Cloudflare Workers. The gateway routes requests to the following providers, all on US/EU infrastructure:

• Google Cloud Vertex AI: processes requests for Claude (Anthropic), Gemini (Google), and open-source models (Llama, Qwen, GLM, Kimi). All traffic routes through Google Cloud infrastructure — no data is sent to China or other jurisdictions, even for models developed by Chinese companies. See Vertex AI data governance.
• Anthropic: Claude models may also be accessed directly via the Anthropic API. Anthropic does not use API data for training and retains data for 7 days for abuse monitoring. See Anthropic's privacy policy.
• OpenAI: GPT and o-series models are accessed via the OpenAI API. OpenAI does not use API data for training. See OpenAI's privacy policy.
• OpenRouter: a small number of models are accessed via OpenRouter with data collection explicitly denied. OpenRouter does not store prompt or completion content by default. See OpenRouter's privacy policy.

No provider uses your data for AI training. Screenpipe does not store any prompt or completion content — only anonymized usage metadata (token counts, model used, timestamps) for rate limiting and cost tracking.

Confidential-inference PII removal: if you enable this Screenpipe Cloud feature, screen content is processed by our proprietary PII-detection model running inside a hardware-isolated trusted execution environment (TEE). The content cannot be read by us or by the infrastructure operator, is used only to detect and redact sensitive information, and is not retained after processing. See our security page for details.

Audio Transcription

• Deepgram: audio data is sent to Deepgram for cloud transcription. Deepgram does not retain transcripts after processing (zero data retention by default). See Deepgram's privacy policy.

Account, Billing, and Communications

If you create an account or buy a paid plan, the following providers process the limited personal data needed to run your account, take payment, and communicate with you. They do not receive your screen recordings, audio, or transcriptions.

• Clerk: manages account sign-in and identity (your email and authentication data). See Clerk's privacy policy.
• Stripe: processes payments and subscription billing. Screenpipe does not store your full card number; Stripe handles payment data as a PCI-compliant processor. See Stripe's privacy policy.
• Loops: sends transactional and product emails (and, if you opt in, marketing email). Receives your email address and basic contact details. See Loops' privacy policy.
• Intercom: powers in-app support messaging when you contact us. See Intercom's privacy policy.

Analytics and Error Tracking

• PostHog: after optional tracking consent, pseudonymous product and website analytics data is sent to PostHog. See PostHog's privacy policy.
• Sentry: crash reports and application errors are sent to Sentry to help us diagnose and fix bugs. Sentry receives stack traces, app version, OS version, and anonymized event metadata — not your screen recordings, audio, or transcriptions. You can disable this in Settings → Privacy. See Sentry's privacy policy.

Complete List of Sub-Processors

The vendors above are the third parties most likely to process your personal data. For the complete, always-current list of Screenpipe's sub-processors (including infrastructure, object storage, payments, support, and analytics providers), see our Trust Center, which also hosts our SOC 2 Type II, ISO 27001, GDPR, and HIPAA compliance documentation.

8. Data Security

We are committed to ensuring the security of your data. Screenpipe employs the following security measures:

Local Data

• Local-first architecture: your screen and audio data stays on your device by default, stored in a SQLite database and local files
• Local database: the SQLite database is protected by your operating system's file permissions. An optional vault feature provides additional encryption at rest using ChaCha20-Poly1305 with Argon2id key derivation
• Local credentials: OAuth tokens and integration credentials for locally connected services are stored on your device in your user-protected home directory. Access is restricted by OS-level file permissions

Cloud Data

• Cloud sync encryption: if you enable cloud sync, all data is encrypted on your device before upload using zero-knowledge encryption (ChaCha20-Poly1305 with Argon2id key derivation). Our servers cannot decrypt your data
• Google OAuth tokens: when you connect Google Calendar, OAuth tokens (access and refresh tokens) are stored on our servers in our database, associated with your Screenpipe account. These tokens are used solely to fetch your calendar data on your behalf
• Transport security: all communications between the app and our servers use TLS/HTTPS encryption in transit
• Server access: access to user data on our servers is restricted to authorized personnel only

Transparency

• Our codebase is open source, enabling public security audits of all data handling code

9. Data Retention and Deletion

Local data: screen recordings, audio transcriptions, and other locally stored data remain on your device until you delete them. You have full control over retention and can delete data at any time through the app or by removing the local database files.

Server-side data: if you use cloud features (e.g. Google Calendar integration), we retain your account information and OAuth tokens only as long as your account is active and the integration is connected. When you disconnect an integration or delete your account, associated data is deleted within 30 days.

Analytics data: consented pseudonymous analytics data is retained for up to 24 months for product improvement. It may be associated with a browser or Screenpipe account identifier and is therefore treated as personal data where applicable.

To request deletion of any data associated with your account, contact us at louis@screenpi.pe. We will process deletion requests within 30 days.

10. GDPR Compliance

If you are located in the European Economic Area (EEA), this section applies to you. Screenpipe's local-first architecture and operational controls are designed to support GDPR obligations, but the final compliance posture for an organization deployment also depends on its configuration, notices, lawful basis, retention, access rules, and agreements.

• Data controller and processor: when you use Screenpipe directly, Screenpipe is the data controller for your account data. When Screenpipe is provided to you through an organization (Team or Enterprise plan), that organization is the data controller and Screenpipe acts as a data processor on its behalf under a Data Processing Agreement (DPA). Enterprise customers can request our DPA at louis@screenpi.pe.
• Lawful basis: depending on the processing, we rely on performance of a contract, consent, legitimate interests in security and service reliability, or legal obligations. Optional browser analytics and marketing tracking rely on consent.
• Your rights: you have the right to access, rectify, erase, restrict processing, and object to the processing of your personal data. You can also request data portability.
• Data transfers: where personal data is transferred outside the EEA, we evaluate and use an appropriate transfer mechanism where required, which may include adequacy decisions or Standard Contractual Clauses.

11. Your Rights

You have the following rights regarding your data:

• Access: request a copy of the data we hold about you
• Rectification: request correction of inaccurate data
• Deletion: request deletion of your data (see Section 9)
• Portability: request your data in a machine-readable format
• Revoke consent: disconnect integrations, use the site footer's Privacy choices, or delete your account

For locally stored data, you have full and direct control — you can access, modify, or delete your data at any time through the app or filesystem.

12. Changes to This Policy

We may update this privacy policy from time to time. We will notify you of any changes by posting the new privacy policy on this page with an updated "last updated" date. Your continued use of Screenpipe constitutes acceptance of the revised policy.