JustPush
FeaturesRecipesHow it worksSDKsPricingvs PushoverDocs
Get started
Back to JustPush
Privacy Policy

Privacy Policy

What we store, why we need it, who helps us run JustPush, how long we keep it, and how to have it deleted.

Last updated 5 October 2026

This policy covers JustPush: the iOS and Android apps, the API at api.justpush.io, JustPush Studio at studio.justpush.io, the JustPush MCP server for AI assistants, the email gateway (your @jpml.io address) and this website. It explains which personal data we process, why, who else handles it, and what you can do about it.

In plain English

This is everything we know about you, why we keep it, and how to make us delete it.

Who we are

JustPush is run by JustPush VOF in the Netherlands. We are the controller of the personal data described here. For anything about privacy, including requests to see or delete your data, email [email protected].

In plain English

JustPush VOF, a Dutch company, is responsible for your data. Write to [email protected].

What we collect

Your account

  • Email address. It's your login (with a one-time code, Sign in with Apple or Google sign-in) and how we reach you. With Google sign-in we keep only your email address. With Sign in with Apple we also keep Apple's identifier for your account; if you use Hide My Email, we only get Apple's relay address. We don't store your name.
  • Language of the app, so emails and the app use it.
  • Your API token and email-gateway address (e_…@jpml.io), which we generate for you.
  • Login records: one-time codes and session tokens, stored hashed, with when they expire and were last used.
  • Usage: how many messages you send per month and which features you've used (images, buttons, acknowledgements, the email gateway), to apply your plan's limits and to tailor onboarding emails.

Your devices

  • Device name. By default this is your phone's name, which often contains your own name (for example "Anna's iPhone").
  • Push token from Firebase Cloud Messaging, and an identifier for the app installation, so notifications reach the right device.
  • Notification settings: sounds per priority, quiet hours with your time zone, muted topics.
  • Delivery health: how often delivery to the device failed.

The app asks for permission to show notifications and nothing else: no location, contacts, camera or photos.

Messages and topics

  • Messages you send through the API, the SDKs, Studio, the MCP server or the email gateway: title, body, priority, sound, images and their captions, buttons and their links, expiry, and acknowledgement settings including the callback URL and parameters you set.
  • Delivery and acknowledgement records: which devices a message went to, whether it arrived, and when and on which device it was acknowledged.
  • Topics: title, avatar (uploaded by you or generated from the title's initials), invite codes, and each member's settings (muted, pinned, last seen).
  • The email gateway uses only the recipient address, the subject and the plain-text body of emails sent to your @jpml.io address. We don't store the sender, the HTML version or attachments.

Images are stored at public, unguessable links on our CDN, so anyone who has the link can open the image. Don't send images that must stay secret. If you send an image by URL, our servers download it from that address.

Studio integrations

  • Each integration's name, description, JavaScript code, the token in its URL, and its webhook verification secret (stored encrypted).
  • The webhook requests it receives: method, headers, query string and body, plus what your code returned and anything it wrote to the console. Request headers usually include the IP address of the service that sent the webhook. Your code runs in an isolated sandbox on our own servers.

AI assistants (MCP)

  • When you connect an AI assistant such as Claude or ChatGPT, we store the name and redirect addresses the assistant registers, your consent (which assistant, when, which access) and its access tokens (hashed).
  • An audit log of every tool call: which tool, the arguments (for example a message's title and body, or integration code and test payloads) and the result.
  • The assistant's provider (for example Anthropic or OpenAI) receives what the tools return, such as your account email, gateway address, topics and integrations, and handles it under its own privacy policy.

Payments

  • Purchases through the App Store or Google Play are handled by Apple or Google. We receive the subscription status and transaction details, never your card details. We give Apple a random identifier for your account so purchases can be matched to it.
  • Payments outside the app stores go through Mollie, which receives your email address and handles the payment.
  • For VAT we keep your country, whether you buy as a business, your VAT number (checked with the EU's VIES service), the amounts, any promo code and the payment reference.

Feedback and support

  • Feedback you send from the app: your rating, your text and the device it came from.
  • Emails you send us, kept in our mailbox.

Diagnostics, logs and this website

  • Server logs and security: our servers and Cloudflare, which sits in front of all JustPush addresses, process IP addresses, browser or app details and request details to deliver the service, limit abuse and fix problems.
  • Processing traces: a record of how each message and webhook was processed, including its content, so we can debug failed deliveries.
  • Crash reports from the app go to Bugsnag: device model, operating system and app version, the screens you visited and the steps before the crash.
  • This website uses Google Analytics, which sets cookies and tells us which pages are visited, from what kind of device and roughly where (based on the IP address). Studio loads its fonts from Google Fonts and its code editor from jsDelivr, which see your IP address when they serve those files.
In plain English

Your email, your devices, what you send through JustPush, your Studio code and webhooks, your AI-assistant activity, payment and VAT details, and the logs needed to run and fix the service.

Data about other people

Your messages and webhooks can contain other people's personal data. A webhook from a web shop, for example, can include a customer's name and address. For that data you are the controller, and we process it on your behalf only to deliver your notifications and run your integrations, under this policy's security and retention rules. Make sure you're allowed to send it to JustPush. If you need a data processing agreement, email [email protected].

In plain English

If your notifications contain your customers' data, that's your data to be careful with; we only use it to deliver your notifications.

Why we use it

PurposeLegal basis (GDPR)
Running your account, logging you in, delivering messages, running integrations and the MCP serverPerforming our contract with you
Payments, invoices and VATPerforming our contract; our legal obligation to keep tax records
Security, abuse prevention, rate limits, the MCP audit log, debugging and crash reportsOur legitimate interest in a secure, working service
Onboarding emails and the tips we push to the app after you sign upOur legitimate interest in helping you get started; you can unsubscribe at any time
Website analyticsOur legitimate interest in knowing which pages are useful

We don't sell your data, we don't use it for advertising, and we don't track you across other companies' apps or websites.

In plain English

We use your data to run JustPush, get paid, keep it secure and help you get started. Never for ads, never sold.

Who we share it with

We share personal data only with the providers below, who process it for us under their data processing terms; with the destinations you choose (callback and image URLs, the AI assistant you connect, the members of topics you share); and with authorities when the law requires it.

ProviderWhat forWhat they receive
CloudflareNetwork protection and routing for all JustPush addressesAll traffic, including IP addresses and request content
DigitalOceanStorage and CDN for message images and topic avatars (Frankfurt), and the Studio code runnerImages, avatars; your integration code and the webhook requests it runs on
Google Firebase Cloud MessagingDelivering notifications to Android and iOS (on iOS via Apple Push Notification service)Push token, title, body, image link, sound and priority
AppleSign in with Apple, App Store purchases, iOS notification deliverySign-in details, purchase details, notification contents
GoogleGoogle sign-in; Google Analytics on this websiteYour email address at sign-in; website visit data
PusherLive updates in the app and StudioMessage title and body; webhook requests and console output while Studio shows them live
Twilio SendGridSending login codes and account emails; receiving email for the email gatewayYour email address; the emails' contents
MailerLiteOnboarding emailsEmail address, language, number of topics and messages, which features you've used
MolliePayments outside the app storesEmail address, payment details
European Commission (VIES)Checking VAT numbersYour VAT number
BugsnagCrash reports from the appDevice, OS and app version; screens and steps before a crash
Google WorkspaceOur emailEmails you send us
Google Fonts, jsDelivrFonts and the code editor in StudioIP address of Studio visitors

Some of these providers are based in the United States or process data there. For those transfers we rely on the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses.

In plain English

A handful of well-known providers help us deliver notifications, send email, take payments and keep the service up. They only get what they need for that job.

How long we keep it

DataHow long
Account, devices, topics and settingsUntil you delete your account
Message contentUntil the message expires or you delete it, and never longer than 18 months
The small copy of an image used in the notification itself1 month
Studio codeThe last 10 versions of each integration, until you delete the integration
Webhook requestsThe last 15 per integration
Processing traces and delivery records30 days
Server logs14 days
MCP audit log12 months
Login codesValid for 1 hour, deleted after 30 days
Payment and VAT records7 years, as Dutch tax law requires
FeedbackUntil you delete your account
Website analyticsAt most 14 months
In plain English

Messages go when they expire or after 18 months at most, logs within weeks, your account when you delete it. Only tax records stay for 7 years, because the law says so.

Deleting your account

  • In the app: open Settings and tap Delete account.
  • By email: write to [email protected] from the address on your account.

We delete your account and everything linked to it (messages, images, devices, topics you own, integrations, webhook requests, traces, audit entries and your MailerLite subscription) within 30 days. Payment and VAT records are the exception: Dutch tax law requires us to keep them for 7 years. Deleting the app doesn't delete your account, and an App Store or Google Play subscription has to be cancelled there.

You can also delete smaller things yourself: a device or a message in the app, an integration in Studio. To disconnect an AI assistant, remove JustPush in the assistant's settings; its access token stops working within 60 minutes, or email us and we'll revoke it straight away.

In plain English

Tap Delete account in the app's settings, or email us. Everything is gone within 30 days, except tax records.

Your rights

Under the GDPR you can ask to see the personal data we hold about you and get a copy, have it corrected or deleted, restrict or object to how we use it, and receive it in a portable format. Email [email protected]; we answer within one month. To protect your account we may ask you to confirm the request from your account's email address.

If you think we're handling your data wrongly, please tell us first. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens, or to the authority where you live.

In plain English

You can always ask what we have, get a copy, fix it or have it deleted.

Emails we send

  • Always: login codes, and emails about your subscription (renewed, cancelled or expired).
  • After you sign up: a short series of onboarding emails, sent through MailerLite, with matching tips pushed to the app. Every onboarding email has an unsubscribe link.

We never email the contents of your notifications.

In plain English

Login codes and billing notices always; a few getting-started emails you can unsubscribe from.

Security

Data travels encrypted (HTTPS). One-time codes and session tokens are stored hashed and webhook secrets are stored encrypted. Studio code runs in an isolated sandbox. Only the people who run JustPush can reach the admin tools. Treat your API token, topic tokens and integration URLs like passwords: anyone who has them can send notifications to you. If a data breach puts your data at risk, we'll tell you and the Autoriteit Persoonsgegevens as the law requires.

In plain English

We protect your data with encryption and limited access. Keep your tokens to yourself.

Children

JustPush is not meant for children under 13. If you think a child has given us personal data, email us and we'll delete it.

In plain English

JustPush isn't for children under 13.

Changes to this policy

When we change this policy we update the date at the top. If a change affects how we use your data in a significant way, we'll tell you by email or in the app before it takes effect.

In plain English

If anything important changes, you'll hear it from us first.

Contact

JustPush VOF, the Netherlands. Privacy: [email protected]. Help with the app: [email protected].

JustPush

Push notifications for backend developers, indie hackers, and anyone tired of writing the same alert glue code twice.

 Status

Product

  • Features
  • How it works
  • Playground
  • Webhook Studio
  • Studio recipes
  • Pricing
  • vs Pushover

Developers

  • Documentation
  • API reference
  • SDKs
  • Open API spec

Company

  • About
  • Blog
  • Contact
  • Privacy
  • Terms
  • Delete account
© 2026 JustPush VOF — Built by devs, for devs.api.justpush.io · v1.4.2