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
- Your email address, used to sign you in with a one-time code and to contact you about your account.
- Your workspace name, the apps you add (name, store, bundle ID or Android package name, optional Apple ID) and your forwarding URLs.
- Integration settings you enter, such as Slack or Discord webhook URLs, Telegram bot tokens, Pushover keys, PostHog API keys and webhook signing secrets. Only owners and admins of your workspace can read them.
- If you choose to save an Apple connection: your App Store Connect team or In-App Purchase signing key, Key ID, Issuer ID and connection name. Private keys are encrypted in Supabase Vault and cannot be read back through the browser. Workspace owners and admins can replace or delete saved connections. We use them for the Apple setup and test API calls you request. You can also use an In-App Purchase key for a one-time test without saving it.
- If you use the shared iPhone app: its delivery capability, app version and alert preferences in your backend, plus the relay routing data described below, so we can send you notifications. Legacy/private direct clients may store a device push token in their backend instead.
- If you connect Google Play: the service-account JSON key, project identity, topic, subscription, audience and push account. The key is encrypted in Vault and cannot be downloaded from the dashboard. Workspace owners and admins can replace it or disconnect the app.
- If you subscribe to Pro: your Stripe customer and subscription IDs and the subscription status. Card details are handled by Stripe and never reach us.
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
| Purpose | Lawful basis (UK GDPR) |
|---|---|
| Running your account and the service: sign-in, apps, the dashboard, alerts, forwarding and the iPhone app | Contract |
| Billing Pro subscriptions | Contract, and legal obligation for tax and accounting records |
| Security: request logs, abuse prevention, debugging | Legitimate interests (keeping Salebell and your data safe) |
| Service emails such as sign-in codes and important account notices | Contract |
Who processes it for us
| Processor | What for | Where |
|---|---|---|
| Supabase | Database, authentication, sign-in emails, encrypted store credentials in Vault and notification receiver functions | United Kingdom (London, eu-west-2) |
| Vercel | Hosting this website and routing requests to Supabase | United States and global edge network |
| Stripe | Payments, invoices and subscription management | United States |
| Apple | Delivering iPhone push notifications (APNs), and requested app discovery, notification URL setup and test notification API calls | United States |
| Google Play purchase lookup and the Google Cloud Pub/Sub setup and notification delivery you configure | Your 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
- Account, app, integration and event data: while your account exists. On the Free plan, history older than 30 days is hidden from the dashboard but not deleted, so it returns if you upgrade.
- Saved Apple keys: until you delete the saved connection or its workspace. Copies in backups expire on our providers' normal backup schedule. Deleting a connection from Salebell does not revoke the key in Apple.
- When you delete your account from Account settings, we delete your user and every workspace you solely own, including its apps, events, integrations, saved Apple and Google keys and devices, and cancel any Pro subscription. Copies in our providers' backups expire on their normal backup schedule.
- Saved Google keys: until you disconnect or delete the app or workspace. Backup copies follow the normal backup schedule. Disconnecting does not revoke the Google key or delete topics, subscriptions or IAM grants in your project.
- Billing records: as long as UK tax and accounting law requires (currently six years).
- Request logs: kept by our hosting providers for a short period for security and debugging.
Your rights
Under UK data protection law you have the right to:
- access the personal data we hold about you and get a copy of it;
- have inaccurate data corrected;
- have your data erased (you can also delete your account yourself at any time);
- restrict or object to processing, including processing based on our legitimate interests;
- receive data you gave us in a portable format (Pro workspaces can also export events as CSV).
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.