Last updated: August 6, 2026
Who operates this website
UrbanCove, Inc. operates this website as a California real estate brokerage. Questions about this notice may be directed to info@urbancove.com or mailed to 5920 Nathaniel Way, Suite 300, Bakersfield, CA 93313.
Information you choose to provide
Website forms may collect contact information, including name, email address, and phone number; the type of real estate or property-management request; property addresses and property characteristics; desired timing and price ranges; rental or listing references; and the message or details you submit.
Recruiting inquiries may include a California DRE license number when the person chooses to provide it. Do not submit Social Security numbers, financial account details, identification documents, medical information, or other sensitive records through ordinary website inquiry forms.
Information collected with a request
The site may record the page path, referring page, campaign parameters, and basic technical request information needed to deliver the service, secure the form, prevent abuse, and understand which public pages lead to inquiries. For abuse prevention, a one-way hash derived from network and browser information may be held briefly in server memory. The website does not intentionally store a raw IP address in the lead record.
Planning-tool answers and reports
Seller, buyer, rental-property, relocation, and new-construction planning tools may process property, timing, preference, and financial-scenario inputs in the browser. Before a contact request, those answers are kept in temporary browser session storage where available. They are not placed in public URLs, and the visitor can clear them from the tool. Closing the browser session may clear them depending on browser behavior.
Tool answers are not transmitted to UrbanCove merely because a preview is generated. When a visitor explicitly requests a complete plan, the lead record stores contact information, attribution, the tool type and version, completion status, planning-profile label, selected scenario labels, and a short high-level result summary. The website intentionally does not send raw financial answers to browser analytics or advertising platforms. Property information needed for the requested service may be included in the lead record.
Marketing consent is separate from permission to respond to a requested report, is optional, and is not selected by default. A saved request does not mean an email report was delivered. An authorized staff-notification service may receive contact details and a high-level service summary; unnecessary financial detail is excluded.
How information is used
- To review and respond to real estate, property-management, rental, recruiting, or general inquiries.
- To understand a property or requested service before a conversation.
- To route requests and coordinate brokerage or property-management work.
- To protect forms and systems from spam, duplicate requests, and misuse.
- To evaluate website performance using limited, non-PII analytics events.
- To meet recordkeeping, legal, regulatory, and professional obligations where applicable.
Submitting an inquiry does not enroll a person in marketing communications. Any future marketing consent should be requested separately and not be preselected.
Analytics
The site may collect limited interaction data about actions such as opening a search, submitting a form, or clicking a portal link. Free-form messages, property addresses, names, email addresses, and phone numbers are not intended to be sent as analytics properties.
Browser analytics honor a Global Privacy Control signal by suppressing browser analytics events. Advertising identifiers or server-side conversion services are not used without appropriate operational controls. Any future customer-data matching or enhanced-conversion use requires separate configuration, appropriate consent, applicable platform terms, and operational review.
Advertising measurement and privacy choices
Optional Google Ads measurement is available for eligible inquiries on our new-construction campaign page. Google advertising initialization requires a valid affirmative advertising-measurement preference and no observed Global Privacy Control signal. You can search and contact us without accepting measurement.
When enabled, Google Ads website conversion measurement loads only after affirmative advertising-measurement permission. On the new-construction campaign and home-search pages, no measurement prompt opens automatically. To grant permission, open Privacy choices in the footer and choose Accept measurement. A previously saved, still-valid acceptance remains effective unless you reject measurement or Global Privacy Control is observed. Accepting permits advertising storage and use of data for this measurement purpose. An unanswered choice, rejection or observed Global Privacy Control keeps measurement disabled. Search, inquiry submission and our response to your request do not depend on accepting measurement. Permission to contact you is separate from advertising-measurement permission.
An eligible conversion event may be sent only after a normal new-construction inquiry is successfully saved and assigned in our CRM, its first-response task is committed, and the application receives the corresponding success receipt. The application conversion event contains only the Google destination identifier and an opaque inquiry transaction identifier. It does not intentionally include your name, email, phone number, property address or message. When its tag is permitted to load, Google may also receive advertising click identifiers, page and referral context, timestamps, IP address and browser/device information, and may use advertising cookies. See how Google uses information from partner sites. Personalized advertising, remarketing, Enhanced Conversions and separate analytics collection remain off; this choice does not enable them.
An affirmative local preference is valid for up to 180 days from the deliberate choice. Reading the preference or reloading a page does not renew that deadline. Expiry ends permission; it does not promise automatic physical deletion of browser data. We keep minimal local preference and opt-out evidence, not customer identifiers. Rejection and observed Global Privacy Control are handled separately from acceptance expiry: a recorded opt-out does not expire into permission or an automatic request to opt in again. Observed Global Privacy Control invalidates older acceptance. Turning that signal off does not restore acceptance. Only a fresh, deliberate choice through Privacy choices, while Global Privacy Control is absent, can grant permission again. If that later acceptance expires, the earlier opt-out still prevents an automatic opt-in prompt.
These preferences apply to this browser and website origin, not to an account or automatically across different website origins. For example, urbancove.com and www.urbancove.com do not automatically share this preference. Opt-out evidence remains until browser data is cleared or storage is otherwise lost; no automatic opt-out expiry is implemented. If storage access is restricted, we keep measurement off in the current page, but cannot guarantee that an unsaved choice survives a reload. These local controls do not complete separate account-level requests or erase existing CRM inquiries.
Advertising click identifiers used by our attribution system are held in browser session storage only with permission; identifiers from other advertising platforms are not enabled by this choice. Ordinary campaign labels may remain in the inquiry context. If measurement is enabled, a limited local browser ledger stores the Google destination, opaque transaction identifiers and claim timestamps to help prevent repeated sends. It holds no more than 500 unexpired claims. Each claim's 30-day period starts when it is recorded, before attempted transmission. Expired entries are removed on the next successful claim write, or when withdrawal cleanup succeeds, not automatically on day 30. At capacity, another conversion is not sent. A claim reserves a receipt for a measurement handoff; it is not proof that an event was transmitted or that Google received or credited it.
When enabled, the Google tag is configured to request host-only, path-/ first-party cookies with a 30-day lifetime, no renewal solely from page loads, and Secure and SameSite=Lax flags. These requested settings do not guarantee that a cookie's original expiry remains unchanged across reloads or navigation. Cookies can be removed and recreated, and nonrenewal has not been established. Expected Google Ads cookies include _gcl_aw, _gcl_au, _gcl_gb, _gcl_gs and _gcl_ag; not every cookie must appear. Google may also use _gcl_ls local storage for click information. The requested cookie lifetime does not establish the lifetime of every Google storage item or Google-owned cookie. No cross-domain linking or cross-origin consent synchronization is enabled.
Open the persistent Privacy choices control at any time and select Reject measurement to withdraw. Withdrawal or observed Global Privacy Control stops future conversion events, cancels pending unsent measurement and attempts to remove our local advertising identifiers and measurement claims. Cleanup also attempts removal of those named first-party cookies at this host and path and the _gcl_ls local-storage item. Browser storage restrictions can prevent physical cleanup. This cleanup cannot remove cookies at other domains or paths and cannot guarantee deletion of Google-held data or cookies. If a Google tag was already loaded, we communicate the denied consent state; that update may itself reach Google, but our application sends no new conversion events while permission is absent. Withdrawal cannot recall information already transmitted and does not erase CRM inquiries. We do not save declined conversions for later opt-in or replay an earlier inquiry receipt as a new conversion. A previously authorized script request already in flight cannot be guaranteed to stop downloading or executing; our application cancels its pending configuration and conversion work.
Google Maps review content
When Google Maps reviews are displayed, the website may request published review text, rating, reviewer attribution, relative date, and Google Maps source links from Google. UrbanCove does not scrape Google review pages.
Google Maps content is subject to the Google Maps Platform terms and the Google privacy policy. Reviewer and source links are displayed when the provider returns them. See the Google privacy policy for more information.
Agent reviews and social media
An agent profile may show reviews from public review platforms or client testimonials UrbanCove has permission to publish. The website preserves source attribution and does not send reviewer names or review text to browser analytics.
When public Instagram posts are displayed, the website may request post identifiers, media type, permalink, timestamp, caption, and platform-hosted preview media. Instagram access tokens are not sent to the browser. UrbanCove does not scrape Instagram and does not import private posts, messages, drafts, comments, follower lists, or Stories. Public posts remain subject to Instagram's terms and privacy practices.
IDX property search
You can open two different property-detail listings before creating a free UrbanCove account or signing in. To remember that browsing limit, this browser stores up to two listing-identity fingerprints and an expiry time for up to 30 days. Reopening the same home does not add a view or extend that period. Expired entries are replaced on the next successful detail-view write. This functional browsing record is separate from advertising measurement and is not sent to advertising services. Phone and marketing permission are not required to continue browsing. Advertising permission is also optional.
Live property search and listing pages may be provided by IDX Broker or a successor IDX provider through a branded search subdomain, wrapper, or supported widget. The provider may process search criteria, listing views, account registration, favorites, saved searches, and property inquiries when those features are enabled. The provider's own privacy terms may apply to its systems. UrbanCove does not copy general MLS inventory into its lead database.
Buildium
Buildium is the external operating system for available rentals, rental applications, resident access, owner access, accounting, and other property-management functions. Information entered after following a Buildium link is handled through Buildium and the applicable property- management relationship. This website does not recreate Buildium portals or application records locally.
Website form storage
UrbanCove may use Supabase to store website inquiry records. If a request cannot be saved, the website does not present it as successfully received.
Security and verification services
Website forms may use Cloudflare Turnstile when configured to distinguish legitimate requests from automated abuse. Technical information may be sent to that verification provider as part of the check. No website transmission or storage system can be guaranteed completely secure.
Phone authentication and communication consent
UrbanCove may process a normalized mobile number, a safely masked display, the phone-verification time and source, the associated Supabase Auth user, and bounded anti-abuse evidence. One-time authentication texts are requested for account security and do not create recurring marketing consent.
Optional marketing-text and live-agent-call choices are recorded separately. Evidence may include the disclosure version and hash, selection status, timestamp, source route and placement, session and anonymous identifiers, bounded campaign context, privacy-preserving IP evidence, bounded user-agent context, verified phone time, account identity, canonical contact, and later revocation or re-consent time. This restricted evidence is not sent to client-side analytics.
Messaging choices, suppression, and number use
Where a messaging program is activated, message frequency varies and message and data rates may apply. Clear STOP and other revocation requests suppress future marketing texts without deleting account access or saved activity. HELP requests may be handled through the approved messaging provider or UrbanCove support. Phone-call permission remains separate from text-message permission.
UrbanCove does not sell or share text-messaging opt-in data with unrelated third parties for their own marketing. Approved infrastructure providers may process phone and consent data to provide authentication, delivery, suppression, security, or recordkeeping services. See the Messaging Terms for the draft program details.
Sharing and service providers
Information may be processed by service providers that support website hosting, lead storage, property search, property management, security, communications, and professional operations. Information may also be disclosed when reasonably necessary to comply with law, protect rights and systems, complete an authorized service, or respond to a valid legal process. UrbanCove does not state in this policy that it sells personal information.
Retention
Information is retained only for as long as reasonably needed for the inquiry, the resulting professional relationship, security, dispute handling, recordkeeping, and applicable legal or regulatory obligations. Different records may require different retention periods. Temporary in-memory abuse controls are not a durable cross-instance retention system.
Expired phone-authentication intents are marked and cleaned on a short schedule; verification codes are never retained. Consent, revocation, and suppression evidence is retained under a separately reviewed policy and is not silently destroyed by account deactivation or a deletion request when a continuing recordkeeping or suppression need applies. Exact retention periods require counsel and operational approval.
California privacy considerations
California residents may have rights regarding access, correction, deletion, or information about certain uses of personal information, subject to the law, the nature of the relationship, and applicable exceptions. To make a request, contact info@urbancove.com and describe the request without sending sensitive identity records by ordinary email. UrbanCove may need to verify the request through an appropriate method before acting.
Children's information
This website is intended for adults seeking real estate or property-management services and is not directed to children. Do not submit information about a child unless it is necessary and appropriate for an authorized housing matter.
Changes to this notice
This notice may be updated as the website, providers, and practices change. The revised date should be updated when material changes are published.