The Houston District

The Houston District Parking Privacy Policy

Effective: 21 October 2026

Urban Properties Houston LLC, Houston, Texas, operates The Houston District parking service. This policy covers the /park/... pages on thehoustondistrict.com and The Houston District app for iOS and Android. It explains the information used to quote, sell, verify and support parking. Some payment, wallet, sign-in and messaging features appear only when enabled for a lot and device.

Information we use

  • Parking and purchases. We receive the lot, the issuing state and license plate, the selected offer and coverage start and end times, purchase and payment status, and the amounts shown at checkout. A numbered-space lot also requires its space number. Every parking purchase, on the website or in the app, requires a valid email address and an E.164 mobile number for receipt contact. An email address is needed for email receipt recovery. We keep the receipt and records of sales, voids and refunds.
  • Accounts. An account may hold an email address and any phone number you provide. When available, you can sign in with Apple, Google or an email code. The web and app use the same account; a first verified email code creates one. Apple sign-in may provide a name. A web sign-in uses a revocable, HTTP-only session cookie with a sliding 90-day lifetime. An account may also hold saved vehicles and their labels, notification choices, devices, purchase history and saved payment method aliases.
  • Payment details. You enter card details in our own card fields. Those details go straight to Authorize.net through Accept.js; The Houston District receives an opaque payment token and payment result, never the full card number, and does not store card numbers. Our checkout rejects full card fields in server requests. If a payment method is saved, The Houston District keeps a reusable alias or label and processor profile identifiers. A processor profile can also be held for a refund after an alias is removed. Wallet payments are offered through Apple Pay or Google Pay only if enabled.
  • App and browser data. If you enable account push notices and grant notification permission, the app can register an iOS or Android push token with platform, app version and language. On supported iPhones, a Live Activity can separately register an update token for a verified active parking session unless you turn that countdown off. Guest receipt access may be kept in the device's protected storage. The website keeps short checkout identifiers in browser session storage to resume a pending purchase. Your vehicle and contact details can be remembered on your own device for convenience, and you can clear those details on that device. A hosted-card return uses a secure, HTTP-only cookie for up to 24 hours. A separate first-party, HTTP-only device cookie may remain for up to 400 days. We collect the IP address, browser user agent, device characteristics and a soft fingerprint hash, terms acceptance, and receipt views to prevent fraud and answer payment disputes. The service also uses keyed hashes of request addresses and identifiers for request limits.
  • Nearby lots. When you select “Use my location,” the app asks for foreground location permission and gets a balanced-accuracy location fix. After you grant permission, later visits to the Find screen can get a fresh foreground fix and refresh it while that screen is open, until you turn off permission. The nearby-lot comparison happens on the device; The Houston District does not send that fix to its parking server for ranking. The native map can display your position using Apple or Google map components. The app does not run background location updates for this feature.
  • Help and enforcement records. If you contact us or request receipt recovery, we use the contact details and message you provide to respond or, if the recovery checks pass, send a one-time link. For a lost receipt, staff may match the receipt code to a verified sale and keep a case/audit record before giving a short-lived recovery code. If an enforcement case is opened, the case may include the lot, plate and state, a reason, a photo, status changes and related audit records.

Why we use it

We use this information to calculate and show the price and coverage window; verify payment before activating coverage; issue receipts; let you view purchases and manage an account; check coverage for the right lot and vehicle; send service messages if the relevant feature and permission are enabled; handle refunds, support and disputes; protect the service; and keep accounting and tax records. A price preview alone does not create paid parking.

Who receives information

  • Payments: Authorize.net is the payment gateway. It receives card details directly through Accept.js and processes payment tokens, transaction amounts and processor profiles. Chase Merchant Services is the merchant acquirer and receives payment information needed for settlement. The Houston District does not receive full card numbers. Purchase and receipt records may also be shared with Chase, the card issuer and card networks to answer payment disputes.
  • Email and texts: Microsoft 365 processes destination email addresses and message content for receipt, reminder and authentication emails, including sign-in codes and password resets, through our connected parking mailbox. Resend processes destination email addresses and message content for promotional emails, and may process transactional emails when no Microsoft 365 connection is configured. Zoom Phone processes your mobile number and the content of our texts. A receipt email includes the lot, plate and state, the coverage window, the price lines, the card brand and last four digits (or Apple Pay), the transaction ID and the receipt link. A receipt text includes the plate and state, the end time, the lot, the total and a receipt link. The messaging choice is unchecked by default. If you select the messaging choice, we text the receipt and parking reminders to a U.S. or Canadian mobile number and email the receipt and parking reminders. Other numbers can receive the email reminders but not texts. If you do not select the choice, we send no texts or reminders; a receipt email is still sent. Message frequency varies. Message and data rates may apply. Reply STOP to stop texts or HELP for help. Every reminder email has a stop link. We do not send marketing texts. We do not sell or share mobile numbers or text-message opt-in data and consent with third parties or affiliates for their marketing or promotional purposes.
  • Device and identity services: Apple and Google receive information needed for their sign-in services when selected. If enabled, Apple Pay and Google Pay handle wallet payment data. Apple Push Notification service and Google Firebase Cloud Messaging may handle device tokens and notification delivery when push delivery is enabled. The native map uses Apple or Google map components.
  • Hosting: Render provides application hosting. Cloudflare provides the network edge and file storage, which may include private enforcement case photos. These services can process technical request data needed to deliver the service.
  • Parking enforcement: The parking enforcement company named on the signs posted at the lot can use authorized, lot-scoped coverage tools to look up a plate and issuing state or a space, and to see a list of currently covered plates for that lot. Results can say PAID (with a paid-through time), PERMIT, IN GRACE, NOT PAID or UNKNOWN, and can include the space, expiration time and permit type. The coverage results do not include your name, email, phone, price or payment method. The company can submit case reasons and photos and see the current status of its own cases; The Houston District records the case changes. A NOT PAID result by itself is not authorization to boot or tow.

Keep receipt links private. A person who has a valid receipt link may be able to view its parking details.

Plate protection and retention

The system normalizes a plate with its issuing state, stores a keyed hash for matching, and encrypts the readable plate and contact fields. Saved vehicles use the same type of keyed lookup hash and authenticated encryption. Authorized parking checks can reveal the plate and coverage details described above; encryption does not hide a plate from someone authorized to check it.

We keep sale, payment, refund, receipt, consent and enforcement records, including encrypted plate and receipt contact, for four years, then delete them. We delete plate and contact data not tied to a sale, such as quotes, unfinished checkouts and gateway-declined attempts, 90 days after the session or quote ends, even if the gateway assigned a transaction ID. A pending or unknown payment remains until the gateway gives a definitive answer. We erase behavioral evidence for a declined attempt 548 days after it ends and its gateway proof four years after its final result. We keep behavioural evidence such as IP, user agent, device identifiers and receipt views until 548 days after coverage ends. We keep opt-out suppression records as long as needed to honour an opt-out. We delete the content of a receipt text or email once it is delivered. We keep text consent and opt-out records for four years after the last text. Delivery records include a keyed hash of the destination, time, status and provider message ID. A dispute legal hold can extend any of these periods. We keep other account and support information only as needed to provide the service, respond to requests, and meet legal obligations.

You can delete your account in the app or at /park/account on the website; /customer/delete also explains the process. After a fresh identity check and an accepted request, The Houston District revokes account sessions and device notifications, clears account email, phone and name, overwrites saved vehicles, and removes access to saved payment aliases. It suppresses account notification content and revokes account-linked receipt access. Completed sale, refund and accounting records remain for the four-year period above, including their frozen vehicle and contact evidence, unless a legal hold applies. A processor payment profile may remain for refund handling even after its alias is unavailable. If you used Apple sign-in, The Houston District attempts to revoke the linked Apple credential; an encrypted revocation token can remain if Apple has not confirmed that step. A later sign-in starts a new account; it does not restore the old vehicles or account receipts.

Your choices and requests

You may use guest checkout where offered, avoid saving a payment method, edit a saved vehicle or take it off your active list, remove access to a saved payment alias, change notification preferences, turn off push or location permission in device settings, and request account deletion. Email receipt recovery is limited to an eligible account with a verified email and exactly one verified sale on that account; simply entering a guest receipt email does not guarantee recovery. Save or share your receipt while you can access it. Contact us to ask about access, correction or deletion of your information, or to raise a privacy concern. We may need to verify your identity and retain records that law requires.

Children, security and changes

Parking purchases are for users 18 or older. We do not knowingly collect personal information from children under 13. If you believe a child under 13 provided information, email park@thehoustondistrict.com so we can review and delete it.

We use our own card fields with direct Authorize.net tokenization, encrypted personal fields, keyed lookup hashes, scoped enforcement access, limited receipt links and request limits. No online service can promise perfect security. We post policy changes on the website and in the app, and email account holders about material changes. Changes take effect when posted unless we state otherwise.

Contact

Email park@thehoustondistrict.com for parking support or privacy requests. Support is by email only; there is no support phone number. This same address is the parking contact on the website, in the app and on receipts. Do not send card numbers in a support request.

Version 2026-10-21-2