Policy version: 25 October 2026. This policy covers the Quest game and its community Workshop.
The last brick game you'll ever buy — 25 October 2026, private beta. Controller: Emile Tixeuil, individual entrepreneur — SIRET 79808711000036 — 6 rue Cambacérès, 87000 Limoges, France. Contact: contact@thelastbrickgameyoulleverbuy.com.
Legal bases and choices
Requested account, publishing, download and online-session features are provided to perform the service; security and abuse prevention rely on legitimate interests. Online voice requires headset microphone permission; you can mute your microphone and revoke that permission. Local building remains available without enabling these services. Where legally applicable, you can request restriction or portability, or object to processing, by contacting us.
The game serves mixed age groups. The online community workshop is for players aged 13 and over. Child accounts and unknown age categories cannot connect to it; local building remains available. Online functions are being qualified during this beta.
Data and purposes
Headset, controller and enabled hand-tracking positions and inputs are processed to display the workspace and manipulate bricks. Buildings, authored instructions, progress, interface and language settings are saved on your headset. Selected music and 3D files are read locally; screenshots you request are saved locally. These files are not automatically uploaded. The server receives no passthrough video. Optional online voice is described below.
Colocated play exchanges the shared construction and necessary operations between session players. Meta discovery and shared spatial anchors help align their boards and may process the required spatial/session data. OVH is not used to record your movement history.
Meta supplies a coarse child/teen/adult category, kept only in memory, without date of birth or exact age. It is not sent to our backend or stored raw in diagnostics. For an admitted account, the game obtains the app-specific Meta user ID and a login proof, verified with Meta. This identifies the creation owner and controls private beta access. We do not receive your Meta password. Invitation emails are managed in Meta's dashboard, not as backend login identifiers.
We keep a session hash and expiry, a proof hash against replay, and a short-lived one-way network/time-window counter against login abuse. The application counter does not store raw IP addresses. Published sets contain their title, author identifier, bricks, colours, positions, instructions, versions and dates, and can be downloaded by admitted workshop players. Unpublished drafts remain local. Private reports contain the reporter, set, written reason and date; moderation actions support review and abuse handling. Do not put personal information in shared titles or instructions. We use this data to provide requested functions, maintain ownership and prevent abuse, not to sell it or target advertising.
Experimental Internet multiplayer
This beta retains Meta age access, currently 13+, for Internet sessions. Unity Authentication verifies the Meta proof and assigns a Unity player ID. Unity Multiplayer Services manages public/private sessions and codes. Relay carries construction operations, board-relative brick positions, controllers and held parts, without sharing the physical board anchor or real room. Public listings show the host nickname, places and a voluntarily declared country.
With microphone permission, Vivox carries voice in a private session channel. You can mute yourself or another participant locally and adjust their volume. Leaving or pausing disconnects voice. The game enables no recording, transcription or Safe Voice analysis. Unity/Vivox processes player identifiers, connection and technical data required for its services; no in-game recording does not mean no provider technical logs.
OVH no longer relays gameplay or audio in this new path. It checks workshop access and Unity membership, privately maps Meta and Unity IDs and issues short-lived admission/voice grants. Service secrets stay server-side and tokens are excluded from diagnostics. Access and erasure requests include this mapping.
Unity/Vivox: data, retention and rights
The Unity Authentication SDK can cache a session token in headset preferences to renew sign-in. This local cache is separate from the Workshop token held in memory and from server-only service secrets. Leaving a match does not necessarily clear the cached credential or delete the Unity account.
For these features, Emile Tixeuil is the controller and Unity is the processor. Authentication handles the Unity ID and Meta identity link; Relay/Lobby handle player identifiers, connections/IP and session information. Vivox handles the player ID, device ID, truncated IP and transmitted voice.
| Service | Retention |
|---|---|
| Authentication | Until the player or developer deletes the game's Unity account. |
| Relay | Personal data: 30 days. |
| Lobby | Player ID in logs: up to 30 days. Session state is transient. |
| Vivox | Technical identifiers: up to 30 days by default. Voice: ephemeral. This game does not use text messaging, Safe Voice or Safe Text. |
These services are not restricted to France or the EU. Processing may occur outside the EEA according to the service and routing. Unity's subprocessor and location list and DPA describe providers and safeguards, including the applicable standard contractual clauses for transfers. Not every listed country processes every player's data.
For access or erasure, contact the operator. After verifying the requester, we first retrieve their mapped Unity ID. Authentication has access/deletion tools; Relay, Lobby and Vivox requests require their support process with that ID. OVH or Authentication deletion does not guarantee erasure in the other services. Each scope is tracked separately.
Sources: Authentication, Relay, Lobby, Vivox, Unity player privacy policy. Documentation checked: 25 October 2026.
Private player reports include the reporter and target account identifiers, session, written reason and time. They go to the game owner, not automatically to Meta, and are purged after thirty days during service activity. Host exclusion applies only to the current session. Verified access and erasure cover these active records.
Hosting and retention
OVHcloud hosts the workshop in Gravelines, France. Its published subprocessors applicable to this service may operate from France, Germany, Spain, Italy, Ireland, Poland, Portugal, the Netherlands, Canada and the United Kingdom; this does not mean that every country actually processes your data. Access is limited to the developer and authorized service/incident handlers as necessary. Meta manages its account, platform and spatial services under its own rules. Other players receive the creations you choose to share, not session tokens, private reports or drafts.
Hosting logs may contain IP addresses, request dates, URLs and results. Proofs and session tokens are not put in URLs. This page loads no advertising tools, external fonts or developer-added analytics.
Sessions expire after 12 hours, replay hashes after 24 hours and network counters within 120 seconds of their time-window start. Expired records are purged on service activity; inactive storage may retain expired rows until the next cleanup. Published sets and versions remain until verified erasure. Withdrawal hides a set but does not physically erase its server versions. Reports/moderation records support handling and abuse review; this beta does not automatically purge them by age. Personal erasure requests are reviewed for the data concerned. Headset files remain until you remove them or clear app data; Meta system backups depend on its settings.
Host backups may retain copies. OVH documents file-space recovery points through day−14 in France for Gravelines hosting; this is not a promise of immediate erasure of all host backups/logs. These are handled separately when responding to a request.
Creation ratings
Optional ratings from 1 to 5 are linked to your account and the creation: one editable vote per account, retained across versions. Other players see only the average and vote count, never voter identities. Verified data access and erasure include your votes; they are kept while the account and corresponding creation exist.
Anonymous technical part reports
The optional controller gesture sends only the catalogue part reference and game version, without account, name, description, creation, image or controller tracking. Offline reports remain on the device until sent. Identical part/version reports are aggregated for diagnosis. The queue is private; processed entries leave the pending list. Short-lived hashed network rate limits protect the endpoint; raw IP addresses are not added to this diagnostic queue. Hosting access logs remain subject to the hosting provisions above.
Request access, correction or deletion
Email contact@thelastbrickgameyoulleverbuy.com, naming the game, account and requested scope. Do not send passwords, tokens or raw login proofs. We verify account ownership before acting. Verified deletion covers the account's published versions, sessions and associated data in active workshop storage. There is no in-game complete account-erasure button yet.
You can withdraw a published set and remove local ateliers in the game. Copies already downloaded by other players and data held by Meta do not automatically disappear when we erase our server data. If a technical restore is needed, completed erasure requests must be reapplied before the affected data is made available. You may contact us with privacy questions or complain to France's CNIL. Changes to data use or community features require an updated policy.
This website
This website uses no advertising tools, analytics scripts, embedded third-party media or external fonts. There is no account or contact form. An email link opens your own email application. Basic hosting access logs may record IP addresses, request dates, URLs and response codes as described above.
Hosting references
OVHcloud subprocessors · OVHcloud data processing agreement · Web hosting backups.