Last updated:
Bedside is operated by Thomas Nisterenko, an individual developer based in Brazil.
Contact for anything in this policy, including exercising your rights: privacy@nisterenko.com
Bedside is a personal notetaking tool for medical students and professionals. It is a place to record your own notes, in your own words.
It is not an electronic health record system, not a hospital system, and not a medical device. It does not provide diagnosis, treatment recommendations, dosing advice, alerts, or risk scores. It is not for emergencies.
You are responsible for the data you choose to record in it, and for meeting whatever obligations apply to you professionally regarding patient information.
Your account. When you create an account we receive your email address, and — if you sign in with Google — the name and profile picture Google provides. We do not receive or store a password, because Bedside has none: sign-in is Google or a one-time code sent to your email.
Your subscription. If you subscribe, our payment processor (Stripe) handles the transaction. We never see or store your card details. We keep a record of which plan you have, when it renews, and Stripe's identifiers for your customer and subscription.
Your notes. Notes you write are stored on your device. If cloud sync is enabled, an encrypted copy is also stored on our servers — see the next section, because how this works matters.
Technical records. Our servers keep ordinary operational logs (timestamps, request paths, error messages) needed to run the service and diagnose faults. The app keeps a local diagnostic log on your device to help debug sign-in and sync problems; it records what happened, never the contents of your notes.
We do not use analytics or tracking, in the app or on the website. There is no telemetry. We do not build profiles, and we do not sell or share your data with anyone for advertising.
This is the part worth reading carefully.
Notes synced to our servers are encrypted on your device before they are uploaded. The key that decrypts them exists only on your devices and in the transfer code we showed you when you created your account. It is never sent to us.
That means:
Keep your transfer code somewhere safe. It is the only thing that can recover your cloud notes if you lose your devices.
Our database and authentication are provided by Supabase, hosted in the São Paulo, Brazil region. Transactional email (sign-in codes, account notices) is sent through Resend, which processes from infrastructure in the United States. Payments are handled by Stripe.
Each of these processes data only to provide its part of the service.
We do not process your data for advertising or profiling, and we do not make automated decisions with legal effects about you.
Brazil's Lei Geral de Proteção de Dados gives you the right to confirm we process your data, access it, correct it, request deletion or anonymisation, obtain a portable copy, know who we share it with, and withdraw consent.
To exercise any of these, write to privacy@nisterenko.com. We will respond within the period the law allows.
Two practical notes. Account deletion is available directly in the app — you do not need to ask us. And a data export will contain your account and subscription details plus your notes as stored: for synced notes, that is encrypted data we cannot decrypt, so the readable copy is the one on your device.
Bedside is intended for medical students and professionals and is not directed at children. We do not knowingly collect data from anyone under 18.
Notes are encrypted end-to-end. The database on your device is encrypted at rest, with its key held in your operating system's secure storage. Traffic to our servers uses TLS. Access to stored data is restricted per user at the database level. An optional app lock (PIN or biometric) protects the app on shared machines.
No system is perfect. If you believe you have found a security problem, please write to privacy@nisterenko.com.
If this policy changes materially, we will say so in the app and update the date above. The current version always lives at the published URL, and the app links to it rather than bundling a copy.