Privacy policy
Version of November 22, 2026
Person in charge of the protection of personal information
David Grenier, the person in charge of the protection of personal information, ensures compliance with Québec's Law 25 for the Consultant Portal.
For any question or request, write to confidentialite@crmproqc.ca.
For the information your consultant holds about you, you can contact your consultant directly.
Information collected
For consultants: name, email, password (stored only in hashed form), preferences (language), Mary Kay rank chosen by her and, if she enters it, her business phone (encrypted), which appears on her promo posters (and on her public page if she has no text number), and, if she enters it, her city (for the name search).
To send promotions by text, the law requires the sender's contact information. A public page, not indexed by search engines, therefore shows the consultant's name, rank, sending number (or, if she has none, her business phone if entered), her public email if she enters one (never her sign-in email in its place), the links she chooses to show (store, social media, website), and the portal's mailing address, or her own business address if she chooses it.
For clients, entered by their consultant: first name, last name, contact details, birthday (year optional), skin type, occupation, Mary Kay rank (a consultant on her team), purchases, follow-ups, notes and consent to communications. Gender is optional.
When a consultant links a Square sale to a record, the portal keeps a fingerprint of the Square customer (never their identifier), to place their next sales on the same record; it is erased with the record.
Only when the consultant taps “Add to Square” on a client's or prospect's record, the portal sends that person's first name, last name, phone and email to her Square account; never their notes or purchases, never a referral.
To pay for her subscription, the consultant saves her card with Square's form: the card number, date and security code go straight to Square, never into the portal. The portal keeps only the card's brand, its last 4 digits, its expiry date and Square's references, to show them to her, as well as her payment history (amounts, periods, taxes, receipt numbers, declined payments and their dates).
The birthday is also used to send a text with wishes on the day, and a reminder on day 27 if the consultant has set an offer, only if the client consented to texts. The year is not used.
When a client and her consultant exchange text messages, the content of those messages is also kept, encrypted, so the conversation stays readable.
We only collect what is needed to follow up with clients.
For newsletters: the consultant's drafts and the images she adds, encrypted. These images are reduced, and their hidden details (where the photo was taken, device) are removed.
For each newsletter sent: an encrypted copy, the list of people it is for, and the result of each send. The portal tracks neither opens nor clicks.
If a consultant sends an idea, a problem or an incident through the portal: her encrypted message, the page she was on and her device (e.g. iPhone, Safari; never the IP address). No screenshot. The portal's administrator reads this message. The consultant or the administrator can delete it.
If a consultant adds a product that isn't in the catalogue to her inventory, the person who administers the portal sees her name and the product's name, to add it to the catalogue. This product is visible to that consultant only until it is added to the catalogue, and it is deleted with her account.
At each successful login, the portal records the country code in the access log, as reported by the portal's protection service, to spot an unusual login.
If an email invitation includes the "I'll be there" button and the person taps it, the portal records their attendance for that event in the advisor's list and on their record. The portal does not track opens or other clicks.
If a consultant connects her Square account, the portal reads her sales and appointments and, to find the right contact, the name, phone number and email recorded in Square. The portal writes to Square only when the consultant asks: “Add to Square” on a record (see below), and “Update my Square”, which sends her products (name, SKU, price, category), never a client. To compare, the portal also reads her Square catalogue. It also keeps the name of her Square business (or main location), to show her which account is connected; it is deleted when she disconnects.
Only for people who already have a contact, and when the consultant chooses it ("Add the history"), the portal also takes their Square sales and appointments from before connecting, then those of a contact linked to a Square customer later. A sale it cannot match with certainty is not added: only its date, amount and contact are kept, in a separate list erased with the contact or on disconnecting.
Why
This information is used so each advisor can serve her clients: purchase history, follow-up reminders and communications the client has consented to. If the advisor chooses, some of her numbers are also used to help her, by the person who recruited her.
Protection
The addresses suggested while typing come from a service installed on our own servers, using OpenStreetMap data: what is typed is not sent to anyone else.
Each consultant only sees her own clients. Contact details, birth dates and notes are encrypted in the database, except city and province, kept readable to sort records by location. Signing in requires a second factor. Access is recorded in a log.
A consultant can sign in with a passkey (Face ID, Touch ID, Windows Hello or fingerprint). Their face and fingerprint never leave their device: the portal only keeps the public part of the key, the device name and the dates it was added and last used. Every added or removed passkey triggers an email notice.
The portal administrator sees each consultant's account (name, email, status, AI follow-up, plan, features turned on, whether two-factor authentication and a passkey are turned on, whether her texting number is connected and with which provider, and numbers for the month: her AI spending and the number of AI-written messages, the newsletter emails she sent and the number of newsletters) to approve sign-ups, manage access and the monthly limits, and a security log of her activity: the time, the type of action, a record number and the login country. They never see a consultant's clients, purchases or messages: the database forbids it. The only exception: what a consultant sends them herself with the "An idea or a problem?" button, where she's asked not to name clients.
An advisor can invite the person she recruited. By accepting, that person joins her team: the whole team (the person who recruited her, the person who recruited that one, and so on) sees her name, her rank and who recruited her. Her numbers are shared only with the person who recruited her directly, and only what she chooses in My account, two boxes unchecked at first: her monthly goal and its bar; her sales for the month, compared with the same days last month, and the details of the products sold (product, quantity, amount). Never a client, a client's name or a message. She can uncheck these boxes or withdraw her agreement at any time, with immediate effect. Only one person recruited her at a time: accepting another invitation replaces the old link. To invite her to her team or her office space without knowing her email, an advisor can search for another advisor by name (at least 3 letters, 10 results at most): she sees her name, her rank, her city if she entered it and the name of the person who recruited her, never her email or her number. Each advisor can choose, in My account, not to appear in this search. The invited person must always accept; if the person who recruited her removes her from the team, nothing is shared anymore and she is told in My account.
A consultant can set a monthly sales goal. It is private, unless she checks “Share my goal” for the person who recruited her directly; it goes with her account.
A consultant can enter her links (her online store, Facebook, Instagram, TikTok, YouTube, Pinterest, her website): her public page shows them under “Find me online”. Each link leads to the site only when tapped; our page loads nothing from these sites and tracks no one.
When a consultant adds an appointment, the portal number (used only for these notices) may text the person the consultant's name, the date, time and place, with a link for that appointment only, then, 24 hours before, a request to confirm by a deadline (and a reminder 2 hours before for an appointment at 11 AM or later, if unanswered). They reply YES or NO, or tap the link; with no answer by the deadline (1 hour before, or 3 hours before for an appointment before 11 AM), the appointment may be cancelled, and they are told. These notices contain no promotion; STOP to that number ends them, without affecting their other exchanges. A fingerprint of their number is used to find their appointments when they reply. They are kept like other texts.
My office space: the person who has premises can invite other consultants to book its offices or rooms. By accepting, each member knows that their name and the number in My account will be seen by the other members of this space, with their bookings (the space, the day, the time). No client appears there. Bookings stay in the space: they do not go into their agenda or their Google or Outlook calendar. An ended or declined link is deleted after 30 days, a past booking after 13 months, and everything goes with the account or with the space.
Posters (Top 10, Star consultant, promotion) are made in the browser: photos and names are never sent to the portal. The poster in progress is kept only on the consultant's device, to find it again after an export or a page reload. It is erased when she signs out, with “Start over”, or after 14 days without changes (the next time the portal is opened on that device). Another consultant who signs in on the same device never sees it: it is erased then.
Calendar and Google and Outlook calendars
Appointments are kept in the portal; their title, location and notes are encrypted. Sophie, the virtual assistant, only knows the day and time of the next appointment of the client who is texting; she cannot create, move or cancel an appointment.
A consultant may connect her Google calendar, her Outlook calendar, or both. Her appointments are copied into a "Portal – Appointments" calendar created by the portal in the one she chooses as main; the other is only used to read her busy times. By default, only the appointment type (or "Mary Kay appointment") and the client's first name appear there: never her phone, address or notes. The consultant may choose to send full details; that information is then also kept by Google or Microsoft, under their own rules.
From the personal calendars, the portal only keeps busy times and their source (Google or Outlook), without titles or details. Access tokens are encrypted. "Disconnect" tries to remove the "Portal – Appointments" calendar if there is one and to revoke access (Google), then erases the tokens.
The read-only subscription uses a secret address the consultant can renew or stop at any time; it shows the same details, minimal by default.
Google data: only if the consultant connects her Google calendar, the portal asks her for three limited permissions. 1) Create the "Portal – Appointments" calendar in her account, and see, create, edit and delete the events of that calendar only: this permission shows no other calendar and no other event. 2) Read the busy times (start and end only, without title or details) of the calendars she chooses. 3) Read the list of her calendars (their names only, never their events), so she can choose which ones count as busy; those names are not kept, only the technical identifier of each chosen calendar (for another person's calendar, it is often that person's email address).
In the "Portal – Appointments" calendar, the portal reads the events of the last 30 days and the next 18 months: the date, time and length of each appointment and, with full details, the location and notes changed in Google, which come back into the portal. An event she creates herself in that calendar becomes a portal appointment, without a client: its title, location and description are read and kept, encrypted.
This Google data is used only to run the calendar: copying her appointments into her calendar; bringing back into the portal an appointment moved, changed or deleted in Google, or an event she creates there; showing her when she is already busy, to avoid two appointments at the same time; and choosing the free slots offered when an appointment is rescheduled. An appointment changed in Google then follows the same path as if it had been changed in the portal: if the client receives confirmation texts, a text tells her the new time (and the location, with full details), sent through Telnyx or Twilio; Sophie, the virtual assistant (Anthropic), knows the day and time of the next appointment of the client who is texting. Busy times and the list of calendars are not sent to anyone. Google data is never sold, never used for advertising and never used to train artificial intelligence. No one reads it, unless the consultant asks for help with a problem, for security, or when the law requires it.
Retention and deletion: busy times cover the previous day and the next 60 days, and are replaced at every check (about every 10 minutes). The "Disconnect" button on the Calendars page, or deleting the account, immediately erases on our side the tokens, the busy times and the chosen calendars, and the portal tries to remove the "Portal – Appointments" calendar from her Google account and to revoke its access. If it does not succeed (Google does not answer, or access has already expired), she can delete that calendar herself in Google Calendar and remove access at https://myaccount.google.com/permissions. She can also remove access there at any time: the portal can then no longer read anything, but the "Portal – Appointments" calendar stays in Google Calendar, where she can delete it, and the tokens, now useless, stay encrypted on our side until she taps "Disconnect" or deletes her account. Appointments, including those that came from Google, stay in the portal, where she can delete them. Encrypted backups are cleared in about five weeks.
Portail Conseilleres's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements. Portail Conseilleres is the name of the application registered with Google.
Referrals given by QR code (collection)
During a get-together, a consultant can show a QR code. A guest who scans it with their phone sees the list of attendees chosen by the consultant (first and last name only), taps their name, then gives the first name, last name (optional) and number of people who would be fine with the consultant calling them. A guest who is not on the list gives their first name, last name and number. They see nothing else.
This information is encrypted and is used only by that consultant: to know who gave which referral, and to call those people personally. If the number of a guest who is not on the list is not already in the consultant's contacts, a contact record is added with what the guest gave, as a prospect. No automatic text message or email is ever sent to a referral, or to these guests. Someone who does not want to be called can tell the consultant, who archives or deletes their record.
The QR code and the list of names stop working at the end of the collection, or earlier if the consultant closes it.
Forms
A consultant can create a form (for example for a party, an event or a satisfaction survey) and send it through a personal link, by text or email, to people in her contacts who gave their consent, or through a public link she chooses to post. Before sending their answers, the person checks a consent statement that says what they are used for, who sees them and when they will be deleted.
The answers (and the name, if asked) are encrypted. Only the consultant who created the form can see them: not the portal administrator, not Mary Kay, not another consultant. They are used only for that form. A sensitive question, such as an allergy for a meal, is allowed, with the same protections. If the form is anonymous, no name or link to a contact record is kept, and only the day of the answer (not the time).
For a public link, a short robot check runs in the browser, without any outside service. A cookie holding a random number, and a fingerprint of the IP address (never the address itself), are used only to limit the number of answers per device.
Answers are deleted automatically 30 days after the form's end date. The consultant is warned 7 days before and can download them. A person can ask the consultant to remove their answer at any time.
Service providers and information that leaves Québec
To run the portal, some information goes through service providers, some of them outside Québec.
Anthropic (United States): the artificial intelligence behind the assistant Sophie, follow-up texts, and writing help for promos and newsletters. The text is sent with the names in the advisor's address book, numbers, emails and addresses masked or removed.
Telnyx or Twilio (United States), depending on the consultant's account: sending and receiving text messages, so the phone number and the content of the messages.
Square (United States, Canada), if the consultant connects her account: the portal reads her sales, appointments and catalogue. Square receives the read requests, her products when she taps “Update my Square”, and, only when she taps “Add to Square”, that person's first name, last name, phone and email.
Square (United States, Canada), for consultants' subscriptions: the portal sends the consultant's name and email to the portal's Square account, where her card is saved through Square's form (the portal never sees it); subscription payments are made there. The portal emails the receipts itself. The bank's strong verification (3-D Secure) may show a page from the card's bank.
To warn the advisor when her balance drops, the portal reads the balance of her Telnyx or Twilio account with her keys, once a day. The amount is never kept. The administrator only sees her name and that the balance is low.
Amazon Web Services (Montréal region): sending emails, so the address and the content of the email.
Cloudflare: secure routing of traffic to the portal.
Have I Been Pwned: refusing a password that has already been stolen. Only five characters of a fingerprint are sent, never the password.
Apple, Google, Mozilla or Microsoft, depending on the device: delivering the advisor's notifications to her phone. The text is general, never a client's name or a message's content.
For Google and Microsoft, see the section on calendars.
How long we keep information
Text messages exchanged with a client are deleted automatically after 3 years without any exchange. An automatic text (birthday, promotion, reminder) does not count as an exchange, and it is also deleted after 3 years.
The date of a birthday text already sent, kept so it is never sent twice, is deleted after 40 days. The list of people for a promotion is deleted after 3 years.
Collection guests who were not on the list and are never linked to a record, and duplicate referrals, are deleted 90 days after the collection. The name and number typed by a guest are also deleted after that time, even if they were linked to a record. Any record that has never had any activity (no call, note, purchase, message or change) is automatically deleted after 12 months. The consultant is warned 30 days before, with the list and a button to keep them. A person can also ask the consultant at any time to correct or delete their information.
When a consultant deletes a client's record, all of that client's information is deleted from the portal at the same time, text messages included. A copy added to her Square account (“Add to Square”) stays in Square: the consultant deletes it herself in Square; the portal reminds her.
A consultant's frozen inventories (her January 1 and December 31 inventory, for taxes: product names, prices and quantities, never anything about a customer) are kept as long as her account exists; when the account is deleted, they are first emailed to her (to her sign-in address), then deleted with it.
When a consultant deletes her account, her card is disabled and her customer record is deleted at Square, and her payment history is deleted from the portal, except her receipts: they are kept apart (her name, her email, the period, the amounts, the taxes, the card brand and last 4 digits, the payment reference at Square), for tax law, then deleted automatically 6 years after the end of the year of payment. Only the person who administers the portal can read them. The history of payments already made also stays at Square, for accounting.
The access log (who viewed or changed what, without the content) is deleted after 1 year. A consultant account that was never activated (a request never processed, an invitation never accepted) is deleted after 30 days.
Two exceptions, to respect a request even if a record is deleted and recreated: someone who asked to stop receiving texts, and an email address that bounced or complained. We then keep only an encrypted fingerprint of the number or address (not the number or address itself), with the date and the reason, never the name. A number's fingerprint is removed if they reply START or give their consent again; otherwise, it is kept as long as the consultant's account exists. An email address's fingerprint is kept with no time limit, because that list protects the whole portal.
As long as the record exists, we keep only the record of consents and refusals (STOP replies), without the content of the messages, as proof required by law.
Technical records of emails sent (type, date, result, without the content) are deleted after 13 months. Encrypted backups are replaced day after day: deleted information also disappears from the backups within about five weeks.
A newsletter draft not picked up again for a year is deleted, as is an image more than a year old that no draft uses. The consultant can delete them sooner.
A sent newsletter, its copy and its list are deleted after 3 years. The record of a send (without the address or content) is deleted after 13 months.
An idea or a problem is deleted 2 years after it's closed, or 3 years after it's sent if it was never closed; an incident, after 5 years.
Security alerts are deleted after 1 year. The privacy incident register is kept at least 5 years, as the law requires.
The "recruited by" link is deleted 30 days after a refusal or the end of the agreement, an unanswered invitation after 60 days, and both with either account. The numbers aren't kept: they're calculated at each reading.
A device registered for notifications is deleted after 1 year without a notification, when it unsubscribes, or with the account.
A buyer's name, phone number and email received from Square, if they do not lead to a single contact, stay encrypted while the consultant chooses: they are erased as soon as the sale is settled, and after 90 days at most.
A Square appointment that leads to no contact keeps the person's name, encrypted: it is erased from the portal 90 days after its date. If the person asks, the consultant can erase it right away ("This person asks to have their information erased", in the appointment window). It then stays in Square, where the consultant erases it directly.
Your rights
You can request access to your information, its correction or its deletion. A consultant can delete her own account and all her data from the "My account" page; only her subscription receipts are kept for 6 years, for tax law (see "How long we keep information").
You can also ask to receive the computerized information you provided, in a structured, commonly used technological format, or to have it sent to the person or organization you designate (right to data portability).
You can withdraw your consent to a use of your information at any time: for example, reply STOP to stop receiving texts, or use the unsubscribe link in a newsletter. A consultant can also disconnect her calendars, change what she shares with her team or delete her account.
We answer a request for access, correction, deletion or portability in writing within 30 days of receiving it. Requests go to the person in charge of the protection of personal information (see above).
If you are not satisfied with our answer, or if you have not received an answer within that time, you can turn to the Commission d'accès à l'information du Québec (https://www.cai.gouv.qc.ca).
Privacy incidents
In the event of an incident, the person in charge assesses the risk, notifies the affected people and the Commission d'accès à l'information when required by law, and records the incident in a register.