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
• Anonymous product analytics (see Section 4)

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

4. Analytics and Transparency

We collect anonymous analytics to improve the app experience. This includes actions like "clicked on search" but does not collect any sensitive information or user queries. Only aggregate numbers are recorded.

Transparency is one of our core values. You can view all our telemetry-related code on GitHub:

• PostHog analytics code
• Sentry error tracking code

5. Data Usage

The collected data is used solely for the purposes you specify within the Screenpipe application. We do not access, transfer, or process your data without your explicit consent.

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 anonymous, aggregated analytics

Screenpipe does not use your data for advertising, profiling, or any purpose unrelated to providing the Screenpipe service. Screenpipe does not use your data 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.
• Anonymous analytics: aggregated, non-identifiable usage data is sent to PostHog for product improvement.
• 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 (DeepSeek, 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.

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.

Analytics and Error Tracking

• PostHog: anonymous product 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.

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: anonymous analytics data is retained for up to 24 months for product improvement purposes. This data cannot be traced back to individual users.

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 complies with the GDPR regulations to ensure your personal data is handled responsibly.

• Data controller: Screenpipe is the data controller responsible for your personal data.
• Lawful basis: we process your data based on your consent and the necessity to provide our services.
• 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: if your data is transferred outside the EEA, we ensure it is protected by appropriate safeguards.

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 or delete your account at any time

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.