1. Scope
This policy covers the Appointment Manager Chrome extension developed by Dr.Mohammed Al Saleem. Its scheduling features operate only on raqeem.anat.sa and moh.raqeem.sa. It is an independent extension and does not replace Raqeem’s own privacy policy or account controls.
2. Information the extension handles
| Information | Purpose and handling |
|---|---|
| Scheduling settings | PHC names and codes, care-provider names, departments, dates, time periods, execution times and preferences are stored locally in Chrome to configure your workflows. This includes names or departments you enter manually. |
| Raqeem page content | The extension reads relevant scheduling forms, session and schedule rows, dates, periods, status and checkbox states. Row text may be processed temporarily to check that results have loaded and that the intended rows are selected. It is not designed to extract patient charts, diagnoses or clinical notes. |
| Run progress and logs | Local records contain the selected PHC, care provider and department; phase configuration; timestamps; steps; results; status; and error messages. Job, task, tab and document identifiers help track execution and avoid unintended duplicate submissions. |
| Authentication information | A password supplied for a Generation run is held temporarily in browser session storage and used only to unlock the recognized Raqeem session-lock form when needed. See the password section below. |
| Target tab address | The current tab address is checked to restrict operation to the supported Raqeem websites and verify the page context. It is not retained as general browsing history. |
The extension also includes bundled PHC, care-provider and department reference lists. It does not download these lists or executable code from a developer server.
3. Passwords and session unlocking
Generation requires a password before a run starts. If your Raqeem session is already open, the workflow continues without entering the password. If the supported session-lock form appears during execution, the extension enters the supplied password and activates Raqeem’s sign-in control.
The password is kept separately in chrome.storage.session, not in persistent settings, Generation records or exported logs. It is removed when the run completes, is stopped or encounters an error, including termination after the target tab closes or leaves a supported Raqeem host. Browser session storage is also cleared when Chrome restarts or the extension is disabled, reloaded or updated.
The password is submitted to Raqeem through its own HTTPS page. It is not sent to the extension developer. The extension does not unlock Windows or bypass one-time codes or other authentication requirements.
4. Use, transmission and sharing
Information is used to perform and review the appointment-management actions you configure. The extension has no developer-operated data backend, advertising, analytics or tracking integration, and does not use Chrome Sync for its settings or logs.
When a workflow enters information, generates a schedule or saves a cancellation, Raqeem receives that action through its normal website controls. Raqeem’s handling of those submissions is governed by its own policies. Exported logs are saved as a text file on your device and are shared only if you choose to share that file.
The extension does not sell user data, use it for advertising, transfer it for unrelated purposes, or use it to determine creditworthiness or for lending.
Limited Use: Appointment Manager’s use and transfer of information received from Chrome APIs adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
5. Retention and your control
- Settings remain in the extension’s local Chrome storage until you edit them or remove the extension’s stored data.
- Generation records retain the latest run and up to 10,000 log entries. Starting a new Generation run replaces the previous run record.
- Passwords are temporary and follow the deletion rules described above.
- Uninstalling the extension removes its extension-local data from that Chrome profile. Exported text files remain on your device until you delete them separately.
You can edit your configuration, stop an active run or disable the extension. Stopping a run does not reverse actions Raqeem has already accepted. Local storage is not a password vault; access to your device and Chrome profile should be protected.
6. Why permissions are needed
- Storage: saves settings, progress and logs locally and holds the current run password temporarily in session storage.
- Scripting: runs the extension’s packaged automation scripts in the selected supported Raqeem tab when needed.
- Alarms: schedules the Generation phases you start and monitors execution timeouts.
- Power: supports the optional Keep computer awake setting while Generation is waiting or running. It prevents automatic idle sleep, allows the screen to turn off and releases the request when the run ends.
- Host access: permits interaction with scheduling controls on the two supported Raqeem HTTPS domains. Access to unrelated websites is not requested.
The extension does not request browser-history, cookies, location, camera, microphone or clipboard permissions.
7. This privacy-policy website
This page contains no analytics scripts, advertising or data-entry forms. Its hosting provider may process technical connection information needed to serve and secure the page under the provider’s own policies. This is separate from data handled by the extension.
8. Changes to this policy
This policy may be updated when the extension’s features or data practices change. The effective date and applicable extension version will be updated here.
9. Contact
Developer: Dr.Mohammed Al Saleem.
For privacy questions, use the developer contact details provided on Appointment Manager’s Chrome Web Store listing.