An interim notice, not a hidden identity.
The name Swovee refers here to the project and its published concept materials. A verified operating legal entity, registered address, privacy officer, representative and monitored privacy email have not yet been published. This page does not invent them.
Do not submit confidential, regulated, export-controlled, health, financial or otherwise sensitive information through this website. A complete notice and verified contact channel must be published before a real registry or upload workflow opens.
No account. No checkout. No live pilot intake.
The current site provides no account, checkout, submission form, parcel upload or live pilot intake. Pilot links lead only to the published program path, which explains what must be established before applications can open. Because there is no entry surface, the project does not intentionally collect or store information entered by a visitor.
The current project source does not configure advertising analytics, behavioral profiling, a customer database, payment processing or a parcel-upload service. If any of those capabilities are added, this notice must be revised before use.
Progress stays on this device.
Swovee Simulator V1 runs its gameplay in the browser. It has no gameplay account, telemetry stream, network upload or leaderboard. The gameplay logic does not send a player's routes, events, scores or debrief to Swovee.
If browser storage is available, the simulator uses the localStorage key swovee.simulator.progress.v1 to store only three progress values: best score, total credits and completed-run count. The simulator's Reset local progress control removes that key and resets those values. Play can continue if local storage is unavailable.
A debrief JSON file is assembled locally from the current run and downloaded through the browser only when the player chooses the download control. It is not automatically uploaded. After download, the file remains wherever the player's browser or device saves it.
The simulator page and its static assets still require ordinary website delivery. Hosting infrastructure may process the request data described in the next section; that is separate from gameplay telemetry or debrief upload.
The hosting layer may still see a request.
Like most public websites, hosting, network and security providers may process technical request data needed to deliver and protect pages. Depending on provider configuration, that can include an IP address, timestamp, requested path, device or browser information and security events.
A verified vendor list, retention schedule, processing locations and contractual role allocation have not yet been published. Until they are, this notice does not claim a specific legal basis, retention period or international-transfer mechanism.
Links to external standards and agencies lead to independent websites governed by their own notices.
A right to enter is not a right to keep everything seen.
A future Swovee assessment may involve an authorized boundary, geospatial control, LiDAR, imagery, surface meshes, obstacles, routes, project records and operator annotations. Those systems are proposed; this public website does not currently accept those datasets.
Before activation, the project must document:
- the verified data controller and contact channel;
- site-owner authority and the exact authorized search polygon;
- purposes, legal basis, recipients, processors and processing locations;
- retention, deletion, access control, encryption and incident procedures;
- bystander and neighboring-property minimization or redaction;
- whether data may be used to improve models, with a separate affirmative authorization;
- survey, cadastral, utility and environmental-record licensing; and
- human review where an automated recommendation could materially affect a project.
LiDAR and cameras measure visible surfaces. They do not establish subsurface conditions, ownership, a legal right to build, code compliance or structural approval.
No request channel is being implied.
No monitored privacy request address is currently published. Until a verified channel exists, avoid providing personal information beyond ordinary browsing. When collection is activated, the project must publish a usable method for access, correction, deletion, objection, restriction, portability, consent withdrawal and regulator complaints where applicable.
The European Commission lists the identity, purpose, legal basis, retention, recipients, transfers, rights and automated-decision information organizations may need to provide when GDPR applies.
European Commission privacy-information guidance ↗This page must mature before the product does.
The review date will change when collection practices, hosting configuration, contacts or the project’s legal status change. Material changes should be explained, not silently backdated.
This interim notice is not legal advice, a data-processing agreement or a claim of compliance in every jurisdiction.