This site measures usage and transmits data in doing so. More in the privacy policy.

Skip to content
Mailcockpit
  • Features
  • Who it’s for
  • Teams
  • Security
  • Pricing
  • FAQ
Get early access
Sign in Deutsch
Language: DeutschDE Sign in Get early access

Legal

Privacy policy

Version 1.4 · Last updated 14 November 2026

This English version is a translation for your convenience. In case of doubt, the German version applies.

Contents

  • The essentials
  • 1. Controller and contact
  • 2. Scope
  • 3. Two roles: controller and processor
  • 4. Which data we process and why
  • 5. What we don’t do
  • 6. Legal bases
  • 7. Recipients and processors
  • 8. Transfers abroad
  • 9. Retention and deletion
  • 10. Data security
  • 11. Cookies and browser storage
  • 12. No automated individual decisions
  • 13. Your rights
  • 14. Complaints to a supervisory authority
  • 15. Minors
  • 16. Changes to this privacy policy
  • 17. Contact

This privacy policy describes which personal data Safkom GmbH processes when operating the Mailcockpit website and app, for what purposes, how long the data is kept and what rights you have.

It is based on the Swiss Federal Act on Data Protection (FADP, SR 235.1) as in force since 1 September 2023 and the Data Protection Ordinance (DPO, SR 235.11). For people in the European Union (EU) and the European Economic Area (EEA, including Liechtenstein) it also contains the information required by the EU General Data Protection Regulation (GDPR); these passages are marked “GDPR”.

The essentials

  • The website and the app run on our own server in Switzerland (Infomaniak, data centre in the Canton of Geneva).
  • The website loads no content from third-party servers; the only exception is the Meta Pixel, which we use to measure how well our ads on Facebook and Instagram work (section 4.18). In Switzerland it runs unless you object; a notice at the top of the page points this out. Outside Switzerland it runs only if you consent. The app uses no tracking.
  • We read the emails of connected mailboxes only to make the dashboard work – on behalf of the customer who connects the mailboxes.
  • No advertising in the app, no selling of data, no profiling, no training of AI models with your data.
  • The AI features are optional and switched off by default. Only if AI is switched on for a mailbox may the emails of that mailbox be sent to an AI service in the USA (section 4.17). The AI never sends anything itself.
  • Emails are only sent on instruction: manually or – if admins expressly switch it on for a template – via a sending interface (section 4.19).
  • The app sets only one strictly necessary cookie for signing in.
  • We store mailbox passwords, email content and attachments encrypted; you can set up a second factor for your account.
  • You can delete your account yourself and export your team’s data. Backup copies expire after 14 days at most.

1. Controller and contact

The controller for the processing described in this policy as Safkom’s own processing (see section 3) is:

Safkom GmbH
Oberdorfstrasse 11
5722 Gränichen
Switzerland
UID: CHE-283.267.062

Email, including for data protection matters: contact@mailcockpit.app

Hereinafter “Safkom”, “we” or “us”.

We have not appointed a data protection advisor under Art. 10 FADP or a data protection officer under Art. 37 GDPR. Please send all requests to the address above.

Our offer is aimed at customers in Switzerland. We have therefore not appointed a representative in the EU under Art. 27 GDPR.

2. Scope

This privacy policy applies to:

  • our website mailcockpit.app (the address mailcockpit.ch redirects there), including the waitlist;
  • the “Mailcockpit” web application at my.mailcockpit.app, also when you install it as an app on your computer or phone (a so-called progressive web app, PWA);
  • the “Mailcockpit” apps for iPhone and Android, once available;
  • the emails that Mailcockpit itself sends (system emails);
  • your contact with us, for example by email.

It does not apply to other providers’ websites we link to, nor to your email provider (for example Hostpoint, GMX, Microsoft), which processes your emails under its own rules.

3. Two roles: controller and processor

With Mailcockpit we have two different roles:

3.1 Safkom as controller. For the data we need to operate the website and the service itself, we decide how and why it is processed. This mainly covers website, consent banner and waitlist data, account and sign-in data, team and role management, security logs, system emails, device notifications, support and (later) billing.

3.2 Safkom as processor. For the content of connected mailboxes and everything a team creates from it (projects, tasks, notes, drafts, templates and their sending log, results of the AI features, daily overviews, the who-did-what log), we process the data on behalf of our customer (Art. 9 FADP; processor under Art. 28 GDPR). The customer is the person or company that opens a team and connects mailboxes. The customer is the controller of this data and decides which mailboxes are connected, who in the team has access and whether AI features or the sending interface are switched on. The details are set out in our data processing agreement. We still describe this processing here so that it is transparent what happens with the data.

3.3 Do you correspond with one of our customers? Then your data (for example your name, email address and the content of your emails) may be contained in a mailbox connected to Mailcockpit. For questions and requests (for example access or erasure), please contact that customer. If we receive such a request, we forward it as far as we can identify the customer responsible.

3.4 Private use. If you use Mailcockpit as an individual exclusively for personal purposes, the FADP does not apply to your own processing (Art. 2 para. 2 let. a FADP; similarly Art. 2 para. 2 let. c GDPR). We still treat the content of your mailboxes in exactly the same way: only to provide the service and only on your instructions.

4. Which data we process and why

4.1 Account

  • Data: name, email address, password (only as a non-reversible hash using scrypt, never in plain text), time the email address was confirmed, settings, time of last sign-in, failed-attempt counter and any lockout, version and time of your acceptance of the terms. Optionally a second factor (TOTP secret, stored encrypted) and recovery codes (stored only as hashes). While you change your email address, also the new, not yet confirmed address.
  • Purpose: setting up and managing the account, signing in, protecting the account, communicating with you about the service.
  • Retention: until you delete the account (see section 9).

4.2 Teams, roles and invitations

  • Data: team name, type (personal space or team), plan and, where applicable, end of a trial, memberships with role (owner, admin, member), permissions per mailbox, settings per membership (for example daily overview by email, device notifications), invitations (email address of the invited person, intended role, who invited them, times).
  • Visibility: team members see the names, email addresses and roles of the other members. Which team mailboxes and which data derived from them a member can see is decided by the owner and the admins (permissions per mailbox); the owner always sees all team mailboxes. Mailboxes in a person’s personal space are visible only to that person.
  • Purpose: collaboration in the team, managing permissions, enforcing plan limits.
  • Retention: until the team is deleted or you leave the team. Invitations expire after 7 days; we delete the invitation details 90 days after acceptance, revocation or expiry.

4.3 Sign-in, sessions and security log

  • Sessions: when you sign in, we store a session: a hash of the random sign-in token (the token itself exists only in your browser’s cookie), times, the active team, the IP address and your browser identifier (user agent). A session ends when you sign out, at the latest after 30 days, and is then deleted.
  • Security log: we log security-relevant events with time, account or team concerned and IP address: registration, sign-in, failed sign-in, lockout after failed attempts, sign-out, enabling and disabling the second factor, use of a recovery code, changing and resetting the password, changing the email address and profile, creating, renaming, exporting and deleting teams, plan changes, invitations, changes to memberships and permissions, switching AI and the sending interface on and off, creating and revoking access keys for the AI agent and the sending interface, signing out all sessions and deleting the account. Passwords, codes, tokens and email content are never logged.
  • Purpose: protecting accounts and the service, detecting and preventing abuse (for example limiting sign-in attempts), investigating security incidents, evidence.
  • Retention: security log 12 months from the event – for security and evidence reasons also if the account has since been deleted.

4.4 Mailbox credentials (on behalf of the customer)

  • Data: name and address of the mail servers (IMAP and SMTP), ports, connection type, user name, password or – when signing in with Microsoft – access tokens, your own sender addresses and your signature.
  • Protection: we store passwords and tokens encrypted (AES-256-GCM) with a separate key per team. The master key from which these keys are derived exists only on the server and is not part of the backups.
  • Purpose: connecting to your mailboxes to fetch, send and move emails.
  • Retention: until the mailbox is removed from the team or the team is deleted.

4.5 Mailbox content and team work data (on behalf of the customer)

  • Data: we fetch the emails from connected mailboxes and store a copy on our server, separated per team in its own database: headers (sender, recipients, subject, date, technical identifiers), content (text and HTML), attachments, folders and status (for example read). In addition, the data you create in the dashboard: areas, projects, tasks, deadlines, reminders, notes, assignments, drafts, templates, your own uploads, daily overviews and notifications.
  • Sensitive data: emails may contain data about third parties and also sensitive personal data (for example health, proceedings, religion, social assistance measures). The customer decides which emails end up in the dashboard by choosing the mailboxes.
  • Actions in the mailbox: on your instruction we send emails via your mailbox’s SMTP server (and store a copy in the “Sent” folder if your email provider does not do so itself), set the “read” flag, move emails to your mailbox’s trash folder or from the trash or spam folder back to the inbox, and permanently delete emails in the trash. When tidying up, at your express request we replace an email with a copy without a duplicate attachment; the original goes to the trash. A sending order via the sending interface that admins have switched on for a template also counts as an instruction (section 4.19). We make no other changes to your mailbox. If a mailbox is removed from the dashboard, the emails in the mailbox itself remain unchanged.
  • Purpose: solely providing the dashboard’s features for the team concerned (displaying, searching, organising, reminding, replying, sending). Automatic sorting (for example assigning an email to a project based on sender or subject) only serves to organise your emails and is not profiling.
  • No use for other purposes: we do not pass data from our customers’ teams on to other systems or business areas of Safkom.
  • Retention: as long as the mailbox is connected and the team exists. If you remove a mailbox, we immediately delete the copies stored for it. If you delete a team, we immediately delete all its data. After a subscription ends, the period set out in the terms and conditions applies. Backup copies expire after 14 days at most.

4.6 Who-did-what log (on behalf of the customer)

  • Data: for changes in the team we record who (identifier and name of the member) did what and when (for example “replied”, “assigned to a project”, “completed a task”), with a reference to the conversation, task or project concerned – without email content. We also record for each draft who created, edited, took over, discarded or sent it and when, and whether the AI prepared it. In addition, the dashboard briefly shows who currently has an email open or is writing a reply; this indicator is not stored and expires after about one minute.
  • Visibility: team members, each for the mailboxes they are allowed to see.
  • Purpose: collaboration in the team (“last edited by”), avoiding duplicate replies.
  • Retention: as long as the team exists. If a member leaves the team, their previous entries remain in the team’s log with their name.

4.7 System emails

  • Data: your email address, your name and the content of the system email.
  • What for: confirming your email address (link valid for 48 hours), resetting your password (link valid for 60 minutes), confirming a new email address, invitations to a team (link valid for 7 days), notices about your plan, your seats in a team and storage used, announcement of a deletion after the trial has expired and – only if you switch it on – the daily overview by email. The daily overview contains titles of tasks, projects and deadlines and thus information originating from your emails.
  • Sending: via the mail server of our email provider Hostpoint AG, Switzerland, from a sender address at mailcockpit.app.
  • Invitations to third parties: if a team invites someone, that person receives an email from us with the name of the team and of the person who invited them.

4.8 Device notifications (push, optional)

  • Optional and per device: you only receive notifications on your phone or computer if you switch them on for that device. You can switch them off again at any time.
  • Content: a notification reports, for example, a new email, a due reminder, a draft that is ready or the daily briefing, never the text of an email. What else it contains depends on the route.
  • In the browser (web push): the notification may contain the sender and subject (shortened), the project or figures of the daily briefing. We store the delivery address (endpoint) your browser receives from its vendor’s push service, your device’s public keys, the browser identifier, times and an error counter. The content is end-to-end encrypted (standard RFC 8291): only your device can read it. It is delivered via the push service of your browser’s vendor – depending on the browser Google (Firebase Cloud Messaging), Apple, Mozilla or Microsoft (Windows Push Notification Service). These services cannot read the content but see metadata such as delivery address, time and size. Your browser determines which service is used.
  • In the apps for iPhone and Android: we store the device’s push token, the platform and times. We send the notification via the push service of Expo (650 Industries, Inc., USA), which passes it on to Apple (Apple Push Notification Service) or Google (Firebase Cloud Messaging). For the mail agent’s “call” on the iPhone (section 4.17) we send the notification directly to Apple. These services can read what the notification says. On this route it therefore contains neither the sender nor the subject nor any other text from your emails, only the type of notification and, where applicable, a number (the texts are in German, for example “Neue Mail” [new email], “3 neue Mails” [3 new emails], “Neue Mitteilung” [new notification], “Wichtige Mail” [important email]; for a “call”, “Eine wichtige Mail” [one important email]). You only see the details in the app. Also sent are the push token, the number on the app icon and random technical identifiers (team, mailbox, thread, call) so that the app opens the right place; they do not reveal names, addresses or subject lines.
  • Exception – Safkom’s own areas: in the areas Safkom runs for its own mailboxes, the notification in the app also contains the sender and subject (shortened); there this information is readable for Expo, Apple and Google. This concerns emails addressed to Safkom itself, not our customers’ mailboxes.
  • Abroad: these services may use servers outside Switzerland, in particular in the USA (see section 8).
  • Retention: until you switch notifications off on the device, delete your account or the push service reports the delivery address or token as invalid.

4.9 Setup assistant when connecting a mailbox

When you enter an email address while adding a mailbox, the dashboard suggests the matching server settings. For this, our server uses:

  1. a built-in list of known providers;
  2. a DNS lookup of the mail servers (MX record) for the domain part of the address (for example “mycompany.ch”);
  3. a query to the public Mozilla/Thunderbird directory (autoconfig.thunderbird.net) – likewise only with the domain part, never with the full email address.

The queries are made from our server, so Mozilla sees our server’s address, not yours. We store nothing except the settings you then adopt. If the domain belongs to an individual (for example “firstname-lastname.ch”), even the domain part can be personal data.

4.10 Signing in with Microsoft (optional, once available)

For mailboxes at Microsoft (Outlook, Hotmail, Microsoft 365) you can sign in directly with Microsoft and allow Mailcockpit to access your mailbox. Signing in takes place on Microsoft’s pages; Microsoft processes data under its own privacy policy. We receive access tokens for IMAP and SMTP and the email address and store the tokens encrypted like a password (section 4.4). You can revoke the permission at any time in your Microsoft account or remove the mailbox in the dashboard.

4.11 Remote images in emails

Images that an email would load from the internet are blocked by default. If you explicitly load them for an email or a sender, your browser fetches the images directly from the sender’s server. That server can then see, for example, your IP address, the time and the fact that the email was opened. If you add a signature logo via a web address, our server fetches the image once from that address.

4.12 Contact and support

  • Data: your contact details and the content of your message; for support cases, any further information you give us.
  • Email to us: we receive and store emails to contact@mailcockpit.app in our mailbox at our email provider, Hostpoint AG, Switzerland.
  • Access to team data: we look at your team’s content (for example a specific email) only if you ask us to and only as far as necessary to solve the problem (see section 5).
  • Retention: 2 years after the request has been closed; longer if the correspondence forms part of our business records (up to 10 years).
  • Setup by video call (for plans with setup): the appointment takes place via Zoom (USA) or Microsoft Teams (Microsoft, USA); we agree on the tool with you when scheduling. Video, audio and – if you share your screen – its content are transmitted; emails may become visible. We do not record and do not store any content; you enter passwords yourself. The video call provider’s privacy terms apply; for transfers abroad see section 8.

4.13 Payment and billing data

Applies only once payment is introduced. Until then we process no payment data. We will name the payment provider in this policy before we introduce payment.

  • Data: name or company, billing address, VAT number where applicable, chosen plan, invoices, payment status and the identifier at the payment provider.
  • Payment provider: payments are handled by a specialised payment provider. We do not see or store full card or account details.
  • Purpose: billing, accounting, dunning, compliance with legal obligations.
  • Retention: invoices and accounting records 10 years (Art. 958f of the Swiss Code of Obligations); other data until the end of the contractual relationship.

4.14 Website, hosting and server logs

  • Hosting: the website and the app run on our own virtual server at Infomaniak Network SA, Geneva, in a data centre in Switzerland (Plan-les-Ouates, Geneva).
  • Cookies and tracking: the website uses no analytics or social media services. Its only advertising service is the Meta Pixel (section 4.18): in Switzerland unless you object, outside Switzerland only with your consent. Otherwise we keep at most your choice in the cookie settings in your browser’s storage (section 11).
  • No third-party content: the website and the app load no fonts, scripts, images or other content from third-party servers; everything comes from our server. Exceptions: on the website the Meta Pixel (section 4.18); in the app images in emails that you explicitly load (section 4.11).
  • Access log: for every request to the website or the app, the web server stores the IP address, time, requested address, status code, amount of data transferred and browser identifier (user agent) – no content. Purpose: operation, security and troubleshooting. Retention: 30 days at most, after which it is deleted automatically.
  • Domains and DNS: the domain mailcockpit.app is registered with Cloudflare, Inc. (USA), which also hosts its DNS records. We use Cloudflare for DNS only, without proxy: Cloudflare merely answers the question at which IP address our server can be reached. This query is usually made by your internet provider’s DNS resolver. The pages themselves and everything you enter do not pass through Cloudflare but travel directly between your device and our server in Switzerland. The domain mailcockpit.ch is registered with Hostpoint AG (Switzerland), which also hosts its DNS records; our server redirects requests to mailcockpit.ch to mailcockpit.app.
  • Encryption: all connections are encrypted with HTTPS. The certificates are issued by Let’s Encrypt (Internet Security Research Group, USA); Let’s Encrypt only receives our domain names, no visitor data.

4.15 Waitlist and early access

  • How it works: the waitlist form sends nothing to our server. It opens a prepared message to contact@mailcockpit.app in your email app. We only receive your details once you send that message.
  • Data: name, email address and – optionally – company, number of mailboxes, number of people and plan of interest, as well as your consent; plus the usual information contained in an email (for example the time).
  • Purpose: we use the details only to inform you about early access and the launch of Mailcockpit and to take your wishes into account in development. We do not sell them or pass them on to third parties. If the Meta Pixel is running, Meta only learns that the form was submitted, not your details (section 4.18).
  • Where: the message arrives in our mailbox at Hostpoint AG, Switzerland (section 4.12).
  • Retention: we delete your details when you ask us to – a short email to contact@mailcockpit.app is enough – or as soon as we no longer need them for this purpose.
  • Consent: you can withdraw your consent at any time with effect for the future.

4.16 Only one free trial per person

  • Purpose: where we offer a free trial, each person should use it only once. This protects the offer against abuse.
  • Data: when an account is deleted or its sign-in address is changed, we store a check value of the previous email address; when a mailbox is connected, a check value of that mailbox (mail server and user name as well as the mailbox’s own address). We also store the reason or a random identifier of the account, whether a trial was running, and the date. A check value is a hash (HMAC-SHA256) of the normalised address, calculated with a secret key of our server. We do not store the address itself; without the secret key it cannot be recovered from the check value, not even by trial and error.
  • Retention: 24 months from the last use, after which the check values are deleted automatically.
  • Your rights: if you are wrongly refused a trial, contact us and we will reset the block.

4.17 AI email agent (optional, off by default; on behalf of the customer)

  • Switching on and off: AI is off by default for every mailbox. Only the owner and the admins of a team can switch it on, per mailbox. Switching it off takes effect immediately; after that no more emails of that mailbox are sent to the AI service.
  • What the AI does: it sorts incoming emails (for example “important”) with a short reason, summarises longer threads in a few lines, detects deadlines and appointments in emails and suggests creating a task from them, prepares drafts of replies and follow-up emails as well as short reply suggestions, and compiles a daily briefing (only figures in the notification). Everything is a suggestion: a task is only created once a person confirms it; a draft is placed in the thread as a marked draft (“prepared by AI”). The AI never sends anything itself; you review and send every email.
  • Data sent to the AI service: the thread of the mailbox concerned (text, sender, recipients, subject, date, names of attachments; not the content of attachments). Where possible we shorten quotes and signatures beforehand.
  • AI service: Our contractual partner is Anthropic Ireland, Limited, Dublin (Ireland); processing is carried out by Anthropic, PBC, San Francisco, as a further sub-processor in the USA (section 8). Under its terms for business customers the provider may not use the data for its own purposes or to train its models, and as a rule deletes inputs and outputs after 30 days at the latest; where it detects violations of its usage policy, it may keep them longer. As long as no AI service is connected for a team yet, the features work with simple rules on our server, without any transfer abroad.
  • Talking to the mail agent (optional, per person, off by default): if you switch it on, you can be notified of important emails by a notification or – in the app – by an internet “call” (no telephone network). The agent reads the summary aloud; you answer by voice (for example “draft: …”, “pending until Monday”). Sending, forwarding and deleting are not possible by voice. Speech recognition and speech output are handled by your device or browser: depending on the device and browser this happens on the device itself or at the vendor (for example Google for Chrome, Apple for Safari and on the iPhone), which then receives your voice recording; the vendor decides this, not we. We only receive the recognised text. In the thread we record which command was carried out, without email content and without dictated text. In the app you expressly confirm the transfer to the AI service before the first “call”; you can withdraw this consent at any time.
  • No automated individual decision: the AI makes suggestions that a person reviews (section 12). AI results may be wrong or incomplete.
  • Responsibility: whether AI is permissible for a mailbox – for example in the case of professional secrecy or sensitive personal data – is decided by the customer (section 3.2).

4.18 Meta Pixel on the website (Switzerland: with a right to object; elsewhere only with consent)

  • Purpose: we advertise Mailcockpit on Facebook and Instagram, among others. The Meta Pixel lets us measure whether visitors reach our website through our ads and show interest in the waiting list, and lets us show ads to people who have visited our website.
  • In Switzerland (objection): if your browser is set to the Swiss time zone, the Meta Pixel runs from the first visit; a notice at the top of the page points this out. You can object at any time via “Cookie settings” at the bottom of every page by choosing “Decline”; the website then deletes the _fbp and _fbc cookies and loads nothing more from Meta. Only your browser reads the time zone; we do not store it or send it anywhere.
  • Outside Switzerland (consent): with any other time zone, a banner asks for your consent on your first visit; “Decline” and “Accept” are equivalent. Until you choose “Accept”, the website loads nothing from Meta and sets no cookie.
  • The pixel runs only on the website mailcockpit.app, never in the app.
  • Data: your IP address, browser and device information, the page visited and the referring page, the time, a random identifier in the _fbp cookie and – if you arrive via a Meta ad – the click identifier in the _fbc cookie. The only events we report are “page viewed” and “waiting list submitted”. We do not pass the contents of the form (name, email address etc.) to Meta, not even in hashed form. We have switched off the pixel’s automatic collection of clicks and page content.
  • What Meta does with it: if you are or have been logged in to Facebook or Instagram on this device, Meta can link the visit to your account and may also use the data for its own purposes under its own privacy policy (for example advertising, improving its services). We only receive aggregated reports from Meta, no data on individuals.
  • Recipient: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland; the data may be transferred to Meta Platforms, Inc. (USA) (section 8). We are jointly responsible with Meta for collecting and transmitting the data via the pixel (Art. 26 GDPR); Meta alone is responsible for any further processing. The joint controller agreement is available at facebook.com/legal/controller_addendum, Meta’s privacy policy at facebook.com/privacy/policy. You may exercise your rights with us or with Meta; we forward requests about Meta’s further processing to Meta.
  • Legal basis: in Switzerland our overriding interest in measuring our ads, with your right to object (Art. 31 para. 1 FADP; information on cookies under Art. 45c TCA in section 11); outside Switzerland your consent (section 6).
  • Retention: _fbp and _fbc cookies 90 days; your choice in the cookie settings 12 months, after which we ask again. At Meta according to its privacy policy.
  • Objection and withdrawal: you can object or withdraw your consent at any time via “Cookie settings” at the bottom of every page. The website then deletes the _fbp and _fbc cookies and no longer loads the pixel. This takes effect for the future.

4.19 Templates and sending interface (on behalf of the customer)

  • What it is: teams can create text templates per mailbox (for example an appointment confirmation). For an individual template, admins can switch on a sending interface (off by default). A program of the customer (for example a CRM) can then, with its own access key that admins create and can revoke at any time, have the template sent to a specified person – via the team’s mailbox, like an email sent manually. Optionally a calendar file can be attached if this is switched on for the template.
  • Data: templates (name, subject, text); for each sending order the recipient details supplied by the program (for example email address, salutation, first name, last name, company, own fields such as an appointment, an identifier in the customer’s program); in the sending log time, template, mailbox, access key, recipient, subject, result and, where applicable, error and name of a calendar file – without the text of the email. The email sent is stored like any email in the mailbox and in Mailcockpit (section 4.5).
  • Protection: access keys only apply to expressly selected mailboxes, are stored only as hashes and are limited to 200 emails per hour. If a value for a placeholder is missing, nothing is sent; the same order is never sent twice.
  • Responsibility: the customer is responsible for whom they contact via the interface and whether consent is required for it (for example for advertising, Art. 3 para. 1 let. o of the Swiss Unfair Competition Act).
  • Retention: templates are archived, not deleted; templates and sending log remain as long as the team exists and are deleted with the team.

5. What we don’t do

  • We show no advertising in the app and sell no data.
  • In the app we use no tracking, no analytics tools (for example Google Analytics) and no social media plug-ins. On the website we only use the Meta Pixel – in Switzerland with a right to object, outside Switzerland only with your consent (section 4.18).
  • We create no profiles of you or your correspondents.
  • We do not use your data to train AI models and do not allow our AI service to do so either. Emails are processed by an AI service only if AI is switched on for a mailbox (section 4.17). AI is off by default.
  • We send no emails without instruction: the AI never sends; the sending interface only sends templates that admins have switched on for it (section 4.19).
  • Safkom staff do not look at the content of your mailboxes – unless (a) you explicitly ask us to in support, (b) it is unavoidable to fix a fault or a security incident, and then only as far as necessary, or (c) we are legally obliged to.

6. Legal bases

Switzerland (FADP): we process personal data according to the principles of Art. 6 FADP (lawfully, in good faith, proportionately, for specific purposes, transparently, accurately). Where a justification is required, we rely on the performance of the contract with you (Art. 31 para. 2 let. a FADP), on your consent (waitlist), on our overriding interest (in particular in the security of the service, in preventing abuse and in measuring our ads with the Meta Pixel, section 4.18) or on a legal obligation. For cookies on the website we inform you in section 11 in accordance with Art. 45c of the Telecommunications Act (TCA) and point out your right to object.

EU/EEA (GDPR):

ProcessingLegal basis
Account, teams, providing the service, system emails about your account, daily overview, device notifications, setup assistantcontract (Art. 6(1)(b) GDPR)
Sessions, security log, server logs of the website and the app, preventing abuselegitimate interest in the security of the service and the protection of accounts (Art. 6(1)(f) GDPR)
Check values against repeated use of the triallegitimate interest in protecting the offer against abuse (Art. 6(1)(f) GDPR)
Waitlist and information about early accessconsent (Art. 6(1)(a) GDPR)
Meta Pixel on the website (storing and reading cookies, transfer to Meta)consent (Art. 6(1)(a) GDPR; for cookies Art. 5(3) of Directive 2002/58/EC or the corresponding law of your country of residence)
Storing your choice in the consent bannerlegal obligation to be able to demonstrate consent, and legitimate interest (Art. 6(1)(c) and (f) GDPR)
Invitation email to an invited personlegitimate interest of the inviting team in collaboration (Art. 6(1)(f) GDPR)
Contact and supportcontract or legitimate interest in answering requests (Art. 6(1)(b) or (f) GDPR)
Invoices and accounting (once payment is introduced)contract and legal obligation (Art. 6(1)(b) and (c) GDPR)
Establishing or defending legal claimslegitimate interest (Art. 6(1)(f) GDPR)
Mailbox content, team work data, AI features, templates and sending interfaceprocessing on behalf of the customer (Art. 28 GDPR); the legal basis lies with the customer

Where we rely on a legitimate interest, you can object (section 13).

7. Recipients and processors

We only disclose personal data where this is necessary for the service, where you initiate it or where we are legally obliged to. Our processors may only process the data on our instructions and not for their own purposes.

RecipientPurposeDataLocation
Infomaniak Network SA, Genevaoperation of our own virtual server (hosting of the website and the app)all data of the service and the website, access logsSwitzerland (data centre in Plan-les-Ouates, Geneva)
Hostpoint AGour email provider: mailbox contact@mailcockpit.app (including waitlist and support), sending system emails; registration and DNS of the domain mailcockpit.chcontent and details of emails to and from us, email address, name, content of system emails (including the daily overview)Switzerland
Cloudflare, Inc.registration of the domain mailcockpit.app and DNS – DNS only, no proxyDNS queries (name queried, IP address of the querying DNS resolver); no content of the website or the appUSA and worldwide (section 8)
Browser vendors’ push services: Google, Apple, Mozilla, Microsoftdelivering notifications in the browser (only if you switch them on)end-to-end encrypted content, metadata (delivery address, time, size)USA and other countries (section 8)
650 Industries, Inc. (Expo), Apple, Googledelivering notifications in the apps for iPhone and Android (only if you switch them on)push token, type of notification and number, random technical identifiers, metadata; neither sender nor subject (exception: Safkom’s own areas, section 4.8)USA and other countries (section 8)
Mozilla Corporation (Thunderbird directory autoconfig.thunderbird.net)suggesting server settings (section 4.9)domain part of an email address onlyUSA and other countries (section 8)
Microsoft (only if you use signing in with Microsoft)signing in and access to your Microsoft mailboxMicrosoft sign-in data, tokensas stated by Microsoft
Zoom or Microsoft (only for setup by video call)setup video call (section 4.12)video, audio, shared screen, appointment detailsUSA and other countries (section 8)
Anthropic Ireland, Limited (contractual partner) and Anthropic, PBC (processing)processing of emails by AI, only if switched on for a mailbox (section 4.17)text, sender, recipients, subject, date, attachment names of the threadIreland, USA (section 8)
Vendor of your browser or device (for example Google, Apple)speech recognition when talking to the mail agent, if not on the device (section 4.17)voice recording; determined by the vendoras stated by the vendor
Meta Platforms Ireland Limited (Switzerland: unless you object; elsewhere only with your consent)measuring and delivering our ads on Facebook and Instagram (section 4.18); jointly responsible for collection and transmissionIP address, browser and device data, page visited, time, identifiers from the _fbp/_fbc cookies, event “page viewed”/“waiting list submitted”Ireland, USA (section 8)
Payment provider – only once payment is introduced; we will name it here beforehandpayment processingbilling and payment datawill be stated beforehand

In addition:

  • Members of your team see the team’s data within their permissions (section 4.2).
  • Recipients of your emails receive the emails you send via the dashboard or the sending interface – via your own mailbox’s SMTP server.
  • Your email provider receives the requests with which we access your mailbox.
  • Programs you connect (sending interface, section 4.19) receive the list of templates and the sending log of the mailboxes released to them.
  • Authorities and courts only receive data where we are legally obliged to provide it.
  • Advisors (for example fiduciaries, auditors, lawyers) only receive data as far as necessary; they are bound by confidentiality.
  • In the event of a transfer of the business (for example a sale), data may pass to the successor; we will inform you beforehand.

The list of sub-processors for mailbox content is set out in Annex 2 of the data processing agreement.

8. Transfers abroad

We store and process your data in Switzerland. Data may be transferred abroad in the following cases:

  • Notifications in the browser: the push services of Google, Apple, Mozilla and Microsoft may use servers in the USA and other countries. The content is end-to-end encrypted; the services only see metadata. Your browser determines which service is used, and the transfer only takes place if you switch notifications on.
  • Notifications in the apps: Expo (650 Industries, Inc.), Apple and Google, USA and other countries. These services receive the push token, the type of notification and technical identifiers, but neither the sender nor the subject (exception: Safkom’s own areas, section 4.8). This only happens if you switch notifications on in the app. According to its own information, Expo participates in the Swiss-U.S. Data Privacy Framework.
  • Setup assistant: query to the directory of Mozilla Corporation (USA) with the domain part of an email address; the servers may also be located in other countries.
  • Signing in with Microsoft (only if you use it): as stated by Microsoft.
  • Setup by video call (only if you book it): Zoom or Microsoft, USA and other countries.
  • DNS of the domain mailcockpit.app: Cloudflare, USA and worldwide – DNS queries only, no content.
  • AI processing (only if switched on): Our contractual partner is Anthropic Ireland, Limited (Ireland); Anthropic, PBC processes the data as a further sub-processor in the USA. We rely on the European Commission’s standard contractual clauses with the adaptations for Switzerland, which form part of the provider’s contractual terms through its Data Processing Addendum (Art. 16 para. 2 let. d FADP; Art. 46 GDPR). You can obtain a copy on request.
  • Speech recognition (only if you talk to the mail agent and your device does not recognise speech itself): at the vendor of your browser or device, as stated by the vendor.
  • Meta Pixel (section 4.18): Meta Platforms Ireland Limited may transfer the data to Meta Platforms, Inc. in the USA. According to its own information, Meta Platforms, Inc. is certified under the Swiss-U.S. and the EU-U.S. Data Privacy Framework; in addition Meta uses the European Commission’s standard contractual clauses.
  • Payment provider (only once payment is introduced): we will name the provider and its location here before we introduce payment.

Safeguards: the EU and EEA states ensure adequate data protection under Annex 1 DPO. For the USA, this applies under Annex 1 DPO (since 15 September 2024) to companies certified under the Swiss-U.S. Data Privacy Framework; for people in the EU/EEA, the European Commission’s adequacy decision on the EU-U.S. Data Privacy Framework of 10 July 2023 applies. Where a provider is not certified or data is transferred to another state without adequate data protection, we rely on the European Commission’s standard contractual clauses recognised by the FDPIC (Art. 16 para. 2 let. d FADP; Art. 46 GDPR) or – for device notifications, speech recognition and video calls, which you choose yourself – on the exception for the performance of a contract with you (Art. 17 para. 1 let. b FADP; Art. 49(1)(b) GDPR). You can obtain a copy of the safeguards on request.

9. Retention and deletion

We keep personal data only as long as necessary for the purpose or as required by law. Overview:

DataRetention
Server access log (website and app)30 days at most
Your choice in the cookie settings (browser storage)12 months
_fbp and _fbc cookies of the Meta Pixel (section 4.18)90 days, deleted immediately on objection or withdrawal
Waitlist detailsuntil you ask for deletion or we no longer need them
Account (section 4.1)until the account is deleted
Sessions including IP address and browser identifieruntil sign-out, 30 days at most
Security log12 months from the event, also after the account has been deleted
Check values against repeated use of the trial24 months from the last use
One-time links (confirmation, password, invitation)until used or expired (48 hours, 60 minutes, 7 days)
Invitation details90 days after acceptance, revocation or expiry
Mailbox credentialsuntil the mailbox is removed or the team is deleted
Mailbox content and team work data (including AI results, templates, sending log)until the mailbox is removed or the team is deleted; after the end of the contract as set out in the terms and conditions
Data at the AI serviceas a rule 30 days at most (section 4.17)
Who-did-what logas long as the team exists
Device notifications (device registration)until switched off, the account is deleted or the push service reports it as invalid
Contact and support correspondence2 years after closure, up to 10 years as business records
Invoices and accounting records (once payment is introduced)10 years (Art. 958f Swiss Code of Obligations)
Backups14 days at most

Deleting your account: you can delete your account yourself under “Account & security”. We then immediately delete your account, your personal space and all teams in which you are the only member – with all their data. If you are the only owner of a team with other members, you first have to transfer ownership or delete the team. In teams with other members, the team’s data remains (it belongs to the team); your entries in the who-did-what log remain there with your name.

Backups: we back up all data every night on our server. Deleted data therefore disappears from the backups only after 14 days at most. If we restore a backup after an incident, we delete again any data whose deletion you requested in the meantime. An additional encrypted off-site copy is planned; it will be stored in Switzerland, and we will name the provider here before setting it up.

10. Data security

We protect your data with appropriate technical and organisational measures (Art. 8 FADP, Art. 1–6 DPO, Art. 32 GDPR), including:

  • encrypted transmission (HTTPS with certificates from Let’s Encrypt) between your device and our server; connections to mail servers encrypted only (TLS);
  • mailbox passwords and tokens encrypted (AES-256-GCM), a separate key per team, master key not in the backups;
  • email content (text and preview), drafts and attachments stored encrypted (AES-256-GCM), a separate key per team; subject, sender, recipients and date remain readable for overview, sorting and search;
  • a separate database per team;
  • passwords only as hashes (scrypt), optional second factor (TOTP), lockout after repeated failed attempts, limited sign-in attempts;
  • access keys for the AI agent and the sending interface stored only as hashes, restricted per mailbox and revocable at any time; the AI agent has no way to send;
  • protection against attacks via other websites, strict security rules for displaying emails, remote images blocked by default;
  • a hardened server (key-only access, firewall, automatic security updates), service running with restricted rights;
  • nightly backup, kept for 14 days at most.

To be frank: we store email content and attachments encrypted; subject, sender, recipients, date and attachment names remain readable so that overview and search work. Our server needs the key to fetch emails and show them to you – so this is not end-to-end encryption. If AI is switched on for a mailbox, the AI service also reads the emails of that mailbox. No system is completely secure. Please protect your account with a strong password and the second factor.

A detailed description of the measures is set out in Annex 1 of the data processing agreement.

11. Cookies and browser storage

Website: the website itself sets no cookies. In your browser’s storage it only keeps your choice in the cookie settings (mc-consent: “yes” or “no” and time, 12 months), so that the banner does not appear on every visit, and, for the duration of the visit, that you have seen the notice at the top of the page (mc-notice). The Meta Pixel sets these cookies – in Switzerland unless you object, outside Switzerland only if you consent (section 4.18):

NamePurposeDurationType
_fbprandom identifier with which Meta links visits to the same browser (ad measurement, section 4.18)90 daysadvertising, set by Meta on our domain
_fbcclick identifier if you arrive via a Meta ad90 daysadvertising, set by Meta on our domain

In addition, Meta may read its own cookies on facebook.com if you are logged in there. You can change your choice at any time via “Cookie settings” at the bottom of every page.

App: the app uses a single cookie:

NamePurposeDurationType
__Host-edsidkeeps you signed in (random session token)until sign-out, 30 days at moststrictly necessary, for our domain only, HttpOnly, Secure, SameSite=Lax

Signing in is not possible without this cookie. It is strictly necessary and therefore requires no consent. In the app we set no cookies for analytics, advertising or by third parties.

In addition, the app stores in your browser: the program files of the interface (so that it starts quickly and can be installed) and small interface settings (for example whether you have dismissed a notice). Email content is not cached there. You can delete this data at any time in your browser settings.

12. No automated individual decisions

We make no decisions based solely on automated processing that have legal effects for you or significantly affect you (Art. 21 FADP, Art. 22 GDPR). Automatic sorting of emails in the dashboard is not such a decision. The AI features do not make decisions either; they make suggestions (sorting, deadlines, drafts) that a person reviews. The sending interface only sends templates that a person has released, on the order of a program of the customer.

13. Your rights

Within the applicable law, you have in particular the following rights:

  • access to whether and which personal data we process about you (Art. 25 FADP; Art. 15 GDPR);
  • rectification of inaccurate data (Art. 32 para. 1 FADP; Art. 16 GDPR);
  • erasure (Art. 32 para. 2 let. c FADP; Art. 17 GDPR);
  • restriction or prohibition of processing or disclosure (Art. 32 para. 2 FADP; Art. 18 GDPR);
  • delivery or transfer of your data in a common electronic format (Art. 28 FADP; Art. 20 GDPR);
  • objection to processing based on a legitimate interest (Art. 30 para. 2 let. b FADP; Art. 21 GDPR);
  • withdrawal of consent with effect for the future (Art. 7(3) GDPR), for example for the waitlist or the Meta Pixel.

Much of this works directly in the app: change your name and email address and delete your account under “Account & security”; switch device notifications and talking to the mail agent on and off; owners and admins can switch AI off per mailbox, revoke access keys, export all of a team’s data as a file (.tar.gz) and delete teams.

How to reach us: by email to contact@mailcockpit.app or by post to the address in section 1. To prevent unauthorised persons from obtaining information, we may ask for proof of your identity (for example a request from your account or from the registered address). We usually reply within 30 days. Access is free of charge; if the effort is disproportionate, a contribution to costs of at most CHF 300 may be charged (Art. 19 DPO) – we will inform you beforehand. The law may restrict these rights in individual cases (for example Art. 26 FADP); we will then give reasons.

Mailbox content: if your request concerns emails in a mailbox of one of our customers, please contact that customer (section 3.3). We support them in responding.

14. Complaints to a supervisory authority

We would appreciate it if you contacted us first. However, you can contact the competent supervisory authority at any time:

  • Switzerland: Federal Data Protection and Information Commissioner (FDPIC), Feldeggweg 1, 3003 Bern, www.edoeb.admin.ch.
  • EU/EEA (GDPR): the data protection supervisory authority in the state where you live or work or where the alleged infringement took place (Art. 77 GDPR); the European Data Protection Board keeps a list at edpb.europa.eu. In Liechtenstein: Datenschutzstelle Liechtenstein, www.datenschutzstelle.li.

15. Minors

Mailcockpit is intended for companies, organisations and adult individuals. Minors may only use it with the consent of their legal representative.

16. Changes to this privacy policy

We update this privacy policy when the website, the service, our providers or the law change. The version published at https://mailcockpit.app/en/privacy/ applies. We inform registered users of material changes in advance by email or in the app.

17. Contact

Safkom GmbH, Oberdorfstrasse 11, 5722 Gränichen, Switzerland
Email: contact@mailcockpit.app

← Back to the home page

Mailcockpit

Turn email into finished work – in your existing mailbox, as a team.

A product of Safkom GmbH, Gränichen, Switzerland.

Product

  • Features
  • Who it’s for
  • Pricing
  • FAQ
  • For accountants and law firms
  • For personal use
  • Get early access
  • Sign in

Legal

  • Legal notice
  • Privacy
  • Terms
  • Data processing agreement

Contact

  • contact@mailcockpit.app
  • Safkom GmbH
  • Deutsch

© 2026 Safkom GmbH · Website with Meta Pixel (in Switzerland with a right to object, elsewhere only with consent); the app uses no trackers.

All trademarks belong to their respective owners.

May Meta measure your visit?

With your consent we load the Meta Pixel. It sets cookies and tells Meta (Facebook, Instagram) about your visit to this website, so we can see whether our ads work. Data may be transferred to the USA. Without your consent nothing is loaded from Meta. You can change your choice at any time under “Cookie settings” at the bottom of the page. More in the privacy policy

Measurement by Meta

We use the Meta Pixel to measure whether our ads on Facebook and Instagram work. It sets cookies and tells Meta about your visit to this website; data may be transferred to the USA. With “Decline” you object: the website deletes the Meta cookies and loads nothing more from Meta. You can change your choice at any time under “Cookie settings” at the bottom of the page. More in the privacy policy