Privacy
URLQ connects a printed code to a web page and gives the business that printed it a record of the interest it produced. This page describes exactly what that involves.
When you scan a code or open a property page
The redirect and the page record that a scan and a page view happened, which printed placement they came from, your browser’s user-agent string, and the country Cloudflare reports for the connection.
Those are URLQ’s first-party buyer-action records: they help the publishing business understand which printed placement led to a visit and which voluntary buyer actions followed. Separately, URLQ uses Google Analytics across the site. By default, Google Analytics uses a first-party _ga identifier/cookie and collects page and on-site activity, approximate geolocation, and browser/device information for product and marketing analytics. Google says GA4 discards IP addresses before logging, but IP addresses are processed at collection. Google Analytics is not the source of the listing’s URLQ buyer-action records.
URLQ’s own first-party database does not store your raw IP address. For URLQ’s first-party records, it is combined with a secret salt and hashed, and only that hash is written. The hash lets URLQ tell one visitor’s actions apart within a listing; it cannot be turned back into an address. This statement describes URLQ’s database and does not override what a separate processor, such as Google Analytics or Cloudflare, may process under its own service terms.
Browsing a property page does not create a contact record, does not tell the agent who you are, and does not subscribe you to anything.
When you send your details
A contact form sends what you type — typically a name, a phone number, an optional email address or messaging ID, how interested you are, and any message — to the business that published that listing. That business, not URLQ, decides how to follow up.
Automated follow-up messages are separate and off unless you tick the follow-up box. Every follow-up email carries an unsubscribe link, and every follow-up text can be stopped by replying STOP.
When you use Property Concierge
Before a Concierge question is sent to an AI service or stored by URLQ, URLQ removes email addresses and phone-like contact details. The minimized question, together with the listing context that is already public, is sent to OpenAI so it can produce a grounded answer.
URLQ stores the minimized question, the answer, its citations and source information, and audit metadata in a private property session for up to 90 days after your last question. The session is then deleted. You can clear your current property session earlier using the Concierge control.
The listing Realtor can see aggregate topics and, at most, a bounded set of recent unique minimized question samples. URLQ does not attach Concierge answers, your name, contact details, or a buyer identifier to those samples. Avoid typing other personal information in a question because the minimizer is designed specifically for email addresses and phone-like details. Asking a question does not create an inquiry or share contact details. A request for a Realtor reply is shared only if you separately submit the Realtor inquiry form.
Who else processes this data
URLQ runs on services that necessarily see some of it:
Cloudflareserves the redirect and the public pages, and reports the connection country.
Resenddelivers email that URLQ sends.
Twiliodelivers text messages, where a business has enabled them.
Stripehandles payments, where a page collects one. Card details go to Stripe directly and are never stored by URLQ.
Google Analyticsprovides site-wide analytics using its default first-party _ga identifier/cookie, page and on-site activity, approximate location, and browser/device data. Google says GA4 discards IP addresses before logging, although it processes them at collection.
OpenAIprocesses minimized activity summaries, follow-up drafts, and Property Concierge questions and listing context.
What is sent to OpenAI
URLQ uses OpenAI for a plain-language activity summary for the business and a draft follow-up message that a person reviews before sending. These existing features use a deliberately reduced payload containing scan, visit, and enquiry counts, the listing’s own details, a first name, an interest level, a status, and any message you typed.
It does not contain your phone number, email address, messaging ID, database identifier, or the business’s private notes about you.
URLQ uses the OpenAI API, not the consumer product. For Concierge requests, URLQ explicitly asks the Responses API not to store application state. OpenAI API content is not used for model training by default, but abuse-monitoring logs may retain customer content for up to 30 days unless legally required to retain it longer. URLQ has not enabled Zero Data Retention (ZDR). If that changes, this notice and its version change with it.
How long data is kept
Minimized interaction events — including scans, page views, enquiry counts, and Concierge topic and answer-class markers — are kept for 24 months and then deleted.
Contact records, and the summaries generated from them, are kept while the publishing business’s account is active. They are deleted within 90 days of that account closing, or of a deletion request being completed.
One exception: if you unsubscribe, a minimal record of that choice is kept indefinitely, because it is the only way to keep honouring it.
Your choices
You can decline to submit a form and still read every property page. You can leave the follow-up box unticked and still send an enquiry. You can unsubscribe from follow-up messages at any time using the link in the message.
To ask for access to, correction of, or deletion of your information, email privacy@urlq.com. URLQ acknowledges a request within 5 business days and responds substantively within 30 days. Where a request concerns a listing you visited, URLQ may need to involve the business that published it, and will tell you if that happens.