Other: Published Ordered Knowledge Base: : | Pushover Support Published Ordered Knowledge Base: Other Helprace RSS https://support.pushover.net/s1-pushover/knowledgebase/top/c9-other?format=rss How to delete/cancel your Pushover account Before proceeding, please note that for most users, Pushover has no recurring subscription fee.  To use it after the free 30-day trial, a one-time in-app purchase is all that is needed to continue receiving notifications for life.

Also note that we do not automatically bill you after your trial.  Prior to your 30-day trial expiring, you will receive a Pushover notification that your trial is about to end, with instructions on how to make an in-app purchase.  After the 30-day trial, if you do not make an in-app purchase for a license, you will no longer receive new Pushover notifications,[_cuted_]

]]> Wed, 14 Jun 2023 03:21:10 +0000 https://support.pushover.net/i73-how-to-delete-cancel-your-pushover-account https://support.pushover.net/i73-how-to-delete-cancel-your-pushover-account Pushover Support Pushover Support Before proceeding, please note that for most users, Pushover has no recurring subscription fee.  To use it after the free 30-day trial, a one-time in-app purchase is all that is needed to continue receiving notifications for life.

Also note that we do not automatically bill you after your trial.  Prior to your 30-day trial expiring, you will receive a Pushover notification that your trial is about to end, with instructions on how to make an in-app purchase.  After the 30-day trial, if you do not make an in-app purchase for a license, you will no longer receive new Pushover notifications, though you will still be able to view the messages you have already received.

Deleting Your Account

To completely delete your Pushover account, visit your Dashboard while logged into your account, then click the Settings menu, then Delete Account and your account will be automatically deactivated and scheduled for deletion.  For security purposes, we will not process account deletion requests received by e-mail.

For fraud and security purposes, we do not immediately delete accounts, but instead deactivate them and mark them for deletion.  After 30 days, we permanently delete all deactivated user accounts including any undelivered messages, API tokens, and other user data.  If you login before this 30-day grace period, your account will be undeleted and restored to its previous state, though you will need to re-register your devices to reactivate them.

]]> Who runs Pushover? Pushover is a service of Pushover, LLC (formerly Superblock, LLC), a private, independently-financed software development company based out of Chicago, Illinois.

We have been developing and supporting Pushover since March 2012 when we first released our apps to the App Store and Google Play (then called Android Market). We introduced Pushover for Desktop in April 2014.

]]> Sat, 27 Aug 2022 19:40:48 +0000 https://support.pushover.net/i45-who-runs-pushover https://support.pushover.net/i45-who-runs-pushover Pushover Support Pushover Support Pushover is a service of Pushover, LLC (formerly Superblock, LLC), a private, independently-financed software development company based out of Chicago, Illinois.

We have been developing and supporting Pushover since March 2012 when we first released our apps to the App Store and Google Play (then called Android Market). We introduced Pushover for Desktop in April 2014.

]]> Reporting a security problem or vulnerability Please see our security page for vulnerability disclosure and other information.

]]> Wed, 14 Jun 2023 03:22:23 +0000 https://support.pushover.net/i50-reporting-a-security-problem-or-vulnerability https://support.pushover.net/i50-reporting-a-security-problem-or-vulnerability Pushover Support Pushover Support Please see our security page for vulnerability disclosure and other information.

]]> Are messages/notifications encrypted? We use industry-standard TLS (HTTPS) encryption for all communication in Pushover, in every step of the process between your servers and our API servers, our servers and Apple's and Google's push notification servers, those push servers to your devices, and our apps back to our servers.

Our iOS and Android apps use AES-256 message encryption with a random, per-device key automatically generated for your device upon registration. Our servers encrypt your messages before sending them through Apple's and Google's notification servers, then our apps running on your devices decrypt the messages before showing them as notifications.

Our desktop/browser app uses TLS[_cuted_]

]]> Wed, 10 Sep 2025 22:07:14 +0000 https://support.pushover.net/i46-are-messages-notifications-encrypted https://support.pushover.net/i46-are-messages-notifications-encrypted Pushover Support Pushover Support We use industry-standard TLS (HTTPS) encryption for all communication in Pushover, in every step of the process between your servers and our API servers, our servers and Apple's and Google's push notification servers, those push servers to your devices, and our apps back to our servers.

Our iOS and Android apps use AES-256 message encryption with a random, per-device key automatically generated for your device upon registration. Our servers encrypt your messages before sending them through Apple's and Google's notification servers, then our apps running on your devices decrypt the messages before showing them as notifications.

Our desktop/browser app uses TLS encryption for all communication between your browser and our servers and messages are pushed directly from our servers to your browser when in direct mode.  When using cloud push notification mode, a small ping message is sent through Apple/Google servers which notifies your browser to securely connect to our API servers and fetch messages which then generate notifications.

Messages on our servers are stored in plain-text but are only stored long enough to send them out to your devices, which then check-in with our servers and trigger those messages to be deleted from our servers.

We store your messages on your devices in plain-text, but in a secure manner that prevents other applications on the device from reading them.

We do not currently support full end-to-end encryption where your server encrypts a message with your own key and sends it to our servers encrypted, which is then decrypted by our app on your device using the key that you stored in the app, which would additionally hide the message contents from our servers as well.

]]> Notification storage and delivery
  • A server, application, or plugin sends a message to our Messaging API over HTTPS (TLS), including its application (API) token, one or more user or group keys, and the message details such as the title, message, sound, attachment image, etc.
  • Our server encrypts the message with each recipient device's specific encryption key (if encryption is supported by the device) and stores the message in our database, then responds to the API client that the message was successfully received.
  • Our dispatch server communicates with the appropriate carrier push server (Google's, Apple's, or ours) over TLS and hands off the encrypted message.[_cuted_]
    • ]]>     Mon, 03 Jan 2022 23:00:32 +0000 https://support.pushover.net/i39-notification-storage-and-delivery https://support.pushover.net/i39-notification-storage-and-delivery Pushover Support Pushover Support
  • A server, application, or plugin sends a message to our Messaging API over HTTPS (TLS), including its application (API) token, one or more user or group keys, and the message details such as the title, message, sound, attachment image, etc.
  • Our server encrypts the message with each recipient device's specific encryption key (if encryption is supported by the device) and stores the message in our database, then responds to the API client that the message was successfully received.
  • Our dispatch server communicates with the appropriate carrier push server (Google's, Apple's, or ours) over TLS and hands off the encrypted message. If successful, the message is marked as delivered in our database.
  • Google's or Apple's push servers deliver the message to the end-user device over their proprietary, persistent TLS connections. Our Desktop push server delivers notifications to web browsers over a WebSocket connection.
    • On Android phones, the notification is received by Google's Firebase service which then forwards it to the Pushover application, launching it in the background if needed. The message is decrypted by the Pushover app and stored unencrypted in its local database, and a system notification is generated.
    • On iOS, the Pushover application's notification extension is launched which decrypts the message, stores it in its local database, and generates a system notification.
    • On Desktop browser devices, the a signal is sent over its persistent WebSocket connection notifying it of a new message pending, which causes it to do a sync with our server and store any new messages in its local database, and a local browser notification is generated.
    • On macOS desktops, the notification is received by macOS's push notification service and a notification is generated. No sync is performed until Safari is opened by clicking on the notification or visiting our Desktop client site.
  • If an image attachment was included with the original message sent to our API, the Pushover app downloads the image attachment from our servers and stores it locally before generating a local notification.  Once the image attachment has been downloaded, the client notifies our API and once all devices that the image was delivered to have reported in, the attachment is marked for deletion on our servers.
  • When the Pushover device client is opened and has not synchronized recently (or a manual sync is requested), the device client communicates with the Pushover servers over TLS and downloads any new messages that were not received by push notification, usually due to transient network issues.
  • Finally, the Pushover device client notifies the Pushover servers of the highest message ID that it has in its database that has been reliably received. The Pushover servers delete all messages up to and including that ID. At this point, the message exists only on the user's devices that it was delivered to.  Image attachments marked for deletion are permanently deleted from our servers so the images are only existing on the devices they have been delivered to.

    • Messages delivered to devices but not acknowledged will be automatically deleted from our servers after 21 days, and image attachments after 3 days.

    ]]>         How are my account password and other private information stored? Pushover uses bcrypt for one-way password hashing. For device identifiers, we create a one-way hash of a stable device identifier available from the operating system together with a randomly generated identifier specific to each Pushover account. We do not use "UDIDs", advertising IDs, or other cross-app personal identifiers.

    Messages are encrypted in transit through carrier notification servers as detailed in this article.

    Access to our servers and databases is tightly controlled, logged, and monitored, and are only accessible through a private network.

    All of Pushover's servers are located within the United States at datacenters operated by US companies.

    Encrypted backups[_cuted_]

    ]]>     Thu, 19 Dec 2024 17:27:16 +0000 https://support.pushover.net/i48-how-are-my-account-password-and-other-private-information-stored https://support.pushover.net/i48-how-are-my-account-password-and-other-private-information-stored Pushover Support Pushover Support Pushover uses bcrypt for one-way password hashing. For device identifiers, we create a one-way hash of a stable device identifier available from the operating system together with a randomly generated identifier specific to each Pushover account. We do not use "UDIDs", advertising IDs, or other cross-app personal identifiers.

    Messages are encrypted in transit through carrier notification servers as detailed in this article.

    Access to our servers and databases is tightly controlled, logged, and monitored, and are only accessible through a private network.

    All of Pushover's servers are located within the United States at datacenters operated by US companies.

    Encrypted backups of our entire systems with separate database snapshots are done off-site every day. For increased security and privacy, we do not backup the contents of the temporary message queue database table (but we do backup all of the other tables, of course). We would much rather lose a few transient notifications that can be re-sent later than to accidentally lose control of a backup of those messages should one of them contain a password or other sensitive information.

    Credit card information (for Pushover for Teams subscriptions, purchasing additional message capacity, and purchasing licenses) is handled by our PCI-compliant payment processor and is never transmitted through or stored on our servers.  In-app license purchases through our Android and iOS apps are handled directly by Google and Apple, respectively, and we cannot access billing information about these purchases.

    ]]>         Pushover Logos and Usage We've put together some various sizes of our logo to show off your Pushover integration. Please download and host these logos on your own websites and documentation rather than hotlinking directly to these files on our site.

    For libraries that encompass our API in a particular programming language, you are permitted to use the Pushover name in your project name (e.g., "php-pushover") as long as you make it clear in your documentation and source code that the library is not written or supported by Pushover. All references to our product or service should be written as Pushover with a capital[_cuted_]

    ]]>     Tue, 28 May 2024 18:07:14 +0000 https://support.pushover.net/i63-pushover-logos-and-usage https://support.pushover.net/i63-pushover-logos-and-usage Pushover Support Pushover Support

    We've put together some various sizes of our logo to show off your Pushover integration. Please download and host these logos on your own websites and documentation rather than hotlinking directly to these files on our site.


    You are permitted to use the Pushover logo in the following ways:

    • Use the Pushover logo to link to the Pushover website (https://pushover.net)
    • Use the Pushover logo to advertise that your product, service, or project has built-in Pushover integration
    • Use the Pushover logo in a blog post or news article about Pushover

    You are not permitted to use the Pushover logo in these ways:

    • Use the Pushover logo for your application's icon
    • Create a modified version of the Pushover logo
    • Integrate the Pushover logo into your logo
    • Use or sell any Pushover artwork without permission
    • Change the colors, scale without retaining aspect ratio, or add your own text/images

    For libraries that encompass our API in a particular programming language, you are permitted to use the Pushover name in your project name (e.g., "php-pushover") as long as you make it clear in your documentation and source code that the library is not written or supported by Pushover. All references to our product or service should be written as Pushover with a capital "P", all one word (not "Push over" or "PushOver").

    For any other services or applications, you are not permitted to use the Pushover name in your software's name.

    If you have any questions regarding the use of the Pushover logo or name, please contact us before use to avoid any complications.

    ]]>