Legal / privacy

Privacy Policy

Last updated August 7, 2026

1. Scope and controller contact

This notice covers the NeuBlink website, the synthetic demo and the discovery-request form. NeuBlink Solutions is the business responsible for reviewing website requests. For privacy questions, access, correction or deletion requests, email hello@neublink.com. This notice is not legal advice; customers should confirm their controller/processor roles and sector obligations in the applicable statement of work.

2. Information collected

The discovery form may collect your name, work email, company, role, phone or WhatsApp number, company size, industry, selected workflow, problem description, approximate monthly volume, preferred contact method, budget range, timeline, consent, source and UTM campaign fields. Do not send credentials, customer records or other sensitive production data through the form.

Cloudflare and the Worker may process request metadata such as IP address, country, timestamp, user agent and request identifiers for security, rate limiting and troubleshooting. IP address and similar identifiers are treated as personal information where applicable.

3. How information is used

  • To assess fit, reply to a request and provide discovery or implementation next steps.
  • To prevent abuse, detect duplicates, rate-limit submissions and investigate failures.
  • To understand aggregate funnel activity when analytics is enabled. UTM parameters may be stored with a request.
  • To process payments only if a separately approved payment flow is enabled; payment records are not collected by this form.

4. Service providers and data flows

Website hosting and edge security are provided through Cloudflare. When configured and approved, the Worker stores an intake record in Cloudflare KV for up to 30 days and sends the request during the form submission to a configured Google Apps Script or other approved delivery endpoint. Records include a delivered or failed delivery status; failed requests are returned as an error and are not presented as received. Error records, if enabled, may be retained for up to 30 days. If Paystack is enabled for a payment flow, payment records may be retained for up to 365 days for reconciliation.

Analytics and advertising scripts are optional configuration, not a promise that every provider is active. Local development may save a test request in that browser’s local storage; that is not an operator delivery path. A production intake response means the approved delivery endpoint confirmed the request; it does not mean a person has read it.

5. Retention and deletion

Retention periods are described above and may be shortened by operational cleanup. A customer-specific SOW may define different retention, deletion, export, residency or subprocessor requirements. Email hello@neublink.com to request access, correction or deletion. We may need to verify the requester and retain limited records where required for security, accounting or legal obligations.

6. Security and transfers

NeuBlink uses HTTPS, platform-managed encryption where supported, secrets outside source control, input validation, rate limiting and bounded provider timeouts. Controls are reviewed against the workflow and data boundary. No ISO 27001, SOC 2, HIPAA, PCI DSS or other certification is claimed. Cloud and provider regions or international transfers are reviewed during customer procurement.

7. Changes

We may update this notice as the website, providers or retention controls change. The date above indicates the current version.

8. Contact

Privacy and security contact: hello@neublink.com.