Vendor review
Last updated November 15, 2026
Before a firm puts client information into new software, someone has to review the vendor: a partner, an IT consultant, sometimes the firm's insurer. These are the questions that review usually asks, answered plainly, including where the answer is no. Print this page or send the link.
Every answer restates what our other pages already say and links to the detail. It is a disclosure, not a contract and not a certification.
Has Fylely had an independent security audit, such as SOC 2 or ISO 27001?
No. Fylely holds no security certification and has not had an independent audit, and no outside firm has been engaged to test it for weaknesses (a penetration test). What it does to protect your records is set out on the Security page, so you can judge it for yourself. Instead of a yearly audit, Fylely checks itself against the live service every day, making the requests a signed-out stranger could make to every table in its database, and shows the latest passing result on that page.
Are the companies that hold our data audited?
Yes, each by its own auditors. As each states on its own website, checked on October 28, 2026: Supabase (database, sign-in and file storage) holds a SOC 2 Type 2 report and ISO 27001 certification (its page); Vercel (application hosting) holds a SOC 2 Type 2 attestation and ISO 27001:2022 certification (its page); Resend (email delivery) holds a SOC 2 Type II report (its page); Stripe (payments) holds PCI Service Provider Level 1 certification and SOC 1 and SOC 2 Type II reports (its page); Anthropic (Claude, only if the firm owner switches it on) holds SOC 2 Type I and Type II reports, and ISO 27001:2022 and ISO/IEC 42001:2023 certification (its page). Those audits cover each company's own systems. They say nothing about Fylely's own code and settings, which no one outside Fylely has audited or tested, as the answer above says.
Where is our data kept, and who else handles it?
The database and uploaded files are held by Supabase in the United States (US East, Northern Virginia), for every firm: there is no choice of region, so a firm in Canada or elsewhere has its records held there too. The application is served by Vercel. Email goes out through Resend, payments through Stripe. Microsoft is involved only if someone at your firm connects their own Outlook account, Google only if someone connects their own Gmail or Google Calendar or installs Fylely for Gmail (which reads only the email they have open, when they press File this email, and nothing else in the mailbox), Clio only if someone connects their own Clio account, Zoom only if someone connects their own Zoom account (Zoom receives each meeting's title, time and length, nothing else from the file), and Intuit only if the firm owner connects the firm's QuickBooks Online company, Xero only if the firm owner connects the firm's Xero organisation, Plaid only if the firm owner connects the firm's bank (the owner signs in to the bank with Plaid or the bank, never with Fylely, and Fylely receives the shared accounts' names, last digits, types, balances and transactions), and Twilio only if the firm owner sets up texting, with a number from Fylely or the firm's own Twilio account, to text clients and receive their replies. Anthropic is involved only if the firm owner switches on Claude in Settings → AI & privacy, and then only with what someone asks Claude about. CourtListener (Free Law Project) and CanLII are involved only if the firm owner switches on Citation check, and then receive only the case citations found in a document or draft someone checks, never a name or the text around them. The Sub-processors page lists each one and what it receives.
Is it encrypted?
Yes. All traffic is encrypted in transit with TLS, and the database and documents are encrypted at rest by the hosting provider.
Are uploaded files scanned for viruses?
No. Fylely does not scan files for viruses. It does check them: storage refuses any file over 25MB; when someone at your firm adds a file to a matter, archives, programs, scripts and web pages are refused, and a file stored as a type a browser would run is removed; and a file from a client is removed if its first bytes are not the kind of file its name says. Treat a file from someone you do not know as you would an email attachment. The Security page sets out each check.
Can another firm see our records?
No. Each firm's records are separated by row-level security in the database itself, not only by the application, and uploaded files are stored under the firm that owns them with the same rule.
How do people sign in?
With a password and, if turned on, a second step: a six-digit code by email, a code from an authenticator app, or a passkey (the device's own fingerprint, face or PIN unlock). The firm owner can require the second step for everyone and set how long an idle session lasts, from 15 minutes to 4 hours. Repeated wrong passwords lock the account for a time.
Can staff sign in with our Microsoft or Google accounts (single sign-on)?
Each person can, for themselves. Anyone can use their own Microsoft or Google account to sign in instead of their password, by linking it in Settings or by pressing Continue on the sign-in page; every other step they or the firm have turned on, such as a code or a passkey, is still asked for. The account's email address alone never signs anyone in: the first time, a six-digit code is emailed to the address on the Fylely account, and only that code connects it. After that the account is recognised by the provider's own id for that person. Linking one in Settings needs a sign-in within the last 15 minutes, and adding or removing one is emailed to the person and written to the security log. Fylely has no firm-wide single sign-on (SAML): the firm cannot require it or manage it from its Microsoft or Google admin console, and each person keeps their own Fylely password. Connecting Outlook, Gmail or Google Calendar links that mailbox or calendar to Fylely; it does not sign anyone in.
Can we limit what staff see?
Yes. Each team member has a role: attorney, paralegal, billing or read-only, or a custom role the firm owner names and chooses permissions for. A paralegal does not see invoices or trust; billing staff do not open matter files; read-only can look and change nothing. A matter can also be made private, for an ethical screen or any other reason: then only the owner and the colleagues listed on it can see it, the database enforces that, and a conflict check run by a screened colleague says the private matter was not searched. The guide by role sets out what each role can do, and the Security page what a private matter hides.
Is there a record of who did what?
Yes. Changes to estate and guardianship records are written to an activity log by the database. A separate security log records sign-ins, refused sign-ins, exports and changes to sign-in settings, the team and share links; the owner can read it in Settings, and entries are kept for 400 days.
Who at Fylely can see our records?
Fylely's operator console has no page that shows a matter. It shows each firm's account details, counts such as how many matters a firm has, the security log, and what a firm sends us itself: support messages, bug reports, files sent for an import and requests to extend a trial. A test fails if the console starts reading another table. It needs each operator's own account, password and authenticator code, and administrative changes are logged under that person's name. Our servers also hold a key that can read the whole database, for scheduled work such as reminders; today one person, Fylely's founder, has access to the accounts that hold it. We look at a firm's records only when the firm asks us to, to keep the service secure, or when the law requires it.
Is our information sent to an AI service?
Not unless the firm owner switches it on. Ask's built-in mode, drafted replies and document descriptions are worked out inside Fylely from your own records and send nothing anywhere. The owner can switch on Claude (Anthropic) in Settings → AI & privacy; from then on, what someone at the firm asks Claude about is sent to Anthropic when they ask, and nothing else: for a question in Ask Claude, the question and the records Claude reads to answer it, which are only the records the asking person's role lets them see and never a document marked privileged or internal; for “Draft with Claude”, that family conversation and the matter's coming dates; for “Summarise” and “Fill from this document”, that one document; for “Build a timeline from records”, the documents the person picks, a few pages at a time; for “Read with Claude” on a bank statement, the pages of that one PDF or scan; for “Read with Claude” on the other side's statement on a family matter, the pages of that one document; for “Suggest wording”, each flagged time entry and the titles of that day's records on its matter, never the hourly rate or the amount billed; for “Describe the report you want”, what the person typed and the list of report columns their role may use, never the firm's records; for an attendance note drafted with Claude in court or meeting mode, that session's notes and transcript and the matter's name; for “Review against our positions”, that one contract's text and the firm's positions chosen; for “Draft with Claude” on a discovery request, that request's text, the facts recorded on the matter and the text of up to three of its documents the person ticks (never one marked privileged or internal, and not the documents’ names). Anthropic is on our sub-processors list, does not train on business data by default, and deletes it within 30 days unless the law or its usage policy needs it kept longer. Switching it on or off is on the security log.
Can our other software read our records?
Only if the firm owner sets it up. The owner can make an API key that reads matters, deadlines, contacts and invoices, and webhooks that send events to an address the owner chooses. A key cannot delete the firm's records. If the owner allows it (which needs an authenticator app or a passkey on the owner's account), a key can add and change contacts, open matters, add tasks and mark them done, log time and add notes, as the person who made it and within what their role allows, with each change logged against the key. If the owner allows it, a key can also add a new enquiry to the firm's intake queue, or add and remove webhooks of its own, which the owner can see and which go when the key does, or suggest a change (a task, deadline, hearing, time entry, note, draft invoice or document request) that waits for someone at the firm to add or decline it in Fylely, and nothing else. Only a fingerprint of a key is stored, and notes, messages, document contents and the trust ledger are not available through it. Each key or webhook made or removed, and each change to what a key may do, is on the security log. The owner can also connect an assistant the firm already has (an MCP connection at /api/mcp), by signing it in or with a key: it reads the same records with the same limits, can suggest changes only if the owner allows that connection to, can be disconnected in Settings, and Fylely sends nothing to that assistant.
How is client money in trust handled?
Each client has their own trust ledger, and the database refuses any entry that would take a client below zero. A reconciliation is done entry by entry against the bank statement and prints as a report with each client's balance on the statement date. A firm can keep more than one trust bank account, such as a pooled account and a separate one for a single client; each has its own client balances and its own reconciliation, and money a client holds in one cannot be paid out of another. Your bar or law society sets what your records must contain; check the report against its rules.
Can we get everything out?
Yes. The firm owner can download every record as spreadsheets or as one file, and every uploaded document as a ZIP, from Settings, at any time and without a paid plan.
What happens to our records if we stop paying, or if Fylely shuts down?
If your plan ends, your matters stay where they are and stay readable, and the exports keep working. If we ever stop offering Fylely, the Terms commit us to emailing every account owner at least 30 days before it is switched off, with export available throughout.
How is data deleted?
Closing the account deletes the firm, its records and its uploaded files. The deletion process sets out the exceptions: backups, retained security logs, legal obligations and copies other people have already received.
Are there backups, and how fast is recovery?
Not yet. Our database host, Supabase, takes daily backups only on its paid plans, and Fylely is on its free plan today; we are moving to a paid plan before launch. Our own nightly backup, encrypted and kept outside Supabase and Vercel, has failed every night since 1 October 2026. Until both are running, the only copies of your records are the ones you download. We do not promise a recovery time or a loss-free recovery window, and we publish a restore check only once one has been completed and measured; the Security page shows the current state. Keep your own copies using the exports if your firm's continuity plan needs them.
Is there a data-processing agreement?
Yes. Our data processing agreement sets out what we may do with the client information your firm enters and what we owe you about it, and it applies to every firm's account without anything to sign. If your firm wants a signed copy for its file, print it, sign it and email it to help@fylely.com, and we will return it countersigned. This page and the Sub-processors page are disclosures, not contracts.
Will you tell us if our records are breached?
Yes. If we find that someone without permission got into your firm's records, we will email your firm's account owner within 72 hours of confirming it, saying what was reached, when, and what we have done about it, and we will keep you updated as we learn more.
What support is there?
Phone, at 604-830-8371 (Pacific time), or we call you back; and email, at help@fylely.com. There is no support service level: we do not promise a response time or an uptime figure.
Who do we tell about a security concern?
Email cole@fylely.com; the same address is in our security.txt file. We will not take legal action against anyone who looks for a security problem in good faith, on the terms the Security page sets out. No system is perfectly secure and we do not promise absolute security, but we will tell you plainly what happened.