DiapStash is designed to preserve your privacy. By default, no application data is transmitted to our servers.
DiapStash keeps data linked to the "Cloud Sync" feature. The "Cloud Sync" feature is not enabled by default
Your data is linked to a unique random identifier (UIID).
The data is deleted by disabling the "Cloud Sync" feature in the application settings.
All "Cloud Sync" data, the account, the API and the catalog are hosted on our own servers. No SAAS platform is used to store them.
DiapStash uses a Sentry hosted on our server to analysis bugs. This allows us to detect and correct bugs.
All data are anonymous. Only application error logs/traces are sent. We do not collect any usage metrics.
DiapStash uses a service (FlagSmith) hosted on our servers to remotely enable some features. This allows us to test features live without impacting all the users.
If the "Cloud Sync" feature is enabled, we can use your user ID to enable a feature of the application on your device(s). If the "Cloud Sync" is not enabled, we can use a device ID generated by the application instead.
Activation of functionality is at the user's request to the DiapStash team. This is done as part of the development of a new feature.
Push notifications are delivered by Apple (APNs) on iOS and by Google (Firebase Cloud Messaging) on Android.
They are only used with features that involve our servers: push updates (your other devices are notified when you start or end a change, or record an accident, if "Cloud Sync" is enabled) and sharing notifications (activity on a stock or history shared with you). Reminders you configure in the application are scheduled on your device and never use push.
A push token identifying your device is sent to Apple or Google, and to our servers so they can address the notification. Notifications are silent messages: the displayed text is built on your device.
You can avoid push entirely by not enabling "Cloud Sync" and sharing, by disabling "Push updates" in the Cloud settings, by disabling sharing notifications, or by refusing the notification permission.
Donations to the DStash Foundation (one-time or monthly, from the application or from this website) are processed by Stripe, and by Apple Pay on iOS. Nothing is sent to Stripe if you do not donate.
Our donation service, hosted on our own servers, creates a Stripe customer with the name and email address you enter, and retrieves your billing address from Stripe, to issue your donation receipt. They are not used for any other purpose.
Your payment details are entered in Stripe's secure payment form (or authorized through Apple Pay): we never see your card number. Stripe also applies its own fraud prevention, according to its privacy policy.
Our donation service has no donor database. It only keeps accounting data: the net amount of each donation (after Stripe fees) and the Stripe charge reference, with no name, email or address. Donor information is kept by Stripe, in the DStash Foundation's account.
The receipt is sent to your email address, with a copy kept by the DStash Foundation for its accounting (legal obligation), through Zoho CPaaS (see "Emails" above). Monthly donations are Stripe subscriptions: each receipt includes a link to manage or cancel it. The identifiers of your Stripe customer and subscriptions are kept in the application settings on your device.
Transactional emails are sent through the email delivery service Zoho CPaaS (formerly ZeptoMail, European infrastructure): the forgotten password email of your DiapStash account, sent only when you request it, and donation receipts (without open or click tracking).
The service receives your email address, your name or username, and the content of the message (such as the reset link or the receipt). It is not used for newsletters or advertising, and your email address is not used for anything else.
The account (sign-in), "Cloud Sync", the API, the error reporting (Sentry) and the feature flags (Flagsmith) run on instances operated by DiapStash, on our own servers. The data they receive is not shared with any other company.
The application only requests the permissions needed by a feature, most of them on first use: camera (QR code and barcode scanners), notifications, biometrics (app lock), and saving shared images to your photo library.
No location, contacts, microphone or advertising identifier is used. No analytics or tracking SDK is embedded.
The complete list, with the feature behind each permission, is available in the permissions documentation.
The full list of permissions and third-party services, with the data involved and the reason for each, is available in the documentation: