Privacy
Grillow is a public forum about property listings. This explains what we collect, who else sees it, and how to get rid of it. It is written to be read rather than to be defensible, so where something is awkward it is said plainly.
The short version
- You sign in with Google, or with an email address and a one-time code. With Google we receive your name, email and picture; with a code, only the address you typed.
- Your email is never shown to anyone and is never sold or shared for marketing.
- What you post is public: your display name, your picture, your comments, any GIF you attach, and your votes. That is the point of the site.
- You choose the name and picture people see. They do not have to be the ones on your Google account.
- We run no analytics, no tracking pixels and no advertising today.
- If we ban an account we keep a one-way fingerprint of its email address so it cannot sign up again. It cannot be read back or used to contact anyone.
- You can delete anything you have written, or your whole account, at any time. See Deleting your data.
Who we are
Grillow operates grillow.xyz and the Grillow browser extension, and is the data controller for the information described here. Write to privacy@grillow.xyz about anything on this page.
What we collect
When you sign in
Signing in is handled by Supabase Auth, either through Google or by emailing you a one-time code. There is no password either way, so there is none for us to store or for anyone to steal. We store when the account was created and when it last signed in.
With Google we receive your email address, an account identifier, and the name and profile picture on that account. With a code we receive only the address you typed — no name and no picture, so the profile starts empty and you fill in what you want people to see.
The form that sends the code is protected by Cloudflare Turnstile, which checks that a person rather than a script is asking. It runs in your browser before the code is sent, sets no advertising cookie and does not track you across sites; it exists so nobody can use our sign-in form to send mail to other people. Delivery of the code itself is handled by Resend, which processes your address for the sole purpose of delivering that message.
Your email address identifies your account and lets us reply to you about it. It is not displayed anywhere on the site, is not visible to other people, and is not used for marketing.
Your profile
A display name and a picture, yours to change at any point. Signing in with Google seeds both from that account; signing in with a code seeds neither, because an email address is all we were given. If you upload your own picture, it is cropped square, resized to 128 pixels and stored in our database as image data rather than as a link to somewhere else. If you keep the one from Google, we store the link and your browser loads it from them.
What you post
Comments and replies, any GIF attached to them, which comments you have liked, and your cookedness votes on listings. Each is stored with your account, the time, and the listing or photo it belongs to. All of it is public and attributed to your display name and picture.
Likes and votes are shown as totals. Nobody is told who liked or voted for what — the database aggregates before anything is sent to a browser.
Listings
We store a listing’s Zillow link, its address, the address of its preview photograph and its asking price. That is information about a property, not about you, and it is public.
It reaches us two ways: somebody submits a link on this website, or somebody with the Grillow extension opens the listing on Zillow, where the extension reads those details off the page and sends them here. The extension already asks us for that listing’s comments in order to show them to you, so opening a page tells us nothing it was not already telling us. We do not record who supplied any of it — the listings table has no column for a person, so this builds no history of what anybody browsed.
Technical information
Our host, Vercel, records ordinary server logs for each request: your IP address, browser user agent, the page requested and the time. Supabase records similar logs for database and sign-in requests. These exist to keep the service running and to investigate abuse, and they are kept for a short period by those providers.
We run no analytics. There is no Google Analytics, no tracking pixel, no heatmap, no session recorder and no third-party script measuring what you do here.
Cookies and browser storage
Grillow does not set advertising or analytics cookies. Your signed-in session is kept in your browser’s local storage rather than in a cookie — that is what keeps you signed in between visits, and clearing your browser data signs you out.
The Grillow extension stores the same session in the browser’s extension storage, so that signing in on one surface signs you in on the other.
Who else sees your information
We do not sell your personal information, and we do not share it for advertising.
These companies are involved in running Grillow:
| Who | What they receive | Why |
|---|---|---|
| Supabase | Everything described above — they host the database and handle sign-in | It is where Grillow’s data lives |
| Vercel | Request logs: IP address, user agent, page, time | They serve the website |
| Google / Meta | That you signed in to Grillow, if you use their sign-in. Your profile picture request, if you kept theirs | They authenticate you |
| Cloudflare | Your IP address and user agent when the anti-spam check on the email sign-in form runs | It is what stops our sign-in form being used to send mail to people who did not ask for it |
| Resend | Your email address, when you ask for a sign-in code | They deliver the email carrying the code |
| Zillow | Your IP address and user agent when a listing photograph loads | Listing photographs are displayed from Zillow’s servers rather than copied onto ours |
| GIPHY | Your IP address and user agent when the GIF picker loads or a GIF is displayed, and anything you type into the picker’s search box | GIFs come from GIPHY’s library and are displayed from their servers |
Because photographs and GIFs load from Zillow and GIPHY directly, those companies can see that a request came from your browser. We send them nothing about you beyond what any embedded image discloses, and we ask browsers not to pass on which page you were reading.
We may also disclose information if the law requires it, or to investigate abuse of the service. If that ever happens we will tell you unless we are prohibited from doing so.
Advertising
Grillow does not currently show advertising. If that changes it will be through Google AdSense, this page will be updated before any advertisement appears, and the following will apply:
- Google, as a third-party vendor, uses cookies to serve ads on Grillow.
- Google’s use of advertising cookies enables it and its partners to serve ads based on your visits to Grillow and other sites.
- You can opt out of personalised advertising in Google’s Ads Settings, or opt out of third-party vendors’ use of cookies at aboutads.info.
- Visitors in the UK and EEA will be asked for consent through a Google-certified consent tool before any personalised advertising cookie is set.
Why we are allowed to hold this (UK and EU)
- To perform our contract with you — your account, your profile, and posting, liking and voting. Without these we cannot provide the service you signed in for.
- Our legitimate interests — keeping the site working, keeping it secure, and investigating abuse. We have considered your interests and think a small volume of server logs is proportionate to those aims.
- Your consent — for advertising cookies, if advertising is ever introduced. You may withdraw it at any time.
Your rights
Wherever you are, you may ask us to:
- tell you what we hold about you, and give you a copy;
- correct anything that is wrong;
- delete your account and everything on it;
- stop using your information for a particular purpose;
- export what you have posted in a machine-readable form.
Write to privacy@grillow.xyz from the address on the account you signed in with. We will respond within 30 days and will not charge you.
If you are in the UK or EEA and think we have got something wrong, you may complain to your data protection authority — in the UK that is the Information Commissioner’s Office. We would rather you told us first.
If you are in California, you have the right to know what we collect, to delete it, to correct it, and not to be treated differently for asking. We do not sell personal information and we do not share it for cross-context behavioural advertising. If advertising is introduced, an opt-out will be offered here before it starts.
How long we keep things
- Your account and profile — until you delete it.
- A comment you delete — hidden from everyone immediately. The row is kept so that a deletion made by mistake can be undone, and so that a comment cannot be erased out from under a report. It is removed permanently when you delete your account.
- Your account, when you delete it — removed within 30 days, and normally within a few days. Nothing is kept behind the scenes.
- Backups — our database provider keeps encrypted backups. Deleted information may persist in those for up to 30 days before ageing out. It is not accessible to the site during that time.
- Server logs — kept briefly by Vercel and Supabase under their own retention policies.
- If your account is banned — we keep a one-way fingerprint of your email address, indefinitely, so the same address cannot be used to open a new account. It is a hash, not the address: it can be checked against an address somebody types, and it cannot be turned back into your address or used to contact you. Nothing else about a banned account is retained beyond the rules above. If a ban is lifted, the fingerprint is deleted.
Children
Grillow is not for children. You must be at least 13 years old to use it, or 16 if you are in the UK or the EEA. We do not knowingly collect information from anyone younger. If you believe a child has an account, write to privacy@grillow.xyz and we will remove it.
Where your information is held
Our database and hosting are in the United States. If you are in the UK or the EEA, that means your information is transferred outside your country; those transfers rely on the standard contractual clauses our providers have in place.
Security
Every table is protected by row-level security in the database, so what a browser can read or write is enforced by the database rather than by the app. Traffic is encrypted in transit. The credential that could bypass those rules is never sent to a browser and is not in our source code.
No service is perfectly secure. If something goes wrong that affects you, we will tell you and the relevant authority as quickly as we can.
Changes
When this changes, the date at the top changes. If a change materially affects what we do with your information, we will say so on the site before it takes effect.
Contact
privacy@grillow.xyz for anything on this page. support@grillow.xyz for everything else.