AllMailHub
FeaturesCalendarAI assistantAppsPricingHelp
Sign inSign up for free

Courtesy translation only. This English text is a non-binding translation of the German original. Only the German version is legally binding.

Read the German version
Legal

Privacy Policy

Last updated: 13 November 2026 · English translation (courtesy only)

PrivacyImprintTermsWithdrawalSubprocessors and recipients
On this page
  1. 1. Controller
  2. 2. Principles
  3. 3. Visiting the website and the application
  4. 4. Registration and account
  5. 5. Connecting your mailboxes – credentials
  6. 6. Processing of your emails, contacts and related data
  7. 6a. Calendar, sharing and invitations
  8. 6b. Optional AI features (processing in the EU)
  9. 6c. AI connector: access by AI applications you connect
  10. 7. Real-time notifications and push
  11. 8. Contact, cancellation and withdrawal
  12. 9. Payment processing
  13. 10. Transactional emails
  14. 10a. Referral programme
  15. 11. Recipients and third-country transfers
  16. 12. Retention periods
  17. 13. Your rights
  18. 14. Right to lodge a complaint with a supervisory authority
  19. 15. Data security
  20. 16. Changes to this policy
Questions? info@allmailhub.com

This policy informs you, in accordance with Art. 13 and 14 GDPR, about how personal data is processed when you visit the AllMailHub website, create an account and use the service. AllMailHub connects email mailboxes that you maintain with third parties. The policy also covers contacts, calendars, the optional AI features, the AI connector, notifications, the support form and the public contract forms.

1. Controller

Responsible person: Sebastian Siebert

AllMailHub
c/o MDC#2189
Welserstraße 3
87463 Dietmannsried
Germany
Email: info@allmailhub.com
Telefon: +49 15679 835576

2. Principles

  • Data transmission between your device and the service is encrypted (TLS).
  • Mailbox credentials are stored in encrypted form (AES-256-GCM); more on this in section 5.
  • Email content is processed for the features of the service. No analysis of content for advertising purposes takes place.
  • Operation and primary storage take place in the Netherlands; encrypted offsite backups are stored in Germany, as are cleaned operating logs for error monitoring (section 3). Other recipients are named in section 11.

3. Visiting the website and the application

Server log files

When you visit, the server automatically processes the information transmitted: IP address, date and time, resource requested, HTTP status code, amount of data transferred, referrer, and browser and operating system identifier. This is technically necessary to deliver the page, to ensure system security and to detect abuse (e.g. automated attacks). The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation). Server log entries are deleted on our servers after seven days at the latest. Security events stored separately are deleted after 90 days at most. For entries transmitted for error monitoring, the following paragraph applies.

Error and operations monitoring

To detect and fix faults, we transmit selected error and operations logs of the application, database, spam filter and web servers to Grafana Cloud. The provider is Raintank, Inc. dba Grafana Labs (USA), which acts for us as a processor; the data is stored in a data centre in Germany. Before transmission, the entries are cleaned on our server: passwords, credentials, tokens and session cookies are removed; full message texts, HTML sources and attachments are not transmitted. They may contain technical identifiers of account, mailbox, folder and message, IP addresses, email addresses, host names and error messages, and in individual diagnostic messages also subject lines and short preview excerpts. In addition, server metrics (load of processor, memory, disks and network) may be transmitted; they contain no user data. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation). The transmitted entries are deleted at Grafana Cloud after 14 days. Access by Grafana Labs from the USA, for example for operation and support, is possible (see section 11).

Necessary cookies and storage on your device

The web application uses the cookies “mailhub_access” (lifetime up to seven days) and “mailhub_refresh” (up to 30 days) for sign-in and session management. When the session is renewed, the lifetimes are set again; when you sign out, the cookies are removed. Session management serves to perform the contract of use (Art. 6(1)(b) GDPR). For the access to your device required for this, Section 25(2) No. 2 of the German Telecommunications Digital Services Data Protection Act (TDDDG) applies.

During registration we additionally set the cookie “amh_signup” (lifetime up to 60 minutes). It contains a random account identifier, the expiry time and the selected billing period and is signed. It proves that the confirmation takes place in the same browser in which the account was created; only then do we sign you in directly after you enter the correct code. The cookie is not a session and is removed after confirmation. It serves to carry out the registration (Art. 6(1)(b) GDPR); for access to your device, Section 25(2) No. 2 TDDDG applies.

Language, display options and drafts for restoring messages not yet sent are also stored in the local browser storage. Draft data may contain recipients, subject and message text. Locally stored data is not automatically removed from every device used by a server-side account deletion; you can delete it through your browser’s website data management. During email dictation, the browser backs up text already recognised but not yet inserted in the tab’s session storage (“sessionStorage”), tied to the signed-in account and the respective compose window. The backup is deleted after insertion or discarding; orphaned backups expire after 24 hours; it is not transmitted to any other service. An explicitly chosen language is stored per device. The public language versions are delivered based on the URL requested. These storage accesses serve the sign-in, display and draft restoration you requested (Section 25(2) No. 2 TDDDG; Art. 6(1)(b) GDPR).

Search engines and audience measurement

The public pages can be indexed by search engines. Google Search Console and Bing Webmaster Tools serve to evaluate search queries and indexing at the respective search engines. Verification by DNS does not transmit any additional visitor data to Google or Microsoft when a page is visited. The website embeds neither an analytics script nor analytics cookies for this. Sign-in, your mailboxes and calendars are not intended to be public for search engines and require a session.

Advertising

No advertising is currently displayed in AllMailHub. Advertising may appear in the free plan in future; paid plans remain ad-free. Email content is not analysed for advertising purposes. Before advertising is introduced, we will adapt this policy.

Hosting

The application and database are operated on a server of Scaleway S.A.S., 8 rue de la Ville l'Évêque, 75008 Paris, France, at the server location Netherlands. Encrypted offsite backups are stored on a Storage Box of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. Both companies are used as processors under Art. 28 GDPR. Full list at Subprocessors.

Data processing agreements under Art. 28 GDPR exist with both providers. The servers are located at the stated locations in the EU. For error and operations monitoring with Grafana Cloud, the paragraph of the same name above applies. For optional features with external services (AI, AI connector, push notifications, support form), sections 6b, 6c, 7, 8 and 11 apply.

4. Registration and account

To use the service you create an account. The following is processed: email address, a hashed password, name, time and IP address of the registration, account status and settings and – if activated – the details required for two-factor authentication (e.g. TOTP key). The purpose is the provision and securing of the account; the legal basis is Art. 6(1)(b) GDPR (contract) and, with regard to the security details, Art. 6(1)(f) GDPR. Time-limited tokens are stored for password reset and account reactivation.

Protection against automated registrations: If bot protection is active, we embed Cloudflare Turnstile (Cloudflare, Inc., USA) during registration and when you request the confirmation code again. Cloudflare processes your IP address and technical characteristics of your browser to detect automated requests; we only receive the result. The legal basis is Art. 6(1)(f) GDPR (protecting the service against abuse); access to your device is strictly necessary for this (Section 25(2) no. 2 TDDDG). A transfer to the USA is possible (section 11).

Confirmation of the email address: After registration we send you a six-digit code and a confirmation link to the address given. The code and link are valid for 60 minutes and are stored only as a check value (hash), together with the number of failed attempts; after five failed attempts a new code is required. As long as the account is not confirmed, you can correct the email address; the previous address is then replaced, and codes already sent become invalid. A paid plan can only be taken out after confirmation.

Unconfirmed accounts: If you do not confirm the address, we remind you one day, seven days and 13 days after registration with a new code. An account that is still unconfirmed 14 days after registration is deleted by us permanently, without a recovery period; the details stored at registration, including time, IP address and acceptance of the Terms, are deleted as well. If payment or subscription data already exist for the account, we do not delete it automatically but clarify the matter; statutory retention periods then apply to payment records. The legal basis for the reminder and deletion is Art. 6(1)(b) GDPR; the deletion period follows the principle of storage limitation (Art. 5(1)(e) GDPR).

The public offering is aimed at persons aged 18 or over for private use. We point this out before registration is completed. The acceptance of the Terms and the notices on eligibility and data protection displayed at that point are stored with version, time and IP address to document the conclusion of the contract (Art. 6(1)(b) and (f) GDPR; legitimate interest in being able to provide proof). No date of birth and no copy of an ID is requested for this. This is not a separate consent to advertising, mobile push content or AI processing.

Name, email address and password are required for registration. Without these details we cannot provide an account. To connect a mailbox we need its connection and sign-in details; without these details the respective mailbox cannot be used.

In the password check, the beginning of the SHA-1 hash of the password you enter (five hex characters) is transmitted by the server to the Pwned Passwords service of Have I Been Pwned; the comparison of matches takes place on our side. Neither the password nor the full hash nor your email address is transmitted to this service. The purpose is protection against passwords that have already become known (Art. 6(1)(f) GDPR).

5. Connecting your mailboxes – credentials

When you connect a mailbox, we process the connection data required for this: server addresses and ports for IMAP and SMTP, user name and the password or an app-specific password or – where supported – an OAuth token.

Why the credentials are stored in a decryptable form: So that AllMailHub can retrieve new messages even when you are not signed in (including for synchronisation and push), the service must continuously sign in to your mailbox on its own. Pure, irreversible hashing – as with your AllMailHub password – is technically not possible for this. The credentials are therefore stored in the database encrypted with AES-256-GCM and are decrypted server-side only for the respective connection process. This means: technical access to the plaintext credentials by the operator is in principle possible. The encryption is not end-to-end encryption of your messages.

The legal basis is Art. 6(1)(b) GDPR – the processing is necessary to perform the contract of use. Where your provider offers it, we recommend app passwords or OAuth. You can remove a connected mailbox at any time in the settings; the associated credentials are then deleted.

Microsoft sign-in for Outlook and Hotmail

When connecting a Microsoft mailbox through the supported OAuth procedure, you are redirected to Microsoft. Microsoft receives, among other things, the technical sign-in and, if used, the email address given as a sign-in hint. AllMailHub requests permissions to retrieve via IMAP, send via SMTP, identify the approved account and renew access. The server exchanges the authorisation code for access tokens and can continue access with the renewal token stored in encrypted form. You can remove the connection in AllMailHub and withdraw the approval in your Microsoft account. This is the sign-in for the connected mailbox, not a blanket sign-in of all users with Microsoft.

Protection against repeated sign-ins and connection overview

So that your mailbox provider is not burdened by repeated failed sign-ins and your account is not locked there, AllMailHub checks before every sign-in to your mailbox whether it is permissible and logs the attempt. For each attempt we store time and duration, the result (success, rejected, unclear, connection error), an error class and an error code (no server responses and no credentials), the protocol (IMAP or SMTP), the occasion (for example retrieval, sending or connection test), a rough provider group and the assignment to your account and mailbox. For existing connections we keep a session overview with times, status and provider group.

After repeatedly rejected sign-ins with unchanged credentials, we delay further attempts and stop them after the third failed attempt until you change the credentials. The settings show the status. In addition, we count sign-ins for stable operation and capacity planning as per-minute and per-hour values for each provider group, without reference to account, user or server. The legal basis is Art. 6(1)(b) GDPR (reliable provision of the mailbox connection) and (f) GDPR (protecting your mailbox from being locked and stability of the service). The periods are in section 12.

6. Processing of your emails, contacts and related data

To provide the service, we process the following data. The legal basis for your own data is Art. 6(1)(b) GDPR. We process data of other persons, such as senders, recipients, appointment participants or persons named in messages, because you and we have a legitimate interest in handling your communication with these persons through AllMailHub (Art. 6(1)(f) GDPR). We do not analyse this data for our own purposes.

  • Messages: Header data (sender, recipient, subject, date), message text and attachments are retrieved via IMAP and – for cross-account search and display – stored as a copy. Messages are kept in the database, attachments in object storage; a separate search index may contain message content. Deleting or moving in AllMailHub affects, depending on the action, the stored copy and the mailbox at the provider.
  • Folders: The folders present in your mailbox are detected and synchronised.
  • Contacts: From email traffic and your input, contact data (name, address, frequency of contact) is detected and stored centrally.
  • Spam filter: Blocked sender addresses are stored. When the spam filter is enabled, message content and header data are also automatically checked for spam. Markings as spam or as a wanted message can be used to adapt the account-specific filter.
  • Newsletter features: Recurring senders are detected as newsletters; at your request an unsubscribe is triggered (including via the List-Unsubscribe standard).
  • Sending: Messages you write are sent through the SMTP server of your provider and – where possible – placed in the “Sent” folder of your mailbox. Signatures, scheduled sends, rules and drafts are stored.
  • HTML display: Email content is displayed in an isolated environment (sandbox iframe) and after cleaning by an HTML filter (DOMPurify), to prevent malicious code. Externally embedded content (e.g. tracking pixels, remote images) is loaded depending on your setting for blocking remote images. When loading, the external provider may in particular receive your IP address and the time of retrieval and may assign the retrieval to a specific message.

Appointments from calendar invitations are detected and stored for the calendar feature.

Appointment detection in emails

If the account setting “Detect appointments in emails” is switched on (default), the server searches newly incoming messages for appointments: in calendar files without a reply option, in machine-readable booking details (e.g. reservation or travel confirmations, can be switched off) and in dates and times in the text. Once, the messages of the past 30 days are also checked. The detection runs exclusively on our server, without AI and without transmission to third parties. For a suggestion, the title, time, place, a short text excerpt of the message and the sender are stored. A suggestion is adopted as an appointment only on your confirmation; no reply is ever sent to the sender. You can switch the detection off and exclude individual senders. The legal basis is Art. 6(1)(b) GDPR, and for data of the senders Art. 6(1)(f) GDPR.

For automatic mailbox configuration, the domain of the email address is queried at Thunderbird ISPDB and, where applicable, at the domain provider. For sender logos, the server queries the sender domain at DuckDuckGo and, where applicable, Google. The domain is transmitted, not the complete message. Newsletter unsubscribes can trigger a request to the address given in the newsletter.

If you yourself store an external address as a profile or contact picture, the browser may load the picture from that address. Its operator then receives in particular the IP address and technical retrieval data of your device. This is to be distinguished from the server-side retrieval of sender logos.

Spam and phishing protection

A spam filter operated by us (Rspamd) checks incoming messages including the header data. Depending on the check rule, it queries IP addresses, domains and hash values of email addresses, links or message components at external reputation services: Spamhaus, Mailspike, Spam Eating Monkey, DNSWL, Virusfree, blocklist.de, MSBL, SURBL, URIBL and rspamd.com (including the fuzzy check). These services do not receive the complete message content. Hash values may nevertheless be personal data. The filter also downloads protection lists such as those of OpenPhish; no message data is transmitted in doing so.

In link protection, domains can be checked by DNS at Spamhaus. If the resolution of short links is enabled, our server retrieves the complete short link including path and parameters. The short-link provider thereby receives the connection data of our server and can assign the retrieval to an individual link. The legal basis is Art. 6(1)(b) GDPR, and for data of other persons Art. 6(1)(f) GDPR (protection against harmful messages and links).

No analysis of the content of your messages for profiling or advertising purposes takes place. For the optional writing-style memory, only your own sent messages are analysed for style traits (section 6b, “Writing-style memory for AI drafts”).

Detection of invoices, returns and deadlines (“Open”)

Incoming messages are checked on our server with fixed rules for whether an invoice is to be paid by bank transfer, whether a shipment was delivered and a return period is running, whether a person names a deadline, or whether you promised something in a sent message. Attachments (PDF, XML, PNG) are read in memory for this; they are not stored additionally. Only the findings (for example sender, amount, due date, IBAN, invoice number, reference, date, a short text excerpt of the passage) are stored in the respective entry; they are deleted with the account. The automatic check is not done by an AI or by third parties; message text and attachments are not transmitted to third parties for it. Only if you explicitly choose “Read with AI” for a contract deadline and the AI features are set up are the visible text of that message and, if there is one, the text of its PDF attachment sent to the AI provider in the EU as described in section 6b. AllMailHub does not initiate payments. To find return periods, our server retrieves public pages of shops; the request contains only the shop’s domain, no information about you or your orders. When “Open” is switched on, the messages of the past 30 days that are already there (for your own unanswered questions, of the past 14 days) are checked once in the same way. You can switch off each type of detection under Settings › Open; it then no longer runs.

6a. Calendar, sharing and invitations

For the calendar feature we store calendar names, appointments with title, description, place, date, time and time zone, recurring series, reminders as well as participant addresses and acceptance or decline status. In addition there are shares, invitation links, changes and delivery information. Sources are your input, entries of other authorised calendar users and calendar invitations or replies from your connected mailboxes.

If you share a calendar, other persons can, depending on the permission granted, see busy times or appointment details and, where applicable, edit appointments or manage shares. Pass invitation links on only to the intended persons. Appointment participants and their email providers receive the appointment data transmitted for invitation, change or cancellation. Reminders can be delivered in the app, by email or through the push services described in section 7.

We process your own data to provide the calendar feature you requested (Art. 6(1)(b) GDPR). For data of other participants, section 6 applies accordingly. Removing a share does not delete copies that recipients have already stored in their own mailboxes or calendars.

Calendar links for other programs

Where this feature is offered for your plan, you can, as the owner of a calendar, create secret links through which other programs retrieve the calendar in read-only form (up to five per calendar). You choose whether only busy times, titles and places or all supported details including descriptions and links are transmitted. Participant and organiser details, reminders and attachments are not transmitted; private appointments appear only as busy. Appointments from 30 days in the past to 365 days in the future are transmitted; recurring series are transmitted in full. Free-text fields may contain details that you or other authorised members have entered.

The link is the access key: any person or application that knows it can retrieve the shared data without signing in. Pass it on only to the intended programs. These or their providers store the link and calendar data under their own responsibility. We store only an irreversible check value of the link, the last four characters as a hint and the time of the last retrieval, but no IP address or program identifier in this usage data. For the technical access and security logs, section 3 applies; the link address is not logged in them. Resetting or deleting a link prevents further retrievals but does not remove copies already downloaded. The legal basis is Art. 6(1)(b) GDPR, and for data of other persons Art. 6(1)(f) GDPR.

External calendars and video conference links

Appointments shown in an email can be added through a link to Google Calendar or Outlook. Only when you open this link are the details contained in it, such as title, description, place and appointment times, transmitted through the URL called to the chosen provider. Its terms of use and privacy notices apply there.

At your request, the calendar feature can generate a link to a room at meet.jit.si and enter it in the appointment. Generating the link is local and does not yet set up a video conference. When you open the link you use the external conference service; connection data and, after your approval, audio and video may be processed there. The room link is shared with the correspondingly authorised calendar users or invited participants. AllMailHub does not operate this public Jitsi instance itself.

6b. Optional AI features (processing in the EU)

If you use the AI revision of an email text or the AI detection of an appointment, the server sends the texts intended for this to the AI interface of Scaleway in the EU (see below). All AI features are off at first. They only become active once you give the release “AI features” and agree to the notice shown. The release covers every feature named in this section except the writing-style memory, for which you agree separately per mailbox. We store the time and text version of the release as proof. If you withdraw the release, AllMailHub no longer transmits anything for any of these features. If the account settings “Revise dictated emails with AI” or “Evaluate appointments with AI” are switched on and the server offers the feature, this happens automatically after a mail or calendar dictation is completed. For typed text, transmission takes place only when you expressly click “Check text” or the AI evaluation of an appointment. The account settings apply server-side to all clients including the Android and iOS apps: if a setting is switched off, AllMailHub transmits nothing for this feature. You can switch them on, agree and withdraw in the settings of the web application and the apps. The normal synchronisation of your mailboxes sends no messages for processing to these AI interfaces. You can also edit emails and appointments without the AI. For AI drafts of emails, the subsection “AI drafts for emails” at the end of this section applies in addition.

  • Dictated emails: The dictated text and the language are transmitted. Long texts are processed in sections; a short excerpt of the previous section may be sent along as context. Recipient field, subject, attachments and the earlier mail thread are not additionally retrieved from the mailbox or attached by this feature. For “Check text” in the web application and the apps, only the text to be checked and its language are transmitted; a passage automatically marked as a signature and quoted thread remain excluded. Names or other personal data that you yourself include in the text are, however, part of the transmission.
  • Appointment detection: Your entered or dictated sentence, language, time zone, reference time, the selected date and the pre-filled appointment times are transmitted. The AI creates an appointment suggestion from this. An existing calendar or the entire mailbox is not sent along with this request.
  • Voice input: The AllMailHub interfaces mentioned receive text, not an audio file. The preceding conversion of speech to text takes place by default exclusively on your device. AllMailHub only uses recognition through the platform provider’s service (browser manufacturer, Google or Apple) if you separately allow this after a dedicated notice; the audio may then also be processed outside the EU.

In the web application, voice input by default only uses speech recognition on your device (“On this device”). If your browser offers no local recognition, recognition through the browser manufacturer’s service (such as Google, Microsoft or Apple) can only be used if you separately allow it in the dictation dialog or in the settings; that service then processes the audio under its privacy terms, also outside the EU. Without this permission the browser does not dictate; typing remains possible. If the browser supports it, installation of a local language pack is offered. AllMailHub receives only the recognised text and neither records audio nor stores or logs it. You grant access to the microphone in your browser and can withdraw it there at any time.

On Android and iOS the apps by default recognise speech only on the device. If this is not possible on your device, recognition through Google or Apple can only be used after a dedicated notice and your separate permission in the app’s settings; the platform provider then processes the audio under its terms, also outside the EU.

The processing of your own data serves the additional service expressly requested in each case (Art. 6(1)(b) GDPR). Using the AI is not a blanket consent to the transmission of any third-party data. Do not enter third-party confidential content or special categories of personal data, such as health data, without a sound legal basis for doing so.

AI processing is carried out by Scaleway SAS, Paris, France, as a processor. It takes place exclusively in data centres in the EU; according to Scaleway, the models used run in a data centre in Paris operated by OPCORE. There is no transfer to the USA or other third countries for the AI. The language model used is DeepSeek V4.1 Flash with openly published weights, operated by Scaleway on its own servers; the model’s maker receives no data.

According to its description of data processing, Scaleway does not store requests and answers in normal operation and does not use them to train models. Exceptions: in the event of an abnormal error or possible misuse, Scaleway may keep the affected request for up to two weeks to reproduce and fix the issue; Scaleway keeps aggregated, anonymised usage data for up to six months. To speed up processing, Scaleway also automatically keeps a cache limited to our project (token cache) that cannot be switched off and is evicted according to how often it is used; Scaleway does not state a fixed duration for it.

The AI endpoints do not write the input text and the response to an application log of their own. For quota management, AI actions used are counted. Adopted texts and appointments are stored as a draft, sent message or calendar entry under the rules applicable to them. Check AI suggestions before adopting or sending them; they may contain errors.

AI drafts for emails

Where the server offers the feature and your plan includes AI actions, AllMailHub can, at your request, draft a reply or a new email and revise such a draft, for example shorter or more formal. The feature is switched off by default. You switch it on in the settings after a notice about the data transmitted and can switch it off again there at any time. Data is transmitted only when you expressly request an AI draft in the compose window or in the reading view, never when merely opening a message and never in the background. The only exception is the style analysis you expressly approve per mailbox (see “Writing-style memory for AI drafts”); it never creates drafts.

  • New email: Your note, the chosen preferences for tone, length and salutation, the language and the indication whether your signature already contains a closing phrase are transmitted.
  • Reply: In addition, the subject, date and sender name of the message you are replying to are transmitted, as well as its text and the file names of its attachments. Depending on the setting “Include previous thread”, the text is sent with or without the quoted thread, at most 6,000 characters. Recognisable signature and notice blocks are removed beforehand. If you have written to the sender before, only the greeting line (such as “Hello Katrin,”) and the recognised form of address (informal or formal) from your last such message are sent along, not its remaining content. If the writing-style memory is active, the style description derived from it is sent instead (see below).
  • Revision: The current draft text including your own changes and, where applicable, your instruction are transmitted.

Before transmission, the server replaces email addresses with a placeholder and links with their domain name. Recipient lists, attachment contents, other messages (except the style sample with “Understand style”, see below), contacts and credentials are not transmitted. For mailboxes that you exclude in the settings, for messages in the spam folder and for messages with indications of phishing or malware, no AI draft is created. What you yourself write in the note or draft is part of the transmission.

The message you reply to generally contains personal data of its sender and, where applicable, other persons. The legal basis is, for your data, Art. 6(1)(b) GDPR, and for data of other persons Art. 6(1)(f) GDPR. The legitimate interest lies in answering a received message, at your request, with assistance. The transmission is limited to the one message being answered, without its addresses, and with the writing-style memory also to the derived style description and, if approved, the style sample. Do not use the feature for content that you may not pass on to a processor, for example because of a duty of confidentiality, and exclude the mailboxes concerned.

Your settings and mailbox exclusions are stored, as well as the time and version of your switching it on as proof. On a draft it is noted whether it contains adopted AI text. To calculate your quota, usage sessions with time and number of calls are stored, without content; they are deleted after 35 days. Note, request and result are not logged. Adopted texts are stored as a draft or sent message. For processing by Scaleway, the information earlier in this section applies.

If a sent message contains adopted AI text that you have not discarded, AllMailHub sets the technical header “X-AI-Assisted: true”. Recipients and their mail systems can read this marking. It contains no further information on the content or the request.

Translation and search in plain language

The extended “AI features” release (text version 2026-11-ai-2) adds two purposes. If you gave the earlier release, you keep every existing feature unchanged. For the two new purposes AllMailHub asks once, with the updated notice, at your first click. If you withdraw the release, nothing goes to the AI for any purpose any more, and stored translations are deleted.

  • Translation on click: Only when you click “Translate” on a message, or choose “Translate to …” in the editor, the server sends the visible text of that message (subject and text, at most 16,000 characters) or your own text to the AI interface of Scaleway in the EU. The language for the hint “This mail is in …” is recognised on your device, without AI. Recognised links, e-mail addresses, IBANs and phone numbers are replaced by placeholders before the transfer and put back from the original after the translation; they are not sent to the AI. What cannot be recognised as such a value, for example a postal address or a number written in words, remains part of the text that is sent. Messages of excluded mailboxes, in the spam folder, with signs of phishing or malware, and from forged or suspicious senders are not translated. One AI action of your quota is charged per translation, only after success. Opening a stored translation again costs nothing.
  • Search in plain language: The rules (“from Telekom since July”) run on your device, without AI. Only when you click “Understand with AI” does the server send to the AI interface of Scaleway in the EU: your question (at most 300 characters), today’s date, your time zone, the language and the providers of your mailboxes (e.g. “GMX”, “Gmail”; no addresses and no names of your mailboxes). What you write in the question yourself, such as names or addresses, is transmitted with it. Message content and results are never transmitted. The answer is turned into search operators on our server, and the search itself runs on our server. Nothing is stored at the provider beyond the processing. The server remembers identical questions of the same day for 10 minutes, in memory only; a hit costs nothing. The question is not logged. One AI action is charged per evaluation, only after success.

We store a translated message for 30 days (translated subject and text, without the replaced links, addresses, IBANs and phone numbers) so that opening it again costs nothing. The translation is deleted at once if you withdraw the AI release or exclude or delete a mailbox, and at the next hourly clean-up if the message has been deleted. It is part of the data export. The text of a translation is not logged. For the processing by Scaleway, the statements earlier in this section apply. The legal basis is Art. 6(1)(b) GDPR for your data and Art. 6(1)(f) GDPR for the data of other people in the message (legitimate interest: understanding a message in a foreign language at your request).

Writing-style memory for AI drafts

If the server offers the feature and your plan includes it (Pro, Max), AllMailHub learns from your own sent messages, with AI drafts switched on, how you write in a mailbox and to individual people. For this, our server itself analyses the messages in your Sent folders (“Measure style”, can be switched off per mailbox): length, sentence length, paragraphs, emoji, punctuation, abbreviations, form of address (informal or formal), language and the greeting line and closing you used. Quoted and forwarded content of others and signatures are excluded as far as recognisable. Per message, only these measurements with the recipient addresses are stored, no full message texts, at most the 300 newest per mailbox.

When you request an AI draft, the server additionally transmits a style description derived from this (such as “informal, usually 30 to 60 words, rarely emoji, greeting ‘Hi Denise,’”) and your own note on the contact, if you have added one. Recipient addresses are not transmitted.

Only if you additionally and expressly switch on “Understand style” for a mailbox does the server transmit your own sent messages from that mailbox to Scaleway, shortened and without addresses and quotes, to determine tone, formality and typical phrases as fixed values. This happens in batches, also in the background, with a maximum per plan, and never for excluded mailboxes. A draft then also includes a short style sample (two to three sentences of your own message to the same person); you can switch this off separately. We store the time, text version and withdrawal of this approval as proof. Withdrawal ends the transmission immediately and deletes the traits determined by the AI.

Your own messages contain information about their recipients. The legal basis is, for your data, Art. 6(1)(b) GDPR, for “Understand style” additionally your consent under Art. 6(1)(a) GDPR, and for data of other persons Art. 6(1)(f) GDPR. The legitimate interest lies in creating drafts in your own style. We do not store statements about people.

You can view what has been learned per mailbox and per contact, fix values and choose “Forget” at any time; messages already analysed are then not learned again. If you switch off “Measure style” or AI drafts, or your plan no longer includes the feature, the data is no longer used and is deleted after 90 days. Contact profiles are deleted with the contact. The data export includes the stored style information.

6c. AI connector: access by AI applications you connect

Depending on the plan and activation, you can connect an AI application of another provider (such as an AI assistant that supports the Model Context Protocol) to your AllMailHub account. The connection arises only through your express approval in the signed-in account; if the last sign-in was longer ago, it is asked for again beforehand. You select the areas (profile, emails, calendar, contacts) and the mailboxes. For reading, the connected application can retrieve, within the approved scope, profile details, messages with header data and text, appointments and contacts.

If you additionally approve “Create drafts” or “Propose sending” (neither is ever preselected), the application can create email drafts in the sender mailboxes you choose, change or delete the drafts it created and propose sending such a draft. The application cannot send: a message is only sent once you review and approve the proposal in a signed-in AllMailHub session. Proposals you do not decide on expire after seven days. While a proposal is open, we store a copy of the proposed content so that you approve exactly this content; it is deleted with your decision, the withdrawal or the expiry. AI drafts are stored like your other drafts and synchronised with the drafts folder of your email provider, where they are also visible in other email programs. Messages you approve carry the header “X-AI-Assisted: true”, which marks the AI assistance. The content of a draft comes from the provider of the application; review it before approving.

We transmit the retrieved data, at your request, to the provider of the application you have chosen. It processes the data under its own terms and privacy notices; it is not our processor, and we have no influence on its processing, retention period or processing locations. A transfer to third countries, in particular the USA, is possible depending on the provider. The data may also contain details of other persons, such as senders, recipients or appointment participants. The legal basis is Art. 6(1)(b) GDPR, and for data of other persons Art. 6(1)(f) GDPR. Connect the connector only with applications to which you wish to entrust this data, and do not approve mailboxes with content that you may not pass on.

Access tokens are valid for one hour at most, renewal tokens for 30 days at most, a connection for 90 days at most; we store tokens only as a check value. Every access is logged without content (time, function used, result, number of hits, duration); this access log is deleted after 90 days. Drafts and send proposals are likewise logged without content and without addresses (time, function, number of recipients, checksum, result); this log and the content-free record of a proposal (state and times) are deleted after 90 days, evidence against duplicate execution after 24 hours. You can disconnect a connection at any time under “Connected apps”. After that no further retrievals are possible; copies that the provider has already received are not deleted by this.

7. Real-time notifications and push

In the browser, new messages are signalled through a direct, encrypted connection to the service (WebSocket); no third-party provider is involved.

When the feature is used, mobile push notifications are delivered on Android through Firebase Cloud Messaging (Google) and on iOS directly through the Apple Push Notification service. In doing so, device push tokens, sender, subject and, where applicable, a text excerpt of the message as well as internal message and mailbox identifiers are transmitted to the respective push provider. For calendar notifications, appointment title, appointment time, calendar name and details of the inviting or changing person may also be transmitted. The legal basis is Art. 6(1)(b) GDPR (notification feature you use), and for data of senders Art. 6(1)(f) GDPR. You can switch off notifications per mailbox in AllMailHub and in the settings of your device. If you switch off the preview in notifications under “Settings → Notifications”, the transmitted notifications contain neither sender, subject nor text excerpt and, for events, neither title, place, calendar name nor names of persons, only a general notice, for events the event time, and the internal identifiers. Processing in the USA is possible; for the transfer see section 11.

Browser notifications

If you allow desktop notifications, the browser can display incoming messages even outside the open window. In doing so, sender and subject may become visible to other people at your screen. You can change the permission in your browser’s website settings. For mobile notifications, the operating system’s settings additionally apply, in particular for previews on the lock screen.

8. Contact, cancellation and withdrawal

When you contact us, we process your contact details and your request in order to handle the enquiry (Art. 6(1)(b) or (f) GDPR). The public contract functions store name, contact email, contract designation, content of the declaration and time of receipt and, for cancellations, the desired end date, the type of cancellation and any reason given. This information is needed to process, confirm and prove your declaration (Art. 6(1)(b) and (c) GDPR, Sections 312k, 356a of the German Civil Code (BGB)). Receipt is independent of the subsequent sending of emails. For a Paddle purchase, the assignment and processing with Paddle is additionally required.

Support form

If you use the support form in the signed-in account, we transmit the type of request, subject, your message, the page called up, a browser indication as well as the email address and internal identifier of your account to our ticket system Zoho Desk. Zoho Corporation B.V. (Netherlands) operates it for us as a processor in a data centre in the EU; access by Zoho companies outside the EU for operational and support purposes is possible under their contract terms (see section 11). Mailbox content, contacts, logs or credentials are not transmitted unless you write them into the message yourself. To avoid duplicate tickets, in AllMailHub we store the ticket number, the status, the email address and a check value of the request. The purpose is to handle your request (Art. 6(1)(b) GDPR, for general enquiries (f) GDPR).

9. Payment processing

Paid plans are processed through the Paddle company named at checkout as “Merchant of Record”. Paddle collects and processes the data necessary for the purchase (including name, billing address, email address, means of payment, transaction and tax data) under its own responsibility under data protection law; the privacy notices of Paddle apply. The Provider receives from Paddle the information necessary for contract and account management (e.g. plan booked, payment status, billing period, invoice number). The legal basis is Art. 6(1)(b) GDPR and – for the retention of invoice documents – Art. 6(1)(c) GDPR in conjunction with tax and commercial law obligations.

The checkout uses the JavaScript loaded by Paddle.

10. Transactional emails

For account management we send emails such as registration confirmation, verification and reminders of a still outstanding confirmation, password reset, security notices and contract or change notifications. The legal basis is Art. 6(1)(b) GDPR, and for legally required contract confirmations Art. 6(1)(c) GDPR. Sending takes place through our own mail server on Hetzner infrastructure in Germany. The recipient address and content are also processed by the recipient’s mail provider.

10a. Referral programme

In the voluntary referral programme we assign a personal code to the inviting account and to a new registration. The benefit requested in the link is stored in the tab’s sessionStorage until registration; the entry is removed after successful registration or when the session is closed. No referral cookies or additional analytics identifiers are set. The storage serves the benefit requested (Section 25(2) No. 2 TDDDG).

To carry it out, we process the code assignment, registration and confirmation times, qualification status, plan credits and the Paddle transaction identifier belonging to the first payment together with its refund status (Art. 6(1)(b) GDPR). For a running subscription, we postpone the next billing date by one month through Paddle; the subscription identifier is transmitted to Paddle for this. The check of the conditions runs automatically once a day. To prevent self-invitations and multiple use, we compare normalised login and connected mailbox addresses of the two accounts and check disposable domains as well as conspicuous clusters (Art. 6(1)(f) GDPR; legitimate interest in protection against abusive credits). Cases of doubt are checked manually; contact support for a review. No additional IP addresses or device characteristics are stored for this.

Inviting persons see only numbers and status, no names or addresses of invited persons. AllMailHub does not send invitation emails to third parties and does not import contacts for this. System emails inform beneficiaries about credits and their expiry. Programme-related account assignments exist during participation; on account deletion, personal credits and rewards are deleted and remaining referrals are detached from the deleted account assignment. Billing and security records are additionally subject to the retention rules stated below. Referrals without a remaining account assignment are removed in the next processing run.

11. Recipients and third-country transfers

Recipients of your data are the service providers named in the Subprocessors list as well as – at your request – the respective mailbox provider when retrieving and sending messages.

  • Scaleway: The contracting party is Scaleway SAS, France. AI processing takes place in data centres in the EU; there is no transfer to third countries for it (see section 6b).
  • Google (Firebase Cloud Messaging) and Apple (Push Notification service): A transfer to the USA is possible. It takes place on the basis of the adequacy decision of the EU Commission on the EU-US Data Privacy Framework of 10 July 2023, under which the respective US companies are certified, as well as the providers’ standard contractual clauses.
  • Zoho (support form): The contracting party is Zoho Corporation B.V. with storage in the EU. Where Zoho companies outside the EU, such as in India, access as subprocessors, this takes place on the basis of the safeguards agreed in Zoho’s data processing agreement (standard contractual clauses).
  • Grafana Labs (error and operations monitoring): The logs are stored in the EU (Germany). The contracting party is the US company Raintank, Inc. dba Grafana Labs. For access from the USA, the transfer relies on the adequacy decision on the EU-US Data Privacy Framework, under which Grafana Labs is certified, and on the standard contractual clauses agreed in the data processing agreement.
  • Providers of connected AI applications (AI connector): The transfer takes place at your request to the provider you have chosen. Whether it processes outside the EU and which safeguards it relies on follows from its terms (see section 6c).
  • Paddle: For the United Kingdom there is an adequacy decision of the EU Commission. It does not automatically cover subsequent transfers to other countries; Paddle describes these in its privacy notices.
  • Mailbox providers: Your messages are exchanged with the provider you connect yourself. If it is established outside the EU or the EEA (e.g. Google or Microsoft in the USA), the transfer relies on the adequacy decision on the EU-US Data Privacy Framework, to the extent that the provider is certified.

12. Retention periods

Account and settings data
Duration
for the duration of the contract of use; then deletion as part of account deletion (see below)
Unconfirmed accounts including registration details
Duration
14 days after registration, then permanent deletion without a recovery period; except accounts with payment or subscription data (see section 4)
Confirmation code and link (as check value)
Duration
60 minutes; a new code replaces the previous one
Mailbox credentials
Duration
until the mailbox is removed or the account is deleted
Sign-in attempts at your mailbox (time, result, error class, occasion, account and user assignment)
Duration
14 days; attempts still open until they are completed. If the mailbox is removed, account assignment, error class and error code are dropped immediately; the rest (user, time, rough result) is kept for 7 days at most. With the final account deletion, all attempts are deleted
Session overview of the mailbox connections
Duration
as long as the connection exists, then 24 hours; immediately when the mailbox is removed
Failed-attempt status per mailbox (number and time of failed attempts)
Duration
until successful retrieval, change of credentials or removal of the mailbox
Operational counters on sign-ins (per minute or hour and provider group, without account, user or server reference)
Duration
per-minute values 14 days, per-hour values 395 days (about 13 months)
Stored email copies, attachments, contacts, rules, signatures
Duration
until deleted by you or until account deletion
Calendar, appointments, shares, invitations and change history
Duration
for the respective calendar feature; deletions may initially affect a recoverable recycle bin. In shared calendars, access and deletion also depend on ownership and permissions. Recipient copies already transmitted are not recalled
Appointment suggestions from emails
Duration
open and rejected suggestions until 30 days after the appointment or until the message is deleted; adopted suggestions 90 days after adoption (the appointment itself remains in the calendar)
Calendar links (check value, hint, last retrieval)
Duration
until the link, the calendar or the creator account is deleted; a change of owner deletes all links of the calendar
AI connector: connections and tokens
Duration
access tokens 1 hour at most, renewal tokens 30 days at most, connections 90 days at most; records to defend against repeated tokens briefly beyond that
AI connector: access log (without content)
Duration
90 days
AI connector: copy of an open send proposal
Duration
until your decision, the withdrawal or the expiry after seven days
AI connector: log of drafts and proposals, records (without content and addresses)
Duration
90 days; evidence against duplicate execution 24 hours
Support requests
Duration
in AllMailHub the ticket assignment until account deletion; in the ticket system until resolved and then until expiry of the regular limitation period (Sections 195, 199 BGB)
AI drafts: usage sessions (time, number of calls, without content)
Duration
35 days
Writing-style memory: measurements of your own sent messages (no message texts)
Duration
at most the 300 newest per mailbox; immediately on “Forget”, exclusion of the mailbox or account deletion; 90 days after switching off or loss in the plan
Writing-style memory: fixed values, notes and traits determined by the AI
Duration
until you change them or choose “Forget”, with the contact or mailbox; 90 days after switching off or loss in the plan; AI traits also until “Understand style” is withdrawn
Writing-style memory: proof of “Understand style” (time, text version, withdrawal)
Duration
until account deletion
Translations of received messages (subject and text, without links, addresses, IBANs, phone numbers)
Duration
30 days; at once on withdrawal of the AI release, exclusion or deletion of the mailbox; for a deleted message at the next hourly clean-up
AI inputs and results
Duration
in the AllMailHub AI endpoint for processing the request, without a log of content of its own; adopted results under the rules for drafts, emails or appointments. For external retention at Scaleway see section 6b
Statistical learning data of the spam filter (per account)
Duration
deletion once they have not been updated for 100 days; this also applies after account deletion
Cached short-link resolutions of the spam filter
Duration
1 day
Server and application logs
Duration
on our servers 7 days at most
Logs transmitted to Grafana Cloud for error and operations monitoring
Duration
14 days
Separately stored security events
Duration
90 days at most
Backups and file versions
Duration
30 days at most
Data exports provided
Duration
7 days; on final account deletion, existing exports are additionally removed
Cancellation and withdrawal declarations
Duration
until expiry of the regular limitation period (three years from the end of the year of the declaration, Sections 195, 199 BGB)
Tax-relevant documents
Duration
under the statutory retention periods (Section 147 of the German Fiscal Code (AO))
DataDuration
Account and settings datafor the duration of the contract of use; then deletion as part of account deletion (see below)
Unconfirmed accounts including registration details14 days after registration, then permanent deletion without a recovery period; except accounts with payment or subscription data (see section 4)
Confirmation code and link (as check value)60 minutes; a new code replaces the previous one
Mailbox credentialsuntil the mailbox is removed or the account is deleted
Sign-in attempts at your mailbox (time, result, error class, occasion, account and user assignment)14 days; attempts still open until they are completed. If the mailbox is removed, account assignment, error class and error code are dropped immediately; the rest (user, time, rough result) is kept for 7 days at most. With the final account deletion, all attempts are deleted
Session overview of the mailbox connectionsas long as the connection exists, then 24 hours; immediately when the mailbox is removed
Failed-attempt status per mailbox (number and time of failed attempts)until successful retrieval, change of credentials or removal of the mailbox
Operational counters on sign-ins (per minute or hour and provider group, without account, user or server reference)per-minute values 14 days, per-hour values 395 days (about 13 months)
Stored email copies, attachments, contacts, rules, signaturesuntil deleted by you or until account deletion
Calendar, appointments, shares, invitations and change historyfor the respective calendar feature; deletions may initially affect a recoverable recycle bin. In shared calendars, access and deletion also depend on ownership and permissions. Recipient copies already transmitted are not recalled
Appointment suggestions from emailsopen and rejected suggestions until 30 days after the appointment or until the message is deleted; adopted suggestions 90 days after adoption (the appointment itself remains in the calendar)
Calendar links (check value, hint, last retrieval)until the link, the calendar or the creator account is deleted; a change of owner deletes all links of the calendar
AI connector: connections and tokensaccess tokens 1 hour at most, renewal tokens 30 days at most, connections 90 days at most; records to defend against repeated tokens briefly beyond that
AI connector: access log (without content)90 days
AI connector: copy of an open send proposaluntil your decision, the withdrawal or the expiry after seven days
AI connector: log of drafts and proposals, records (without content and addresses)90 days; evidence against duplicate execution 24 hours
Support requestsin AllMailHub the ticket assignment until account deletion; in the ticket system until resolved and then until expiry of the regular limitation period (Sections 195, 199 BGB)
AI drafts: usage sessions (time, number of calls, without content)35 days
Writing-style memory: measurements of your own sent messages (no message texts)at most the 300 newest per mailbox; immediately on “Forget”, exclusion of the mailbox or account deletion; 90 days after switching off or loss in the plan
Writing-style memory: fixed values, notes and traits determined by the AIuntil you change them or choose “Forget”, with the contact or mailbox; 90 days after switching off or loss in the plan; AI traits also until “Understand style” is withdrawn
Writing-style memory: proof of “Understand style” (time, text version, withdrawal)until account deletion
Translations of received messages (subject and text, without links, addresses, IBANs, phone numbers)30 days; at once on withdrawal of the AI release, exclusion or deletion of the mailbox; for a deleted message at the next hourly clean-up
AI inputs and resultsin the AllMailHub AI endpoint for processing the request, without a log of content of its own; adopted results under the rules for drafts, emails or appointments. For external retention at Scaleway see section 6b
Statistical learning data of the spam filter (per account)deletion once they have not been updated for 100 days; this also applies after account deletion
Cached short-link resolutions of the spam filter1 day
Server and application logson our servers 7 days at most
Logs transmitted to Grafana Cloud for error and operations monitoring14 days
Separately stored security events90 days at most
Backups and file versions30 days at most
Data exports provided7 days; on final account deletion, existing exports are additionally removed
Cancellation and withdrawal declarationsuntil expiry of the regular limitation period (three years from the end of the year of the declaration, Sections 195, 199 BGB)
Tax-relevant documentsunder the statutory retention periods (Section 147 of the German Fiscal Code (AO))

The periods for logs and account data relate to the active systems. A backup created earlier may still contain this data until the end of its own retention period; backups are not used for regular operation.

Account deletion: After deletion is initiated, the account is placed in a pending-deletion status and can be restored within 30 days; final deletion then begins. If the removal of attachments or search data fails, deletion is attempted again; the record is not treated prematurely as completely deleted. Security and contract records are subject to their separate periods. Backups are removed after the period stated above. The mailboxes with the third-party provider remain unaffected.

For shared calendars, account deletion in the account may initially require that you transfer or remove the calendars, cancel invitations you organised and resolve open delivery problems. The application shows these cases separately. This concerns the technical self-service process and does not restrict any statutory data protection rights.

The account recovery period does not restrict your right to erasure under Art. 17 GDPR. For such a request you can contact info@allmailhub.com directly; we examine it independently of the account recovery function.

13. Your rights

Under the GDPR you have the following rights:

  • Access to the data processed about you (Art. 15)
  • Rectification of inaccurate data (Art. 16)
  • Erasure (Art. 17) and restriction of processing (Art. 18)
  • Data portability (Art. 20)
  • Withdrawal of consent given, with effect for the future (Art. 7(3)); the lawfulness of the processing before the withdrawal remains unaffected

Right to object under Art. 21 GDPR

Where we process your data on the basis of legitimate interests (Art. 6(1)(f) GDPR), you can object to this processing at any time on grounds relating to your particular situation. We will then no longer process the data unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. You can address your objection informally to info@allmailhub.com.

You can exercise many of these rights directly in the account: data export as MBOX/EML, deleting individual messages, removing mailboxes, adjusting the settings and account deletion. You can also reach us at info@allmailhub.com.

We generally process requests within one month of receipt (Art. 12(3) GDPR). In the case of an extension permitted by law, we inform you of the reasons within this month. A data protection request requires neither the cancellation of a plan nor the waiver of other statutory rights.

No automated decision with legal effect

The AI features described create suggestions that you check and adopt yourself. They therefore involve no solely automated decision with legal or similarly significant effect on you within the meaning of Art. 22 GDPR.

14. Right to lodge a complaint with a supervisory authority

You have the right to lodge a complaint with a data protection supervisory authority. The authority responsible for the controller is:

Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Baden-Württemberg
Heilbronner Straße 35, 70191 Stuttgart
Telephone: 0711/615541-0, email: poststelle@lfdi.bwl.de

Contact and complaint options of the LfDI Baden-Württemberg

15. Data security

We take technical and organisational measures in line with the state of the art, including TLS for website access, AES-256-GCM encryption of the stored mailbox credentials, access restrictions, rate limiting, server-side cleaning of email HTML and optional two-factor authentication for your account.

16. Changes to this policy

We adapt this privacy policy when the processing or the legal situation changes. The version published on this page applies in each case. In the event of material changes, we additionally inform signed-in users in text form.

Cancel contracts here (German form)Withdraw from contract (German form)
AllMailHub

All mailboxes. One inbox.
© 2026 AllMailHub

DEENFR
Product
  • Features
  • Calendar
  • AI assistant
  • Apps
  • Pricing & plans
  • Moving from Gmail
  • Gmailify alternative
Help
  • Help Center
  • Connect Gmail
  • Connect Outlook
  • Connect Yahoo
  • Contact
Legal
  • Security
  • Imprint
  • Privacy
  • Terms
  • Right of withdrawal
  • Subprocessors
Cancel contracts hereWithdraw from contract