Privacy Policy

Homza Privacy Policy

Effective date: September 3, 2026 Homza is operated by Anthony Biafore, a real estate professional with MaxWell Canyon Creek in Calgary, Alberta. This Privacy Policy explains how Homza collects, uses, discloses, protects and retains personal information when you use this website and its real estate services.

Information We Collect

Depending on how you use Homza, we may collect your name, email address, telephone number, property address, preferred showing date and time, home-search criteria, favourite properties, home-evaluation information, mortgage-inquiry information, messages you submit, communication preferences and records of your interactions with Homza. We may also collect limited technical information needed to operate and protect the website, such as IP address, browser or device information, requested pages, timestamps, cookie identifiers, referral or campaign information and security events.

How We Use Information

We use personal information to respond to inquiries; arrange and follow up on showing requests; provide requested property alerts, favourite-property emails, home evaluations and mortgage-related follow-up; maintain customer and consent records; operate, secure and improve the website; prevent abuse and fraud; meet legal, regulatory, brokerage and real estate obligations; and communicate with you as permitted by law.

Consent and Email Choices

Saved Search alerts are not activated until the recipient verifies the email address. Property-alert emails contain controls to manage or unsubscribe from alerts. Favourite and Saved Search verification emails include an “I did not request this” link that adds the address to Homza’s global Do Not Contact list. You may withdraw consent for optional communications at any time, subject to legal or contractual restrictions and reasonable notice.

How Information May Be Shared

Homza does not sell or rent personal information. Information may be shared only as reasonably necessary with MaxWell Canyon Creek; property owners, listing representatives or brokerages when arranging a requested showing or real estate service; a mortgage professional when you specifically request mortgage assistance; technology providers that host, secure or deliver Homza services; professional advisers; regulators or law-enforcement authorities when required or permitted by law; or another party with your consent. Service providers may include Rocket.net for website hosting and security, Microsoft 365 or configured email-delivery providers, CREA and REALTOR.ca services supporting DDF® listings, mapping and website-performance services, and Twilio if SMS notifications are enabled. These providers are expected to handle information only for the services they supply and may process information outside Alberta or Canada, where it may be subject to the laws of that jurisdiction. Information submitted in connection with a showing or real estate inquiry may be provided to Anthony Biafore, MaxWell Canyon Creek, the applicable listing representative or brokerage, and other parties reasonably necessary to respond to or arrange the requested service.

DDF® Listings and CREA Analytics

Property listing information is supplied through The Canadian Real Estate Association’s Data Distribution Facility. When you view an individual DDF® property, Homza sends CREA a listing-view event containing the property’s DDF ListingKey, Homza’s DDF Destination ID, event type, site language and a pseudonymous random browser identifier. Homza intentionally does not send your IP address or referral URL to the CREA Analytics Web Service and does not store the raw CREA analytics identifier in its own analytics database. Although property listing information generally concerns real property, some listing information may also be considered personal information. Listing information displayed by Homza is supplied through participating real estate boards, associations and CREA’s DDF® and is displayed in accordance with the applicable listing permissions, agreements and DDF® rules.

Cookies, Browser Storage and Listing Analytics

Homza uses limited first-party cookies and browser storage to operate and protect the website, remember visitor choices and provide property-search features. Homza does not currently use cookies for behavioural advertising or third-party remarketing. The website may use:

DDF Terms and Privacy acceptance cookie: Records the version accepted by the visitor so DDF® listings can be displayed. It does not contain a name, email address or listing history and expires after 180 days.
Security and session cookie: Uses a random identifier to help prevent spam, abuse and excessive requests. It expires after 30 days.
CREA analytics identifier: After the visitor accepts the DDF Terms and Privacy Policy, a random pseudonymous identifier is used for required CREA listing-view analytics. Homza does not send the visitor’s IP address or referral URL to the CREA Analytics Web Service. This cookie expires after 365 days.
Favourites and recently viewed storage: Remembers selected and recently viewed properties in the visitor’s browser. This information remains on the device until it is removed, replaced or the visitor clears browser storage.
Attribution and session storage: Helps Homza understand how visitors reached the website and how listing features are used. Attribution information is ignored after 30 days, while session information normally ends when the browser tab or session closes.
WordPress cookies: WordPress may set functional cookies for authentication, administration, preferences or other standard WordPress features when applicable.

Homza may load mapping resources, REALTOR.ca identification images and other website resources from external providers. Requests to those providers may disclose ordinary network information, such as an IP address and browser user-agent, even when Homza does not intentionally create a third-party cookie. Visitors can remove or block cookies and browser storage through their browser settings. Doing so may erase saved favourites, recently viewed properties or acceptance preferences and may cause some website features to stop working or require renewed acceptance. If Homza later introduces advertising, remarketing or other non-essential tracking technologies, this policy and the website’s consent controls will be updated before those technologies are enabled.

Retention and Safeguards

Homza retains personal information only as long as reasonably necessary for the purposes described above and applicable legal, regulatory or business requirements. Current automated retention settings generally remove pending Saved Searches after 30 days, unsubscribed Saved Searches after 90 days, showing requests, Favourite collections, seller leads and mortgage leads after 365 days, and CRM contacts and activities after 730 days when no continuing relationship requires retention. These periods may be adjusted where reasonably necessary. Homza uses administrative, technical and physical safeguards appropriate to the sensitivity of the information, including access controls, encryption in transit, managed hosting protections, form-abuse controls, restricted administration and scheduled data cleanup. No internet service can guarantee absolute security. Homza may retain limited records of consent, verification, unsubscribe and Do Not Contact requests where reasonably necessary to honour communication preferences, demonstrate compliance with Canada’s anti-spam legislation, resolve disputes or meet legal obligations. Suspected privacy incidents or complaints should be reported promptly to Homza’s Privacy Officer. Homza will investigate privacy concerns and provide information about available recourse. You may also contact the Office of the Information and Privacy Commissioner of Alberta regarding concerns governed by Alberta’s Personal Information Protection Act.

Access, Correction and Deletion Requests

You may ask whether Homza holds personal information about you and request access to, correction of or deletion of that information, subject to applicable legal exceptions and retention obligations. Homza may take reasonable steps to verify your identity before completing a request.

Privacy Contact

Homza takes reasonable steps to keep personal information accurate, complete and current for the purposes for which it is used. You may request correction of inaccurate or incomplete personal information by contacting the Privacy Officer. Questions, consent withdrawals, access or correction requests, and privacy complaints may be directed to: Anthony Biafore, Privacy Officer, MaxWell Canyon Creek, Calgary, Alberta, at notifications@homza.ca. 203,20 Sunpark Plaza SE Calgary AB T2X 3T2 Phone (403)-991-8855

Policy Updates

This policy may be updated when Homza’s practices, services or legal obligations change. Material changes to this policy will cause the DDF Terms and Privacy notice to be shown again.

Third Party Link

Homza may contain links to REALTOR.ca, virtual tours and other independently operated websites. Homza does not control those websites, and information you provide to them is governed by their own privacy policies and terms.

Cookies, Browser Storage & Listing Analytics

This site uses limited first-party cookies and browser storage to provide DDF listing access, security/abuse protection, favourites, recently viewed properties, attribution and analytics. The Homza items currently used by this site are listed below.

Item	Purpose and data	Retention / protection
homza_ddf_terms First-party cookie	Records acceptance of the DDF Terms of Use and Homza Privacy Policy so protected DDF listing content can be displayed. Terms version only; no name, email or listing history.	180 days HttpOnly; SameSite=Lax; Secure on HTTPS; first-party path.
homza_session First-party cookie	Random anti-abuse/session token used to rate-limit DDF and lead-form activity without storing the raw token in security logs. Random opaque token. Homza derives a keyed hash for security controls.	30 days HttpOnly; SameSite=Lax; Secure on HTTPS; first-party path.
homza_crea_analytics_uuid First-party cookie	Pseudonymous browser identifier used only for CREA listing-view analytics after DDF Terms acceptance. Random UUIDv4. Destination ID is appended only in the server-to-server CREA analytics request.	365 days HttpOnly; SameSite=Lax; Secure on HTTPS; first-party path.
homza_favorites_v1 localStorage	Keeps the visitor’s selected favourite DDF properties in this browser. Up to 100 compact listing summaries: listing key/ID, price, display address/community/type, beds/baths, brokerage, REALTOR.ca listing URL and photo URL.	Persists until the visitor removes favourites, clears site storage, or the browser removes it. Active/displayable listings are revalidated before rendering. Cookie flags do not apply to localStorage. Readable by same-origin JavaScript.
homza_recently_viewed_v1 localStorage	Shows recently viewed DDF properties in this browser. Up to 8 compact listing summaries using the same listing fields as favourites.	Persists until cleared/replaced by newer items or browser/site storage is cleared. Active/displayable listings are revalidated before rendering. Cookie flags do not apply to localStorage. Readable by same-origin JavaScript.
homza_attribution_v1 localStorage	Preserves first-touch/last-touch marketing attribution for lead reporting. Landing/referrer and recognized campaign parameters such as UTM values and ad click identifiers when present.	Operational max age 30 days; older stored data is ignored and replaced on a later valid touch. Cookie flags do not apply to localStorage. Readable by same-origin JavaScript.
homza_analytics_session sessionStorage	Groups Homza internal interaction events such as listing clicks, showing-button clicks and opening Save Search during the current browser tab/session. Random session identifier. Event requests can also contain the current page URL, document referrer and listing identifiers for the clicked item.	Browser session/tab storage; normally removed when the tab/session is closed. Cookie flags do not apply to sessionStorage. Readable by same-origin JavaScript.
WordPress core cookies WordPress / first-party	WordPress may set authentication, logged-in, settings, comment-author and test cookies depending on whether the visitor signs in, comments, or uses WordPress features. Controlled by WordPress core and the site configuration, not by Homza DDF.	Varies by WordPress cookie and user action. WordPress controls these attributes. HTTPS is required for Secure transport where applicable.
External resource requests Third-party network resources	Homza currently references Leaflet from unpkg.com, OpenStreetMap map tiles, REALTOR.ca badge images, CREA/DDF API services and the CREA Analytics Web Service. A browser request to an external resource can disclose ordinary network metadata such as the visitor IP address and user agent to that resource host. CREA listing analytics itself is sent server-to-server and Homza intentionally omits the documented visitor IP and ReferralURL parameters.	Controlled by the external service/browser where applicable. Homza code does not explicitly create a third-party cookie. Actual third-party Set-Cookie behaviour must be checked in a real staging/production browser session.

CREA listing-view analytics

After DDF Terms acceptance, viewing an individual DDF property causes Homza to send a server-to-server CREA analytics event containing the DDF ListingKey, this site’s Destination ID, event type “View”, site language and a pseudonymous random browser identifier. Homza does not send the visitor IP address or ReferralURL in the documented CREA analytics parameters, and does not store the raw CREA analytics UUID in its own analytics database.

LocalStorage and sessionStorage

Browser localStorage/sessionStorage are not cookies and therefore do not support Secure, HttpOnly or SameSite attributes. They are accessible to JavaScript running on this site. Homza limits these stores to the functions described above and does not place contact-form names, phone numbers, email addresses, seller-lead details or mortgage-lead details in these browser-storage records.

WordPress and third parties

WordPress core, the active theme or other installed plugins may set additional cookies outside Homza DDF. External resource providers may also change their cookie behaviour independently. The final production privacy review should include a browser/network scan of the live or staging site to confirm the complete runtime cookie inventory.