Privacy Policy

1. Who is responsible

The operator uses the Brainfish AI brand for this pre-release project. A verified legal entity name, business address, and governing jurisdiction have not been supplied. Those facts must be added before a broader commercial launch; this policy does not invent them.

Privacy questions and rights requests can be submitted through the working privacy-request form on this site. No unverified email address is published.

2. Information the website collects

• Early-access and contact forms collect your name, work email, company, optional role, selected workflow, message, and an optional marketing preference.
• The privacy-request form collects your name, email, optional company and role, request type, and details needed to locate and handle the request.
• The forms do not accept file uploads. Visitors are instructed not to submit passwords, API keys, production records, sensitive personal data, or confidential attachments.
• The hosting layer may process network data such as IP address, request time, browser information, and security logs to deliver and protect the site.

3. Why the information is used

Submission details are used to review and respond to the request, assess potential pilot fit, keep a record of the conversation, prevent misuse, and handle privacy rights. Optional launch updates are sent only when the separate marketing choice is selected. A contact request is not treated as marketing consent.

4. Storage and access

Form submissions are stored in a private, Sites-managed Cloudflare D1 database bound to this deployment. The public application exposes a write-only form endpoint and no public list or read endpoint. Access is limited to authorized project operators through the hosting environment.

This website does not send submission contents to an AI model, email-delivery provider, CRM, analytics service, payment processor, or advertising network. No product credentials, connected-system data, or agent traces are collected by this marketing implementation.

5. Retention

No automated deletion schedule is configured for website submissions. Records are kept while the request is assessed, while a conversation remains relevant, or as reasonably needed for security and recordkeeping. You may request deletion through the privacy-request form. The operator should formalize a retention schedule before a larger public launch.

6. Cookies and browser storage

The Brainfish AI site code does not set analytics, advertising, or preference cookies and does not store form data in localStorage or sessionStorage. A hosting access layer may use strictly necessary authentication or security technologies when the site is private. See the Cookie Notice for the current implementation.

7. Sharing and international processing

Submission data is processed by the hosting infrastructure needed to run the site and database. We do not sell form data or share it for advertising. Because the operator’s legal location and final product infrastructure are not verified, this site does not claim a specific data-residency region or international-transfer mechanism. Those facts must be settled in any pilot agreement.

8. Your choices and requests

• Ask for access to, correction of, or deletion of information you submitted.
• Object to or ask to restrict how a request is handled.
• Withdraw optional marketing consent without affecting the underlying contact request.
• Request information about the processors used by this marketing site.

9. Future product processing

The proposed Brainfish AI product may, under a separate pilot agreement, process company data, operational instructions, business rules, connected-system records, credentials, action requests, and approval records. None of that processing is activated by using this marketing site. Any pilot must define source access, processor roles, model providers, security, retention, deletion, and human approval controls before connection.