Skip to content

Doctorus information

Website privacy

How the public website is designed to handle enquiries, browser preferences and optional technical monitoring. This is not the privacy policy for patient records in Medical Space.

Enquiries and their purpose

An access request includes your first and last name, email, profession and country of practice. Specialty, phone number, current software, migration assistance and additional information are optional. A contact request includes your name, email and message, with an optional phone number. We use these details to assess your request, discuss a demonstration or migration, and provide a personal team reply.

Do not send patient details, medical records, passwords or access codes through this website. The forms do not accept attachments. Free-text fields can still contain information you choose to enter; they are not a clinical-data submission channel.

Acceptance stores the enquiry and pending staff notification together. A receipt means the request was received, not that access was approved, a demonstration was booked or a team member has replied. No automatic acknowledgement email is sent to the visitor.

Enquiry storage and retention

Enquiry storage uses an encrypted AWS DynamoDB table provisioned in Europe (Ireland), eu-west-1. Accepted enquiries include submitted information, a request reference, acceptance time, submitted language, accepted catalogue choices, retry information and notification state. Restricted staff tools support retrieval and delivery recovery; there is no public enquiry lookup or deletion endpoint.

The approved production policy has no automatic age-based expiry for accepted enquiries and their notification state. The backend implementation omits an expiry time for these records, keeping them available for authorised follow-up and notification recovery until authorised deletion.

No age-based expiry does not remove the need to assess continued necessity or handle legitimate deletion requests. It does not promise permanent recovery of a browser session or unlimited notification retries. Existing records created under a finite retention policy keep their original expiry; no existing records are rewritten automatically.

Backups, technical logs, failure metadata, staff email and any authorised staff downloads have separate retention arrangements. The configured technical limits are 35 days for database recovery backups, 30 days for technical logs and 14 days for metadata-only failure queues. Mailbox copies and staff downloads have separate access and deletion responsibilities; the enquiry policy does not retain every copy indefinitely.

Staff notification and email

The form handoff sends the submitted details to the fixed staff recipient, abdesselem.idani@doctorus.io, through AWS SES. Open and click tracking are disabled in the notification source. The two approved production smoke notifications reached the bounded sent state and the owner confirmed inbox receipt. That verifies those test enquiries, not every future delivery or a personal response. The receiving mailbox uses Microsoft 365; its access, retention and delivery handling remain separate from the enquiry database policy.

Direct email is handled in the receiving mailbox; it does not automatically create a website enquiry record. The owner confirms adding hello@doctorus.io as an alias on the existing Microsoft 365 operator mailbox, with its primary address unchanged. Receipt and personal reply through the alias have not yet been verified.

Browser storage

Form drafts, retry commands and receipts are held in page memory, not saved by the website in local storage, session storage or a browser database. Leaving or reloading the page does not withdraw an enquiry already accepted by the backend.

When monitoring is available, the website remembers only your monitoring choice, its policy version and expiry time in local storage. This preference contains no name, email or enquiry reference. The reviewed production policy keeps the choice for 30 days. Clearing your browser's site data removes the saved choice.

Optional website monitoring

Optional AWS CloudWatch RUM is configured for the production website in AWS Europe (Ireland), eu-west-1. Collection starts only after you allow it. Among visitors who allow it, 10% of sessions are sampled. Monitoring cookies and session replay are disabled. You can review or change your choice using Monitoring preferences in the footer. Declining monitoring does not prevent website navigation or enquiries.

The website sends only approved page identifiers, language and release information, performance timings, fixed error categories, and enquiry-operation timing and result categories. A random session identifier exists only in memory for that monitoring interval. After consent, the browser sends these events directly to a public AWS RUM resource-policy endpoint without AWS credentials. The website does not use monitoring cookies, session replay, advertising tracking or form-content capture. It excludes names, email addresses, enquiry references, full URLs, query values, referrers and raw error details from monitoring events.

Withdrawal stops future collection and attempts to cancel in-flight transmissions. It does not erase events already received by AWS. The production monitor endpoint is in AWS Europe (Ireland), eu-west-1. AWS RUM retains event-level data for 30 days under its service behaviour; this is separate from the 30-day browser-choice lifetime. Operator access remains governed by separately reviewed AWS permissions.

Hosting and technical safeguards

The public hosting architecture uses Amazon Web Services: a private S3 origin for generated website files and CloudFront for HTTPS delivery. CloudFront uses a distributed edge network; it is not a promise that all processing stays in one country. The enquiry API, database, mail and monitoring have separate configurations. The enquiry storage is provisioned in Europe (Ireland), eu-west-1. Website delivery, mail and optional monitoring have separate operational settings.

The enquiry source limits access logs to technical request identifiers, fixed routes, methods, status and time. Staff-operation audit records contain restricted operational metadata, not form bodies. Network and hosting providers also process connection information to deliver and protect their services. Their applicable arrangements are separate from the enquiry-record retention policy.

Questions, corrections and deletion requests

Contact abdesselem.idani@doctorus.io about website information or to request access, correction or deletion of your enquiry. Include only the information needed to identify your request; do not send patient records or identity documents unless a suitable verification process has been agreed.

Deletion requires a manual, authorised process covering the active record, notification copies, mailbox and any staff exports, with separately assessed backup and log limits. There is no automated self-service deletion workflow or verified deletion deadline. A restore must account for previous deletion requests before records or notifications return to service.

Read the legal notice. Read the Terms of Use. These documents do not replace separate Medical Space privacy information or an applicable data-processing agreement.