Capy Files · capyfiles.com/for-it · Updated 18 November 2026
For your IT department
What Capy Files sends, what it can’t, and what a roll-out takes. Every line here can be checked in a browser, and the steps are below.
In short
- Where files are worked on
- In the browser tab, on the person’s own device, by WebAssembly builds of open-source engines. The graphics card is used where the browser offers it.
- What is uploaded
- Nothing from a file: not its contents, not its name, nothing made from it. There is no server that could take one.
- What to install
- Nothing. No extension, no desktop agent, no admin rights.
- What to allow
- capyfiles.com over HTTPS. A tool page can’t connect to any other host, and the browser is what enforces that.
What crosses the network
This is all of it.
- The app itself
- Pages, scripts, WebAssembly and fonts, downloaded from capyfiles.com (hosted at Cloudflare) on a visit and kept by the browser afterwards, so the tools also work offline.
- AI models, OCR languages
- Downloaded from capyfiles.com the first time a tool needs one, then kept in the browser. A download to the device; nothing goes with the request.
- Sign-in
- Only for someone with an account. Google’s sign-in service (Firebase Authentication) handles it. From a tool page it is relayed through capyfiles.com, so tool pages never connect to Google themselves.
- Plan check
- While signed in, the sign-in token goes to capyfiles.com and the plan comes back. On the free plan, an AI run also sends how many files it will use, as a number.
- Usage counts
- To capyfiles.com: the name of a step (a page opened, a button pressed, a job finished) and of the tool, the step before it, and a two-letter country. No identifier, no IP address, nothing about files.
- Payment
- On the checkout pages only, by whoever buys. Stripe and Link take the payment; card details never reach us.
- Error report
- Only when someone clicks “Send report”: the tool, the browser version and the error message, with file names taken out.
None of these carries a file, a file’s name or anything made from one.
Check it yourself, in about five minutes
- 1Watch the requests
- Open capyfiles.com/compress-pdf with developer tools on the Network tab (F12). Type
method:POSTinto its filter and run the tool on a large file. No request is anywhere near the size of the file; click any that appear to see what they carried. - 2Read the policy
- Click the page’s own request and find the
Content-Security-Policyresponse header. Itsconnect-srcis'self' blob: data:: scripts on the page may reach capyfiles.com and addresses inside the page, nothing else. - 3Pull the cable
- Use the tool once, switch the network off, then reload the page and run it again. It works: the file never needed to go anywhere.
- 4Close the firewall
- On a test machine, allow capyfiles.com at the proxy and nothing else. The tools keep working.
What still rests on trust is the code we serve: it loads from capyfiles.com, and a version that sent files anywhere would show up in step 1, to anyone who looks. The security page shows the full header, fetched live, and every host the sign-in and checkout pages may reach.
Rolling it out
- Browsers
- Chrome and Edge 113 or newer, Firefox 115 or newer, Safari 16.4 or newer, on Windows, macOS, Linux, ChromeOS, iOS and Android.
- Browser settings
- JavaScript and WebAssembly have to be allowed for capyfiles.com. A hardened profile that switches WebAssembly off needs an exception for this one site.
- Network
- capyfiles.com on port 443 is enough for the tools. Signing in also needs Google’s sign-in hosts and paying needs Stripe’s; the security page lists both.
- Storage
- AI tools keep their model in the browser’s storage: tens of megabytes for most, several hundred for the largest. Clearing site data removes them, and they download again when needed.
- Memory
- Files are worked on in the tab’s memory. When the files picked are large for the device, the tool says so before it starts instead of failing halfway.
- As an app
- Optional. The browser’s own “Install” puts it on the taskbar or dock: the same site in its own window, with nothing installed outside the browser profile.
- Updates
- The app updates itself when a page loads. There is nothing to package or patch.
- Seats
- From 2 seats, €5.99 a seat a month. Whoever pays lists work email addresses on their account page. Each person signs in with that address, by a link emailed to them or with Google, and a seat moves to someone else when people change.
What we hold
- Files
- Nothing, not for a moment. They never arrive.
- Professional secrecy
- Law firms, tax advisers and practices: since files never reach us, nothing a duty of confidentiality covers passes to us, so there is no access of ours to agree terms for.
- An account
- An email address and an account ID, the plan and its dates.
- A team
- The addresses that hold a seat, whether each has signed in, and which account pays. An address is deleted when its seat is taken back, and at the latest 12 months after the team ends.
- Payments
- Taken by Link, Stripe’s merchant of record. We see the plan, the billing country and whether it was paid, never card details.
- Where
- Hosting and our database are at Cloudflare, sign-in at Google Firebase Authentication, our emails go out through Resend. The privacy policy names each one and what it gets.
What it doesn’t do
- Single sign-on
- No SAML and no SCIM: nothing connects to your identity provider. People sign in with an emailed link or with Google.
- Admin console
- No audit log and no usage reports. Whoever pays sees which addresses hold a seat and whether each has signed in, and nothing more: not anyone’s files, and not what anyone does with them.
- Self-hosting
- No self-hosted version and no offline installer. The app loads from capyfiles.com.
- A compromised device
- Malware, or a browser extension allowed to read every page, can read what any page reads. Files here are as safe as the device they are on.
Who is behind it
Capy Files is made by Devinfi OOD (Девинфи ООД), a company registered in Burgas, Bulgaria, in the European Union (EIK 208828839). For a security question or a report, write to hello@capyfiles.com with “Security” in the subject; the same details are in security.txt.