00
Privacy at a glance
- You can play the current games without giving us your name, email address or payment details.
- Some games save progress or send completed scores to our servers automatically. Rankings can show your results under a guest label or a run identifier.
- A guest identifier is not a personal account. It can still be personal data, and it may identify the same browser across visits to a game.
- The Minigames pages use Google Analytics 4 for audience measurement. It is on unless you switch it off in Cookie settings. No Meta Pixel or advertising cookies. Other websites linked from these pages have their own notices.
- The entry notice records your acknowledgements. Cookie settings remember your preference, including whether analytics is on or off.
- The “Report a mistake” feature sends your note and limited technical diagnostics when you select “Send report”.
- Contact contact@buildner.com about privacy or your data rights.
01
Who is responsible
BUILDNER, SLU (“Buildner”, “we”, “us” and “our”) is the controller of personal data processed for Buildner Minigames. A controller decides why and how personal data is used.
Registration number: 715322-T
Registered address: Carretera Mas de Ribafeta 6, 3-1, Arinsal, La Massana, AD400, Andorra
Privacy contact: contact@buildner.com
Please include “Buildner Minigames — Privacy” in your email subject where convenient. You can also write to our registered address. This is our general privacy contact; it is not a statement that we have appointed a data protection officer.
We handle personal data under Andorra’s Law 29/2021 on personal data protection, as amended, and applicable implementing rules. The EU General Data Protection Regulation, UK data protection law and other privacy laws apply where the relevant processing falls within their scope. This policy does not limit rights provided by applicable law.
02
What this policy covers
This policy covers the Buildner Minigames landing page, its error-reporting feature and the Buildner-operated games Brief Encounter, Load-Bearing Ego, Something’s Off, Site Visit, Permit Pending, Egress, The Client, Poché, Cantilever and Envelope, including their game-specific saving and ranking features. A description of a feature applies only where that feature is available.
All ten games in this collection run on the same microsite. Cookies and browser storage are specific to this website. Cantilever and Envelope share a browser player identifier and ranking name; other games may use their own identifiers. The collection does not provide a shared registered account or automatic cross-device synchronisation. Your progress in one game is not necessarily available in another browser, on another device or at another website address.
Architecture competitions, Tools, BIM Tools and other linked Buildner services have their own terms and privacy notices. Entering a competition, subscribing, paying for another service or contacting an external provider involves separate processing. This policy does not make those features part of Minigames.
The Terms & Conditions govern use of the games. This policy explains data processing. Reading it, playing a game or accepting terms is not consent to optional advertising or analytics tracking.
03
Information we use and where it comes from
Personal data is information relating to an identified or identifiable person. It can include online identifiers, an IP address, correspondence and gameplay records associated with a browser. Replacing a name with a random identifier, or hashing information, does not necessarily make it anonymous.
We receive information from your browser when it requests pages or sends game records; from the game actions you take; from reports or enquiries you submit; and from hosting or security services supporting those requests.
Swipe to read all columns.
| Information | Examples | When it is processed |
|---|---|---|
| Connection and technical information | IP address, time, requested address, response status, browser details and referring address where supplied | Loading a page, using an online game feature or requesting an asset |
| Guest identifiers | Random visitor or player ID, a guest cookie and a hashed guest token where used | Saving progress, recognising a returning browser or showing personal rankings |
| Notice records and privacy choices | Hashed acknowledgement token, notice version, acknowledgements, choice and expiry times | Completing the entry notice or saving cookie preferences |
| Gameplay and progress | Floor, tile rotations, game state, attempts, hints, mistakes, active playing time, outcomes and scores | Playing a game with saving or score submission |
| Ranking information | Guest label or run identifier, points, performance measures, position and completion time where shown | A completed result enters a game’s rankings |
| Local browser information | Personal best and completed results waiting to be sent | A game uses browser storage for continuity or retry |
| Reports and correspondence | Your note, report reference, page details, limited diagnostics, and contact information you choose to provide | Sending a report or contacting us |
The current games do not ask for your real name, email, date of birth, precise location, camera, microphone, contacts or payment card details to play. They do not provide a project-file upload function. If you include personal information in an email or report, we receive it as part of that communication. Please avoid sensitive details, passwords, access tokens and information about other people unless necessary and appropriate.
04
What happens in each game
Brief Encounter and Permit Pending
The current versions run their game logic in your browser. They do not have a game-specific server leaderboard or account sign-in. Ordinary page delivery still involves network requests and technical information. Game state held only in the page may be lost when you reload or close it.
Load-Bearing Ego
The game stores a personal-best value in local browser storage. When you complete a qualifying run, it sends a run identifier, game and scoring version, outcome and placement history to the score service. The service recalculates the result and stores points, overhang, floor statistics and a completion time. The current ranking service identifies runs rather than a named player account.
If a result cannot be sent immediately, the game can keep it in a local pending queue and retry later. A result may therefore reach the service after the original play session. Successfully saved results are removed from the pending queue. Local storage may be unavailable, cleared by you or evicted by your browser.
Something’s Off
This game uses a guest cookie to recognise a browser. Its server stores a player ID and a hash of the guest token. Completed runs include a run identifier, scoring and generator versions, round results, precision, pace, consistency, solved rounds, mistakes, streak information, active playing time and the time the record was saved.
Completed results can be submitted automatically. Unsaved results may remain in a local retry queue. Rankings associate results with a generated guest label and include a player identifier in the data returned by the ranking service. They do not require a real name or email address.
Poché
Poché stores your daily grid, timing, mistakes, naming bonus, completed plans, streak, drawing tool and ranking name in this browser (bn-poche-v1). A random identifier in bn-player-id associates saved scores with the same browser on this website. These local records have no fixed expiry and remain until cleared by you or the browser.
A result is sent only when you choose Save to ranking. It includes your chosen display name, random player identifier, daily edition, final time, elapsed time, naming result and mistake count. The service stores one result per player and day; saving again updates the name. Daily and all-time rankings show names and times. Practice results are not submitted. Save requests use a daily hash of the connection address to limit repeated requests; those rate-limit records are removed after one hour when the service next receives a save request. Raw connection addresses are not stored in Poché’s ranking tables.
Site Visit
Site Visit uses a visitor cookie to load and save progress. Progress can include the current floor, tile orientations, remaining time, rotation counts, hints, completion state and an attempt identifier. When you complete a floor, the service can save an attempt record with points and related performance measures. Rankings can show a generated visitor label and results based on the best saved attempts.
The landing page’s integrated Site Visit uses a cookie scoped to its game path. Saving progress is a server feature; the existence of local gameplay does not mean that progress remains only on your device.
Egress
Egress saves a random player identifier, your chosen ranking name, completed daily plans and in-progress door cuts in this browser’s local storage (bn-egress-v1). Reloading the game resumes the saved day. The local record has no automatic expiry and stays until replaced or cleared by you or the browser.
A completed Egress result is sent to the ranking service only when you select Save to ranking. The submission includes the daily edition, player identifier, chosen name and each plan’s door cuts. The service verifies the completed plans and stores the result with creation and update times. The public rankings show your chosen name, result and daily edition; the API also returns the player identifier. Use a nickname you are comfortable making public. Saving again for the same player and day changes the name without replacing the original score.
The catalog’s Egress service uses a hash derived from the request’s IP address and current hour to limit score submissions. The rate-limit records retain the current and previous hour; older records are cleared on subsequent submissions. Raw IP addresses are not stored in these application records. The supplied optional points-hub script is not loaded in the catalog.
The Client
The Client keeps daily decisions, progress, practice unlocks and your chosen ranking name in local browser storage (bn-client-v1). It also uses an HTTP-only guest cookie restricted to its ranking service. When you choose Save to ranking, it sends your chosen name, daily challenge number and yes/no decisions. The server replays those decisions and stores the verified result, meter total, client, ending and submission time. Rankings display the chosen name and result; your name can be a nickname. Practice runs are not submitted.
Cantilever and Envelope
Cantilever stores daily attempts and a chosen ranking name in bn-cant-v1. Envelope stores progress and personal bests in bn-env-v1. These two games also use bn-player to share a browser player identifier and name on this microsite. These records have no fixed expiry and remain until cleared or replaced by you or the browser. They do not create a registered account or synchronise devices.
When you choose Save to ranking, Cantilever sends your player identifier, name, daily edition, five level results and result symbols. The service stores the first submitted daily score; subsequent saves may update the name. Envelope submits a result when you enter a ranking name and save. Once a name is saved, later completed runs can be submitted automatically, and pending results can be retried. It sends the player identifier, name, day, floor area score, floor count, height, completed cities and result symbols. The service retains the best submitted run per player and day. The ranking boards display player names, scores and selected game results. Use a nickname you are comfortable making public.
Both services use a short-lived hash derived from the connection address and time window to limit repeated submissions. Records for earlier windows are cleared on subsequent saves; raw connection addresses are not stored in these application ranking or rate-limit tables.
05
Public rankings and guest identities
For games that submit results automatically, completing a qualifying run or floor can save a ranking result without a separate “make this score public” step. Egress instead submits its daily result only when you select Save to ranking. If you do not want a score published, do not complete a qualifying run in those games; you can also contact us about removing a saved record where it can be identified.
Rankings may show a guest or visitor label, run or player identifier, score, position, timing and game-specific statistics. Other visitors can view, copy or share information displayed publicly. Removing a record from our service cannot guarantee removal of copies someone else has already made.
Guest labels do not establish verified identity, age, professional qualifications or competition eligibility. Gameplay scores are for recreation. They are not used by these games to decide employment, credit, insurance or access to essential services.
Clearing a guest cookie normally makes the game treat you as a new visitor. It does not automatically erase earlier attempts or public rankings. It can also make it harder to connect a privacy request to an older record. A new browser or website address may create a different guest identity.
06
Cookies and browser storage
Cookies are small values a website asks your browser to store and send with later requests. Local storage holds values on your device for scripts on the same website to read. Both can support functionality without creating a personal account.
Swipe to read all columns.
| Name or storage item | Purpose and location | Duration |
|---|---|---|
bn_games_consent | Necessary cookie referring to the server record of the current entry-notice acknowledgements | Up to 365 days; a changed notice version can require acknowledgement sooner |
bn_games_privacy | Cookie recording the cookie-preference version, choice, categories and timestamps | Up to 180 days, unless cleared, replaced or invalidated by a changed version |
bn-egress-v1 | Egress local storage for the guest identifier, chosen ranking name, daily results and in-progress door cuts | No fixed expiry; until cleared or evicted by the browser |
bn-cant-v1, bn-env-v1 | Local progress, player name and results for Cantilever and Envelope | No fixed expiry; until cleared or replaced |
bn-player | Browser player identifier and name shared by Cantilever and Envelope | No fixed expiry; until cleared or replaced |
bn-poche-v1, bn-player-id | Poché daily progress, ranking name and browser player identifier | No fixed expiry; until cleared or replaced |
bn-client-v1 | The Client daily decisions, progress and ranking name | No fixed expiry; until cleared or replaced |
bn_client_player | The Client guest cookie, restricted to its ranking API | Up to 365 days from the latest identity request |
sv_visitor | Site Visit visitor cookie, used to retrieve progress and associate floor attempts with a browser | Set for up to 365 days, unless cleared or replaced sooner |
bnr_game_guest | Something’s Off guest cookie, used to recognise the browser and associate runs with its guest record | Set for up to 365 days, unless cleared or replaced sooner |
load-bearing-ego.best.v1 | Local storage for the Load-Bearing Ego personal-best value | No fixed expiry in the game; until removed or browser storage is cleared or evicted |
load-bearing-ego.pending-runs.v1 | Local storage for Load-Bearing Ego results awaiting successful submission | Pending entries are removed after successful saving or when the storage is cleared |
buildner-somethings-off-pending-v2 | Local storage for Something’s Off results awaiting successful submission | Pending entries are removed after successful saving or when the storage is cleared |
The game-specific cookies above support guest recognition, saving and rankings; they are not advertising identifiers. We rely on the exemption for storage strictly necessary to a service you request only where its legal requirements are met. A new optional use requires separate consideration and any consent the law requires.
You can use your browser’s website-data controls to inspect, block or remove cookies and local storage. Blocking storage can prevent returning to saved progress, recognising your previous guest identity or retrying unsent results. Clearing a pending queue before it has been sent removes that local copy; it does not recall a copy already received by the service.
The cookie expiry is not a server-record deletion period. Server retention is addressed in section 13. Private browsing and browser eviction may remove local data sooner. You can reopen Cookie settings in the footer and read the Cookie Policy. Google Analytics is on unless you switch it off with Reject optional or the Analytics switch; advertising is not used. A saved choice is not permission to silently activate another provider.
Entry notice and privacy choices
Before entering the collection, the entry notice asks you to acknowledge the recreational-use notice, accept the Terms & Conditions, confirm receipt of this Privacy Policy, and acknowledge the Cookie Policy and necessary storage. All four acknowledgements are required and start unchecked. The server stores a hash of a random acknowledgement token, the notice version, acceptance and expiry times and the acknowledgement values. This application record does not include a raw IP address, user agent or email address. Hosting requests can still involve separate technical logs.
The entry cookie links your browser to that record. The server checks the version and expiry before accepting it. If the record is absent, invalid or expired, you may need to complete the current notice again. Blocking this necessary cookie can prevent entry to the collection. The policy pages remain readable before acknowledgement.
The cookie-preference cookie separately records the selected action, necessary/analytics/advertising category values, policy version and choice and expiry timestamps. It is stored in your browser and, like a normal cookie, is sent with matching requests. The current application does not create a separate server database of those preference choices. Acknowledging receipt of the Privacy Policy is not consent to all processing, and accepting the Terms does not turn on optional tracking.
07
Website delivery and security
Loading pages and online features requires infrastructure providers to process requests. Request information may include an IP address, requested path and query, request time, browser headers, referring address, response status and technical errors. Provider logs can exist separately from the application’s game and reporting databases.
This processing supports delivery, troubleshooting, availability and protection against excessive requests or abuse. The current game score tables do not deliberately store a raw IP address as a score field. That does not mean the hosting infrastructure never processes or logs IP addresses.
Minigames does not request precise device location. An IP address can indicate an approximate area, but that is not a reliable statement of your physical location. Please do not put confidential information into a page address or a link you share.
08
“Report a mistake”
The reporting feature keeps a limited buffer of recent technical errors in the page’s memory. The report feature sends that buffer when you select “Send report”; simply opening the report dialog does not send a report. Separate page requests, hosting logs and game-saving requests continue to operate as described elsewhere in this policy.
Your report includes its random request reference, your optional note, page address and title, date and time, browser information and selected diagnostics. Diagnostics can include language, time zone, connection status, viewport dimensions, pixel ratio, software release and up to 40 recent technical-error entries. It does not take a screenshot or attach game project files, cookies or a recording of every interaction.
The report service strips query strings and fragments from the stored page address and filters technical strings to reduce incidental secrets and email addresses. Filtering is not a guarantee that all personal information is removed. Your optional note is retained as submitted, so please leave personal and confidential details out of it.
For report rate limiting, the service derives a daily hash from the connecting IP address where that address is supplied by the hosting infrastructure. It stores that hash with the report rather than a raw IP address in the report table. This remains pseudonymous information; the hash is not a promise of anonymity. Its daily input changes, but stored report records do not automatically disappear at the end of the day.
Reports are not part of public rankings. Authorised people working on support, maintenance and security may access them. A report reference helps us locate a submission. The report form does not ask for an email address, so it does not normally allow us to reply personally; email us if you need a response.
09
Email and other enquiries
If you contact us, we use the message, sender information, attachments and any relevant correspondence to respond, investigate your request and maintain an appropriate record. Only send information needed to explain the issue. Emailing an attachment is separate from playing a game in your browser.
We may ask for additional information to locate a score or check that a request relates to you. We aim to use proportionate verification. Do not send a password, full cookie value or an identity document unless we have explained a necessary, appropriate way to provide verification.
10
Analytics, advertising and future features
The Minigames pages load Google Analytics 4 (Google Ireland Limited, property G-5BRMD23HY4) to measure visits, pages and which games are played. It runs from your first page view unless you switch it off in Cookie settings; switching it off stops measurement, tells Google that analytics storage is denied and removes its cookies from this browser. Advertising features, Google signals and ad personalisation are off, and Google Analytics 4 does not store IP addresses. The pages do not load Google Tag Manager, Meta Pixel, advertising scripts, third-party session replay or an email-marketing sign-up. We do not use current game records to sell advertising audiences or combine players’ activity into an advertising profile across the collection. Technical error reports and score records are separate from advertising tracking.
The Tools and BIM privacy examples describe features that are not automatically active here. Following a link to another service may expose you to that service’s cookies and processing; consult its own notice and settings.
If we introduce advertising or another optional service, we will identify the purposes, providers, information and storage involved, update this policy and provide the choices required by applicable law before it operates. Consent to optional tracking will be separate from using basic games or accepting terms. Where consent is required, refusing or withdrawing it will not remove access to basic gameplay.
Accounts, profile linking, payments, cloud uploads or other new features would also require appropriate information before use. A future-feature description is not a statement that the feature currently exists. The current games do not send gameplay to an AI model for inference or training.
11
Purposes and legal grounds
The legal ground depends on the activity and applicable law. In particular, an exemption from cookie consent and a legal basis for processing personal data are separate questions.
Swipe to read all columns.
| Purpose | Information involved | Legal ground where applicable |
|---|---|---|
| Deliver the game and requested saving or score features | Requests, guest identifiers, progress and game records | Performance of the service contract, to the extent objectively necessary to provide the feature you request |
| Operate public guest rankings and validate results | Guest labels, run identifiers, results and performance measures | Legitimate interests in running the advertised recreational rankings and limiting manipulated results, subject to your rights and a balancing assessment |
| Protect availability and investigate faults or abuse | Technical records, reports and rate-limiting information | Legitimate interests in maintaining a safe, reliable service |
| Remember entry acknowledgements and privacy choices | Notice record, acknowledgement reference and preference cookie | Legitimate interests in administering the service and demonstrating notices presented; compliance with applicable consent or privacy obligations where relevant |
| Respond to enquiries | Correspondence and information needed to investigate | Legitimate interests in providing support; contract performance where the enquiry concerns that service |
| Handle statutory requests and legal obligations | Relevant identification, correspondence and supporting records | Compliance with an applicable legal obligation |
| Establish, exercise or defend legal claims | Relevant service, incident or correspondence records | Legitimate interests in resolving disputes and protecting legal rights |
| Measure visits and which games are played (Google Analytics 4) | Page views, game events, a random client identifier in the _ga cookies, browser and coarse location derived by Google; no IP address is stored | Legitimate interests in understanding how the collection is used, with the Analytics switch in Cookie settings as an opt-out available at any time; consent where applicable law requires it |
| Introduce advertising or another optional service, if offered later | Information explained in the updated notice and preference controls | Consent where required; no such integration is active in the current games |
Our legitimate interests do not automatically override your rights. You can object on grounds relating to your situation, and we will assess the request under the applicable law. Where processing relies on consent, you can withdraw it without affecting the lawfulness of earlier processing.
Providing a name or email is not required to play. A request still needs basic connection information to be delivered. Guest saving and personalised rankings need a usable identifier; preventing that processing may mean the requested feature cannot work. Sending a support report is optional.
12
Recipients and international processing
Information is available as needed to authorised Buildner personnel and service providers supporting hosting, databases, security, maintenance and correspondence. Providers receive information relevant to their role. We may also disclose necessary information to professional advisers, authorities or other recipients where required by law, to protect rights or to address a dispute. Public ranking information is available to visitors as described in section 5.
Some preview versions are accessed through a hosting-platform address. The platform may process information for access, delivery and security under its own notice. That processing is distinct from a player account in a Buildner game. A local copy served on your computer does not, by itself, mean its application database is hosted externally.
Depending on the website version you use and its hosting arrangements, providers may process information outside Andorra or your country, including through remote support and backups. Where an international transfer is restricted by applicable law, it requires an applicable adequacy decision or another lawful transfer mechanism, such as appropriate contractual safeguards, with additional measures where necessary. A provider name or server region alone does not establish the transfer mechanism.
Google Analytics 4 is provided by Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) with Google LLC (United States) as a sub-processor; the transfer relies on the EU-US Data Privacy Framework and Google's standard contractual clauses. Google processes the measurement data as our processor under the Google Ads Data Processing Terms.
Contact us to ask which providers handle the version you use, where relevant processing takes place and how to obtain information about applicable safeguards. Include the game’s website address so we can identify the relevant service. We do not sell current Minigames player records to data brokers.
13
How long information is kept
Local information follows the browser-storage periods described in section 6. The server uses separate records for progress, score attempts and reports. A cookie expiring, a score dropping out of a displayed top list or a leaderboard being filtered to the last seven days does not automatically delete the underlying record.
The current application has no automatic age-based deletion routine for saved game records or reports. Those records remain until they are deleted through administration, a valid rights request, database reset or service retirement. We do not represent a fixed automatic deletion deadline that the application does not implement.
Entry acknowledgement records expire after 365 days. When a new acknowledgement is saved, the service attempts a limited cleanup of expired acknowledgement records. This is not continuous scheduled deletion and does not guarantee removal exactly at expiry. Expired acknowledgements no longer grant entry even if a stored record awaits cleanup.
Retention decisions must be tied to a continuing purpose: allowing a player to resume saved progress; maintaining the relevant scoring season or version; investigating a report or security issue; dealing with a request; or meeting an applicable legal obligation or claim. Once information is no longer needed for those purposes, it should be deleted or made genuinely anonymous. A need to preserve particular evidence does not justify keeping unrelated information indefinitely.
Google Analytics keeps event-level data for the retention period set in the analytics account (2 or 14 months) and aggregated reports for as long as the property exists; switching analytics off in Cookie settings stops new collection from that browser.
Provider access logs, support correspondence and backups follow their own operational and legal requirements. Deleting an active record may not immediately remove an isolated backup copy. If you need the applicable period or criteria for a specific category, contact us with the game or page address. We will explain any relevant retention restriction when responding to a deletion request.
14
Security
The application uses measures such as input validation, restricted database access, checks on score submissions, limits on reports and protection of guest cookies from direct script access where supported. Appropriate deployment, access controls, maintenance and transport security are also necessary. No website or storage system can guarantee absolute security.
A shared browser can expose a previous player’s saved progress or guest identity to the next person using it. Clear site data when appropriate on a shared device, recognising the consequences described above. Guest records are not a substitute for a verified account or a personal backup.
If a personal-data breach occurs, we will assess it and make notifications required by applicable law. Please report suspected privacy or security issues to contact@buildner.com.
15
Your rights and how to use them
Depending on the applicable law and circumstances, you can ask to access your personal data, correct inaccurate information, erase information, restrict its use, object to processing based on legitimate interests and receive portable data where the legal conditions apply. You can withdraw consent where we rely on it. These rights have legal conditions and exceptions; this policy does not replace them.
Email contact@buildner.com or write to our registered address. Explain what you would like us to do and, if available, include the game name, website address, approximate play or report date, public guest label, run reference or report reference. Do not post private identifiers publicly. We will explain any further verification needed through a suitable channel.
We do not normally know a guest player’s real-world identity. If we cannot reasonably connect a request to a record, we may need information that enables the connection and will explain the limitation. We do not ask you to create an account solely to make a privacy request. Consider contacting us before clearing the browser identity associated with the records you want located.
We will respond within the period required by applicable law. Where the GDPR applies, this is normally within one month, with a permitted extension for complex or numerous requests accompanied by an explanation within the initial period. Requests are normally free; any permitted refusal or reasonable charge must have a lawful basis and be explained.
You do not have to contact us before complaining to a competent authority. We will not penalise you merely for exercising a privacy right. Deleting information needed for saved progress or rankings can make that particular feature unavailable.
16
Children and younger players
Minigames is intended for adults. The current Terms & Conditions require users to be at least 18 and legally capable of entering the agreement. The service does not use a date-of-birth form or claim to verify every player’s age. It does not deliberately create named child profiles or target advertising at children.
Any age and capacity requirements for using the service are explained in the Terms & Conditions. Where a feature requires a child’s consent or parental authorisation under applicable law, the relevant requirements must be met before that processing. A parent or guardian’s involvement does not remove the child’s privacy rights.
If you believe a child has provided information that should not have been collected or made public, contact us with enough detail to locate it. We will review the situation and take appropriate steps, including deletion where required. Please avoid putting a child’s name or other identifying details into report notes or publicly shared scores.
17
Automated scoring and regional rights
Games calculate scores, evaluate moves and order rankings using game rules. The service may reject invalid or excessive submissions. These processes affect the game result; the current service does not use them to make decisions producing legal or similarly significant effects on a player. You can contact us about an apparent scoring or record error.
Additional regional privacy rights may apply, including rights concerning targeted advertising, sale or sharing, appeals and authorised agents. The current games do not run advertising or sell player records as described above. We will assess an applicable regional request under the relevant law and explain the available response or appeal route. Browser signals do not automatically erase existing game records.
18
Complaints, changes and contact
You can raise a concern with us or with the Andorran Data Protection Agency (APDA). Where the GDPR applies, you may also complain to a competent supervisory authority, including in the EU/EEA country of your habitual residence, work or the alleged infringement. UK users can contact the Information Commissioner’s Office.
We may update this policy when features, processing, providers or legal requirements change. The date and version at the top identify this text. Material changes will be explained appropriately before or when they take effect; if new processing requires consent, merely publishing an updated policy will not supply it.
For questions or requests, contact BUILDNER, SLU at contact@buildner.com, or write to Carretera Mas de Ribafeta 6, 3-1, Arinsal, La Massana, AD400, Andorra.