Privacy notice

What we collect

• •The title and message you add, if any.
• •When you send by email: the sender name you type and the email addresses of up to 50 recipients.
• •Your browser, or the Dropvi command-line tool on your own computer, encrypts the title, message and sender name before upload, and Dropvi stores them only in encrypted form, with random values used to derive the keys: the key salt and, when you set a PIN, the PIN salt. Recipients’ email addresses are not encrypted, because Dropvi needs them to send the emails.
• •Your account email address, when you ask Dropvi to email your recipients or to tell you when the first download starts.
• •Your settings: the expiry date, any download limit, and any PIN or password, which is stored only as a hash.
• •If you are signed in, Dropvi emails your account address once, about a day before each transfer you sent expires, unless you turn these reminders off in your dashboard. The email gives the number and size of the files and when the transfer expires, and links to your dashboard; it never contains the transfer’s link or key. We record when the reminder was sent. If you extend a transfer, the new expiry date replaces the old one.
• •The number of files, their total size, how many times the transfer has been downloaded, and when it was created, finished uploading and was deleted.
• •If you are signed in, which account sent it; on a paid plan with a branded subdomain, the subdomain.
• •If you sent it without an account and later choose to add it to your account, which account that is. After you sign in on the upload page in the browser you sent from, Dropvi asks whether to add the transfers sent from that browser; nothing is added unless you choose to (asking for an account from a transfer’s success screen adds that transfer). Once added, its deletion key stops working. A transfer that would take the account past the storage its plan holds is not added. On a shared browser, add only transfers you sent.

The key is in the link after the # sign, and browsers do not send that part to Dropvi. When you send by email, your browser or the command-line tool gives Dropvi the key when the upload finishes, so that the email can contain the full link; Dropvi uses it only to send that email and does not store it, but the email itself, with the full link, is kept by ZeptoMail as Emails we send describes. Anyone with the full link can see the title, message, sender name and files; if the transfer has a PIN or password, they also need it. Without the key, the download page shows the number and size of the files and the expiry date, but not the names, title or message.

When the sender uses Dropvi in a purely personal capacity, Zorinto Ltd is the controller of this data. When the sender is a business or other organisation, it is the controller of the files, their details, the messages and the recipients’ addresses it sends, and Zorinto Ltd processes them for it as its processor.

Why

To store and deliver your files, show them on the download page, send the emails you ask for, remind you before a transfer expires, and let you see, extend and revoke your transfers.

Lawful basis

Contract: we need this to provide the transfer you asked for.

What we collect

• •Your email address, if a sender enters it.
• •Dropvi sends you one email with the download link. The email gives the sender’s email address, the number and size of the files and the expiry date, and the full link with the key, so anyone who can read the email can open the files. It does not contain the title, the message or the sender name. If you reply to the email, your reply goes to the sender’s email address.
• •Each recipient gets a separate email, and recipients’ addresses are not shown on the download page. The sender gets a confirmation email that lists every recipient, except for a reply with files (see below).
• •If you use Reply with files on the download page, Dropvi emails the sender a link to your files and gives them your email address. See Replies with files.
• •If the sender was signed in and has saved recipients turned on, your address is also saved to their account’s saved recipients, so they can pick it next time. See Saved recipients.

You do not need an account to download.

When the sender uses Dropvi in a purely personal capacity, Zorinto Ltd is the controller of this data. When the sender is a business or other organisation, it is the controller of the files, their details, the messages and the recipients’ addresses it sends, and Zorinto Ltd processes them for it as its processor.

Why

To deliver the files a sender chose to send you.

Lawful basis

Legitimate interests: delivering a transfer that the sender asked us to deliver.

What we collect

• •When you are signed in and email a transfer, Dropvi saves each recipient’s email address to your account, in lower case, with when it was first saved and last used. The address of the person you reply to with files is never saved.
• •This is on for every account unless you turn it off. You can turn it off at any time in your dashboard settings; turning it off deletes every address saved to your account, and nothing more is saved until you turn it on again. We store whether it is on with your account.
• •The upload form offers your saved addresses as you type, most recently used first. Only you can see them, when signed in.
• •Your account keeps up to 200 addresses. When a send would take it past 200, the addresses you used least recently are deleted.

You can remove an address with the × next to it on the upload form. Recipients’ addresses are not encrypted, as for the transfers themselves.

When the sender uses Dropvi in a purely personal capacity, Zorinto Ltd is the controller of this data. When the sender is a business or other organisation, it is the controller of the files, their details, the messages and the recipients’ addresses it sends, and Zorinto Ltd processes them for it as its processor.

Why

To let you pick people you have sent to before instead of typing their addresses again.

Lawful basis

Contract: part of the service you use when signed in. For the recipients: legitimate interests, making it easier for you to send to people you chose.

What we collect

• •A download page offers Reply with files when the transfer was emailed to recipients by a signed-in sender and is not branded. Anyone with the link can reply after confirming their email address with a sign-in code, and, if the transfer has a PIN or password, after unlocking it.
• •A reply is stored as a transfer, with the replier’s account email address as its sender address and any sender name they type. Dropvi also stores which transfer it answers and its place among that transfer’s replies: a transfer can take up to 5 replies, and up to 2 from any one account.
• •Dropvi looks up the original sender’s email address itself and stores it as the reply’s recipient. Dropvi does not show that address to the person replying: the download page and the reply form give only the original sender’s name, if they gave one, and their confirmation email calls them the original sender.
• •The original sender receives the reply as a transfer email. For a reply sent since end-to-end encryption was introduced, the email gives the replier’s email address; for an older reply, it showed the replier’s name, or their email address if they gave no name. Replies to it go to the replier’s confirmed email address. Replying therefore shares your email address with the original sender.
• •Every reply is end-to-end encrypted in the same way as a transfer sent from the website. Your browser also sends with the reply a copy of the reply’s key, encrypted so that the original sender can open it from the browser they sent from, if they sent from a browser, unless the original transfer has a PIN. Dropvi cannot open that copy. Anyone else needs the key, which you send another way.

Why

To deliver files back to the person who sent you a transfer, and to limit how many replies one transfer can receive.

Lawful basis

Contract with the person replying, who asks us to deliver their files. Legitimate interests for the original sender’s address: delivering replies to a transfer they sent by email.

What we collect

• •The title, message and the name people sending files see, which you type as plain text. Anyone with the link can see them on its upload page.
• •Each link’s limits (the largest upload, the most it takes in total, how long it stays open and how long each upload is kept), whether it is open or closed, and when it was created, closed and last told you about new files.
• •Your receive key’s public half and its key ID. Your browser makes the receive key, and its private half never leaves your browsers: Dropvi does not receive it, the backup file or the backup passphrase.
• •When a receive key is set up on your account or replaced, Dropvi emails your account address with the key ID and the time, so that you would notice a key set by someone else.
• •When files arrive through one of your links, Dropvi emails your account address, at most once an hour for each link. The email gives the link’s title, the number and size of the files and how long they are kept. It does not say who sent them or what they wrote, because Dropvi cannot read that.
• •When you have Dropvi email one of your links, Dropvi sends one email to each address you enter (up to 10 at a time), with the link, its title, the name on the link, your account’s email address and your message. Dropvi uses the addresses and the message only to send those emails and does not store them. It stores only how many addresses each send went to, which link it was and when, to apply the daily limit on how many addresses an account can email, and deletes that record 7 days later.

Uploads through your links count against your account’s storage, and you decide what to ask people to send and what to do with the files you receive.

If you email a link, you decide whom to email and you are responsible for having the right to email them. The people you email see your account’s email address.

Why

To provide the link, take files through it for you, email it for you when you ask, and tell you when files arrive.

Lawful basis

Contract. For the addresses you email: legitimate interests, sending the email you asked us to send to people you chose, and limiting how many an account can send.

What we collect

• •You do not need an account. Every upload runs the Cloudflare Turnstile security check.
• •Your browser encrypts your files, their names, types and checksums, and the name and message you add, for the link’s owner before upload. Dropvi cannot read them. Dropvi stores the number of files, their sizes, which link they came through, when they were sent, and a public key your browser makes for that upload only.
• •For a link of an account on the free plan, Dropvi also records the upload’s size, the time and a keyed hash of your network for the 24-hour upload limits, as described under Request logs, rate limits and error reports.
• •Only the link’s owner can download the files. You cannot open or delete them after sending; contact the link’s owner if you need them removed.

The link’s owner decides what to ask for and what to do with the files. Dropvi has not checked who the owner is. If a link looks like it is misusing your trust, report it from its upload page.

When the link’s owner uses Dropvi in a purely personal capacity, Zorinto Ltd is the controller of what you send. When the owner is a business or other organisation, it is the controller, and Zorinto Ltd processes what you send for it as its processor.

Why

To deliver your files to the link’s owner, and to stop request links being used to fill an account’s storage or to upload without limit.

Lawful basis

Legitimate interests: delivering files to the person who asked for them, and keeping Dropvi safe.

What we collect

• •The files you upload. They can contain personal data about you or about other people.
• •For each file: its name, size and type, and its SHA-256 and CRC-32 checksums, which are worked out while the file uploads.
• •Your browser, or the Dropvi command-line tool on your own computer, encrypts each file, its name, its type and its checksums before upload, and Dropvi stores only the encrypted form and the file’s size.

Dropvi does not scan files for their content or build any index of what they contain, and it cannot read them. Recipients can preview some file types in their browser: the recipient’s browser fetches the encrypted file and decrypts it.

When the sender uses Dropvi in a purely personal capacity, Zorinto Ltd is the controller of this data. When the sender is a business or other organisation, it is the controller of the files, their details, the messages and the recipients’ addresses it sends, and Zorinto Ltd processes them for it as its processor.

Why

To store the files until the transfer expires and deliver them to people who have the link.

Lawful basis

Contract with the sender.

What we collect

• •Each time a file is downloaded or previewed, or a transfer is downloaded as a ZIP file: which transfer and file, the type of event, the time, the size of the file or ZIP file, the country that Cloudflare associates with the connection, your browser’s user agent (up to 512 characters) and a hash of your IP address.
• •The hash is made by combining your IP address with a secret key and applying SHA-256, so the address itself is not stored. The same address always gives the same hash, so events from one address can be linked.
• •When the first download of a transfer starts, Dropvi emails the sender: always for transfers sent by email, and for link transfers when the sender ticked the option to be told. The email says that a download has started. It does not say who downloaded.
• •A signed-in sender can instead choose, for a transfer or as their account’s starting choice, an email on every download. Dropvi then sends at most one email every 15 minutes for the transfer, listing the downloads since the last one: for each, the time, the country Cloudflare associates with the connection, and whether it was the whole transfer or one file. It never gives the IP address, its hash or the user agent. Downloads inside the 15 minutes are listed in the next email, which can come up to about an hour later. We record when the last of these emails was sent and which downloads it covered.
• •A sender signed in to the account that owns a transfer can see its 100 most recent downloads in their dashboard: the time, the type of event and the country of each. They do not see the hash of the IP address or the user agent. They can save that list as a CSV file, which their browser makes from the same details, with no IP address.

Why

To tell senders that a download has started, or about each download when they ask for that, show them when their transfers were downloaded, investigate misuse, and produce service statistics such as downloads per day and per country.

Lawful basis

Legitimate interests: running, securing and improving the service, and giving senders notice that a download has started and a record of when their transfers were downloaded.

What we collect

• •Your email address when you ask for a sign-in code, a keyed hash of the six-digit code (not the code itself), when it was sent and used, and how many wrong attempts were made.
• •When you confirm your address with a code, Dropvi creates a free account for that address if there is none. The account holds your email address, your plan, and when it was created and last updated.
• •When you sign in, a random session token linked to your account, with its start and expiry dates.
• •When you sign the command-line tool in through the browser (dropvi login): a sign-in request with a short code, the country it came from (as Cloudflare reports it, not your IP address), whether it was approved or denied, which account approved it, and when it was made and expires. A one-way hash of the request’s secret is stored, not the secret itself, and no session token is stored with it.
• •If we suspend your account: when, and the reason we recorded. We email you when we suspend it and when we lift the suspension.
• •If we close your account, it is deleted as described in Deleting your account, and we email you that it is closed. Before that, a transfer from your account that we keep as evidence or that has an open report, and that has no sender email address, takes your account’s email address as its sender address, because a report to the National Crime Agency must include the uploader’s email address.
• •After we close an account, we may refuse sign-in, and new accounts, for its address for up to 5 years. For that we keep a keyed hash of the address (lower case and without any +tag; the address itself is not stored) and the date, and nothing else. Any other account on the same address with a different +tag may be suspended at the same time, as described above.

You need to sign in to have Dropvi email your recipients or tell you about downloads, to reply with files, to use a paid plan, and to see your transfers in the dashboard. Sharing a link needs no account.

Why

To confirm that you control the email address, provide your account and keep you signed in, to suspend or close an account that breaks our terms or the law, and to stop a closed account coming straight back.

Lawful basis

Contract; legitimate interests for suspensions, closures and the record that stops a closed address signing up again: keeping Dropvi and other people safe, including under our duties in the Online Safety Act 2023. Legal obligation for the sender address kept on evidence for the National Crime Agency. Where the record that stops a closed address signing up again relates to suspected criminal offences, we also rely on the condition in paragraph 10 of Schedule 1 to the Data Protection Act 2018 (preventing or detecting unlawful acts), with an appropriate policy document in place.

What we collect

• •If you set up a branded portal: your subdomain, brand name, headline, accent colour, logo address, background image address, download page message and download page link.
• •While your paid plan is active, anyone can see these on your portal and on your branded transfers.
• •Your logo and background image load from the addresses you enter. If they are hosted on another website, a recipient’s browser requests them from that website, which can see the recipient’s IP address. The background image is requested without saying which page asked for it.

Why

To show your branding, as part of your plan.

Lawful basis

Contract.

What we collect

• •The team’s name, which its owner types as plain text, and who owns it.
• •Each member’s email address, name (if they gave one) and the date they joined. Everyone in the team can see these while the team’s plan is active; once it has ended, only the team’s owner can.
• •Invitations: the invited email address, a one-way hash of the invitation code (not the code itself), who sent it, and when it was sent, expires, was accepted or was revoked. Dropvi emails the invitation, with the code in the link, to the invited address.
• •Which transfers were sent with the team. While the team’s plan is active, everyone in the team sees, for each team transfer, who sent it, its size, the number of files, its dates, its downloads and download limit, whether it has a PIN, and the number of recipients. They do not see who it was sent to, and they cannot open it: its key is made in the sender’s browser and Dropvi never stores it, so it cannot pass it to anyone, the owner included. Once the plan has ended, only the owner sees the team’s transfers.
• •The team’s owner can remove members, revoke the transfers members sent with the team, and see members’ transfers in the team list as above. When a member is removed or leaves, Dropvi emails the person affected or the owner.

Team transfers count against the team’s shared storage. A member’s transfers stay theirs: they can still see and revoke them after leaving the team.

Why

To provide the team plan: shared storage, the team’s portal, its transfer list and one bill.

Lawful basis

Contract with the team’s owner, and with each member for their own account. Legitimate interests for an invited person’s address: delivering the invitation the owner asked us to send.

What we collect

• •When you upgrade, Dropvi sends your email address and account ID to Stripe, with the label of the upgrade link you came through if any (see Plan limits and checkouts), and takes you to a Stripe checkout page. You enter your card details on Stripe’s page; Dropvi never receives them.
• •From Stripe we store your Stripe customer and subscription IDs, the price you chose, the number of seats on Teams & Suite, your subscription status and the end of the current billing period.
• •A history of plan changes: the old and new plan, what caused the change, and when.
• •For the Business Pro free trial: when a checkout offering it was opened and that checkout’s ID at Stripe (so that, if you cancel it on Stripe’s page, we can close it and offer the trial again), when your trial started, when you first paid, and when we sent the email 2 days before it ends. To check that a trial has not been had before, Dropvi asks Stripe whether your Stripe customer, or any Stripe customer with your email address, has had a Dropvi subscription. Before sending that email, Dropvi reads your subscription from Stripe, so it is not sent if you have cancelled. When a trial starts, Dropvi emails you to confirm it, with the date of the first charge, unless Stripe does.
• •When a trial starts, Dropvi also keeps two pseudonymised records, so that deleting your account and signing up again, or using the same card on another account, does not give a second trial: a keyed hash of your email address (lower case, without any +tag, and for Gmail without dots), and a keyed hash of each card’s fingerprint, which Stripe gives us in place of the card number. Neither is the address or card itself, and nothing links them to your account. If a card has had a trial before, the new trial ends at once, the subscription starts and we email you to say so.

Why

To take payment, apply your plan, offer the free trial once, remind you before a trial turns into a charge, and let you manage billing in Stripe’s customer portal.

Lawful basis

Contract; legal obligation where tax and accounting law requires us to keep payment records; and, for the hashes of email addresses and cards kept after an account is deleted, legitimate interests: preventing abuse of the free trial. You have the right to object to that use; see Your rights.

What we collect

• •Anyone can report a transfer from its download page. We store the transfer, the reason, any details you write (up to 1,000 characters), any link you give (up to 300 characters), your email address if you give it, a hash of your IP address made in the same way as for downloads, and the date.
• •Dropvi emails the report to info@dropvi.com, including your email address and the sender email stored with the transfer. While a report is open, further reports about the same transfer for the same reason are stored without another email.
• •Dropvi cannot see the files, file names, title or message of an encrypted transfer. If you want us to check them, you can paste the transfer’s full link, including the key after the # sign, into the optional Full link field of the report form. The link is then stored with your report, and anyone at Dropvi who handles the report can open the transfer with it. The email to info@dropvi.com says that a link was given but does not contain it.
• •An intimate image report needs your email address and three declarations: that it is intimate image content, that you are the person shown or acting for them, and that the report is made in good faith and is true to the best of your knowledge and belief. We store which of the two you are and when you made the declarations, with the report.
• •If you give your email address, Dropvi emails you once to confirm that it received your report and to say what happens next. It sends at most 3 of these emails to one address in 24 hours, ignoring any +tag in the address.
• •For an intimate image report of a transfer, the acknowledgement contains a single-use link that confirms the report, which works for 7 days. We store only a one-way hash of its code, and when it was used. If a confirmed report is still open 46 hours after we received it, Dropvi stops the transfer being downloaded and keeps its files and record until we decide, and emails the account or sender address of the transfer that it is unavailable, which transfer it is (when it was sent, the number of files and their size) and how to appeal, without saying who reported it. At most 3 transfers are taken down this way in 24 hours for one account or sender address (transfers sent with neither count together), one reporter address (ignoring any +tag) or one reporter IP address; a report over these limits, or one whose confirmation link could not be sent because its address had already had 3 emails from us that day, is passed to a person to review within 48 hours. If we decide it is not intimate image content, we make the transfer available again, or, if it has expired meanwhile, its files are deleted. When we decide, we email the reporter the outcome.
• •If the owner of a request link reports a file sent to it as child sexual abuse material or terrorist content, we take it down and keep it, rather than deleting it, while we investigate.
• •If we disable a reported transfer, its files are deleted. If a report may be child sexual exploitation and abuse content, we take the transfer down but keep its files and records, and if we report it to the National Crime Agency we store the NCA’s reference and when we sent it. A request link reported to the NCA has its title, message, owner name and owner’s email address copied into the report.
• •Anyone can also report a request link from its upload page. We store the link, the reason, any details you write (up to 1,000 characters), your email address if you give it, a hash of your IP address made in the same way, and the date. Dropvi emails the report to info@dropvi.com with the link’s title, message and owner name and the owner’s account email address. We can disable a reported link, and its owner cannot then reopen it.

Why

To investigate reports, remove unlawful or harmful transfers, report child sexual exploitation and abuse content to the National Crime Agency, and contact you about your report if you gave an address.

Lawful basis

Legitimate interests: keeping Dropvi safe and dealing with misuse. Legal obligation for intimate image reports and for reports to the National Crime Agency and the records kept about them, under the Online Safety Act 2023 and the regulations made under it.

What we collect

• •Your email address, your name if you give it, and what you write.

Why

To answer you.

Lawful basis

Legitimate interests; contract where your message is about your account or a transfer.

What we collect

• •Cloudflare, which hosts Dropvi, receives the IP address of every visitor in order to deliver the service. Our website and API record requests in Cloudflare’s Workers Logs: the time, the web address requested, and other details of the request and response that Cloudflare adds. They also hold messages our API writes. When a request fails unexpectedly, our API logs the method, the path of the web address with transfer and file IDs and request link codes replaced, and the type of error with its message and stack trace; if a database query failed, the values the query used are cut out of that message. Its other messages can still name a transfer or a file, and, when a stored file cannot be deleted, its file name. Where our API catches a database error itself, its message holds the query and the values it used, such as the country, browser and hashed IP address recorded with a download. A message about an email we could not send can hold the address it was for.
• •Dropvi’s emails show the Dropvi logo, and in some mail apps use the Dropvi font, both loaded from dropvi.com when your mail app loads images. That is a request to dropvi.com like any other. The addresses are the same in every email, so they do not tell us who opened which email.
• •To slow down misuse, we count recent requests over one-minute periods using Cloudflare’s rate limiting: by IP address (for IPv6, each /64 network), by email address for sign-in, by account for transfers and replies sent while signed in, and by request link for uploads to it.
• •When you start a transfer without an account or on the free plan, or send files through a request link of an account on the free plan, we record its size, the time and a keyed hash of the network it was sent from: your IP address, or for IPv6 its /64 network and its wider /48 network, each combined with a secret key and hashed with SHA-256, so the address itself is not stored. This record is kept separately from the transfer and the account, and holds nothing else. We use it to limit how much can be uploaded from one network in 24 hours without a paid plan, which stops our storage being misused, and to see how much free uploading Dropvi takes in 24 hours altogether. Transfers sent on a paid plan are not recorded, and nor are uploads through a request link of an account on a paid plan: those are limited by that account’s storage and the link’s own limits instead.
• •When error reporting is configured, errors in our API are sent to Sentry. A report holds the type of error, its message and stack trace, the time, the request method and the path of the web address with transfer and file IDs and request link codes replaced. If a database query failed, the message keeps the query but not the values it used. A report does not hold your IP address, the time zone Cloudflare associates with your connection, a record of what our API did earlier in the same request, or the request’s headers, cookies, query string or body, so a PIN, password, sign-in code or session token is not sent.
• •When something goes wrong in your browser on our website, it sends a short error report to our API. This happens when one of our own scripts fails unexpectedly, when an upload stops, or when you close or leave the page while an upload is running. A report holds the type of error and, for a script failure, its message and stack trace. For an upload, it holds the step the upload stopped at (encrypting, creating the transfer, checking the file, sending a part or finishing), the HTTP status our API returned, which part of the file it had reached and, if the connection failed, your browser’s own network error text. Every report holds the path of the page you were on. Before a report leaves your browser, and again when our API receives it, web addresses are cut to their path, so the decryption key in a share link, any query string and a branded subdomain are removed, and transfer IDs, a request link’s code and other long codes are replaced. A report never holds a file name, the contents of a transfer or your email address. Our API adds your browser’s user agent string, records the report in Workers Logs and, when error reporting is configured, sends it to Sentry without your IP address. A page sends at most five reports.

Why

To run, secure and fix the service.

Lawful basis

Legitimate interests.

What we collect

• •Some links to Dropvi, in its emails and download pages or on other websites, carry a fixed label, such as ?src=email_recipient or ?src=hn, that says where the link was placed. Each label comes from a fixed list and does not identify you or the transfer.
• •When you follow one of these links, the label is recorded in Cloudflare’s request logs as part of the web address, and your browser keeps it in session storage for that tab.
• •When you follow a link to Dropvi from another website, and your browser tells Dropvi which website that was, your browser keeps the domain that website is registered under, such as ycombinator.com for news.ycombinator.com, in session storage for that tab. Only that domain is kept, never the address of the page you came from. Dropvi’s own sites, including branded subdomains, are not kept, and a hostname already kept in that tab is not replaced by a later one.
• •The next transfer you create in that tab stores the label and the domain with the transfer record, and both are then removed from your browser. A reply is stored with the label reply and the transfer it answers, as described under Replies with files. A transfer sent with the Dropvi command-line tool is stored with the label cli.
• •Our admin view counts transfers by label, and by domain for the 20 websites with the most transfers.

Why

To see which links and websites bring people to Dropvi and how many transfers they lead to.

Lawful basis

Legitimate interests: understanding which of our links, and which other websites, bring people to Dropvi.

What we collect

• •On the public information pages listed under Analytics and tools below, Cloudflare Web Analytics sends Cloudflare the page address, including any part after a #, the referring website and how the page loaded. Cloudflare receives your IP address with it, as it does for every request.
• •It sets no cookies and uses no browser storage. Cloudflare states that it does not keep the query string of a web address and does not track visitors across websites.
• •We see only totals in Cloudflare’s dashboard, such as visits and page views by page, referring website, country and browser.

Why

To see how many people read the public information pages and which websites bring them.

Lawful basis

Legitimate interests: understanding which of our pages people read and how they find them.

What we collect

• •When you reach a limit of your plan, such as the largest transfer, the longest expiry or the storage it holds at once, our API records which limit it was and the time. Your browser reports two of these to our API itself, the transfer size and the expiry, because it checks them before anything is sent.
• •When you start a checkout for a paid plan, complete one, or cancel one on Stripe’s payment page, we record the plan, the time and, if you came through one of Dropvi’s upgrade links, its fixed label, such as ?src=size-limit, which says where the link was placed.
• •If you are signed in, the record holds your account ID. It never holds your IP address or email address, and no cookie or third-party analytics service is used for it.
• •Our admin view counts these records by limit and by label.

Why

To see which plan limits people reach and which upgrade links they use, so we can make them clearer.

Lawful basis

Legitimate interests: understanding how people use our plans and how our upgrade links work.

What we collect

• •When you ask for a sign-in code, when you send a transfer without signing in, and every time you send files through a request link, your browser runs Cloudflare Turnstile, a check that tells people from automated programs. It usually needs nothing from you; now and then it asks you to tick a box.
• •The check is a script and a small frame served by Cloudflare from challenges.cloudflare.com. Cloudflare receives your IP address and signals from your browser, such as its user agent, and gives your browser a single-use token. Our API sends that token, with your IP address, to Cloudflare’s verification service, which tells us whether the check passed, for which page and for which action. We do not store the token or the result. When a check fails, our request logs note Cloudflare’s reason, the action and the website it was solved on, without your IP address.
• •Cloudflare describes what it does with this data in its Turnstile Privacy Addendum.

Why

To stop automated programs sending sign-in codes to other people’s addresses, filling our storage with transfers nobody asked for, and filling an account’s storage through its request links.

Lawful basis

Legitimate interests: keeping Dropvi safe and dealing with misuse.