Privacy
Nexus handles contact and mission information as project data: only for a defined purpose, inside controlled storage and with access limited to the people responsible for the request.
1. Information submitted through the website
When somebody starts a mission discussion, applies for the private beta, proposes a capability, contacts Nexus about software integration or asks to work with the team, the website may store the information supplied in the relevant form. A beta application can include contact details, company and role, country, company description, selected mission, systems involved, preferred authority, AI provider, AI usage route, budget range and onboarding notes.
2. Why the information is used
The information is used to understand the request, evaluate a beta mission, choose an appropriate AI and credit route, route the application to the responsible Nexus project owner, answer the sender, organise onboarding and preserve the context needed to continue that discussion.
3. Mission and project information
Information shared during a Nexus project is handled according to the project boundary and authority defined for that work. Project rules, resources, decisions, evidence and mission history remain associated with the relevant project rather than being treated as general public information.
4. Storage and access
Website contact submissions and beta applications are stored in private server-side queues. Access is limited to people responsible for Nexus operations, the relevant project or the requested partnership. The public website does not display submitted contact information.
5. Retention
Contact and project information is retained for as long as it remains necessary for the conversation, company administration, security, project continuity or legal obligations. Information that no longer has a valid operational purpose can be removed from active storage.
6. Technical data
The server may process normal request information required to deliver and protect the website, such as timestamps, requested pages, browser information and security events. This information is used for operation, diagnostics and abuse prevention.
7. Cookies and local storage
The website uses a secure session cookie for form protection, multi-step beta application state and temporary form recovery. The site does not require advertising cookies for its core operation.
8. AI provider and credit preferences
The beta form records the preferred AI provider and usage route, but it must not be used to submit API keys, passwords or provider credentials. Those details are connected only after acceptance through the controlled onboarding process. Selecting Nexus-managed credits allows the team to prepare a funded usage profile and agreed limit for the beta workspace.
9. Sharing
Contact or project information is shared only where it is necessary to operate the relevant Nexus project, provide infrastructure, protect the service, meet a legal obligation or follow the sender’s explicit instruction.
10. Requests about personal information
Questions about stored contact information, correction or deletion can be submitted through the Nexus contact form. Include enough information for the team to identify the relevant request safely.
11. Security
Nexus applies project boundaries, limited access, server-side storage, form protection and operational logging to the website. The wider product uses the same principle: capability, authority, evidence and human decisions remain distinct.
Website privacy information · Version 3.3.0 · August 2026