Regulatory Compliance Notice: This Privacy Statement has been structured to satisfy the stringent transparency and accountability requirements governing digital data systems within Canada. This framework explicitly enforces operational alignment with the federal Personal Information Protection and Electronic Documents Act (PIPEDA), Ontario's provincial privacy guidelines, consumer protection statutes, and international cross-border data handling standards where applicable to Canadian commercial ventures.

1. Introduction and Corporate Commitment

Dealogo Technologies Inc. operates an intelligent price and product discovery platform designed to aggregate, analyze, and deliver real-time retail intelligence directly to consumers. The system functions across a unified omnichannel ecosystem, including the primary public website, embedded web products, secondary landing zones, browser utility environments, and native mobile applications.

The management team is deeply dedicated to maintaining comprehensive security, confidentiality, and architectural transparency regarding all data elements captured, ingested, or processed during consumer operations. This Data

Privacy Statement outlines the exact mechanical processes used to collect, isolate, share, and protect informationacross the active product architecture.

2. Scope of Application

This policy governs all active interactions with platforms managed by Dealogo Technologies Inc. It applies universally to basic online inquiries, registered user accounts, consumer dashboard interfaces, mobile application modules, automated real-time Product Intelligence Page (rPage) generation requests, product alert configurations, and click-through referral tracking links. The policy covers all five core operational frameworks:

• The public-facing corporate and utility website infrastructure.

• The user-facing data configuration dashboards and comparison tools.

• Native mobile application codebases distributed via certified digital stores.

• Automated backend data ingestion interfaces and utility pipeline tools.

• Bilingual localized user interface endpoints serving Canadian consumer segments.

3. Classifications of Data Collected

The technical infrastructure separates data collection into distinct categories based on operational necessity, ensuring that data gathering is strictly restricted to fields required to maintain high-fidelity comparison services.

3.1 Personal Information Provided Voluntarily

This category encompasses information provided directly by users when creating profiles, activating premium utilities, or establishing communication pipelines:

Account Identifiers: Legal names, primary electronic mail addresses, preferred contact details, unique account passwords, and profile image files where explicitly uploaded.

Preference Configurations: Custom watchlists, user-initiated product categories, search tracking keywords, saved store directories, and localized threshold notifications.

Communication Logs: Text files, direct feature inquiries, feedback forms, customer support requests, and survey response records submitted during pre-development and live testing phases.

3.2 System-Generated and Technical Data Ingestion

To generate dynamic rPages and verify merchant affiliate connections, the core system automatically processes metadata elements from the user's terminal environment:

Device Specifications: Internet Protocol (IP) addresses, device hardware identifiers, hardware models, browser build versions, localized operating system layers, and language settings.

Telemetry and Interaction Metrics: Search queries executed, historical click paths, active duration per rPage,

exit link selections, and button interaction tracking within mobile environments. 

Geographic Location Factors: General regional location markers determined via IP routing paths or precise Global Positioning System (GPS) coordinate fields where mobile device permissions are explicitly granted by the user to filter proximity-based Canadian retail inventory.

3.3 Financial Transaction Infrastructure

When a user activates specific premium commercial tiers or merchant monetization options, processing is routed through isolated external frameworks:

Payment Gateway Isolation: Payment card numbers, billing addresses, authentication codes, and expiration files are processed directly through specialized Stripe processing systems. The company database infrastructure never stores raw payment card numbers. It retains only truncated verification strings, transaction timestamps, and tokenized receipts returned by the partner processing clearinghouse.

4. Legal Foundations and Mechanical Purposes of Processing

Information processing is strictly limited to clear legal frameworks based on contract execution, user consent, legal mandates, or legitimate corporate interests that do not infringe upon consumer privacy rights.

5. Architectural Data Protection and Trust Layer Protocols

The backend architecture utilizes advanced data masking protocols known as the "Trust Layer." This infrastructure secures user profiles by isolating internal database nodes from external query loops.

All personal fields are encrypted both at rest and during transit. Databases leverage industry-standard Advanced Encryption Standard (AES-256) controls, while external network connections run strictly via Secure Sockets Layer / Transport Layer Security (SSL/TLS 1.3) configurations. System administrators enforce strict, role-based access tokens to ensure that only designated internal engineering assets can view operational telemetry pipelines.

6. Data Retaining Frameworks and Elimination Policies

The storage lifecycle enforces a strict data minimization model. Personal details are retained only for the duration necessary to deliver the active comparison service or to comply with statutory Canadian financial record-keeping obligations.

Aggregated behavior metrics used for general product research and comparative market pricing indexes are stripped of all personal tracking elements. They are permanently stored as anonymous data blocks that cannot be traced back to an identifiable individual.

Account Purge Timeline: Upon a formal request for profile termination, the system automatically removes personal data fields from active production environments within thirty business days. Backed up image archives and cold data reservoirs are entirely purged or permanently anonymized within ninety calendar days from the initial deletion request.

7. Data Transfer and Downstream Disclosures

Dealogo Technologies Inc. does not engage in the open sale or direct rental of consumer profile records to thirdparty data brokers. External distribution occurs exclusively under strict, audited conditions:

• Downstream Technology Infrastructure: Essential cloud storage components, regional server hosting providers (including Amazon Web Services and regional Canadian hosting entities), Stripe processing pipelines, and ElasticSearch cluster engines.

• Retail Affiliate Networks: Outbound link routing engines require specific device identifiers to validate transaction referrals and secure merchant-supported conversion commissions.

• Legal Enforcement Requirements: Disclosures mandated by Canadian judicial warrants, regulatory audits, or active corporate litigation fields where disclosure is required by law.

8. Consumer Rights and Compliance Privileges

In strict adherence to PIPEDA frameworks and general data protection concepts, users maintain absolute control over their information through accessible configuration tools. Users have the legal right to exercise several data privileges:

• The Right of Inspection: Users can request a standardized JSON export of all personal details recorded within the production ecosystem.

• The Right of Correction: Users can update incorrect account profiles or preference configurations directly via their profile management dashboards.

• The Right of Erasure: Users can permanently close their accounts and trigger automated data purging scripts across all servers.

• The Right to Revoke Consent: Users can instantly opt out of marketing communications, location tracking permissions, or automated alert delivery pipelines.

9. Integrated Electronic Mail, Web Cookies, and Tracking Scripts

The platform utilizes modern cookies, tracking pixels, and storage tokens to maintain system state configurations across browsing sessions. These tools handle user language selections (English or French), secure session tokens, and affiliate referral validation codes.

Users can manage cookie behaviors via their web browser configurations. However, disabling all tracking tokens may break specific real-time rPage tracking features and automated merchant redirection pathways.

10. Continuous Revisions and Operational Status

This Privacy Statement is updated periodically to reflect software architecture changes, new retail integrations, or evolving Canadian legislative requirements. Revised policies take effect immediately upon deployment to our live web and app environments. Users are encouraged to review this document regularly to monitor active security protocols.

11. Institutional Privacy Contacts

For formal inquiries, data access requests, or to file a privacy grievance, users can contact the oversight team directly through our corporate monitoring frameworks:

Dealogo Technologies Inc.

8920 Woodbine Avenue, Unit 304, Markham, Ontario, L3R9W9, Canada

Email: contact@dealogo.com 

Corporate Registry: OCN 1001034955