Privacy at lindly

Who is responsible

The controller for the personal data described here — the party that decides why and how it is processed — is:

Controller

Prescore GmbH

Address

Überlandstrasse 198, 8600 Dübendorf, Switzerland

Contact

hello@lindly.app

You can reach us at that address for any question or request about your data.

What we process, and why

We keep to what the service actually needs:

• ✓Your account email. Once you confirm one, so you can sign in — with a link or a 6-digit code we email you — and recover your account across devices. Legal basis: the contract to provide the service you signed up for.
• ✓The health-event data you enter. The feeds, diapers, sleep, growth and notes you log, plus each child's details — the shared timeline itself. Legal basis: the contract to provide the service.
• ✓Device & session metadata. The technical data needed to keep you signed in and the app working — a session identifier, app/device version, and security logs. With each request, the app also tells our servers which version it is (its platform, build number and the app update it is running), so that we can require an update when an old version would no longer work correctly with our servers. Legal basis: contract for what runs the service, and our legitimate interest in keeping it secure and free of abuse.
• ✓Your waitlist email. Only if you join the pre-launch waitlist. Legal basis: your consent, which you can withdraw with the one-click unsubscribe in every email.

Where your data lives

Every server that stores or processes your family's data runs in Switzerland — Google Cloud's Zurich region (europe-west6): the database (Cloud SQL), the services that run the app (Cloud Run), and our secrets (Secret Manager). Your account and sign-in data, the shared timeline of events, and any files all sit there, and backups are kept in the same region.

Hosting physically in Zurich is a fact we can state plainly: nothing can quietly deploy your data elsewhere, because the Swiss region is a hard constraint in our infrastructure, not a default.

Who processes it for us

We use a small, deliberate set of processors. Your logged health data stays in Switzerland; where a service can't be Swiss-pinned, it never carries that content.

• PostHog (EU)

  Privacy-first product analytics — how the app and this site are used (pages, taps, funnels), cookieless and hosted in the EU (Frankfurt). It processes this on our behalf; it never receives anything you log about your baby, and you can turn it off any time in the app under Settings.

• Google Cloud

  Hosting — Cloud SQL, Cloud Run and Secret Manager in the Zurich region (europe-west6), with backups in the same region.

• Hostpoint AG

  Transactional email — the sign-in links and codes, caregiver invites and the waitlist note. A Swiss provider.

• Cloudflare

  DNS only — it answers where our domain names point. It does not proxy or see any app traffic or health data.

• Expo / EAS

  App builds only. No user data passes through it.

• The AI assistant provider you connect

  Only if you connect one over MCP, and only for the Home and scope you consent to — see “Connecting an AI assistant” below. That provider then processes what you share on its own infrastructure.

Apple and Google (the app stores)

You download lindly from Apple's App Store or Google Play. Apple and Google run those stores as independent controllers, under their own privacy policies — for your store account, the download, and anything else you do in the store. We don't receive personal data about you from them: in this version, nothing is bought through the stores. They may show us aggregated statistics, such as download counts, and crash reports if you allowed your phone to share them with app developers.

What we don't do

• ✓No ads, ever — we make money from subscriptions, not from advertising.
• ✓We never sell or share your data for advertising. Your child's data is not a product.
• ✓No third-party analytics or trackers. Any usage measurement is first-party and Swiss/EU-hosted, and never includes what you log about your baby.
• ✓No cookie banner, because there are no non-essential cookies. The one cookie we set is the session cookie that keeps you signed in — SameSite=Lax, HttpOnly, Secure.

Connecting an AI assistant

You can connect your own AI assistant to a Home over MCP — entirely optional. It only ever gets access with your explicit, per-Home consent: you choose which Home, which children, and read-only versus read-and-write. That access is revocable at any time, and the access tokens expire. Whichever provider you connect becomes a processor acting on your behalf, on their own infrastructure, for exactly what you granted — and nothing more.

Notifications

While a timer is running — a feed or a sleep, say — the app can show it as a notification on your phone, with buttons to pause or stop it. These are local notifications: your phone creates and shows them itself, and nothing is sent through Apple's or Google's push services. We don't send push notifications today. If we introduce them, they'll be delivered through a global service (Firebase Cloud Messaging) that carries only a device token and a short message — never the content of a health event.

How long we keep it, and erasure

We keep your data for as long as your account exists. Deleting your account in the app is immediate and irreversible: your personal data is hard-deleted, not hidden. There is deliberately no “delete Home” button, so no caregiver can erase another's records — a shared Home's data is removed once its last member leaves.

Backups are rotated on a fixed schedule, and deleted data leaves them with that rotation.

You can also delete your account without the app, on the web: delete my account — sign in with your email, confirm, and it's done.

Your rights

Over the personal data we hold about you, you can:

• ✓Access and export. Download your complete history as CSV or JSON — free on every tier, including Free. Data portability is your right, so it's never paywalled.
• ✓Correct. Fix anything inaccurate, directly in the app.
• ✓Delete. Self-serve account deletion in the app, or without the app on the web (see above) — immediate and irreversible.
• ✓Object. Object to processing we base on our legitimate interest, such as security logging.
• ✓Complain. Raise a concern with the Swiss Federal Data Protection and Information Commissioner (FDPIC), or with your data-protection authority in the EU/EEA.

The pre-launch waitlist

While lindly is pre-launch, you can leave your email to be notified when it goes live. If you do:

• ✓Only your email address. That's the only personal data the waitlist stores — no name, no tracking.
• ✓Used for one thing. To email you about the launch — nothing else, no marketing drip.
• ✓Stored in Switzerland. In the same Zurich-hosted database (europe-west6) as everything else — the waitlist honors the same residency promise.
• ✓Unsubscribe in one click. Every waitlist email carries a one-click unsubscribe link that removes you immediately.

Children's data

lindly stores information about infants, entered by the parent or guardian who cares for them. The children can't consent for themselves, so their data is processed on your authority — and the account holder must be an adult. We treat infant health and children's data as special-category personal data and handle it with extra care.

Changes

If we make a material change to this policy, we'll tell you in the app and by email before it takes effect. This policy is governed by Swiss law.