Privacy Policy

Draft for review — not yet effective. Prepared on 2026-10-17. This draft describes the website features reviewed for drafting and identifies matters that must be confirmed before a final version takes effect.

Scope and responsible companies

This draft concerns information provided through the website's inquiry and account-request forms. It does not describe the processing arrangements of a separately purchased cloud service, model API or customer project.

COREBYTE TECHNOLOGY PTE. LTD. in Singapore and BYTEBAY GLOBAL LIMITED in Hong Kong are peer entities. The company responsible for website operation, decisions about personal data, inquiry handling and any related contract or payment must be identified for each activity before a final notice takes effect. This draft does not assign those roles to a single company or assume that information is shared between the two.

Information requested by the forms

The sales inquiry form requires a name, work email and message. Company information is optional for sales inquiries but required by the account-request form. Phone contact, target market, current cloud setup and budget are optional. The inquiry service can also accept a use-case description from an earlier form version.

Provide only information you are authorised to share and that is needed to explain your inquiry. Do not include passwords, API keys, production credentials, unnecessary sensitive personal information or other customers' records. You can leave optional fields blank; without the required information, the form cannot complete its normal submission process.

Purpose and your submission choices

The forms are intended to support assessment of service needs and follow-up about an inquiry or account request. Additional uses, including marketing or forwarding information to a model provider, would need to be identified and reviewed before being included in a final notice; they are not inferred from the existence of the form.

The design preview disables form submission. The implementation prepared for publication is configured to send a submitted inquiry to the website's /api/inquiries service. A browser draft alone is not a submitted inquiry. You may choose not to use the form and address a question to the existing website inquiry contact, info@bytebay.ai.

Inquiry records and possible email notifications

The reviewed backend saves an accepted inquiry with a request reference and an acceptance time recorded in UTC. Its private management functions can also retain status, notes, follow-up dates and an audit history. Marking a record resolved changes its status; it does not delete the original inquiry.

Email notification is disabled by default in the reviewed service and can be configured separately. If enabled, the notification can include the full inquiry text and contact details. The actual production setting, recipients, email provider and processing locations have not been verified for this draft. A server receipt, an attempted notification and receipt or reading of an email are separate events.

Retention and production arrangements to confirm

The reviewed service documentation specifies no automatic deletion schedule for server inquiry records. The browser draft's 30-minute expiry check is a separate feature and is not a server retention period. Before a final notice takes effect, retention and deletion rules must be confirmed for inquiries, management records, mail copies, logs and backups, including how a deletion request would be handled.

The production hosting and notification providers, storage and processing locations, authorised recipients, access arrangements and relevant legal grounds also require confirmation. A review of frontend source does not establish the logging or tracking behaviour of a live CDN, proxy or hosting service. See the Cookie and Browser Storage Policy draft for the observed browser-storage behaviour.

Questions and requests

Use info@bytebay.ai, the existing website inquiry contact, to raise a privacy question or ask about access, correction or deletion of information you submitted. Include an inquiry reference if available, but do not send credentials or unnecessary sensitive material.

Before the final version takes effect, the responsible privacy contact, identity-verification procedure, applicable rights and limitations, and handling process must be confirmed. This draft does not promise that every request can be granted or specify a response deadline.