Privacy, in plain words

Independent, not the city. Free, no account. Homeabouts is a BYU Law student project testing an idea. It is not a service of Provo City, BYU or the State of Utah. This page lists everything Homeabouts keeps or sends from the app, the sign-up page and the Facebook sign-up form. If the code does something with your information, it is on this page.

The short version

The app needs no account and never asks your name. The Facebook sign-up form asks for your full name, email and street address.
The address you type in the app is used to look up your street. Homeabouts does not keep it. Your phone does, so it can show your street next time. Homeabouts keeps the address from the Facebook form to find your council district and count one entry per address.
Homeabouts keeps your email if you ask for an email, tap "Count me in" in the app, or submit the Facebook form. It uses it only for the emails described below. "Count me in" keeps your email, your council district and your two choices, never your address.
The app counts what gets used, with no name. From October 10, 2026, a random code on your phone lets the project see how one visit leads to the next, for up to 14 days. See "The visit code" below.
Some council cards and project lines in the app are drafted by an AI model from Provo's public documents only, and are labeled "Drafted with AI · not yet checked by a person". Nothing you type is sent to it.
No advertising trackers and no Meta pixel on this page or in the app. If you came from a Facebook or Instagram ad, Homeabouts tells Meta when that visit set an address or tapped "Count me in", with the click code Meta put on the ad's link and your browser type. Never your address, your location, your email or anything you type. See "If you came from a Facebook or Instagram ad" below.
Homeabouts never sells your information. Reports to Provo City use totals, with no names. If you tick the box on the Facebook form, Homeabouts also gives Provo City staff your name and council district in a list of residents who asked.
"Delete your data" in Settings clears what this phone keeps. It also deletes your email from Homeabouts when this phone holds the key for it.

Your address, in the app

When you type an address, the app sends what you type to Homeabouts to find it in Provo's address list and to look up your street: trash day, your council member, what is nearby. Homeabouts answers and does not keep or log the address. It is never saved in the database, with or without your email.

Your phone keeps the address so it can show your street again next time you open the app. It also keeps the last answer about your street for up to 14 days, and shows that saved copy, marked with its date, if the connection is down. "Delete your data" clears both.

From October 14, 2026, "Use my location" is on the first screen for everyone (before that, only on pages opened from an ad). If you tap it, your phone asks you first. If you allow it, your location is sent once to Homeabouts to find the nearest Provo addresses in the city's list. It is not kept, logged or sent anywhere else. You then confirm your address, or type it instead. After that the app knows only the address you confirm, kept on this phone like a typed one.

To show reports near you, Homeabouts asks SeeClickFix, the city's reporting service, about a square of a few blocks around your street. SeeClickFix never gets your address.

Your email

The app works without an email. On the sign-up page and in the app, you can ask for these emails:

On the sign-up page: one email if Homeabouts launches.
On the sign-up page: one more email about the paid test session, if you ticked that box.
In the app: one email when Homeabouts starts sending updates by email, if you tap "Get one email when updates start". Nothing else.
In the app: one email when the City Council sets a date for an item, if you tap "Tell me when the council sets a date" on that item and save your email. Nothing else.
In the app: one email if Provo City connects a sample you asked about, if you tap "Email me if Provo connects it" and save your email. Nothing else.
In the app: if you tap "Count me in" on your street's screen, one email right away to confirm your email address, and one short email a month about what is changing near you only if you ticked that box. See "Count me in" below.

Those are the only emails from the sign-up page and the app. Emails from the Facebook form are described under "The Facebook sign-up form" below.

With an email saved in the app, Homeabouts keeps the day it was saved and which kind of link you first came from (an ad, a card, a shared link). For a date or a sample, it also keeps that item's id or the sample's name. Never your address, and never the visit code.

If you tap "Tell me when the council sets a date" on an item and save your email, Homeabouts keeps your email and that item's id. It sends you one email when the City Council sets a date for that item, and nothing else. If your email was already on file (from another phone or the sign-up page), the item's id is added to it. A sample works the same way, with the sample's name.

If you ask the app to remind you about something, it remembers that item on your phone, and, only if you have asked for an email, a note with Homeabouts of which item you asked about. Because items are near your address, that note shows roughly which part of Provo you live in.

Count me in

From October 14, 2026, your street's screen in the app has a card: "Want your bill, passes and outage alerts here too?" They need Provo City to connect them. If you leave your email and tap "Count me in", Homeabouts counts you as asking Provo to connect, in your council district.

What Homeabouts keeps: your email; your council district (the number, 1 to 5, or none, which the app already knows from your address); whether you ticked "One email a month about what is changing near you" and "Invite me to try new parts first"; the day you signed up; and the day you pressed "Confirm my email", if you do. Never your address, your street, your location or your name. One sign-up per email: a second "Count me in" with the same email changes nothing and sends nothing.

The thank-you email: Homeabouts sends one email, once, to the address you typed, from hello@homeabouts.com, through Cloudflare's email service. It says you are counted, has a link to confirm the email address is yours, and a link to stop any email. Opening the confirm link changes nothing until you press "Confirm my email" on that page. The email has no pictures and nothing that tells Homeabouts whether you opened it.

If you leave "One email a month" unticked, Homeabouts sends you no other email from this card. "Invite me to try new parts first" is kept as your choice; no invite has been sent yet. Totals by council district appear on the public counts page (see "Counts, in the open" below), where any number under 11 shows as "fewer than 11". Homeabouts does not give your email to Provo City.

Say where you stand on a council item (switched off for now)

This part of the app is switched off. When it is on, you can add an answer to some council items without your name: For, Mixed, Against, Need more information, or Does not affect me.

Where it is offered: only on items where the council makes a general rule (an ordinance, a zoning change, a general plan change, a budget, a fee, a resolution that applies to everyone), and only on summaries a person at Homeabouts checked. Not on a hearing about one application, not on a summary drafted with AI that no person has checked, and not once a referendum petition has been filed on the decision. It closes 4 hours after the meeting starts.
What we keep: for each item, how many answers there are for each choice, by Provo neighborhood and by council district. If you write a reason, the reason, with no neighborhood, district, choice or date beside it. A person at Homeabouts reads a reason before any could be shown to others.
While the item is open, two more things: a random receipt for each answer, so the phone that holds it can change that answer; and a one-way code made from a random code your phone keeps for this app, so each phone answers an item once. When the item closes, both are deleted. After that, nothing we keep links two answers to the same phone.
What we never keep: your name, address, email or phone number; your phone's app code itself; the visit code; your connection address (IP address) or device details; the date or time you answered.
We keep no list of who answered and could not produce one. While an item is open, if someone had your phone's app code, we could check whether that phone answered that item; we cannot list who answered.
Your connection: to stop floods of answers, our host, Cloudflare, counts requests from each connection for up to a minute. It counts them under a one-way code of the connection address made with a key that changes every day, and we delete each day's key the next day. Our request logs are switched off. Cloudflare carries every request to this site and sees connection addresses under its own privacy policy.
Small numbers: no count under 11 is shown anywhere, in the app or on the counts page, and a number that would let someone work out a count under 11 by subtracting is hidden too. Small counts can hint at who answered: if only a few people you know use this app, a count could point to them. That is why nothing under 11 is shown. Homeabouts itself can see small numbers in its own database.
Watching the numbers: the public counts page changes once a day. In the app, the numbers on an item change as answers come in, so someone watching at the moment a person they know answers could see which number went up, once the numbers are 11 or more.
Not verified: one answer per phone, as far as this app can tell. Someone who clears this app's data or uses another phone can answer again. These are answers from people using this app who chose to answer, not a vote and not a sample of Provo.
On your phone: your phone keeps your answers, their receipts and the app's random code. "Delete your data" in Settings removes them from the phone. Answers already counted stay counted, without your name.
If a court asked, we would have the counts and the reasons, and while an item is open the receipts and one-way codes. There is no list of who answered.
Counts and reasons are deleted 90 days after the meeting.

Counts, in the open

The page homeabouts.com/counts shows, to anyone, the same numbers for everyone: the answers on council items (while that part is switched on) and the "Count me in" sign-ups, by council district. Every count there is a number of phones or sign-ups, never people. Any number under 11 shows as "fewer than 11", a number that would let someone work out a smaller one is hidden too, and there are no percentages. The page is updated once a day. Opening it is not counted and nothing about the visit is kept.

Drafted with AI

From October 14, 2026, some council cards and project lines are drafted overnight by Claude, an AI model from Anthropic, using only Provo's public documents: the council agenda and the planning map's public summaries. Nothing you type, no address and no email is ever sent to it. Each drafted line is checked against the city's own words by code and by a second model; anything that fails is not shown. Drafted cards say "Drafted with AI · not yet checked by a person". A person's name on an application is left out and becomes "the applicant".

If you came from a Facebook or Instagram ad

If you came from a Facebook or Instagram ad, Homeabouts tells Meta (the company behind those apps) when your visit set an address (typed, or found with "Use my location") or tapped "Count me in", so the project can see which ads work. Homeabouts sends Meta the click code Meta put on the ad's link, the time it happened, and your browser type (the line every browser sends to every website, naming the browser, its version and the phone's system). Homeabouts never sends Meta your address, your location, your email, your council district, your connection address (IP address) or anything you type.

Your phone keeps the click code for 7 days from the tap on the ad, and only to pass it on, so a visit a few days later that sets an address still counts for that ad (Meta credits an ad for 7 days after a tap). After 7 days, or when you tap another Meta ad, or use "Delete your data", it is gone. Homeabouts' server, not your phone, tells Meta, at most once for an address and once for "Count me in" for each tap on an ad. Homeabouts does not keep the click code; it counts only whether Meta was told, and which ad's link it came from (see "What the app counts"). Meta made the click code when you tapped its ad, so Meta can connect what it is told to the account that tapped the ad, and keeps it under its own terms. A visit that did not come from a Meta ad sends Meta nothing. A visit marked as a test is never sent as a real one.

The sign-up page (homeabouts.com)

Your email address, always. A ZIP code, if you choose to add one (it is optional). Who pays the city utility bill where you live, and whether you have followed a city council meeting in the last year: the main sign-up form asks both and requires an answer; a few test cards skip them. If you tick "I'd do a paid 45-minute test session," that is also saved, and we will email you once about it. Anything you type in the optional "one thing you'd want it to tell you" box. Please do not put personal details in that box.

The page also records where a visit came from (an ad, a printed card, or typed in directly), so the project can tell which way of reaching people works. It does not record your IP address or details about your phone or computer.

The app's own email sign-up asks only for your email. It never asks who pays your bill, whether you follow the council or your ZIP code.

The Facebook sign-up form

From October 11, 2026, Homeabouts runs ads on Facebook and Instagram with a "Sign up" button. It opens a form inside Facebook or Instagram, called a Meta Instant Form. It is not the app.

The form collects:

Your full name and email. Meta fills these in from your profile. You can change them before you submit.
Your street address in Provo, which you type.
Which you would use most: your own Provo bill line by line; splitting the bill with the people on it; one login for bill, rec and library; or street work near you before it starts.
Which of the three optional boxes you tick, which ad you came from and when you submitted.

All three optional boxes start unticked:

Share your name and council district with Provo City staff as a resident who wants this connected. Homeabouts shares them only if you tick this box.
Try it first if Provo connects it. If you tick this box, Homeabouts may email you once to invite you if Provo City agrees to a trial.
One email a month about this. If you tick this box, Homeabouts sends at most one email a month about this.

Everyone who submits may also get one email if Provo City agrees to connect it. Homeabouts sends no other emails from this sign-up. Every email has a way to stop them.

Homeabouts downloads the entries from Meta. Meta keeps its own copy under Meta's terms. Homeabouts uses your street address to find your council district (1 to 5) and count one entry per address. Homeabouts never gives your street address to Provo City.

If you tick the box to share your name, Homeabouts gives Provo City staff your name and council district in a list of residents who asked. If you do not tick it, Homeabouts gives staff only counts by council district, with no name. In reports, any total under 11 is shown as "under 11". Homeabouts never sells these entries, uses them for advertising or shares them beyond what is described here.

Homeabouts deletes its copy within 12 months, or sooner if the idea is not taken forward. To be removed sooner, email hello@homeabouts.com from the email you used on the form. Homeabouts deletes its copy within a week.

The form's entries stay apart from the app's counts and its visit code. If you tap the form's button to open the app, the app treats it like any other ad link. The link's code says which ad brought you. The app does not get your name or email from the form.

What your phone keeps

The app keeps these in its own storage on your phone. They stay there, except where a count below says it carries one of them. "Delete your data" clears all of them, except the test marker.

Your address, and the last answer about your street (up to 14 days).
Reminders you set, whether you have set one before, and whether alerts are paused or on.
Your answers (rent or own, the hassle you picked, "Does this matter to you?", the water question and the samples), so they show as chosen.
The day you first opened the app, the code of the link that first brought you here, and which one-time counts were already sent, so none is sent twice.
The visit code and the day it was made.
The key for your email, if you asked for an email and it was new, so "Delete your data" can delete it.
Whether you closed the offer to add the app to your home screen, and how many times you sent Homeabouts to the people at home.
If you split a bill, the day you last did it and how many times.
A test marker for 7 days, only when a link marks this phone as a test (with the list of features being tried, if the link names any). It keeps test visits out of the counts.

While a page opened from an ad stays open, it also remembers that ad's code and item, so a reload opens the same item, and which steps of the visit it already counted, so a reload does not count them twice. Closing the page clears these, and so does "Delete your data". If the ad was on Facebook or Instagram, the phone also remembers, for 7 days, the click code Meta put on the link, the time the page first saw it, which ad's link it was, and whether Meta was already told about an address or "Count me in". After 7 days it is gone; "Delete your data" clears it at once.

If you split a bill, the amounts you type stay on your phone and Homeabouts never sees them. The message you send does include the amount, and you can read and change it before it goes. The link in it has no amount.

Alerts

If you turn on alerts, Homeabouts keeps the push address your browser gives it for this site, its two keys, your council district (the number, 1 to 5, the app finds from your saved address; the address is not sent with it), the day you turned them on and how many alerts you got this week. Alerts are about what the City Council takes up in your council district, at most two a week and never at night. Turning alerts off deletes it.

What the app counts

The app also counts, without your name, email or address. Here is every kind of count, in plain words:

When the app is opened, whether in a browser, from a home screen or inside another app, and whether you came back within 7 or 14 days, and once a week that it was used. A coming-back count also says which week you first came, whether alerts are on, whether you have sent Homeabouts to the people at home, and how many items were near your address (0, 1 or 2 or more).
Which screens you open, which rows on Home you tap, and which council cards you open (by their id). On the map, which pins and list items you tap (by their id).
When an address is set (that one was set, never the address itself), with your council district (1 to 5, also on some other counts), your trash type (cart or dumpster) and how many projects and council items are near it as 0, 1 or 2 or more. Never the street. An address found with "Use my location" is counted the same way, marked as found by location, never with the location.
Your two optional answers, rent or own and the hassle you picked, as a count with no name. If you come back a week or more later, the app may ask the hassle question once more, in the same words; that count carries your first answer with it so the project can see what changed, still with no name. The rent or own answer also rides along on each alerts count and each share and household count, and the hassle you picked on each coming-back count.
The code in the link or printed card that first brought you here, so the project can tell which way of reaching people works. A printed card can be for one building, so that code can name the building but never your apartment or address. Counts of your two optional answers and of coming back keep only the kind of link (an ad, a card, a shared link), not the code.
When you use write, report, reserve, remind, pause, delete, the one-email button, the bill and phone buttons, the bill page's jump to why water costs more, or the library and recreation links.
When you use Tell a neighbor (by the phone's share sheet or by copying, and which item), and Send Homeabouts to the people at home (how many times, as 1, 2 or 3 or more, never who). Each share and household count also says whether your address has a cart (a trash day in the city's list), a shared dumpster or neither, never the address.
If you open a link that a household member sent, which of its three buttons you tap: turn on alerts, add it to your home screen, or not now. Nothing about who sent it is known or kept.
If you split a bill: that you opened the split, worked one out and sent it (by the share sheet or by copying), with how many people (2, 3, 4, or 5 or more), the kind of bill (utilities, internet, rent or other), on how many different days you have split one (1, 2, or 3 or more) and your rent or own answer. Never an amount, and never who it went to.
When alerts are turned on or off, and when an alert is opened (which item it was about).
On the "Count me in" card: that it was shown, that "Not now" was tapped, and a sign-up or a repeat, each with your council district only. Homeabouts also counts each thank-you email sent, failed or not sent (with a reason word such as "switched off"), never the address.
If you came from a Facebook or Instagram ad: each time the app asks Homeabouts to tell Meta, a count of which it was (an address or "Count me in"), the short code of the ad whose link it came from, and whether it was sent, not sent (with a reason word such as "switched off" or "test") or failed. Never the click code.
When the app is opened, whether the visit came from tapping an ad on Facebook or Instagram, as a yes or no (yes when your phone holds a click code from the last 7 days), so visits from people can be told apart from Meta's own systems, which open an ad's link when the ad is published. Never the click code, and never which person.
How the app is used, with PostHog (a company that makes tools for seeing where an app is hard to use): a recording of taps, scrolling and which screens were opened, where on the screen people tap, how fast the app loads on your phone, and when the app breaks (the error, never what you typed). It records this so we can see where the app is hard to use. Anything you type, your address and your email are hidden before anything leaves your phone, and no name is ever sent. It also notes which ad's link the visit came from and whether it came from tapping an ad on Facebook or Instagram, as a yes or no. It goes through Homeabouts' own server, which does not pass on your internet address (IP address), so PostHog does not keep it. Nothing is stored on your phone for it, and each visit gets a new random code, so two visits cannot be linked. Because a recording carries no name or code, it cannot be found again to delete. Visits marked as a test are not recorded.
When the app is offered or added to a home screen, when a request to our server failed (which kind of request, no details), and when an address search found nothing (never what was typed).
If you type an address in a nearby town, like Orem or Springville, which town it was, counted once per visit with the ad that first brought you here (for any other link, only its kind). Never the address. Homeabouts covers Provo only for now; this count shows where people want it next.
Whether you tapped into the address box before an address was set, counted once per phone with the code of the link that first brought you here, never what you typed. (An earlier version showed the ad's item as a card on the first screen and counted a tap on it the same way.)
When you read to the end of a council item, and when you tap Remind me, Write to the council, Send this to a neighbor, Tell me when the council sets a date, Read the city's record or Use my location. Each count says which of these it was, which item (by its id, when there is one) and the ad that first brought you here (for any other link, only its kind). Never the words you write, who you write to, or where you are.
If you answer "Does this matter to you?" on an item (A lot, Somewhat or No), the answer is counted with the item's id and the ad that first brought you here (for any other link, only its kind), and nothing else. This phone remembers your answer so it shows as chosen; a changed answer is counted again.
If you answer "Did you know Provo raised the water rate this year?" (Yes or No), the answer is counted once with the ad that first brought you here (for any other link, only its kind), and nothing else is kept. This phone remembers your answer so it shows as chosen; only a changed answer is counted again.
From October 11, 2026, on a page opened from an ad, the app also counts the steps of a visit, so the project can see where people stop. Each count is one step, with the ad that first brought you here (for any other link, only its kind), and nothing about you. The steps:
- In the address box: that you tapped into it, that you typed a first letter (never what you typed), that suggestions were shown (as 1 to 3, or 4 or more), that you picked one, that the button found your address, that nothing matched, that you tapped the button with the box empty, that the lookup failed (and whether it took too long, lost the connection or was busy), that you emptied the box, or that you closed the page with no address set (and which of these steps came last before that).
- After "Use my location": whether your phone said no, could not find a location or took too long, whether a Provo address was near, whether "Is this your address?" was shown, and whether you tapped Yes or No. Never the location.
- When the page is closed or another app comes in front: which screen was showing, about how long it had been showing (under 5 seconds, 5 to 15 seconds, 15 to 60 seconds, 1 to 5 minutes, or longer), whether an address was set, and whether this was the first, second or a later time the page went away.
- Before an address is set: how far down a screen you scrolled (a quarter, half, three quarters or all of it), and which buttons and links you tapped, each by a fixed name, such as "Use my location" or "Read the full record". Never the words you type or write.
Each step is counted once per visit, except the page being closed or another app coming in front, which is counted each time (at most five times each time the page is opened). These counts never keep what you typed, where you are, the exact time or anything about who you are. Like the other counts, they carry the visit code (see below). From the same day, the counts of which screens you open and of an address search that found nothing also carry the ad that first brought you here (for any other link, only its kind).
If you answer “Would you use this if Provo connected it?” on a sample, the answer (Yes or No) is counted with the sample’s name, where it was shown (first on the page, second, from a line under another sample, on Home or in the list) and the ad that first brought you here (for any other link, only its kind). Seeing a sample, opening one, skipping one and tapping a button inside one are counted the same way. This phone remembers your answer so it shows as chosen; a changed answer is counted again. If you then type an address, one more count for each sample you answered says which sample and how you answered, with the same ad or kind of link. None of these counts carries your name or your address. If you tap “Email me if Provo connects it” and save your email, the app keeps your email, the sample’s name and which kind of link you first came from, and sends that one email only if Provo City connects that sample.

The visit code

From October 10, 2026, the counts above carry a random code that the app makes on your phone: 20 letters and numbers, picked at random. It lets the project see how one visit leads to the next. For example: did someone who read an item come back a few days later and set an address?

The code is not your name, email, phone number or address, and nothing in it comes from you or your phone. It is kept only with the counts, never with an email, and the counts sent when you save an email carry no code. It goes only to Homeabouts, never to Meta, Google, SeeClickFix or the city. After 14 days your phone replaces it with a new code, and nothing connects the two. "Delete your data" clears it. Counts from before October 10, 2026 have no code.

What this means for you: for up to 14 days, the counts from your phone can be put together. Together they show one phone's steps, such as which ad brought it, its council district, its trash type and what it tapped. Because the items it opened are near its address, the steps together can show roughly which part of Provo it is in. Never a name or an address. If you open the app in another browser, or first inside Facebook or Instagram and later in Safari, each one gets its own code.

Times, tests and totals

Each count from the app keeps only the hour it happened, and an email saved in the app or a reminder note keeps only the day. The sign-up page's entries and visit counts, and the count made when a printed card or ad link is opened, keep the full time. Counts from one phone can be matched to each other for up to 14 days through the visit code. The app's counts and emails are kept apart and never put together: the app's counting never reads the email list.

A link marked as a test (for 7 days) and the same check used against automated visits on the sign-up page keep test and bot traffic out of these counts. Totals may appear in a report to Provo City or to the project's grant, and any total under 11 is shown as "under 11". The Facebook form's list of names and council districts is separate and includes you only if you tick the box to share your name.

The ads

Homeabouts takes no side on any council item. Its ads say the same facts more than one way so more neighbors see them. Some ads open the Facebook sign-up form. Ads that link to the app use a short code that says which ad it was. Meta's tracking pixel is not on this page or in the app. What Homeabouts tells Meta about a visit from its ad is under "If you came from a Facebook or Instagram ad" above.

Who sees it

The BYU Law student running Homeabouts and the software tools used to run this page and the app, which include AI tools, handle your information. The AI model that drafts council cards and project lines (Anthropic's Claude) gets only Provo's public documents, never your information. Cloudflare's email service carries the "Count me in" thank-you email. Meta is told when a visit from its ad set an address or tapped "Count me in", as described above. Homeabouts never sells or rents your information. Homeabouts shares it only as described on this page. This includes your name and council district with Provo City staff only if you tick that box on the Facebook form. Meta also keeps its own copy of the form's entries under its terms.

Where it is stored

The sign-up page and the app use a database hosted by Cloudflare, a US company that also serves this page and the app. The database service keeps a restore copy for 30 days, and it cannot be switched off. For those 30 days, someone with access to the Homeabouts account could restore an earlier copy and see what the database held then, for example roughly when a count changed. Homeabouts downloads the Facebook form's entries from Meta, which also keeps its own copy under its terms. No advertising tracker or outside script runs on this page or in the app.

How long

Homeabouts deletes its copies of sign-ups and one-email entries within 12 months, or sooner if the idea is not taken forward. Backups can take up to 30 days to clear after a deletion. Deletion also happens sooner when you ask (see "Your choices" below).

One sign-up per email, on the sign-up page and in the app

If an email is already on file, a second sign-up or one-email request with the same address is recorded as a repeat (so we know you tried again), but no new, separate entry is created, and the app is not given a key to change or delete that earlier entry on its own. If that happens to you in the app, email us (below) to make any change or deletion.

Your choices

From the sign-up page or the Facebook form: to be removed at any time, email hello@homeabouts.com from the email you signed up with. Homeabouts will delete its copy within a week.

From the app: Settings has a "Delete your data" button. If the app has a key for you (you asked for an email and it was a new email), this deletes your email, your "Count me in" sign-up and anything you asked to be reminded or emailed about from our side at once, and clears everything this phone remembers, the visit code included. (A backup copy can still exist for up to 30 days; see "How long" above.) If the app has no key (you never asked for an email, or your email was already on file from somewhere else), this only clears what this phone remembers; for anything held on our side, email hello@homeabouts.com.

Counts already sent by the app stay counted. They carry no name, so they cannot be found or removed.

Questions

hello@homeabouts.com

Last updated October 14, 2026.