Privacy policy
Last updated:
This page explains what personal data MedFlow handles, why we handle it, who can see it and how long we keep it. We wrote it in plain language, for doctors.
1. Who we are
MedFlow is practice software for doctors in Algeria. It has two parts: a Windows desktop app that runs the practice, and this website with online services (doctor accounts, the public profile and directory, ticket tracking and the colleague room).
The service is operated by MedFlow. How to reach us is at the end of this page.
2. Two kinds of data
Practice data: on your computers
Patient records, visits, prescriptions, the queue, appointments and reception staff accounts. They are stored in local databases on the practice’s own computers: the Main PC and the reception PCs connected to it on your local network. The app works with no internet connection.
Cloud account data: on MedFlow’s servers
What a doctor needs for online services: the account, verification documents, the public profile, the licence, payments, ticket tracking and the colleague room. The next sections list each one.
The two are kept separate on purpose. The cloud has no copy of your patient files. The only clinical text it can hold is what a doctor chooses to write in the colleague room, without identifying the patient.
3. What we collect and why
Your doctor account
We collect your full name, email address, phone number, medical licence number, password, preferred language and public handle. We also record which version of the terms you accepted and when.
- Why: to create and protect your account, check that you are a doctor, issue your licence and help you when you ask for support.
- Your password is stored only as a one-way hash, never in readable form.
- When you sign in on the website we record the time, your IP address and a description of your browser for that session.
- We use your email address only to write to you about your account and about changes to these terms and this policy. Account help goes through our support team.
Verification documents
When you register you upload documents such as your medical licence and national ID. Our staff use them to approve your account. They are private: only authorised MedFlow staff can open them, and they are never shown on your profile.
Your public profile
You choose what to publish: display name, specialties, languages, location and address, practice phone numbers, map link, biography, experience, education, certifications, consultation price range, services and photos. This information is public by design. Anyone can see it, and search engines may list it.
- Photos are resized and re-encoded on our server, which removes hidden data such as GPS location.
- Your email, account phone number, licence number and verification documents are never shown publicly.
Your licence and your Main PC
To activate the app, your Main PC sends its machine code, practice identifiers and app version, and we return a signed licence. We keep the licence, a history of link events (such as connecting and disconnecting, with the app version) and when the PC was last seen. No patient data is part of this.
Payments
For online payments we use Chargily. We send it the amount, a short description of the product, your language and internal reference numbers. You enter your payment details on Chargily’s page, and we never see them. Chargily tells us the result.
- For manual payments (CCP, BaridiMob or cash) you may upload a proof of payment (PDF or image) and a reference. Our staff review it.
- We keep the payment record: amount, product, status, dates, reference and review notes, together with your online-services periods.
Why: to sell and deliver the licence and online services, and to keep accounting and dispute records.
Ticket tracking for patients
When a practice with active online services prints a ticket with a QR code, the Main PC sends the cloud only that ticket’s code (for example A-042), its status, how many people are ahead and the estimated minutes. The Main PC works these out; the cloud never receives what they are based on.
- Never sent: patient names, phone numbers, records, appointments, other tickets or the waiting-room list.
- The printed QR is a private link to that one ticket. Whoever holds the ticket can see its status, so keep it private. The page keeps the link only in the browser tab’s session storage.
- Optional notifications: if the patient turns them on, the browser gives us a push address, which we store linked to that ticket only. We use it to tell the patient when the ticket is called or close. The message travels through the browser’s push service (Google, Mozilla, Apple or Microsoft, depending on the browser).
Why: so each patient can follow their own turn from their phone.
Technical and security records
Our server logs record the request method, the page path without its query string, the status code and a request number. They do not record what you send, your password or your browser headers. We also keep short-lived counters tied to your IP address to slow down abuse.
- Actions by MedFlow staff (approvals, payments, licences, moderation) are written to an audit log with who did it, what and when.
- Our hosting provider necessarily handles the network traffic to the website and API and may keep its own technical logs.
Desktop app updates
The app checks for updates by contacting MedFlow’s server, which receives the app version and the Windows platform. The app may also read a public file on GitHub that announces a next major version; GitHub then sees the computer’s IP address.
4. Patients’ data and the doctor’s role
The patient records belong to the doctor’s practice, not to MedFlow. The doctor decides what is recorded and why, and is responsible for those records: informing patients, medical confidentiality, answering patients’ requests, and keeping the computers and backups secure.
MedFlow supplies the software. We do not see the records, we cannot open them, and we cannot restore them if both the backup password and the recovery key are lost.
What leaves your computers
- Licence activation and link information (section above).
- The public profile, only when you publish it.
- The status of tickets that carry a QR code.
- Text you choose to send to the colleague room.
- Update checks.
By design, nothing else is sent: not patient records, visits, prescriptions, appointments or reception accounts.
On the practice network
Reception PCs keep a working copy of the data their role needs. Paired computers talk to the Main PC over an encrypted connection on your local network, and unpaired computers are refused. Reception staff have their own local accounts with limited access, which the doctor manages.
Backups
The app creates encrypted backup files on the USB drive or folder that the doctor chooses. MedFlow does not receive them. If the chosen folder is synchronised by a cloud-drive service, the encrypted file goes to that service, under the doctor’s own agreement with it.
What we recommend to the doctor
- Protect each computer with a Windows password and, if possible, disk encryption, and control who can use the reception PCs.
- Keep the backup recovery key in a safe place, apart from the backups.
- Remove the accounts of staff who leave, and tell patients how the practice uses their data.
A patient who wants to see or correct their record should ask their doctor’s practice. MedFlow holds no patient record and could not find a patient in its own data.
5. The colleague room
The colleague room lets a verified doctor ask other verified doctors for an opinion on a case. It is only for doctors with active online services who accepted the room’s rules, and only when MedFlow has switched it on. It is not for emergencies.
Cases must not identify the patient
The doctor writes the case without any name, phone number, address, exact birth date or MedFlow code. The app shows the exact text before it leaves the computer and warns about anything that looks like an identifier. The server refuses phone numbers, email addresses and MedFlow codes.
- Images are cleaned on the doctor’s device before upload (metadata removed, with tools to crop or black out a name or face) and re-encoded again by our server.
- When a case starts from a patient chart on the Main PC, the doctor picks what to include (for example age, sex and chosen clinical fields). Identity fields are never offered.
- The link between a patient and a question stays only on the Main PC. It is not sent to the cloud and is left out of backups.
Who can see a question
The asker chooses one specialty or all doctors. Only verified doctors of that specialty (or all verified doctors) and those who asked or answered can see it; the server enforces this. A question shows the asker’s verified display name and specialty.
- A question can be asked anonymously: other doctors see only “Verified doctor”, with the specialty when enough doctors share it. MedFlow staff can see the real author, and each time they look it is logged. Answers are never anonymous.
- Staff can read room content to handle reports. They can hide content or remove it permanently, and they can suspend a doctor’s access to the room.
Notifications
If a doctor turns on phone notifications, the browser’s push address is stored for that doctor. Notifications are generic, such as “New answer to your question”, and never contain case text. The doctor can turn them off at any time.
Keeping and deleting
- An author can edit or delete their own question, answer or reply. Deleting wipes the text and its images and leaves an empty “deleted” placeholder.
- By default, a discussion is deleted for good 24 months after its last activity. This period is a setting that MedFlow staff can change.
- Unfinished drafts are deleted after 7 days. Images that were never attached are deleted after 24 hours.
- When an account is closed, the doctor’s phone-notification subscriptions, drafts, pending images and sign-in sessions for the room are removed. Published questions and answers stay until the retention period ends, unless staff remove them; the author then shows as “Former member”.
- Our hosting provider’s own database backups may keep deleted content until they rotate out.
7. How long we keep data
- Practice data on your computers: until the doctor deletes it. Backups are kept per destination as 7 daily, 4 weekly and 12 monthly files, and older ones are replaced.
- Verification documents: the file is scheduled for deletion 90 days after our decision on your account. We keep the record of the decision and basic file details.
- Account, licence and payment records, payment proofs and the staff audit log: kept while needed to run the service and for accounting and disputes. We have not set an automatic deletion period yet; closing an account stops sign-in but does not erase these records.
- Website sign-in sessions: a session lasts up to 30 days. The record of a session (time, IP address, browser description) stays with the account.
- Public profile: while the account exists. A replaced or removed photo stops being shown at once and its file is deleted within about a day.
- Ticket tracking: not shown after 03:00 the next morning (Algeria time) and deleted within about 30 minutes after that. Notification addresses are removed when the ticket is finished or cancelled, or at the end of the day.
- Colleague room: see the section above.
- Abuse-protection counters: short-lived, deleted automatically when their time window ends.
Deletion periods set by our hosting provider, such as for its own logs and backups, are outside our control.
8. Security
- Connections to the website and API use HTTPS. The desktop app only calls out to MedFlow’s servers; the cloud never opens a connection into your practice.
- Passwords are stored as one-way hashes. Verification documents and payment proofs are in private storage and are opened only by authorised staff through a logged action.
- The staff console requires a second sign-in factor, and sensitive actions ask for it again.
- Backups made by the app are encrypted. They can be opened with the doctor’s backup password or with a separate recovery key that only the doctor holds.
- Our servers do not log request contents, and push messages and logs never contain colleague-room case text.
No system is perfectly secure. If you suspect that your account has been misused, contact us right away.
9. Your rights and how to use them
We handle personal data with Algeria’s data protection law (Law 18-07) in mind.
You can write to us to ask what data we hold about you, to have it corrected, or to have it deleted. We will check your identity first. Some records, such as payments, may have to be kept, and we will tell you if that is the case.
Some things you can do yourself:
- Change your public profile, and replace or remove your photos.
- Edit or delete your own colleague-room questions, answers and replies, and turn its notifications off.
- Sign out, and clear the cookies of your browser.
- As a patient, stop ticket notifications from the ticket page or your browser settings.
For patient records, contact the doctor’s practice (see the section on patients’ data).
11. Changes to this policy
When we change this policy we update the date at the top of the page. We also tell doctors about changes in the app and, where available, by email.
12. Contact
For any question about this policy or about your data, write to us: