Mailordo Privacy Policy

1. Introduction

Mailordo is an AI-powered email triage tool that runs in your web browser. We take the protection of your personal data seriously. This privacy policy describes how Mailordo handles your data.

Core principle: Mailordo does not store your emails. The content of your emails and billing data is fetched from Google directly in your browser. For AI analysis, relevant emails are sent to the AI provider (Anthropic, Google or OpenAI) using your own API key. That request passes through a Mailordo relay service: the content is processed there but not stored or logged. Tasks and settings are stored locally in your browser.

Exception — your Google connection: to keep your session active without asking you to sign in again each time, we store one encrypted Google refresh token on our servers (Supabase). That token is used only to request a new, short-lived access token; your email and calendar content itself does not pass through it. The token is deleted when you sign out.

2. What data is processed?

Mailordo processes the following data, exclusively in your browser:

• Gmail messages: subject, sender, date and body of recent emails (read-only access via Google OAuth)
• Google Calendar: we read calendar events for today and tomorrow from the calendar you choose, and can — at your request, via the AI assistant — create a calendar event for you. This requires write access to your calendars (Google OAuth scope calendar.events). Mailordo never creates events unprompted or automatically.
• API keys: your own Claude, Gemini or OpenAI API keys (stored locally in your browser, with additional browser-side encryption when Web Crypto is available; during an AI analysis the key is included in the request without us storing it)
• Settings: your preferences, client domains and spam filters (localStorage in your browser)
• Generated tasks: the task list the AI generates from your emails (localStorage)

3. Website analytics and cookies

On public website pages we use analytics such as Google Tag Manager, Vercel Analytics, Ahrefs Web Analytics and possibly Google Analytics. Ahrefs and Google Analytics are only loaded after you have given consent. These analytics help us understand which public pages are visited and where the website can be improved.

These analytics are not loaded in the signed-in triage app. We do not use analytics to track mailbox content, tasks, AI results, billing data or individual emails. We do not use a Facebook Pixel or advertising networks, and we do not sell data.

Functional cookies or similar storage may be needed for authentication, security, local settings and your analytics choice. You can change your analytics choice via the cookie settings on the public website.

4. How we protect sensitive data

We protect your emails, calendar data, Google tokens and API keys with the following measures:

• Encryption in transit: all traffic between your browser, our servers, Google and the AI providers uses HTTPS (TLS) exclusively. HTTP Strict Transport Security (HSTS) enforces this.
• Encryption at rest: the Google refresh token is encrypted with AES-256-GCM before storage, using a key that exists only on the server. Where possible, API keys in your browser get an additional encryption layer (AES-GCM via the Web Crypto API). This is a supplementary measure: the key is derived in your browser itself, so the main protection for local data remains the security of your browser and device.
• Access control: the table holding Google tokens is protected with Row Level Security and cannot be reached directly from the browser. Only our server can read the token: it first verifies your sign-in and then retrieves only the token belonging to your verified account. Access to Google uses short-lived access tokens and the minimum necessary OAuth scopes (Gmail read-only, calendar events).
• No storage or logging of content: email and calendar content is not stored on our servers. The relay service for AI analysis forwards requests directly and does not log email content or API keys; on errors we only record technical data such as status codes.
• Browser security: a strict Content Security Policy and other security headers limit which scripts and external resources the app may load. Analytics is not loaded in the signed-in app.
• Retention and deletion: when you sign out, your stored Google refresh token is deleted from our servers. Signing out does not delete all your data: tasks and settings remain in your browser until you clear them via your browser settings, and your Mailordo account and subscription data are kept for as long as your account exists. You can request deletion of your account via the contact page. You can also revoke Mailordo's access to Google at any time in your Google account settings.

5. Google API Services User Data Policy

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

Mailordo uses Google user data only to provide the functionality authorized by the user. Google user data is not sold or used for advertising purposes.