Data processing addendum
You decide. We process on your instructions, in writing. The processing commitments that form part of every Mercleo agreement: purpose limits, confidentiality, subprocessors, breach notice, assistance with rights requests, export and deletion.
Scope
Last updated: 12 November 2026.
This addendum forms part of the Terms of service between Mercleo Technologies Inc. ("Mercleo") and the customer organization ("Customer"). It applies whenever Mercleo processes personal information that Customer puts into the Services about Customer's own people: contacts, members, donors, attendees, applicants, employees and learners ("Customer Personal Information").
Roles
Customer decides why and how Customer Personal Information is collected and used, and is the organization accountable for it under PIPEDA, Quebec's private-sector privacy act, and any other law that applies to Customer. Mercleo processes it on Customer's documented instructions to provide the Services. Customer's instructions are the Terms, this addendum, and the settings Customer configures in the product.
For information Mercleo collects in its own right (account holders, billing contacts, website visitors) Mercleo is accountable directly, and the Privacy policy governs.
What Mercleo will do
- Process Customer Personal Information only to provide, secure and support the Services, and never for Mercleo's own marketing.
- Keep it confidential, and limit access to personnel who need it to do their job and are bound by confidentiality obligations.
- Protect it with safeguards appropriate to its sensitivity, as described at /trust/security, including encryption in transit and at rest and access logging for sensitive fields.
- Use only the subprocessors listed at /trust/subprocessors, flow down equivalent obligations to them, and update that page when the list changes. Customer may ask for email notice of changes and may object to a new subprocessor; if the objection cannot be resolved, Customer may cancel the affected Services and receive a refund of unused prepaid fees.
- Assist Customer in responding to access, correction and deletion requests from individuals, and pass to Customer any such request that reaches Mercleo directly.
- Notify Customer without unreasonable delay after confirming a breach of security safeguards affecting Customer Personal Information, with what Mercleo knows about its nature, the information involved, and the steps taken.
- Make an export of Customer Personal Information available on request during the term and for 30 days after termination, and delete it from live systems on a verified deletion request, within 30 days of that request, except copies Mercleo must retain by law. Copies in encrypted backups age out on the backup schedule.
- Answer reasonable written questions about these commitments so Customer can meet its own accountability obligations.
What Customer will do
- Have the consents, notices and legal bases its collection requires, including for tracking on its own websites and for messages it sends through the Services (see CASL in the Terms).
- Configure the product's consent, privacy-link and retention settings for its own obligations.
- Not put into the Services information the Services are not designed to hold, such as government identifiers or health information, except in fields marked sensitive.
AI features
- If Customer uses Mercleo's AI features, Mercleo processes the Customer Personal Information they read only to produce the answers, drafts and changes Customer's users ask for, through the model providers listed at /trust/subprocessors. Those providers process it under zero data retention: they do not keep prompts or outputs and do not use them to train models. Mercleo's AI gateway keeps request metadata, not content.
- Mercleo does not use Customer Personal Information to train or improve AI models, and one customer's information is never used in another customer's AI features.
- AI features act as the person who asks: they see only what that person can see in the Services. Anything that changes live data or reaches other people waits for approval by an authorized user in the product, and email is sent only through Customer's own review.
- An AI answer may name the people behind Customer's results (contacts, event attendees and email recipients) using their name and email address only, and only people the asking user can already see. This is Customer's choice: it is on by default, and Customer's owners and admins can turn it off in the product's AI settings, which stops every AI feature from naming them. A report a user saves to the Services' documents keeps the names as they were when it was saved, marked with that date.
- AI features never read employee or HR records (employee files, HR fields, documents, emergency contacts, offers, pay, reviews or time off), except that drafting an offer letter inside the HR module may read the HR records it needs once Customer's owners or admins turn that on in the product's AI settings.
- Customer can turn AI features off for its organization in the product's AI settings.
- If Customer uses Mail, Mercleo processes what Customer's shared inboxes receive and send: subjects, message text and formatting, attachments, the names and addresses in From, To, Cc, Bcc and Reply-To, selected headers, delivery and bounce events, and the notes, drafts and labels Customer's users add. Much of it concerns people outside Customer's organization. For this addendum all of it is Customer Personal Information and the Roles section applies: Customer decides what its inboxes are used for and is the organization accountable for what they hold, including any notice its own law requires it to give the people who write to it. Mercleo processes it only to receive, store, show, send and secure that mail, and for the AI features described below when Customer's users ask.
- Original messages, rendered HTML, composed HTML and attachments are encrypted by Mercleo before they reach file storage, using AES-256-GCM with a data key for each inbox (for attachments, a data key for the account). Those data keys are encrypted by a master key in AWS KMS that Mercleo manages; customer-managed keys are not offered. Subjects, message text, addresses, notes and drafts sit in a database separate from Mercleo's other products without that extra layer, so that they can be searched, and rely on the encryption at rest of the platform hosting it. A file being attached sits in a staging area of file storage without that layer until it is sealed; a daily job deletes any upload left unfinished for more than a day. Mail is not end-to-end encrypted: Mercleo's servers and Amazon SES handle messages in readable form in order to receive, show and send them.
- In the product, a thread can be read by the members of its inbox. Customer's owners and admins are not members by default: they manage the inbox, read its access log and can add people to its team, themselves included, but they open threads only as members. If an inbox manager, owner or admin turns on showing the inbox's mail on contact records, or a member shows one message there, anyone who can see that contact can read that message, read-only. That is off by default; otherwise they see only that an email was sent or received, when, and which inbox has it. A person removed from Customer's account loses inbox access, on notice from the platform with a daily check behind it.
- A link that opens a message or a file lasts 10 minutes or less and works for whoever holds it. For a file over 25 MB, a member can create a public link that lasts 7 days by default and 14 at most, stops after 100 downloads, can be revoked, and works for anyone who has it.
- Mercleo's staff console has no route into Mail, and of Mercleo's applications only the one that runs Mail holds its database and key credentials. Personnel with production access could reach them, under the confidentiality commitment above. The access log below does not record that kind of access.
- Reads in the product are logged for each inbox: opening a thread, downloading an attachment, searching, viewing a shared email from a contact record, and reads by AI features, along with changes to sharing and addresses and removal of the inbox. The log records who, what and when, and identifiers, never content or search terms. Inbox managers and Customer's owners and admins can read it. It outlasts the removal of an inbox and is deleted with the account.
- Mail has no automatic retention limit: a thread stays until a member deletes it. A deleted thread goes to Trash, and a daily job permanently deletes it 30 days later; a member can also delete it from Trash at once. Either way that removes its messages, notes, drafts, labels and stored copies, and any attachment nothing else uses.
- Customer's owners and admins can remove an inbox. That removes its threads, messages, notes, drafts, members, sent-message records, stored copies, data key and any attachment no other inbox uses. A row with no name or address stays as a marker, with the access log.
- On a verified deletion request for the account, Mercleo schedules a job that removes the account's inboxes, stored objects, keys and remaining Mail records, the access log included. The record of the landing object stays, stripped of recipients and verdicts, so that the object is not processed again.
- These copies outlast those deletions. A received message stays in its original form in an Amazon S3 landing bucket, encrypted with AWS KMS, until the bucket's lifecycle removes it after 7 days. A thread's deletion from Trash also removes the record of what was sent from it, including recipients, subject and text, apart from a record with none of those, kept for up to about two days so sending limits still count. Files a member uploaded to send, and the record of who a received message was delivered to, stay until the inbox or account is removed. A contact's timeline keeps the subject and date of an email to or from that contact, and an AI chat keeps what was said in it; neither is removed with the thread. Signature images are described below. Copies in encrypted backups age out on the backup schedule.
- Amazon SES checks received mail for spam and viruses, and Amazon GuardDuty scans it for malware. A message found to carry a virus or threat is quarantined: only its encrypted original is kept, on its own thread in Spam, with no text or HTML body to read. Mail marked as spam, or failing DMARC under a reject policy, goes to its own thread in Spam, where members can read it. Nothing is dropped for being spam, and Spam is not deleted on a timer. An attachment on received mail is stored only once the scan finds no threats. Files Customer's users upload are not scanned.
- Mail reaches a shared inbox by forwarding from an address Customer controls to a private Mercleo receiving address. Sending from that address requires Customer to verify its domain for Amazon SES. What Customer's own mail provider keeps, and what happens to a message once it reaches a recipient's servers, is outside this addendum.
- A signature image is hosted in a separate public storage bucket so that recipients can load it. Anyone with its address can view it. The address is random and names no account. Mercleo does not encrypt these images and does not use requests for them to track opens, and they are not removed when a signature, an inbox or the account is deleted, because mail already sent points at them. Pictures in the body of a message are never placed in that bucket.
AI features and Mail
- AI features read mail only when one of Customer's users asks: by asking Inglis, Mercleo's AI assistant, about a conversation they attach, or by asking it to draft a reply. They read only the inboxes that person is a member of. Being an owner or admin gives them nothing more.
- Reading is read-only. AI features cannot send, forward or reply to mail. A draft reply lands in the person's composer for them to review and send, with its recipients set by code from the thread, never by the model.
- What goes to the model provider is the subject, the sender's name and address, the To and Cc addresses, dates and plain text of the messages it reads, in bounded amounts stated at /trust/ai. Bcc recipients are not sent. Reply-To is not sent, and no AI feature uses one as a recipient. Attachment contents and HTML are not sent. Spam threads and quarantined messages are never read.
- The provider and zero-retention position in the AI features section above apply to these reads, and the same section's commitments on training and on one customer's information apply.
- Each thread read appears in the inbox's access log as read by Inglis for the person who asked. A search appears there as that person's search.
- What Inglis says about a message is saved in the asking person's chat, which only that person can open, and it is not removed when the thread or inbox is deleted. Deleting the chat removes it from view; its text is deleted with the account.
- Customer's settings do not include a switch for AI features reading mail, and the switch for naming people in answers does not cover it. An organization that needs this off should say so at legal@mercleo.com.
- A person who writes to a shared inbox from outside Customer's organization has no account with Mercleo and Mercleo does not contact them. An AI feature reading their message is processing on Customer's instructions under this addendum. Customer decides whether its users do this and is responsible for any notice its own law requires.
Where processing happens
Some subprocessors process data in the United States. The jurisdictional picture is stated at /trust/data-residency. Customer is responsible for any assessment its own law requires before transferring personal information outside its province or country, and Mercleo will supply the information needed for it.
Term and precedence
This addendum applies for as long as Mercleo holds Customer Personal Information. If it conflicts with the Terms on the handling of Customer Personal Information, this addendum governs. Organizations whose own obligations need different or additional terms should write to legal@mercleo.com before purchase.