Security and privacy, in plain words
Information is stored and processed in Canada, encrypted, and deleted once you’ve filed it. Here is exactly what that means — including the limits.
- Stored in CanadaAWS Montréal
- Encryptedat rest and in transit
- Deleted on schedule35 days at most
- Every action loggedexportable audit trail
Stored in Canada
Every record, file, answer and login lives in Amazon Web Services’ Montréal region (ca-central-1). The service is set up so it cannot be deployed anywhere else.
Encrypted
At rest with a dedicated encryption key, and in transit with HTTPS only.
Scanned and checked
Uploads land in a separate quarantine store, are scanned for malware, and must really be the PDF or photo they claim to be — a renamed web page or script is blocked. Your team can only open clean copies.
Deleted on a schedule
Files: when filed, a set time after download, or unclaimed — 35 days at most, never backed up. A request’s names, contact details and form results: 90 days after its files. Clients your team saves: when deleted, or after 24 months without activity. Database backups age out 35 days later. Audit log: 2 years.
Signed in twice
Every user needs a password and an authenticator-app code. Breached passwords and risky sign-ins are blocked.
Upload-only links
A link can only upload. It never shows other files or other people.
Locked-down apps
Our web pages run only our own code — no third-party scripts, trackers or ads — and the browser is told to refuse anything else. Forms are plain questions, never code.
Direct access raises an alarm
Anyone other than the app itself reading files or client records — including our own team — is recorded and triggers an alarm.
Every action on record
Who sent, opened, uploaded, downloaded and deleted what — without personal details in the log. Your admins can export it.
Nothing sensitive in messages
Emails and texts carry your organization’s name, the secure link and its expiry — the first name only if you turn that on. An email’s subject can end with a short request code, which says nothing about the person.
The API: what a key can and can’t do
Your organization can connect its own software (a CRM, records or tax software) with an API key. A key acts only for your organization, only within what an admin allowed it.
What a key can do
- Send requests, and send to groups with a live key
- Read requests and answers; download documents through 5-minute links to malware-scanned copies
- Confirm an import — SealDrop then deletes its copy at once
- Keep clients and groups in step; read the audit log and events
What a key can’t do
- See any other organization
- Touch staff accounts, settings, keys, webhooks, the plan or closing the account
- Download a file that failed the malware scan
- Run from a web page: keys belong on servers (no cross-site access)
- API keys are shown once and stored only as a one-way hash; admins choose each key’s access, IP addresses and expiry, and are emailed every change.
- Every API call is in your audit log, with the key’s name. The API runs in Montréal over TLS 1.2 or newer.
- Webhooks carry ids only and are signed. Test keys never email or text a real person.
- Documents your software pulls into your own systems are then governed by those systems and your own policies — as with any download.
You stay in charge
Your organization is responsible for the personal information it collects, under PIPEDA or the provincial law that applies to you (for example BC PIPA). SealDrop is your service provider and handles it only on your instructions, under a data processing agreement. We never sell data, use it for advertising, or train AI on it. The tools the SealDrop team uses show account settings and counts only — never people, files or answers.
Being precise
- Emails and texts pass through the recipient’s own email or phone provider, which may be outside Canada — that is why they carry nothing sensitive.
- The web certificate for our addresses (domain names only, no data) is issued in AWS’s US East region, as required by the content network.
- There is no official certification for PIPEDA or BC PIPA. We say “built to help you meet your obligations”, and give you the documents to check it: the privacy policy, a data processing agreement and a privacy impact summary.
- Some sectors have their own record-keeping rules (for example professional regulators); your organization stays the owner of its records.
- Our hosting provider’s ISO 27001 and SOC 2 certifications are AWS’s own, not SealDrop’s.
Evidence: the Trust Center has the full data map, answers to vendor-review questions and our automated residency report.
Privacy questions: reach our Privacy Officer at privacy@sealdrop.ca.
Questions
Is the information stored in Canada?
Yes. SealDrop stores and processes it in AWS’s Montréal region and cannot be deployed to another region.
Who can see the documents?
Only signed-in staff of your own organization. The tools the SealDrop team uses show account settings and counts only — never people, files or answers.
Is there an API?
Yes. Your organization's software can send requests, pull documents (SealDrop then deletes its copy) and keep clients in step, with keys stored only as a one-way hash and every call in your audit log. See the developer docs at sealdrop.ca/developers.
Can we get a data processing agreement?
Yes. Every customer signs a data processing agreement that makes SealDrop its service provider.