Privacy Policy

Last updated: 2026-04-14

1. Data Controller

Kotekorbya Technologies di Jacopo Di Pumpo

VAT / P.IVA: IT14253050968

General inquiries: contact@imap.pm

Data Protection Officer (DPO): dpo@imap.pm

imap.pm is an email routing service that connects IMAP mailboxes to messaging platforms (Telegram, Discord, webhooks). This privacy policy explains what data is processed, how it is handled, and your rights regarding that data.

Kotekorbya Technologies di Jacopo Di Pumpo (“we”, “us”, “the Controller”) is the data controller (responsabile del trattamento) for all personal data processed through imap.pm, pursuant to EU Regulation 2016/679 (GDPR) and Italian Legislative Decree 196/2003 as amended.

2. Data We Process

2.1 Email Content

When a new email arrives in a monitored IMAP mailbox, imap.pm reads the following from the mail server:

Processing: Email content is forwarded in real time to the configured destination (Telegram chat, Discord channel, webhook endpoint). The email body is truncated to platform limits (4,096 characters for Telegram). Attachments up to 20 MB are forwarded.

Storage: Email content is not stored persistently on the imap.pm server. When mail previews are enabled, a temporary encrypted cache may be created with a configurable TTL (default: 8 hours). Cached previews can be permanently destroyed by the user via PIN.

2.2 IMAP Credentials

2.3 Admin User Accounts

2.4 Message UID Tracking

To avoid re-sending previously forwarded emails, imap.pm stores the UID (unique identifier) of each processed message. UIDs are numeric identifiers assigned by the IMAP server and do not contain email content.

2.5 Destination Configuration

2.6 IP Addresses

IP addresses are processed for rate limiting on the mail preview destroy feature (PIN verification). They are stored in memory only and are not persisted to disk. No IP-based tracking or analytics is performed.

2.7 Failure Logs

A rolling buffer of up to 200 failure log entries is maintained in memory. Entries include: timestamp, HTTP status code, request path, and error message. Log entries may contain email addresses from failed operations. Logs are not persisted to disk and are lost on server restart.

3. How Data is Used

DataPurposeLegal Basis (GDPR)
Email contentForwarding to configured destinationLegitimate interest / consent of mailbox owner
IMAP credentialsConnecting to mail serverContract performance
Admin credentialsAuthentication and access controlContract performance
Message UIDsPreventing duplicate deliveryLegitimate interest
IP addressesRate limiting (anti-abuse)Legitimate interest
Failure logsDebugging and operational monitoringLegitimate interest

4. Third-Party Services

imap.pm transmits data to the following third-party services as configured by the administrator:

ServiceData TransmittedPurpose
Telegram Bot APIMessage text, attachments, chat IDDelivering email notifications to Telegram
Discord WebhooksMessage text, attachments, channel IDDelivering email notifications to Discord
Custom WebhooksMessage JSON payloadDelivering email notifications to user-configured endpoints
Google FontsBrowser IP, user agent (client-side)Loading web fonts for the admin interface

The IMAP connection is made directly to the mail provider specified by the user. imap.pm does not proxy IMAP traffic through any third party.

5. Data Retention

DataRetention Period
Email content (forwarded)Not stored. Forwarded in real time and discarded.
Mail preview cacheConfigurable TTL (default 8 hours). Destroyed on PIN request or expiry.
Message UIDsIndefinite (required to prevent re-sending). Deleted when account is removed.
IMAP credentialsUntil the account is deleted by the admin.
Admin user accountsUntil deleted by an owner.
Subscription metadata (plan/customer/subscription IDs, billing status)Stored while account is active and retained for compliance and accounting requirements.
Planless/expired account deadline dataUp to 2 months grace window before account expiry, shown live in the admin profile for GDPR transparency.
Short linksConfigurable TTL (1 day to 1 year, or indefinite).
Failure logsIn-memory only. Rolling buffer of 200 entries. Lost on restart.
Session cookies24 hours.

If no plan is selected, or if a subscription expires/cancels, the account remains viewable in admin with a live deadline countdown and expires after a grace period (2 months) unless a valid plan is added. This retention/expiry mechanism is applied to satisfy GDPR data minimization and storage limitation principles.

6. Data Security

7. Your Rights (GDPR)

If you are located in the European Economic Area (EEA), you have the following rights under the General Data Protection Regulation:

To exercise these rights, contact the administrator of the imap.pm instance you are using.

8. No Analytics or Advertising

imap.pm does not use any analytics services, tracking pixels, advertising networks, or behavioral profiling. No data is sold or shared with data brokers.

9. International Transfers

Data is processed on the server where imap.pm is deployed. Email content is transmitted to third-party messaging platforms (Telegram, Discord) whose servers may be located in different jurisdictions. The administrator is responsible for ensuring appropriate data transfer mechanisms are in place.

10. Children

imap.pm is not intended for use by individuals under the age of 16. The service does not knowingly process data from children.

11. Changes to This Policy

This policy may be updated to reflect changes in the service. The “Last updated” date at the top indicates the most recent revision.

12. Contact

For privacy-related inquiries or to exercise your GDPR rights, contact us at:

Kotekorbya Technologies di Jacopo Di Pumpo

General inquiries: contact@imap.pm

Data Protection Officer (DPO): dpo@imap.pm

VAT / P.IVA: IT14253050968

You also have the right to lodge a complaint with the Italian Data Protection Authority (Garante per la protezione dei dati personali) at www.garanteprivacy.it.