Security and privacy
Section 1 — Scope and definitions
1.1 Scope of this document
This Security & privacy page describes, at a general and public level, the measures and principles applied by Conciergerie Successorale Valora inc. (“VALORA”) to protect the information and files handled in connection with:
- the use of the valoraestate.com website (the “Site”), including the contact/quote forms and related communications;
- the delivery of after-a-death services (access & security, on-site inventory, disposal/storage, liquidation, final report);
- the delivery of during-your-lifetime services (lifetime estate file: estate inventory, document index, access & key register, update plan, handover protocol).
This page aims to explain how we approach security and privacy, without replacing our Privacy policy, which sets out the categories of personal information, the purposes, disclosures to third parties, retention periods and applicable rights.
1.2 Applicable framework (summary)
VALORA operates in Québec. The protection of personal information held, used or disclosed in the course of carrying on an enterprise is governed in particular by the Act respecting the protection of personal information in the private sector (P-39.1) (often associated with “Law 25” for its amendments).
Note on method: security is implemented according to a principle of reasonable measures, proportionate to the sensitivity of the information and the context of use, in accordance with the framework of the Private Sector Act.
1.3 Definitions (for the purposes of this page)
For the purposes of this page:
- Personal information: any information concerning a natural person that allows that person to be identified, directly or indirectly (e.g., contact details, financial information, information related to an estate file, etc.), within the meaning recognized under Québec law applicable to the private sector.
- File: all information (documents, photos, inventory, reports, communications) relating to a mandate entrusted to VALORA (after a death or for a lifetime estate file).
- Confidentiality incident: an event involving, for example, unauthorized access, unauthorized use, unauthorized disclosure, or loss of personal information. The Private Sector Act sets out a management framework and, in certain cases, obligations to give notice or keep a register of incidents.
- Supplier / subcontractor: a third party that may provide technological or operational services (e.g., hosting, storage, e-signature, transport, storage of goods, specialized services) in connection with a mandate, subject to applicable authorizations and the governance set out in the file.
- Security measures: administrative, physical and technological controls intended to protect the confidentiality, integrity and availability of information (e.g., access control, logging, backups), described here in general terms.
- Technological means: notably a website, an online form or an application through which personal information may be collected; the CAI stresses the importance of clearly written policies that are accessible to the public when collection takes place through such means.
Section 2 — Security commitments (general framework)
2.1 Guiding principle: “reasonable” and proportionate measures
VALORA implements security measures to ensure the protection of personal information collected, used, disclosed, retained or destroyed. These measures are designed to be reasonable and proportionate, taking into account in particular:
- the sensitivity of the information (e.g., financial information, estate documents, photos, inventories);
- the purpose of the use;
- the quantity and medium (paper/digital) of the information;
- the operational context (on site, multiple parties involved, urgency, etc.).
Important: “zero-risk” security does not exist. Our commitment is part of a structured and proportionate approach focused on prevention, detection, response and continuous improvement.
2.2 Governance: responsibilities, internal policies and practices
VALORA governs the protection of personal information through governance policies and practices designed to ensure its protection throughout its life cycle. These policies and practices cover in particular:
- retention and destruction;
- the roles and responsibilities of staff members;
- internal complaint-handling mechanisms relating to the protection of personal information.
VALORA also designates a person in charge of the protection of personal information, whose identity and contact details must be made accessible (notably through the Site, where applicable).
2.3 Minimization and “need to know”
VALORA applies a discipline of minimization: collecting and using the information needed to carry out the mandate, while avoiding over-collection. This approach is combined with a need-to-know principle:
- access limited to the people who need the information to carry out the mandate;
- segmentation of information where relevant (e.g., separate access to sensitive documents);
- oversight of internal and external communications according to role and scope.
2.4 Traceability and operational discipline
In estate mandates, VALORA favours a traceability-based approach, notably through:
- logging and registers where required by the mandate (e.g., access to the premises, key handovers);
- structured deliverables (exportable inventory, indexed photo album, decision log) to reduce grey areas and improve governance.
This traceability supports operational and evidentiary clarity, while remaining consistent with minimization (keeping only what is justified by the purpose of the mandate).
2.5 Security culture: awareness and continuous improvement
VALORA strives to maintain a security culture suited to on-site realities and sensitive files, through:
- staff awareness of good practices (confidentiality, care in communications, document handling);
- review and adjustment of practices when risks are identified;
- a continuous-improvement approach (e.g., updating procedures as tools or threats evolve).
Section 3 — Access control, identity and logging
3.1 Principle: “least privilege” and separation of roles
VALORA applies the principle of least privilege: each person accesses only the information needed to perform their tasks, for as long as required. Access is structured by role (e.g., on-site, coordination, administration) and adjusted according to the sensitivity of the file.
This approach reflects the obligation to protect personal information through reasonable security measures (notably based on its sensitivity and context).
3.2 Identity management and authentication
When technological tools are used (e.g., storage, document sharing, e-signature, file management), VALORA favours:
- individual user accounts (no shared accounts, where possible);
- strong authentication mechanisms (MFA) where available and proportionate to the risk;
- disciplined credential management (creation, deletion/deactivation, reset) to limit the risk of unauthorized access.
Exact measures vary depending on the tool and the scope of the mandate, but the logic remains the same: access that is controlled, traceable and reviewable.
3.3 Access control for files and data (digital)
VALORA structures access to files and documents according to:
- per-file permissions (e.g., file A ≠ file B);
- limits on external sharing (e.g., controlled links, identified recipients);
- a separation, where relevant, between:
- operational management documents (inventory, indexed photos, reports),
- highly sensitive documents (e.g., certain financial information), with restricted access.
The goal is to avoid “implicit access” and to keep the access granted consistent with the purposes of the mandate.
3.4 Physical access control (on site) and “chain of custody”
On site, VALORA applies access-control practices suited to estate mandates:
- key register (who holds what, handover/return dates, restrictions);
- access log (who entered, when, why), where the context warrants it;
- basic instructions to reduce ambiguity when several people are involved.
These mechanisms aim to reduce grey areas regarding access and support traceability, while remaining proportionate to the file (no unnecessary over-documentation).
3.5 Logging: purpose, minimization and duration
Where logging is in place (depending on the tool and the file), VALORA aims for useful logging:
- to detect and understand unauthorized access or anomalies;
- to support operational traceability (what was done and when).
Logs are retained on the basis of necessity and minimization and must not become a disproportionate collection of information. Exact parameters (type of logs, duration) are adjusted according to risk, sensitivity and context.
3.6 Access review and removal
VALORA aims to:
- review access when the scope changes (new milestone, new supplier, change of role);
- remove or deactivate access when no longer required (end of mandate, staff changes, etc.).
This discipline reduces the risk of residual access and supports overall compliance with the principle of protecting information.
Section 4 — Encryption, backups and continuity (a realistic level, without overpromising)
4.1 Principle: protecting confidentiality, integrity and availability (proportionately)
VALORA aims to protect:
- confidentiality (preventing unauthorized access),
- integrity (preventing unauthorized alteration),
- availability (maintaining legitimate access when required),
through reasonable measures proportionate to the sensitivity of the information and the context of use.
4.2 Encryption: “in transit” and “at rest” where available and appropriate
When VALORA uses technological tools (e.g., storage, sharing, file management, e-signature), we favour solutions that offer, where available, protections such as:
- encryption in transit (secure communications between systems),
- encryption at rest (protection of stored data).
Important: the exact level of encryption depends on the tools selected and the scope of the mandate. We avoid publicly disclosing specific technical parameters, while keeping the objective of limiting the exposure of information and reducing the risk of unauthorized access, in accordance with the obligation to take reasonable security measures.
4.3 Backups: a reasonable recovery objective
VALORA implements backup mechanisms suited to the criticality of operational information (inventories, reports, supporting documents and deliverables), to reduce the impact of accidental loss or an incident.
- Backups are designed to allow reasonable recovery of information, depending on the context and the tool used.
- The terms (frequency, retention, scope) are determined according to volume, sensitivity, use and risks.
We avoid publishing quantified commitments (e.g., guaranteed timeframes) when this is not realistic for field operations; the objective remains proportionate resilience.
4.4 Restoration: pragmatic checks
Where applicable to the tools selected, VALORA performs pragmatic checks to make sure that backup and restoration mechanisms are usable (e.g., spot checks, checks during major changes or as needed).
4.5 Business continuity: operational priorities
If a tool becomes unavailable or an incident occurs, VALORA applies a proportionate continuity approach based on:
- prioritizing critical actions (e.g., access, inventory, deliverables required at the milestone),
- using reasonable alternative mechanisms (e.g., fallback procedures, rescheduling, limited manual consolidation),
- documenting impacts when deliverables or timing are affected.
This approach is aligned with the obligation to protect information and to manage risk reasonably in the course of business.
4.6 Limitations (reality clause)
No security measure can eliminate all risk. VALORA is committed to a structured and proportionate approach and to adjusting its practices as risks or tools evolve, in compliance with the applicable framework.
Section 5 — Incident management (cyber/breach) and register
5.1 Principle: a structured, proportionate, documented response
VALORA applies an incident management process designed to:
- detect and assess the event (nature, scope, data involved);
- contain and limit the impact (reasonable immediate measures);
- correct the cause or reduce the likelihood of recurrence;
- document the incident and the actions taken.
This approach reflects the obligations of the Private Sector Act regarding confidentiality incidents (definition, measures, keeping a register, notices where required).
5.2 Internal process (typical steps)
Without claiming a heavy “corporate” model, VALORA follows a pragmatic process:
- Reporting and assessment
- receipt of a report (internal or external);
- initial assessment (urgency, systems involved, data potentially affected).
- Containment / immediate measures
- restricting access, suspending an account, removing a shared link, etc., as the case may be;
- measures to reduce the risk of harm.
- Analysis and assessment
- identification of the personal information involved;
- analysis of the probable cause (e.g., human error, unauthorized access, loss, supplier incident).
- Remediation and prevention
- reasonable corrective measures (procedure, configuration, access, training, etc.);
- adjustments to controls where relevant.
- Closure and documentation
- entry in the incident register;
- lessons learned and follow-up actions.
5.3 Register of confidentiality incidents
VALORA keeps a register of confidentiality incidents, in accordance with applicable requirements. The register keeps a record of incidents and how they were handled, notably to support:
- internal traceability;
- compliance with the obligations of the Act;
- continuous improvement of practices.
Note: the register may include items such as the date, the nature of the incident, the information affected (categories), the measures taken and, where applicable, the notices sent, as required by the legal framework.
5.4 Notice to the CAI and to individuals: when and why
When a confidentiality incident presents a risk of serious injury, the Private Sector Act provides for obligations to notify:
- the Commission d’accès à l’information (CAI); and
- the person concerned, subject to the terms set out in the Act (and applicable exceptions).
VALORA assesses the risk taking into account, in particular:
- the sensitivity of the information involved;
- the anticipated consequences of its use;
- the likelihood that it will be used for harmful purposes.
5.5 Mitigation measures and pragmatic communications
Depending on the context, VALORA may implement reasonable measures to reduce the risk, for example:
- deactivating access, resetting links/credentials, limiting sharing;
- targeted notices to the people concerned about precautions to take (without causing undue alarm);
- coordination with a technology supplier when the incident involves it.
External communications are framed to be factual (what, when, plausible impact, measures taken) and to avoid unrealistic promises, while meeting notice requirements where they apply.
5.6 “Incident / privacy” point of contact
VALORA maintains a point of contact to:
- report an incident or a privacy concern;
- exercise rights relating to personal information.
(The contact details of the person in charge appear in the appropriate documents, notably the Privacy policy.)
Section 6 — Management of suppliers and subcontractors
6.1 Principle: use of suppliers, with controlled access
VALORA may use suppliers and subcontractors (e.g., hosting, storage, e-signature tools, messaging, operational services such as transport and storage, or specialized subcontracted services) when necessary to carry out a mandate.
In all cases, the objective is to:
- limit access to personal information to what is strictly necessary (minimization);
- govern access and use through reasonable measures;
- maintain traceability and governance consistent with the mandate.
6.2 Typical categories of suppliers (examples)
Depending on the mandates and tools selected, VALORA may use or coordinate suppliers, including:
- Technology: hosting, storage and sharing, productivity tools, e-signature, CRM/file management (if deployed), analytics (if enabled).
- On-site operations: transport, storage, disposal and processing of goods (depending on the channels), as well as occasional services.
- Specialized services: e.g., subcontracted preparation of tax returns (in accordance with the defined mandates and scope).
These examples are not exhaustive. The suppliers actually used depend on the mandate and operational choices.
6.3 Contractual framework and supplier obligations
When VALORA entrusts a third party with collecting, retaining, using or disclosing personal information on its behalf, the Private Sector Act requires a written contractual framework, including in particular:
- the supplier’s obligation to implement security measures;
- the obligation to notify VALORA of any confidentiality incident;
- conditions on the disclosure of information (e.g., limitation, authorization);
- requirements regarding the destruction or return of information at the end of the mandate.
6.4 Access control and operating principles
In practice, VALORA applies a “reasonable” discipline to reduce exposure:
- access limited to only the people/functions needed at the supplier;
- document sharing through controlled mechanisms (identified recipients, limited links where possible);
- removal/deactivation of access when the need no longer exists (end of milestone, end of mandate);
- framing of communications (avoiding sending sensitive data through uncontrolled channels).
6.5 Operational subcontracting: decisions, approvals and evidence
When suppliers work on site (e.g., storage, transport, disposal), VALORA oversees the work through:
- a clear scope (what, when, how);
- approvals when irreversible actions or significant disbursements are involved;
- supporting documents, where available (slips, confirmations, receipts), and their inclusion in the file.
6.6 Transparency: where it is documented
Details on:
- the categories of personal information,
- the purposes,
- disclosures to third parties,
- and, where applicable, the possibility of transfers outside Québec (if applicable)
are described in more detail in the Privacy policy, which must be accessible through the Site when collection takes place by technological means.
Section 7 — Data outside Québec (if applicable): principle and governance
7.1 Principle: transparency and caution
VALORA may, where applicable, use suppliers or technology solutions whose infrastructure or certain operations involve the disclosure of personal information outside Québec (“transfer outside Québec”). In such a case, VALORA takes a cautious approach: limiting what is disclosed, governing the disclosure and ensuring that the level of protection remains adequate given the sensitivity of the information.
7.2 Legal framework: assessment and safeguards before disclosure
When personal information must be disclosed outside Québec, the Act respecting the protection of personal information in the private sector requires prior safeguards, notably:
- a privacy impact assessment (including, among other things, the sensitivity of the information, the purpose, the protective measures, and the legal framework applicable in the destination jurisdiction); and
- the conclusion of a written agreement containing measures to ensure adequate protection.
Deliberately cautious wording: VALORA does not state here that transfers systematically take place; this section governs the case where a transfer would be necessary.
7.3 Minimization and operational choices
Should a transfer outside Québec be required, VALORA aims to:
- limit disclosure to the information needed for the purpose;
- favour, where reasonable, configurations that reduce exposure (e.g., restricted access, segmentation of files);
- avoid over-collection and uncontrolled sharing.
7.4 Information for the persons concerned
Information on disclosure to third parties and, where applicable, on the possibility of disclosures outside Québec is set out in the Privacy policy, which describes the categories of information, the purposes, and disclosure practices.
Section 8 — Privacy settings, technologies and consent
8.1 Principle: transparency and control “where relevant”
VALORA aims to use technologies and privacy settings sparingly: only when necessary for the operation of the Site, the handling of requests (quotes and assessments) or the performance of a mandate. When technologies can identify, locate or profile a person, transparency and prior information are essential.
8.2 Identification, location or profiling technologies (if used)
If VALORA uses, on the Site or through digital tools, a technology that allows a person to be identified, located or profiled, VALORA aims to:
- inform the people concerned beforehand;
- indicate the means available to activate these functions (or, where applicable, to configure or disable them), in accordance with the applicable framework.
8.3 Consent: “transactional vs. marketing”
VALORA distinguishes between:
- transactional communications (responding to a request, managing a mandate), which are necessary to the service relationship;
- marketing communications (newsletter, offers), which require separate consent and appropriate withdrawal and unsubscribe mechanisms.
8.4 Cookies, trackers and analytics
When the Site uses cookies/trackers (e.g., for statistics, performance or conversion measurement), VALORA aims to:
- clearly describe the categories of cookies/trackers and their purposes;
- offer, where relevant, configuration choices (notably for non-essential cookies).
Details (categories, purposes, duration, preference management) are set out in the Cookie policy, available on the Site.
8.5 Communications and document sharing: operational caution
To reduce exposure, VALORA favours pragmatic practices:
- avoiding sending highly sensitive information through generic, unsecured channels;
- using controlled sharing mechanisms when documents need to circulate (identified recipients, limited access where possible);
- limiting the information shared to what is needed for the mandate (minimization).
Section 9 — Retention and destruction
9.1 Principle: keep only what is necessary
VALORA aims to retain information (including the components of a file: inventory, photos, reports, communications) only for as long as necessary for the purposes for which it was collected or used, in particular:
- processing a request (quote and assessment);
- carrying out a mandate and delivering the agreed deliverables;
- ensuring reasonable administrative follow-up (billing, file management, relevant operational evidence).
This principle is part of a governance approach to protecting personal information within an enterprise.
9.2 Retention parameters: adapted to the mandate and the risk
The retention period may vary depending on:
- the nature of the mandate (partial vs. full service);
- the sensitivity of the information;
- operational needs (e.g., deliverables, follow-up, traceability);
- applicable legal obligations (if any).
VALORA avoids “indefinite by default” retention: the objective is justified and proportionate retention.
9.3 Secure destruction and disposal
When retention is no longer necessary, VALORA aims for the secure destruction of information according to its medium:
- secure deletion of digital copies and removal of access;
- secure destruction of paper documents where applicable;
- internal confirmation or documentation of the disposal where relevant (depending on the type of file).
These practices aim to reduce the risk of unauthorized access and are aligned with the obligation to take reasonable security measures.
9.4 Handover of deliverables and file closure
At the end of a mandate (or at the end of a major milestone), VALORA hands over the agreed deliverables (e.g., final report, exportable inventory, index of supporting documents) and applies a closure process:
- confirmation of the items handed over;
- clarification of any items retained temporarily (if applicable) and of the retention/destruction terms;
- removal of external access when no longer required.
Details (typical retention periods, exact terms, deletion requests, etc.) are set out in the Privacy policy and, where applicable, in the terms of the mandate.
Section 10 — Security & privacy contact
10.1 Person in charge and point of contact
For any question about security, confidentiality or the protection of personal information, you may contact VALORA’s person in charge of the protection of personal information.
The Act respecting the protection of personal information in the private sector provides that the person exercising the highest authority within the enterprise is responsible for the protection of personal information, unless this function is delegated in writing, and imposes related governance obligations.
Contact details (to be inserted)
- Name / title: Marie-Josée Legault, Privacy Officer (RPRP) — VALORA
- Email: legal@valoraestate.com
- Mailing address: 2572, boul. Daniel-Johnson, 2e étage, Laval, Québec, H7T 2R3
10.2 Reporting an incident or a concern
If you believe that personal information has been:
- lost,
- disclosed to a third party without authorization,
- accessed without authorization,
- or used inappropriately,
you may contact VALORA using the contact details above. VALORA will assess the information received and apply its incident management process, including keeping a register and, where applicable, sending the required notices when the risk of serious injury warrants it.
10.3 Requests concerning your personal information
To exercise your rights or make a request concerning your personal information (access, correction, withdrawal of consent where applicable, etc.), please consult the Privacy policy, which describes:
- the categories of information collected,
- the purposes,
- disclosures to third parties,
- and the request procedure.
Section 11 — Updates
11.1 Changes to practices and to this document
VALORA may update this Security and privacy page to reflect:
- changes to its services (after a death / lifetime estate file);
- changes in technology tools or suppliers;
- improvements to its operational practices;
- or changes to the applicable framework.
Any update aims to keep the information clear and consistent with the Privacy policy and the Cookie policy, where these documents apply.
11.2 Dates
- Effective date: February 26, 2026
- Last updated: February 26, 2026
11.3 Where to find the current version
The current version of this page is published on valoraestate.com and accessible via the Site’s footer.
