ClearBreach

A customer asks what you have in place. This is the assessment you would answer from.

⚠

Sample assessment, fictional organization

ACME Residential does not exist. The staff, the contact address and every answer are invented. What is real is the assessment: this page shows the output ClearBreach produced from those answers, generated by the same product a subscriber uses.

← How ClearBreach works·See a breach assessment verdict →

This is what the Business plan produces for your own organization: $799 a year, plus applicable taxes. PIPEDA, Alberta PIPA and BC PIPA.

See plans and pricing →

ClearBreach Compliance Assessment

ACME Residential

A residential property manager in Alberta and British Columbia. About 40 staff, 2,600 rental units, and records on more than 10,000 tenants and applicants. One IT person and an outside IT provider.

Issued 2026-11-01 · Reference CR-ACMERE-20261101 · AB_PIPA and BC_PIPA and PIPEDA

Where this organization stands

Shown in full. This is the whole result, not a preview. It is about one fictional property manager’s answers, so there is nothing in it to hold back.

At risk

Where they stand

50

questions scored

36

gaps found

7

documents produced

The property manager operates in two provinces, so three frameworks reach it. The areas below are the ten this assessment covers; the ones marked not applicable were ruled out by the answers rather than skipped.

Every area, applicable or not

Shown in full. All ten, including those that came out clean.

AreaIn placePartlyNot startedGaps
Accountability and Governance2123
Privacy Policy and External Communication2336
Consent and Collection2123
Retention and Disposal0134
Security Safeguards3303
Access and Correction0325
Training and Awareness1112
Service Provider Management0224
Incident Management0134
Commercial Email (CASL)4112

What is missing, and what to do about it

Shown in full. Every gap the assessment found, with the wording the subscriber receives.

Critical, 21

Does your organization have a written privacy policy that staff can find and read?

Partly · accountability · moderate effort

Write down how your own people should handle personal information. Put it where they can read it, and set one date a year to look at it again. PIPEDA clause 4.1.4 lists what it has to cover. Procedures to protect the information, procedures for complaints and inquiries, training staff on those policies, and information explaining your procedures. The annual look is the 2012 guidance’s oversight and review plan, which revisits the policies, the training, the breach response and the vendor arrangements.

Have you written down what personal information you collect and why, for each kind of it?

Not started · accountability · moderate effort

Write down each kind of personal information you hold and the reason you collect it. PIPEDA clause 4.2.1 makes this a duty: the organization shall document the purposes for which personal information is collected. One row per kind of information, not per person or per field. The reason is the column people fill in last and worst, and it is the one the Act asks for. "Business purposes" is not a reason. "To book and bill appointments" is, because you can test a retention period against it. Four later duties read from this list. How long you keep each kind. Where to look when somebody asks for their information. What was affected in a breach, and what your published policy has to say.

Does your published privacy policy say what personal information you collect and why, for each kind of information?

Partly · policy · moderate effort

List the kinds of personal information you hold, and what each is used for. PIPEDA clause 4.8.2(c) requires a description of the type of information held, including a general account of its use. Kind by kind, not one sentence covering everything.

Does your published privacy policy name the countries your information goes to, and what the provider there may do with it?

Not started · policy · moderate effort

Name the countries in your policy, and say what the provider there is authorized to do with the information. Alberta PIPA s.6(2) requires both, wherever a service provider outside Canada collects, uses, discloses or stores personal information for you. Neither PIPEDA nor BC PIPA imposes this, so it is an Alberta duty. The federal Commissioner's cross-border guidelines ask for more than Alberta does, and that is asked separately.

Does your published privacy policy explain how someone can ask to see their information, and who to complain to?

Partly · policy · moderate effort

Say how someone asks for their information, and name who complaints and inquiries go to. PIPEDA clause 4.8.2(b) puts the means of gaining access into what you make available. Clause 4.8.2(a) requires the name or title and address of the person complaints go to. Clause 4.10.2 requires the complaint procedures themselves to exist. That they also be "easily accessible and simple to use" is a should under s.5(2), and worth doing anyway.

Do you collect only the personal information you actually need for your stated purpose?

Partly · consent · moderate effort

Collect only what the purpose actually needs, and drop the fields nobody uses. PIPEDA clause 4.4 limits collection to what is necessary for the purposes identified. Clause 4.4.1 adds that both the amount and the type must be limited. BC s.11 limits it to what a reasonable person would consider appropriate.

Before you collect or use staff information without asking consent, do you tell the person and say why?

Not started · consent · quick effort

Tell the person, before you start, that you will be collecting or using their employment information and what it is for. Alberta and BC both allow this without consent and both require the notice. The exemption is what the notice pays for. Alberta s.15(1)(c) and s.18(1)(c) owe it to a current employee, as a condition of collecting or using without consent. BC s.13(3), s.16(3) and s.19(3) owe it to the individual, which is wider: a job applicant and a former employee are covered. If you operate in both provinces, write to the BC rule and you meet Alberta as well. A line in the offer letter or the staff handbook is usually enough.

When someone asks to withdraw their consent, do you tell them what that will mean for them?

Not started · consent · quick effort

When somebody tells you they are withdrawing consent, tell them what follows from it before you act on it. All three Acts require this. PIPEDA 4.3.8 says the organization shall inform the individual of the implications of the withdrawal. Alberta s.9(2) and BC s.9(2) both require the likely consequences. Alberta alone allows you to skip it: s.9(3) excuses the notice where the consequence would be reasonably obvious to the person. BC and PIPEDA have no such exception, so an organization in more than one place should simply always say. Keep it factual rather than discouraging: the Acts let you explain a consequence, not warn somebody off. A short standard paragraph covers almost every case.

Is personal information securely destroyed once it is no longer needed?

Not started · retention · moderate effort

Destroy or anonymize the information once its purpose is finished and no legal or business reason to keep it remains. Write down the procedure for doing it. AB s.35(2) and BC s.35(2) both make the destruction itself a duty in those terms. The word "securely" is part of the duty, not our addition. PIPEDA clause 4.7.5 requires care "in the disposal or destruction of personal information, to prevent unauthorized parties from gaining access". A recycling bin is not disposal. Clause 4.5.3 then makes the guidelines and procedures a duty, even though it phrases the destruction itself as a recommendation. BC puts a floor under all of this. Where you used the information to decide something about somebody, s.35(1) requires you to keep it a year. The Act says that applies "despite" the duty to destroy, so the year wins.

When you use someone’s information to make a decision about them, do you keep it for at least a year afterwards?

Partly · retention · quick effort

Keep personal information for at least one year after you use it to make a decision that directly affects the person. BC PIPA s.35(1) requires it, so that the individual has a reasonable opportunity to obtain access to it. Three things catch people out. It is a floor rather than a ceiling. The Act says it applies "despite" the duty to destroy, so the year beats your ordinary disposal timing. It covers unsuccessful applicants as much as successful ones, which puts a rejected job application squarely inside it. Alberta's s.35(1) is the opposite rule, a limit rather than a floor. An organization in both provinces cannot run one practice built on the Alberta reading.

Do you have a set way of handling it when someone asks to see their own information?

Not started · access · moderate effort

Write down who receives an access request, what they check, and how the information is provided. BC s.23(1) asks for three things, not one. The information itself, how it has been used, and who it was disclosed to. PIPEDA clause 4.9 imposes the same right, and AB s.24(1.1) and s.24(1.2) do the same in Alberta. Two parts of the procedure are duties in their own right and are easy to leave out. If you refuse access, both provinces require the reasons and the provision of the Act you rely on. BC s.30(1) and Alberta s.29(1)(c)(i). Both also require somebody who can answer questions about it. A bare no is not a response. On money, neither province lets you charge for an employee's own information: Alberta s.32(1.1) and BC s.32(1). Where a fee is allowed, both require a written estimate before you do the work. Alberta s.32(3)(a) and BC s.32(3). A bill arriving afterwards is too late.

Are access requests answered within the deadline the law gives you?

Not started · access · quick effort

Put the deadline on the request the day it arrives, and give it an owner. The periods are not the same: PIPEDA s.8(3) gives 30 days, BC s.29(1) gives 30, and Alberta PIPA s.28(1)(a) gives 45. An extension of up to 30 more days is available in stated circumstances, under PIPEDA s.8(4), AB s.31 and BC s.31. Missing the deadline is treated as a refusal. PIPEDA s.8(5) deems it one, and AB s.28(2.1) treats it as a decision to refuse. Either way the person gets a complaint to the Commissioner.

When someone shows you their information is wrong, is it corrected and are the people you gave it to told?

Partly · access · moderate effort

Correct it as soon as you reasonably can. Then tell the organizations you already sent the wrong information to. The two Acts bound that differently. BC s.24(2)(b) covers organizations it went to during the year before the correction. AB s.25(2)(b) covers them where it is reasonable to do so. Where you decide the information is not wrong, AB s.25(3) and BC s.24(3) require the request to be annotated on the record instead. The individual's account of it stays with the file. PIPEDA clause 4.9.5 requires the amendment, and its transmission to third parties where appropriate.

Do you take reasonable steps to keep the personal information you hold accurate and complete?

Partly · access · moderate effort

Take reasonable steps to keep personal information accurate and complete, in proportion to what you use it for. All three Acts require this. PIPEDA Principle 6 says information shall be as accurate, complete and up to date as the purpose needs. Alberta s.33 and BC s.33 both require a reasonable effort. BC narrows its duty to information likely to be used for a decision affecting the person, or likely to be disclosed to another organization. Two things people get wrong. Accuracy is not a reason to collect more: PIPEDA 4.6.2 says you shall not routinely update information unless the purpose needs it. And the standard is what the use requires, so a mailing list needs less than a file a decision rests on.

Is there a set way for someone to complain about how you handled their personal information, and does someone answer?

Partly · access · quick effort

Decide who receives a privacy complaint, how they can be reached, and what happens next. Then write those three things down. PIPEDA clause 4.10.2 requires procedures to receive and respond to complaints or inquiries. Both halves are the duty: a way in, and an answer. Clause 4.10.3 requires telling people who ask that the procedures exist. BC s.5(b) requires a process to respond to complaints, and s.5(c) requires information about it on request. AB s.6(1) carries it as part of the policies and practices duty. Having the route is only half of it. PIPEDA 4.10.4 requires you to investigate EVERY complaint, not the ones that look serious. Where one turns out to be justified, the Act requires appropriate measures, and it names amending your policies and practices as one of them. So a complaint that reveals a bad practice is meant to change the practice, and the change is the evidence the duty was met.

Have the people who handle personal information been trained on how to handle it?

Partly · training · moderate effort

Walk the people who handle personal information through your own policy. What they may collect, who they may give it to, and what to do when something goes wrong. Then repeat it once a year, and keep a list of who has done it. PIPEDA clause 4.1.4(c) makes training staff part of the policies-and-practices duty. Clause 4.7.4 requires making employees aware of the importance of confidentiality. The repetition and the record are asked for in the 2020 joint self-assessment, at ss.4.5 and 4.6.

Do your arrangements with them require comparable protection of that information?

Partly · vendors · significant effort

Get two things into the contract at once, because you will only negotiate it once. Comparable protection of the information, and a requirement that they tell you promptly if they are breached. PIPEDA clause 4.1.3 requires "contractual or other means to provide a comparable level of protection" while a third party is processing it. Comparable to your own, not merely something in writing. The 2020 joint self-assessment covers protection at s.4.17 and breach reporting at s.4.18. The second matters to you directly: your reporting clock runs on information they hold as well as yours.

If you had a reportable breach, would the report reach the right regulator in time?

Not started · incident · moderate effort

Know which regulator applies before you need to. PIPEDA s.10.1(1) requires a report to the federal Commissioner where the breach creates a real risk of significant harm. Alberta PIPA s.34.1(1) requires notice to the Alberta Commissioner without unreasonable delay, on the same test. British Columbia imposes no breach-notification duty at all under PIPA. A BC organization reports only where PIPEDA reaches it.

Do you keep a record of every privacy incident, including the ones you decided not to report?

Not started · incident · moderate effort

Keep a record of every incident, including the ones you decided not to report. PIPEDA s.10.3(1) says "every breach of security safeguards", and the ones you assessed and let go are the half people miss. SOR/2018-64 s.6 requires the records to be kept 24 months, and s.10.3(2) lets the Commissioner ask to see them.

For the people you send marketing email to, can you show how and when they agreed?

Partly · casl · significant effort

Keep, for each contact, how and when they agreed and what they agreed to. CASL s.13 puts the onus of proving consent on whoever claims it. So a list with no provenance is treated as a list with no consent. Section 6(1)(a) is the duty: no commercial electronic message without consent, express or implied.

Have the people whose implied consent under CASL has expired been removed from your commercial email list?

Not started · casl · moderate effort

Record the date the relationship started for everybody on the list through implied consent, and remove them when it expires. CASL gives you two windows and they are not the same length. A purchase, lease or barter gives two years from the transaction, under s.10(10)(a) to (c). A written contract counts while it is current, or if it ended inside that window. An enquiry or application that went nowhere gives six months, under s.10(10)(e). The six-month one is the trap, because a request for a quote feels like a lead for far longer than the law allows. Express consent does not expire. So for a list you cannot date, the practical fix is to ask those people to opt in before the window closes. CASL s.13 puts the burden of proving consent on the sender, so an undated list is one you cannot defend.

Important, 12

Does your published privacy policy say who outside your organization receives personal information, and why?

Partly · policy · moderate effort

Say who outside the organization receives personal information, and why. PIPEDA clause 4.8.2(e) makes this a duty for related organizations such as subsidiaries. Naming your ordinary service providers is not itself a statutory requirement. It is what the regulators look for, and what a customer reading the policy actually wants to know.

If information goes outside Canada, does your published privacy policy say it may be reachable by that country’s authorities?

Not started · policy · moderate effort

Say plainly that information held in another country may be reachable by that country's law enforcement and national security authorities. No Act requires this. Alberta's s.6(2) asks for the countries and the purposes, and stops there. PIPEDA and BC PIPA ask for neither. The OPC's 2009 cross-border guidelines ask for the foreign-authority point specifically, "in clear and understandable language". They add that it should ideally be said when the information is collected, rather than only in a policy. It is here because it is the part a customer has never been told, and would want to know.

Does your published privacy policy explain how someone gets wrong information corrected?

Not started · policy · quick effort

Add a line saying how to ask for a correction, and who to send it to. No provision requires this in the policy. Clause 4.8.2 lists what a policy must contain, and correction is not on the list. What is a duty is doing it. PIPEDA clause 4.9.5 requires the amendment. Alberta PIPA s.25(2) and BC PIPA s.24(2) require the correction, and notice to everyone you sent the wrong information to. Publishing the route is what makes that duty reachable by the person it belongs to.

Do you have a defined approach to how long personal information is kept?

Not started · retention · moderate effort

Decide how long each kind of record is kept, and write it down. This one is a recommendation rather than a duty. PIPEDA clause 4.5.2 says organizations "should" develop guidelines with minimum and maximum retention periods. Section 5(2) of the Act says a "should" imposes no obligation. What IS a duty is clause 4.5: information is kept only as long as the purpose needs it.

Are retention periods set separately for your more sensitive categories of information?

Not started · retention · moderate effort

Set the period by the kind of information, rather than one period for everything. No regulator asks for this. PIPEDA clause 4.5 ties retention to the purpose, and Principle 7 scales safeguards to sensitivity. Joining the two is our own reading. It is offered because information that would do more harm if it leaked is worth holding for less time. A single blanket period is usually wrong in both directions at once.

Is sensitive personal information encrypted, both where it is stored and when it is sent?

Partly · safeguards · moderate effort

Encrypt sensitive information where it is stored and when it is sent. No Act requires this. PIPEDA names encryption once, in clause 4.7.3, and that clause is a recommendation. AB s.34 and BC s.34 ask for reasonable security arrangements and name no method. What makes it worth doing is what happens after a theft. In Alberta decisions P2022-ND-066 and P2022-ND-068 the Commissioner found a real risk of significant harm, because the stolen devices were password protected rather than encrypted.

Is access limited so people can only reach the information their job requires?

Partly · safeguards · moderate effort

Give each person access to the information their job requires and no more. Take it away when the job changes. No Act requires this. PIPEDA names need-to-know access in clause 4.7.3, which is a recommendation. AB s.34 and BC s.34 ask for reasonable security arrangements and name no method. The BC Commissioner's PIPA guide asks for it directly at p.10 question 9. The reason to do it is containment: it sets how much a single stolen password can reach.

Are paper files and portable devices holding personal information locked away when nobody is with them?

Partly · safeguards · quick effort

Lock paper files away, and do not leave laptops or drives unattended. No Act requires a lock. PIPEDA names physical measures in clause 4.7.3, "locked filing cabinets and restricted access to offices", and that clause is a recommendation. AB s.34 and BC s.34 ask for reasonable security arrangements and name no method. What the Acts do settle is that the duty covers paper. Clause 4.7.1 requires protection "regardless of the format in which it is held". The 2020 joint self-assessment asks about secure storage when unattended, at s.5.4.

Do you have a list of every outside company that handles personal information for you?

Partly · vendors · moderate effort

Write the list: payroll, bookkeeping, email, booking, cloud storage, anyone who holds information for you. No Act requires the list itself. PIPEDA clause 4.1.3 and AB s.5(2) make you accountable for what a processor does with the information. The 2020 joint self-assessment asks at s.1.2 where your information is held. The list is how a small organization answers that.

Do your contracts with service providers require them to tell you if they have a breach?

Not started · vendors · significant effort

Require them to tell you promptly if they have a breach, in the contract. No Act requires this clause. The 2020 joint self-assessment asks for it at s.4.18, and no provision in the three Acts makes it mandatory. What makes it worth negotiating is that your own duties do not wait for them. PIPEDA s.10.1 and Alberta PIPA s.34.1 run on personal information under your control. That is true whether it sits on your systems or on theirs, and whether or not anyone told you.

Do you have a written plan for what to do if a privacy breach happens?

Not started · incident · moderate effort

Write down who is told, what is contained first, who decides whether it is reportable, and who makes the report. Then walk it through once with the people named in it. No Act requires a plan. The duties are the report under PIPEDA s.10.1, the record under s.10.3, and the notice under AB s.34.1. The 2020 joint self-assessment asks for a plan at Section 14, and for the walk-through at Sections 14 and 15. It is how a small organization meets those duties under pressure. The point of the rehearsal is finding out that a phone number is wrong while it costs nothing.

Do staff know who to tell, straight away, if they think something has gone wrong?

Partly · incident · quick effort

Tell staff one name and one way to reach it. Say plainly that reporting a suspicion is never held against them. No Act requires an internal escalation route. The duties are the report under PIPEDA s.10.1, the record under s.10.3, and the notice under Alberta PIPA s.34.1. The 2020 joint self-assessment covers incident management at Section 14, including whether the right people can be assembled quickly. A breach nobody passes on is a breach none of those duties ever reach.

Recommended, 3

Has your internal privacy policy been reviewed in the last 12 months?

Not started · accountability · quick effort

Put one date in the calendar each year. The 2012 accountability guidance, Privacy Management Program - At a Glance, asks for an annual oversight and review plan at Part B. It revisits the inventory, the policies, the training, the breach response and the vendor arrangements.

Does privacy training repeat at least once a year?

Not started · training · moderate effort

Repeat the training once a year, and keep a list of who has done it. No Act requires this. PIPEDA clause 4.1.4(c) requires training and says nothing about how often. Neither AB nor BC PIPA mentions training at all. The 2020 joint self-assessment asks for a recurring basis at s.4.5, and for completion to be tracked at s.4.6. The record is what turns 'we train people' into something you can show.

When you stop working with a service provider, does your contract have them return or destroy the information?

Not started · vendors · moderate effort

Say in the contract what happens at the end, the information comes back or is destroyed, and they confirm it. The 2020 joint self-assessment covers return and destruction at ss.4.22 and 4.23.

The documents this produced

Structure only. The headings of each document are listed so you can see what is in it. The text is not shown: these are the drafted documents the subscription provides.

The first page of the generated gap remediation roadmap for ACME Residential, listing the gaps found in priority order with what closes each one.
The first page of one of them. The rest are shown by their headings below, because they are the documents the subscription provides.

Gap Remediation Roadmap

39 sections

  • Required by privacy law
  • 1. Are access requests answered within the deadline the law gives you?
  • 2. Is there a set way for someone to complain about how you handled their personal information, and does someone answer?
  • 3. Before you collect or use staff information without asking consent, do you tell the person and say why?
  • 4. When someone asks to withdraw their consent, do you tell them what that will mean for them?
  • 5. When you use someone’s information to make a decision about them, do you keep it for at least a year afterwards?
  • 6. Do you have a set way of handling it when someone asks to see their own information?
  • 7. When someone shows you their information is wrong, is it corrected and are the people you gave it to told?
  • 8. Do you take reasonable steps to keep the personal information you hold accurate and complete?
  • 9. Does your organization have a written privacy policy that staff can find and read?
  • 10. Have you written down what personal information you collect and why, for each kind of it?
  • 11. Have the people whose implied consent under CASL has expired been removed from your commercial email list?
  • 12. Do you collect only the personal information you actually need for your stated purpose?
  • 13. If you had a reportable breach, would the report reach the right regulator in time?
  • 14. Do you keep a record of every privacy incident, including the ones you decided not to report?
  • 15. Does your published privacy policy say what personal information you collect and why, for each kind of information?
  • 16. Does your published privacy policy name the countries your information goes to, and what the provider there may do with it?
  • 17. Does your published privacy policy explain how someone can ask to see their information, and who to complain to?
  • 18. Is personal information securely destroyed once it is no longer needed?
  • 19. Have the people who handle personal information been trained on how to handle it?
  • 20. For the people you send marketing email to, can you show how and when they agreed?
  • 21. Do your arrangements with them require comparable protection of that information?
  • What regulators look for
  • 22. Do staff know who to tell, straight away, if they think something has gone wrong?
  • 23. Does your published privacy policy explain how someone gets wrong information corrected?
  • 24. Are paper files and portable devices holding personal information locked away when nobody is with them?
  • 25. Do you have a written plan for what to do if a privacy breach happens?
  • 26. Does your published privacy policy say who outside your organization receives personal information, and why?
  • 27. If information goes outside Canada, does your published privacy policy say it may be reachable by that country’s authorities?
  • 28. Do you have a defined approach to how long personal information is kept?
  • 29. Are retention periods set separately for your more sensitive categories of information?
  • 30. Is sensitive personal information encrypted, both where it is stored and when it is sent?
  • 31. Is access limited so people can only reach the information their job requires?
  • 32. Do you have a list of every outside company that handles personal information for you?
  • 33. Do your contracts with service providers require them to tell you if they have a breach?
  • Good practice
  • 34. Has your internal privacy policy been reviewed in the last 12 months?
  • 35. Does privacy training repeat at least once a year?
  • 36. When you stop working with a service provider, does your contract have them return or destroy the information?

Incident Response Plan

26 sections

  • 1. Purpose and scope
  • 2. Immediate actions
  • 3. Roles and responsibilities
  • 4. First response by incident type
  • Ransomware or other malware
  • Lost or stolen device
  • Email sent to the wrong recipient
  • Phishing or a compromised mailbox
  • Cloud storage or website left open
  • An employee looked at records they should not have
  • A supplier or service provider was breached
  • Paper records lost, taken or wrongly disposed of
  • 5. Response steps
  • 5.1 Assess the risk
  • 5.2 Report to the regulator where required
  • 5.3 Notify affected individuals where required
  • 5.4 Notify other organizations where required
  • 5.5 Record the incident
  • 5.6 Learn from the incident
  • 6. Records
  • 7. Regulatory notification
  • Office of the Information and Privacy Commissioner of Alberta
  • Office of the Information and Privacy Commissioner for British Columbia
  • Office of the Privacy Commissioner of Canada
  • 8. Common errors
  • 9. Review

Privacy Management Program

19 sections

  • Part A: Organizational commitment
  • A.1 Senior support
  • A.2 The person accountable
  • A.3 Reporting
  • Part B: Program controls
  • B.1 Personal information inventory
  • B.2 Policies
  • B.3 Risk assessment
  • B.4 Training and education
  • B.5 Breach and incident management
  • B.6 Service provider management
  • B.7 External communication
  • B.8 Safeguards
  • Part C: Ongoing assessment and revision
  • C.1 Review plan
  • Part D: This year's assessment
  • D.1 Standing
  • D.2 What this assessment covered
  • D.3 Area by area

Personal Information Inventory

4 sections

  • 1. What this is for
  • 2. The inventory
  • 3. Filling in each column
  • 4. Keeping it current

Privacy Registers

6 sections

  • 1. Access and correction requests
  • 2. Privacy complaints
  • 3. Privacy incidents
  • 4. Privacy training
  • 5. Commercial email consent
  • 6. Unsubscribe requests

Internal Privacy Policy

11 sections

  • 1. Who this applies to
  • 2. Who is accountable
  • 3. Collecting personal information
  • 4. Using it and sharing it
  • 5. Keeping it safe
  • 6. Getting rid of it
  • 7. Information about our own people
  • 8. When somebody asks for their own information
  • 9. When something goes wrong
  • 10. If this policy is not followed
  • 11. Review

Complaint Handling Procedure

9 sections

  • 1. Purpose
  • 2. Scope
  • 3. How to make a complaint
  • 4. Acknowledgement
  • 5. Investigation
  • 6. Response
  • 7. Escalation to a privacy commissioner
  • 8. Records
  • 9. Review

Offered, and not included by default

You already make your privacy practices available, so a template would invite you to replace a working policy with a generic one. It is below if you want to compare.

Where these figures come from

Every number on this page was produced by the same product a subscriber uses. Nothing here was written by hand or chosen to look good. Issued 2026-11-01, package reference CR-ACMERE-20261101, the same reference the organization’s own documents carry. When the product changes, this page is produced again from it.

The ClearBreach compliance results screen for ACME Residential: an overall status of At Risk, a summary of its outstanding duties, and every one of the ten areas scored separately.
The result screen. Every area scored on its own, and the overall status against all three so it can be placed.

These findings came from answers to twenty five questions. Change four of them yourself and watch the findings move →

Is this right for your business? →