Privacy Policy
Draft dated October 8, 2026. These pages are being prepared for review. They are not final legal terms or a completed privacy notice.
Who is responsible
This is a draft notice for Launch Axis. The operator's legal name, address, privacy contact, and effective date have not been finalized. An organization using the platform may have separate responsibilities for the information it collects from its members. The final notice must explain these roles and provide the relevant contact details.
Information used by the service
Information may include account and contact details; organization roles and applications; company and founder profiles; preferences and consent choices; documents and messages you provide; meeting and service-request records; and security, access, and usage events. The features you use determine what is collected. Avoid including unnecessary sensitive personal information or information you are not authorized to share.
Why information is used
The proposed purposes are to create and secure accounts, manage organization participation, save company information, provide requested collaboration features, respond to support requests, and keep records of authorized changes. Optional processing, AI features, and communications require separate choices where applicable. The operator must confirm and document the legal basis for each purpose before production use; this draft does not treat all processing as consent-based.
Visibility and recipients
Membership and permissions determine which organization records a person can access. Private documents and conversations require their own access rules; an administrative or platform role is not blanket permission to view them. Public summaries or listings should be visible only after the applicable publication steps. The final notice must identify hosting, authentication, storage, communications, AI, and other providers actually used, the information each receives, and any required disclosures.
AI and document processing
Saving a profile or uploading a file does not by itself mean that AI analysis, text extraction, or external processing has occurred. Where an AI feature is enabled, explain what information will be sent, the provider involved, and the applicable data handling terms before use. Provider retention and model-training practices must be confirmed before activation; this draft makes no unverified promises about them.
Cookies and preferences
The application uses session cookies for sign-in and an organization-selection cookie to remember the chosen workspace. It may store interface preferences, such as theme, on your device. The operator must review the deployed site's actual cookies and any analytics before publishing a final notice and obtain any consent required for optional tracking.
Retention and security
The final notice must specify retention periods or clear criteria for account records, business content, communications, usage records, security logs, and backups. Account deletion and revoked access are different: removing access does not necessarily delete a record. Access controls and other safeguards reduce risk, but no system can promise absolute security. Recovery, deletion, and incident-response procedures must be confirmed for the deployed service.
Your choices and requests
You can review the information you enter and change available optional consent choices. Depending on the laws that apply, you may have rights to access, correct, delete, restrict, object to processing, obtain a copy of information, or withdraw consent. The final notice must give a working request channel, explain identity checks and response procedures, and identify the appropriate complaints authority. Withdrawing consent does not automatically undo earlier lawful processing.
Locations, transfers, and children
Before production use, the operator must identify the countries where information is processed and any safeguards required for international transfers. The service is intended for business participation; the final policy must state an age and eligibility rule appropriate to the intended audience and applicable law. Do not use this draft as a statement of compliance with any particular jurisdiction.
Changes and contact
Material changes to data practices should be explained before they take effect where required. Complete the operator and privacy contact details, retention schedule, provider list, transfer arrangements, legal bases, request process, and effective date before treating this notice as final. The draft is not a substitute for a published contact channel.