Sub-processors
Last updated November 15, 2026
To run Fylely we rely on a small number of third-party services. This page lists them and what each one handles, because a firm deciding whether to put privileged client information into software should be able to see who else touches it without having to ask.
This page is a factual disclosure, not a contract. It is not a data-processing agreement, and nothing here asserts a certification or audit on our part or theirs. Read it alongside our Privacy Policy.
1. Current Sub-processors
| Service | What it does | What it handles |
|---|---|---|
| Supabase | Database, authentication, and file storageUS East (Northern Virginia), AWS us-east-1; verified for this deployment. | Everything you enter: matters, clients, contacts, deadlines, documents, notes, time and billing records, and your account credentials. |
| Vercel | Application hosting and content deliveryGlobal edge network. | Serves the application and processes requests in transit. Request logs may include IP address and page paths. Application processing and diagnostic logs may contain data needed to serve a request; avoid placing client details in URLs. |
| Resend | Email delivery, and receiving email you send inDetermined by Resend. | The content of emails the Service sends on your instruction — sign-in codes, password resets, deadline digests, and any client email or status update you choose to send, the notice that tells a person named on a matter a message is waiting (never the message itself), the confirmation, reminder or cancellation of a consultation someone booked on a firm’s booking page (the firm’s name and the time, never what they wrote), and a link a firm sends its client to book a meeting on their matter — together with the recipient address. If your firm turns on a matter’s email address, or a person turns on their own file-by-email address: the emails sent to those addresses, with their attachments, which Resend receives and passes to the Service. |
| Stripe | Subscription billing for your firm’s own Fylely plan, and card payments from your clients if you turn on online paymentsDetermined by Stripe. | For your plan: your firm’s billing contact and payment details. If you connect your own Stripe account so clients can pay invoices online, each payment sends Stripe the invoice number, the amount, your firm’s name and the matter’s name, and the person paying gives Stripe their own card or bank details and contact details. A refund made from an invoice in Fylely sends Stripe the payment and the amount. Nothing else from a matter is sent. If you also turn on autopay, a client who signs the authorization saves their card, or a bank account if your firm allows one, on Stripe’s own page, on your firm’s Stripe account: Stripe receives that person’s name and email address and your firm’s name, and each later charge sends the invoice number and the amount. If you do not turn on online payments, no client or matter information is sent to Stripe. Stripe handles card and bank data directly; we never receive or store card or bank account numbers. |
| Microsoft | Outlook calendar, mailbox and (if allowed) OneDrive access, only if you connect it; signing in, only if you link itDetermined by Microsoft and by your own Microsoft tenant. | Nothing, unless a person at your firm connects their Outlook account, or links their Microsoft account for signing in, in Settings. A Microsoft account linked for signing in tells the Service only an id for that account and its email address, each time the person signs in with it. An Outlook connection: the hearings, court dates and deadlines from your matters are written into that person’s calendar (and, if the firm turns on video links for booked consultations and this is the firm owner, each confirmed consultation is added as a Teams meeting, with the prospect’s name and time), and the Service can read messages in that mailbox to file them against a matter and send messages the person asks it to send. If the person also allows OneDrive, the Service can list and read their OneDrive files, and copies a file into a matter only when they choose it. If they use Edit in Word, Microsoft grants the Service write access to their OneDrive; it is used only to place a copy of that document in a Fylely folder in their OneDrive and read it back, and the Service does not change or delete their other files. If they add Teams chat, the Service copies the names of the people in their own one-to-one and group Teams chats and the text of those messages (not files or pictures), visible only to them and deleted when they turn Teams chat off or disconnect, and sends a reply to a chat when they press Send. This is the person’s own Microsoft account and the mail already lives with Microsoft; the connection lets Fylely read and write it, and it can be removed from Settings at any time. Nobody else at the firm can see or use another person’s connection. |
| Sending from Gmail, and matter dates in Google Calendar, only if you connect them; signing in, only if you link it; the Fylely for Gmail panel, only if you install itDetermined by Google and by your own Google account. | Nothing, unless a person at your firm connects their Gmail account or their Google Calendar, or links their Google account for signing in, in Settings, or installs Fylely for Gmail. Signing in: Google tells the Service only an id for that account and its email address, each time the person signs in with it. Gmail: the Service sends the messages that person asks it to send, from their Gmail address, and Google tells the Service that address. The Service cannot read the mailbox, and nothing is sent automatically. Fylely for Gmail, a separate add-on installed in Gmail: Google shows a Fylely panel beside the email the person has open. When they press File this email, the Service reads that one email (Google’s permission covers only the open email and its conversation, while the add-on runs) and sends Google the panel to show: the names and file numbers of the matters it offers, and afterwards what was filed. The Service does not list, search or read the rest of the mailbox. To connect the panel, the person signs in to that Google account in Google’s own window, and Google tells the Service only that account’s id and verified address, to check it is the account the panel was opened in. Google Calendar, a separate connection: the hearings, court dates, deadlines and dated tasks from your matters are written into that person’s primary calendar, and changed or removed when the matter’s dates change; if the firm turns on Google Meet links for booked consultations and this is the firm owner, each confirmed consultation is added with a Meet, with the prospect’s name and time. The Service does not read the person’s other events. Each connection can be removed from Settings at any time. Nobody else at the firm can see or use another person’s connection. | |
| Anthropic | Claude, the AI in Fylely, only if the firm owner switches it onDetermined by Anthropic. | Nothing, unless the firm owner switches on Claude in Settings → AI & privacy. If they do, a request goes to Anthropic only when someone at the firm asks, or, if the owner has also switched on the website chat, when a prospective client sends a message in that chat: for a question in Ask Claude, the question, the conversation so far and the records Claude reads to answer it: matters, deadlines, contacts and invoice totals and, as far as the asking person’s role allows, matter notes, family messages, the text of documents (never one marked privileged or internal), time entries and trust balances; for “Draft with Claude”, that one family conversation, the matter’s name and its coming hearings and deadlines; for “Summarise” and “Fill from this document”, the text of that one document and its file name; for “Build a timeline from records”, the text of the documents the person picks, a few pages at a time, with their file names and page numbers; for “Read with Claude” on a bank statement, after the person is told so and presses it, each page of that one PDF or scan as the file has it, whatever is printed on the page, and its file name; for “Read with Claude” on the other side’s statement on a family matter, each page of that one document on the matter as the file has it, and its file name; for “Write with Claude”, what the person typed and the matter’s facts listed under the draft: its details, its people (with an address only for the person written to), its coming hearings and deadlines and, on an estate, accounts by institution and last four digits, assets, claims and ledger totals, never notes, documents or a full account number; for “Suggest wording” in pre-bill review, each flagged time entry’s description, date and length, the matter’s name, the first name of the person who logged it where Fylely holds one, and the titles and first lines of that day’s records on the matter, never the hourly rate or the amount billed; for “Describe the report you want” on Reports, 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, the matter’s name, that session’s title and times, its notes and its transcript; for “Review against our positions” on a contract, the text of that one document (never one marked privileged or internal; not its file name), the side the firm acts for and the firm’s positions chosen for the review; 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); and, only if the owner has also switched on the website chat on the firm’s intake form, each message a prospective client types in that chat, with the firm’s name, the area of law they picked and the firm’s own questions, never anything from the firm’s records. Claude’s answer comes back to the person who asked and is sent only if they choose; where the request concerns a matter, a record of it stays with the firm on that matter. In the website chat, Claude’s reply is shown to the prospective client straight away, after Fylely’s own checks, and the conversation is kept for the firm with the enquiry, or deleted a day after the last message if it is never sent. By default Anthropic does not train its models on what businesses send it, and deletes requests and answers within 30 days unless the law or its usage policy needs them kept longer. The owner can switch Claude off at any time; nothing is sent after that. |
| Intuit | QuickBooks Online, only if the firm owner connects itDetermined by Intuit. | Nothing, unless the firm owner connects the firm’s QuickBooks Online company in Settings. If they do: for each invoice the firm sends, the client’s name and email address (as a QuickBooks customer), the invoice’s number, dates, matter name and its fees and costs totals; and for each payment recorded against it, the amount, date, method and reference. Nothing else from a matter is sent. Fylely reads back only what doing this needs: the company’s name and home currency, its products and services, whether it numbers invoices itself, whether a customer of the same name already exists, and the version number QuickBooks requires before an invoice it was sent can be voided or a payment deleted. The records go into the firm’s own QuickBooks company, which the firm holds under its own agreement with Intuit. The owner can disconnect at any time; what is already in QuickBooks stays there. |
| Xero | Xero accounting, only if the firm owner connects itDetermined by Xero. | Nothing, unless the firm owner connects the firm’s Xero organisation under Accounting. If they do: for each invoice the firm sends, the client’s name and email address (as a Xero contact), the invoice’s number (as its reference), dates, matter name, a link back to the invoice in Fylely, and its fees and costs totals; and for each payment recorded against it, the amount, date, method and reference. Nothing else from a matter is sent. Fylely reads back only what doing this needs: the organisation’s name, base currency and short code, its chart of accounts, whether a contact of the same name already exists, and whether Fylely already created an invoice with the same reference. The records go into the firm’s own Xero organisation, which the firm holds under its own agreement with Xero. The owner can disconnect at any time; what is already in Xero stays there. |
| Plaid | Reading the firm’s bank accounts for the bank feed, only if the firm owner connects a bankDetermined by Plaid. | Nothing, unless the firm owner connects a bank under Connect your bank in Settings → Connections. If they do, the owner signs in to the bank in Plaid’s window, or at the bank’s own website, and chooses which accounts to share: Fylely never sees or stores that sign-in. Fylely sends Plaid an id for the firm (never a name), its requests, and the credential Plaid issued for that connection, and nothing from a matter, a client or a document. Plaid sends Fylely, for each account shared, its name, the last digits of its number, its type and its balance, and its transactions (date, amount, the bank’s description and, where Plaid recognises one, the merchant’s name) for the last 180 days and from then on. Fylely keeps the accounts and transactions to suggest which invoice payment or trust entry each line is, for someone at the firm to confirm; it does not keep balances, and it never moves money or records, changes or reconciles anything on its own. What Plaid does with the bank data it handles is set out in Plaid’s own End User Privacy Policy. The owner can disconnect at any time: the connection is ended at Plaid, and its accounts and transactions are deleted from Fylely. |
| Clio (Themis Solutions Inc.) | Working alongside Clio, only if a person at your firm connects their own Clio accountThe Clio region of the firm’s own account (United States, Canada, Europe or Australia). | Nothing, unless a person at your firm connects their own Clio account in Settings. Reading: the firm’s matters (number, description, client, practice area, responsible lawyer, status and dates) and contacts (name, type, email address, phone number, address and whether each is a client) are read from Clio only when that person presses Fetch from Clio on the import page, and nothing is saved until they confirm the import; the Service also reads their Clio name, email address and calendar. Sending, only if that person turns it on: the firm’s court dates, deadlines and limitation dates, with the matter’s name and the date’s description, go into their Clio calendar, on the Clio matter with the same matter number; and the time entries they record from then on (date, length, description, whether billable and any rate of its own) go to the Clio matter with the same matter number. Changed and deleted dates and entries are changed and deleted in Clio too. The records go into the firm’s own Clio account, which the firm holds under its own agreement with Clio. The person can disconnect at any time; what is already in Clio stays there. Nobody else at the firm can see or use another person’s connection. |
| Zoom (Zoom Communications, Inc.) | Video meetings, only if a person at your firm connects their own Zoom accountDetermined by Zoom and the person’s own Zoom account. | Nothing, unless a person at your firm connects their own Zoom account in Settings → Connections and chooses Zoom: the firm owner for booked consultations, or anyone for a meeting they book on a matter. Zoom tells the Service that person’s Zoom user id and email address. For each meeting, the Service sends Zoom a title, the start time, the length and the time zone. For a booked consultation the title is “Consultation with” and the prospect’s name; for a meeting booked on a matter, it is the meeting’s title and the matter’s name. Nothing else from the booking, the matter or the firm’s records is sent, and nobody is invited through Zoom. Zoom sends back the meeting’s id and join link, which are kept with the booking or meeting and sent to the people in it. When the meeting is moved or cancelled in Fylely, it is moved or deleted at Zoom. The meeting itself, and anything recorded in it, is held in that person’s own Zoom account under their own agreement with Zoom. The person can disconnect at any time, which ends the access at Zoom and deletes it from Fylely, as does removing Fylely in Zoom; meetings already made stay in their Zoom account. Nobody else at the firm can see or use another person’s connection. |
| Twilio | Text messages to clients, only if the firm owner sets up textingDetermined by Twilio, and for the firm’s own account by that account. | Nothing, unless the firm owner sets up texting in Settings, either with a number from Fylely or by connecting the firm’s own Twilio account. With a number from Fylely, Fylely opens a Twilio subaccount for the firm under Fylely’s own Twilio account, buys a toll-free number in it, and sends Twilio, for the toll-free verification US carriers require, what the owner enters: the firm’s legal and trade name, website, business type, EIN, business address, and a contact person’s name, email and phone, together with a description of how the firm texts its clients, the consent script its staff read, a sample text and an estimate of texts a month. Nothing about any client is part of that. Either way: for each text someone at the firm sends to a client (which Fylely allows only to a number the firm has recorded the client agreed to be texted at), the client’s mobile number, the firm’s sending number or Messaging Service, and the words of the text — for a text-to-pay, that includes the invoice number, the balance and the link to the invoice. Nothing is sent automatically. To check the credentials when they are saved, Fylely asks Twilio for the account’s name, type and status, and whether the sending number or service is on the account. Replies go to the firm’s Twilio number. Only if the firm owner points that number’s incoming messages at Fylely does Twilio send Fylely each text a client sends to it: the Twilio account and message IDs, the number it came from and the number it was sent to, the Messaging Service if there is one, the words, how many pictures or files came with it (which Fylely does not fetch), and Twilio’s STOP, START or HELP marker. Fylely sends no reply of its own. With a number from Fylely, the incoming messages are pointed at Fylely when the number is bought, and the subaccount and its records are held under Fylely’s agreement with Twilio; the owner can stop at any time, which closes the subaccount and releases the number. With the firm’s own account, the account, its number and its message records are the firm’s, held under its own agreement with Twilio, and the owner can disconnect at any time, which deletes the stored credentials from Fylely. |
| Free Law Project (CourtListener) | Checking that US case citations lead to a real decision, only if the firm owner switches on Citation checkDetermined by Free Law Project. | Nothing, unless the firm owner switches on Citation check in Settings → AI & privacy. If they do, a request goes to CourtListener only when someone at the firm presses Check citations on a document or a draft: each US case citation Fylely found in it, as volume, reporter and page (for example “123 F.3d 456”), and nothing else: never a case name, the words around the citation, the document, its name or anything about the matter. A citation points to a published decision that may name people, so we treat it as personal information. CourtListener answers with the decision each citation leads to, its name and its page on CourtListener. Fylely keeps that answer for up to 90 days, without saying which firm, document or matter asked, so the same citation is not sent again. CourtListener is a free public service of Free Law Project, a non-profit, used under its published API terms rather than a contract with us. The owner can switch Citation check off at any time; nothing is sent after that. |
| CanLII (Canadian Legal Information Institute) | Checking that Canadian neutral citations lead to a real decision, only if the firm owner switches on Citation checkDetermined by CanLII. | Nothing, unless the firm owner switches on Citation check in Settings → AI & privacy. If they do, a request goes to CanLII only when someone at the firm presses Check citations on a document or a draft: each Canadian neutral citation Fylely found in it, as year, court and number (for example “2019 SCC 65”), and nothing else: never a case name, the words around the citation, the document, its name or anything about the matter. A citation points to a published decision that may name people, so we treat it as personal information. Fylely also asks CanLII for its list of courts, which carries nothing of the firm’s. CanLII answers with the decision’s name and its page on CanLII. Fylely keeps that answer for up to 90 days, without saying which firm, document or matter asked. Reporter citations such as “[1999] 1 S.C.R. 1” are never sent. CanLII is a free public service for Canada’s legal profession, used under its published API terms rather than a contract with us. The owner can switch Citation check off at any time; nothing is sent after that. |
2. What We Do Not Use
We do not use analytics, advertising, retargeting, or session-recording services, and there are no third-party scripts, embeds, or tracking pixels in the Service. The exceptions: Google's file Picker and sign-in, and Dropbox's Chooser, which load only when someone presses Google Drive or Dropbox on a matter's Documents tab to copy files from their own account (see section 3); Plaid's Link, which loads only when the firm owner presses Connect a bank or Reconnect, so the bank sign-in happens in Plaid's window rather than ours; and the optional Outlook and Word add-ins, whose pages run inside Outlook and Word and load Microsoft's own Office.js library, as Microsoft requires every Office add-in to; it is never loaded in the Service itself. Fonts are served from our own deployment rather than a font CDN, so loading a page does not contact a third party for them.
3. Connections You Set Up Yourself
Someone copying files into a matter from their own Google Drive, Dropbox or Box account chooses the files in that service's own window (Google's Picker, Dropbox's Chooser) or, for Box, signs in to Box and chooses them in Fylely. Fylely receives only the files chosen, and copies them into the matter; it sends those services nothing of the firm's. Google's permission lets Fylely open only the files picked, for an hour; Dropbox's links last four hours and need no permission at all; Box's sign-in lasts an hour, is held only in that person's browser, and is not kept afterwards. Each is the person's own account with that company, not a sub-processor of ours.
If the firm owner makes an API key or a webhook in Settings, the firm's own software reads records from Fylely (or, if the owner allows it, adds and changes records, sends new enquiries in or sets up its own webhooks), or Fylely sends events to an address the owner chose. Whoever runs that software or that address, Zapier included, is a provider you chose, not a sub-processor of ours, and what they do with what they receive is between you and them. Nothing is sent this way unless the owner sets it up.
4. Your Clients’ Information
Where you use Fylely to hold information about your own clients, you are the one deciding what is collected and why; we hold and process it to provide the Service to you. If your professional obligations or your own client agreements require a data-processing agreement, or a restriction on where data is stored, contact us before entering client information rather than after.
5. Changes
If we add or replace a sub-processor that handles information you have entered, we will update this page. If a change materially affects how that information is handled, we will also tell account owners by email rather than relying on you to re-read this page.
6. Questions
Questions about this list, or a request for the documentation your firm needs before adopting the Service, can go to our Privacy Officer using the contact details in the Privacy Policy.