Version 2.1 · Final, 2026-11-01 · Effective: 2026-11-19
Replaces the policy of June 14, 2019.
The French version is the official version. This English text is a courtesy translation.
1. Who is responsible for your information
AdocSys, 657 route Marie-Victorin, Verchères, Quebec J0L2R0, Canada — NEQ 2269434314.
Person responsible for the protection of personal information:
Mathieu Peloquin, President
Email: support@adocsys.net · Phone: 1 877 749-9579 · Mail: the address above, attention of the person responsible.
Requests for access, rectification, portability or de-indexing, and complaints, go to that person. That person also decides what to do when an incident occurs.
2. What this policy covers
It covers the personal information we collect:
- on adocsys.com and our other sites;
- when you order a service, request a quote, contact support or call us;
- when you are a client and we manage your account, billing and infrastructure.
It does not cover personal information that our clients hold about their own customers, subscribers, patients or members and store on our servers: for that information, the client is the person responsible and we act as mandatary (see section 10).
3. Information we collect
| Category | Examples | Source |
|---|---|---|
| Identity and contact | name, business, email, phone, address | you, at order or support |
| Account and authentication | username, encrypted password, connection IP, access log | you and our systems |
| Billing | name, address, invoice history, payment status, last four digits of the card | you and Stripe |
| Hosted content | emails, files, sites, databases | you, in the course of the Service |
| Support | messages, attachments, screenshots, intervention notes | you and us |
| AI assistance | the text, files and tool output submitted to an AI model when a task requires it (section 6.1) | you, in the course of the Service |
| Technical | IP address, browser type, pages viewed, server logs | automatically |
| Cookies | session cookies and, where applicable, analytics cookies | automatically (section 12) |
We do not collect information about your health, political opinions, religion, sexual orientation or criminal record, and we do not ask you to send us any.
4. Why we use it
| Purpose | Information | Basis |
|---|---|---|
| Provide, host, configure and maintain the Service | account, content, technical | performance of the contract |
| Invoice, collect and keep accounts | billing, contact | contract and legal obligation |
| Answer support requests and diagnose | support, technical, account | contract and serious and legitimate interest |
| Protect our systems, prevent fraud and abuse | technical, logs, account | serious and legitimate interest |
| Tell you about a change, outage or incident | contact | contract, legal obligation |
| Send you news and offers | consent (CASL), withdrawable at any time | |
| Meet tax and legal obligations | billing | legal obligation |
| Prepare, summarise, translate, search or draft with AI assistance, only where the task requires it | the document, message or file concerned | performance of the contract |
We do not use your information for other purposes without informing you and, where the law requires it, without your consent.
5. Consent
We collect and use your information with your consent, except where the law allows us to do without it (performance of a contract, legal obligation, serious and legitimate interest under the conditions set by law).
Consent must be clear, free, informed and given for specific purposes. It may be implied where the law allows — for example, when you write to us to obtain a service. It is explicit for anything sensitive or unexpected.
You may withdraw your consent at any time, subject to legal retention obligations and to the consequences for a service that depends on it. Write to support@adocsys.net.
6. Disclosure to third parties
We do not sell or rent your personal information. Ever. That is not a figure of speech: it is the business model.
We disclose it only to providers that let us deliver the Service, and only what is necessary:
| Provider | Role | Information | Location |
|---|---|---|---|
| Stripe | payment processing | contact, billing, card (we never see it) | United States / Ireland |
| OpenProvider | domain registration and renewal | registrant contact, as required by ICANN or CIRA | Netherlands |
| eM Client | mail client licences | licence address | Czech Republic |
| 1Password | password manager licences | licence address | Canada |
| Gestion France Chapleau | bookkeeping | billing | Verchères, Quebec |
| Google Analytics | audience measurement | browsing data (section 12) | United States |
| LM Studio — Element Labs, Inc. | cloud AI inference for our internal tools, where local processing cannot carry the task (section 6.1) | the request submitted: text, attached files, tool output | United States |
| Authorities | where required by law, a court or an order | what is required | — |
We require these providers to protect the information and not to use it for their own purposes. For the AI provider that requirement takes the form of a published Zero Data Retention commitment: the request is processed transiently, is not kept after the answer, and is not used for training.
This list does not describe every piece of software we run. Billing, control panels, mail and hosting servers run on our own infrastructure, under our control. They are not third parties: they do not receive your information and do not disclose it to anyone. We do not publish an inventory of our infrastructure — that would be a map for anyone looking for a door — and the law does not require it. What must be named are the providers that receive personal information, and every one of them is listed above.
6.1 AI assistance
Part of our work is done with an AI agent. The rule that governs it is simple: the model runs on our own machines unless the task genuinely needs more computing power than they have.
- Here (the default). Nothing leaves the equipment we control. Your Content, our notes and your messages stay here.
- In the cloud (the exception). Only the request the task needs is sent: the text, the attachments that task needs, and the output of the tools it used. Inference runs in the United States, in LM Studio Secure Cloud, operated by Element Labs, Inc., through its inference and search subcontractors.
- Never sent: passwords, authentication secrets, payment card data, and the content of a mailbox or a drive that the task does not require.
- Not kept, not used for training. The provider's commitment is Zero Data Retention: the request is processed, the answer is returned, nothing is stored.
- A person decides. AI assists; it does not decide (section 14). Every deliverable is reviewed before it leaves us.
- No client content in a public model. What is sent is limited to what the task requires, under the mandate described in section 10 and in the Terms, section 8.
If you would rather that none of your information ever reach a cloud model, tell us: it is a setting we apply to your account, and it costs nothing.
7. Information disclosed outside Canada
Your hosted Content — email, files, sites, databases — stays in Canada, on servers we operate, with a copy replicated to a second Canadian site. No cloud provider hosts that data. It does not travel to an AI model unless the task requires it, and section 6.1 states exactly what is sent when it does.
Five peripheral services involve processing outside Canada:
| Service | What is disclosed | Where |
|---|---|---|
| Stripe | contact and billing data | United States and Ireland |
| OpenProvider | domain registrant contact | Netherlands |
| eM Client | software licence address | Czech Republic |
| Google Analytics | browsing data and IP address | United States |
| LM Studio (Element Labs) | the request submitted to a cloud AI model (section 6.1) | United States |
Before such a disclosure we assess the privacy factors required by law (s. 17): sensitivity of the information, purposes, safeguards offered, legal regime of the host country. We require contractual confidentiality and security commitments from these providers.
You should know that information disclosed this way may be accessible to the authorities of the country where it sits, under that country's laws. That is a consequence of the service, not a preference of ours — and it is one more reason to keep your email and your files here.
8. How long we keep it
| Information | Period | Why |
|---|---|---|
| Client account, email, files, sites | during the Service, then 90 days after the Service ends or the last connection, where there is no activity | retrieval and export |
| Support tickets | as long as the account exists; deleted with it at the end of the 90 days | technical history |
| Server backups | about 30 days on the primary site, up to 12 months on the secondary site | restoration and disaster recovery |
| Online backups | 12 months | restoration |
| Invoices and accounting records | 7 years | tax obligation |
| Server logs and metrics | 13 months | security and diagnosis |
| Cookies | at most 13 months | consent and operation |
| Incident register | at least 1 year after closure | legal obligation |
AI working sessions are not kept as a separate archive. A session lives in the project folder it belongs to and is destroyed with it, under the periods above. What is sent to a cloud model is not kept by the provider at all.
Two exceptions deserve to be said. A registered domain name outlives the closed account: the registrant's contact details remain at the registrar for as long as the domain exists, because that is how the registry works. And an invoice does not erase an account: accounting records stay 7 years, without the account's content.
At the end of the period, information is destroyed securely, or irreversibly anonymized if used for statistics.
9. Security
We apply reasonable safeguards proportionate to the sensitivity of the information:
- access limited to those who need it, with two-factor authentication;
- encryption in transit and, for sensitive elements, at rest;
- regular security updates and a server encryption policy;
- on-site and off-site backups, in Canada;
- integrity and access monitoring, with logging;
- a confidentiality undertaking from anyone who accesses the data;
- AI assistance follows section 6.1: local by default, cloud only for the part of the task that needs it, never credentials;
- secure destruction of equipment at end of life.
No system is invulnerable, and we will not pretend otherwise. What we commit to is doing what is reasonably possible, telling you when something happens, and fixing it.
10. Information we host for our clients
When a client stores personal information about its own customers, subscribers or patients on our servers:
- the client is the person responsible for that information under the Act;
- AdocSys acts as mandatary: we process it only on the client's instructions, to provide the Service, and never for our own purposes;
- we access it only for technical operation, requested support, security, or a legal obligation, and, where the task requires it, through an AI tool under the rules of section 6.1;
- we notify the client without delay of any incident affecting it, with the information needed for the client to meet its own obligations;
- at the end of the Service, we return the Content and destroy it under section 8.
11. Your rights
You may, at any time:
- access the personal information we hold about you;
- have it corrected if it is inaccurate, incomplete or ambiguous;
- request portability of the information you provided to us, in a structured and commonly used technological format;
- request de-indexing of information, or that its dissemination cease, in the cases provided by law;
- withdraw consent to a non-essential use;
- request deletion, subject to our retention obligations;
- complain to the Commission d'accès à l'information.
How: write to support@adocsys.net, or by post to the attention of the person responsible. State your request and provide proof of identity if we need it to avoid disclosing information to the wrong person.
Timeline: we answer in writing within 30 days of receipt, with written justification where the law allows an extension. If we refuse, we explain why and tell you how to challenge it before the Commission.
Cost: none for a reasonable request. Reproduction fees may apply to bulky copies, after notice.
12. Cookies and similar technologies
| Type | Use | Consent |
|---|---|---|
| Necessary | session, cart, authentication, security, language | not required (necessary to the service) |
| Analytics | Google Analytics — pages viewed, visit duration, referral source | required before placement |
| Advertising or social | no advertising cookies, no retargeting pixels | — |
We use Google Analytics to learn which pages serve and which do not. These cookies are not necessary for the site to work: they are placed only after you agree, and you may withdraw that agreement at any time. Their maximum duration is 13 months. Google is established in the United States; see section 7.
Details are in the Cookie Policy. Your browser lets you refuse or delete cookies; a refused necessary cookie may stop part of the site from working.
13. Electronic communications
We write to you for service communications (invoice, outage, change, incident): they are part of the contract and cannot be disabled while you are a client.
For commercial communications (news, offers, articles) we comply with Canada's Anti-Spam Legislation: consent, sender identification, postal address, and a working unsubscribe mechanism in every message. Unsubscribing takes effect within 10 business days and does not affect service communications.
14. Automated decisions
We make no decision based exclusively on automated processing that would have a significant effect on you. If that changes, we will tell you, and you will be able to ask for the decision to be reviewed by a person.
AI tools help us search, summarise, translate and draft. They do not decide. Any decision about your account, your service or your Content is made by a person who can explain it to you.
15. Minors
Our services are intended for adults and businesses. We do not knowingly collect personal information from minors under 14 without the consent of a parent or guardian. If you believe such information has been sent to us, write to us: we will delete it.
16. Governance and incidents
- A person responsible is designated and their contact details are published (section 1).
- We keep a register of confidentiality incidents — date, nature, persons affected, measures taken, notices given — retained at least one year after closure. Technical incidents (outage, loss of service) are recorded in support tickets; confidentiality incidents have their own register, kept by the person responsible.
- Where an incident presents a risk of serious injury, we notify the Commission d'accès à l'information and the persons concerned promptly, and we take measures to limit the harm and prevent recurrence.
- We carry out a privacy impact assessment before any project involving new information, a new system, a new AI tool, or a disclosure outside Canada.
- We apply privacy by default: the most protective settings apply without any action on your part.
17. Changes to this policy
We may amend this policy. Any significant change is announced on this page and, for clients, by email, at least 15 days before it takes effect. The update date and version number appear at the top. The previous version remains available on request.
18. Contact us
AdocSys · 657 route Marie-Victorin, Verchères, Quebec J0L2R0, Canada
Person responsible: Mathieu Peloquin · support@adocsys.net · 1 877 749-9579
Commission d'accès à l'information du Québec
cai.gouv.qc.ca · 1 888 528-7741 · Quebec City, Quebec
If you are not satisfied with our answer, you may complain to the Commission.