CohortMarkEffective October 28, 2026. CohortMark is operated by Logic Foundry. Contact [email protected] for privacy, access, correction or deletion requests.
Information we process
Accounts contain an email address, password hash, recovery-code hash, email-verification state and billing identifiers. Issuer workspaces store template text and logos, course details, recipient names, optional emails/references, issued record snapshots and correction/revocation history. Company workspaces also store employee IDs, names, optional contact/department/role details, module content and versions, assignments, assessed completions, expiry dates and administrator notes. Company directories and training histories are private to their administrator account. Uploaded roster documents are processed temporarily on our server to extract plain roster values and are not stored as uploaded files. Only the fields you review and confirm are saved with the workspace. Optional signature images are stored with issuer templates. Recipient acknowledgements store the recipient’s matching typed name, optional drawn signature, signing time, consent wording version, a hash of the specific record and a keyed network-address hash. Private email invitations expire in seven days and cannot be reused to sign again. Recipient signatures can appear in badge PDFs available through the unlisted record link after consent.
Use recipient data only when you are authorized and the recipient expects the certificate. This service is intended for adult workshop providers. Do not submit sensitive identity, medical or financial records, or records about minors.
How we use it
We use this information to operate accounts, generate certificates, show record checks, send requested account and certificate notifications, prevent abuse, manage payments and support the service. We do not sell recipient information or use it to train AI models.
Sharing and service providers
A verification link lets anyone holding it view the recipient name, course, issuer, dates and record status, and download a current PDF. We exclude these pages from search indexing but cannot control copies or links shared by others. We never publish recipient emails on these pages. An internal reference can be printed on a PDF; do not put confidential identifiers there.
Stripe processes payments and billing data; we do not receive card numbers. Resend processes notification emails. Cloudflare provides website delivery/security. Those providers may process information outside Canada under their own terms. Our application records run on the operator’s servers. No independent security certification or data-residency guarantee is claimed.
Cookies and operational counts
A secure, HttpOnly session cookie keeps you signed in for up to 30 days. It is used for authentication. We count aggregate landing/demo visits, issued certificates, checkout starts and provider events. Counts are not unique people. There is no advertising pixel or cross-site analytics identifier. Short-lived rate limits use keyed hashes of network addresses; ordinary network providers may maintain security logs.
Retention and control
Issued records remain while the account exists, including on Starter, unless removed for an account-deletion or abuse request. Export PDFs, CSVs and an account JSON from Settings. Deleting an account removes its personal workspace data and turns old verification links into non-personal withdrawn-record notices. Cancel or settle billing before deleting the account.
Security/administrative history is retained with the account. Expired authentication tokens and rate-limit entries are removed periodically. Sent notification bodies/addresses are cleared from the queue after acceptance; sending status is retained for up to 30 days. Daily application snapshots rotate after seven days; separate disaster-recovery archives expire after 30 days. Deleted data can remain in restricted recovery copies until those copies expire. Payment providers retain records under their own requirements. We do not promise indefinite verification hosting; keep your own exports.
Security and contact
Controls include encrypted website transport, password hashing, unpredictable record links, access checks, sending limits and backups. No system is immune to loss or unauthorized access. Report suspected impersonation, an unwanted certificate or exposed data to [email protected] with the record link.