Cookie Policy

Draft for review — not yet effective. Prepared on 2026-10-17. This draft describes observed browser-storage features; the production inventory and responsible companies must be confirmed before a final version takes effect.

Scope and responsibility

This draft concerns cookies and similar browser storage on the website. COREBYTE TECHNOLOGY PTE. LTD. in Singapore and BYTEBAY GLOBAL LIMITED in Hong Kong are peer entities. The company responsible for each storage or tracking activity must be confirmed; this draft does not treat either company as the sole operator or assume that both receive the same data.

Browser storage, information submitted to the inquiry service and data held by hosting or email providers are separate matters. The Privacy Policy draft addresses the inquiry records and unresolved production-processing arrangements.

Temporary drafts in the implementation prepared for publication

The form code prepared for publication uses sessionStorage to save a temporary inquiry draft in the browser. The draft may contain your name, work email, message and any company, phone, market, cloud-setup or budget details you enter. If one has been generated, the draft may also include a technical key used to help avoid duplicate submissions. Do not enter passwords, API keys, production credentials or unnecessary sensitive records.

Saving this browser draft does not by itself submit the inquiry. Draft recovery can help preserve entries when switching website language. The design preview disables the form and does not activate its draft-saving functionality.

Expiry checks and successful submission

The form applies a 30-minute expiry check measured from the most recent draft save. It rejects an expired draft when restoring it and schedules browser-side clearing. It also clears the draft after an accepted submission. Browser suspension, restoration and storage settings can affect when code runs; this is an application expiry mechanism, not a guarantee of deletion at an exact instant.

The 30-minute check does not set a retention period for server inquiry records, management notes, email copies, logs or backups. Clearing a browser draft does not remove a record already accepted by the server. A draft is also not evidence that a submission succeeded.

What the reviewed frontend shows

The reviewed frontend source uses local font and asset paths. The review found no analytics integration, embedded iframe, localStorage use, document.cookie write or sendBeacon call in that source. These are source-level observations, not a statement that every live response or infrastructure component is free of tracking or browser storage.

Production CDNs, proxies, hosting responses, external destinations and later integrations may introduce different behaviour. Their cookies, storage, network requests and purposes must be inventoried before a final policy takes effect. No claim of a complete production tracking audit is made here.

Your browser choices

You can use your browser's site-data controls to inspect, block or remove browser storage. Blocking storage may prevent draft recovery or preservation across language changes. Browser controls and restoration behaviour vary; use the instructions for your browser.

Removing site data does not delete submitted inquiries or mail copies. If you follow an external link, the destination's storage practices and controls need to be considered separately. This draft does not describe a consent preference centre or a tracking opt-out control that has not been implemented.

Final review and contact details

The final version needs a confirmed inventory stating the responsible company, purpose, storage type, duration and recipients for each production mechanism, together with any applicable consent or choice requirements. These details remain subject to review and confirmation.

For browser-storage questions, use the existing website inquiry contact, info@bytebay.ai. This draft does not specify a response deadline or establish a server-side deletion procedure.