L2Privacy Policy
How information is handled in V1.
This policy separates the current memory-only frontend from services that may be introduced later.
- Effective
- 27 July 2026
- Last updated
- 27 July 2026
- Version
- 1.0
1. Scope and current status
This Privacy Policy explains information handling for noeTrace.
noeTrace is currently a pre-launch product in Australia. Verified operator and legal contact details will be published before production account, data-storage, or payment services become available.
2. Information you provide
The current frontend can receive name and email fields, onboarding answers, markets followed, competence and exploration areas, custom research areas, assistance requests, research prompts, watchlist choices, and other research context.
In the current pre-launch shell, Auth and onboarding fields are kept only in browser memory for the active interface session and are not sent to an account service. Passwords are not persisted. A future backend may process account credentials, support communications, watchlists, and saved research only after this policy is updated and the relevant service is connected.
3. Information collected automatically
noeTrace does not currently add analytics, advertising trackers, device fingerprinting, or tracking pixels. A boolean sidebar interface preference may be stored in a cookie when that component is used.
The Lovable editor error hook is limited to local development and receives a sanitised message. Production server diagnostics are designed to emit a scoped identifier and generic error text rather than user research, credentials, or raw error payloads.
Hosting infrastructure may process ordinary request information such as IP address, time, and browser request metadata to deliver and secure the site. The production host’s exact telemetry and retention must be verified before deployment.
4. Why information may be used
- provide and secure the requested service;
- create and manage accounts when production accounts become available;
- maintain the research context requested by the user;
- improve reliability and respond to support requests;
- prevent misuse; and
- comply with legal obligations.
5. AI and model providers
No AI or model provider currently receives user content from this frontend. If AI processing is activated later, user prompts and relevant research context may be sent to configured providers to generate outputs.
Before activation, this policy must identify processor categories, relevant cross-border handling, and verified retention terms. noeTrace will not claim that a provider never retains data unless that is contractually verified.
6. Service providers and data sources
Future service providers may include identity and Auth providers, hosting, payment, AI/model, and market or news data vendors. Providers will be named when active and appropriate. No analytics provider is currently connected.
The public site intentionally requests font styles and files from Google Fonts. Those hosts may receive ordinary request metadata; no user-entered research text is included in font requests.
7. Cross-border processing
Future providers may process information outside Australia. Actual locations and safeguards must be confirmed and this policy updated before such processing is activated. No data-residency guarantee is made.
8. Retention
Information should be retained only as long as reasonably required for the stated purposes and legal obligations. Current memory-only onboarding and profile state ends with the relevant browser session or page lifecycle.
Documented retention schedules must be established before production backend storage begins.
9. Security
Reasonable technical and organisational safeguards should be used in proportion to the service and information involved. No internet service can guarantee absolute security.
10. Choices and rights
Depending on applicable law and the service stage, users may request access, correction, deletion, account closure, or make a privacy complaint through a verified published contact. Automated self-service controls are not currently claimed.
No marketing preference or consent is collected in the current shell.
12. Children
noeTrace is not knowingly directed to children. A legally reviewed age threshold has not been invented for this pre-launch policy.
13. Questions and complaints
Verified privacy and legal contact channels are not yet published. They will be added before production accounts or persistent user-data services become available. Once published, privacy questions and complaints can be made through the Contact page.
14. Updates
This policy will be updated when information handling, providers, jurisdictions, or product capabilities materially change. The deliberate effective date, last-updated date, and version appear above.