BrightNTech

Privacy Policy

Website journey measurement and owner access

On the investor and public discovery guide pages, first-party journey events record page paths, survey steps, technical failure categories and server-confirmed submission outcomes. A first-party session cookie groups activity for 30 minutes of inactivity. Journey events contain no email address, survey answers, verification codes or form text. We retain these event files for 30 days and prune them during later activity. We honor Do Not Track and Global Privacy Control for this measurement. The report is available only to the named owner through mailbox-verified passwordless access provided by Bright Identity. These observations help diagnose the website journey and are not used for marketing profiles.

Investor interest enquiries

If you complete the investor survey, we store your stated mandate, contact details, consent and rule-based profile-context and engagement scores for internal investor research and human review. Optional thesis, proof-threshold and objection wording is preserved with its submission reference and source date in an internal research corpus. We do not publish those responses or infer personal psychological traits. Scores do not determine investment eligibility or establish a commitment. We send a receipt and use your requested next step to guide follow-up. Marketing updates require separate permission. You can request access, correction or deletion through our contact form.

The survey accepts professional email addresses only. To confirm the address belongs to you, we email a 6-digit one-time code that expires after 10 minutes and can be used once. We keep only keyed cryptographic fingerprints of the code and address (never the code itself) plus timestamps and attempt counts, and purge them during later verification activity once they are more than 24 hours past expiry. Your response records the time the address was verified.

At BrightNTech, privacy is treated as a design constraint. We collect only the data required to process requests, execute licensed workflows, and deliver contractual communications.

Form submissions capture consent metadata and traceability identifiers (submission token, license request ID/number, contract IDs). These records are retained for legal, security, and audit requirements.

Records are persisted in append-only JSONL/Blob storage and synchronized to normalized PostgreSQL tables when configured. Access is restricted to authorized personnel and governed by least-privilege controls.

You can request access, correction, or deletion where legally permitted. For privacy and legal inquiries, use our contact form.