1. Comprehensive Application & Legislative Framework
1.1 Scope of Application & Corporate Commitment
Project 86 Digital is fundamentally committed to the absolute operational transparency and security of your corporate data.
This Privacy and Data Governance Policy applies unequivocally to all digital properties, software integrations, and physical operational audits conducted by the Company.
It strictly governs our third-party middleware integration architectures, AI-driven voice telephony systems (FOH Shield), algorithmic foodtography capture, and web development infrastructure.
By navigating our public-facing digital properties, your explicit consent to our baseline tracking and telemetry mechanisms is legally implied.
Explicit, legally binding consent for deeper operational data processing, POS integration, and financial auditing is secured upon the formal execution of our Master Terms of Service.
This overarching policy serves as the definitive, singular framework governing the complete lifecycle of all information we gather from our clients and their end-users.
1.2 PIPEDA & Provincial Compliance Mandates
Our corporate data operations are engineered from the ground up to strictly comply with the federal Personal Information Protection and Electronic Documents Act (PIPEDA).
We further adhere to all applicable provincial frameworks and municipal guidelines governing commercial data processing within the jurisdiction of Ontario, Canada.
We treat the safeguarding of continuous data flows—including POS tokens and delivery app webhooks—as our most critical, non-negotiable infrastructure responsibility.
We actively prioritize the principle of data minimization, strictly isolating our data collection exclusively to that which is absolutely required for immediate service delivery and system diagnostics.
The Company processes collected information exclusively for commercial business purposes related directly to restaurant optimization, middleware bridging, and systemic health monitoring.
1.3 Policy Modification & Supremacy
The Company reserves the unilateral, unrestricted right to amend, augment, or otherwise modify this governance policy at any time without prior individual notice.
Such modifications may be necessitated by rapidly evolving algorithmic models, the deployment of advanced AI capabilities, or sudden legislative privacy shifts at the federal level.
All material amendments to this policy will be digitally posted on this page, establishing a new, publicly visible effective date of governance.
Continued utilization of our services following any published modifications constitutes an active, binding, and irrevocable acceptance of the newly revised privacy infrastructure.
This document completely supersedes any previous privacy statements, unwritten operational assumptions, verbal guarantees, or informal data handling agreements.
If any single clause within this framework is deemed legally unenforceable by a court of competent jurisdiction, the remaining data protocols shall survive in full force and effect.
2. Data Collection & Telemetry Protocols
2.1 Direct Client Data Acquisition
The Company initiates systematic data collection at the precise moment of client onboarding, preliminary consultation, and audit scheduling.
Directly provided data includes essential business contact nomenclature, corporate ownership structures, and authorized internal personnel directories.
We actively collect physical operating addresses, provincial tax identification parameters, and primary corporate communication email frameworks.
To facilitate our technical integration services, we mandate the secure, encrypted transfer of necessary third-party credentials from the Client.
This includes, but is not limited to, POS API tokens (e.g., TouchBistro), delivery platform administrative logins (for SkipTheDishes, Uber Eats, and DoorDash), and localized CMS credentials.
Historical operational data, encompassing previous menu pricing architectures, ticket velocities, and baseline gross sales, are gathered during the initial '86 Audit' phase.
2.2 Financial Data & Communication Logs
Financial and recurring billing parameters are collected exclusively through highly secure, PCI-compliant third-party payment gateways (such as Stripe).
The Company actively refuses to store, process, or maintain raw credit card numerics or direct bank routing variables on our internal proprietary databases.
All direct communication logs, including support email threads, SMS dispatches, and recorded virtual consulting sessions, are preserved within our encrypted CRM ecosystem.
These communication logs are retained to ensure absolute service continuity, historical accountability, and dispute resolution accuracy.
2.3 Automated Telemetry & Non-PII Tracking
Beyond directly provided inputs, our digital architecture relies heavily on automated, service-generated telemetry to monitor algorithmic health.
We deploy standard web tracking technologies, including localized session cookies and persistent tracking pixels, across all our managed domains.
This automated data captures generic user agent strings, incoming IP addresses, broad geographic estimations, and operating system identifiers.
Within the live restaurant environment, our integration workflows actively log API handshake frequencies to monitor system connectivity.
We meticulously track payload delivery times, web-hook receipt confirmations, and automated error-code generations (e.g., 500 Internal Server Errors).
This automated telemetry is strictly categorized as non-personally identifiable information (Non-PII) and is utilized exclusively for systemic diagnostics.
3. FOH Shield, Conversational AI & Voice Processing
3.1 Real-Time Audio Capture & Transcription
The 'FOH Shield' relies on advanced conversational Artificial Intelligence, necessitating the real-time processing of complex, live public audio streams.
When an end-user dials a Client’s dedicated FOH Shield telephony number, the audio input is captured and immediately digitized into a temporary buffer.
This ephemeral digital audio buffer is utilized for the sole, explicit purpose of Natural Language Processing (NLP) and high-speed order transcription.
Following the successful API injection of the transcribed food order into the Client’s POS, the raw audio file is designated for immediate, automated deletion.
This deletion protocol ensures that strict ephemeral storage principles are upheld regarding actual voice recordings of the general public.
3.2 PII/PHI Sanitization & Model Training
The Company employs rigorous, automated sanitization protocols engineered to systematically scan all AI text transcripts for highly sensitive numerics.
This system actively attempts to identify and strip Payment Card Industry (PCI) data and Personal Health Information (PHI) prior to database storage.
Furthermore, obvious Personally Identifiable Information (PII) belonging to the end-consumer is actively obfuscated from our permanent NLP transcript logs.
Anonymized, thoroughly sanitized text transcripts may be retained indefinitely within our secure neural network training environments.
This long-term text retention is absolutely vital to continuously refine our intent-recognition algorithms and localize complex culinary vocabulary.
3.3 Client Notification Obligations & Metadata
Telephony metadata, including caller ID numerics and exact call duration timestamps, are retained strictly outside the core AI learning model.
This external metadata is utilized exclusively for monthly billing reconciliation, telecom carrier compliance, and pattern-abuse (spam) prevention.
The Client assumes the absolute, non-transferable legal obligation to maintain proper localized recording notifications for their inbound callers.
This includes configuring mandatory automated preamble warnings advising the end-user that their interaction is being recorded and processed by artificial intelligence.
The Company accepts zero liability for the Client's failure to legally secure the 'consent to record' from their own local consumer base.
4. Middleware Security & Third-Party Vendor Data Flow
4.1 API Payload Routing & Ephemeral Caching
Our integrated middleware architecture operates as a secure conduit between multinational delivery apps and localized POS terminals.
It is meticulously designed to securely translate conflicting payload languages without permanently warehousing the underlying transactional data.
During a standard API cycle, we process essential operational data including item modifiers, pricing matrices, and localized tax codes.
We temporarily process customer delivery coordinates, courier GPS tracking links, and specialized kitchen preparation instructions necessary for fulfillment.
Data packets traversing our integration architecture are subject to extremely strict, time-bound memory caching limits.
Information is held in active memory only for the exact microsecond duration required to confirm a '200 OK' success receipt by the target POS architecture.
Once successful POS injection is confirmed, the transactional payload is systematically and permanently purged from our active processing queue.
4.2 Third-Party Integrations & DPA Compliance
Because we interface directly with global entities, data processed through our integrations may inevitably route through secure cloud instances located outside of Canada.
We strictly adhere to the mandatory Data Processing Addendums (DPAs) enforced by delivery platforms including SkipTheDishes, Uber Eats, and DoorDash.
In the event of a localized API rejection or network timeout, payload data is temporarily diverted to a highly secure error-logging queue.
This isolated error queue exists solely to facilitate rapid manual reconciliation, webhook redelivery, and debugging by our senior technical architecture team.
Under absolutely no circumstances does Project 86 Digital engage in the sale, brokering, or commercial leasing of POS operational data to outside entities.
4.3 Cryptographic Security & Client-Owned Hosting
The Company deploys enterprise-grade Advanced Encryption Standard (AES-256) block ciphers for all highly sensitive data secured at rest within our environments.
Every single API handshake, token refresh, and webhook delivery is strictly tunneled through Transport Layer Security (TLS 1.3) protocols to prevent interception.
For web development deliverables, codebases are deployed directly to the Client's self-owned hosting accounts (e.g., Vercel, AWS), ensuring the Company does not act as a continuous web host or server administrator.
We elect exclusively to utilize industry-leading cloud infrastructure providers that maintain rigorous, globally recognized SOC 2 Type II compliance.
Internal employee access to highly sensitive Client API credentials is compartmentalized via strict, zero-trust Role-Based Access Controls (RBAC).
5. Client Rights, Data Erasure, and Breach Response
5.1 Data Access & The Right to Erasure
In strict accordance with PIPEDA, authorized Client representatives maintain actionable, legal rights regarding their archived corporate data.
Clients may submit a formal, written Data Access Request to review the precise categories and classifications of information currently held by the Company.
If documented inaccuracies are identified within our databases, the Client possesses the absolute right to mandate immediate systemic corrections.
Upon the complete termination of all active service contracts, Clients may formally invoke their right to comprehensive data erasure.
This erasure protocol encompasses the permanent, irrecoverable deletion of all proprietary POS configurations, delivery API tokens, and AI routing logs.
However, the right to erasure is not legally absolute; specific historical financial records must be retained by the Company indefinitely.
We are legally compelled to maintain invoice histories, payment gateway logs, and dispute resolution records to satisfy federal corporate taxation and auditing laws.
5.2 Incident Response & Breach Notification
To fiercely combat external cyber threats, the Company maintains a specialized, highly documented internal Incident Response Plan (IRP).
In the extremely unlikely event of a verified data breach exposing sensitive API credentials, we will immediately initiate total network isolation protocols.
The Company legally commits to notifying all materially impacted enterprise Clients within seventy-two (72) hours of definitively confirming a breach.
The official corporate breach notification will explicitly outline the nature of the intrusion, the attack vector, and the specific data classifications exposed.
It will further detail the immediate cryptographic and infrastructural corrective actions currently being deployed to neutralize the active threat.
Where required by federal or provincial law, the Company will simultaneously report the breach metrics to the Office of the Privacy Commissioner of Canada.
5.3 Law Enforcement & Corporate Transitions
Following total breach containment, the Company will authorize an independent internal forensic review to identify the root vulnerability.
We will cooperate fully, transparently, and immediately with localized and federal law enforcement agencies regarding cyber-intrusions when legally compelled via subpoena.
Should the Company undergo a major corporate transition—such as a merger, acquisition, or asset liquidation—Client databases will securely transfer as a core, protected business asset.
Any formal inquiries regarding these privacy practices, erasure requests, or DPA compliance must be directed securely to: privacy@project86digital.com.