Privacy policy
Operated by SealDrop, British Columbia, Canada.
SealDrop lets businesses — accounting firms, law firms, brokers and others — send people a secure link to upload documents and, if the business chooses, fill in a form. The business decides what to ask for and is responsible for your information; SealDrop stores and delivers it for that business, in Canada, and deletes it shortly after the business has filed it.
Who is responsible
- The business that sent you the link (“the organization”) is responsible for your personal information under the privacy law that applies to it — for example PIPEDA, British Columbia’s Personal Information Protection Act (PIPA), or a provincial law specific to its sector. Questions about your records, corrections or access go to the organization.
- SealDrop is the organization’s service provider. We only use your information to provide the service to that organization, under a written agreement with them. We never sell it, use it for advertising, or combine it with other data.
What we handle
- Your name and email and/or mobile number, entered by the organization — to send you its link and reminders.
- Files you upload, answers to the organization’s form (which may include your date of birth or an identification number if the organization asks), and a message to the organization if it lets you reply — to deliver them to the organization. If the organization’s form works out results from your answers (its own scores, review flags, calculations and notes for its team), those results are kept with the request record after your answers are deleted.
- Your IP address and when you used the link — for security, abuse limits and the organization’s audit trail.
- For the organization’s staff: name, work email, role and the parts of the app they may open, sign-in times and IP address — for accounts, security and audit; for staff who turn on Face ID or Touch ID in the app, a passkey’s public key, kept by our sign-in service until they turn it off (the face or fingerprint itself never leaves their device); when an admin accepted our terms for the organization (who, when, from where); and, for staff who turn on notifications on a phone or computer, that device’s push address and a label like “iPhone · Safari”, kept until they turn it off or 90 days after the device was last used. Notifications pass, encrypted, through the push service of their browser (Apple, Google, Mozilla or Microsoft) and show the organization’s name and a request reference, never a client’s details.
- If the organization saves you as a contact: your name, email and/or mobile number, an ID number it uses for you if it asks for one (such as a government-issued number or its own file number — its staff see it masked unless they choose to show it, which is recorded), the groups it puts you in, and how and when you agreed to be contacted — so it can send you requests again without typing your details. If the organization turns it on for a form, also a short summary of what that form found (the date, its own scores and review notes, and the answers it chose to keep), never your documents or all your answers; and a form can update your name, email, mobile, date of birth or ID number in that record from your answers. Kept until the organization deletes you, and deleted automatically after 24 months without any request or activity.
- If the organization sends a request to a list of people: the list itself is not uploaded or kept. So nobody is emailed twice by mistake, we keep a one-way scrambled code of your email address (never the address) for 90 days after a request is sent, or 12 months if an email to it bounced or was reported as spam. The organization’s confirmation that it had permission to contact the people on the list (who confirmed, when, and the exact wording) is kept for 3 years, without any names or addresses. Every bulk email has an unsubscribe link; if you use it, that organization’s later lists skip your address (kept as the same scrambled code, until the organization lifts it).
We do not use cookies or trackers on the upload page or this website.
Paying for SealDrop
Organizations pay through Stripe, our payment processor. On Stripe’s page the person paying gives their email, billing address, the organization’s name, industry and time zone, and a card or bank account. Stripe keeps the card and bank details; SealDrop never sees them. SealDrop receives the organization’s name, industry and time zone, the email (it becomes the first admin’s sign-in), the plan, and Stripe’s reference numbers and payment dates, and keeps them while the account is open. Stripe may process billing information outside Canada; it never receives the organization’s clients’ files, answers or details. See Stripe’s privacy policy.
This website’s data residency check
If you use the data residency check, the domain you type is sent to SealDrop’s server in Canada, which looks up that domain’s public DNS records and compares its addresses with the address ranges that cloud providers publish (and, for other addresses, asks the public RDAP registry about that address). The domain and the result are not stored or logged, and nothing about you is sent to anyone else. Your IP address is counted for abuse limits, in a counter that deletes itself within a few days.
This website’s contact form
If you write to us through the contact form, your name, work email, organization, industry, team size, the plan you’re interested in, your note and, for a demo, the times that suit you are emailed to our team so we can reply (and we email you a short confirmation, at most one a day, holding nothing you typed except the demo times you picked), and your IP address is counted for abuse limits (in a counter that deletes itself within a few days, never with what you typed). Nothing you type is stored in SealDrop itself; the message stays in our team’s mailbox while we talk with you. Ask our Privacy Officer to delete it at any time.
Emails and text messages
Links are sent by email and, if the organization uses texts, by text message from SealDrop’s number, using Amazon Web Services in Canada. Messages contain the organization’s name, the secure link, its expiry and (for texts) how to stop texts. They contain your first name only if the organization has turned that on, and nothing else about you. Reply STOP to a text to stop texts from SealDrop’s number.
The SealDrop extension for Google Chrome
An organization’s staff can add SealDrop’s extension to Google Chrome, to use SealDrop beside the other apps they work in. They sign in with their own SealDrop account (two-step sign-in) and see only what they could see in the app.
- Reading a page. It reads a web page only on the tab where staff open it (its toolbar icon, its right-click entry or its keyboard shortcut), or on sites the staff member turned it on for: one app (such as their records system or CRM), one site, or every site (“Look on every site”, off until they turn it on, and Chrome asks them first). It looks on that page for email addresses, phone numbers and the organization’s ID numbers, to find the person in the organization’s SealDrop account. What it reads stays in the browser: only the detail staff choose to search for is looked up, in the organization’s own account, as a search in the app would be.
- Putting documents into another app. It fetches a person’s documents from SealDrop into the browser’s memory (recorded as a download, as in the app) and hands them to the upload in the app the staff member chose. It never saves them to the computer.
- What it keeps. Its sign-in and what it is working on, in the browser’s memory only: gone when Chrome closes, after 30 minutes without use, or when staff sign out. In Chrome’s settings it keeps only the list of sites it was turned on for and, if the staff member ticks “Don’t ask for a code on this device for 30 days”, the sign-in service’s key for that computer (as the app does; the password is still asked).
- Nothing else. No analytics, trackers or advertising. It uses what it reads only to provide these features, never sells or shares it, and never uses it for anything else; its use of information follows the Chrome Web Store User Data Policy, including the Limited Use requirements.
Where and how long
- Everything SealDrop stores is in Canada (Amazon Web Services, Montréal region), encrypted at rest and in transit. (Payment details stay with Stripe; see above.)
- Uploaded files are checked for malware before the organization can open them.
- Files, form answers and your message are deleted when the organization marks them filed, a set time after it first downloads them (72 hours by default), or 30 days after you submit if nobody downloads them — and after 35 days at the latest. Deleted files are not kept in backups.
- If the organization saved you as a contact, those details stay until it deletes you, and are deleted automatically after 24 months without any request or activity (or 35 days after the organization leaves SealDrop).
- People added to a bulk request but never sent are deleted after 30 days. The rest of the request record (your name, contact details, the organization’s note, file names and the results its form worked out) is deleted 90 days after the files. The audit trail of actions (IDs and times, never your files or answers) is kept for 2 years for security, then deleted. Encrypted database backups age out 35 days after any deletion.
Who can see it
- Staff of the organization who have a SealDrop account (two-step sign-in required).
- SealDrop staff only to keep the service running, never to read files or answers in the normal course.
- Amazon Web Services hosts the service in Canada.
- Stripe processes the organization’s payments (billing details only, never clients’ information).
Your choices and rights
Ask the organization to see or correct your information. You can ignore a link; nothing is collected unless you use it. Questions or complaints about SealDrop: reach our Privacy Officer at privacy@sealdrop.ca. If you are not satisfied, you may contact the Office of the Privacy Commissioner of Canada or your provincial privacy commissioner (in British Columbia, the Office of the Information and Privacy Commissioner).
Changes
We will post changes here with a new date and tell organizations in advance.