Privacy Policy

1 Introduction and Service Definition

Welcome to Murshid, the smart clinic management app designed for dietitians. This app is developed and fully managed by FES HealthTech, a company specializing in nutritional care technologies and medical content platforms.

This document defines the privacy policy applicable to the Murshid app, detailing the data we collect, how we use it, who we may share it with, and the safeguards we employ to protect it. This policy was last updated on October 14, 2026.

The use of the Murshid app is restricted to qualified professionals in nutrition and dietetics. This app does not constitute a medical service provided directly to patients; rather, it is a professional tool used exclusively by licensed healthcare providers.

2 Data We Collect

We are committed to collecting only the minimum data necessary to operate and improve the service. Below is a comprehensive breakdown of each category of data we handle:

A) Personal Account Data

When you authenticate and log in for the first time using Google Sign-In or Apple Sign-In, we collect your Email Address. Due to the default secure design of third-party authentication services, your public profile information such as your Display Name and Profile Picture URL are also securely retrieved and stored by our authentication service provider (Firebase Authentication) as part of your digital credential profile.

B) Professional Profile and Reports Data

After creating an account, you can enter your professional profile details such as clinic or health center name, nutritional specialty, clinic logo, and license number. This data is stored locally ONLY on your device (in the Isar DB database) and is used locally to customize the header of PDF reports issued to patients. It is NEVER uploaded or stored on Cloud Firestore or our external servers.

C) Patient Data (Including Encrypted Patient Web Form)

Patient Follow-up Web Form (End-to-End Encrypted): If you choose to utilize the Patient Follow-up Web Form feature to collect data from your patients, the App generates a secure, unique E2EE form link. The patient accesses this form via their web browser, where all input data (including physical measurements, health history, dietary assessments, and uploaded images) is encrypted locally in the patient's browser prior to transmission. This encryption uses authenticated AES-256-GCM cipher combined with asymmetric NaCl/X25519 key exchange. The encrypted payload is saved as a secure client data package that the patient shares directly with the specialist (e.g., via direct secure messaging or email). At no stage does FES HealthTech collect, store, transmit, or have access to either the decryption keys or the patient's medical data on its servers. The decryption and import process occur exclusively on your local device.

D) Usage and Analytics Data

We use Firebase Analytics to collect anonymous data about how you use the app, such as screens visited, frequency of using certain features, and session durations. This data is used exclusively to improve the user experience and develop features.

E) Wallet and Cloud Subscriptions Data

The subscription system, Gold Points balance, and Blue Points are managed via Cloud Firestore. Cloud servers exclusively process and store the following operational data: the email address linked to the account, subscription details, points balance history, and dates of consumption transactions.

F) Device and Session Management Data

We collect hardware and connectivity identifiers including your Device Name/Model, Device ID, and Approximate Location (Country-level only, via IP). We also monitor active sessions, last seen timestamps, and login attempts. This data is essential to link your device securely to your digital wallet, manage multi-device conflicts, enforce account-sharing prohibitions, and prevent abuse of the rewarded advertising system. We NEVER collect precise GPS location data, and your device/session data is never used for direct marketing.

G) Billing and Financial Transactions Data

The app allows issuing electronic invoices and financial receipts (such as simplified invoices compatible with ZATCA in Saudi Arabia, VAT settings, and customized global currencies). All billing data and financial records are stored locally ONLY on the dietitian's device under financial privacy mode, and are NEVER uploaded to any external servers.

H) Security and Anti-Fraud Data (Time & Connectivity)

To protect your subscription and ensure data integrity, the app collects and processes your device's System Time and Date, and stores local timestamps of your "Last Online Sync" and "Last Seen Activity". The app also makes periodic anonymous pings to public Network Time Protocol (NTP) servers (e.g., Google Time Servers) to verify the true global time. No personal data is attached to these time-check requests.

I) Biometric Verification Data (Strict Zero-Access Hardware Authentication)

If you choose to enable the Biometric Security Lock (Face ID, Touch ID, or Android Biometric Prompt) to protect patient clinical files or financial clinic data, all biometric scanning and template matching are executed entirely on your physical device by your operating system's dedicated hardware security architecture (such as the Apple Secure Enclave or Android Trusted Execution Environment / Keystore). FES HealthTech never accesses, captures, intercepts, collects, or stores your fingerprint patterns, facial geometry, or biometric credentials. Murshid receives only an encrypted cryptographic token from the local operating system confirming successful authentication.

J) Clinical Audio Notes & Voice Memos (Strict Local Storage)

Murshid includes a clinical notebook feature allowing you to record verbal patient observations, dictations, or clinical voice memos. When you record audio, the sound file is stored strictly in your device's local application sandbox. Audio recordings are NEVER uploaded to cloud servers, never processed through external cloud transcription APIs, never monitored, and never accessible to FES HealthTech or third parties.

3 How We Use Your Data

We use the collected data exclusively for the following purposes:

• Core Service Operation: Verifying your identity, granting you access to your account, and customizing your in-app experience based on your professional profile.
• Smart Data Extraction (OCR) Tools: When the dietitian voluntarily chooses to use the Cloud OCR feature to extract tests or medications from images, the selected image is sent via an encrypted connection (HTTPS/TLS) through FES HealthTech's secure Firebase Cloud Functions (acting as a secure API Proxy) to the Google Gemini API for optical character recognition. The image data is processed purely in real-time RAM memory, is never written to disk or stored on our servers, and is immediately destroyed after the text results are returned. Google API terms prohibit using this data for model training.
• Rewarded Ads Processing (AdMob SSV): When watching a rewarded ad, the AdMob system sends a secure confirmation via Server-Side Verification (SSV) to add Blue Points to your wallet.
• Google Drive Backup: If you voluntarily enable the backup feature, your database file is encrypted locally and then uploaded securely to your private space on Google Drive.
• Communication and Notifications: We may contact you via your email to send important service updates, security notices, or technical support responses.
• Service Improvement and Development: Analyzing anonymous usage data to understand usage patterns, improve the user interface, and fix bugs.
• Subscription Verification & Anti-Fraud: We utilize your device's time data and NTP time-checks strictly to manage the "Offline Grace Period" (allowing you to use the app without internet for up to 45 days) and to prevent clock tampering or replay attempts designed to artificially bypass subscription renewals or security locks.
• Device Conflict and Session Security: We use your device name, approximate location, and active session logs to monitor for unauthorized access. If simultaneous logins from different devices are detected, our system will automatically manage the conflict by securing the account or terminating older sessions, protecting your license and data.
• Patient Follow-up Web Form Feature: We provide the cryptographic software libraries (in-browser Web Crypto API and local app decryption) to facilitate the secure encryption and decryption of patient forms. FES HealthTech does not collect, access, or utilize any data processed through this feature.
• Nutritional Database Queries (USDA FoodData Central): When you perform an online food search within the Food Bank, the App transmits the generic food name or search keyword (e.g., "oats", "almonds") via secure Firebase Cloud Functions to the official USDA FoodData Central API to retrieve analytical nutritional values. Food search queries contain purely food-related query strings and contain zero patient identifiers, clinical tags, or personal health information.

4 Data Sharing with Third Parties

We share your data with a limited number of trusted services necessary to operate the app, according to the following table:

Service	Purpose	Type of Shared Data	Privacy Policy
Firebase (Google)	Authentication, Subscriptions and Points Management, Analytics	Email address, subscription and points data, anonymous usage data	firebase.google.com/support/privacy
Google Gemini AI (OCR API)	Cloud image processing to extract test results and medications	Test/medication images voluntarily selected by the dietitian (real-time memory processing without storage or training)	ai.google.dev/gemini-api/terms
Google AdMob	Displaying rewarded ads and monetization	Device ID, device data for ad targeting	AdMob Support
Google Drive	Optional encrypted backup	Encrypted database file only (cannot be read without the user's key)	policies.google.com/privacy

In the event of a merger, acquisition, or transfer of commercial assets of FES HealthTech, you will be notified in advance and given the opportunity to delete your account and data prior to any transfer.

5 Patient Data Protection and Geographical Residency

Recognizing the highly sensitive nature of patients' health and financial data, we adopt the highest technical and legal standards for data protection and geographical residency worldwide:

• AES-256 Encryption and Hardware Keystore/Keychain: The local Isar DB database is fully encrypted using the Advanced Encryption Standard (AES-256). Encryption keys are generated and stored locally in the device's secure hardware repository (Keystore on Android and Keychain on iOS), in a completely isolated environment (Zero-Knowledge Architecture). The company holds no cloud encryption keys and cannot decrypt or recover the data in case the device is lost or damaged without a previous backup.
• Local Storage and Global Data Residency: Since all patient data is stored locally ONLY on the dietitian's device within their country, the app voluntarily and autonomously complies with the geographical residency and health data localization requirements set out in global and regional regulations, such as: the General Data Protection Regulation (GDPR) in the EU, the Personal Data Protection Law (PDPL) in Saudi Arabia, the UAE Personal Data Protection Law, and health privacy laws (such as HIPAA frameworks for independent practitioners).
• End-to-End Encrypted Patient Web Form: The Patient Web Form is designed to run entirely client-side using the browser's Web Crypto API. Encryption takes place locally on the patient's device using the dietitian's public key before the file is shared. This ensures that even during transit, the data remains fully encrypted and unreadable by intermediate networks, ISPs, or FES HealthTech.
• OCR Image Processing and Privacy Protection: When the OCR feature is invoked, the selected image is transmitted upon the dietitian's request via an encrypted channel (SSL/TLS) for digital and real-time processing via the API, without any human review and without being saved on the company's servers. Google's privacy terms are enforced, which prevent the exploitation of API data to train models, and the dietitian is always advised to focus the camera on the medical table area and the required numbers.
• Screenshot Prevention and Privacy Mode: Screenshot protection is automatically enabled on sensitive screens, in addition to the "Financial Privacy Mode" feature that obscures numbers and data with a single touch in front of clinic visitors.
• SSL Pinning: The app uses SSL Pinning technology to verify the identity of authorized servers, preventing Man-in-the-Middle (MitM) attacks.
• Offline Security & Anti-Tampering Integrity: When operating in offline mode during permitted offline grace periods, the App utilizes local hardware-backed monotonic time counters to safeguard the cryptographic integrity of local databases. Any detected tampering with the device's clock to artificially prolong offline periods engages an immediate security freeze on local decryption until a genuine online authentication is completed.
• Temporary Local Cache Encryption & Automated Purging: To support local synchronization, secure document exports, and PDF generation, the App temporarily caches encrypted transfer bundles within sandboxed local application directories on the specialist's device. To minimize attack surface and prevent data residue, these temporary artifacts are automatically shredded and purged following defined lifecycles (temporary staging folders within 2 hours, and encrypted backup staging archives within 12 hours).

Device Hardware Permissions Disclosures (Operating System Runtime Controls)

To deliver local clinical functionality and workflows, Murshid requests access to specific hardware capabilities on your mobile device. We strictly adhere to the principle of least privilege, activating permissions only when necessary for user-initiated clinical actions:

Permission	Platform Identifier	Clinical Purpose & Privacy Safeguards
Camera	android.permission.CAMERA NSCameraUsageDescription	Used exclusively for two user-initiated actions: (1) Capturing images of laboratory test tables or prescription sheets for on-demand OCR text extraction; and (2) Real-time scanning of food product barcodes (UPC/EAN) in the Food Bank. Barcode image frames are processed entirely in transient local RAM on your device and are never recorded, cached, or transmitted to company servers.
Microphone / Audio	android.permission.RECORD_AUDIO NSMicrophoneUsageDescription	Used strictly when you voluntarily record verbal clinical memos, audio notes, or consultation dictations within the Clinical Notebook feature. Audio files are saved directly into the sandboxed local application directory on your device. Audio recordings are NEVER uploaded to cloud servers, never processed through external cloud transcription APIs, and never accessible to FES HealthTech or third parties.
Notifications & Alarms	android.permission.POST_NOTIFICATIONS RECEIVE_BOOT_COMPLETED, VIBRATE	Used solely to deliver scheduled patient appointment reminders, clinical follow-up alerts, and subscription renewal warnings. Scheduled alarms are managed locally on your device and do not transmit calendar contents or patient names to external tracking servers.
Local Storage & Files	READ/WRITE_EXTERNAL_STORAGE (Legacy Android)	Used exclusively to allow you to save and export client-side PDF documents (such as meal plans, clinical progress reports, and tax receipts) to your device storage or attach images to patient clinical files. Murshid never inspects, accesses, or scans personal photos or unrelated documents stored on your device.
Biometrics	USE_BIOMETRIC, USE_FINGERPRINT NSFaceIDUsageDescription	Used strictly to allow you to lock/unlock the Murshid application or restrict access to the Financial Privacy screen using Touch ID, Face ID, or Android Biometrics. Biometric authentication is managed entirely by the operating system's hardware secure enclave; FES HealthTech has zero access to biometric data.

6 Backup on Google Drive and Google API Requirements

The Murshid app provides an optional backup feature using Google Drive. Here are the full details and compliance disclosures:

• Completely Optional: The backup feature is disabled by default and you must enable it manually with your explicit consent.
• Encryption Before Upload: The database file is fully encrypted with a key derived from your account data before being uploaded to Google Drive. Even if a third party gains access to this file, they will not be able to read its contents.
• Limited Access Scope (drive.appdata scope): The app requests access only to the app's specific data folder (appDataFolder), which is a hidden folder that does not appear in your Google Drive and cannot be seen by any other app.
• We Do Not See Your Personal Files: The limited scope means the Murshid app cannot under any circumstances see your personal files, photos, or any other content in Google Drive.
• Managing Backups: You can delete the backup at any time from within the app settings or via the app permissions management in your Google account.

7 Advertising and Usage Tracking

The Murshid app uses the Google AdMob service to display rewarded ads that grant you Blue Points for voluntarily watching them. Here is what you need to know:

How do AdMob ads work?

• AdMob uses your device's Advertising ID to target ads based on your interests and app usage.
• AdMob may collect technical data about your device such as its type, operating system, screen resolution, and approximate location (at the city level).
• Your patients' data is never transmitted to AdMob and is not used in ad targeting.

How to turn off personalized ads?

• On Android: Go to Settings → Google → Ads → select "Delete advertising ID" or enable "Opt out of Ads Personalization".
• On iOS: Go to Settings → Privacy → Tracking → turn off "Allow Apps to Request to Track".

Firebase Analytics

We use Firebase Analytics to analyze app usage. You can turn off analytics from the app settings at any time. All Firebase Analytics data is anonymous, aggregated, and not linked to your personal identity.

HTML5 LocalStorage Disclosures (Web Platforms & Portals)

Our public web properties, specialist Bio-Sites, and the Verification Portal (/verify/) do not deploy commercial tracking cookies, third-party advertising cookies, or cross-site tracking scripts. We utilize standard, strictly necessary HTML5 LocalStorage purely to retain functional client-side user interface preferences:

• Language Preferences (murshid_lang, murshid_verify_lang): Stored locally in your browser to remember your chosen interface language (Arabic or English) across page visits and reloads.
• No Tracking & Zero Cross-Site Sharing: These local storage values contain zero personal identifiers, browsing history, or biometric data, and are never transmitted to third parties, advertising networks, or analytics providers.
• User Control: You can clear your browser's LocalStorage at any time via your browser settings without affecting the core accessibility of our web pages.

California Do Not Track (DNT) & Global Privacy Control (GPC) Signals

California law (CalOPPA and CCPA/CPRA) requires operators of websites and online services to disclose how they respond to "Do Not Track" (DNT) signals. Because FES HealthTech web properties, specialist Bio-Sites, and the Verification Portal do not track visitors across third-party websites or engage in cross-context behavioral advertising, our websites do not alter their behavior upon receiving automated browser DNT signals or Global Privacy Control (GPC) signals. We do not sell or share personal information with third parties for cross-context behavioral advertising.

8 Privacy of Public Specialist Bio-Sites, Verification Portal, and Abuse Reporting

To support independent dietitians and specialists in showcasing their practice, the Murshid platform enables specialists to publish public digital clinics and bio-sites (accessible via URLs such as https://murshid.feshealthtech.com/p/:slug) and issue cryptographically verifiable clinical documents. This section outlines how we handle privacy, data flow, and telemetry for visitors of these public sites, verification portal users, and individuals submitting reports:

A) Public Bio-Site Visitors — Zero Behavioral Profiling & Minimal Telemetry

When public visitors, prospective clients, or patients browse a Specialist Bio-Site:

• No Tracking Cookies or User Profiling: We do not deploy third-party advertising cookies, cross-site behavioral trackers, canvas fingerprinting, or marketing profiling scripts on public Specialist Bio-Sites. Visitors browse freely without tracking across the web.
• Transient Edge Infrastructure Telemetry: Like any standard web infrastructure, our hosting environment (Google Cloud / Firebase Hosting edge nodes) processes minimal, transient technical request headers (such as incoming IP address, browser user-agent, and request timestamp) solely for low-level DDoS mitigation, edge caching, server health, and network security. These technical logs are transient and are never linked to personal health or user identities.
• No Collection of Visitor Clinical or Health Data: Browsing a Specialist Bio-Site does not collect or transmit medical or clinical information to FES HealthTech. The page is purely an informational directory and practice showcase.

B) Voluntarily Published Specialist Data

Information displayed on a Bio-Site (such as professional name, title, clinic location, contact numbers, WhatsApp links, services, prices, and public testimonials) is content voluntarily configured and published by the specialist. Specialists retain complete autonomy through their Murshid App dashboard to edit, conceal, or completely unpublish their Bio-Site in real time.

C) Third-Party Outbound Links & External Channels

Specialist Bio-Sites may contain interactive links directing visitors to external platforms (such as direct WhatsApp chats, Instagram, Google Maps, or external payment gateways). Clicking any external link transfers the visitor to the corresponding third-party platform governed by its respective terms and privacy policies. FES HealthTech has no control over and assumes no responsibility for third-party privacy practices or external communications.

D) Abuse & Violation Reporting Privacy (Trust & Safety)

Every public Bio-Site includes an abuse reporting mechanism allowing visitors and authorities to report prohibited or misleading content. When a report is submitted:

• Data Collected: We collect only the reported page slug/URL, the selected category of violation, explanatory notes submitted by the reporter, and optional contact details (such as email or telephone) if voluntarily provided by the reporter for follow-up.
• Strict Reporter Confidentiality: All reports and reporter identities are treated as strictly confidential. FES HealthTech will never disclose the reporter's personal identity or contact details to the reported specialist.
• Administrative Storage & Access: Violation reports are stored in secure administrative cloud collections accessible exclusively by authorized FES HealthTech trust and compliance personnel with multi-factor authentication, solely for investigating violations and enforcing moderation decisions.

E) Official Document & Specialist Credential Verification Portal (/verify/)

The Murshid Verification Portal allows patients, clinical partners, and institutions to verify the cryptographic authenticity of meal plans, certificates, and specialist credentials. When querying the Verification Portal:

• Zero Clinical Data Transmission: The verification engine only receives and processes cryptographic hashes, Ed25519 digital signature payloads, and issued document metadata (such as document ID, issuance timestamp, and verification status). The private clinical contents, diagnostic narratives, and patient notes remain strictly local on the specialist's device and are never ingested, reconstructed, or stored by the verification server.
• Display of Verified Specialist Credentials: For verified records, the portal presents authorized public verification details of the issuing specialist (e.g., Verified Specialist Name, Professional Title, and Verification Badge) to assure the public against fraudulent impersonation and uncertified practice.
• Abuse Prevention & Cryptographic Rate Limiting: Minimal operational telemetry (transient IP headers and Firebase App Check attestation tokens) is evaluated in real time solely to enforce query rate limits and defend against automated cryptographic brute-force scraping.

9 User Rights and Global Regulations

This policy guarantees you all the rights stipulated in international data protection legislation (such as GDPR, CCPA, PDPL, etc.) regarding your personal data:

• Right to Access: You can at any time view all the data we hold about you through your account settings within the app.
• Right to Rectification: You can update and correct your professional profile data directly from within the app at any time.
• Right to Data Portability: The app provides a feature to export your professional profile reports and logs in readable and usable formats.
• Right to Erasure (Right to be Forgotten): You can request the permanent and direct deletion of your account and all your cloud data via the Data Deletion Request page.
• Right to Withdraw Consent: You can at any time revoke the app's access to your Google or Google Drive account through your Google account security settings.

Data Protection Officer (DPO) & Patient Request Limitation

FES HealthTech has designated a Data Protection Officer (DPO) to handle inquiries regarding the personal data of dietitians (accounts, subscription billing, and points history). You can contact our DPO team at privacy@feshealthtech.com. Please note that since FES HealthTech has zero access to patient data, we are legally unable to process or fulfill any requests for access, rectification, portability, or deletion submitted directly by patients. All patient data inquiries must be addressed directly to the treating dietitian who acts as the Data Controller.

App Store Privacy Disclosures Mapping (Google Play & Apple App Store)

For transparency during application store reviews, the data collected from the dietitian maps directly to the following official store privacy categories:

• Contact Info: Email address (Used for authentication; Linked to User).
• Purchases: Points balance and subscription transaction history (Used for account management; Linked to User).
• Usage Data: Screen navigation and session durations via Firebase Analytics (Used for diagnostics and analytics; Not Linked to User).
• Diagnostics: Crash logs and performance metrics via Firebase Crashlytics (Used for app optimization; Not Linked to User).
• Identifiers: Device ID and model (Used strictly for session security and anti-fraud management; Linked to User).

10 Data Retention and Deletion

We commit to retaining data only for the necessary period, according to the following policies:

Data Type	Retention Period	Upon Deletion Request
Account Data (Firebase Auth)	For the duration of account activity	Permanent deletion within 30 business days from request date
Professional Profile (Local Isar DB)	Under your full control on your device	Never uploaded; deleted upon clearing app data
Patient Data (Local Isar DB)	Under your full control on your device	FES HealthTech does not possess or control it
Specialist Bio-Site Content (Cloud Firestore)	For the duration of active publication	Immediately hidden upon unpublishing; permanently deleted within 30 business days upon account deletion
Document Verification Records (Public Cloud Firestore)	For the duration of active document validity or specialist account tenure	Revoked immediately upon specialist request; permanently deleted within 30 business days upon account termination
Web LocalStorage Preferences (Browser Cache)	Until browser storage is cleared by user	Stored purely client-side; zero retention on company servers
Abuse and Violation Reports (Cloud Firestore)	Up to 24 months for trust, safety, and legal compliance auditing	Archived and securely purged following compliance review cycles
Gold/Blue Points Balance (Firestore)	For the duration of account activity	Permanently deleted with the account (non-recoverable)
Usage Data (Firebase Analytics)	Max 14 months (Google Policy)	Auto-deleted after the period ends
Google Drive Backup	Until manually deleted from your account	Can be deleted anytime directly from the App Data folder settings in your Google account (the company has no access post-account deletion)

To submit an official data deletion request, please visit the Data Deletion page or contact us via email at privacy@feshealthtech.com.

11 Privacy of Minors

The Murshid app is designed exclusively for use by qualified adult dietitians aged 18 years or older. This app is not directed at minors and they are not permitted to use it directly.

Regarding data of minor patients (patients treated by the dietitian, including any minor patient who fills the Patient Follow-up Web Form), that data falls under the full responsibility of the registered dietitian, subject to child health data protection laws applicable in the respective country. The dietitian is obligated to ensure proper legal consent is obtained from parents or guardians before sending the form link or processing minor patients' data.

12 Policy Updates

We may update this policy from time to time to reflect changes in the service, new legal obligations, or improved privacy practices. We commit to the following:

• Prior Notice of Material Changes: If we make any material modifications affecting how data is collected or used, you will be notified via an in-app notification and/or email 30 days before the changes take effect.
• Date of Update: We always retain the last updated date at the top of this page so you can know when the policy was last reviewed.
• Implied Consent: Your continued use of the app after being notified of changes constitutes implied consent to the updated version of the policy.
• Right of Refusal: If you do not agree to the material changes, you have the right to delete your account and data before the new policy takes effect, following the deletion procedures outlined in Section 10.

Governing Language & Prevailing Version

This Privacy Policy is prepared, executed, and published in the English language. In the event of any conflict, discrepancy, ambiguity, or divergence between the English text of this Privacy Policy and any translation into Arabic or any other language, the English language version shall exclusively govern, control, and prevail in all legal, administrative, regulatory, and arbitral proceedings worldwide.

It is recommended to review this policy periodically for the latest version. You can always find the newest version at this link: privacy-policy.html.

13 Contact Us

If you have any inquiries, questions, or concerns regarding this privacy policy or how we handle your data, we are here to answer:

To submit official data deletion requests, please use the dedicated Data Deletion page, as it ensures a faster and more efficient processing of your request.

If you do not receive a response from us within 7 business days, please resend your email and ensure the word "Privacy" is included in the subject line to help route it to the relevant department faster.

• Owning Company: FES HealthTech
• Email: privacy@feshealthtech.com
• Data Deletion Page: data-deletion.html
• Terms of Use: terms-of-use.html