MeowPush Privacy Policy
Effective date: August 26, 2026
Last updated: August 26, 2026
The provider of MeowPush (referred to as “we,” “us,” or “our”) respects and protects your privacy. This Policy applies to the MeowPush website, account services, client applications, application programming interfaces (APIs), and cross-platform notification delivery services offered worldwide (collectively, the “MeowPush Services”). It explains how we process personal data, the rights available to you, and how third-party delivery chains affect the privacy of push notifications.
“Personal data” includes personal information or data that identifies an individual under applicable law. If this Policy conflicts with privacy rights that cannot be waived in your place of residence, the mandatory law controls. Additional notices or data processing agreements may apply to particular features, regions, or business customers; they supplement this Policy only to the extent expressly stated.
1. Scope and Our Role
For account data, device management, service security, customer support, and optional website analytics, we generally determine the purposes and means of processing and act as a Controller or Business under applicable law.
For push content submitted by a business or organizational customer through a Push Key or API, where that customer determines the recipients and purpose, we perform only the validation, transformation, routing, and forwarding necessary to follow the customer’s instructions. Depending on the parties’ actual decision-making authority, applicable law, and any data processing agreement, we may act as a Processor or Service Provider. When an individual user submits push content for their own purposes, we process it as necessary to perform our service contract with that user; the specific legal role still depends on the actual processing activity and applicable law. Users acting for others must ensure that they have a lawful basis and fulfill any applicable notice, consent, and rights-response obligations.
2. Personal Data We Process
Depending on the features you use, we may process the following categories of data:
- Account and identity data: email address or phone number, password hash, verification codes and status, nickname, account identifiers and status, session-token hashes, and registration, login, and update times. We do not store plaintext passwords or plaintext session tokens on the server.
- Device and push credentials: device name, installation and public identifiers, platform and push channel, device type, operating system and version, device model, app identifier, push environment, device push token or a compatible push-gateway endpoint configured by the receiving client, platform-specific attributes, last-active time, and Device Push Keys or Group Push Keys. A Push Key is an access credential that can initiate push delivery directly and is generally retained until you rotate it or delete the corresponding device or device group.
- Non-content delivery metadata: notification identifiers, target devices, routing channels, submission and delivery times, status, error category, retry information, collapse or grouping identifiers, and data necessary to synchronize read or withdrawal status. This data does not include notification titles, bodies, or custom content.
- Local client data: a client may store notification history, original payloads, custom data, and action state on your device. After visible history is deleted, the client may retain a minimal deletion marker to prevent the same system notification from being collected again. Whether message history is included in device backups depends on your Apple, HarmonyOS, or other system settings. Account tokens and Push Keys use system-provided secure storage and, according to current client capabilities, are configured not to synchronize across devices.
- Logs, security, and anti-abuse data: IP address, request time, API path, response status, request or diagnostic identifiers, minimized technical account and device identifiers, error information, security events, and service-operating metrics. We may combine account, device, network, and usage-frequency signals to identify attacks, bulk account registration, quota evasion, or other abuse, but we do not analyze push content for this purpose.
- Website usage and support data: when Google Analytics is configured on the website, it may process the page title, full page address, access path, query parameters, and browser or device data used by Google to provide analytics. When you contact us, we process the contact details, issue description, and correspondence you choose to provide.
- Approximate regional determination: some clients may request
api.country.is, which derives a country or region code from the requesting IP address to choose whether phone or email sign-in is shown by default. The client briefly caches the sign-in-method choice in memory and does not store the IP address, country code, or complete response.
3. Privacy Boundary for Push Content
“Push content” includes the title, subtitle, body, custom data, image or destination URL, sound, badge, icon, and platform-native extension fields that you submit.
We do not log, store, or analyze your push content. MeowPush validates, transforms, routes, and forwards push content transiently and only for the time needed to complete an individual delivery. We do not write it to business databases, logs, analytics systems, search indexes, or user profiles, and we do not use it for advertising, model training, or product-behavior analysis. After delivery completes, we do not retain a server-side copy of the push content. Non-content delivery metadata may be retained separately as described in this Policy.
If you voluntarily submit push content or a screenshot during a customer-support conversation, that copy is processed as support data you provided, not as content recorded from the push-delivery path. Notification history stored by a client on the receiving device is controlled by you and the device system and is not server-side retention of push content.
After push content leaves MeowPush, it must travel through the internet and the relevant delivery chain. Privacy during transmission, temporary handling, and display therefore also depends on the technical architecture, terms, and privacy practices of your network operator, cloud infrastructure providers, upstream system push platforms, and any compatible or self-hosted push gateway configured by you or the recipient. Network operators generally process connection and transmission metadata; the use of encrypted transport does not by itself mean that they can read notification plaintext. We remain responsible under applicable law for processors that we select and instruct, but we cannot control upstream platforms, networks, or gateways that you select or that operate independently. You should carefully assess whether notifications contain sensitive or regulated data and use encryption, data minimization, or other safeguards appropriate to your business risk.
4. Purposes and Legal Bases
Where applicable law requires us to identify a legal basis, we process data on the following grounds:
- Performance of a contract or steps before entering a contract: creating accounts, verifying identity, registering and managing devices, maintaining Push Keys, executing push requests, synchronizing necessary state, and providing customer support;
- Our legitimate interests: protecting the service and users, preventing fraud, attacks, and account abuse, troubleshooting, maintaining reliability, and improving the service through aggregated non-content metrics. Where applicable, we balance these interests against your rights;
- Your consent: enabling optional analytics, non-essential technologies, or other clearly described features when consent is required by law. You may withdraw consent without affecting the lawfulness of processing before withdrawal; and
- Compliance with legal obligations and protection of legal rights: responding to valid legal process, meeting regulatory requirements, handling disputes, and protecting the rights and safety of users, the public, us, or third parties.
5. Data Sharing, Processors, and Third-Party Services
We disclose data only to the extent necessary to provide the service, protect security, comply with legal obligations, or complete a request you expressly make:
- Upstream system push platforms: depending on the receiving device, we send the device push token, push content, and necessary delivery parameters to Apple Push Notification service (APNs), Google Firebase Cloud Messaging (FCM), Huawei Push Kit (HMS), Microsoft Windows Push Notification Services (WNS), or another compatible or self-hosted push gateway configured by the receiving client;
- Cloud infrastructure and communications processors: providers may supply necessary hosting, networking, storage, monitoring, email, or SMS services subject to contractual, confidentiality, security, and purpose limitations;
- External media services: when a notification contains a remote image or link, the receiving device may connect directly to the server you specified. That server receives ordinary network-request data, including an IP address; and
- Legal and corporate matters: we may disclose necessary data where required by law, to protect legal rights, or in connection with a merger, financing, restructuring, or asset transfer after applying appropriate safeguards.
We do not sell personal data or share it for cross-context behavioral advertising or targeted advertising. We do not permit processors to use entrusted data for their own advertising or for purposes unrelated to the agreed service.
6. International Data Transfers
MeowPush is offered globally, and data may be processed outside your country or region. Upstream system push platforms, cloud infrastructure, website analytics, or a push gateway you configure may also operate in multiple jurisdictions.
Specific cross-border arrangements depend on actual deployment, processors, and delivery platforms. We assess and implement transfer mechanisms required by applicable law. Available mechanisms may include adequacy decisions, Standard Contractual Clauses, the United Kingdom International Data Transfer Addendum or Agreement, and other legally recognized safeguards. Where the law requires separate notice or consent, we will complete the applicable process. This Policy does not state that one mechanism applies to every data flow and does not promise that all data is stored in a particular country or region.
7. Retention and Security
We retain personal data for the period necessary to fulfill the relevant purpose. Account data is generally retained until the account relationship ends and necessary cleanup is complete. Device and Push Key data is generally retained until you delete the device or device group or rotate the key. Retention periods for non-content delivery metadata, logs, and security records are determined by state synchronization, troubleshooting, anti-abuse, dispute handling, and legal requirements. Data in backups may remain for a limited cycle, during which it is used only for recovery, security, or legal obligations. Push content is not server-retained data.
We use reasonable measures such as transport protection, access controls, secure credential storage, least privilege, log minimization, monitoring and auditing, and backups. Internet and software systems cannot guarantee absolute security. If a data incident legally requires notification, we will take remedial measures and provide applicable notices to affected individuals and regulators.
8. Your Privacy Rights and Regional Supplements
Depending on your region, you may have the right to access or learn about processing, obtain a copy, correct or delete data, restrict or object to processing, withdraw consent, request data portability, and complain to a regulator. Some rights are subject to identity verification, statutory exceptions, and technical feasibility.
- European Economic Area, United Kingdom, and Switzerland: you may request access, correction, deletion, restriction, and portability; object to processing based on legitimate interests; withdraw consent; and complain to your local data-protection authority. We do not make decisions that have legal or similarly significant effects on you solely through automated processing.
- California and other U.S. states with applicable privacy laws: you may have rights to know, access, correct, delete, or obtain a portable copy, and the right not to be discriminated against for exercising privacy rights. We do not sell personal data or share it for cross-context behavioral advertising. If our practices change, we will update the notice in advance and provide any applicable opt-out mechanism. Where processing legally constitutes the use of sensitive personal data, you may also have the right to limit its use or disclosure.
- Other countries or regions: we respond to applicable requests for inquiry, access, correction, deletion, objection, complaint, or other statutory rights under the law where you live.
You can manage devices, rotate Push Keys, and delete devices or visible notification history in the client. Account requests or other requests that cannot be completed directly can be submitted through the channel listed under “Contact Us.” We may verify your identity and may require an authorized agent to provide valid authorization. We respond within the period required by applicable law; if the law permits us to deny a request, we will explain the reason.
9. Children and Minors
MeowPush is not designed specifically for children. We do not knowingly collect children’s personal data in violation of applicable law. If a parent or guardian believes that a child provided personal data without appropriate authorization, contact us at ••••••••. After verification, we will take deletion or other necessary action as required by law.
10. Updates to This Policy
We may update this Policy when the service, processing activities, or applicable law changes. For changes that materially affect your rights, we will provide prominent notice through the website, client, or another appropriate channel and obtain consent again where required by law. The “Last updated” date at the top reflects the most recent revision.
11. Contact Us
For questions, comments, or complaints about this Policy, personal-data processing, or rights requests, email ••••••••. Do not send passwords, verification codes, Push Keys, platform tokens, complete push content, or other unnecessary sensitive data by email. If a request requires identity verification, we will separately explain what information is needed and an appropriate way to submit it.