How to reach a person about this app

tajbrah@quotograph.io, for anything at all: a bug, a number that looks wrong, a question about what the app is, a privacy question, or something on a screen that a screen reader or a keyboard cannot get to.

It is the same address this website shows you if a page fails, the address the phone app’s About screen sends you here to find, and the one on the store submission, so there is one inbox rather than several that disagree about who is watching.

There is deliberately no form on this page. Nothing in this build stores what a form receives, so a support form would take your message, tell you it had been sent, and drop it. A mail client you control at least leaves you holding the evidence that you wrote.

None of this is mandatory and a one-line report is still worth sending. It is listed because these are the five things that decide whether a problem can be reproduced.

• Where you were. The address in the browser bar, or the name of the tab and screen in the phone app.
• What you expected and what happened instead. The gap between those two is the report; either on its own usually is not.
• Whether it happens again. A problem that repeats on demand is fixable in an afternoon. One that happened once is worth sending anyway, marked as such.
• The browser and operating system, or the phone. Half of the problems that reach one person and nobody else are one of those two.
• Any figure you are disputing, as it appeared on screen. The figures in this app are estimates built from the assumptions shown beside them, so the assumptions are half of the evidence.

One more, if you got an error panel rather than a page. It ends with the word reference and a short string of characters, and that string is worth copying exactly. It identifies the one failure you hit rather than the page it happened on, which makes it the only part of a bug report that cannot be typed from memory.

Nobody you were writing to received it. That is the build rather than a fault, and it is worth knowing before you wait on a reply. One message can still leave, and it is the copy addressed to you rather than the one addressed to them.

• A viewing request is checked, echoed back to you and discarded. The response calls it a draft rather than a sent message, because nothing left.
• An insurance quote request is turned into a summary and handed back to you. The form then offers you a mail link, so that if it goes anywhere you are the one who sent it.
• An advisor introduction is composed and returned to you. The advisor records in this build carry no email address or phone number to send it to.
• A tradesperson’s application to join is held in the memory of the one server process that received it and goes when that process does. The response says so.
• A quote request to a trade and an inspection booking are the only two with an email path at all, and half of that path is shut. The message to the trade or the inspector is not sent: the delivery code refuses to mail a seeded record under any configuration, and every trade and inspector in this build is one. The confirmation copy addressed to you is a separate send with no such check on it, so on a deployment that has the two environment variables the path needs, that copy goes out through an email provider, carrying your name, your email address and, for an inspection, the property’s street address and your access notes. With either variable absent nothing is attempted at all and the response reports the delivery as not configured rather than as sent.

So the honest answer to “did the trade, the inspector or the advisor get my request” is no. The only message that can leave is the receipt addressed to you. If you meant to reach a person, the address at the top of this page is the way, and it is the only one. The privacy policy sets out what that receipt carries and which provider it goes through.

There is no account here and no server-side copy of anything you have entered, so there is nothing to ask anybody to delete on your behalf. What the app keeps is written by your own browser, or by the phone app into the phone’s own preference store, and it is yours to remove.

Your file lists every key the website writes, what is in each one on this device right now, what deleting it costs you, and a control that deletes it. Clearing your browser data removes all of it at once. In the phone app each item has its own clear control, and uninstalling takes the rest.

The privacy policy lists the keys in full, names the one cookie this build sets and when, and states which third parties see a request. It also marks the clauses a lawyer still has to write, which includes how to make a formal access or deletion request. Until that is drafted, a request sent to the address above reaches the operator directly.

The listings in this build are seed records, labelled as seed data on the card and on the listing page. They are not live MLS listings, the addresses do not describe houses that are on the market, and their prices and sale histories are generated to be plausible rather than true. The tradespeople, advisors and market statistics are seeded in the same way and marked the same way.

Mortgage figures are estimates for illustration only and are not a loan offer or financial advice. The arithmetic is real and runs against published Ontario and federal rules, and the assumptions behind each figure are printed next to it.

Which makes the split worth stating. That a price looks wrong for a neighbourhood, or that an address is not a real house, is the seed corpus behaving as described, and nothing needs reporting. That a figure disagrees with the assumptions shown beside it, that a page fails, that a control cannot be reached by keyboard or announced by a screen reader, or that a statement on this page or the terms of use contradicts what the product does, is a defect, and the code is the evidence.

There is no account, no sign in and no demo account, because the product has no authentication at all. Every screen is reachable from a cold install with no credentials. There is nothing to buy and no subscription.

Some deployments of the website sit behind a single shared password while the build is unreleased. This page, the privacy policy and the terms of use are exempt from it by design, so if every other page sends you to a password form, the origin you were given still has that password set. That is a deployment setting rather than anything in the app, and the address at the top of this page is the way to say so.