Tyler Johnston-Kent

Posted on Jul 30

The Customer Black Book Problem: When a Retail President Is Also the Privacy Officer

#privacy #humanrights #a11y #indigenous

Can a major Canadian retailer internally profile a disabled Indigenous customer, impose special company-wide restrictions, use complaint records adversely, allow those narratives to enter a personal court proceeding, and then have its own president deny or delete the records while serving as the company’s Privacy Officer?

That is the question now facing Long & McQuade.

I am an Indigenous, disabled software engineer, security-systems developer, musician, and long-standing Long & McQuade customer. I identify as Ojibwe. I have ADHD, autism, a noticeable lisp, and mobility limitations.

This article is based on preserved emails, repair records, screenshots, a recorded management call, a recorded in-store interaction, a formal PIPEDA access request, and a complaint submitted to the Office of the Privacy Commissioner of Canada.

It does not ask readers to trust a vague memory of a bad shopping experience.

It asks readers to examine a management record in which:

Long & McQuade confirmed that my original technical diagnosis was correct;
one manager apologized and said the guitar should have been accepted;
senior management circulated the dispute internally;
management reframed continued complaint communication as harassment;
the president invoked the hostility of numerous employees against one customer;
all staff were instructed to communicate with me under special restrictions;
the company remained willing to sell to me while closing the complaint channel;
corporate complaint narratives later appeared in a personal court proceeding;
the president and designated Privacy Officer initially denied possessing the internal records behind those decisions;
he admitted that he deletes emails once he personally considers disputes resolved;
and he tried to reverse his position shortly after the federal privacy complaint was filed.

This is not normal retail management.

It is a privacy-governance and human-rights failure with national public-interest implications.

Documentation note

This is a first-person account. Direct quotations come from the preserved record. Allegations that have not yet been adjudicated are identified as allegations or issues under investigation.

The facts that already exist in writing remain facts regardless of what regulators ultimately decide:

the technical defect was confirmed;
management discussed me internally;
management adopted a shared adverse narrative;
Steve Long issued company-wide restrictions concerning me;
Steve initially said he retained no internal emails beyond our direct correspondence;
Steve said he deletes emails after he considers matters resolved;
and Steve attempted to end the customer relationship immediately after receiving the privacy request.

The legal conclusions belong to the Office of the Privacy Commissioner of Canada, the Manitoba Human Rights Commission, and any court with jurisdiction.

The documentary record is already a serious public-interest record.

The original issue was a confirmed guitar defect

On May 23, 2026, I brought an Ibanez guitar to Long & McQuade’s Ellice Avenue store in Winnipeg.

I reported a grounding or shielding fault. The symptoms included extreme electrical noise, interference, and almost no usable output.

The interaction should have been routine:

open a warranty repair intake;
let a technician test the instrument;
repair or replace it;
notify the customer.

Instead, the intake was rejected after a quick sales-floor test, before a technician properly assessed the instrument.

I experienced the interaction as mocking, condescending, and based on an assumption that I did not understand the equipment I was describing.

The next store accepted the same guitar.

On May 25, Jason Charney wrote:

“Our tech checked it out, and as you already know, it is a ground issue.”

That confirmation is important.

The technical dispute was over.

My original report was correct.

Dave Reeves, a manager at the Ellice location, separately reviewed the evidence, acknowledged that the problem was clearly a grounding issue, said the guitar should have been accepted, apologized, and offered to cover costs.

Dave’s response demonstrated what competent management looked like:

review the evidence;
acknowledge the confirmed fact;
recognize that the intake should have happened;
apologize;
offer a practical correction.

The problem did not become serious because a guitar needed repair.

It became serious because senior management treated the technical correction as permission to erase the discriminatory-treatment complaint that arose from the failed intake.

A repaired product does not automatically resolve degrading treatment.

A corrected transaction does not erase the process that first discredited the customer.

The human-rights issue was credibility

I repeatedly explained that the issue was not merely whether the guitar eventually entered service.

The issue was why my specific technical report had been treated as untrustworthy in the first place.

My lisp is immediately audible. I am visibly Indigenous. I communicate directly and in detail because of my disabilities and technical background.

The treatment I reported followed a familiar pattern:

presume the disabled Indigenous customer is confused;
substitute an employee’s quick impression for the customer’s evidence;
resist normal escalation;
treat persistence as aggression;
focus on tone rather than substance;
close the complaint without addressing the conduct.

Under Manitoba’s Human Rights Code, race, ancestry, ethnic background, physical or mental disability, and social disadvantage are protected characteristics. Section 13 prohibits discrimination in services available to the public. The Manitoba Human Rights Commission describes discrimination as differential treatment that disadvantages a person because of a protected characteristic, without reasonable justification. It also recognizes a duty to reasonably accommodate disability-related needs.

This matters because equal service is not limited to whether a business eventually accepts money or repairs an item.

It includes the terms, conditions, dignity, credibility, access, communication process, and management response attached to the service.

A retailer cannot avoid a human-rights issue merely by saying the transaction was eventually completed.

Dave Reeves acknowledged the service failure

Dave Reeves’s response is important because it shows that Long & McQuade management could understand the distinction.

He did not simply say the guitar would be fixed.

He reviewed the evidence, acknowledged that the fault was audible, stated that the guitar should have been accepted, apologized for how the matter had unfolded, and offered a concrete remedy.

That response did not require a tribunal.

It required basic management competence.

Dave’s response also creates an important comparison with what followed.

Once senior management became involved, the company’s focus shifted away from:

What happened, and how do we correct it?

The focus became:

Why is this customer still talking about it?

That shift is the centre of the dispute.

Steve Long personalized a corporate complaint

Steve Long is not merely another person copied on an email.

Long & McQuade’s published Privacy Policy identifies him as the company’s Privacy Officer. The same policy says Long & McQuade takes responsibility for handling and protecting customer information, that employees with access must maintain confidentiality, that customers may request details of their information and disclosures, and that privacy complaints may be directed to Steve.

He was therefore occupying several roles at once:

president and senior corporate authority;
recipient of the discrimination complaint;
defender of management;
decision-maker over customer access;
issuer of instructions to staff;
custodian of disputed records;
and designated Privacy Officer.

That structure became dangerous as soon as Steve began treating the complaint as a personal conflict.

In July, Steve wrote that I had:

“managed to really upset a lot of people”

and that I was one of the most difficult people he had dealt with that year.

Most revealingly, he wrote:

“Honestly nobody likes having their conversations thrown back in their face.”

That statement deserves close attention.

The concern was not expressed as:

the quotation is false;
the record is fabricated;
the context changes its meaning;
the complaint was independently investigated;
here is the written finding.

The concern was that management’s words had been preserved and could be compared against later statements.

Documentation was being treated as the offence.

For an Indigenous disabled customer dealing with a national corporation, documentation is the only thing preventing the corporate version of events from automatically replacing the customer’s version.

Steve’s statement effectively acknowledged that record retention was interfering with management’s ability to control the narrative.

Jason Charney converted complaint persistence into harassment

By July 21, the issue had gone through weeks of incomplete responses, redirection, and management claims that it had already been resolved.

I attended a Long & McQuade store with my partner to ask who was actually responsible for addressing the human-rights complaint.

The interaction was recorded.

Jason Charney refused to meaningfully address the substance of the complaint. He characterized my continued communication as harassment, relied on the store’s private-property status, moved into my physical space, and attempted to remove or physically guide me rather than provide a functioning complaint path.

During the interaction, Jason also unexpectedly raised a $25,000 figure.

I had not entered the store demanding $25,000 from Jason.

The figure corresponded to the maximum general-damages amount commonly discussed in Manitoba human-rights remedies.

That matters because it showed that management had already been discussing and interpreting my complaint before the recorded interaction.

Jason was not encountering the facts neutrally.

He arrived with an internal narrative about my motives.

The management loop had become:

The complaint remains unresolved
        ↓
The customer asks who is responsible
        ↓
Management refuses a clear answer
        ↓
The customer follows up
        ↓
Management calls the follow-ups harassment
        ↓
The harassment label becomes the reason not to answer
        ↓
The original complaint remains unresolved

That is not complaint management.

It is a system manufacturing the very communication volume it later uses against the complainant.

Adam admitted the management chain

A recorded call with Adam, a manager at the Ellice location, further exposed the internal chain.

Adam said:

“You started this.”

He argued that because I publicly documented the original incident, management could treat the later conduct as a conflict I had initiated.

He also said:

“You’ve gone up to Steve Long. Steve Long has forwarded it to us. Me and Jason Charney are handling this.”

That statement establishes several things.

First, Steve was not detached from the store-level response.

He received the complaint and forwarded it to Adam and Jason.

Second, Adam and Jason were acting within a management process created through Steve’s involvement.

Third, the response was not a neutral investigation.

Adam had already adopted the theory that the customer “started” the problem by documenting the service failure.

The company therefore transformed the act of recording and reporting a verified incident into the central wrongdoing.

This is exactly how institutional retaliation works in practice.

The original conduct disappears.

The complaint becomes the misconduct.

Steve admitted broad internal circulation

Steve repeatedly referred to the reactions of multiple employees.

He said I had upset “a lot of people.”

He later described an extraordinary number of staff members as having been affected by my complaint.

He then issued instructions to all staff.

These statements prove that the dispute was internally circulated far beyond a one-to-one email exchange.

That matters under privacy law because personal information includes more than account numbers and addresses.

It can include:

opinions about a person;
evaluations and allegations;
labels such as difficult, aggressive, unsafe, or harassing;
complaint histories;
disability disclosures;
Indigenous identity;
records of calls and store visits;
management instructions;
risk assessments;
account flags and restrictions.

Once those opinions are recorded, circulated, relied upon, or used to make decisions about a customer, they become part of the customer’s personal-information environment.

PIPEDA’s accountability principle makes the organization responsible for personal information under its control.

The fact that information may be spread across managers, stores, phones, email accounts, chat systems, notes, or corporate platforms does not remove that responsibility.

All staff were ordered to treat me differently

On July 24, Steve wrote:

“All staff have been instructed to only discuss specific product need and purchase requests, and have no other contact with you.”

That is a company-wide instruction governing one identified customer.

It is direct evidence of differentiated treatment.

The company remained willing to accept purchases.

But the same customer was restricted from discussing:

the unresolved discrimination complaint;
disability-related treatment;
privacy concerns;
management conduct;
retaliation;
or the continuing consequences of the dispute.

The practical rule was:

You may remain a customer when you are spending money, but you may not use the customer relationship to demand accountability.

This is not a normal retail boundary imposed after a completed investigation.

There was no independent investigation report.

There were no findings.

There was no written resolution of the human-rights issues.

There was no appeal route.

There was no alternate complaint representative.

There was only a company-wide restriction issued by the executive personally involved in the dispute.

Why the special restriction matters under Manitoba law

Section 20 of Manitoba’s Human Rights Code prohibits denying a benefit, threatening to deny a benefit, causing a detriment, or threatening a detriment because a person:

filed or may file a human-rights complaint;
made or may make a disclosure about a possible Code violation;
testified or may testify;
participated or may participate in a Code proceeding.

The Manitoba Human Rights Commission calls this reprisal: retaliation for filing, participating in, or supporting a human-rights process.

That does not mean every communication boundary is automatically illegal.

It means the reason, timing, scope, and effect matter.

Here, the restriction followed explicit disclosures that I was Indigenous, disabled, had a lisp, had ADHD and autism, and intended to pursue the matter through the Manitoba Human Rights Commission.

The restriction was not limited to abusive language, threats, or one communication platform.

It instructed every employee to treat me through a special rule while preserving the company’s ability to sell to me.

The documentary question is therefore obvious:

Was the detriment imposed because I made protected disclosures and continued pursuing a human-rights complaint?

That is a serious reprisal issue, not a minor customer-service disagreement.

Harassment law also imposes duties on management

Section 19 of Manitoba’s Human Rights Code prohibits a person responsible for a covered activity from harassing a participant or knowingly permitting or failing to take reasonable steps to terminate harassment by another participant.

The Code defines harassment, in part, as a course of abusive and unwelcome conduct or comment based on a protected characteristic.

The management question is not limited to whether Steve, Jason, Dave, or Adam personally made every disputed comment.

It also includes:

what management knew;
when management knew it;
whether the conduct was connected to race, ancestry, disability, or social disadvantage;
whether management took reasonable steps to stop it;
whether management instead blamed the complainant;
whether the company’s response added further disadvantage.

Dave’s early apology shows that management could recognize the immediate service problem.

The later record raises the opposite concern: senior management may have permitted the complaint to become an adverse internal profile rather than terminating the degrading treatment.

The “customer black book” problem

The phrase “customer black book” describes the functional risk created when a business accumulates informal adverse information about a customer and uses it across locations or staff without transparency.

The record raises questions about whether Long & McQuade created or used:

account flags;
difficult-customer labels;
safety warnings;
staff-wide instructions;
complaint summaries;
subjective assessments;
call histories;
screenshots;
internal emails;
group chats;
social-media monitoring records;
notes about disability or Indigenous identity;
assumptions about motives;
information connected to legal or regulatory processes.

A company may legitimately keep records needed for safety, transactions, dispute resolution, fraud prevention, or legal compliance.

But PIPEDA requires identifiable purposes, appropriate use, accountability, safeguards, limited disclosure, accuracy, access, and a functioning challenge process.

A hidden profile cannot become a licence to treat someone adversely.

The customer has a right to know what personal information exists, how it was used, and where it was disclosed, subject to specific statutory limits.

PIPEDA does not apply only to obvious identity data

Long & McQuade’s own privacy policy describes personal information and promises accountability, confidentiality, access, and complaint procedures.

Federal privacy law goes further.

PIPEDA Principle 4.9 says that, on request, an individual must be informed of the existence, use, and disclosure of personal information and given access to it.

The Office of the Privacy Commissioner explains that personal information can include opinions about a person, recordings, photographs, account notes, and other information connected to an identifiable individual.

That means a request is not satisfied merely by exporting a point-of-sale screen.

A proper search may need to include:

email;
internal messaging;
customer-management systems;
repair systems;
shared drives;
call logs and recordings;
account notes;
complaint files;
security or access records;
social-media administration tools;
archived records;
records held by employees or service providers on the company’s behalf.

The organization must identify whether the information exists, explain how it has been used, and provide an account of disclosure, subject to narrow exemptions.

Third-party information can often be severed rather than used as a reason to withhold the entire record.

The conflict at the centre of the privacy office

Long & McQuade’s Privacy Policy publicly identifies Steve Long as Privacy Officer.

PIPEDA Principle 4.1 says the organization must designate a person accountable for compliance.

Principle 4.1.1 makes clear that accountability remains with the designated person even when day-to-day processing is delegated.

Principle 4.10 requires accessible complaint procedures and says the organization must investigate complaints. Where a complaint is justified, it must take appropriate measures, including changing policies and practices where necessary.

The structural conflict here is severe.

The person asked to investigate the alleged misuse of customer information was also:

the president;
the management contact;
the person repeating adverse staff opinions;
the person issuing company-wide restrictions;
the person attempting to terminate the relationship;
and the person deciding what records existed.

That is not independent accountability.

It is a closed loop.

Receive the discrimination complaint
        ↓
Discuss the customer with management
        ↓
Collect or repeat staff reactions
        ↓
Issue company-wide restrictions
        ↓
Declare the matter resolved
        ↓
Control the records
        ↓
Answer the privacy complaint about the same conduct

The regulator now has to examine whether that structure complied with PIPEDA.

The formal access request

I submitted a formal PIPEDA request seeking all personal information Long & McQuade held about me, including:

account and repair records;
restrictions, warnings, flags, and annotations;
internal emails and messages;
management summaries;
complaint and human-rights records;
opinions and allegations;
access and disclosure histories;
social-media monitoring records;
records showing who accessed or circulated my information;
deletion, alteration, or reclassification records;
and communications involving Steve, Jason, Dave, Adam, and other personnel.

The request also included an explicit preservation notice.

It invoked subsection 8(8) of PIPEDA, which requires an organization holding information subject to an access request to retain it long enough for the requester to exhaust available recourse.

That preservation obligation is critical here because Steve’s response immediately raised a deletion problem.

Steve’s first response

Steve replied:

“You already have all the emails.”

He continued:

“I dont have anything other than what you sent and the ones I replied to.”

Then he wrote:

“I don't keep emails once they are resolved.”

He offered to send point-of-sale information.

He also said that, once my account was at zero and outstanding orders were completed, he would be happy to delete everything.

Finally, he wrote:

“I think its time to end our relationship. It is honestly far too time consuming.”

This response is extraordinary for several reasons.

First, it treated a company-wide access request as though the company consisted only of Steve’s personal inbox and the point-of-sale system.

Second, it contradicted the documented management chain:

Steve had communicated with Jason;
Steve forwarded the issue to Adam and Jason;
Adam said he and Jason were handling it;
Steve described reactions from numerous staff;
Steve issued instructions to all staff.

Third, it admitted an informal deletion practice based on Steve’s own determination that a matter was “resolved.”

Fourth, it paired the privacy request with an attempted termination of the customer relationship.

The response did not identify a privacy file number, a search plan, custodians, systems, exemptions, or an alternate complaint officer.

It was not written like a privacy office response.

It was written like an irritated executive trying to end a conversation.

The dispute was not resolved

Steve’s deletion statement depends on a unilateral definition of resolution.

But the matter was plainly active.

At the time of the request, there were:

unresolved discrimination allegations;
active privacy concerns;
company-wide customer restrictions;
a personal court proceeding containing corporate complaint narratives;
a planned Manitoba Human Rights Commission filing;
a formal access request;
and an OPC complaint.

A corporate executive cannot convert an active dispute into a resolved one merely because he no longer wants to discuss it.

More importantly, PIPEDA contains specific retention requirements.

Principle 4.5.2 says personal information used to make a decision about an individual should be retained long enough to allow access after the decision.

Subsection 8(8) requires information covered by an access request to be retained while the individual exhausts recourse.

The OPC has previously found organizations in violation where requested records were deleted or purged before the access process was complete.

The OPC has also instructed organizations to override routine deletion practices when necessary to preserve information covered by a request.

This is not optional etiquette.

It is a statutory obligation.

The real-time backtrack

The privacy complaint was submitted to the Office of the Privacy Commissioner.

Shortly afterward, Steve sent another email:

“Just noticed we have 30 days to reply so you wull have your reply by then.”

The sequence is preserved:

immediate claim that no internal email records existed;
admission that resolved emails were deleted;
offer to delete everything after the account was cleared;
attempt to end the relationship;
federal privacy complaint submitted;
sudden realization that the organization had a statutory response period.

The later email does not erase the earlier answer.

Instead, it creates a regulatory question:

Why did the designated Privacy Officer deny the records and discuss deletion before understanding the basic response obligations attached to the request?

PIPEDA does give an organization 30 calendar days to respond.

That period exists so the organization can perform a diligent search and issue a lawful response.

It does not convert the first denial and deletion admission into words that were never written.

What PIPEDA requires

A compliant response is more than an acknowledgment.

According to the OPC, an organization must generally:

respond with due diligence within 30 calendar days;
identify whether it holds the requested personal information;
explain its use;
provide an account of disclosure;
provide access in an understandable form;
search all reasonably likely sources;
apply exemptions narrowly;
provide written reasons and recourse when refusing;
correct demonstrated inaccuracies or record unresolved disputes;
retain responsive information while recourse remains available.

An extension is possible only in defined circumstances.

Notice must be sent within the original period and must state:

the new deadline;
the statutory reason;
the right to complain about the extension.

A statement that “we have 30 days” is not itself a complete response.

The organization still has to conduct the search.

Why deleting requested information is serious

Subsection 8(8) of PIPEDA is backed by an offence provision.

Section 28 states that an organization that knowingly contravenes subsection 8(8), or obstructs the Privacy Commissioner or a delegate during an investigation or audit, may be prosecuted.

The maximum fine is:

$10,000 on summary conviction;
$100,000 for an indictable offence.

This does not mean Steve’s email alone proves that the offence occurred.

It means the preservation issue is not minor.

The regulator must determine:

what records existed;
what was deleted;
when deletion occurred;
who authorized it;
whether responsive records remain in backups or archives;
whether a preservation hold was implemented;
whether the company’s search is complete;
whether the first denial was accurate;
and whether any post-request deletion occurred knowingly.

The deletion admission gives the OPC a concrete reason to examine those questions.

The difference between retention and erasure

Privacy law does not say companies must keep every record forever.

It requires disciplined retention.

Information should not be retained longer than necessary for its lawful purpose.

But information used to make a decision about a person must be kept long enough to allow access.

And information subject to an access request must be preserved while recourse remains available.

Those rules prevent a convenient cycle:

Use personal information against a customer
        ↓
Make a decision affecting the customer
        ↓
Declare the dispute resolved
        ↓
Delete the record
        ↓
Tell the customer nothing exists

That cycle would make access rights meaningless.

The attempted relationship termination

Steve’s response to the PIPEDA request also attempted to end the customer relationship because it was “far too time consuming.”

That statement cannot be isolated from the human-rights chronology.

Before the privacy request:

I reported race and disability discrimination;
management knew I intended to approach the Manitoba Human Rights Commission;
Jason characterized my complaint efforts as harassment;
Adam said I “started” the issue;
Steve invoked numerous angry staff;
Steve ordered all staff to treat me under special restrictions.

Then I exercised a federal privacy right.

Steve responded by proposing the end of the relationship.

That timing raises two separate issues:

Privacy accountability: Was the privacy process being handled objectively by the designated Privacy Officer?
Human-rights reprisal: Was a detriment imposed or threatened because I made protected disclosures or intended to file a complaint?

The Manitoba Human Rights Commission, not Long & McQuade, will determine the human-rights issue.

The timing and wording belong in that investigation.

Wanting my money while closing accountability

Steve repeatedly maintained that I could still shop at Long & McQuade.

The company wanted to preserve the commercial relationship.

It did not want to preserve the accountability relationship.

That distinction is important.

A business cannot claim that access remains equal merely because the cash register remains available.

A customer relationship includes:

ordinary communication;
repair and warranty access;
management escalation;
complaint handling;
freedom from discriminatory restrictions;
privacy rights;
correction of false information;
and access to records used in decision-making.

The position communicated to me was effectively:

We will continue accepting purchases, but we will not discuss the discrimination, privacy, or management issues attached to your customer record.

That is not equal service.

It is monetized segregation of the relationship.

Why disability accommodation matters

My communication style is direct, detailed, persistent, and evidence-heavy.

I disclosed ADHD, autism, a speech disability, and mobility limitations.

A competent accommodation response could have been simple:

assign one contact;
use written communication;
set a predictable response schedule;
separate urgent evidence from routine updates;
provide clear decisions;
identify an appeal or review process;
avoid treating disability-related verbosity as instability.

Instead, communication style became the indictment.

Steve repeatedly characterized me as angry or difficult.

Jason treated continued attempts to obtain an answer as harassment.

Adam said I had started the conflict.

That response failed to separate actual misconduct from disability-related communication differences.

Human-rights accommodation does not require a business to tolerate threats or genuine abuse.

It does require the business to consider whether a disability affects communication and whether a reasonable process can prevent disadvantage.

There is no evidence that Long & McQuade conducted that analysis before imposing the company-wide restriction.

Why Indigenous credibility matters

This began with a credibility judgment.

I reported a specific fault.

My report was dismissed.

Another store accepted the same report.

Technical staff confirmed it.

Management then resisted addressing why my explanation had been treated as unbelievable.

Indigenous customers do not experience credibility in a social vacuum.

Canadian institutions have a documented history of treating Indigenous people as unreliable, threatening, dishonest, intoxicated, unstable, or incapable.

The legal question is not whether a manager openly announced racial prejudice.

Discrimination is often proved through differential treatment, context, pattern, credibility choices, stereotypes, and the absence of a credible non-discriminatory explanation.

The subsequent narrative repeated familiar stereotypes:

difficult;
angry;
upsetting everyone;
harassing;
unsafe to communicate with;
subject to special restrictions.

Those labels carry particular harm when applied institutionally to an Indigenous disabled person.

How management escalation transformed the case

The four managers illustrate four different stages.

Dave Reeves: acknowledgment

Dave reviewed the evidence, recognized the ground issue, said the guitar should have been accepted, apologized, and offered a remedy.

Jason Charney: confrontation

Jason confirmed the technical issue in writing, but later refused substantive discussion, characterized complaint communication as harassment, invoked private-property authority, and attempted to remove me instead of identifying a functioning complaint process.

Adam: reversal

Adam said I “started” the issue and confirmed that Steve had forwarded the matter to him and Jason.

Steve Long: institutionalization

Steve invoked broad staff hostility, complained about preserved conversations, imposed company-wide communication restrictions, retained the sales channel, tried to close the complaint channel, initially denied internal records, admitted deletion practices, attempted to end the relationship, and then backtracked after the privacy complaint was filed.

That is how a repair issue became a governance crisis.

This is not merely an interpersonal dispute

Long & McQuade is a national retailer.

Steve was communicating as its president and designated Privacy Officer.

Jason and Adam were communicating as managers.

Their decisions affected:

access to services;
company-wide staff conduct;
the customer account;
complaint handling;
use of personal information;
record retention;
participation in human-rights and privacy processes.

A corporation acts through people.

Manitoba’s Human Rights Code expressly addresses the acts of officers and employees.

PIPEDA places accountability on the organization and its designated privacy official.

Calling the matter “personal” does not remove corporate responsibility when corporate roles, systems, information, staff instructions, and customer access are being used.

Potential legal issues

The evidence raises several distinct legal issues.

1. Discrimination in services

Manitoba Code section 13 prohibits discrimination in services, goods, benefits, programs, and privileges available to the public.

The question is whether race, ancestry, disability, or social disadvantage contributed to:

diminished credibility;
degrading treatment;
barriers to warranty service;
restricted access to management;
company-wide differential treatment.

2. Failure to accommodate

The question is whether Long & McQuade considered reasonable communication accommodations after learning of ADHD, autism, a lisp, and mobility limitations.

3. Harassment

Section 19 prohibits harassment connected to protected characteristics and requires responsible persons to take reasonable steps to terminate it.

The question is whether management stopped the conduct or expanded it into an institutional narrative.

4. Reprisal

Section 20 prohibits detriment because a person made or may make a disclosure or complaint under the Code.

The timing of restrictions and attempted relationship termination is central.

5. PIPEDA accountability

Principle 4.1 makes the organization and designated Privacy Officer accountable for information under the organization’s control.

6. Limiting use and disclosure

Principle 4.5 prohibits using or disclosing personal information for unrelated purposes without consent or lawful authority.

The question is whether complaint and customer information was used for legitimate resolution or adverse profiling and retaliation.

7. Accuracy

PIPEDA permits individuals to challenge inaccurate or incomplete personal information.

Subjective labels can cause real harm when they drive corporate decisions.

8. Individual access

Principle 4.9 and section 8 require a diligent response, access, explanation of use, and an account of disclosure, subject to specific exceptions.

9. Preservation

Subsection 8(8) requires responsive information to be retained while recourse remains available.

10. Challenging compliance

Principle 4.10 requires an accessible complaint procedure and an investigation.

Having the accused executive investigate himself raises an obvious structural concern.

Potential remedies

If the Manitoba human-rights allegations are established, an adjudicator may order remedies including:

ending the discriminatory conduct;
changes to policies and practices;
human-rights training;
an apology;
compensation for financial losses;
compensation for injury to dignity, self-respect, and feelings, up to $25,000;
exemplary damages where malice or recklessness is established;
affirmative-action or special-program measures.

The OPC may investigate, make findings and recommendations, seek compliance, and in appropriate cases the matter may proceed to Federal Court remedies under PIPEDA.

A knowing preservation violation or obstruction can also engage PIPEDA’s offence provision and financial penalties.

The legal exposure is therefore not limited to a refund or customer-service apology.

It can include:

regulatory findings;
mandatory policy reform;
access and correction obligations;
independent audits;
training;
compensation;
exemplary damages;
court orders;
and statutory fines.

Why this deserves national attention

This case exposes a structural weakness relevant to every Canadian customer.

What happens when:

the president is also the Privacy Officer;
the privacy complaint concerns the president’s conduct;
the president controls management;
the president controls customer restrictions;
the president controls access to records;
the president decides when the dispute is resolved;
and the president says he deletes emails after making that decision?

A privacy policy is meaningless if its enforcement depends entirely on the person accused of violating it.

A human-rights policy is meaningless if the complainant becomes the target of a management campaign for refusing to let the complaint disappear.

An accessibility commitment is meaningless if disability-related communication is converted into evidence of instability.

A reconciliation statement is meaningless if an Indigenous customer’s proven technical report is treated as less credible than management’s preferred story.

This is not only my problem.

It is a governance problem.

The importance of preserving records

Steve wrote:

“Honestly nobody likes having their conversations thrown back in their face.”

He later wrote:

“I don't keep emails once they are resolved.”

Those statements belong beside each other.

The first expresses resentment toward preserved evidence.

The second describes a method through which corporate history can disappear.

My records did not disappear.

I retained:

Jason’s technical confirmation;
Dave’s apology;
Adam’s recorded admissions;
Jason’s recorded confrontation;
Steve’s comments about staff hostility;
the company-wide restriction;
the PIPEDA request;
the immediate denial;
the deletion statement;
the attempted relationship termination;
the OPC filing timestamp;
and the later backtrack.

That is why the history cannot be casually rewritten.

What competent management would have done

The proper response was available from the beginning.

Long & McQuade could have written:

We confirmed the technical fault. The intake should have occurred. We apologize for the treatment. A manager independent of the store will review the human-rights concern. Please direct future evidence to one email address. You will receive a written decision by a specific date. Staff have been instructed not to discuss or engage with you outside that process. All relevant records have been preserved. A separate privacy representative will handle your access request.

That process would have:

acknowledged the confirmed facts;
stopped uncontrolled staff discussion;
accommodated written communication;
prevented retaliatory framing;
preserved records;
separated privacy review from the accused executive;
protected both the customer and the company.

Instead, management repeatedly chose narrative control.

The question Long & McQuade must answer

The issue is no longer whether the guitar had a grounding fault.

Long & McQuade confirmed that it did.

The issue is whether a national retailer can:

discredit an Indigenous disabled customer;
circulate an adverse internal profile;
use complaint communications against him;
restrict every employee’s contact with him;
keep accepting his money while closing accountability channels;
allow corporate narratives to affect a personal court proceeding;
deny the internal record;
admit deleting dispute emails;
and place responsibility for investigating all of that in the same president who personally directed the response.

That is why the matter is before the Office of the Privacy Commissioner of Canada.

That is why the matter belongs before the Manitoba Human Rights Commission.

And that is why the public should know how easily a customer-service complaint can become a corporate surveillance, profiling, and retaliation system when one powerful executive controls the people, the policy, the records, and the official version of history.

Official legal and policy sources

This article documents an active dispute and regulatory complaints. It presents my account and the written management record. Final findings of legal liability belong to the relevant regulators and courts.