Terms of Use — Seal LIFAIO
Version : 2026-09-22b — © Technologies Marco Prive · Head office : 2200-1250 Rene-Levesque Ouest, Montreal, Quebec, Canada H3B 4W8 · Telephone : +1-263-999-2751 · info@lifaio.com
Renewal stops. Service continues until the end of the period already paid for, and your account and all your data stay in place. You can resume in one click before that date.
No reason is asked for and no justification is required.
Seal LIFAIO only confirms that a presented code matches an ACTIVE employee of an organization whose displayed proofs were verified, at the time of verification. Seal never vouches for a person's full identity, competence, honesty or quality of work, and is neither a certification, a guarantee, nor a government approval.
A "not confirmed" result NEVER means someone is a fraudster: the organization may not be registered, the code may have expired (they change every minute) or been mistyped. When in doubt, call the organization's official number; in an emergency, call your local emergency number (911, 112…).
The organization agrees to: (a) provide accurate, up-to-date information; (b) IMMEDIATELY revoke any employee who leaves or whose link is compromised — this responsibility is its own and revocation takes effect instantly; (c) reserve seals for its real employees (no lending or sharing); (d) keep professional licenses valid where applicable; (e) never use the service for illegal or deceptive purposes.
Legal-existence checks are performed by specialized providers and public registries; the representative's identity is verified by Didit; control of public channels (phone, domain) is checked by Seal. The public page shows the exact state of each proof. A discrepancy triggers review, never an accusation. The service is provided on an assumed BEST-EFFORT basis.
Company verification fee: US$35, one-time, due with the first payment, non-refundable once the verification has been performed (refunded if it fails through our fault). Per-seat subscription per the public grid (cumulative brackets), monthly or annual, payable via Stripe (merchant of record — it collects and remits applicable taxes). Cancellation takes effect at the end of the paid period. See the Refund policy. Seal Email: the subscription includes a monthly quota of email verification codes by headcount band, as per the published grid. Beyond the quota, blocks of 10,000 codes are sold at the published price, paid once via Stripe, with no expiry, and non-refundable from the first code used. The delegated issuing key is reserved to paid and verified files of 501 employees and more. Verification receipt: where the organisation requests it for a code, the person verifying alone decides whether to notify the organisation; Seal then transmits the code's fingerprint, the event and the time — never a name or address — and keeps these events for 30 days. A receipt attests neither reading, nor understanding, nor consent.
Seal may suspend an organization for: expired verification, lapsed professional license, false declaration, payment default, or use contrary to these terms. Suspension takes immediate effect on the public page and on code validation.
To the extent permitted by law, the total liability of Technologies Marco Prive is limited to the amounts paid by the organization in the preceding twelve (12) months. Seal is not an emergency service and does not replace police forces or the Canadian Anti-Fraud Centre.
The "Impersonation protection" service is an aid to protecting one's identity. It is not a guarantee against fraud, identity theft or impersonation, does not replace any security measure of a financial or other institution, and assures no outcome. Each institution remains solely responsible for its own identification procedures and free to decline any verification through Seal Lifaio. The subscriber remains responsible for safeguarding their device, password and two-factor authentication, and for rotating their key upon compromise. Technologies Marco Prive disclaims all liability for any damage resulting from fraud or impersonation, including where the service was active at the time, to the maximum extent permitted by applicable law — subject to consumer-protection rights that cannot be waived.
The "Get paid for remote orders" feature is a FACILITATION TOOL: it lets the organization generate, on its own connected Stripe account, payment links intended for its customers. The payment relationship is established EXCLUSIVELY between the organization (merchant of record for the transaction), Stripe and the buyer. Technologies Marco Prive is party to no transaction, never receives, holds or transfers any funds, never has access to card numbers, and collects no transaction fees. Stripe processing fees, refunds, chargebacks and all disputes (including delivery, quality or service disputes) rest exclusively with the organization and its Stripe account, under Stripe's terms. 3-D Secure authentication is implemented by Stripe and the buyer's bank; any resulting liability shift is governed by card-network rules and is neither controlled nor guaranteed by Technologies Marco Prive. A refund triggered from the portal is executed by Stripe on the organization's account, in its name and on its instruction. Technologies Marco Prive disclaims all liability relating to transactions, to the maximum extent permitted by applicable law.
Stripe offers only two authorization scopes: read-only or read-and-write. Because opening a payment session on the organization's account requires write access, the authorization granted through OAuth is read-and-write. Technologies Marco Prive undertakes to use that authorization solely to open ticket payment sessions and read their state; to create no customer, product, invoice or subscription; to move no funds; and to collect no commission on the transaction. Every call appears in the organization's own API logs, and the organization may revoke the authorization at any time and without notice, from its own Stripe dashboard.
The service, its source code, mechanism, algorithms, keys, pages, texts, look and feel, and the LIFAIO™ brand are the exclusive property of Technologies Marco Prive, protected by copyright, trademark law and trade secret. Registration grants only a personal, limited, non-exclusive, non-transferable and revocable right of access, for the intended use of the service. Except to the strict extent expressly permitted by mandatory, non-waivable law, it is prohibited to: (a) decompile, disassemble or reverse engineer the service, or attempt to reconstruct its mechanism, keys, algorithms or code by any means; (b) probe, bypass or test its security measures; (c) mass-extract data, scrape the service, or access it through bots or automated means other than the intended interfaces; (d) develop, train or feed a competing product or service from the service or its data; (e) resell, sublicense, rent or share access; (f) remove, hide or alter proprietary notices. Any breach results in immediate account termination, without refund, and may give rise to any remedy in damages and injunction.
Site protection is sold PER DOMAIN, as an ANNUAL SUBSCRIPTION at the price displayed for the declared workforce band. Like all Seal LIFAIO subscriptions, it renews AUTOMATICALLY at each term (via Stripe) and can be CANCELLED AT ANY TIME from your portal, « Subscription » section — access then continues until the end of the period already paid. If the subscription ends, the badge visibly switches to its “expired” state and the authenticity code is no longer served for that domain. Protection applies only to domains whose control has been proven (anchored domain or DNS record). DISCLAIMER: the badge and the authenticity code are AIDS to detecting impersonating websites — they NEVER constitute a guarantee that no fake site exists or will deceive anyone; their effectiveness depends on the verification act performed by the visitor themselves (typing the domain from their own address bar and comparing the codes). Technologies Marco Prive is not liable for fraud committed by third parties, for losses caused by an impersonating site, or for interruptions of third-party DNS, hosting or payment services. Article 6 (limitation of liability) applies in full.
The Vault encrypts the customer's data with a key split into TWO SHARES: one share held by the customer, one share derived by Seal at the moment of an authorized opening. Neither Seal nor the customer can decrypt alone. Seal never holds the customer's share, never receives it, and can neither reconstruct, restore nor bypass it.
Safekeeping of its share is the customer's SOLE responsibility. Loss of the customer's share — or simultaneous loss of both shares — renders the encrypted data DEFINITIVELY AND IRREVERSIBLY UNREADABLE: no recovery is possible, by Technologies Marco Prive or by anyone. Revoking a vault or ending the subscription alters no already-encrypted data, but bars any later opening by the service.
NO GUARANTEE against a persistently installed attacker: during an authorized operation the reconstituted key necessarily exists in memory on the customer's system, and an attacker with persistent privileged access there can observe it. The Vault narrows the exposure window and makes every opening traceable; it does not make an already-compromised system invulnerable. Article 6 (limitation of liability) applies in full.
The media seal binds the perceptual fingerprint of a work — image AND sound of the same interval, sealed together — to a verified entity, at an instant, under the authorisation of a second person or, for a natural person, of a second device. Sealing is sold by annual subscription; VERIFICATION is free, unlimited and account-free, for ever, and is billed to no one.
WHAT THE SEAL DOES NOT ESTABLISH: it confirms WHO published and that NOTHING has been altered since sealing. It NEVER states that what is asserted in the work is true, accurate or lawful. A sealed lie remains a lie, correctly attributed.
ACCEPTED TECHNICAL LIMITS: platform re-encoding is absorbed, but an alteration both very small and very brief may remain below the decision threshold; on a highly repetitive work an excerpt may match several positions and the first is reported; platforms protected by digital rights management allow no browser to read their stream, so a work cannot be verified there as broadcast, only from the file held or a copy in circulation. Article 6 (limitation of liability) applies in full.
SCREEN OR CAMERA CAPTURE: these channels serve to IDENTIFY the work and the entity answering for it. They return NO integrity verdict, the noise of these channels exceeding the signature of a localised alteration. Knowing whether a given copy was altered requires the file or the address. Nothing captured leaves the verifier's device: only the fingerprint is transmitted.
PROOF OF CHANNEL CONTROL: identity verification does not establish that an entity controls the channel it declares. A place of publication whose control has not been proven is REFUSED at sealing. A channel proven by one entity cannot be claimed by another.
PUBLIC ANCHORING: the sealings of a closed day are summarised into one fingerprint recorded in a public blockchain, which makes the DATE verifiable without trusting us. IT PROVES WHO SEALED FIRST — NEVER WHO CREATED FIRST. Technologies Marco Prive warrants neither the availability nor the permanence of third-party timestamping services.
BADGE: it is served by Seal, which reads the host transmitted by the browser and compares it with the declared places. No visitor data is read or retained: the host, and nothing else.
DECLARATION BY THE SEALING ENTITY: by sealing, the entity declares that it holds the necessary rights in the work and controls the places it declares. It remains solely responsible and indemnifies Technologies Marco Prive against any third-party claim arising from them. Activation and account-setup fees cover verifications already performed and are not refundable.
This article applies to you only if you have declared an erasure perimeter. It concerns neither citizens verifying a code nor ticketing.
7.1 — What Seal receives, and what it does not. Seal never receives a name, an email address, a postal address or any other identifying information. It receives an opaque internal reference that YOU choose yourself (for example "CLI-4471") and it returns a cryptographic contribution. Seal does not host your data, does not index it, does not receive it and has no technical means of reading it. You undertake never to send Seal a reference containing identifying information: a reference of the form "jean.tremblay@example.com" would be your breach, not ours.
7.2 — Characterisation, and what applies either way. Our position is that Seal does not act as a processor in respect of your personal data under this service, because it processes none: an opaque reference, with no means reasonably likely to be used to trace it back to a person, is not personal data in our hands. But that characterisation is not ours to settle. Should a competent authority or court find that Seal nevertheless acts as a processor in respect of any processing connected with this service, the following undertakings apply of right, without any need to amend this agreement: Seal acts only on your documented instructions; Seal processes nothing for its own purposes; Seal maintains confidentiality and appropriate technical measures; Seal assists you in handling data subject requests; Seal engages no sub-processor for this service without informing you; and at the end of the service Seal destroys what it holds (which contains no personal data). This clause exists so that no uncertainty of characterisation leaves you without a compliant contract.
7.3 — You remain the sole controller. You determine the purposes and the means: which tables, which fields, which people, at what time, and on what legal basis. Seal exercises no choice on your behalf and never rules on the merits of an erasure request you receive.
7.4 — WHAT THE ATTESTATION RECORDS, AND WHAT IT DOES NOT CHARACTERISE. The attestation records a technical fact: the key material specific to one person, within the perimeter you declared and signed, has been irreversibly destroyed. It does not characterise that fact in law. In particular, Seal does not warrant, and you acknowledge that Seal does not warrant:
(a) that destroying that key material constitutes erasure within the meaning of Article 17 of Regulation (EU) 2016/679, Article 17 of the UK GDPR, section 23 of the Quebec Act respecting the protection of personal information in the private sector (CQLR c. P-39.1) or any equivalent provision;
(b) that your records thereby become anonymous data. We expressly draw to your attention that the European Data Protection Board, in its Guidelines 01/2025 on pseudonymisation, takes the view that pseudonymised data becomes anonymous only if the conditions for anonymity are otherwise met, including where the data and the additional information are in different hands; and that section 23 of the Quebec Act requires irreversibility assessed at all times;
(c) that any supervisory authority, court or data subject will accept this mechanism as satisfying a legal erasure obligation. As at the date hereof, no European, UK or Canadian supervisory authority has, to our knowledge, either accepted or rejected key destruction as constituting legal erasure. The question is open, and we tell you so rather than let you find out.
It is for you to assess, with your own legal adviser where needed, whether this mechanism meets your obligations in each territory where you operate. Seal gives you a verifiable fact; the legal characterisation of that fact is yours.
7.5 — The attestation covers only the perimeter YOU declared. You name the tables and the fields. Seal attests destruction within that signed perimeter, and nothing else. Identifying information left outside the perimeter — in a free-text note, an attachment, an email, an application log, a data warehouse, a third-party system — is not covered and stays readable. The completeness of the perimeter is entirely yours, and Seal has no means of checking it, since it does not see your data.
7.6 — What the attestation does not prove. It does not establish that no copy was taken before the destruction, which no method can establish. You undertake never to present it to a data subject, an authority or a court as proof that no copy exists anywhere. That limit is written on the attestation itself, and it will stay there.
7.7 — The operation is irreversible, and Seal cannot undo it. Once the key material is destroyed, neither you, nor Seal, nor both together can restore readability. No request, no court order and no payment changes this: it is not a commercial policy, it is a technical incapacity. Seal bears no liability for an erasure you requested that executed as requested, including if it turns out you requested it in error, on the wrong reference, or without being required to.
7.8 — Your half of the key is your responsibility. It never leaves your systems; Seal does not hold it, has never seen it, and cannot give it back to you. Losing it makes your own exports unreadable, including for people who were never the subject of an erasure request. Seal is liable neither for that loss, nor for its consequences, nor for its disclosure by you or by one of your providers.
7.9 — YOUR STATUTORY RETENTION OBLIGATIONS REMAIN YOURS, AND THEY MAY PROHIBIT ERASURE. Several laws require you to keep documents, and those obligations prevail over an erasure request:
• Canada — section 230 of the Income Tax Act requires records and books of account to be kept for six years from the end of the last taxation year to which they relate; section 286 of the Excise Tax Act imposes an equivalent duty for GST/HST. The Canada Revenue Agency further requires written permission for any early destruction.
• European Union — Article 244 of Directive 2006/112/EC requires invoices issued and received to be stored, and Article 247 leaves each Member State to set the period (commonly six to ten years). Particular attention: Article 247(2) and (3) allow a Member State to require that the authenticity, integrity and legibility of stored invoices be ensured throughout the retention period. Rendering fields of an invoice unreadable inside that period is in direct tension with that requirement.
• GDPR and UK GDPR — Article 17(3) sets aside the right to erasure where processing is necessary for compliance with a legal obligation (17(3)(b)) or for the establishment, exercise or defence of legal claims (17(3)(e)).
• Quebec — section 23 of the private sector Act expressly subordinates destruction to any preservation period provided for by an Act.
What this means concretely for your perimeter. Identifying fields carried by documents under a mandatory retention duty — invoices, accounting records, employment files — must either be excluded from your perimeter or made subject to a deferred destruction at the date your obligation expires. You determine that date and that obligation; Seal does not know them, does not compute them and does not warn you. An erasure carried out in disregard of a retention obligation is your breach, and Seal does not answer for it.
7.10 — Unauthorised access detection. Seal counts requests aimed at envelopes that correspond to nobody. It reports a number and an hour to you, never an identity: Seal counts, Seal does not know who. That count is an indication and not judicial evidence, and Seal makes no finding as to anyone's identity or intent.
7.11 — Limitation specific to this article. Save to the extent applicable law does not permit its exclusion, Seal's total liability in respect of the attested erasure service is limited to the amounts you actually paid for that service in the twelve months preceding the triggering event. Seal is in no case liable for administrative fines, penalties or awards made against you by a supervisory authority or a court, those decisions bearing on your processing of your data and on your legal characterisation, of which you alone are master.
The French version of this article governs.
Article added on 16 September 2026. The legal references cited here were verified on that date; they are given so you can read them yourself, not as legal advice.
8.1 — What the verification fee is. Before your organisation can produce anything a third party can read — a badge, a verifiable code, an erasure attestation — it must be verified. That verification is charged once only: $35 for a business, $10 for an artist or an individual. This is not a subscription, it is never renewed, and no recurring charge is attached to it.
8.2 — The fee pays for the verification, not for its outcome. Verification is work: registry lookups, identity checking of the representative, domain and number checks. That work is carried out whether verification succeeds or not. If it does not succeed, the fee is not refunded — and this sentence is shown to you before payment, not after. Seal does not sell an outcome; Seal sells an honest examination.
8.3 — Express request and waiver (European Union and United Kingdom). Before payment, a checkbox — never pre-ticked, never optional — has you expressly request that verification begin immediately and acknowledge that once it has been fully performed you lose your right of withdrawal. Both elements are required by Article 16(a) and Article 8(8) of Directive 2011/83/EU, and by regulations 36(1) and 36(2) of the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013 in the United Kingdom. Without that checkbox you would bear no cost at all: Article 14(4)(a) of the Directive, and regulation 36(6). The date, the language and the exact text you accepted are retained.
8.4 — Quebec and Canada. The information required by section 54.4 of the Consumer Protection Act (CQLR, c. P-40.1) — including, at paragraph (k), cancellation and refund conditions — is disclosed to you before the contract is concluded, on the payment screen itself. The seven-day right to rescind under section 54.8 arises where the merchant has failed those obligations; Seal meets them, which is why this prior disclosure is your real protection rather than a formality.
8.5 — United States. No federal cooling-off period applies to this fee: 16 CFR Part 429 covers sales made at the buyer's home or away from the seller's place of business, not a service taken out online. This one-time fee is not a negative option and therefore falls under neither the Restore Online Shoppers' Confidence Act (15 U.S.C. § 8403) nor the FTC's automatic-renewal regime — that regime concerns recurring charges, and there are none here. The disclosures above are made clearly and conspicuously in accordance with Section 5 of the FTC Act.
8.6 — Demo mode is a privilege. After a successful verification, full access to every module is opened to you for ten days. One fourteen-day extension is offered in self-service, once only; beyond that, write to support@lifaio.com. Demo mode is a temporary unpaid service, granted at the discretion of Technologies Marco Prive, which may withdraw it at any time and without notice. It creates no acquired right, no legitimate expectation of renewal and no obligation of continuity.
8.7 — No automatic charge at the end of the trial. When the trial ends, nothing is triggered: your account becomes read-only and you decide whether to subscribe. Seal keeps no payment mandate arising from the trial. This clause concerns the trial only. A paid subscription does renew automatically at each term — monthly or annual, whichever you chose — and can be cancelled at any time from your portal, "Subscription" section, access remaining until the end of the period already paid for (articles 4 and 6.3).
8.8 — What "read-only" means, and what survives. The end of a trial, its withdrawal, or a failure to pay suspend the issuance of new items, and nothing else. Three things are never affected by a billing matter: (a) an erasure attestation already issued remains verifiable forever — the person concerned has nothing to do with your billing; (b) no badge and no public page will ever display a negative or misleading state on account of non-payment; (c) no subject seed is ever destroyed for non-payment — Seal holds one half of a key, and destroying it would make your enveloped files unreadable forever. Seal will not do that.
8.9 — Caps during the trial. Demo mode is for evaluating the product, not for running it in production: the number of actors, events, sealed media, erasures and fingerprint deposits is capped. Those caps are shown at all times on the demo-mode screen and disappear entirely upon subscription.
8.10 — This fee is never charged twice, and verification is not done again. Once the verification fee has been paid, it is acquired for good: if you paid it in order to enter demo mode, your later subscription carries the subscription only — the fee line is not on it, and you have no account verification to redo. Your verification file, your identity check and your registry check remain acquired; they are neither cancelled by the end of the trial nor asked for again on subscription. The amount due is computed server-side in a single place, and it is zero as soon as a payment date exists: a second request to pay is refused, not charged and then refunded.
8.11 — No successful verification, no demo mode. Demo mode is opened only to a file whose verification has succeeded. If the examination does not conclude — a discrepancy with the registry, a missing document, an identity not confirmed — the trial is not granted, and paying a second time would not unlock it: the fee pays for the examination, the examination was carried out, and clause 8.2 applies. The only path is to send us the documents that resolve the discrepancy at support@lifaio.com; we then take the file up again at no additional cost.
Last revision of this article: the French version governs.
9.1 — Documents that govern, and promotional material. The documents that create obligations are these terms, the privacy policy and the service documentation pages published on seal.lifaio.com. Promotional material — presentation pages, advertisements, press releases, social media posts, summaries written by third parties — is provided for information: it describes the service in plain language, it does not define it. Where a promotional description differs from the documents above, those documents apply. If an error, an imprecision or a typo finds its way into promotional material, it creates no right, no warranty and no additional obligation, and Technologies Marco Prive corrects it as soon as it is reported — an email to info@lifaio.com is enough. This clause reduces no mandatory right granted to a consumer by law, and releases Technologies Marco Prive from none of its obligations regarding commercial representations.
EXCLUSIVE governing law and forum: these terms and any dispute, claim or controversy arising from or relating to the service are governed EXCLUSIVELY by the laws in force in the Province of Québec (Canada) and applicable Canadian federal law, without regard to conflict-of-law rules. Any proceeding shall be brought EXCLUSIVELY AND SOLELY before the competent courts of the Province of Québec (Canada), judicial district of Montréal, and the parties attorn to the exclusive jurisdiction of those courts. (This clause applies to the extent permitted by mandatory consumer-protection laws of a consumer's place of residence, where applicable.) Authoritative language: the FRENCH VERSION of these terms (and of all service policies) alone is authoritative; translations into other languages are provided for convenience only and create no divergent obligations. These terms may be updated; any major update is notified and requires renewed acceptance. Brand and mechanism: exclusive property of Technologies Marco Prive.
Archived versions of this document → Every version a customer accepted stays readable exactly as it was.
