Privacy Policy
MicroAge Abitibi-Témiscamingue takes the protection of personal information seriously. This policy explains what information will be collected through our cloud services, why we collect it, who we share it with, how long we keep it, and what your rights are.
It applies to the client portal (https://portail.microage-at.com) and to every product available through it. It does not replace the policies of the MicroAge Canada marketing website, which cover that website only.
The French version of this policy prevails in case of discrepancy.
Privacy Officer
Any question, access or correction request, or complaint regarding personal information may be addressed to our Privacy Officer:
- Eric Beaupré, Vice-président;
- Email: administration@microage-at.com;
- Phone: 1 800 249-8263;
- Address: 447 Av. Larivière, Rouyn-Noranda, QC J9X 4H9, Québec, Canada.
We respond to requests within a maximum of 30 days.
Our role: service provider, and sometimes controller
Our role differs depending on the information involved. The distinction matters because it determines who you must direct your requests to.
| Information | Our role | Who to contact |
|---|---|---|
| Employees of our client organizations (Microsoft 365 directory, signatures, service tickets, cloud environment) | Service provider — we process this information on behalf of your employer, on their instructions | Your employer, as they are responsible for it. We will assist them in handling your request. |
| External recipients of a secure transfer | Controller — no contractual relationship with us | Our Privacy Officer |
| Holders of a local portal account (clients without Microsoft 365) | Controller | Our Privacy Officer |
| Our employees and operators | Controller | Our Privacy Officer |
When we act as a service provider, we are bound to your employer by a written agreement covering purposes, security measures, incident notification and the fate of the information at the end of the contract.
What our tools do not do
It is just as useful to state what our tools do not do. These statements are verifiable in the configuration of our services.
- We do not read the content of your emails. The signature module runs only while a message is being composed, to insert a signature block. It is not triggered on send or on read;
- We do not track email opens. No tracking pixel, no per-message identifier, no read receipts;
- We run no advertising and never sell, rent or trade your personal information;
- We use no analytics tooling (Google Analytics, Meta Pixel, Matomo or equivalent) on our services;
- We build no profiles for commercial purposes and make no decision about you on a solely automated basis;
- We do not access the decrypted content of the files you send through the secure transfer service.
This list is not exhaustive.
Information processed
Client portal (all products)
- Professional identity: first and last name, work email address, Microsoft Entra identifier, organization, role assigned in the portal;
- Local accounts (clients without Microsoft 365): email, password hash (Argon2id — never the password itself), encrypted two-factor authentication secret, one-time codes, sign-in attempts;
- Access log: for every authenticated request, the user identifier, the IP address, the browser, the page visited and the response code. See the “IP addresses” section below;
- Preferences: display language, home page layout, cookie choices;
- Consent records: when you accept our terms or acknowledge this policy, we keep your identifier, the document version, the language displayed, the date, the IP address and the browser as evidence.
Outlook Signature
- Microsoft 365 directory record, synchronized from Microsoft Entra: first and last name, display name, job title, department, email, sign-in identifier, phone numbers (office, mobile, fax), office location, the organization’s postal address, company name, account status and group memberships;
- We also keep a complete copy of the record as returned by Microsoft, including the list of assigned Microsoft 365 licences. This copy is used to resolve signature variables and for diagnostics. We state this explicitly rather than imply a narrower collection than actually occurs;
- Custom values you enter yourself (for example an extension number or pronouns), which override the directory value;
- Computed signature, briefly cached to avoid recomputing it for every message;
- Activity log: one entry per signature generation, with the user identifier, IP address, device and timestamp.
Secure Transfer
- Senders: Microsoft 365 identity, authorization to use the service;
- Recipients: email address, hash of the one-time code (never the code itself), number and dates of openings, IP address and browser of each event;
- Content: subject, message body, files and replies (encrypted at rest). We keep the original file name, type, size and checksum;
- Electronic signature: signer’s name, email, expressed consent, IP address, browser, timestamp and a digital fingerprint of the signed document. These elements establish the evidential value of the signature and appear on the certificate.
Other products
- Environment review: user identifiers and names, last sign-ins, usage statistics (email, Teams, OneDrive), licences, security posture, devices and backups for your organization;
- Tickets and billing: contact details, service ticket and note content, contracts, hours and invoices.
IP addresses in our logs
We have chosen to keep the real IP address in our logs rather than anonymize it. We prefer to say so plainly.
Why: these logs are used to detect abnormal access, establish the scope of a security incident and diagnose outages. A truncated address makes all three impractical.
How we limit the scope:
- high-volume logs have a short retention period (see “Retention”);
- they are partitioned by organization at the database level;
- they are append-only, no one, including us, can alter them afterwards;
- for secure transfer, the IP address of each event is erased after 90 days while the event itself is kept;
- reading these legal pages is not logged: you can read this policy without leaving a trace.
Why do we process this information
We use your information in order to:
- Deliver the requested services, in particular generating and applying an electronic signature, transmitting files in encrypted form, displaying the state of your environment or handling a service ticket;
- Authenticate users and manage access according to the roles and permissions assigned;
- Maintain the security of systems and data, by detecting intrusion attempts, preventing abuse and determining the scope of a security incident;
- Provide technical support and resolve issues related to the services used;
- Meet our legal and regulatory obligations by retaining the required evidence, such as consents and electronic signatures.
We reuse this information for no other purpose. No client data is used to train any artificial intelligence model.
How this information is collected
- From your organization: synchronization of the Microsoft Entra directory, authorized by an administrator of your organization;
- Directly from you: portal forms, custom signature values, sending or receiving a secure transfer;
- Automatically: technical logs generated by your use of the service (IP address, browser, timestamp).
We purchase no lists and collect no information from data brokers.
Cookies
Our services use only strictly necessary cookies: session persistence, cross-site request forgery protection, two-factor authentication, display language and network security. We use no advertising or analytics cookies.
These cookies do not require your prior consent, but we inform you of them. The full inventory (name, purpose and duration of each) is in our cookie policy. You can review and change your preferences at any time from the Cookie preferences page.
Hosting and delivery
All of our services are hosted in the Microsoft Azure Canada East region, located in Quebec City: application servers, database, file storage and secret vault. Your data is stored there and stays there.
Delivery of our services relies on the global Cloudflare network (attack protection, web application firewall, rate limiting). That network terminates the secure connection at the point of presence closest to the person connecting and therefore has access to the content exchanged during that step. The points of presence serving our services are located in Canada; that location depends on the connecting person’s network and is not guaranteed.
Our artificial intelligence assistant is deployed in Quebec within an isolated private network, with no exposure to the Internet.
Providers involved
| Provider | Role | Location |
|---|---|---|
| Microsoft Azure | Application hosting, database, storage, secret vault | Quebec (Canada East) |
| Microsoft Entra ID and Microsoft Graph | Authentication and source of your organization’s directory | Depends on your Microsoft 365 tenant configuration |
| Azure OpenAI | Drafting assistant (optional) | Quebec (isolated private network) |
| Cloudflare | Content delivery network, web application firewall, rate limiting | Global network (Canadian points of presence for our services) |
| Kaseya / Datto (Autotask) | Service ticket and billing management system, when that product is enabled | Per the applicable contract (see next section) |
Each of these providers is bound by an agreement governing the confidentiality and security of the information entrusted to them.
Disclosure outside Quebec
Because our primary infrastructure is located in Quebec, the vast majority of the information we process never leaves it.
Disclosure outside Quebec may nonetheless occur in the following cases:
- Microsoft Entra and Microsoft Graph: authentication and directory reads occur against the Microsoft infrastructure associated with your organization’s Microsoft 365 tenant, whose region is determined by that organization;
- Service ticket management system: when that product is enabled, depending on the hosting chosen by the provider;
- Content delivery network (Cloudflare): traffic is routed through the point of presence closest to the person connecting. Those serving our services are located in Canada, but a connection made from abroad may be served outside Quebec.
Before any disclosure outside Quebec, we carry out a privacy impact assessment to ensure the information receives adequate protection.
Retention periods
| Information | Period |
|---|---|
| Directory record, signature values, templates | Duration of the contractual relationship with your organization |
| Signature module activity log | 180 days, automatic purge |
| Portal access log | 90 days, automatic purge |
| Configuration log (who changed what) | Duration of the contractual relationship; erased when the client record is deleted |
| Cached computed signature | A few minutes; recomputed on every change |
| Secure transfer content (message, files, replies) | 30 days after expiry or revocation, by default. Erasure is cryptographic: the keys are destroyed, permanently rendering the content unreadable. |
| IP address of transfer events | Erased after 90 days |
| Transfer events (without IP address) | 12 months by default |
| Sign-in attempts | 30 days |
| One-time codes | 24 hours |
| Terms acceptance records | Kept as evidence of consent, including after the relationship ends |
| Electronic signature certificate | Kept with the signed document, as evidence |
Some of these periods are configurable by your organization. Those shown are the default values.
At the end of the contractual relationship, erasure of a client record is orchestrated: cascading deletion in the database, file deletion, cache purge and content delivery network purge.
Security measures
- Partitioning by organization enforced at the database level itself, not only in application code;
- Encryption in transit (TLS) and at rest. Secure transfer content is encrypted with a key unique to each send;
- Mandatory two-factor authentication for local accounts; passwords protected with Argon2id;
- Role-based access control, enforced deny-by-default;
- Append-only logging of access and configuration changes, including when one of our operators works in your record;
- Secrets kept in an Azure Key Vault, never in code;
- Web application firewall and rate limiting at the network edge;
- Internal penetration testing and security code reviews.
Our operators may access a client record to provide assistance. Such access is scope-limited, systematically logged and visually flagged in the interface for its entire duration.
Your rights
Quebec law grants you the following rights:
- Access: obtain the list of information we hold about you;
- Correction: have inaccurate, incomplete or ambiguous information corrected;
- Withdrawal of consent, where processing relies on it;
- Portability: receive, in a structured and commonly used technological format, the computerized information you provided to us;
- De-indexing: request that dissemination of information cease, or that a hyperlink giving access to it be removed, under the conditions set out by law;
- Complaint: if our response does not satisfy you, you may file a complaint with the Commission d’accès à l’information du Québec.
Write to administration@microage-at.com. We respond within a maximum of 30 days and may request proof of identity before acting.
If you are an employee of a client organization, direct your request to your employer, who is responsible for that information. Write to us anyway if you are unsure who to contact, we will point you in the right direction.
Automated decisions and profiling
We make no decision about you based exclusively on automated processing.
Our services do include automatic processing — selecting the applicable signature template based on your group membership, or temporarily locking access after several failed sign-in attempts — but none produces legal effects or significantly affects you within the meaning of the law. A human can always intervene.
We carry out no profiling, meaning no collection intended to assess your personal characteristics, performance or behaviour.
Confidentiality incidents
We maintain a register of confidentiality incidents. Where an incident presents a risk of serious injury, we promptly notify the Commission d’accès à l’information and the individuals concerned, as well as the client organization when we act on its behalf.
To report a vulnerability or an incident: administration@microage-at.com.
Changes to this policy
We may amend this policy to reflect changes in our services or in the legal framework. The version in force and its date appear at the top of the page.
Any substantial change is brought to your attention at your next sign-in to the portal, where we ask you to acknowledge it.
Contact us
MicroAge Abitibi-Témiscamingue
447 Av. Larivière, Rouyn-Noranda, QC J9X 4H9, Québec, Canada
Email: administration@microage-at.com
Phone: 1 800 249-8263
See also our terms of use and our cookie policy.