This privacy policy covers Pixel Real Estate ("we", "us"), a project run by Alina Amirkhanian as an individual, not a company. She is the one responsible for your data; write to support@pixelrealestate.homes.
| Data | When |
|---|---|
| Email address, password (stored hashed, never in plain text) | When you create an account. If you buy a plot without one, we open an account for the email you gave at checkout, without a password |
| If you sign in with Google: the name, profile picture link and Google account ID that Google passes on with your email address (sometimes also your language setting, and for a work or school account its domain) | Only if you use “Continue with Google”. They are kept with your account, like your email; the site does not show them anywhere |
| Which plots you own, price paid, purchase date | When a purchase completes |
| The name and email address of someone a buyer gives a plot to | Only if a buyer names you as the owner of a plot they give away (for example the free plot for the first 20 buyers). We use them to register that plot to you and send you its certificate. The name is shown on the plot like any owner’s name; you can change it at any time, or ask us to remove the plot. If you had no account, we open one for that email, without a password |
| Display name, image, link, description, social links you add to a plot | Only if you choose to add them — entirely optional |
| Which subscription you have, when it renews, which of your plots it covers, and the payment provider’s own reference for the payment | Only if you buy Plus. The reference is what lets us match a renewal, a cancellation or a refund to your account |
| Your IP address, held temporarily (auto-deleted after about a day); for arcade unlocks, also a one-way code made from your account ID (the ID itself is not put there) | To stop spam and abuse of checkout, uploads, the report form, the support chat, the email list, hearts, the visit counter, the arcade leaderboards and unlocks, the toy shelves in apartments and the pictures made for sharing a plot |
| A heart you leave on a plot: a one-way code made from your IP address (the address itself is not kept), so that one connection gives one heart per plot | Only if you press the heart; kept while the heart is there |
| An arcade leaderboard entry: the nickname you type, your score and when you set it, the game and the details of that round (for example the three spits, or how many cans, ducks and targets), a one-way code made from a random number your browser keeps for the arcade, a one-way code made from your IP address (neither the number nor the address itself is kept), and your account ID if you are signed in | Only if you press “Add to board” after a game. The nickname and the score are shown to everyone on the board; the codes and the account ID are never shown. The codes are there to show you your own place, to stop the same result being sent twice and to stop cheating; the account ID only marks the entries made while you were signed in. Kept while the board exists; write to us and we remove your entries |
| Free plot offer: which account took which free plot and when, the domain of your email address (such as gmail.com) and a one-way code made from your email address (the address itself is not kept in this record) | Only when you claim a free plot. To keep it to one free plot per person: the same mailbox can’t take a second one, and only a few go to any one less common email domain. Kept while your account exists and deleted with it. Each attempt to claim also goes into the anti-spam log described in this policy (your IP address and a one-way code made from your account ID, deleted after about a day): it limits attempts and gives one connection at most three free plots a day. |
| Arcade unlocks: which items (looks such as a blaster) your account has unlocked and when; for each finished round that could unlock something, the round number, the game, what that round unlocked, and the same two one-way codes as for the leaderboard (neither the random number nor your IP address itself is kept) | Only while you are signed in, when a round you played could unlock something. To keep your unlocks, apply the daily limits, stop one round counting twice and stop cheating. Nobody else sees your unlocks, with one exception you choose: if you put the “Media wall with toy shelves” in the apartment of a plot you own, anyone who opens “Visit the apartment” sees the Pixel Claw toys standing on it (not your account or email; your studio in Pixel House is seen only by you). Unlocks are kept while your account exists and are deleted with it; round records are deleted after 30 days |
| Walking together in the 3D city (“In the city”): while you walk with Pixel, your browser sends to other people walking at the same time where your Pixel is, which way it faces, what it wears (colour, pattern, hat, glasses, face and extras — not the flag with your plot’s picture and not the name tag), the emotes and ready-made phrases you tap, and a session number made anew each time you open the page (8 characters computed from your sign-in and a random number, so nobody can tell your account from it). If you invite a friend (“Invite a friend”), the link holds only a random code; the name you may type for friends goes only to people who have that link (also anyone they pass it on to; the code is removed from the address bar, so it does not travel with a copied page address, and “Leave friend group” forgets it). To count our monthly message allowance, your browser also sends us two numbers every 5 minutes: how many of these messages it sent and received | Only after you start a walk. It goes live through our realtime provider (Supabase) and is not stored: nobody can see where you were before. It is meant for the people walking at that moment. These live channels are closed: only someone who is signed in — with an account or with the anonymous sign-in below — can join them. But anyone can start a walk, and someone with technical skill could join the way a walker does without walking themselves, so treat your Pixel’s place in the city as visible to anyone walking at that moment. If you are not signed in, starting a walk signs you in anonymously with Supabase: it creates an account ID with no email, name or password, which your browser keeps in local storage so the next walk uses the same one (a private window, or a browser that clears site data — Safari does after 7 days without a visit — gets a new one). We create it only to let you into these channels, and it is not a shop account, but from then on the site treats it like any sign-in: if you later write to us in the support chat or ask us to tell you when card payments open, that is linked to this same anonymous ID. Like any sign-in, Supabase logs when it was made and from which IP address. There is no automatic clear-out yet, so it stays until you ask; because it carries no email, write to us in the support chat from the same browser, so we can tell which one is yours, and we delete it. There is no anonymous sign-in when the page loads, with “Walk alone” or while live visitors are switched off, with one exception: a friend’s walk link (one with ?walk=) starts the walk by itself once the city is ready, so opening one signs you in. If you log out during a walk, you are not signed in anonymously in its place: you see others again once you start a new walk. Strangers’ dots appear only on the small corner map, not on the big map. Strangers see your Pixel only as a cube with its outfit — never your name, account, email or plots. “Walk alone” sends nothing and shows you no one. You can hide anyone’s Pixel for yourself until you reload the page (if that person reloads theirs, they get a new session number and show up again); if you are signed in, “Report” also sends us, through the site chat, that Pixel’s random session number, the copy and district of the city and the time. The monthly counts are kept as two totals per month, without session numbers or IP addresses |
| Pixel Headers online (a match with a friend by link or with a random opponent): while you play, the other player’s browser gets your Pixel’s team and player number, its moves and the emotes you send. A friend also gets the name you type for them, if you type one; a stranger gets no name and there is no chat. To let you into the game’s private live channels, starting online signs you in to Supabase anonymously if you are not signed in on this device already (an account with no email and no password, like the one the support chat creates; your real sign-in is used if you have one). Like the chat’s, that anonymous sign-in then stays on this device, so the next match uses it again instead of making a new one; clearing the site’s data in your browser removes it | Only when you start a match online yourself. Against a random opponent every message goes through Supabase Realtime, so neither of you sees the other’s IP address. With a friend by link your two browsers connect directly, so each can see the other’s IP address (the game says so before you connect); to find a direct route the browsers ask a public STUN server (Cloudflare’s or Google’s) for their own public address, and if a direct route can’t be made the match goes through Supabase instead. Nothing about a match is stored. If you report an opponent while signed in, a short line goes to us through the support chat with their random session number for that page (no name, no account) |
| Visits in the 3D city: when your Pixel walks up to someone’s house and stays there a few seconds, we count a visit — once a day for each plot. All we keep is a one-way code made from your account ID if you are signed in, or else from a random number your browser keeps for this (under “prGosti”), mixed with the date and a secret that stays on our server. The code changes every day; within one day the same code marks every house you visited that day. Neither the ID, the number nor your IP address is kept, and the anti-spam log for this gets only a one-way code made from your IP address. If you leave a sticker in the house’s guestbook (only ready-made stickers such as “Nice house!”, no text of your own), the same kind of code marks that you already left one that day | Only while you walk with Pixel. Everyone sees only numbers: how many visits a house had in the last 7 days and how many of each sticker it got — never who. A visit record is kept for 8 days (the day of the visit and the 7 days after it), the mark about a sticker for 2 days; what stays is the number of stickers of each kind, kept for the owner who got them: when a plot passes to someone else, the new owner’s guestbook starts at zero, and the old numbers are deleted with the old owner’s account. The owner of a plot can switch all of this off for it |
| Your apartment, if you own a plot: the choices you make in its renovation (the layout, floors, walls, kitchen, curtains, doors, furniture and appliances you pick from the site’s catalogue), together with the plot number and your account ID | Only if you furnish the apartment of a plot you own while signed in. Kept in your browser and in our database, so the apartment looks the same on any device. Anyone who opens “Visit the apartment” on that plot sees the renovation, the way they see the house and its picture on the map; your account ID and email are not shown. Deleted with your account |
| Your free studio in Pixel House: the choices you make in it (the floors, walls, kitchen, curtains, doors, furniture and appliances you pick from the site’s catalogue), together with your account ID | Only if you open your own studio while signed in. Kept in your browser and, once it is saved to your account, in our database, so the studio looks the same on any device. Other visitors can’t see it. The copy in our database is deleted with your account; the copy in your browser stays until you clear the site’s data |
| Your city passport: which stamps and badges you have collected on walks with Pixel, which rides counted towards a badge and how long you walked in the rain, and Pixel’s level on walks (experience points and which of those stamps and badges already gave points), together with your account ID | Only if you are signed in. Kept in your browser and, once it is saved to your account, in our database, so the passport and the level are the same on any device. Nobody else sees it. The copy in our database is deleted with your account; the copy in your browser stays until you clear the site’s data |
| The email you typed at checkout without an account, if you did not pay | Kept with that unpaid order for 30 days, then deleted automatically; write to us and we delete it sooner |
| What you write in a content report | Only when you report a plot. It carries no account, no name and no email |
| Your email address, the plot(s) you had picked, the language you were reading in, and which part of the site you left it from; if you are signed in (also anonymously, see “Walking together” above), your account ID | Only if you ask us to write to you when card payments open. Deleted on request; otherwise kept until we have written to you |
| The messages you send in the support chat, and the anonymous visitor account they are attached to | When you write to us in the chat window. Opening the chat creates an anonymous account for you — it has no email and no password, exists only so your side of the conversation stays yours, and is never a shop account |
Which page was opened, which site you arrived from (the site’s name only, never the full address, or the short tag of a link we shared, such as ?from=newsletter), the country your visit came from as our host reports it, whether you opened the 3D city, which plots were opened, the language the page is shown in, whether the screen is phone-sized, and which steps on the way to buying were pressed (for example Buy, Try your picture, a heart), whether the page stayed open on screen for 30 seconds, how long the 3D city took to build on your device, whether you used the walk with Pixel (opened it, walked, opened its map, flew or took the bus, which kind of card it showed you), whether you played the claw game (dropped the claw, caught something, and what), and whether you opened an apartment or the studio in Pixel House (and whether it was the show one). Each of these carries a random code that ties together the pages opened in one sitting. The code is made up in your browser, is not linked to your account, your email or your address, and disappears when you close the tab | On every page view, so we can see how many people find the site, from where, and what they look at |
Your cart and watchlist are never sent to us at all — they're stored only in your own browser (localStorage) and disappear if you clear your browser data. The one exception is notifications: if you ask us to tell you when a particular plot is taken, we have to keep that plot's number together with your browser's delivery address, because otherwise there is no way to know whom to notify. That list holds nothing else — no email, no name — and it disappears the moment you turn notifications off.
Content reports are submitted anonymously — a report carries no account, name or email. For about a day after it is sent, the anti-spam log described above still holds the IP address the request came from, so in that window the two could in principle be lined up by time; after that the log is deleted and the report stands on its own.
We use a small number of service providers to run the site. Each only receives what it needs to do its job:
Account emails — sign-up confirmation and password reset — are written by Supabase and handed to Resend for delivery. Both are listed above, and the email itself carries your address and a one-time link, nothing else.
We use your browser's local storage (not traditional tracking cookies) to keep you logged in and to remember your cart/watchlist on your own device. Disabling local storage will log you out and clear your cart. We set no cookies of any kind. Fonts and code are served from this domain. Plot images and live map updates come from Supabase, our database host (listed above), which sees your IP address the way any server does and nothing else. No third-party advertising, analytics or social-media code is loaded; the visit counter described in Section 1 is our own. If you add the site to your home screen, a service worker is installed; it stores only the offline page and the app icon, and never a copy of the site's code. The per-tab code the visit counter uses, and the short tag of a link we shared if you arrived through one, live in session storage and are thrown away when you close the tab. The one exception: a link we only use on our own devices leaves a single flag in that browser's local storage, which marks its visits as ours so we can tell them apart from guests' visits. Clearing the site's data in your browser removes it. The apartment of a plot you own keeps its renovation on this device in local storage too, under the plot number. Your studio in Pixel House does the same, under your account ID; if you press “Get your free studio” before signing in, a mark stays there so the studio opens as soon as you are signed in; after an hour it is no longer used and is removed on your next visit. During Halloween (28 October to 2 November) the city also keeps here which of the ten candies you found and whether Pixel wears the pumpkin head (under “prHallo” and the year); nothing of it is sent to us. The 3D city also remembers here whether you turned its sounds on and at what volume (under “prZvuk”), and which of the 25 golden pixels you have found (under “prZoloto”); nothing of it is sent to us either. If you close the tip that your browser is drawing the 3D city without the graphics card, the city remembers that here, so the tip is not shown again (under “prCity3dBezGpu”); nothing of it is sent to us either. The photo mode of the 3D city keeps here which of the 20 postcards you have taken, small copies of them for the album and the days you did the daily photo task (under “prFoto” and “prFotoMini”); your photos are not uploaded anywhere, and nothing of it is sent to us. The walk with Pixel keeps here which of today’s errands for the city’s Pixels you have done and how many you have done in all (under “prZadaniya”); nothing of it is sent to us either. It also keeps the random number for the visit count and which houses you visited and signed today (under “prGosti”); the number reaches us only as the one-way code described in Section 1. The walk with Pixel also keeps here its city passport: which of the 12 stamps and 7 badges you have collected, which rides counted towards a badge and how many seconds you have walked in the rain and, once you have signed in, which account this copy belongs to (your account ID) (under “prPasport”); if you are signed in, the same passport is also saved to your account (see Section 1). It also keeps Pixel’s level on walks: the experience points, which one-off things (stamps, badges, golden pixels, postcards) have already counted, today’s counts towards the daily limits, the last level it showed you, whether Pixel rides your scooter or bike and, once you have signed in, which account this copy belongs to (your account ID) (under “prUroven”); if you are signed in, the experience points and which stamps and badges have already counted are saved to your account together with the passport (see Section 1), while which golden pixels and postcards counted, today’s counts and the ride choice stay only here. The jobs on the walk (courier, taxi and post) keep here your best results of the week and whose house the next delivery goes to (under “prRabota”); nothing of it is sent to us either. Walking together (see Section 1) keeps here the name you typed for friends (under “prVmImya”, until you change it), your friend group’s code, used for 12 hours (under “prVmKod”; “Leave friend group” removes it), whether you chose “Walk alone” (under “prVmOdin”), a mark that live visitors were switched off, which counts for 6 hours (under “prVmVykl”), the session numbers of your other open tabs of this site for 3 minutes, so your own second Pixel is not shown to you as a stranger (under “prVmMoi”), and, if a walk signed you in anonymously, that account ID, so the support chat does not ask us about replies until you write to it (under “prVmAnon”); none of it goes anywhere beyond what Section 1 describes. Pixel Hole (/hole/) keeps here its best: the most that was swallowed in one round and the furthest step the hole reached (the two can come from different rounds) and the day of the last round you finished (under “prHoleBest”), and whether its sound is on (under “prHoleSound”); nothing of it is sent to us. The game pages with a “How to play” card also remember here whether you folded it (under “prHowto:” and the game’s name). The arcade games keep your best result on this device in local storage, and from your first game also the random number for the arcade described in Section 1 (it ties a score to the game it came from); once you put a score on a leaderboard, also the nickname you used (so the field is filled in next time) and a mark that this browser has a score on that game’s board (so the board shows your place). Pixel Tower keeps only your best height, whether its sound is on and whether its “How to play” card is open or folded (under “prTowerBest”, “prTowerSound” and “prHowto:tower”); you do not need an account for it and nothing of it is sent to us. If you are signed in, the arcade games (and the toy shelf in your apartment or studio) also keep on this device a copy of the list of what you have unlocked, and the games keep the look you chose in each of them. If you press “Sign in” on a game’s result card, that round (its number, score and details) and the game’s address wait there for up to an hour, so the round can still be saved and you come back to the game once you are signed in; after that they are no longer used. While you sign in with Google, a one-time code for this tab and the answer Google sends back (your name and email address) wait in session storage for a few seconds and are deleted as soon as you are signed in. If that sign-in fails, local storage remembers it for 24 hours, and the Google button then signs you in through Supabase instead. The new 3D city keeps here the progress of your walks: your coins, the cars, boats and planes you have in the garage and the ones you chose, which stamps, achievements, golden pixels, chests and fish you have found, and what Pixel wears (under “g2prog” and “g2wear”), and also the graphics and sound you chose (under “g2q”, “g2qa” and “g2snd”); coins are only earned in the game, and nothing of it is sent to us. When the city is opened from our app, session storage marks that tab as the app (under “prApp”). If you press “Try your picture on the roof” on a plot, your picture, reduced to 512 pixels, waits in that tab’s session storage (under “prTryOn”) and the city uses it for up to 12 hours to put it on the roof; only you see it and it is not uploaded. Pixel Dust (/dust/) keeps its saved game here too (under “prDust:pd_save”); nothing of it is sent to us either.
Account and ownership records are kept as long as your account exists, since a plot's history is part of what owning a plot means on this site. You can ask us to delete your account — see Section 7.
This service is not directed at anyone under 18. We don't knowingly collect data from anyone under 18. If you believe a minor has created an account, contact us at support@pixelrealestate.homes and we'll look into it.
We may update this policy from time to time. Material changes will be reflected by updating the "Last updated" date above.
Pixel Real Estate · support@pixelrealestate.homes