A cookie and device-storage review draft. The deployed-site inventory and any consent requirements are not yet confirmed.
Read draftThis is an original review draft, not an effective policy, a service agreement or legal advice. The operator must confirm the open points and approve a final version before activation.
No effective date has been assigned. Reading this draft does not mean accepting it.
This document is for operator review. It is not an effective cookie policy or legal advice. It does not assert that SeekDoctor uses no cookies, nor does it identify an approved list of cookies. No effective date has been assigned.
SeekDoctor is the service name on seekdoctor.net. The registered operator's identity remains to be confirmed. The final policy must describe the actual deployed website, not a competitor's technology or a development preview alone.
A cookie is a small value that a website can ask a browser to retain and send with later requests. Websites can also use local storage, session storage or similar browser features. A server may receive request information without setting a cookie.
These are general explanations, not a declaration that each technology is active on SeekDoctor. The operator's inventory needs to cover more than visible cookie names and should distinguish device storage from server-side collection.
The inspected site source did not reveal an authored cookie-consent banner or explicit cookie, local-storage or session-storage routines in the reviewed application files. That is a limited code-review observation, not a deployed-site cookie audit.
Hosting features, platform-injected scripts, response headers and third-party resources may behave differently on a deployed site. This draft does not declare a particular analytics or marketing product active. No tracking script or consent system was introduced when these draft pages were prepared.
The operator needs to inspect the live site's requests, response headers and browser storage across representative pages and actions. Checks should include a fresh browser session, later visits and any existing choice controls.
For each observed item, record the following before turning this draft into a policy:
A final inventory may distinguish items required for a requested feature from preference, measurement or advertising items. A category must follow the observed purpose, not a label borrowed from another site.
The names of an analytics provider, payment service or marketing platform should be added only if the site's actual configuration confirms them. These contact-only draft pages contain no payment flow. This does not settle what another part of the deployed platform may collect.
Browsers commonly let people inspect, clear or restrict cookies and other stored site data. The available settings depend on the browser and version. Restrictions can affect a feature that actually relies on storage; the operator must identify such features before describing any impact for SeekDoctor.
This draft does not promise an operational consent banner, category switches, a reject button or a remembered withdrawal choice. The operator must first establish which controls exist and whether consent or another legal requirement applies to each item. A policy statement cannot replace a functioning control.
The inventory should cover resources and services used by the deployed site, including any platform-injected functionality. A visible page or a source-file scan does not establish the complete recipient list or every storage action.
The built-in enquiry mechanism stores form submissions and notifies the workspace owner. That mechanism is distinct from a browser cookie inventory. Information about contact-only enquiries and unresolved data handling appears in the privacy review draft.
A new embed, integration or tracking configuration can change device-storage behaviour. The operator needs a process for rechecking the inventory when those features change, and for keeping any required controls consistent with the final policy.
No refresh interval, consent expiry period or retention timetable has been confirmed. The operator must approve the actual inventory, control behaviour and final text together before assigning an effective date.
For questions about the draft, the confirmed operator contact is 18309180000@139.com, +86 18309180000, Xi'an, China. Do not send clinical files or payment information with a cookie question.
The published flag must remain off until the operator confirms the unresolved configuration and approves a final policy. This draft does not change browser settings or activate any tracking.
These are open decisions, not statements of an approved procedure or a legal compliance assessment.
Keep this policy unpublished. Activation needs separate operator approval of the completed final version.
