Pulse
FeaturesHow It WorksPrivacySupport
Coming soon
FeaturesHow It WorksPrivacy PolicyTerms of ServiceData DeletionSupport

Privacy Policy

Your inbox data stays under your control.

This policy explains exactly what Pulse reads, why it is needed, where it is processed, and how you can remove it.

Effective date: July 13, 2026

At a glance

Pulse uses read-only Gmail and Microsoft access. Email analysis and storage happen on your device, not on a Pulse server.

Questions or support →
01

Who we are

Pulse is an independent iPhone email-security application developed and provided by JalenKidd, the business name used for Pulse (“Pulse,” “we,” “us,” or “our”). Pulse helps users review warning signals in Gmail, Outlook, Hotmail, and supported Microsoft 365 inboxes they choose to connect.

This Privacy Policy applies to the Pulse mobile application and this public Pulse website. Google, Microsoft, Apple, GitHub, and other third-party services have their own privacy policies.

02

Information Pulse accesses

When you connect an inbox, Pulse accesses only the information needed for its visible features:

  • Your connected account’s email address, display name, provider, and provider account identifier;
  • OAuth access and refresh tokens needed to maintain the connection;
  • Message identifiers, sender information, subject lines, received timestamps, and the short message preview supplied by your email provider; and
  • Your in-app choices, including account names and icons, scan window, category changes, alert resolution state, and deletion state.
What Pulse does not access

Pulse does not request permission to send email, change email, or delete messages from your mailbox. The current version does not request or analyze attachments and does not intentionally retrieve full message bodies.

03

Google account and Gmail data

If you connect Gmail, Pulse requests the Gmail read-only permission. Pulse uses this permission to retrieve recent message identifiers and the limited message fields described above, then presents security categories, explanations, activity, and trends to you inside the App.

Google Limited Use disclosure

Pulse’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google user data is not used for advertising, sold, provided to data brokers, used to determine creditworthiness, or used to train a general-purpose artificial intelligence or machine-learning model. The developer does not allow humans to read Google mailbox data because that data is not sent to the developer.

04

Microsoft account and mailbox data

If you connect Outlook, Hotmail, or Microsoft 365, Pulse requests Mail.Read and User.Read. Mail.Read is used for the recent message fields described above. User.Read is used to identify the connected account. Pulse does not sell Microsoft user data or use it for advertising.

Access to work or school Microsoft 365 accounts may be restricted by the account owner’s organization and may require administrator approval.

05

How information is used

Pulse uses connected-account information only to provide features you can see and control, including to:

  • Connect the inboxes you authorize;
  • Classify recent messages using sender, subject, and available preview signals;
  • Explain why a message may be safe, spam, promotional, social, an update, or in need of review;
  • Show account health, recent activity, trends, and unresolved alerts;
  • Remember your account labels, category corrections, resolved alerts, deleted items, and settings; and
  • Protect, troubleshoot, and maintain the App.

Pulse produces heuristic risk signals, not guarantees. A finding may be incorrect, and Pulse may miss a harmful message.

06

On-device processing and storage

Email-derived data is analyzed and cached locally in the Pulse app on your iPhone. Pulse does not operate a backend service that receives or stores your mailbox data, and there is no separate Pulse cloud account in the current version.

  • OAuth tokens and connected-account credentials are stored in the iOS Keychain using device-only protection;
  • Cached activity, classifications, alert state, and deletion state are stored in the App’s local database; and
  • Preferences and account customizations are stored in the App’s local settings.

Apple may handle device backups according to your device-backup settings. Those backups are controlled by Apple and your device settings, not by Pulse.

07

When Pulse scans

You choose a 7-, 14-, or 30-day scan window. Pulse checks that period when the App launches, when you tap Refresh, and when iOS grants an optional scheduled background refresh for enabled scan notifications. Pulse does not continuously monitor your inbox, and iOS does not guarantee when background refresh will run.

08

Sharing and service providers

Pulse does not sell personal information or connected-account data and does not share it for targeted advertising. The App communicates directly with Google or Microsoft to provide the connection you authorize. The current App does not include third-party advertising, analytics, or crash-reporting services that receive mailbox data.

This website may generate ordinary network and security logs through its hosting provider. If you open a support issue, GitHub processes the information you submit under GitHub’s own privacy terms. Do not post passwords, OAuth tokens, authentication codes, or private email content in a support issue.

Information may be disclosed if required by valid legal process. Because mailbox data is not sent to Pulse’s developer, we generally do not possess mailbox data to disclose.

09

Retention

Active cached email activity is limited to your selected 7-, 14-, or 30-day scan window and is trimmed as the window changes. Items you move to Recently Deleted are kept locally for up to 30 days unless you permanently delete them sooner. Resolved activity remains local while it is within the active scan window or until you delete Pulse data.

Provider tokens remain in the iOS Keychain until you disconnect the account, use Delete Pulse Data, revoke access with the provider, or the credentials otherwise expire or become invalid.

10

Your deletion and disconnection controls

In Pulse, open Settings → Delete Pulse Data to disconnect every inbox and erase cached activity, alert history, account customizations, tokens, and Pulse preferences from the device. You can also disconnect one inbox at a time from Accounts. These actions do not delete or change the original messages held by Google or Microsoft.

You may separately revoke Pulse through your Google or Microsoft account security settings. See the Data Deletion page for step-by-step instructions. Because the current App has no Pulse server account, there is no additional server-side mailbox copy to request from the developer.

11

Security

Pulse uses OAuth so you do not give the App your Google or Microsoft password. Tokens are stored in the iOS Keychain, provider communication uses HTTPS, and mailbox analysis stays on the device. No software or storage method can be guaranteed completely secure. If you believe a security issue exists, use the support link below without posting secrets or private mailbox content publicly.

12

Children’s privacy

Pulse is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has used Pulse in a way that raises a privacy concern, contact support.

13

Your privacy choices

Depending on where you live, you may have privacy rights in addition to the controls described here. Since connected mailbox data stays on your device, the fastest way to access, correct, or delete it is through Pulse and your device. For questions about these rights, contact support and do not include sensitive information in a public issue.

14

Changes to this policy

We may update this policy as Pulse changes. The effective date will be revised when an update is published. If a future version adds a backend, new data use, or materially different sharing, the policy and in-app disclosure will be updated before that use begins.

15

Contact

Pulse is provided by JalenKidd. For support, privacy questions, or security reports, email jalenjkidd@gmail.com or visit the Pulse support page on GitHub. Do not include passwords, tokens, authentication codes, or private email content in a public issue.

Pulse

A simpler way to understand the security signals in the inboxes you choose to connect.

ExploreHomeFeaturesHow It Works
LegalPrivacy PolicyTerms of ServiceData DeletionSupportEmail JalenKidd
© 2026 Pulse · Developer: JalenKiddPulse is an independent application and is not affiliated with Google or Microsoft.