Skip to content
Salebell

Privacy policy

Last updated 16 October 2026

This policy explains what Salebell collects when you use the website, the dashboard and the iPhone app, why, and the rights you have. We collect only what we need to run the service. We don't sell data or use it for advertising.

Who we are

Salebell is operated by Salebell, company number 13431390, registered office Demsa Accounts, 565 Green Lanes, Haringey, London, England, N8 0RL, the controller of the personal data described here ("we"). For the purchase data your apps send us, we process it on your instructions.

Contact us about privacy at morfozz@proton.me.

What we collect

Your account

Notifications from Apple

When Apple sends an App Store Server Notification to your Salebell URL, we verify its signature and store the decoded payload: notification type, product ID, price and currency, storefront country, transaction IDs, dates, and the appAccountToken if your app sets one. We don't keep the raw signed token. Apple doesn't include your customers' names, email addresses or Apple Account details in these notifications, so we never receive them.

Notifications from Google Play

We verify authenticated Pub/Sub delivery, look up purchase state with Google Play, and retain the event type, date, product and order metadata and a purchase-token hash. Raw purchase and OAuth tokens are not retained in event history. Google revenue remains unknown in the preview. Automatic setup also sends the topic, receiver and access settings you request to your Google Cloud project.

Technical data

Our hosting providers keep standard request logs (such as IP address, time and URL) to operate and secure the service. We use only the cookies needed to keep you signed in. There are no analytics or advertising cookies. We count page views with Vercel Web Analytics, which uses no cookies and doesn't identify you or track you across sites.

Shared iPhone app and push relay

When you use a compatible shared Salebell app with an independent instance, your database, account and event history stay with that instance's operator. The app signs in directly to the backend you select. iPhone push depends on the Salebell-operated relay; dashboard access and other alert channels work independently. This source implementation does not establish that a distribution or live relay is available.

The relay receives the notification title and body for delivery. It stores the APNs device token, backend origin, user and route identifiers, and a route content key in private, access-restricted storage. Installation control secrets and delivery capabilities are stored as hashes; the content key itself is stored so the relay can encrypt messages. Its hosting providers process the relay requests and retain their operational logs and backups.

Route expiry or revocation stops future authorization; it does not itself erase the stored routing records or delivery identifiers. Ask the relay operator about record removal and backup retention, separately from deleting an account on your chosen backend.

Sale text is encrypted by the relay before delivery through Apple APNs. APNs receives a generic visible message plus encrypted sale content. This is not end-to-end encryption from your backend to your phone: the relay can see the title and body. The phone's notification extension decrypts only its active route. Unknown or obsolete routes retain generic content without the sale sound or badge; an Apple-accepted push cannot be recalled and late generic alerts remain possible.

The app keeps one active backend and user per installation. Signing out or switching requires central route revocation; a relay outage may delay that action until you retry. Automatic session loss clears the phone's active route and blocks a replacement until revocation succeeds. A customer backend stores only its users' delivery capabilities for this flow. Privately maintained direct-APNs apps use their own operator's Apple credentials and device registrations instead.

Why we use it, and our lawful basis

PurposeLawful basis (UK GDPR)
Running your account and the service: sign-in, apps, the dashboard, alerts, forwarding and the iPhone appContract
Billing Pro subscriptionsContract, and legal obligation for tax and accounting records
Security: request logs, abuse prevention, debuggingLegitimate interests (keeping Salebell and your data safe)
Service emails such as sign-in codes and important account noticesContract

Who processes it for us

ProcessorWhat forWhere
SupabaseDatabase, authentication, sign-in emails, encrypted store credentials in Vault and notification receiver functionsUnited Kingdom (London, eu-west-2)
VercelHosting this website and routing requests to SupabaseUnited States and global edge network
StripePayments, invoices and subscription managementUnited States
AppleDelivering iPhone push notifications (APNs), and requested app discovery, notification URL setup and test notification API callsUnited States
GoogleGoogle Play purchase lookup and the Google Cloud Pub/Sub setup and notification delivery you configureYour Google Cloud project settings and Google's infrastructure

The integrations and forwarding URLs you configure (for example Slack, Discord, Telegram, Pushover, PostHog or your own server) receive the event data you choose to send them, under their own terms. They are not our processors.

International transfers

Your workspace data is stored in the United Kingdom (Supabase, London). Vercel, Stripe and Apple may process personal data in the United States. Those transfers are protected by the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses in each provider's data processing terms.

How long we keep it

Your rights

Under UK data protection law you have the right to:

You can complain to the Information Commissioner's Office (ICO), the UK data protection regulator, at ico.org.uk. We'd appreciate the chance to sort out any concern first.

To exercise any of these rights, email morfozz@proton.me.

Children

Salebell is a tool for app developers and businesses. It isn't meant for children and we don't knowingly collect their data.

Changes

If we change this policy in a way that matters, we'll update the date above and tell signed-in users.