Privacy Policy

Last updated: September 2026

This policy covers the PoolDose mobile app (com.pooldose.app, available on Google Play) and this website.

Who we are

PoolDose (pooldose.djump.io) is operated by DJUMP, MB, Šilutės pl. 35G-36, LT-94105 Klaipėda, Lithuania (registration code 307521980). We are the data controller. Contact: start@djump.io.

Your account

You can create an account with an email address and password, or sign in with Google or with Apple (Sign in with Apple). Sign-in is handled by Supabase Auth; we store your email address and, if you gave one, your name. If you turn on reminders, a push notification token for your device is stored on your profile so we can send them.

You can also use PoolDose without an account. A pool you create as a guest stays on your device and reaches our servers only when you sign in and it is moved to your account.

What the app stores for you

Pools — the name you give them, water volume, sanitizer type and surface type.
Water readings — the chemistry values you enter or scan, the doses PoolDose calculated from them, and any note you attach.
Seasonal programs — which opening and closing steps you have ticked off.
Scan counter — how many test-strip photos you have read and on which day, so the free allowance (3 scans in total) and the Pro limit (20 per day) can be enforced.

These rows belong to your account and the database restricts them to it. We do not use them for advertising and we do not sell them.

Test-strip photos

When you scan a strip, the app sends the photo to our read-strip function, which passes it to a third-party vision service to read the colour pads and returns the estimated values. The photo is processed in memory only — it is never written to storage and never written to logs, and it is discarded with the response. What is saved to your account is the reading, not the image. The app asks for camera and photo-library access only when you start a scan.

Purchases

Premium is sold through Google Play, which takes the payment — PoolDose never sees your card details. We use RevenueCat to tell the app whether your purchase is active; it receives a store transaction identifier and an app-specific user identifier, and returns your subscription status.

Analytics and crash reports

The app uses PostHog (EU-hosted) for product analytics: which screens are opened and which features are used, as counts and outcomes — for example that doses were calculated, not what your water values were. Once you sign in, those events are linked to your account identifier and email address. It also uses Sentry for crash and error reports, which carry the technical diagnostics of the failure (device model, app version, stack trace). Neither receives your test-strip photos. Both are switched off in development builds.

This website

This website sets no cookies and carries no advertising trackers. We use Vercel Web Analytics to count page views: it is cookieless and uses no cross-site identifiers, it processes technical data about your visit (including your IP address, from which a short-lived visitor hash is derived), and we see only aggregate numbers. If you write to us through the contact form, your message and your email address are delivered to our inbox by Resend. If you joined the pre-launch waitlist, we still hold the address you gave us until you ask us to remove it.

Why we process it, and on what legal basis

Performance of a contract (GDPR Art. 6(1)(b)) — your account, your pools, readings and programs, reading a photo you submit, and your purchases.
Legitimate interests (Art. 6(1)(f)) — keeping the service working and paid for: crash reports, aggregate product analytics, and the scan counter that enforces the free and Pro limits.
Consent (Art. 6(1)(a)) — waitlist and launch emails, and push notifications, each of which you can withdraw at any time.

Where it is stored, and who processes it

Your account and app content live in a Supabase (PostgreSQL) database hosted in the European Union. Processors acting on our behalf are: Supabase (EU hosting), the third-party vision service that reads a submitted strip photo in memory, RevenueCat (USA, purchase status), PostHog (EU hosting, product analytics), Sentry (USA, crash reports), Vercel Inc. (USA), which hosts this website and operates its analytics, and Resend (Plus Five Five, Inc., USA), our email provider. Google and Apple act as independent controllers for the sign-in and payment steps that happen on their side. Where data is transferred to the United States, the transfer is safeguarded by the European Commission's Standard Contractual Clauses or an adequacy mechanism such as the EU–U.S. Data Privacy Framework, as applicable to each provider.

How long we keep it

Your account and everything attached to it are kept until you delete them — deletion in the app is immediate. Crash reports and analytics events are retained for up to 12 months and then age out. Purchase records held by Google and by RevenueCat survive account deletion because tax law requires transaction records to be kept; they no longer identify a PoolDose account once the account is gone. Waitlist addresses are kept until you ask us to remove them.

Deleting your account and data

In the app: Profile → Settings → Delete Account. This deletes your PoolDose account and every pool, reading, dosing result and program record attached to it, and removes your sign-in entirely unless another DJUMP app still holds data for you. Full instructions, and how to ask us to do it by email, are at pooldose.djump.io/delete-account.

Your rights

You may request access to, correction of, deletion of, or a copy of your data, restrict or object to processing, and withdraw any consent you have given, by emailing start@djump.io. You may also lodge a complaint with your local data protection authority.