Answers to the most common questions about how Provlyn works, what it proves, and what happens to your data. Click any question to expand the answer.
Provlyn produces cryptographic proof that a digital file existed at a specific point in time. When you deposit a file, three things happen in sequence: your file is fingerprinted on your device using SHA-256, that fingerprint is countersigned by a trusted European timestamping authority, and the fingerprint is anchored to the Bitcoin blockchain. The result is a self-contained certificate that anyone, anywhere, at any future point in time can verify — without needing to trust Provlyn or any single party.
Anyone who needs to prove a file existed at a specific moment and hasn’t been altered since. Common users include songwriters and musicians protecting unreleased work, game developers preserving builds, design documents, and creative assets, founders and engineers establishing the provenance of inventions and code, lawyers and IP firms preserving evidence for disputes, and venture capital firms running due diligence through Provlyn Deal Rooms.
Two things. Prove it — you can demonstrate to a court, an investor, a counterparty, or a future version of yourself that a specific file existed at a specific moment, in its exact form. Permanently — the proof does not expire and does not depend on Provlyn continuing to exist. Once a deposit is anchored to Bitcoin, the cryptographic evidence persists for as long as Bitcoin does, which is independently maintained by tens of thousands of computers globally.
No. The cryptography happens automatically. Drop a file into the app, and you get a certificate. To verify a file later, drop it into the verifier and get an answer in seconds. The technical detail is available if you want it — full white paper, command-line verification tools, and an open-source verifier library — but you do not need it to use the product.
Three things happen in sequence, and all of them are designed so you don’t need to trust Provlyn for the proof to hold up.
First, your file is fingerprinted on your device. A SHA-256 hash — a 64-character cryptographic signature — is computed in your browser before anything is sent to Provlyn. Changing a single byte of the file produces a completely different fingerprint, and no two distinct files can produce the same one.
Second, the fingerprint is sent to a European timestamping authority that signs it with the exact date and time. This is the same legal mechanism that backs qualified electronic signatures across the EU under eIDAS, and it’s admissible as evidence in courts across the UK, EU, US, Switzerland, and Singapore.
Third, the fingerprint is submitted to OpenTimestamps, which anchors it to the Bitcoin blockchain. Within a few hours your deposit becomes part of a permanent public record that cannot be altered without rewriting Bitcoin itself.
The end result is a self-contained PDF certificate that anyone can verify, even if Provlyn no longer exists.
You tell it. When you click "Deposit new version" on an existing deposit, the new file is explicitly linked to the original through a parent reference, regardless of filename or content. This is deliberate: the contents of v2 may be completely different from v1 — a re-recorded track, a redrafted document, a new build — so the only reliable signal is your own action.
Provlyn detects this. Before a new version is created, the system compares the SHA-256 hash of the file you’re uploading against the existing version. If they match, the upload is blocked with the message "This file is identical to the existing version — no new version was created." You will not end up with two version rows pointing at the same file.
Each version preserves the filename of the file that was actually uploaded at that moment. If you upload report-draft.docx and then later upload report-final.docx as a new version, the chain will show both filenames. The version relationship is stored explicitly in Provlyn’s database, so the chain stays intact even when filenames change.
The search box at the top of each vault searches your deposits by filename, SHA-256 hash, or certificate ID. You can scope the search to the current vault or to all of your vaults using the toggle next to the search box. Vault names appear next to each result when searching across vaults.
Functionally no — Provlyn computes the hash in streaming chunks on your device, so even very large files are supported. In practice the limit is whatever your browser and connection can handle for the upload itself. If you’re working with very large files (full audio sessions, video masters, design archives) the "Protect only" mode on Music plans avoids the upload entirely and just records the cryptographic proof.
Any file type. Provlyn treats every file as a stream of bytes and produces a hash from those bytes. It does not parse, open, or interpret the file content. Documents, audio, video, images, source code, archives, binaries — anything that exists as a file can be deposited.
Provlyn only needs the bytes of the file, not its location. Cloud services like Dropbox, OneDrive, Google Drive, and iCloud all expose your files as normal folders on your computer when their desktop apps are installed — you can pick the file from any of those locations using the verifier’s drop zone or file picker. For files only stored online without a desktop sync, download the file first, then verify.
Verifying by file confirms that a specific file you have on your device matches one of your Provlyn deposits — useful for checking that a file hasn’t been altered since you protected it. Verifying by certificate ID confirms that a certificate is authentic and shows the deposit details associated with it, without needing the original file. Use file verification when you’re asking "is this the same file?", and certificate verification when you’re asking "is this certificate real?".
Yes. The verification pages at /verify-file and /verify-certificate are open to anyone, no account required. A counterparty, court, auditor, or any third party can drop your file into the verifier or enter the certificate ID and confirm the deposit independently. The certificate PDF itself is also self-contained — the embedded RFC 3161 timestamp and the OpenTimestamps Bitcoin proof can be verified offline using free open-source tools, with no dependency on Provlyn’s servers.
Available on Music Pro and Music Studio plans, Protect only creates a cryptographic proof of your file without uploading the file itself. The SHA-256 hash, RFC 3161 timestamp, and Bitcoin anchor are all generated and stored, but the file content stays on your device. It’s the right choice when the file is too large to make uploading practical, when you already have your own storage and backup workflow you’d rather keep using, or when internal policy requires that certain material never leaves your machine. Protect only deposits do not count toward your storage quota.
Files stored in your Provlyn vault are held encrypted on enterprise-grade cloud infrastructure and are not accessed by Provlyn staff — the choice between modes is about workflow and file size, not safety.
Protect only is a Music plan feature because it was designed around the specific workflow of musicians and producers who routinely work with very large session files and need cryptographic proof without uploading the content. Standard plans focus on smaller documents and code where keeping the file in your vault is generally the right default. If you need Protect only and you’re on a Standard plan, switching to Music Pro is the easiest move — and if your needs go beyond what any standard plan covers, Provlyn Bespoke is the alternative.
Provlyn Bespoke covers everything that doesn’t fit the standard plans. That includes substantially higher storage limits, large volumes of Protect only deposits beyond what Music Studio offers, a white-labelled version of Provlyn that you can embed inside your own product, and any other tailored arrangement. If you find yourself outgrowing Scale, Music Studio, or you need Provlyn integrated into something you’re building, get in touch and we’ll put together a quote.
Sharing gives one-off, read-only access to a single vault or file. The recipient does not need a Provlyn account — they verify their email address and view the contents. Shares are tied to a token that you control and expire after 24 hours by default.
Inviting a member gives a person ongoing access. They must have a Provlyn account, and they can view files, deposit new files, and deposit new versions. All of their actions are logged for the vault owner. Members can be removed at any time.
The limit depends on your plan. Starter and Creator each allow 1 member per vault. Founder allows 3, Scale allows 10. On the Music side, Music Pro allows 5 and Music Studio allows 10. If you reach your limit and try to invite another person, you’ll see a clear notice in the invite dialog. To add more, upgrade to a plan with a higher cap, or contact us about a Provlyn Bespoke arrangement.
Yes. As soon as you click Remove, the user can no longer access the vault on their next request, even if they have the vault URL bookmarked or saved in a previous email.
No. Only the vault owner can invite or remove members. Members can view, deposit, and deposit new versions, but they cannot manage who else has access.
When you share a file, Provlyn can embed into each recipient’s copy a repeating, low-opacity mark displaying that recipient’s email address together with the date and time of access. This serves as a leak-deterrent measure: should a watermarked copy be disclosed without authorisation, the embedded mark identifies the specific recipient to whom that copy was released. A distinct copy is generated for each recipient at the point of viewing or download, so that every copy can be individually attributed.
Watermarking is applied at your discretion. For downloadable document sharing it is optional and is selected on a per-share basis. For view-only sharing it is applied in all cases. It is never applied to the copies held in your own vault; it applies solely to files released to other parties.
Watermarking is available for PDF documents and for common image formats (JPEG, PNG, WebP, TIFF, and GIF). File types that cannot carry a visible mark, including audio and video, are delivered to the recipient in their original, unaltered form.
No. Your stored file is never modified. The watermark is applied to a separate copy generated for each recipient at the time of sharing; the original held in your vault remains exactly as it was deposited.
Yes. The recipient’s email address and time of access are visible within the copy they receive, and they persist within the file if it is saved, copied, or forwarded. This should be taken into account when determining what to share and with whom. You are responsible for ensuring that you are entitled to process each recipient’s email address in this manner; please refer to our Terms and Privacy Policy.
Every deposit is anchored to the Bitcoin blockchain via a protocol called OpenTimestamps. The cryptographic proof is created immediately when you deposit, but it takes between one and six hours for that proof to be permanently embedded in a Bitcoin block. During this window the deposit shows "Pending confirmation". Once confirmed, the deposit shows "Bitcoin confirmed" and the certificate can be independently verified by anyone using public infrastructure.
RFC 3161 is a recognised legal standard for proving a file existed at a specific time, and it’s issued instantly. The Bitcoin anchor is an additional layer of proof that does not depend on any single authority — even if the original timestamp authority disappeared, the Bitcoin proof would still stand. Provlyn deposits include both so that you never have to rely on any single party.
Yes. The certificate PDF you download is fully self-contained. It includes the RFC 3161 timestamp token signed by a public timestamping authority, and the OpenTimestamps Bitcoin proof. Both can be verified using free, open-source tools that have nothing to do with Provlyn. As long as Bitcoin and the timestamping authority’s certificate remain part of public infrastructure, your proof remains valid. Provlyn’s continued existence is not required.
The RFC 3161 timestamp remains independently valid even if the Bitcoin layer were ever lost. The blockchain anchor is an additional layer of certainty, not the only one. In practice Bitcoin failing in any short horizon is highly unlikely — it’s secured by approximately 800 exahashes per second of computing power maintained by tens of thousands of independent nodes globally — but the architecture does not depend on Bitcoin alone.
No, for several reasons working together. To forge the timestamp, an attacker would need to compromise a qualified timestamping authority’s signing key, which is held in hardware security modules under audited policies. To substitute a different file with the same hash, an attacker would need to break SHA-256 — currently estimated to require computing resources that won’t be available until post-quantum computing matures around 2040 or later. To backdate a deposit, an attacker would need to rewrite Bitcoin’s history, which is detected within minutes by every Bitcoin node globally and would cost billions of dollars to attempt. And Provlyn itself cannot forge a deposit, because the TSA signature and Bitcoin anchor are produced by external systems that Provlyn does not control.
A qualified eIDAS timestamp is issued by a Qualified Trust Service Provider listed on an EU trusted list, and carries the presumption of accuracy under Article 41 of Regulation (EU) 910/2014. Provlyn applies qualified eIDAS in two contexts: automatically to your daily access log on every paid plan, and optionally per deposit when you want that extra layer. For the full definition, the statutory text, and how recognition works across the EU, EEA, UK and US, see our reference page on what a qualified electronic timestamp is.
Qualified electronic timestamp: Articles 41 and 42 explained →
For the vast majority of evidence purposes, yes it is. SHA-256 hashing, RFC 3161 timestamping, and Bitcoin blockchain anchoring together produce a cryptographic chain of custody that is widely accepted as evidence in UK, EU, and US courts. eIDAS adds one specific procedural advantage — the Article 41 legal presumption — inside EU member states. It is not a replacement for the free stack; it is an optional fourth layer on top of it.
Blockchain timestamp or qualified timestamp: what each proves →
Provlyn uses AlfaTrust Certification S.A. (AlfaSign brand), a Qualified Trust Service Provider listed on the EU Trusted List. The architecture is provider-agnostic so Provlyn can add or rotate qualified providers without disrupting your existing evidence.
Yes. The qualified timestamp is a standard RFC 3161 token. You can verify it using any compliant tool, including OpenSSL or commercial signature verification software. The token is independent of Provlyn — your evidence does not depend on us remaining online.
When you upload a file, Provlyn shows a checkbox asking whether to apply qualified eIDAS to that deposit. Off by default — the free triple anchor applies regardless. Each per-deposit application uses one stamp: inside a VC Data Room it draws from that room’s included allocation first, otherwise from your monthly allowance, then from any standalone packages you have bought.
No. Monthly plan allowance resets to its full amount on the 1st of every calendar month, and unused monthly stamps do not roll over. If you need stamps that persist beyond the month, buy a standalone package — those roll over for 12 months from the date of purchase. Your monthly allowance is always used first, so you never expire a standalone stamp early through bad ordering.
VC Data Rooms work differently: each room includes a fixed allocation of qualified stamps for the room’s lifetime rather than a monthly allowance, so they are not reset on the 1st. When a room’s included stamps are used up, deposits draw on any standalone packages you have bought.
Each paid plan includes a monthly allowance of qualified eIDAS stamps: 10 on Creator, 25 on Founder, 50 on Scale, 50 on Music Pro, and 200 on Music Studio. The Starter plan includes no monthly allowance. Where additional stamps are required, standalone packages are available: 25 stamps for $7.99, 100 for $25, 500 for $99, 1,000 for $179, and 5,000 for $749. Your monthly allowance is always consumed before any purchased stamps, and purchased stamps remain valid for twelve months from the date of purchase. The daily access-log timestamp is included at no additional charge on every paid plan.
The cryptographic mechanisms Provlyn uses are recognised in evidence law across multiple jurisdictions. The RFC 3161 timestamp is the same legal mechanism that backs qualified electronic signatures under EU regulation. The Bitcoin anchor adds an independent, public layer of evidence that does not rely on any single authority. Whether a specific Provlyn certificate is accepted in a specific case depends on the court, the type of dispute, and how the evidence is presented — but the underlying proof is built on standards that courts have repeatedly recognised. Provlyn is not a law firm and certificates should be presented as part of a wider evidentiary package put together with proper legal advice.
eIDAS is the EU regulation (910/2014) governing electronic identification, signatures, seals and timestamps. Under Article 41, a qualified electronic timestamp enjoys a presumption of the accuracy of the date and time it indicates and of the integrity of the data bound to them, which shifts the burden of proof onto whoever disputes it. The UK retains an equivalent framework, and the mechanism is recognised on similar terms in Switzerland and Singapore, though the US has no equivalent statutory presumption. When you deposit a file with Provlyn, the RFC 3161 timestamp portion is built on this framework. Our reference page sets out Articles 41 and 42 in full.
Qualified electronic timestamp: Articles 41 and 42 explained →
A Provlyn deposit can record that the bytes of a will document existed at a specific date and have not been altered since. It does not replace the formal witnessing requirements under the Wills Act 1837. Use Provlyn alongside the traditional witnessing process — the timestamp adds an additional layer of evidence that the document a court is reviewing is the document that was witnessed, not something altered afterwards.
The mechanisms Provlyn uses are recognised under: eIDAS in the EU, the Electronic Communications Act 2000 and retained UK eIDAS in the UK, the Federal Rules of Evidence 901 and 902 plus UETA and ESIGN in the US, ZertES in Switzerland, and the Electronic Transactions Act in Singapore. The Bitcoin anchor is jurisdiction-neutral — it’s verifiable anywhere there is internet access. In jurisdictions with specific evidentiary requirements such as China’s qualified electronic data standard under recent Civil Procedure Law amendments, local legal advice is required. Provlyn can supply technical attestations to support such proceedings.
In most cases, Provlyn does not replace a notary — they serve different purposes. A notary public verifies the identity of the person signing a document; Provlyn proves the document existed at a specific moment. For routine evidence of when something existed and that it has not been altered, Provlyn is faster, cheaper, and globally verifiable. For acts that civil law specifically requires a notary for — certain property transfers, some company formations, certain affidavits in specific jurisdictions — a notary is still required. The two are complementary, not substitutes.
Standard plans are built around documents, code, and smaller files — the typical use case is a founder, engineer, lawyer, or business protecting intellectual property as it’s being created. Files are stored in your vault and counted against a storage quota. Music plans are built around the workflow of musicians, producers, and audio engineers, with higher deposit counts and the Protect only mode that lets you create cryptographic proof of very large session files without uploading them.
No. Prices shown on the site are in USD and exclude local taxes. Tax is calculated and added at checkout based on your billing location. The invoice you receive shows the subtotal, the tax, and the final amount paid separately.
Yes. Upgrades within the same family — for example Starter to Creator, or Music Pro to Music Studio — happen immediately, with a prorated charge for the remainder of your current billing period. Downgrades within the same family are scheduled to take effect at your next renewal, so you keep what you’ve already paid for. Switching between families (Standard to Music or vice versa) involves a checkout for the new plan; your old plan stays active until the new one is paid for.
In all cases, your existing vaults, deposits, and certificates are preserved when you change plan. Your data is tied to your account, not to a specific plan.
New accounts get a 7-day free trial. During the trial you can create a vault, deposit files, and generate certificates exactly as a paying customer would. At the end of the trial you choose a plan to keep using Provlyn. If you don’t subscribe, your access ends but past certificates remain verifiable through the public Bitcoin anchor.
Cancellation is scheduled — your subscription remains active until the end of the billing period you’ve already paid for. After that, your account enters a retention window during which your files are preserved but not accessible. If you resubscribe during retention, everything returns intact.
After cancellation takes effect, your files enter a 30-day retention period. During retention your vault is locked but the files are not deleted. If you change your mind and resubscribe, your full vault is restored as it was. If retention expires without resubscribing, the files are permanently deleted.
The file content stored in your vault is permanently deleted. However, the cryptographic record of each deposit — the SHA-256 hash, the RFC 3161 timestamp token, the OpenTimestamps Bitcoin proof, and the certificate ID — is retained indefinitely. This means any certificate you previously generated and downloaded remains verifiable forever, even though Provlyn no longer holds the file itself.
Standard plans (Starter, Creator, Founder, and Scale) do not stop you when you reach your monthly deposit allowance. You may continue to deposit, with a small recurring add-on covering the additional capacity: the first add-on provides a further 10 deposits per month (and 500 MB of storage) for an additional $1.99 per month, and each subsequent add-on provides a further 20 deposits per month (and 1 GB of storage) for an additional $2.99 per month. Add-ons may be stacked as required. When upgrading your plan — including moving to a Music plan — would cost less than continuing to add capacity, this is suggested to you at that point. You may upgrade at any time. Your monthly deposit allowance resets on the first day of each calendar month.
Yes. On Music Pro and Music Studio you may continue to deposit beyond your monthly allowance, with a flat monthly charge applied for the usage band into which you fall. On Music Pro this is an additional $10 per month for 501 to 1,000 deposits and $20 per month for 1,001 to 1,500; beyond 1,500 deposits, Music Studio is the more economical plan. On Music Studio it is an additional $15 per month for 2,001 to 3,000 deposits and $30 per month for 3,001 to 4,000; beyond 4,000 deposits, a Provlyn Bespoke arrangement applies. Your usage is reviewed at each renewal, and any added capacity you no longer require is removed.
To store files beyond your plan allowance, you may purchase a standalone storage add-on for the band into which your total storage falls: $4.99 per month up to 5 GB, $9.99 per month up to 20 GB, and $19.99 per month up to 50 GB. Total storage above 50 GB is provided under a Provlyn Bespoke arrangement. You are charged for a single band only; bands do not accumulate. The add-on is charged at the annual rate, applied pro rata for the remainder of your current billing period, and is included in subsequent renewals. It is removed automatically if your storage later returns to within your plan allowance. Files that would take you over your current storage limit cannot be uploaded until the necessary storage is added.
No. Limits apply only to new actions. All material you have already deposited — including your files, cryptographic hashes, certificates, and blockchain anchors — remains unaffected and fully verifiable.
A Deal Room is a time-limited, invite-only vault built for venture capital due diligence and similar processes where multiple parties need controlled access to sensitive documents. Every file deposited into a Deal Room is cryptographically timestamped and anchored to the Bitcoin blockchain, exactly like a normal Provlyn deposit — but the access model is different. Deal Rooms are paid per room, not per subscription.
A normal vault is part of your Provlyn subscription, lives indefinitely while your account is active, and uses the member model for ongoing collaboration. A Deal Room is a separate paid product, lasts 6 months from activation, supports unlimited invited recipients who only need to verify their email address (no Provlyn account required), and gives the owner a full audit trail of every recipient’s actions. Deal Rooms are designed around a specific transaction or process; vaults are designed around ongoing IP protection.
Six months from the date of payment. You can renew at any time before or after expiry — renewing extends the room by another 6 months. While expired, the room is locked: the owner can still see the files exist and can renew, but recipients cannot access content until renewal.
Yes, by default. Every download is logged in the audit trail with the recipient’s verified email address, IP address, and the exact file and time. If a deal goes south, you have a complete record of who saw what and when.
Every action is logged: opening the room, viewing the room contents, opening a specific file, downloading. Each log entry records the recipient’s verified email, their IP address, the action taken, and the precise timestamp. The full log is exportable as a PDF for inclusion in legal filings or internal records.
Files you store in your vault are held on enterprise-grade cloud infrastructure in Europe. Metadata, access logs, and account information are held in a managed Postgres database, also in Europe. Data is encrypted at rest and in transit. Provlyn is a UK company (Provlyn Ltd, Company No. 17185877) and processes data under UK GDPR.
Provlyn’s systems process your file only to do what you ask. Its fingerprint (its SHA-256 hash) is calculated in your browser, and that fingerprint is what gets timestamped and anchored. If you use Protect only mode, the file itself never leaves your device. If you use Protect and save, the file is uploaded to your vault and stored encrypted at rest. Provlyn’s systems then process it only for things you ask for: checking on upload that it matches the fingerprint your browser calculated, adding a recipient’s watermark when you share with watermarking on, and rendering pages for read-only viewing. Provlyn staff do not open, index or review your files as part of normal operations.
No. We do not sell, rent, or share user data with third parties for marketing or any other commercial purpose. We do not run advertising on Provlyn products. The full position is set out in our Privacy Policy.
No. The cryptographic proof of each deposit is anchored to the Bitcoin blockchain and signed by an independent timestamping authority — neither of which Provlyn controls. Once a deposit has been timestamped and anchored, even Provlyn cannot alter the hash, the time, or the existence of the record without that change being immediately and publicly detectable. This is by design: the entire value of Provlyn rests on the proof being independent of us.
Only you, people you’ve invited as members of the vault, and recipients you’ve shared a vault or file with. Provlyn staff do not access customer files as part of normal operations. In rare cases, for example to comply with a court order, or with your written consent for support, access may be required. Every download, and every page viewed, through the Provlyn application is recorded in your vault’s access log, which is sealed daily with a qualified timestamp. Access made directly on our storage infrastructure is not yet recorded there; we are building that now, and this answer will be updated when it is in place.
You can download every certificate you’ve generated from within your vaults at any time, and you can download files stored in Protect and save mode from each deposit individually. To delete your account and all associated data, contact us through the support address on the site — we’ll confirm the request and process the deletion. Note that the cryptographic record of each deposit (hash, timestamp, Bitcoin anchor) persists indefinitely, by design, so that certificates remain verifiable; the file content and account metadata can be deleted on request.
Yes. Provlyn operates as a data controller under UK GDPR and EU GDPR for account data, and as a data processor for the file content you choose to store. You have the standard data subject rights — access, rectification, erasure, portability, restriction, and objection. To exercise any of these, contact us through the support address on the site.
Bitcoin confirmation typically completes within 1-6 hours, but congestion on the Bitcoin network occasionally extends this. If you’re past the 6-hour window and still pending, wait another few hours before getting in touch. The deposit itself is not affected — the RFC 3161 timestamp portion is already in place and legally valid regardless of Bitcoin confirmation status. If it’s been more than 24 hours, contact support and we’ll investigate.
Deposits are not deletable, by design. The whole value of Provlyn is that records are permanent and tamper-evident — if deposits could be deleted, the system would no longer be a reliable record. If you uploaded the wrong file, you can deposit the correct version on top of it as a further new version. The old (incorrect) version remains in the chain but is clearly marked as an earlier version. Anyone reviewing the chain can see the sequence of what was deposited and when.
The most common cause is that the file has been modified since you deposited it. Even a tiny change — a metadata update, a re-save in a different format, a copy that’s been through a document converter — produces a completely different SHA-256 hash and will not match. If you have an unmodified copy of the original file, verify with that instead. If you only have the modified version, the cryptographic proof of the original still stands; you just can’t bind this particular copy to it.
Refresh the page first — occasionally the deposit succeeds but the list doesn’t refresh fast enough. If it’s still missing, check your search filter is cleared and the vault scope is set correctly. If the deposit succeeded, you also have the certificate on your machine and can use the certificate ID to verify it exists — that’s the definitive answer regardless of UI state.
Use the search box at the top of the vault page. Search by filename, SHA-256 hash, or certificate ID, and toggle the scope to "All my vaults" if you’re not sure which vault it was in. If you have a partial filename, the search matches substrings, so even a fragment of the name should find it.
This is a Microsoft Edge browser behaviour, not a Provlyn issue. Edge automatically routes downloads of Microsoft Office files through its online preview service, which opens in a separate tab while the actual download proceeds in the background. You can disable this in Edge’s settings under Downloads, or simply close the preview tab. Other browsers (Chrome, Firefox, Safari) don’t do this.
Can't find what you're looking for?
Get in touch →