Pridestel Logo Pridestel Mail
Home Terms of Service Security ← Back to App
Privacy Policy & Data Protection

Pridestel Mail Privacy Policy

Effective Date: October 22, 2026 • Version: 1.1 • Publisher: Pridestel

Executive Summary: Pridestel Mail is built on a strict zero-telemetry, zero-cloud architecture. The software runs 100% locally on your desktop computer. We do not operate user accounts, we do not have an intermediary mail relay server, and we never collect, store, or sell your emails, credentials, or personal identity.

1. Zero-Collection Principle

Pridestel strictly enforces zero data collection across the entire application lifecycle:

🚫 No Snooping

We do not collect, read, inspect, transmit, or store your email messages, subject lines, attachments, or contact lists on any Pridestel server.

🔑 No Credential Harvesting

Your email passwords and OAuth access tokens are stored directly in your operating system's native hardware-backed credential vault (Windows Credential Manager / macOS Keychain).

📊 No Behavioral Tracking

We do not record what emails you open, how frequently you write, or who your correspondents are. There are zero usage analytics or telemetry events.

🛡️ No Third-Party Trackers

The application contains zero advertising SDKs, tracking pixels, behavioral cookies, or analytics services.

🔒 No Auto Error Transmission

To eliminate accidental data leakage, crash dumps or error logs are never sent automatically over the internet. Diagnostic logs stay on your local disk.

💻 100% Sovereign Local AI

Our optional AI assistant runs entirely on your local machine using embedded llama.cpp weights. No prompt or email is ever sent to an external AI cloud.

2. Google API Services & User Data Policy

Pridestel Mail allows users to connect their Google Gmail accounts via standard, secure Google OAuth 2.0 authentication. When you connect a Google account:

How We Access and Use Google User Data

  • Direct End-to-End Connection: Pridestel Mail communicates directly with official Google endpoints (oauth2.googleapis.com and imap.gmail.com / smtp.gmail.com) using encrypted TLS 1.3 connections. No Google user data is ever routed through or proxied by Pridestel servers.
  • Local Authentication: During OAuth authentication, the Google authorization page is opened in your default system web browser. Once authorized, the authorization code is received locally by Pridestel Mail's loopback listener.
  • Secure Token Storage: OAuth access tokens and refresh tokens are encrypted and saved exclusively in your operating system's secure credential store (Windows Credential Manager / macOS Keychain / Linux Secret Service). Pridestel has no access to these tokens outside your local machine.
  • Local Caching Only: Downloaded email messages, threads, and folder hierarchies are stored solely in a local SQLite database on your device to enable instant full-text search and offline reading.
  • No Data Transfer or Sharing: We do not sell, rent, disclose, or transfer your Google user data to any third party. Your data remains on your personal computer.
  • No AI Model Training: Google user data is NEVER used to train, retrain, or fine-tune any machine learning or generalized AI models.

Google API Limited Use Disclosure:
Pridestel Mail's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

3. Data Stored Locally on Your Computer

Because Pridestel Mail is an offline-capable sovereign desktop application, all essential data remains strictly on your local disk drive:

  • Local SQLite Database: Stores cached mail headers, message bodies, folder structures, and contact indices for instant indexing and local search.
  • OS Secure Credential Store: Passwords, OAuth tokens, and server secrets are managed by your operating system's native keychain.
  • Application Preferences: Local configuration files record your theme preferences, font sizes, signatures, and custom mail rules.
  • Local AI Model Weights: Optional GGUF model files (Qwen / Llama) are stored on your disk for on-device natural language summarization.

4. Direct Network Communications

Network activity initiated by Pridestel Mail is strictly limited to direct, necessary user operations:

  • Mail Provider Connections: Direct, encrypted TLS connections to IMAP, SMTP, POP3, and CalDAV endpoints specified by the user or discovered via standard DNS/MX lookups.
  • App Update Verification: The desktop client may periodically check Pridestel's public repository for new release versions (checking version strings only, with zero personal identifiers transmitted).
  • Model Weight Download: When you enable the local AI assistant for the first time, model weights are downloaded directly from verified HTTPS repositories and verified against cryptographic SHA-256 hashes.

5. Application Security Architecture

Pridestel Mail employs defense-in-depth protections to guard against hostile email payloads and internet threats:

  • DOMPurify HTML Sanitization: All incoming email bodies are aggressively sanitized via DOMPurify before rendering.
  • Sandboxed Iframe Execution: Email HTML renders inside an isolated, sandboxed iframe preventing script execution, cookie access, or host DOM manipulation.
  • Anti-Phishing Shield: Outbound link clicks are intercepted by a safety modal that flags punycode homograph attacks, naked IP addresses, insecure HTTP, and hidden redirection URLs.
  • Attachment Quarantine: Executable or potentially malicious attachment extensions (.exe, .bat, .vbs, .scr, .js) trigger an explicit warning and are quarantined with the OS Zone.Identifier marker.

6. User Sovereignty & Data Deletion

You have absolute ownership and control over your data at all times. Because there is no centralized Pridestel account or cloud server holding your data:

  • Account Removal: Removing an email account from Pridestel Mail immediately revokes and purges the OAuth tokens from the OS Credential Manager and deletes all local cached messages for that account.
  • Database Purge: You can purge the local SQLite database cache from within Settings at any time.
  • Uninstallation: Uninstalling Pridestel Mail removes the application binaries. Deleting the application data folder permanently destroys all local cache files.

7. Revisions to this Privacy Policy

We may update this Privacy Policy from time to time to reflect enhancements in the software or regulatory standards. When revisions occur, we will update the "Effective Date" at the top of this page. Because we do not store your contact info, we recommend reviewing this policy periodically or checking the version bundled with new releases.

8. Contact & Inquiries

If you have any questions, suggestions, or concerns regarding this Privacy Policy or Pridestel's security architecture, please contact us: