Technical Tracking & Session Protocol

Operational Session Management under Statutory Data Governance

Statutory Compliance: [Chapter 12:07]Last Verified: May 13, 2026

This protocol defines the mechanical application of cookies and similar tracking technologies within the Propertyzone infrastructure. These tools are not utilized for invasive behavioral profiling; they are functional necessities engineered to ensure session persistence across erratic mobile networks, mitigate account takeover risks, and optimize lead-routing efficiency for registered Practitioners under the Cyber Security and Data Protection Act [Chapter 12:07].

Technical Definition and Operational Scope

Tracking technologies—specifically cookies and local storage objects—are discrete data strings deployed to your device to facilitate technical handshakes between your hardware and our infrastructure. On Propertyzone, these are not used for non-consensual profiling; they are mechanical components required to maintain the state and security of the marketplace.

Sparkline Labs utilizes these tools to solve for session persistence (ensuring Practitioners remain authenticated during network fluctuations), security integrity(preventing unauthorized account hijacking), and performance analytics (identifying latency bottlenecks in local ISP routing).

Administrative Sovereignty

You maintain administrative control over these identifiers. While you may calibrate your browser to reject non-essential tracking, Essential Cookies are non-negotiable. Disabling them will result in the immediate failure of authentication systems and lead-routing tools.

1. Taxonomy of Technical Identifiers

1.1 Operational Classification

Infrastructure & Security (Strictly Necessary)

These identifiers are deployed to ensure the Platform satisfies the security mandates of the Cyber Security and Data Protection Act. They manage:

Practitioner Authentication: Maintaining secure login states across high-latency connections.
CSRF Shielding: Protecting your professional data from cross-site request forgery attacks.
Cryptographic Salting: Ensuring secure data transmission for transaction leads.
Preference Logic: Remembering your statutory data consent settings.

Marketplace Continuity (Functional)

Tools that preserve your operational workflow across sessions:

Search Persistence: Storing specific suburb filters and price-point criteria.
Asset Archiving: Tracking recently viewed properties and comparison shortlists.
Regional Customization: Locking in language and currency (USD/ZiG) display preferences.

Performance Intelligence (Analytics)

Used exclusively to optimize the technical efficiency of the Platform:

ISP Routing Analysis: Identifying performance drops across specific mobile networks.
Conversion Metrics: Measuring the effectiveness of lead-delivery to registered Agents.
Interface Heatmaps: Analyzing Seeker interaction patterns to refine UI for faster navigation.

Temporal Scope

Session Identifiers expire the moment you terminate your browser instance.Persistent Identifiers remain stored (from 30 days to 12 months) to ensure recurring Practitioners do not have to re-configure their professional dashboard upon every visit.

Source Origin

First-Party data is managed exclusively by Propertyzone. Third-Partytools are only utilized where international infrastructure standards (Google Analytics, Security Pixels) provide superior protection and accuracy.

2. Technical Identity Inventory

The following table identifies the primary technical assets utilized within the current production environment:

Identifier	Utility Purpose	Taxonomy	Duration
pz_session	Practitioner authentication and state management	Essential	Session
pz_csrf_token	Anti-hijacking and security shielding	Essential	Session
pz_trust_consent	Statutory record of privacy preference	Essential	1 Year
pz_currency_lock	Currency display persistence (USD/ZiG)	Functional	1 Year
pz_search_buffer	Preserves complex search filters for continuity	Functional	6 Months
_ga	Google Performance Analytics (Latency tracking)	Performance	2 Years

Note: This inventory is dynamic and is updated as our technical stack evolves to meet new security threats or network optimization requirements.

3. Third-Party Technical Integration

We utilize verified third-party infrastructure to enhance Platform robustness. Each partner is vetted for Chapter 12:07 compliance:

Google Technical Suite

Utilized for Platform speed analytics and conversion optimization. These cookies identify technical failures in lead-delivery to ensure no professional inquiry is lost.

Conversion Tracking Pixels

Used to measure the efficacy of Agency marketing budgets across professional networks. They help us determine which channels provide the highest-quality property seekers.

4. Management and Deletion Protocols

4.1 Browser-Level Deletion

Users may manually purge all Propertyzone identifiers via their native browser settings. This will immediately terminate all active sessions and reset your search preferences.

Chrome: Settings → Privacy → Cookies

Safari: Preferences → Privacy → Manage Website Data

Firefox: Options → Privacy → Cookies and Site Data

Edge: Settings → Cookies and site permissions

Operational Impact Warning

Disabling Essential technical identifiers will result in the complete failure of the Propertyzone Dashboard. You will be unable to list properties, manage mandates, or receive lead notifications. Statutory security protocols (CSRF protection) cannot be bypassed; their rejection will lead to an automated refusal of Platform access.

5. Policy Evolution and Technical Realignment

Sparkline Labs reserves the right to amend this Technical Tracking Protocol to ensure continuous synchronization with the Cyber Security and Data Protection Act [Chapter 12:07], advancements in local network optimization, or shifts in regulatory mandates. When a significant technical realignment occurs, we will:

Update the "Last Updated" timestamp at the apex of this protocol for version control.
Dispatch a formal notification to the primary administrative email linked to your Practitioner Account.
Deploy a high-visibility operational notice within the Agency Dashboard for 14 days.
Request a renewed technical consent for any non-essential tracking tier introduced by platform upgrades.

Practitioners are expected to review this protocol periodically. Continued utilization of the Platform following a technical update constitutes an irrevocable acceptance of the revised session management standards.

6. Administrative and Regulatory Contact

For specific inquiries regarding session persistence, data salting, or to exercise your rights under Chapter 12:07, contact our administrative infrastructure:

Electronic Correspondence

privacy@sparklinelabs.co.zw

Statutory Oversight

Data Protection Officer (DPO)

dpo@sparklinelabs.co.zw

Registered Physical Address

Sparkline Labs (Private) Limited
Harare, Zimbabwe

Technical Utility Covenant

Identifiers are utilized as mechanical components to optimize lead-delivery and ensure session persistence across unstable network infrastructure.

Practitioners maintain total administrative sovereignty over non-essential tracking through browser-level controls and the Platform Dashboard.

Essential Cookies are non-negotiable architectural requirements for authentication and statutory security (CSRF shielding).

Operational compliance is maintained in strict alignment with Zimbabwean Cybersecurity and Data Protection laws.

Statutory Regulatory Matrix

Data Privacy Mandate Service Covenants EACZ Enforcement

Technical Definition and Operational Scope

Administrative Sovereignty

Identifier

Utility Purpose

Taxonomy

Duration

pz_session

Practitioner authentication and state management

Essential

Session

pz_csrf_token

Anti-hijacking and security shielding

Essential

Session

pz_trust_consent

Statutory record of privacy preference

Essential

1 Year

pz_currency_lock

Currency display persistence (USD/ZiG)

Functional

1 Year

pz_search_buffer

Preserves complex search filters for continuity

Functional

6 Months

_ga

Google Performance Analytics (Latency tracking)

Performance

2 Years

Technical Tracking & Session Protocol

Technical Definition and Operational Scope

1. Taxonomy of Technical Identifiers

1.1 Operational Classification

Infrastructure & Security (Strictly Necessary)

Marketplace Continuity (Functional)

Performance Intelligence (Analytics)

Temporal Scope

Source Origin

2. Technical Identity Inventory

3. Third-Party Technical Integration

Google Technical Suite

Conversion Tracking Pixels

4. Management and Deletion Protocols

4.1 Browser-Level Deletion

Operational Impact Warning

5. Policy Evolution and Technical Realignment

6. Administrative and Regulatory Contact

Technical Utility Covenant

Statutory Regulatory Matrix

Technical Tracking & Session Protocol

Technical Definition and Operational Scope

1. Taxonomy of Technical Identifiers

1.1 Operational Classification

Infrastructure & Security (Strictly Necessary)

Marketplace Continuity (Functional)

Performance Intelligence (Analytics)

Temporal Scope

Source Origin

2. Technical Identity Inventory

3. Third-Party Technical Integration

Google Technical Suite

Conversion Tracking Pixels

4. Management and Deletion Protocols

4.1 Browser-Level Deletion

Operational Impact Warning

5. Policy Evolution and Technical Realignment

6. Administrative and Regulatory Contact

Technical Utility Covenant

Statutory Regulatory Matrix

Properties for Sale

Properties for Rent

Commercial for Rent

Commercial for Sale

Popular Suburbs