Email Alarm for iOS Privacy Policy

Updated: October 9, 2026

Who operates this app

Email Alarm for iOS is operated by Luciano Reverberi. Privacy questions: support@email-alarm.com.

What we access

With your authorization, we access sender, subject, message identifiers and dates to detect new emails and evaluate your rules. Gmail uses gmail.metadata and Outlook uses basic mail read permissions. We do not request access to message bodies or attachments, or permission to send emails.

What we store and why

The server stores your connected account, rules, matching terms, time zone, language, status and device notification token to deliver alerts. Access renewal credentials and matching alert details are encrypted. Rules and identifiers are retained to operate the service.

History and retention

Processing jobs and remote alert details are removed by scheduled cleanup once they are older than seven days. Connection information remains while the account is linked. Rules and the latest 20 events are stored on your phone. Infrastructure providers may also retain technical logs and backups under their policies; deleting active data does not imply immediate removal from those copies.

How we protect data

We use HTTPS/TLS for data in transit. Access-renewal credentials and remote alert details are encrypted at rest with AES-256-GCM, and the encryption key is kept separately from the database in protected server configuration. Authenticated sessions, access controls and least-privilege permissions limit access to the service. No security method can guarantee absolute protection, but we maintain procedures designed to protect the confidentiality and integrity of Google user data.

How and with whom we share, transfer or disclose data

We disclose Google user data only to the service providers listed below, and only to operate the features requested by you. They process data on our behalf for these stated purposes and may process it outside your country:

• Google provides OAuth authorization, the Gmail API and Pub/Sub delivery used to notify Email Alarm of mailbox changes.
• Vercel hosts the application server that receives Gmail events and checks sender and subject against your rules.
• Neon hosts the database that stores the connected account, encrypted access-renewal credentials, rules, message identifiers and limited alert details described in this policy.
• Expo and Apple Push Notification service (APNs) receive the device notification token and a generic alert payload needed to deliver the notification. That payload does not contain the sender, subject, email body or attachments.

Microsoft is used only when you separately connect an Outlook or Hotmail account; Google user data is not disclosed to Microsoft. We may disclose the minimum information required by law, legal process, or to protect users, the public, our rights or the security of the service. If Email Alarm is involved in a merger, acquisition or asset transfer, data may be transferred to the successor subject to this policy and applicable law, with notice where required.

Your controls

You can pause alerts without disconnecting, or disconnect an account in Settings. Disconnecting requires Internet and, when completed, removes the connection and associated active data from the server. Local history and rules are removed separately in the app. You can also revoke permissions in Google or Microsoft. Contact us to request access, correction or deletion of your data.

Limited use of data

We do not sell email data or use it for advertising or training AI models. We do not share Google user data with data brokers or other third parties for their own purposes. Email Alarm’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Changes and contact

We will publish updates on this page with their date. This policy covers iOS; the Android version processes notifications differently and has its own policy.

Support messages

If you email support@email-alarm.com, Resend receives and stores the message, your email address and any attachments you choose to send so we can provide support. This is separate from the limited email metadata processed by the app. Do not send passwords or verification codes. Contact us to request deletion of support correspondence.