Skip to content
Pulsyn

Health data that stays yours.

Pulsyn’s AI runs on your phone. By default, your biometrics stay on your device. Data leaves your phone only if you turn on optional encrypted cloud sync, export it yourself, or connect a third-party app.

  • On-Device AI
  • AES-256
  • Zero Data Training

The rules we hold ourselves to.

On-device AI

The model that reads your biometrics runs on your phone, not on a server we control. Inference happens locally by default. If you opt into Pro cloud AI, your question context is used only to generate the answer, never to train models.

Optional encrypted sync

If you turn on Pro cloud sync, your phone encrypts your data with AES-256-GCM before it leaves. It is stored encrypted on EU servers in Frankfurt, protected by an app-managed key. To be clear, this is not a zero-knowledge design: we are technically able to decrypt synced data, and we commit to accessing it only as necessary to run the service.

No data training

Your biometrics are not used to train AI models. Not ours. Not a third party. Not in aggregate. Your readings are yours.

Data portability

Export everything in standard formats whenever you want. Delete your account and the data is gone within 30 days, not buried in a backup.

Three places. One of them is optional.

  1. Rune 1

    Sensor data

    Heart rate, motion, temperature. Captured on your finger.

    Bluetooth LE

  2. Your phone

    On-device AI

    Insights are computed here. Health data is stored on your phone in an encrypted local database.

    Optional

  3. Optional cloud

    Off by default

    Turn on encrypted backup if you want to. Synced data is stored encrypted on EU servers, protected by an app-managed key.

Your phone does the AI work and stores the results locally. If you turn on encrypted backup, your phone encrypts everything before it leaves, so the cloud only ever stores encrypted data.

What we will never do

Promises are easy. These are the lines we commit not to cross.

  • We will not sell your data. Not anonymized, not aggregated, not at all.

  • We will not train AI models on your biometrics, ever.

  • We will not access your synced health data except as strictly necessary to operate the sync service — never to sell it or train models on it.

  • We will not run advertising trackers, fingerprinting, or third-party pixels.

  • We will not share your data with insurers, employers, or advertisers. We disclose personal data only where legally required.

  • We will not lock you in. Export everything, anytime, in standard formats.

The cryptography behind it

Standard primitives. No homegrown cryptography. Here is what is doing the work.

AES-256-GCM
Health records synced to the cloud are encrypted on your device with AES-256-GCM before transmission, and stored encrypted.
Encrypted at rest
Your on-device health database is encrypted at rest, and synced data is stored encrypted on EU servers.
PBKDF2 key derivation
Cloud-sync encryption keys are derived with an iterated key-derivation function, which protects synced data if the database is compromised.
TLS 1.2+
When data does move, it is protected in transit with TLS 1.2 or higher.

If you turn on Pro cloud sync, your phone encrypts your data with AES-256-GCM before it leaves. It is stored encrypted on EU servers in Frankfurt, protected by an app-managed key. To be clear, this is not a zero-knowledge design: we are technically able to decrypt synced data, and we commit to accessing it only as necessary to run the service.

Read the full Privacy Policy to understand exactly how your data is handled.

Export your raw health data at any time as JSON or CSV. No lock-in, no hostage data.

Read the full privacy policy