தனியுரிமைக் கொள்கை
PushWard is run by MAWIK Maciej Kędziora, a sole proprietorship registered in Poland ("we", "us"), the controller of the personal data described here. This policy explains what we collect, what we don't, and what you can do about it.
What we collect
When you sign in with Apple, on iOS and Mac or through Apple's sign-in page in the
Android app, we receive only an opaque identifier -- no email, no name. The Android app
also lets you sign in with Google, and the web console at console.pushward.app with Google or with a one-time code sent to your email
address. If you choose one of those, we
store the email address you use, and for Google also Google's identifier for your account
and its email address. When Google vouches for that address (a Gmail address, or one on
your organization's Google Workspace domain), it also becomes an email sign-in method of
your account. If signing in with Google creates your account, the name on your Google
account becomes your display name until you change it. When you sign in with Apple or add
an Apple ID to your account in the Android app, the app also sends us a Google Play
Integrity token, which we pass to Google to confirm that the request comes from an
unmodified PushWard app from Google Play, on an Android device that passes Google's
integrity checks. The token and Google's answer describe the app and the device, not your
account or its content, and are good for that one sign-in only. The iOS and Android apps send us
your device push tokens (Apple push tokens on iOS, a Firebase Cloud Messaging
registration token on Android) so we can deliver Live Activities and notifications, a
random identifier for each device, basic device info (OS version, app version, model,
locale, time zone, permission state) for diagnostics, and the activities and
notifications you create through the API.
If you use the optional email channel, we also store the recipient email addresses you register (each confirmed by the recipient through a double opt-in link), the subject lines and delivery status of the emails you send through us, and -- transiently, only while we hand it to our email provider for delivery -- the message body. That confirmation email tells each recipient who added them, and every message lets them unsubscribe at any time.
Purchases. Paid plans for your own account are bought in the app: in the App Store on iOS and Mac, and through Google Play on Android. Apple or Google takes the payment, and card details never reach us. On Android, the purchase carries an opaque identifier of your PushWard account (not your email or name), the app sends us Google Play's purchase token, and we check it with Google's Play Developer API. Google also notifies us when a purchase renews, ends or is refunded. We store the product, Google's order number, the status and the expiry date with your account, so we can turn the plan on and off.
Organizations (PushWard Team)
If you join an organization, it can see your name in the app, your role, and for each of your devices: its name and model, the OS and PushWard app version, and whether notifications are allowed. It cannot see your location, your Apple ID, your Google account or your sign-in email address, or the Live Activities, notifications, widgets and keys of your personal account. You are shown this before you join, you choose which of your devices receive the organization's sends, and you can leave at any time. Each organization decides what it sends to its members and is responsible for having a reason to do so. Contact [email protected] for a data processing agreement.
Changes to an organization, such as members joining or leaving and settings changed in the console, are written to its audit log with who made them, when, and the IP address and user agent of the request. The organization's owners, admins and viewers can read the log, including those details.
When an owner or admin invites someone by email, or gives a member an email address as a label, we keep the address they typed. An invite's address is used to mail the invite and becomes the label of the member who joins with it. Owners and admins also see the address on the organization's invite list. The invite goes out through the same email delivery provider as our other email and carries an unsubscribe link; an address that bounced, reported spam or unsubscribed from the organization's mail is not sent another invite from it. The organization's owners, admins and viewers see the label on the member; it is not verified and never how anyone signs in. A label stays until an owner or admin changes it or the member leaves or is removed. The invite's own copy is cleared 30 days after the invite ends, or when the member who joined with it leaves or is removed.
Single sign-on and SCIM (Enterprise). An organization on the Enterprise plan can verify the email domains it owns and connect its own identity provider, such as Okta, Microsoft Entra ID or Google Workspace. If you sign in to the console through it, the provider sends us your email address on one of those domains and its identifier for you (the OpenID Connect subject or the SAML NameID). We keep both with your PushWard account, so your next sign-in finds it, and the address also becomes an email sign-in method of your account; if the sign-in creates your account, the name the provider sends becomes your display name. If the organization provisions its people through SCIM, its provider sends us what it maps for you: your work email address, your given, family and display names, its identifier for you and whether you are active, and the names and identifiers of the groups it pushes and who is in them. We use these to invite, update and remove members and to keep the organization's groups in step. The organization decides what its identity provider sends: for this data the organization is the controller, and we process it on its behalf. The organization's verified domains, its identity provider settings (an OpenID Connect client secret is stored encrypted and never shown again) and its SCIM keys belong to it the same way. Its owners, admins and viewers can also download the audit log as a CSV file, with the IP addresses and user agents as the log shows them to their role; we create that file when they ask and keep no copy, and the download itself is recorded in the log.
Billing. PushWard Team and Enterprise subscriptions are sold by Paddle.com, our reseller and merchant of record; Enterprise is billed by an invoice that Paddle sends. Paddle collects the payment and the billing details (the billing contact's name and email, the company name, VAT ID, address and country) and handles them as the seller, under its own privacy notice. Card and bank details go to Paddle and never reach us. Paddle tells us the billing contact, company, VAT ID and country, and the subscription's state (seats, renewal date, payment status), so we can run the organization's seats and answer billing questions.
What we don't collect
We never require your name, phone, address, or location to create or use your account,
and not your email either when you sign in with Apple, which gives us only an opaque
identifier. Signing in with Google in the Android app gives us your Google account's
email address and name as described above. The exceptions are the
ones you choose: the email address or Google account you sign in to the console or the
Android app with, the
optional email channel above, where the recipient addresses you choose to send to are
stored so we can deliver and verify them, the billing contact of a PushWard Team or Enterprise
subscription (name, email, company, VAT ID), which Paddle reports to us, and what your organization's
identity provider sends about you if it uses single sign-on or SCIM (above).
No advertising identifiers (IDFA or Android advertising ID), or cross-app tracking. No tracking or advertising
cookies. The iOS and Mac apps and this website use no third-party analytics, crash reporters, or
SDKs of any kind. The Android app has no analytics or crash reporters either; its only
third-party SDKs are Google's: Firebase Cloud Messaging to receive notifications, Android's
Credential Manager for signing in with Google, Google Play Integrity for Sign in with Apple,
Google Play Billing for purchases, and the Google Play services code scanner,
used only when you scan an encryption key's QR code, which reports device and app
information and performance metrics to Google. The iOS app talks only to Apple (including
iCloud) and to api.pushward.app, and the Android app only to Google, to
Apple's sign-in page if you sign in with Apple, and to api.pushward.app;
beyond that, either app fetches the images and calls the
action addresses that a notification or Live Activity you receive points to, from the
sender's own servers.
Cookies
The website and the iOS and Android apps set no cookies. The web console at console.pushward.app uses two cookies on api.pushward.app, both
strictly necessary to sign in, so they need no consent: __Host-pw_login protects the sign-in step and expires after 10 minutes, and __Host-pw_session keeps you signed in for up to 7 days, ending sooner after a
day without use or when you sign out. Both are HttpOnly, Secure and SameSite=Strict, so
page scripts and other websites cannot read or send them. We store each console session
with your browser's user agent and delete the record 7 days after you sign out or it
expires. The console's checkout and billing pages load Paddle's checkout (Paddle.js),
which may set Paddle's own cookies under Paddle's privacy notice. If you sign in with
Google, the console sends you to Google's sign-in page, where Google's own cookies and privacy policy apply; nothing from Google loads in the console before you choose it. Sign in with Apple
in the Android app opens Apple's sign-in page in your browser, where Apple's own cookies and privacy policy apply. Signing in with single sign-on uses the same two cookies and sets no other: while you
are at your organization's identity provider, the console keeps only the address of the
sign-in page you started from, in that browser tab's session storage
(pushward.sso), and removes it when you come back; the rest of the sign-in's
state stays on our server. The identity provider's sign-in page sets its own cookies under
its own policy.
How your data is handled
We process this data to operate the service (contractual basis) and to protect it from abuse (legitimate interest). API tokens and integration keys are stored as SHA-256 hashes -- we never see your plaintext tokens. Push delivery telemetry hashes destination tokens too, and payload contents are never logged. IP addresses are used transiently for rate limiting and discarded, except in an organization's audit log (above).
Email sign-in codes are six digits, stored only as a hash, valid for 10 minutes and only in the browser that asked for them. The record of each code request, including the address it went to, is deleted within two days. When you start a free PushWard Team trial, we keep a SHA-256 hash of each email address you sign in with (lowercased, without a +tag, and for Gmail without dots), so the same address cannot start a second trial with a new account. If that account signs in with Apple or Google, we also keep a SHA-256 hash of the identifier Apple or Google gives us for it, for the same purpose. We do not keep the address or identifier itself, but a hash can be matched against an address or identifier we are given, so we treat these hashes as personal data. We keep them after you delete your account, for as long as we offer free trials, to prevent repeat trials.
Emails you send are delivered through a third-party email delivery provider; bounce and spam-complaint feedback is used to suppress addresses that should not be contacted again. If you turn on iCloud settings sync, your app preferences (notification settings, language, sort order) are mirrored through your own private Apple iCloud account -- secrets such as tokens and keys are never included.
Where your data lives
Application data is hosted in the EU (Frankfurt). Live Activities and notifications,
with their content and the device's push token, travel through Apple's APNs to Apple
devices and through Google's Firebase Cloud Messaging to Android devices (both
US-based), covered by the EU-US Data Privacy Framework and Standard Contractual Clauses.
Firebase Cloud Messaging also uses a Firebase installation ID that Google assigns to the
Android app on each device. The third parties that touch your data are Apple (Sign in with
Apple, push delivery to Apple devices, App Store purchases, and -- if you enable it --
iCloud settings sync), Google (push delivery to Android devices; Google sign-in, only if
you sign in with Google in the Android app or the console or add Google to your account;
Play Integrity checks, only when you sign in with Apple in the Android app; Google Play
purchases, only if you buy in the Android app; and the code scanner above, only if you
use it), Cloudflare (DNS and TLS for pushward.app), and -- if you use the email channel or sign in with an email
code -- a third-party email delivery provider, which sends those emails from the EU
(Frankfurt) region. For PushWard Team and Enterprise subscriptions, Paddle handles payments and billing details as
described above. We do not sell, rent, or share your data for advertising.
How long we keep it
Activities you create through the API are automatically deleted once their TTL expires. Records of emails you've sent are kept for 90 days; the recipient addresses you register stay until you remove them or delete your account. Addresses that hard-bounce or report your mail as spam are added to a suppression list we keep indefinitely so we don't email them again. The trial hashes described above outlive your account. Everything else exists for as long as your account does -- delete your account from inside the iOS or Android app or from the console's Account page and everything tied to you (devices, activities, tokens, integration keys, sign-in email addresses, purchase records) is removed by database cascade. Backups roll over within 30 days.
An organization's audit log entries are deleted after 12 months. An organization whose trial ended without a subscription is deleted 30 days later, and a Team organization whose subscription ended is deleted 60 days later. An Enterprise organization is never deleted automatically: it stays until an owner deletes it or asks us to at [email protected]. Owners can delete an organization at any time, even while its subscription is still running, and its data is then removed at once. When you leave an organization or delete your account, your membership ends and the organization no longer sees your devices. Paddle keeps the invoices and billing records of PushWard Team and Enterprise as the seller, under its privacy notice. We keep our own records of Paddle's payouts to us for as long as Polish tax law requires (five years from the end of the year in which the tax on them is due). The copy of the billing contact that Paddle reports to us is deleted with the organization.
The link between your account and an organization's identity provider (its identifier for you and the address it came with) ends when the organization removes that domain or its verification lapses, when it changes or removes its identity provider, when it is deleted, and when you delete your account. A single sign-on in progress is kept on our server, with the random values that tie it to your browser and, for SAML, the request's identifier and the result, until it finishes and for 10 minutes at most; expired ones are deleted within the next hour. The identifiers of SAML assertions are kept until each assertion expires, so none is accepted twice, and deleted within the next hour too. What SCIM sends about you stays until the organization's identity provider deletes you or the organization is deleted, and verified domains until the organization removes them or is deleted.
Your rights
Under the GDPR you can access, correct, export, or delete your data, restrict or object to processing, and lodge a complaint with the Polish data protection authority (UODO, uodo.gov.pl). Email [email protected] to exercise any of these rights -- or start a data request straight from the iOS app's Backup & Sync settings -- we respond within 30 days. You can also delete your account directly from the iOS or Android app or the console's Account page at any time.
Changes & contact
If we change this policy, the updated version will be posted here. Controller: MAWIK Maciej Kędziora, NIP 8943263728, Wrocław, Poland. Questions: [email protected] · GitHub.