Scope and responsibilities
This policy applies to the PushNotifications.org website, dashboard, API, SDK, opt-in widget, billing, support, AI features, and Web Push delivery service. PushNotifications.org is the service operator and is responsible for account administration, billing state, security, abuse prevention, and its own website operations.
For subscriber data and campaign content submitted by an account owner, that owner normally decides why and how the data is used and is responsible for its subscriber-facing notice, lawful basis, permission records, and campaign content. PushNotifications.org processes that data to provide the service and may process limited records independently where necessary for security, fraud prevention, suppression, legal compliance, and enforcement. A connected website must provide its own accurate privacy notice when requesting browser notification permission.
Information we process and where it comes from
- Account and authentication
- Google's stable account identifier, confirmed email address, display name, session and security events, plan, allowances, settings, and usage counters. These come from Google sign-in, the account owner, and use of the service. We do not create a separate site password.
- Websites and widget design
- Registered HTTPS origins, ownership-verification results, site keys, VAPID credentials, widget configuration, logo, colors, brand name, and public homepage content requested for design analysis. These come from the owner, the verified public website, and service configuration.
- Browser subscriptions and audience attributes
- Encrypted push endpoint, p256dh key and authentication secret; consent and subscription timestamps; current state; country, locale and timezone; device class; browser family and version; operating-system family and version; push service; engagement; delivery, click, failure, and opt-out events. These come from the browser, SDK, network-derived country signals, and account activity. A Web Push subscription does not require a subscriber email address or phone number.
- Campaigns and imports
- Campaign copy, destination, audience, schedule and results; provider name and export date; consent evidence; file name and hash; key fingerprints; risk and review results; browser revalidation; and suppression hashes. These come from the owner, import file, public checks, browsers, providers, and Trust & Safety review.
- Billing and support
- Stripe customer and subscription identifiers, plan, payment status and renewal period, plus communications supplied in support, privacy, security, or billing requests. Stripe, rather than PushNotifications.org, receives complete card details during hosted checkout.
- AI activity
- Prompts, supplied source material, generated drafts, model choice, feature usage, and stored proposals and source references where monitoring is enabled. Context can include registered-site information and aggregate audience, engagement, campaign, and usage statistics, but is designed to exclude subscriber endpoints and encryption secrets.
- Technical records
- IP address, request time, browser and device information, route, response, cookies, and security events needed to operate, diagnose, and protect the service.
Why we process information
- Authenticate accounts, provide requested features, manage subscriptions, and perform a contract with an account owner.
- Verify public HTTPS origins, isolate each site's credentials and audience, deliver approved campaigns, and report bounded results.
- Analyze a verified public website to create editable logo, color, wording, and layout suggestions when requested.
- Measure use, enforce delivery and AI allowances, troubleshoot failures, improve reliability, and support account owners.
- Protect subscribers and the service through fraud screening, import quarantine, browser revalidation, suppression, rate limits, and security logging.
- Operate the optional promotion-supported Free program and retain evidence of enrollment, revocation, authority, and promotional limits.
- Meet tax, accounting, legal, regulatory, dispute, and valid government-request obligations.
Depending on the context and applicable law, these activities rely on performance of a contract, compliance with a legal obligation, consent, or legitimate interests such as service security, fraud prevention, and reliable operation. Where consent is required, it may be withdrawn for future processing without affecting earlier lawful processing.
AI features and OpenRouter
Premium AI tools can prepare editable campaign drafts, calendars, translations, audience recommendations, send-time suggestions, quality reviews, experiments, analytics explanations, migration mappings, and website-monitoring proposals. They do not send or schedule a campaign without an explicit human action.
When an AI feature is used, the prompt, selected source material, and relevant account context are transmitted through OpenRouter to the selected model provider. Provider retention, training, and geographic processing practices vary. Account owners must review the OpenRouter privacy policy and the selected provider's terms, avoid unnecessary personal or confidential data, and verify output. A personal OpenRouter key is encrypted at rest. No subscriber endpoint, p256dh key, authentication secret, private VAPID key, or raw subscriber list should be placed in an AI prompt.
AI output can be incomplete or inaccurate. PushNotifications.org does not use AI output by itself to make a decision that produces legal or similarly significant effects for a subscriber.
Who receives information
- Google for account authentication and security. See the Google privacy policy.
- Stripe for hosted checkout, subscriptions, payment status, fraud prevention, and billing support. See the Stripe privacy policy.
- OpenRouter and selected model providers when an account owner chooses an AI feature.
- Browser push services to route an approved notification to the relevant subscription.
- Infrastructure, email, security, and monitoring providers under appropriate contractual and confidentiality controls.
- Authorities, advisers, or transaction participants where legally required, needed to protect rights or safety, or part of a legitimate corporate transaction with appropriate safeguards.
We do not sell subscriber lists, browser endpoints, or encryption keys. Sponsors in the promotion-supported Free program do not receive an account owner's subscriber list. If advertising technology that constitutes a sale or sharing under applicable law is enabled in the future, we will provide required notice and choice first.
International processing
Providers and model vendors may process information outside the account owner or subscriber's country. Where applicable, we use contractual or other recognized safeguards for restricted transfers and consider the information, destination, and provider controls. Account owners remain responsible for transfer requirements applying to content and subscriber data they direct us to process.
Retention and deletion
- Account, website, active subscription, campaign, and configuration records are generally kept while the account or relevant site is active and as needed to provide the service.
- A subscriber record is removed or made ineligible after an effective opt-out, site deletion, account closure, or permanent endpoint failure, subject to necessary suppression and security records.
- Migration files are processed for validation rather than retained as a file store. Quarantined credentials are encrypted and removed after activation or rejection. Hashes, attestations, decisions, and audit evidence may be retained to prevent repeat abuse, investigate fraud, and demonstrate review.
- Endpoint hashes and minimal suppression evidence may be retained as long as reasonably necessary to honor opt-outs, block re-import, and protect subscribers and providers.
- Ordinary AI prompts and outputs are not maintained as a subscriber-data archive. Monitoring proposals and necessary usage records may remain in the account; OpenRouter and model providers apply their own retention rules.
- Billing, dispute, tax, security, and legal records are kept for the period required by law or reasonably necessary to establish, exercise, or defend claims.
- Logs and backups are removed or overwritten through operational cycles unless preservation is required for an incident, dispute, or legal obligation.
Owners can delete sites and associated records through dashboard controls or request closure. Deletion from live systems may not immediately remove access-restricted backup copies, which remain until overwritten.
Cookies and advertising
Strictly necessary cookies and similar storage support sign-in, session continuity, security, CSRF protection, and preferences. Google and Stripe may set or receive data during authentication or hosted payment under their policies.
If Google AdSense or another advertising service is enabled, partners may use cookies, local storage, IP address, device information, and page activity to deliver, limit, personalize, or measure ads. Google's partner-sites disclosure explains its use. Where consent is required, optional advertising storage and personalized advertising will not be enabled before the appropriate choice. This disclosure does not state that advertising is currently active.
Your choices and privacy rights
Subscribers can revoke notification permission in browser or device settings and should use the connected site's unsubscribe or preference controls where available. Owners can manage sites, subscribers, campaigns, AI credentials, promotion enrollment, and paid subscriptions through dashboard controls.
Depending on location and law, a person may request access, correction, deletion, portability, restriction, or objection; withdraw consent; and complain to a supervisory authority. California residents may also have rights to know, correct, delete, opt out of sale or sharing, limit certain sensitive-information uses, and receive equal service. We do not discriminate for exercising an applicable right.
Subscribers should normally contact the connected website, which controls the relevant audience. Requests sent to us will be verified and, where appropriate, coordinated with that owner. Rights may be limited by exceptions for security, fraud prevention, legal claims, and records another person has no right to access.
Children
The account service is for adults and organizations able to enter a binding agreement, not children. Owners must not target children or process children's information without all permissions and safeguards required by law. Contact us if you believe a child created an account or was improperly targeted.
Security
Controls include HTTPS, access control, server-side secrets, encryption of sensitive records, exact-origin checks, separate site credentials, safe-destination validation, import quarantine, independent review, browser revalidation, suppression, delivery and AI allowances, and endpoint cleanup. The security page distinguishes implemented controls from current limitations. No internet service can guarantee absolute security.
Policy changes and contact
We may update this policy when the service, providers, or legal requirements change. We will change the updated date and highlight material changes through the service or another reasonable channel before they take effect when required.
PushNotifications.org is the service operator. Privacy questions and rights requests can be sent to [email protected]. Include the registered domain and enough context to locate the record, but never email API keys, payment details, push secrets, or private VAPID keys. Security reports belong at [email protected].