Privacy Policy

It covers two groups of people with different rights, so it matters which one you are in.

If you use Qwalify because you work at a brokerage that subscribes, Qwalify LLC is the controller of your account details: your name, your email address, your password, your role and what you did in the product.

If a brokerage holds your details in Qwalify because you are a borrower, a lender representative or a contact in someone's book, the brokerage is the controller and Qwalify is their processor (a "service provider" in California's terms). We act on their instructions. That includes clients who upload documents through a brokerage's request link. Requests to see, correct or delete that information should go to the brokerage, and we will help them answer you.

If you join our launch list, Qwalify LLC is the controller of the email address you give us.

Qwalify is a business product. It is not meant for anybody under 18, and we do not knowingly collect information from children.

Account details: name, email address, a hashed password, an optional photo, job role, team membership, and two-factor secrets if enabled.

Deal records the brokerage enters: borrowers and their contact details, properties and addresses, loan amounts and terms, lenders, notes, milestones, tasks, deal chat messages and uploaded documents. A property can also hold its public record (parcel number, size, year built, last sale, tax and assessed values) and its location, when somebody looks it up or chooses a suggested address.

Details from people a brokerage asks for documents: when somebody uploads through a brokerage's request link, their name, email address and the files they send.

Operational records: what AI actions were run and what they cost, how much storage is used, notifications, bug reports and feedback (with a screenshot when the sender includes one), and the log of any time Qwalify staff viewed the product as a user.

If you join the launch list on our website, your email address, so we can tell you when sign-up opens.

The product has no field for government identification numbers, bank account numbers or card numbers. Documents are different: bank statements, tax returns and similar files that a brokerage or its clients upload often contain them. Those files are kept in private storage that only that brokerage's account can reach, and files a client sends through a request link are checked for malware before anybody can open them.

Qwalify runs on other companies' infrastructure. These are all of them, and what each receives.

• Supabase

  Hosts Qwalify's database and file storage, and handles sign-in.

  Everything held in Qwalify: deal records, uploaded documents, names, email addresses, hashed passwords, two-factor secrets, team and seat records, usage metering and the audit logs.

• Anthropic

  Runs the AI features: reading a pasted inquiry, reading a business card or email signature into a contact, reading a screenshot or photo into the people on a deal, shortlisting lenders, reading a meeting's transcript to write its note and suggest updates, reading a recorded loan's note, statement or payoff letter to propose its terms, and analysing a bug report for the Qwalify team once it is sent.

  Only what the action being run needs: the inquiry pasted in, the card, signature, screenshot or photo, the property's address and figures, the deal criteria and lender book being matched, a meeting's transcript with the deal's status, milestones, team and open tasks, or the text of a loan document somebody chose to read, with Social Security, taxpayer, account, routing and card numbers hidden first (the PDF itself only for a scanned document, and only after they agree), or a bug report's description, page and browser details and recent errors, with those numbers, email addresses and sign-in tokens hidden, and its screenshot as taken when one was included (never the reporter's name, email or firm).

• Property records provider

  Supplies the property records behind Qwal Advanced Research: a property's public record (parcel number, ownership, size, year built, zoning, recorded mortgages, sales, assessments and tax history), when somebody asks for them on that property.

  The property's street address and unit, city, state and ZIP code. No names, contact details, deal figures or documents.

• Rentometer

  Supplies the rent comparables and rent ranges behind Rental Market, when somebody asks for them on a property.

  The property's address, the number of bedrooms, and optionally the number of bathrooms and whether it is a house or an apartment. No names, contact details, deal figures or documents.

• Google (Maps Platform)

  Suggests US addresses as somebody types a property's street and confirms the one they choose (its standard form, county and location). Places a property's address on the map and supplies the Street View, satellite and map images shown for a property that has no photo.

  What is typed in a property's street address box, the address chosen, and a property's address and map location for its images. No names, contact details, deal figures or documents.

• Google (Gmail)

  Lets a person connect their own Gmail or Google Workspace mailbox, if they choose to, so emails about a deal show on that deal.

  The person signs in at Google, not at Qwalify. Qwalify then sends Google its requests to read that mailbox, using the permission the person gave. Nothing is written into the mailbox.

• Microsoft (Outlook and Microsoft 365)

  Lets a person connect their own Microsoft 365 work or school mailbox, if they choose to, so emails about a deal show on that deal.

  The person signs in at Microsoft, not at Qwalify. Qwalify then sends Microsoft its requests to read that mailbox, using the permission the person (or their company's admin) gave. Nothing is written into the mailbox.

• AssemblyAI

  Turns a recorded or uploaded meeting into a transcript with speakers labelled, and shows a live transcript during the meeting when that is turned on.

  The meeting's audio, which can include anything said in it, such as names, financial details and account numbers. Qwalify asks AssemblyAI to delete each transcript once Qwalify has its copy.

• Plivo

  Places calls made with Call & record: rings the caller's own phone, connects the person called, plays the recording notice and records the call so it can be transcribed on the deal.

  The caller's own phone number (confirmed with a one-time code), the number called, and the call's audio, which can include anything said on it. Qwalify asks Plivo to delete each recording once Qwalify has its copy.

• Resend

  Delivers Qwalify's email: password resets, email address changes, sign-up and trial notices, document requests and launch-list confirmations.

  The recipient's email address and the contents of that message.

• Amazon Web Services (GuardDuty)

  Checks files that clients send through an upload link for viruses and other malware before they can be opened.

  A copy of the file's contents, under a neutral name (not the client's file name), in a private storage area of Qwalify's own AWS account. The copy is deleted as soon as the check is done, and in any case within a day; the file itself stays in Qwalify's storage.

• Stripe

  Takes subscription payments and hosts the pages where a card is entered and a subscription is managed.

  The account holder's email address, which seats are being bought and how many, and an identifier for the account. Card details are entered on Stripe's own pages and never reach Qwalify, which holds only Stripe's identifiers for the customer and the subscription.

• Federal Reserve Bank of St. Louis (FRED)no personal data

  Supplies published rate indexes such as SOFR and Prime.

  Nothing. Qwalify reads public economic series; no customer data is sent.

A person using Qwalify can connect their own Gmail or Microsoft 365 mailbox, so that emails about a deal show on that deal. It is optional, each person connects only their own mailbox, and they sign in at Google or Microsoft, not at Qwalify. Connecting asks only for permission to read email. Qwalify never changes, moves, labels or deletes anything in a mailbox.

Sending is a separate permission that a mailbox's owner can turn on for their own mailbox. With it on, Qwalify sends a reply only when that person writes it and presses Send, from their own mailbox, to the people they chose. Nobody else can send from it. A file attached from their computer for a reply is held only until the reply is sent, and deleted within a day if it is not.

What Qwalify keeps from a connected mailbox is the outside of each message: who sent it and to whom, when, the subject, a short preview, and the names and sizes of any attachments. It does not keep a message's body or its attachments. When somebody opens an email in Qwalify, the body is fetched from Gmail or Outlook at that moment and shown, not stored. An attachment is fetched the same way when somebody opens it, and is kept only if a person saves it to the deal's Files, where it is checked for viruses first. Searching older email for a deal looks in the searcher's own mailbox; what it finds is shown, not kept, unless they add it to the deal. The permission Google or Microsoft gives Qwalify is stored encrypted, and is never sent to a browser.

To suggest which deal an email is about, Qwalify compares those same details (the subject, the preview, who was on it, when it was sent, and attachment names) with the firm's own deals: a deal number, a property address, a borrower or a Deal Person, and when the deal began. It does not read message bodies to do this. When it is not sure, the email waits for a person on the deal to approve it or turn it away.

An email shows on a deal only to people who can already see that deal. The person who connected a mailbox can disconnect it at any time, which stops Qwalify reading it and deletes the permission, or remove it, which also deletes everything Qwalify kept from it. The email itself stays in Gmail or Outlook, untouched.

Email from a connected mailbox is not used for advertising, is not sold, and is not used to train any AI model, ours or anybody else's. Qwalify staff do not read it, except with the mailbox owner's permission for a support question, where security requires it, or where the law does.

Qwalify's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Information from Microsoft is held to the same rules.

Qwalify uses only the cookies it needs to sign you in, keep you signed in, remember which brokerage you are working in and remember a device you have trusted for two-factor sign-in, plus one that lasts ten minutes while you connect a mailbox. Your browser also keeps display preferences, such as the theme. There are no advertising or analytics cookies and no third-party trackers, so we do not respond differently to "Do Not Track" signals: there is no tracking to turn off.

A subscription is paid by card, and the card never reaches us. The number is typed on a page Stripe serves, at a Stripe address; what comes back to Qwalify is an identifier for the customer and the subscription. We could not show you your own card number if you asked.

What we do hold is what you bought and what it costs: how many seats of each kind, when the period ends, and whether the last payment succeeded. A failed payment makes an account read-only after Stripe stops retrying; it does not lock anybody out, and nothing is deleted.

A few places in the product build a link to somewhere else. A property shows a "map" link to Google Maps, and that link contains the property address. A lender or contact can hold a LinkedIn profile link. A lender rep's NMLS or DRE badge links to that license's public record on NMLS Consumer Access or the California Department of Real Estate, and that link contains the license number.

Qwalify sends nothing to any of them. Your browser does if you click, and at that point Google sees the address you clicked from. We mention it so it is clear what our server sends (nothing) and what your click sends.

Address suggestions while you type a property's street come from Google through our server, as listed above, and are also covered by the Google Privacy Policy.

These features send data to Anthropic's API: reading a pasted inquiry into a deal, reading a business card or email signature image into a contact, reading a screenshot or photo into the people on a deal, researching a property record, shortlisting lenders for a deal, writing a meeting's note from its transcript, and reading a recorded loan's note, statement or payoff letter. Each sends only what that action needs, and only when somebody runs it. One more runs on its own, for the Qwalify team: analysing a bug report once it is sent.

Reading a loan document sends its text, with Social Security, taxpayer, bank account, routing and card numbers hidden first on our own server, so they are never sent. A scanned document, whose pages are pictures, is sent as the PDF itself, and only after the person reading it agrees and is told that numbers in pictures cannot be hidden. What Qwal reads is a proposal: nothing is saved to the loan until somebody approves it, field by field.

Analysing a bug report sends what the report says, the page and browser details it was sent with, and the errors the page had just run into, with Social Security, taxpayer, bank account, routing and card numbers, email addresses and sign-in tokens hidden first. A screenshot, when the person included one, is sent as it was taken, so whatever was on screen is sent with it. The name, email address and firm of the person who sent it are not. The analysis helps the Qwalify team fix the problem; it changes nothing in your account.

None of these features performs a web search. Researching a property with Qwal Advanced Research sends its address to the property records provider listed above, and no model is involved.

Nothing in Qwalify is used to train models: not ours, because we do not train any, and not Anthropic's, under the terms we use their API on. AI output is a draft for somebody to check, never a decision. No lending decision is made by a model.

Within a brokerage, access follows the roles the brokerage sets. Records are scoped to the account that owns them; nobody at one brokerage can read another's.

Qwalify staff can view the product as a user in order to help with a support question. That session is read-only, expires after thirty minutes, requires a written reason, and is recorded permanently with who did it, whose account, when and why. The person being viewed as sees a banner throughout.

Passwords are stored hashed, never in a form anybody can read. Two-factor authentication is available to every user, and once somebody turns it on, their sign-in needs it. Sessions last twelve hours and end when the password changes.

A browser cannot reach the database at all: every table has row-level security switched on, and the roles a browser could hold have no access to any of it. Only Qwalify's servers connect to it. For deal and directory records, the database also checks every row against the signed-in person's brokerage and role, as well as the application doing so.

Data is stored in the United States and encrypted in transit and at rest. If we confirm that a brokerage's data has been accessed without authorization, we will tell that brokerage without undue delay and help it meet any duty it has to notify its clients or regulators.

Deal records last as long as the brokerage keeps them. They can delete any record at any time, and deleting it removes it from Qwalify.

If a subscription ends, the brokerage's data remains available for thirty days so they can export it, and is deleted after that on request or within a further sixty days. Copies in backups are overwritten on their normal cycle.

Account details are kept while the account is in use. Billing records are kept for as long as tax and accounting law requires. A launch-list address is kept until sign-up opens and you have been told, or until you ask us to remove it.

The impersonation log is never deleted. That is the point of it: a record of staff access that could be pruned would not be evidence of anything.

If Qwalify holds your account details, you can see them, correct them or ask us to delete them using the contact route at the foot of this page. If a brokerage holds your details as their client, ask them. They control that record, and we will help them act on it.

We do not sell personal information, and we do not share it for advertising. There is no advertising in Qwalify.

California residents have the right to know what personal information we hold about them, to correct it, to have it deleted, and not to be treated differently for asking, to the extent the law gives those rights. We will confirm who is asking before we act, and answer within the time the law sets.

If this policy changes in a way that affects what we do with personal information, we will tell account owners by email before it takes effect rather than only changing the date at the top.